EskeRahn

I would be surprised if the handling of the physical keys and touch are not substantially different, so do not think we can deduce from differences between the two.

Yes it is stated somewhere that IF you want to use gapps, then it MUST be installed before first OS-boot after a flash, and must be reinstalled after each OS flash.

That sounds like something eats up the processing power, so it is unable to process the keystrokes in real time. But obviously what ever does the processing should have had sufficient priority for this not to happen normally. Anything you are aware of running in the background that might be what is disturbing. E.g. some complex sound decoding, playing high-resolution sound? I would try to install something like GSam or the like, to find out what is using the resources. (GSam registers the battery pull over time, but any substantial CPU activity should also leave a mark in the power cons

Silly me, i did not read the log provided closely enough> .... healthd : battery l=75 v=3983 t=30.0 .... So that should hardly cause anything to shut down

Swapped: A=Keyboard, B=Case - at the least that is the naming used in the FactoryKit....

Most likely a scancode for historical reasons is a byte, somewhere in the 'pipeline', so the map to 464 must happen later.

The Hall_a is the keyboard open/close detector, the Hall_b is the one in the display (case detection) They are called a and b in the 'factorykit'-test (The one just above OTG almost at the bottom) See this

Look at it another way. Why should a bank care if they did not see a reduction in their risk of loosing money somehow?

(lineage-18.1-20210830-nightly-pro1-signed.zip on August 5 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.

Have not tried it (I might find some time for it later) but I really think you should consider @Slion's idea of changing the initial qwertY/qwertZ switch to some radiiobuttons (or a drop down), collecting the settings in named sets. There could be one (say "custom") with all the options unfolding. But it will be terrible difficult for most user to understand the consequences of all the switches. It gets a bit like AICP: very customizable, but also very hard to set up for the normal user. But if we are into switches, the alt or fn debate could be handled by letting that be yet another switch

Well part of it is that could well be that in many countries the banks hold the responsibility for fraudulent activities on your account, unless they can prove that you have shown gross irresponsibilty, e.g. Sharing your pasword. And as security on phone banks apps are often down to simple four digits pins, and phones are stolen more than laptops, it all adds up to higher risk for the banks, so at the least they want to reduce the risk of any troyan horse or the like accessing your bank app. And this is easier on rooted devices. But of course they could offer an option of you taking all

Ah, so though obviously very impractical, at the least you will be able to charge it this weird way, until the bug is found and fixed. But really odd that only some are affected by it. I use a pretty dumb no name charger, to keep the charging current low (about 5W), to be kind to the battery, I wonder if that is related? ADD: I'm using a charger with roughly 5W cap. I have tested that it starts fast charging too, but did not leave it fast charging for a lengthy period. But as fast charging gives quite a heavy heating of the battery, it just MIGHT be a security mechanism tha

Maybe the usage of the Logo/Meta-key as the selector for the non existent physical keys would be even better than Alt/Sym/†, so the hardcoding does not touch the normal modifiers at all. This way any 'missing' key produced with Logo could be used combined with any modifier. And obviously if Logo is not pressed with a recognised key, it should be handled as Android Meta. The only drawback I see with this is that the Logo key pressed alone would not act as a Meta pressed alone, but plain Meta could be mapped just like any other 'missing' key. ....One could perhaps even map if met

Uh, that is bad... Just for test. Can you turn it off, and then charge it (assuming you have the flag for boot on charge cleared obviously). fastboot oem off-mode-charge enable (to be sure it is an issue 'limited' to while in LOS, and to be sure you can always charge when Off as a fall back).

Indeed, it would be clever if Fn was a modifier if (and only if) not hardcoded to produce a plain key (physically not present on the Pro1) (And whether this is to be Fn or Alt is an entirely different discussion *LOL* )

It is the key often represented with a magnifier glass for search, Also used combined for short cuts - I have no idea what else it is used for...

Try pressing the Logo+Alt , it will toggle the Caps mode

(Phew that took a while to get through all the posts the last week here 😅)

Shift and ctrl

I disagree, if QWERTZ print-layout only work some languages, it sure should be considered a bug. The smart idea by @tdm to have a setting selecting the print-layout, independent of the language selection, is a MUCH smarter solution than what we got on stock. Look at all the 'doubles' @Anssi Hannula made to make things work, e.g. Danish for qwertY print and Danish for qwertZ print. The idea by @tdm to convert the keyboard to a standard one, and then have standard android languages on top is clever, as it means that any language known by Android should work out of the box. And the point o

(Very late to last weeks many post in this thread) I think this looks like a PERFECT solution with two optimized build in layout-interpretation, but ALSO to have one additional mirroring stock. I bet it will be very little overhead code, but will be very helpful for various international users to be able to benefit from the work of @Anssi Hannula and others without having this to be redone in LOS-variants.

I know that the 'addonsu' works with 16.0, is there also one for 18.1 ?

Welcome. Both on stock Android, LineageOS 18.1 and AICP Q, the Pro1 got a stamina around 10 days connected but idle. So much a matter of what you want to run on it, and how much screen-on time your usage pattern requires. It also matters if your normal usage is mainly outdoor in the sun or indoor, as brightness affects the power usage. There are other threads on Pro1 stamina in here.

(i did it between the two packages, but it stayed on b - and yes it is magic to me too *LOL* so purely guessing here, it does not really print out much during the install, I guess that some more details ends up in a log-file somewhere)

I do not think that is quite accurate, I think it is the package flash that ends by setting the next boot partition to 'the other'. If you in recovery mode goes to advanced, reboot to recovery again, it does not change each time. I used to do that between gapps and su on 16.0, and they both went to b.