Jump to content

Name_not_avail

Members
 View Profile  See their activity

  • Content Count

    70

  • Joined

  • Last visited

  • Days Won

    6

 Content Type 

Everything posted by Name_not_avail

  1. Name_not_avail
    According to the principle of, "Never ask someone to do something that you wouldn't do yourself", by which I lead my life, I just updated my second 1x, the one without any Gapps. It worked flawlessly. Don't know what to tell you Hook, but this is definitely not a universal problem for the 1x.
  2. Name_not_avail
    OTA, because I am too lazy for sideload unless absolutely necessary. Start the OTA, let it grind on ad nauseam, wait for the message to reboot, stop there and open Magisk app, select install to vacant slot, Magisk runs its little script, then swap back to the OTA and touch reboot. Done it a couple of dozen times like that, it always works. I recall that you and I installed Magisk in different ways, and had words here about it. I can't recall exactly what the difference was now, but you could parse our old comments here to check it. I think you claimed you didn't need to do this
  3. Name_not_avail
    Interesting. I just did this update on one of my Pro 1x phones, and it worked fine. I did it the usual way that I do to avoid losing root, ie. wait for the update process to require reboot, then open Magisk, select install to vacant slot, then reboot. All working tickety boo now, version 23.2-20260209-NIGHTLY-pro1x Of course LTE reception remains unusably bad, but that kinda goes without saying now. I guess I should wait for the next update for my other 1x.
  4. Name_not_avail
    I just dealt with this issue on a new Windows 11 PC, mentioned in the LOS 23 thread. Same symptoms as the OP here, trying to use fastboot. If you look at the devices attached to the PC once the phone is connected to it in fastboot mode, I expect you would see a driver error on the PC. The solution for me was to install a dedicated Andriod phone fastboot interface driver in the PC operating system. I can't advise how to do that with Linux, but I'm sure the OP can figure it out.
  5. Name_not_avail
    I went ahead and did this, too. No issues as yet. The one hiccup was that I had recently "upgraded" the OS on my PC to Windows 11, and it didn't have a fastboot driver for an Android device, to use with installing the Magisk img file. The phone shows as an unknown device on the PC when the phone was rebooted into fastboot mode, and when trying to update the driver manually, the default driver list does not show Android Phone. The default driver list did show "Samsung Android Bootloader Interface" though, and I installed driver version 2.21.0.0 of that. It worked just fine f
  6. Name_not_avail
    Are you still on stock Android, or have you updated to LineageOS? I recall the problem with Chrome refreshing the page from the fingerprint sensor was present in the stock Android, but fixed in LOS. IIRC, the work around was to switch to Firefox, if you don't switch to LOS. Some of your other issues might work better with LOS, too. No real downside to it, except for the time it takes to set it up.
  7. 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.
  8. Name_not_avail
    @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.
  9. Name_not_avail
    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
  10. Name_not_avail
    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
  11. Name_not_avail
    Link?
  12. Name_not_avail
    Me too, including root, which I attribute to the sideload trick.
  13. Name_not_avail
    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.
  14. Name_not_avail
    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.
  15. Name_not_avail
    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.
  16. Name_not_avail
    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!
  17. Name_not_avail
    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
  18. Name_not_avail
    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.
  19. Name_not_avail
    Can anyone post a link to the 2.1.6 beta? Are there release notes to show what was changed?
  20. Name_not_avail
    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.
  21. Name_not_avail
    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.
  22. Name_not_avail
    This problem existed on the initial stock Android ROM, 2.1.2, but was fixed in the 2.1.5 gms-less Android ROM that was subsequently released. For some reason, LOS devs must have been given the initial vendor blobs where the problem still existed.
  23. Name_not_avail
    This analysis makes good sense. I was surprised that the gps.conf file would be read at any time other than boot. I now think I let "coincidence imply causation", and the GPS was actually using the gps.conf file as last edited for the prior boot.
  24. Name_not_avail
    If I can get the previously useless GPS going this way, it makes me wonder whether there is a similar configuration file for the LTE modem, that I could force the 1x to use a SNR that would normally be below its threshhold. A sort of "perfection is the enemy of the good" configuration, that would stabilize voice calling.
  25. Name_not_avail
    Here is the full text of the gps.conf file that unlocked the ability of my 1x to get a GPS fix. Thank you, @claude0001 [quote] XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin XTRA_VERSION_CHECK=1 # Error Estimate # _SET = 1 # _CLEAR = 0 ERR_ESTIMATE=0 #NTP server NTP_SERVER=north-america.pool.ntp.org #XTRA CA path XTRA_CA_PATH=/usr/lib/ssl-1.1/certs # DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info # 4 - Debug,
×
×
  • Create New...

Important Information

Terms

  I accept