Leaderboard
Popular Content
Showing content with the highest reputation since 05/05/2025 in all areas
-
one more note regarding protecting my battered Pro 1x: I ordered one of these cases, took out the wallet insert quite easily, increased the cut out at the bottom for the charging access, and figured out that if I open my Pro 1x, I can insert the bottom, keyboard portion into the case quite snugly, and then i can slide the phone close and open securely. I just have to memorize the locations of the up, down and power buttons as they don't correspond exactly, but not difficult. Now I don't feel like i'm risking another disaster. Hope this can be of help to others.4 points
-
Update after one year of usage: Current version (video): I still love it. I had to replace the keyboard one time as the touchpad stopped working (probably my fault since I sealed the touchpad chip on the board with super glue so it could have overheated. Part cost: 25β¬ The hinge system is still in place since the first day. At one point, I replaced the phone cover (which is fixed on the hinges with super glue). Part cost: 10β¬ These changes gave me the opportunity to do a better job with the backside of the phone so it looks more professional and to probably make it l4 points
-
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 have3 points
-
I've uploaded an updated build of LineageOS 16.0 for good-old qx1000 (SD835 Pro1) to: https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 The ROM dated '20250528' contains backported ASB fixes up to patchlevel "1 May 2025". No other changes since last post. Have fun.3 points
-
Lineage-22.2-20250519-NIGHTLY-pro1x with May 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
(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: Got it charged to 100% and after 3h it is down to 96% and that is OK. So now I will try to reenable the stuff I disabled, and recharge. But still No sim, no WiFi, no apps UPDATE: After 75m it is down to 99% and that is OK. So now I tried to add sim and WiFi, no account, no apps, and recharged. UPDATE: After 4h it is down from 100 to 82% and that is not good, 4Β½ %/h... I will now remove WiF3 points
-
Lineage-22.2-20250512-NIGHTLY-pro1x with May 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
...and i am on battery from approx 8am morning...now i have 56%. LineageOS 22.2 UNOFFICIAL3 points
-
Lineage-22.2-20250505-NIGHTLY-pro1x with April 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
An updated build of LineageOS 16.0 for OG Pro1 (qx1000) is available for download at: https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 The build dated '20250504' gives you backported security fixes from the Android Security Bulletin up to the "1 April 2025" patchlevel, and updates the bundled WebView to Chromium 135.0.7049.100. Otherwise no changes with respect to last month's upload. Have fun.3 points
-
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.2 points
-
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Β½ hours2 points
-
Lineage-22.2-20250526-NIGHTLY-pro1x with May 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.2 points
-
7-8% in 7 hours with flightmode on and mounted SIM.2 points
-
(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...2 points
-
Well, and this will probably be my last comment on this unless something changes-- I updated both my Pro1 x and Pro1 (in that order) today to the latest OTA updates. On both I downloaded the updates and performed the install and reboot. I also looked around on both to find some settings (the same on both). Otherwise, I just let them sit. Both started out at 85% battery (the max I allow them to charge). 7 Hours later, the pro1x was 73% and the Pro 1 was 75%. I'm going to declare pretty confidently that I don't have the battery drain problem.2 points
-
Lineage-22.2-20250517-nightly-pro1-signed.zip on May 5 (2025) security patch, installed smoothly using OTA. I have still the issue with the battery drain: 10-15% per hour.2 points
-
(lineage-22.2-20250517-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, from 100% to 24% in roughly 11 hours idle over night2 points
-
On 22.2 (without factory reset) it went from 100 to 72% in 8h idle over night, so 28% compared to 6% for 8h on 22.1! ..Just did a factory reset, no net, no sim, no account, and disabled all I can (leaving it totally useless - see attached), and will recharge and see how things goes...2 points
-
Just as a data point, my Pro1 with official LOS 22.2 is having no battery problems still. About to do the May 10th OTA. I will finally be getting everything set up again this afternoon, and will report if anything changes with my, so far, good battery life. This is very puzzling.2 points
-
Lineage-22.2-20250510-nightly-pro1-signed.zip on April 5 (2025) security patch, installed smoothly using OTA.2 points
-
I agree with Eske. Yes, my (second) battery was not the best. Charging every day 2 times, but after upgrade (dirty flash) from 22.1 to 22.2 it is noticeably worse. I try simple things first, before I will reset the system. I have many backups of my apps incl. whole settings, but ... please no reset π2 points
-
Hmm, not in my case. It worked fine on 22.1, and now works fine back on latest stock android. Though I will not rule out if Lineage got the calibration wrong, and thought it was at 100% when it was not, and thus did not use the full span - I highly doubt it though. Much more likely that 'something' in the system got confused on the dirty flashing from 22.1 to 22.2 (or maybe rudiments from earlier dirty flashing, that kicked in going to 22.2) I really ought to have made a factory reset while on 22.2, to test before going to stock, but well I did not.... But anyone else seeing the bug, I2 points
-
Well, I don't have any fancy battery app analysis readouts, but here's what I did and the results. The takeaway is I am not seeing the battery drain on my Pro 1, I went hooked my Pro1 up for adb (to my Manjaro ThinkPad). I rebooted the Pro1 into recovery and did a factory reset. I then sideloaded the May 3rd LOS 22.2 zip, rebooted into recovery and flashed Magisk28 and the Feb 2025 MTG, I did a system reboot. Finally I did a simulated battery pull, I set up a few apps and settings, including setting max charge to 85%. I made sure I had SU, At that point, the battery was at 77% (it wa2 points
-
Definitely do not have the battery drain with Google-less Pro 1 on Lineage 22.2. I will make the MTG test tonight.2 points
-
Well, thatΒ΄s my first ticket π LetΒ΄s see, what happen https://gitlab.com/LineageOS/issues/android/-/issues/87672 points
-
I just followed the guide at page 1, and took the liberty to adjust a few more details The line on userdata missed a destination Commented that you might want to skip flashing persist.img if from Android/LineageOS Added that you MUST do an extra factory reset from the settings, to use the full amount of memory. Hope that's OK @Waxberryπ2 points
-
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.....1 point
-
Well, Yesterday 11pm, I reset my phone. Now, IΒ΄m back on LOS 22.1.π1 point
-
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.1 point
-
1 point
-
Lineage-22.2-20250531-nightly-pro1-signed.zip on May 5 (2025) security patch, installed smoothly using OTA. I have still the issue with the battery drain: 10-15% per hour.1 point
-
So I took my pro1 and pro x and switched Sim cards.. This confirmed that, in fact, my Pro 1 is unable to do calls anymore. There was no problem with either sim card in my Pro1x. So, it may be that my good battery performance on the Pro1 is due to the fact that it can't use a SIM. I sort of don't care enough to do anything about it as I do not ever use my Pro1 as a phone. (I rarely use my Pro1x as a phone and it works). This also suggests that, to the degree that it is a LOS 22 problem, it does NOT seem to be a problem with the Pro1x version of LOS 22. Round and round we go... π1 point
-
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.1 point
-
@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 mode1 point
-
Tomorrow I will test it for 12 hours and 85% battery, with just Wifi and BT. No GPS, no active SIM / network.1 point
-
..Nice @hling, we got a very long thread mainly with DIY cases over here:1 point
-
Well. I'm completely baffled by the phone on my Pro1 not working. My Pro1x works fine, so I don't think it;s a LOS problem. Since I almost never use my Pro 1 as a phone (so I don't actually know when this problem occured), I'm not highly motivated to trouble shoot it. Lol. If anything occurs to me I'll let you know. I will have to get around to trying out a new SIM card. Both my Pro1 and Pro1x are on T-Mobile, although the SIM in the pro1x is Ting. Bands for US T-mobile are 4 (1700/2100 MHz), 5 (850 MHz), 66 (extension of Band 4), 12 (750 MHz) and 71 (600 MHz). I don't think the P1 point
-
I have a sim in. Have something I'm in the middle of, but will get the bands for you later this morning. It is T-Mobile US. But here is the curious thing... I don't use my Pro1 or Pro1x for calls, but they have sims and have always been capable if I needed to. I've suddenly discovered my Pro1 can't make calls, (my Pro1x does just fine still). I will investigate this further later.1 point
-
I'm happy I got mine but seems like when it's EOL I'll have to procure something else. AGH.... As usual... Too unfair.1 point
-
I have upgraded it (without factory reset) to 22.2 20250503, and will recharge and see what happens. If horrible, I will try with yet another factory reset (and no MTG, no and no apps whatsoever, all left default, and skip/disable to all questions)....1 point
-
At 22.1 20250405 with same setup after two hours it has gone from 100% to.... 99% So I still claim that 22.2 is borked... Sorry. ...After 5h: 97%, 8h: 94%1 point
-
I HOPE that I sometimes in the following week will have verified that all from the original Pro1 that can be transferred has been, so I can install LineageOS 22.2 on it freshly reset, and I will be sure to install the same 0503 version reported on above, to rule out that anything that had issues has been fixed. (But no promise I will find time for it)1 point
-
USUALLY the problems people experiences with fastboot is related to the communication with the watch. Either cable, port or driver. Silly as it may sound on Windows11, a 'newer' USB3 port might cause problems. On my Lenovo X1 Yoga gen 6 (20XY), I can not get fastboot to work directly. But if I use an old usb2 hub, things works fine. It also works fine if I go via my thunderbolt 4 docking, and a USB3 port on that. AFAIK, there are fewer issues if the machine is on LINUX. You might also try from an old PC with USB2 ports only. Usually it is not super picky on the cable, but try sw1 point
-
One thing just occurred to me. I received a free battery replacement in 2022. I had sent in my Pro1 to London for a warranty screen repair at the end of 2021 a month before my warranty ended. They accepted the repair as under warranty, but I had to wait 6 months until they had screens again for the Pro1x. So when they replaced the screen 6 months later, they replaced my battery as a "thank you" for my patience. Could it simply be that your batteries are just degrading? Maybe not, but I guess it makes it hard to use my test results.1 point
-
Thanks a lot for your test and feedback, Hook! My next three steps: - install new MTG (yes, I read your post π ) - wait for the next 5-8 LOS updates with hope, the "issue" is solved - compelte reset / roll-back (without TWRP, I hate these step) (- Pro-2 will be released π)1 point
-
....For comparison here an old one from stock: Note that it is at 82% after 10h, and even among that MUCH lesser usage, a lesser portion is apps.1 point
-
It's too early to say.but almost an hour later, I am not seeing excessive battery drain on my Pro1 after updating from 22.1 to 22.2. I did a simulated battery pull right after updating. If this continues, I will have to further experiment because this is a Google-less installation. Cornholio's comment got me thinking-- what if the problem is actually MTG? That is the primary difference between Official and Oddsolution. It would be odd if that were true because I am not seeing the battery drain at all on my Pro1x, but it was a much older version of MTG that I first installed on that a1 point
-
Well I'm now off the LineageOS wagon for a while, at the least until I get all transferred, a lot is omitted by google on transfer. Several important apps .... π Note that I did NOT do a factory reset going from 22.1 to 22.2, so that MIGHT be the issue, and obviously would be the first to try for a support ticket.....1 point
-
The lineage page is correct. CPU-Z misreports it. I've had Lineage on for a very long time and it works fine. Lineage is currently on Android 15 (Lineage 22) which you will probably not be thrilled by if you don't like Android 11. Android 11 is the earliest Android the Pro1x can take. But yes, you can reinstall stock Android 11 if you don't like Lineage, but you will get no security updates. Make sure you thoroughly investigate the Pro1x's call and text performance on Stock. Lineage will not affect that, either ofr better or worse, so make sure you know what the problems are ahead of t1 point