ducksoup

If only an alternate ROM could change the Pro1-X into an actually usable device, but you can only polish a turd so much.

Errrr, yeah. Completely glossed over the "on" in there. Sorry.

(Edit: I'm an idiot and apparently can't read. Ignore this! ) Why are you trying to install such an ancient version? The current version of Magisk is 26.1. Flashing the patched boot.img doesn't affect the Magisk app at all. You either need to adb sideload the apk from recovery, or install the apk as a normal app in LineageOS. It should then keep itself up to date if you don't disable update checks.

This is the key to Magisk surviving updates. When you flash Magisk in recovery mode, it installs its survival script. It can't do that if you just install it as an apk. And yes, you can install Magisk in recovery on top of an existing apk install to gain this functionality.

Anyone know if this be installed on top of the unofficial builds that have been on XDA?

I've installed the 20230120 image on my device, and so far everything is going nicely. No (new) problems to report. However, as anticipated, early indications are that this build does not improve the LTE situation, so I will continue to keep my device locked at 3G.

Before anyone gets too excited, do note that in all the screenshots, there are no cell signal strength indicators, so I would hazard a guess that hardware isn't working yet. Looks like wifi is working though.

What were you expecting?

I am running GMS-less 2.1.5 and I see all wifi networks in the quicksettings panel.

Plenty of people to have their devices, and plenty of photos of them have been posted, including in many of the threads you're spamming with your complaints.

After flashing stock, it'll show 8 GB until a factory reset is done through Settings -> System -> Reset options -> Delete all data (factory reset). Maybe they just failed to do this step, so you might want to try that first.

Since I'm sure I'll end up dropping my device if it's not in a case, I bought a ZRANTU Case Huawei P20 Mobile Phone Case with RFID Protection from Amazon to try out. I thought that with its phone holder portion being rubber, I might be able to get it to stretch in the right ways to hold the Pro1-X, but that was not to be. I ended up tearing the whole rubber portion out, retaining only the wraparound cover, and then stuck the Pro1-X in using some thin double-stick mirror mounting foam tape. So far it seems fairly good. It's a little tight when closed, but the magnetic clasp does hol

Same. I've been planning to poke around at that a bit, but haven't had the chance yet.

"Preferred" seems to be the key term there. Even when I set the device to "prefer" only bands not even available in my area, it still ends up on those that are. I don't think this menu is a means to actually blacklist bands, just to tell the device which ones to use if available. I got a SMS from a friend this morning telling me he was unable to call me last night. This despite everything seeming okay on the phone this morning. He was trying to call me after midnight, though, so missing the call isn't all bad. 😉

My situation is much improved after forcing VoLTE on, but not entirely fixed. I've had no more known incidents of the "the service has not been implemented" error, and I no longer lose connectivity when I receive incoming calls, but I did see once today where cell connection vanished on my primary SIM, and when it returned, data connection did not return. I was in a bit of a hurry at the time, so didn't take the time to attempt to cajole it into working again, and simply rebooted to fix. So, there is clearly still some work to be done on the connectivity issues, even after the currently

Yes those commands require root. I've modified my post to note that. The LTE connection stayed up all night long. However, when I just called the phone, I got a "the service has not been implemented" recording, which I've never heard before. Second attempt at a call worked fine. So something is still not quite right.

I got a tip on the Telegram beta channel to force the toggles to show in SIM setup via the following commands (requiring root): setprop persist.dbg.volte_avail_ovr 1 setprop persist.dbg.wfc_avail_ovr 1 After entering those commands, and then enabling VoLTE on my primary SIM, it does appear to have registered properly to use VoLTE, and when I called into the phone, it did ring, did not change to "3G" on the network indicator, and did not lose connectivity. I'll let the phone sit overnight and we'll see in the morning if the problem is solved.

Certainly agree VoLTE should be turned on. Curiously, I don't even get a toggle for that in the SIM settings for my primary SIM. I do see that toggle for my secondary SIM (which is a different provider), no matter which SIM slot that secondary SIM is installed in. I don't know whether the absence of the toggle means "always on, you have no choice", "VoLTE not available from this provider", or something entirely different.

I don't think the problem is that simple, as I'll lose connectivity whether or not calls are placed or received. When the phone is first booted up, or the SIM is otherwise reset, everything is generally fine for a while, and then I lose connectivity and the ability to make or receive calls, without moving the phone at all. I was earlier thinking that this issue was only related to phone calls, but now that I've disabled wifi, I see that I'm actually losing all mobile connectivity.

Sadly the current beta seems no better. Even though the phone shows connected (actually even "LTE" now), with good signal strength, incoming calls are not arriving. This device is essentially unusable as a phone at present. Calls are clearly almost getting there, because when I dial in from another phone, "LTE" switches to "3G" on the Pro1-X, but nothing else happens, and the calling phone eventually gets "number not available".

Due to discovering that my old daily driver is actually physically falling apart, I've been trying to use the Pro1-X as my primary device for about a week, which means using Android for the moment, and I have found the same problems reported by many others in this thread: Sometimes it's fine, but much of the time, outgoing calls take 30 seconds to connect or do not connect at all, and most incoming calls receive a "number not reachable" error message. I've been playing around with the network settings a bit, and it seems that forcing certain modes will improve the success:failure ratio s

I just added the microG repository to F-Droid with no problem at all. Seemed to work identically to native Android.

I tried out Adam's latest kernel tonight, and I'm glad to report that although I still can't get the more recent UT kernels to boot, Adam's does boot, and also I've got Waydroid up and running just fine. Whether or not it's in a usable state is a different question of course. 🙂

My backup persist does have keys in it. My persist flashed onto the device (for now) does have keys in it. restorecon relabeled everything. After a reboot, I still don't have attestation. restoredon did fix the sensors though. I've never touched the backup persist. Even my read-only explorations of the image have been performed on a copy.

Okay, I've now tried this, with no luck. I QFIL flashed the whole device to stock Android, then used the edl Python script to write out my persist backup, and I've got the same place as I get with fastboot, i.e. broken sensors and no attestation. Bit of a mystery. Would be good to get more data from others, in case I've somehow just broken the keys in my persist backup and don't know it.