claude0001 1,150 Posted March 26 Share Posted March 26 The latest build of LineageOS 16.0 (for SD835-Pro1 only) is available at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1. Go for the ROM dated 201230326. It includes backported ASB fixes up to 5 March 2023. As for the last months, there is no upstream code review any more. I can confirm that there are no problems on my own Pro1. Beyond the ASB, there are no changes since last month. My full list of increments with respect to the upstream LOS 16.0 tree can be downloaded for reference. Have fun. 2 Quote Link to post Share on other sites
claude0001 1,150 Posted April 25 Share Posted April 25 So ... in case you want to relive the good old days with the Pro1 (SD835 only!), LineageOS 16.0 just got another update. At https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 fetch the ROM dated 202304024. It gives you backported ASB patches up to 5 April 2023. There are no other changes compared to last month's release. Refer to my tarball of localmods for the full list of code changes with respect to upstream LineageOS 16.0. Have a lot of fun. 3 2 Quote Link to post Share on other sites
claude0001 1,150 Posted May 17 Share Posted May 17 Another update of LineageOS 16.0 (for SD835-Pro1 only) is available at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1. The ROM dated 20230516 gives you backported security patches up to the 5 May 2023 ASB. No other changes since last month. As usual you can refer to the tarball of local mods to learn all about differences with respect to the official lineage-16.0 tree. Have fun! 1 2 Quote Link to post Share on other sites
raymo 156 Posted June 23 Share Posted June 23 (edited) Hi @claude0001 In order to experiment and gain freedom in my SD card I've installed your (non official) LOS 16 on my old Pro1. Unfortunately I had some hassle bug in my phone (who remains me the beginning with LOS in a new pro1) -No camera (app crashed at launch on day 2) -When receiving (or doing) a phone call, screen is stupidly dark, with absolute no chance awaking as I'm in a phone call, it's funny but not for a long time. -Strangely keyboard is...slower, with often ghosts touch. What a pity, it was so nice to freedom access to SD card, but as pro1 is my only phone, I can't live with this at this moment. I precise I've reflashed phone with stock (using LOS17.1 before) and complete wiped data before any LOS flash. Could this mean there are hardware difference in good old pro1's ? Also surprisingly LOS 20.0 work like charm. No luck here, and I'm afraid for the pro1x if this phone come one day in my hand, but this will be an other story 😄 So, this was my report, and really really a big thanks for your good work 😄❤️ Edited June 24 by raymo tag Quote Link to post Share on other sites
claude0001 1,150 Posted June 26 Share Posted June 26 (edited) Hi @raymo, Thanks for your interest and feedback. So you are saying you had no HW keyboard issues with LOS 17.1, but input problems started when you tried my ROM? That is interesting: My keyboard driver indeed contains several mods with respect to the upstream LOS 16.0/17.1 one, as documented in my patch log. Partly, those are backports from LOS 18.1 and above that are actually supposed to improve keyboard behavior ... E.g. I think unwanted multiple presses of the same key became much fewer (for me) after I had backported the respective patch from 18.1. I do experience problems with (sometimes) unresponsive keys on my Pro1, but was assuming this was due to the ageing of the keyboard ... Maybe I was fooling myself ... I am currently compiling a test build with all my keyboard-related mods disabled, i.e. with the original driver as it came with (official) 16.0 and 17.1, and will see what difference that makes on my device. Thanks for reporting. Unfortunately, I cannot reproduce your other two issues: While I rarely use the original camera app, it does seem to do its job on my Pro1 with my latest ROM (May 2023 ASB). I normally have OpenCamera set as default, though, so I never really battle-tested it. Also screen brightness auto-adjusts fine during voice calls for me (if set to auto) and can also be manually adjusted using the top-bar slider. But maybe I misunderstand the problem here. Edited June 26 by claude0001 Quote Link to post Share on other sites
raymo 156 Posted June 27 Share Posted June 27 This is weird, but I am quite sure my keyboard has a hardware problem. In my opinion this is related with cable sheet or with parasite appearing in the i2c bus, as when I press on its border it suddenly works perfect, see my related post here. I wanted to dismount the whole keyboard, but I never found a phone replacement for my daily use, and I'm a bit afraid I could definitively broke something. Unfortunately Fxtec doesn't send spare keyboard. As very few users have reported a problem with (sometimes) no responding keys I'm not sure this problem is related with your Lineage builds, but with a faulty hardware or something. Today it's not perfect, but suitable for daily use (and I developped an huge allergy on touchscreen system particularly with the original intrusive android os). I had two second-hand pro1 (I loose the first one) and who were (as far as I know) igg first batch pre-ordered. I had this strange behaviour on the two devices. My best option will be to find a broken pro1 as spare parts, not easy to find with many LTE problems reported on the pro1x. And I'm not sure keyboard from 1x is compatible with the 1's. Another story, the bug with black screen hapenning in phone call was here with first LOS16 batch but disappeared later with OTA update, wich is weird to explain as your build use the latest drivers and patch. This bug is sometime reported in LOS with other phone, but in my case it seems not related with proximity sensor, I tryied some fix to recalibrate proximity sensor and other workaround with no luck. Quote Link to post Share on other sites
claude0001 1,150 Posted June 27 Share Posted June 27 (edited) @raymo: I'm a bit confused now. I had understood your initial report in a way that, with my unofficial LOS 16.0, you experienced keyboard problems that you didn't previously on 17.1 and also not on your present 20.0? I anyway just built a test-rom with all my keyboard mods and backports disabled, and will test that on my device. However, I too believe that my keyboard in fact just has (small) hardware issues. It is true that the proximity sensor is sometimes slow to react when you take the phone off your ear, but eventually the screen always does switch on for me. I did nothing to change that sensor's behaviour in my rom. Yes, I am based on the same code and blobs than the last official LOS 16.0 OTA (20201026-nightly) was built from. Of course, on top of that, I include all the ASB fixes that were made in the 2.5 years since. Those are quite a few patches indeed, but none of those was device-specific to the Pro1 ... Edited June 27 by claude0001 Quote Link to post Share on other sites
raymo 156 Posted June 27 Share Posted June 27 (edited) Quote I had understood your initial report in a way that, with my unofficial LOS 16.0, you experienced keyboard problems that you didn't previously on 17.1 and also not on your present 20.0? True, and sorry I was unclear. Yes my keyboard problems were really really worse with your unofficial LOS16.0, ghost touchs and no responding keys, really worse. And it's far better in LOS20.0, as it was in LOS17.1, strange. Quote it is true that the proximity sensor is sometimes slow to react when you take the phone off your ear Same here in LOS20.0, but works far better as in LOS17.1, where I had to push power button to awake screen in phone call. Don't worry I've reported here because I thought it could maybe bring an explanation, considering a hardware who is not perfect. Also fingerprint works well in LOS20.0 (slowly, but well), poorly in 17.1 and quite not in 16.0. I wonder how my settings could explain this as I tested for months in LOS16.0 and LOS17.1. Edited June 27 by raymo Quote Link to post Share on other sites
claude0001 1,150 Posted June 28 Share Posted June 28 (edited) @raymo: So I installed a test build of my ROM with all my keyboard-related modifications disabled. I.e. the driver is the same than in (official) LOS 16.0 and 17.1. My sometimes unresponsive keys ("N" is the most problematic one for me) are definitely still there. As I remembered, I get a lot more unwanted doubles ("douubless") this way, as the respective patch introduced in LOS 18.1 is now missing. Edited June 28 by claude0001 1 Quote Link to post Share on other sites
claude0001 1,150 Posted June 28 Share Posted June 28 I've uploaded another build of LineageOS 16.0 at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 which includes backported ASB fixes up to "5 June 2023". Go for the ROM dated 20230628. Based on @raymo's feedback above, I have removed @Slion's "fn-tab = alt-tab" patch from the keyboard driver for now. It was the only mod that -- while significantly modifying the driver code -- was never included in any later official LOS trees. Based on my own testing, I still do not think it introduces any problems with regard to keyboard response, but I want to give it a shot. If "fn-tab=alt-tab" is super-important to you, please PN me, I'll then make a dedicated ROM for you. As usual, all my code modifications with respect to upstream LOS 16.0 can be followed from the patch tarball linked above. Have a lot of fun. 1 Quote Link to post Share on other sites
EskeRahn 5,179 Posted June 29 Share Posted June 29 On 6/27/2023 at 5:54 PM, raymo said: In my opinion this is related with cable sheet or with parasite appearing in the i2c bus, as when I press on its border it suddenly works perfect, see my related post here. If my memory does not fail me we have had at the least one other post on this, though I think it was quite a while back, maybe 2020 or 2021? If I recall correctly it was the screw under the sticker that was loose. Quote Link to post Share on other sites
MonCon 87 Posted June 29 Share Posted June 29 (edited) 13 hours ago, EskeRahn said: If my memory does not fail me we have had at the least one other post on this, though I think it was quite a while back, maybe 2020 or 2021? If I recall correctly it was the screw under the sticker that was loose. This thread? Edited June 29 by MonCon 1 Quote Link to post Share on other sites
raymo 156 Posted June 30 Share Posted June 30 (edited) This one : Unfortunately just tightening the screws doesn't work for me. Edit : find a workaround, I've entirely disassembled the keyboard, and it works perfect (in LOS20.0) I will test a few days and make a new post later with pictures. Joy of joyces. Edited June 30 by raymo workaround 2 Quote Link to post Share on other sites
claude0001 1,150 Posted September 7 Share Posted September 7 I have uploaded a new build of LineageOS 16.0 for Pro1 (SD835) at: https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 It gives you ASB fixes backported to Android 9 up to patchlevel "5 August 2023". There are no other changes with respect to the June update above. I will continue to make new builds of LOS 16 as long as I use my Pro1 or until Markus stops backporting the ASBs, whatever comes first. However, as the Pro1/X community -- and by extension this forum -- seems to be dying, I'm not sure I will keep updating this thread much longer. If you are using my builds, check my website above for ROM updates. 1 1 Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.