EskeRahn

....it happened shortly after unplugging at 98%. Which in it self will give a drop in voltage. I then checked for new app updates at the Android Market. So in total it went from 98 to 94 in fairly short time, and the logic mathematically predicts that it will be depleted shortly.... Perhaps this could be prevented by adding a check for NOT doing these estimates within the first minutes after unplugging.

Minor bug. Just got this notification: I would say a bit early to suggest to turn on the battery saver at 94% *LOL*

(do with flash - after some troubles with win11)

(I can get my old driver installed and working temporarily disabling the driver check as described in Fix 6 here, but that only last to next boot)

Did you find a workaround? I just got a new PC with Win 11, that requires drivers to be signed (unless going through all kind of hoops to loosen the security at bios-level to disable that). With the default windows driver ADB works just fine. But fastboot does not.... The driver I used on the previous PC (that worked fine) are not signed. I tried downloading from Google, but they aren't signed either. The force method mentioned on XDA does not work on Win 11. (I do not get the question to install it anyway, it is just denied) I have not tried all the manufacturer on the list.

New to me too. 🙂 Let us tag @Elysia to see if she can find a way to make stuff like this more visible. If no smarter solution found, a pinned post with links to stuff like this might do the trick. Maybe the general header on https://www.fxtec.com/ could be added to the community too? Perhaps even with something smart like the 'Stars' in the community, to indicate if the other 'tabs' have content the logged in user have not (yet) seen?

I agree that it sounds like a software priority issue. But rather than lack of priority I would guess something else having too high priority thus interfering with the keyboard operation, as not everyone reports it. But could still be a system isssue, where some other system stuff gets activated by some actions or apps not all use or use the same way. Starting with the ones power consumption points at as posssible culprits, I would try to stop (or even deactive/uninstall) stuff and see if whatever triggers the phenomenon can be narrowed down. Ultimately trying a factory reset, and t

Hmm cable perhaps, or connector for some reason not working as it is supposed to?

If we look at the previous update dates, it has been slightly over a month every time (less May+June) since Janurary. Creeping from January 06 to September 20 - So hardly a surprise that it has gone over a month this time too. Just saying....

Update to October 20, with October 1 security patch using flash, and with OpenGapps-Pico went smoothly. Known keyboard bug still there (see lineage thread)

(lineage-18.1-20211018-nightly-pro1-signed.zip on October 1 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above.

I feel similar to Hook. The lineage is a cleaned up Android, where you can infest it with the Gapps you need or none at all to your liking. The Aicp is (in my layman terms) like a Lineage with added options to tweak as you please. I like the AICP better, as it somehow feels cleaner. But I must admit that I barely use all the options, as none of the OS's are on my daily driver (a normal retail unit) that runs plain Android. I have a suspicion (though I have not yet tested!) that some of my apps will not work if I upgrade from stock Android to AICP. One app that I find crucial with a fli

Indeed, thanks for correcting. 🙂

A modified case for a Honor Huawei P20 Pro. See e.g this

,,,Or you could make a case where the flap goes the other way. Just 12h stiching... *LOL*

If you add a strategically placed magnet to your case it does. You can get these very tiny (and cheap), I bought various sizes from ebay, (display the below at full size in normal portrait for position)

(Download and flash worked smoothly too)

Though it does not look like it, it IS clean. it is dust&pocketlint that have crept into the case, that have 'sanded' down small areas of the back In hindsight it would have been wise to add a small sheet of some tissue between the TPU-casing and the Pro1 And though the above might look like deep dents, they are so shallow I can hardly feel any difference sliding a fingertip over the back

I do not use it either. But thanks for the warning to those that do. (there are no measurable costs for the function detecting a close with the HAL-sensor though)

I agree. The back of my daily driver is most likely just as worn as if I had not used a case. Though the wear with a case is 'spotted'.

If you should endeavour in the project again, you should consider the variant where the straps meet at the side https://community.fxtec.com/topic/2681-how-to-openshut-the-pro1/?do=findComment&comment=42061 Whether is should open as a 'Japanese' or 'western' book is a matter of taste of course.

If I don not remember wrong, the issue there is the margins, not that it does not react at all. So I think @Rob. S. is on the right track with something not connected, either the connector or a cable issue,

(merged)

I fail to see why we need a new thread on this, why not post in the old one just reviving that? As already posted there, the proposal is more than just a new print, as there are not 'currently' yellow under that many keys. Sure it is feasible, but come at a cost - and possibly delay(!) - if they have to change the base they already use, and add more yellow stickers before the black layer is printed. (of course the material cost of the stickers should be negligible, but it is likely to come at a cost to ask the supplier to modify their process)

The first one looks interesting indeed. Though I got so many of my own (less elegant) 'home made'/modified variants, so others might be more in need.