Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Name_not_avail last won the day on April 28 2023

Name_not_avail had the most liked content!

Community Reputation

64 Excellent

About Name_not_avail

  • Rank
    Pro 1x

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Me too, including root, which I attribute to the sideload trick.
  2. 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.
  3. 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.
  4. 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.
  5. 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!
  6. 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
  7. 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.
  8. Can anyone post a link to the 2.1.6 beta? Are there release notes to show what was changed?
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. 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