All Activity

I'm not sure about the timing of when it last worked but think it was under some of the LOS 20 releases. As I remember it, it has been broken for all 22 and 21. I reported it long back, and it was fixed later, working for a not so long period only to break again, and I gave up a bit.... I guess it is a design issue. Some people love to mess up functioning designs (MS are masters in this mess-up-art....). Back in Android 9 it was check-boxes, and though very practical, it does not look good, and for the majority that only can handle one language, the selecting of the active by a simpl

Thanks for the feedback. With my Pro1 still on LineageOS 16.0, this works. I can select multiple layouts under "Keyboard & input methods > Physical keyboard" and then cycle through them on the fly. Pretty cool, actually. I didn't know about this feature. However, on the Pro1 with LOS16, the hotkey for layout switching is Ctrl + Spacebar. Yellow arrow + Spacebar is equivalent to pressing the power button in my case, which is another pretty cool feature introduced by @tdm with his initial port of LOS.

I just tested on my Pro1x with LOS. I think it works there. That is (just to confirm I know what is being talked about). I added Dansk (Denmark) to my list of system languages (the main one is US English). When I go to type in an editor, I am typing in English. and then I hold the yellow arrow and press spacebar and I get a notification that I am now typing in Dansk and I can get that weird ae mashup ;-). I can use the yellow arrow spacebar as a toggle between the two. Doesn't work on my Pro1. yellow arrow + spacebar pulls up search. Don't know why. My Pro1 is currently Google Free

OK. I just think: this sounds like a general regression in AOSP, as keyboard support in Android is generally nothing specific to the Pro1 (hence my question whether this is also observed in the Pro1-X port). I just wonder if it could be worthwhile to open a bug against LineageOS because of this.

@rotesatom Sorry, I'm just a voluntary moderator I do not know how their business logic is set up. But @Casey might shed some light here?

@EskeRahn & @cash, thank you both for your replies. I'm not sure about their Zendesk System. I never actively used a specific ticket system, so the question is: if i write an e-amil to the info mail address will there be an ticket opend automatically?

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

Yeah, I've used multiple chargers and cords, hasn't made a difference. Powered off or powered on it doesn't seem to be charging. It powers on when I plug it in, so can't see if it charges when powered down.

Yeah, that's not normal. Try a different charging cable or even a different charging brick (you are using wall charger and not USB port on computer, right?) If either is faulty, after the rubber band got it going, the cable or wall wart alone might not be enough to charge faster than discharge. Start with the cable. Try a different cable and leave it plugged in for a while.

Indeed, it was broken long ago, then fixed and later broken again, but you are right the chances of a fix seems slim.

Uh that definitely sounds like something is faulty.

Rubber band worked for me, but now my battery shows 1% - plugged in, can't charge right now. Occasionally it will go up to 35 to 65 percent, but if unplugged it drops to 1 almost immediately. Not sure if it's software or hardware related. It does turn off after a bit if I unplug it. Anyone else experiencing this?

I probably missed why you have been including this warning every week for quite some time. Is this problem unique to the Pro1 (as the corresponding qx1050 thread does not mention it)? Anyway, it seems I can find no open bug reported against LOS about this. So, whatever your issue is, I doubt it will ever be resolved "automatically" by an OTA.

(lineage-22.1-20250208-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.

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

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.