Jump to content

LineageOS 22.x Official Release for Pro1 (QX1000)


Recommended Posts

  • Replies 132
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Official Release: https://download.lineageos.org/devices/pro1/builds Changelog: https://download.lineageos.org/devices/pro1/changes First Build: LINEAGE-22.1-20250101-NIGHTLY-PRO1-SIGNED.ZIP

(BTW it seems so greedy that the reduced current at 98% makes it hard to reach 99%, it has been at "98% - charging" for over half an hour 🙈... display off, checks about every five minute...) UPDATE:

It would be far easier to stay with lineage 21.0: That branch still gets patched with ASB fixes upstream, so all you'd have to do is fetch the source tree and make the build, which is piece of cake. B

Posted Images

9 hours ago, EskeRahn said:

I wonder if it is like AICP a nice project that was just made horrible by some crucial bugs.... 😣:classic_sad:

Not that I have anything constructive to add, but in LineageOS's defence: They are stuck forever with the Linux kernel version and drivers that shipped with the original Android 9 OS. As the divide between increasingly modern Lineage/Android userland and the base Linux OS amplifies, bugs like this become more and more likely, unfortunately. 

  • Like 2
Link to post
Share on other sites
3 hours ago, claude0001 said:

Not that I have anything constructive to add, but in LineageOS's defence: They are stuck forever with the Linux kernel version and drivers that shipped with the original Android 9 OS. As the divide between increasingly modern Lineage/Android userland and the base Linux OS amplifies, bugs like this become more and more likely, unfortunately. 

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.

  • Like 1
Link to post
Share on other sites
11 hours ago, EskeRahn said:

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....

It would be far easier to stay with lineage 21.0: That branch still gets patched with ASB fixes upstream, so all you'd have to do is fetch the source tree and make the build, which is piece of cake. Basically all you need is a Ubuntu virtual machine with enough storage and RAM.

Because of the new QPR release scheme, staying with 22.1 is more complicated: Only the latest QPR (22.2 as of writing) is getting patched according to the ASB. 22.0 and 22.1 are not and I'm not sure if the available ASB patches for 22.2 could be directly applied to them. At least in the long run you'd probably have to backport all the patches yourself if you wanted to stay with some intermediate QPR.

Anyway, I'm not going to do either of these things, sorry. Imho, distributing an unofficial ROM really makes sense only if you daily-drive it yourself. Otherwise bugs, like the one here discussed, slip through unnoticed far too easily. Since I keep my Pro1 on LOS 16.0, those builds are the only ones I feel comfortable distributing.    

  • Like 1
  • Thanks 2
Link to post
Share on other sites
10 hours ago, claude0001 said:

Imho, distributing an unofficial ROM really makes sense only if you daily-drive it yourself.

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.....

  • Like 1
Link to post
Share on other sites

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

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

Terms