EskeRahn

Digging three years back in history, we had odd battery issues previously, that magically disappeared Back then 10% per day was good, and 30% per day was horrible. Interesting to compare with the numbers we get with even 22.1 not to mention 22.2

...So If I should maintain an older Rom I would have to go back to when the keyboard last worked, I'm not sure if it was some 21.x or 20.x .....

Totally agree, and I really only use it for testing the usability of LOS, and have it idle as a workphone, that does not ring each month anyway... So would easily overlook al kind of bugs myself, I just check that it installs smoothly, check if the keyboard works (and it has not really worked for me for quite a while) - and else keep it on stand by. So if I suddenly could not make or receive a call there could go half a year before I found out....On the other hand a drop in idle stand by was quickly spotted.....

Oh I know it is good people doing their best - I'm just frustrated, sorry for whining. But as you keep the 16.0 alive, we can hope that you, or someone else with the suitable knowledge, can keep the 22.1 alive, if the 22.2 stay broken.... Let us see what the coming months or the 23.0 next year will bring. But as this is a bug not all seem to see, I guess the chance for it ever being fixed is slim. As with any bug the first step to a fix very often goes trough being able to reproduce it.

Note that the bug is on 22.2, but NOT on 22.1

Next step 22.1 and factory reset here, wasted enough time on useless 22.2 - I wonder if it is like AICP a nice project that was just made horrible by some crucial bugs.... 😣 (PS the factory reset, sets the band selection back to the default LTE/TDSCCDMA/CDMA/EvDo/GSM/WCDMA) ADD: And back to a more reasonable consumption 4% in roughly three hour Will try "LTE/CDMA/EvDO/GSM/WCDMA (PRL)" on 22.1 just for the fun of it..... And it is down 4% in another 3½ hours

"LTE Only" and suggested was even worse, see edited above...

Picked fairly at random... Need UMTS B1+B and LTE B3+7, https://www.frequencycheck.com/carriers/3-tre-denmark and or https://www.frequencycheck.com/carriers/tdc-denmark (GSM 900, 1800, UMTS B1+B8, LTE B7+B20+B3)

...I got it at default LTE/TDSCCDMA/CDMA/EvDo/GSM/WCDMA just tried to change to LTE/TDSCCDMA/GSM ADD I: ...The "LTE/TDSCCDMA/GSM" ate 50% in slightly short of eight hours while I slept - so still utterly useless. ADD II: Tried "LTE only" (after some recharging) And this seems even worse. 5% in half an hour!!! ADD III: Now trying "LTE/CDMA/EvDO/GSM/WCDMA (PRL)" , as suggested by @CornholioGSM Absolutely horrible 9% in an hour, if it improved anything compared to "LTE only" it was by a tiny tiny margin.

(lineage-22.2-20250531-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20250214_082511) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage. The draining bug with a sim inserted is still there... 5% in the first hour, completely idle, with almost all apps removed 👎

Well we could live with that... I got a bit better, but mine is currently a REALLY minimalistic setup, and was with zero screen interaction, so that was to be expected. But in the order of 1% / hour would be what I'm used to see WITH the sim mounted and online on e.g. 22.1.

@TeZtdeviceInteresting idea with the Aeroplane mode, I will try that overnight WITH the sim physically mounted. ADD: After 11 hours in Aeroplane mode it was down to 94%, so roughly 0.5% per hour. Certainly not impressive, but tolerable. Will recharge, and see what the day brings, but has not got my hopes up high..... ADD II: still bad out of Aeroplane mode

(lineage-22.2-20250524-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20250214_082511) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage. I have no idea whether the draining issue has been improved/fixed. The bug is still there...

There are SO many things that could be tested and adjusted, that just might affect this, so really a complex job to pin-point. Just like FxTec never really pin-pointed the conditions in which the Pro1X has network issues.... But it sure could be interesting to dig into the differences. A bit sad it came with a semi-major update, making it much harder to give a qualified guess on where the bug was introduced.

No, I have not bothered to fiddle with that, nor have I tried with a sim from another carrier.