EskeRahn

(I noticed on the AICP download site that at the least some devices are on their third iteration of 'S', e.g. Pixel 5a, so hope we will get a less buggy version soon)

And this is precisely the problem FxTec and many many others in all kind of branches are faced with... It isn't even limited to tech. Sure we have paid to fxtec so they are the one we can blame, and they can blame someone else and so on, perhaps in a long chain - but it unfortunately will not bring the devices closer to our hands, so rather futile. FxTec isn't a huge player with a lot of punch. If someone does not do what they have promised, what exactly do you think FxTec can do? Most often they are faced with only two options: More waiting, or looking for alternatives - and either mea

....On the battery-charging issue. See this.

We have in the lineage threads for 18 and 19, as well as AICP-R had a number of posts on a strange charging issue, where it keeps the battery at a stable level, neither charging nor discharging while connected. This seems not to be limited to the Pro1, but is an issue that also affects the Pro1. See the post I made here in the Lineage 19 thread. Unfortunately this common problem is rather illusive, as it is not easy to say how to trigger or avoid it. All we know for sure is that it is temporarily gone after a reboot. I have tried multiple times to find a 100% reproducible method, b

It may be the easiest for FxTec as it is out of their hands, but that does not mean that it will be fast... 'everyone' is whinning over how hard it is to get stuff from China, that a few years back was as easy as pie to get... Just heard about the bicycle(!) sellers in Denmark having two years of backlog as they can not get the parts they are used to.... Had anyone guessed this crisis would last this long, local production would have been (re)started for many things.... On the other hand some things still gets here within a few days. So have no idea on the finer details in what is go

(lineage-19.1-20220718-nightly-pro1-signed.zip on July 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313)

I doubt it is hardware, as we 'only' have it reported in here for Lineage 18+19 and AICP-R and neither Stock Pie nor Sailfish nor earlier Lineage/AICP. However it COULD well be that something in Android 11/12 (And thus Lineage 18/19) needs to be set up differently than what it is currently to work correctly with the Pro1, so could well be outside what is changed by the LineageOS implementation. If we had a plain AOSP 11 or 12, we could see if it has the same problems. BUT as we have not (yet) found a consistent way of triggering the bug, it is really hard to test/debug what is going on.

Interesting that you detected QC charge issues as well, but that is unfortunately an additional bug you found... I'm not using QC and the bug I see is NOT that it will not draw power. It keeps the phones battery at a stable level. So the attached power DO feed the phone, but without really charging (or discharging) the battery.

Though I doubt that it is software, you could try to install and run KeyEvent. Showing the make and break codes for each key. If you press one key, and keep it down, and then another you will see that it you wil get independent codes, and two different up's If you do the same with the two shift keys, you will see that they act as parallel. Press and hold 1, the press and hold the other, and relase the first then the second, and it acts exactly as if it was one key. The yellow arrows does not (and if they work, the ctrls act in the same way as the shifts(

I hope you are right 😁 Though we never found a way to consistently trigger the bug, so hard to say for sure. Has anyone that updated to 20220711 seen the charging-bug since? Bad news: Just managed to trigger it...... (at 67%) What I did was: In unlocked state, Plugged, unplugged and replugged a few times Locked, waited three minutes (while it was charging on a table). Picked it up and unlocked the device with fingerprint Unplugged and replugged Tried to do exactly the same after a reboot, but it did NOT trigger it again, so not a consistent method, Tried

He he. If so I doubt things would work as relative well as they did... Especially the camera But is a bit odd that it is 'released' in a state where I can not even do a clean wiped GAPPS-free flash and boot it.... So I assume that in special conditions an upgrade might work. An obviously thing to try would be a clean gapps-free wiped AICP-R and then do a AICP-S flash without wiping. I have not tried that (yet?) Tried, no cigar...

See this thread for working install: ---------------------------------------------------------------------------------------- Below is initial attempts where I used a wrong boot image Using this AICP.S mage aicp_pro1_s-17.1-WEEKLY-20220713.zip I was super optimistic and went from 16.1 with OpenGapps to 17.1 and MindTheGapps 12 in one go, without a factory reset (=wipe). ...and that did not go well,,,, I got a boot-loop (I used the recovery-image from Lineage lineage-19.1-20220711-recovery-pro1.img) Then did a factory reset, and it booted - obviously with

Aicp S-17.1 now available, though not really working (yet?).... See

(on the wiring, the two shifts and the two ctrls are physically wired pairwise. so though we see 66 keys, there are only 64 distinct keys)

Indeed and remember that some have preordered not perked for a Pro1X, and we have no knowledge on how these two lines are interwoven, but I guess they all come after the Pro1 orders, if things goes by chronology....

(lineage-19.1-20220711-nightly-pro1-signed.zip on June 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313)

(lineage-19.1-20220704-nightly-pro1-signed.zip on June 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313)

Same here. It could be unfair, but I have the feeling of Magisk like a can of worms I avoid to install.

The keyboard itself seems very close to identical to the Cosmo, and some have wrote about using that in here. If i recall correctly you can do thumb-typing. ADD: Here two report it in a non-positve way as too large for it

Peronally I have long been advocating for one hand operability, and this means a limit around 65mm wide. BUT there are two drawbacks on that. One is lesser keys (or for me worse: fewer). Secondly the display would be lesser, and that again would mean less information (=a lot of scrolling) or the use of a font so small that it gets beyond what my aging eyes can handle without extra glasses. Also remember that the newer ugly material design wastes more screen space, so many apps are today designed for the oversized phablets and not phone-size (quite similar to a lot of apps working poorly i

The principal difference keyboardwise (apart from the opening system) is that Pro1 got more but minor keys. So I expect what is the best for a specific person depends on if they need A-Z (almost) only, or have fingers that struggle with small keys, if so the larger keys are likely to be a plus. If you on the other hand want national letters and other keys in their standard positions the Pro1 is likely to be a better choice.

would be great if the niche products could find ways to help each other, as they target different parts of the small keyboard segment. But the big question is if the visions are compatible?

The second i've heard mentioned before. The first is new to me. Before the obvious suggestion of a factory reset, you might try to do a very long power-press, (about 10 sec) it seems to do a deeper reboot than just the ordinary 'restart'.

Glad you found a workaround. but odd indeed.

odd, the combo works fine here...