Hook

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 P

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.

Lineage-22.2-20250512-NIGHTLY-pro1x with May 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

I only did a factory reset when I started over so I could install MTG and root. I do perform a simulated battery pull after the first reboot into a new OTA update. It's probably superstition and likely doesn't do anything, but it's easy so I do it.

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.

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.

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 wa

Definitely do not have the battery drain with Google-less Pro 1 on Lineage 22.2. I will make the MTG test tonight.

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 a

Lineage-22.2-20250505-NIGHTLY-pro1x with April 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250428-NIGHTLY-pro1x with April 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained. I think the April 1st dates in previous posts was a typo I kept perpetuating. Lol. So far well behaved, battery-wise. Lost 3% in 2 hours including activity post-update. Edit: Looks good. 7 hours, yes, mostly idle, but has only dropped 10%. That's par for the course given that I have background mail, dropbox ans calander syncing.

So, I discovered my Pro1 is still on 22.1. So I will get a baseline as-is, and then I'll update. It's also Google-less for now, so I'll see what happens.

I am actually seeing much better battery performance after the simulated battery pull. My Pro1x only dropped from my max of 85% to 77% in 7 hours, and my Pixel only dropped to 80% with quite a bit of use. I'll keep monitoring just to make sure I'm not jumping to conclusions, But I have to admit simulated battery pull is my go-to for weird stuff happening. However, now I need to try it with my Pro 1, which I haven't used much for a couple of weeks.

I think I am also seeing it on my Pro1x. I'm testing this week-end. But I also have been getting unusual battery drain on my Pixel 7 Pro. Coincidence? Or is the problem an Android 15 update problem and not a purely Lineage problem. I did a simulated battery pull on both devices (to clear out janky stuff going on and will watch both.

I don't know if I have a suggestion, but I suspect more information is needed. Is this a Pro1x that was formerly working ok and this just suddenly happened? Or did it do this when you got it. If the former, what kinds of things were you doing with the phone? Is it Stock Android or did you flash some other ROM? Anything you can tell people will help them decide if they know something you can try.

I don't really understand what mirrorbits is or what it's advantages are (even after reading their Github, lol), but Saturday's Pro1 update downloads just fine from the official Lineage download sites. Just FYI for folks.

Lineage-22.2-20250421-NIGHTLY-pro1x with April 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

The same thing happened to my Pro1 about a month before the end of its 2 year warranty. Replacing the screen didn't fix it, so it isn't the screen or at least not entirely. Luckily this was 2021 and FxTec accepted it for warranty repair. I had to wait 6 months until they got their Pro1 parts shipments. Unfortunately, I didn't ask what the exact problem was and what they did to fix it. I was just happy to get my phone back 6 months later. It has never reoccurred.

Interesting, I *think* but do not know that it means does not work correctly. The trouble is, to test it, I would need to replace the screen, and I'd rather not. Lol. But you raise a good possibility. If I ever have a screen fail on my Pro1x, I will test.

Lineage-22.2-20250414-NIGHTLY-pro1x with April 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained. Notes: I encountered no problems after the OTA going from 22.1 to 22.2. I use Magisk, but only as SU, I don't use any Magisk modules. Also, since I update OTA, I don't flash newer packages of MindTheGapps. My contention is, that since Google updates both the Gapps and Play services, there is no need to flash the newer MTG packages unless you are moving to a new full version of Lineage (new version of Android) that can't be installed OTA. I don't k

Lineage-22.1-20250407-NIGHTLY-pro1x with March 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.1-20250331-NIGHTLY-pro1x with March 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

The main problem for the Pro1x is that the app doesn't work on any version of Android after Android 10 (Lineage 17) and the Pro1x doesn't have any options older than Android 11.

Lineage-22.1-20250324-NIGHTLY-pro1x with March 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

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 t