EskeRahn

I do not think I done a stock flash, that did NOT have this memory issue, so would strongly suggest to either always do the reset, or at the least make a check, part of the installation procedure

Sadly I highly doubt that more will ever be produced, nor that they have any left to send out. Though they in theory might make a new one I highly doubt it will ever happen - frankly I'm positively surprised that this community site is still kept alive.

Well it depends a bit on what you mean. Originally yes,, I for one bought a Pro1 ages back, and got it in 2019. but I have no idea when a weborder was last sent out,

...Ah well I took the chance and 'up'graded... lineage-22.2-20250621-nightly-pro1-signed.zip on June 1 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. Will report back in some hours if it seems to have become usable.... ADD: From 94% to 23% in 11hours, so 6½% per hour, so still completely useless! Oh well back to 22.1 it is...😠

I see a LOT of changes for the 20250614, including something with network callback. The 20250621 seems to contain only minor changes, And 202506207 does not look related. Anyone tried either release and see if they make Lineage usable again on a Pro1?

In theory I think yes, but in practise very hard without seeing the display. One option could be to copy the content of the entire user partition, but again some interaction with the phone might be needed. If you have allowed google to take backup, at the least some data is saved. And if you allowed google to stea...erhm STORE your pictures, they will be saved in the cloud too, maybe in poor resolution though. But start booting it to bootloader. If you see a menu, it is software 'only', so you would know that you are unlikely to need a new display.

Hmm this might actually be good news, as this sounds more like a software bug than a hardware bug. Can it boot into bootloader-mode showing the menu? If so a factory reset is most likely the way to go, and if that does not do the trick a full reflash to factory mode. (follow the first post on the forum)

If you are 'lucky' it is 'just' the display, though that it not something you just go and buy a new around the corner, it is possible to replace for many with a little tech knowledge. If I recall correctly @CornholioGSM has offered the service of swapping for some price. so if that still holds and depending on your location, that might be an interesting option.

It does not seem to be everyone that gets this bug, but the risk is clearly there.

Did you try with an OLD computer or one on Linux? As I explained usb-3 under windows can be problematic. If no data-communication at all can be established there could be an electric problem, e.g. dirt in the plug, or a plug that has gone partly loose

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