All Activity

I suspect, you don't need to go the Magisk App OTA path for every update once you have Magisk in both slots, but I still always to it.

Lineage-22.1-20250203-NIGHTLY-pro1x with January 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Another unofficial build of LineageOS 16.0 (for qx1000) is here, celebrating 3 years of support beyond its AOSP EOL. 🥳 At https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 Go for the ROM dated 20250203. Changes since last release: Backported fixes up to the "1 January 2025" Android Security Bulletin. Updated system WebView and browser engine to Chromium 132.0.6834.122. Have fun.

Hello, ...i mean that bl unlock on priv will be possible if you rewrite boot part on emmc with unlocked boot part - maybe from preproduction/testing device + will be needed to add device info. But this is not good question for me. Have you tried to contack Balika001 directly? I have in my collection one priv too so i can test it...but problem is time 😞 Another problem is, that priv have problematic SOC and only 2GB ram...so it is not device for newer Android device. Maybe will be good for android GO. Without sw solution will it be really hard and not simp

Lineage-22.1-20250201-nightly-pro1-signed.zip on January 5 (2025) security patch, installed smoothly using OTA

Rubbished may be overstating it, I don't recall exactly. And it sounds like you and I installed Magisk differently. I installed the apk normally on the phone like any other app, then downloaded the boot image corresponding to the current version of LOS, then had the Magisk app patch that boot image, then used a PC with adb to fastboot flash the patched image back to the pro1x. If anyone else here did Magisk that way, then to preserve root with OTA updates of LOS, I recommend doing the "interrupted OTA and install to inactive slot" trick that I mentioned above. It saves a bunch of hassle.

@CornholioGSMCan the bootloader be unlocked for the Blackberry Priv now too? I flipped through the Discord pages on these Blackberry projects, and although there was a guy claiming he had unlocked the Priv bootloader 6 months ago and promised a "How To" manual, nothing seemed to have followed. First he claimed it required a new EMMC soldered in with a patched rom, then he claimed a subsequent software-only exploit. No patch files visible to me anywhere on the Discord, though. I'd love to get my Priv going again with LOS.

(lineage-22.1-20250201-nightly-pro1-signed.zip on January 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20240928_150548) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.

Looks as if they pulled it off--the first proof I've seen of the phone truly functioning. Love the text rendering, a Kindle party, but not sure about e-ink browsing, etc. Well, they said it was going to be minimal...

I doubt I "rubbished" you as that is generally not my style. All I see in that thread is us kind of agreeing on what works. Lol. Basically, what works for me (and I can only vouch for me) is that I side load Magisk as a zip when I first install a full version of LOS, then open the app and let it do the automatic install which takes care of the whole patching the boot sector. After that, OTA always maintains root. But as long as you have found a method that works for you, that's great.

I just did the January 27 OTA on my first pro1x, and root was NOT maintained. This is the first time I tried an OTA after the manual installation of this version of LOS. I had followed the normal Magisk install instructions in the app, instead of initially sideloading the patched boot file or whatever deprecated method it was that I had done to initially root the last version of LOS. Now I forget exactly what secret sauce it was, but it was the only thing preserving root with OTA for me in the last version of LOS. I remember Hook rubbished me for it as being unnecessary when I posted abou

Lineage-22.1-20250127-NIGHTLY-pro1x with January 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

It seems that the connection is only working, when the phone is connected via bluetooth first.

(lineage-22.1-20250125-nightly-pro1-signed.zip on January 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20240928_150548) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.

verizon will only work with LTE. VoLTE should be toggled on. CDMA is no longer used by verizon and GSM isn't used by them

Lineage-22.1-20250125-nightly-pro1-signed.zip on January 5 (2025) security patch, installed smoothly using OTA

Have you tried to enter Verizon in the search field here? There are whole threads discussing the issues with getting it to work e.g. https://community.fxtec.com/topic/2133-fxtec-on-verizon

Thanks! so i have a question regarding making calls which setting is the best on making calls using verizon? Ie like LTE, CDMA, GSM?

Superrr. Thank You 🙂

The respective fix for the Pro1 is here: https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/318274 Note that this is specific to the qx1000.c keyboard driver in android_kernel_fxtec_msm8998, it won't be directly applicable to another device.

So hello 🙂 I have today HW/SW modified Blackberry Passport. Maybe it will be my second device...or device just for fun 🙂 It works relatively good...yess it is old and yess it have only 3gb ram....but good device. It runs LOS 18.1 (A11). I have one question. Passport have on lineage same problem as was on FX (first custom roms) - multipressing keys. Can anyone help me fix it? Will be needed to add something like key press deelay.

Just the opposite. It was able to boot properly at 1%. When I said it went off, I meant the screen turned off, but I could turn the screen right back on, And it did charge pretty rapidly. Slowed down once it hit 90% but took not much time getting to 90. And not hot.

As for the first mystery, I guess it wasn't low enough to boot properly, but as for the time it took to charge, I know that Lithium batteries can't be fast charged safely below 10-20%. It will actually charge very slowly when it's very low like this.

Okay, this is just weird. I have a second Pro1x that I have kept on Stock so that I can try and answer questions about stock. I have tried to make sure I charged it every so often, but, sure enough, during another very hectic time, I failed to do so and it would not turn on this morning. So, I plugged it in (using my usb cable from my Pixel plugged into an Anker fast charging wall plug, if it matters, not the FxTec brick). It booted up, showed 1% battery (first mystery... how was it able to fully boot at 1%) and said "charging rapidly," Then the screen went off. I figured, that w

Now this is weird, after trying to do the updates since Saturday, today (Wednesday) all updates went in smoothly, so must have been some glitch on a server or network somewhere.