Hello --
Anyone aware of MOD and/or app that would allow user to tweak Bluetooth connectivity settings for ONE_S/Ville?
my ONE_S disassociates with car Bluetooth every 30 seconds, then reconnects, all day long. My previous FOUR Android HTC phones never experienced this problem. It's annoying as all hell
the problem drove me root my ONE_S with sole purpose of trying new TMOUS RADIO. This did not solve the problem.
currently, ONE_S running LeeDroid v2.1 with latest TMOUS radio.
same Bluetooth problem with car audio before and after root. Plantronics Voyager Pro headset at home works fine.
any suggestions would be appreciated.
Note: I have contacted dealer service to see if software update available for auto stero.
Check out a2dp volume in the market. It might help...
To the OP, there are other threads on this. Unpair your device from the Car, on the H1S go to advanced Bluetooth settings and turn off MAP, now repair and reconnect to the car ... fixed?
v looked in the advanced settings and can't see the MAP option. What is it exactly?
vibez said:
Check out a2dp volume in the market. It might help...
Click to expand...
Click to collapse
Second on A2DP volume... fixed my Bluetooth issues with the One S.
Hi all!
I wanted to open up a discussion about the new Oreo features for Bluetooth codecs in the developer section. I haven't been able to find a comprehensive guide or info anywhere that covers how it actually should work, and I don't believe it's working correctly - I would like to explore more with you.
I'm on a Google (carrier free) Pixel, using a fresh install of OPR6.170623.012 - which is working brilliantly by the way.
It seems to me that I can't make the settings stick, if I for example change the Bluetooth Audio Codec to aptX, or modify any of the other settings when I go back in it always reverts to the 'Use System Selection (Default)' option. I'm typically trying this with Bluetooth off, changing the setting and turning Bluetooth on. I've also tried rebooting in-between, as well as different variations. The developer toggle is set to on of course.
It may be my misunderstanding of how this works, but it even if I stay on the developers screen and change the codec, if I turn Bluetooth on and it connects to a device, for instance my in-car Bluetooth audio, which I believe supports aptX, it doesn't care what the codec setting is and displays 'Streaming: SBC', which is of course what I'd expect would be overridden.
The only thing that seems to stick is the AVRCP version. I'm wondering if the Bluetooth HCI snoop log will provide any information?
Have any of you had any experience with this, or have anything to add to the conversation?
Many thanks in advance,
OK so it seems this codec list doesn't allow you to set a 'default', it just allows for modifying the codec during playback?
What I've experienced so far is that it does work with 'Use System Selection' to use the best codec available on the device you are connected to. It also allows you to change the codec to another while streaming/playing. The sub-text under Bluetooth Audio Codec does dynamically change from SBC to AAC.
Example: My headphones support SBC and AAC, the Pixel defaults to AAC on establishing a Bluetooth connection but does allow downgrading to SBC by picking from the list (as a test).
It however doesn't retain whatever you pick in the list if bluetooth is turned off then back on, it basically always defaults to system selection, then auto-picks on every connection. Perhaps this is by design, it is developer tools after all.
I haven't been able to get this to work with aptX in my car yet with my Pixel, even though it is apparently supported?
Also of note: To achieve AAC on my Bluetooth headphones I had to put them into a 'Priority on sound quality' mode and also turn off the Bluetooth phone (i.e. call connectivity, music ONLY) on the Pixel connection to achieve AAC.
are you sure that your car supports aptx? before this developer option it was very hard to actually see the codec being used.
I believe so, the Bluetooth product states that it supports EDR and aptX, but yes, I cannot be 100% certain.
Are you suggesting it should be possible with Pixel and the Oreo build as-is?
I am on the GA release of 9.0. It was a total clean flash.
Bluetooth audio works great I can even get phone calls to come in and go out. the problem I'm having is it seems that the person cannot hear me on any Bluetooth headset.
It seems like the microphone piece is not working. I have tried completely forgetting devices and repairing I have also ensured that all of the profiles are enabled.
Any ideas?
Edit: fixed it by resetting the Bluetooth settings in Developer Settings to system default
Just had update PPR2.181005.003.WW_Phone-16.1220.1906.174-0 a few days ago. Didn't notice any significant changes but my bluetooth headphones voume/media controls stopped working. Anyone else experience sth similar or have a fix? TIA
It looks to be solved if I switch to AVRCP 1.6
Settings -> Developer Options -> Bluetooth AVRCP Version.
Does anyone have a hotfix for the bluetooth handsfree calling issue found in all of the custom roms of android x. Its been pointed out that changing bluetooth avrc from default to 1.6 would solve it, but after every reboot, it returns to its default value.