Name_not_avail

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.

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

I agree that it must be a software bug, and it happens more readily as the battery is aging. Might be connected to LineageOS breaking the original charging software (you recall when offline charging got broken with respect to the stock Android rom, and the LOS devs eventually gave up trying to fix it). The LED often glows red when I leave the 1X on charging for longer than it takes to hit 100%. One time I left it charge overnight and it completely discharged the battery, presumably after reaching 100% and then bugging at that point. I had to use the rubber band trick to get going aga

Link?

Me too, including root, which I attribute to the sideload trick.

For LOS 20, I initially installed Magisk the recommended way, but I would lose root with every OTA while watching you post "I upgraded and kept root and GApps." That was annoying! After I did the sideload trick, I no longer lost root with the OTAs. I didn't uninstall Magisk, just sideloaded it over the existing installation. So I hope that works on v.21 for me now too.

I just updated to LOS 21, thank you for the instructions on the LOS wiki page. Boot time is the same or better than version 20, about 25 seconds from cold, so the 3 minute comment is not my experience. i flashed Magisk by downloading the v.27 .apk and changing the extension to .zip, and then sideloading that with adb. That is the deprecated install method, but I believe @Hook said that is what preserves root after OTA updates, so I did that, no problems, we shall see if root is preserved on the next OTA.

Pretty strange outcome when the stock Android ROM did not suffer from this problem. The problem only arose after installing LOS. That would strongly suggest that it was a LOS issue introduced at that point.

And my final comment on documenting this issue. It is completely solved in the current version of LineageOS, 20-20230803-NIGHTLY. Issues discussed above were in respect of a much earlier unofficial version of LOS, and version 2.1.5 GMS-less Android from Fx Tec. The current official LOS permits three codecs with these headphones, SBC, AAC and Qualcomm aptX, and they all work just fine, no sudden "suspend" disconnects. So thank you very much LOS devs, and mystery solved!

Playing with this a bit more, I see when I switch to HD Audio, two codecs are permitted with this combination of HyperX headphones and Pro 1x. They are SBC and Qualcomm aptX. By default, enabling HD Audio triggers the Qualcomm aptX codec, and that kills the headphone sound and starts the "suspend" problem. But it is possible to select the SBC codec instead of Qualcomm aptX when HD Audio is enabled, and that reconnects the sound. Interesting. Some kind of failure related specifically to the Qualcomm aptX codec. Anyone else have a Bluetooth device working properly, using that

Solved! I tried the solution proposed by @Tim6263 to disable HD audio within the Developer Options menu, and now these headphones connect normally. I expect if @Tim6263 had tried a Bluetooth snoop log when he was having trouble, before disabling HD audio, he probably would have seen the same "suspend" commands as I did.

Can anyone post a link to the 2.1.6 beta? Are there release notes to show what was changed?

Notorious problem in stock 2.1.2, then fixed in GMS-less 2.1.5, and for some reason LOS developers are not using that updated vendor blob for the current versions of LOS. Does anyone have a way to communicate this issue to the LOS devs? Seems like it should be a relatively easy fix, to just use the 2.1.5 stuff for LOS.

It's the phone. Or maybe it's the firmware drivers, but it makes no difference, it won't get fixed at this point. You have a wifi tablet with a mechanical keyboard, not a phone. We have all been soaked, and LOS can't fix it.