Database Info

Bluetooth Device Problem

I have noticed a couple of times not that i will sync a BT device but a little later its removed from the list. Any thoughts? Thanks

Update. I have realized that this happens everytime i do a softreset using rebootnow app. Has anyone else had this problem? Thanks

Also this happens when i turn my phone off... no one else has this problem ???

sorry to keep pushing this thread but its the most annoying bug i've ever had. I tested almost everthing except a hard reset but whenever i do a softreset my bt devices that i have paired with get erased.... any guesses

I'm having similar problems - if I turn the phone off & back on again, it won't connect to my car. The bluetooth menu still shows that it's paired, but it won't connect (even if I try to manually connect). The only way to get it to connect again is to turn bluetooth off & back on - then it connects automatically.
I've only seen it delete paired devices from the list once - that was when I rooted the phone. It hasn't deleted them since.

kc9qix said:
I'm having similar problems - if I turn the phone off & back on again, it won't connect to my car. The bluetooth menu still shows that it's paired, but it won't connect (even if I try to manually connect). The only way to get it to connect again is to turn bluetooth off & back on - then it connects automatically.
I've only seen it delete paired devices from the list once - that was when I rooted the phone. It hasn't deleted them since.
Click to expand...
Click to collapse
well my phone is rooted so i'm hoping thats not the problem. Also I just made a lengthy video to show the problem and i will post it in a little bit on here so others can see the problem.

so for some reason i can't get the video of my friends iphone 4 but i was looking through the settings.db file and i found some interesting stuff about the bluetooth devices so i was wondering if anyone could look at this and tell me if there is something wrong also can a couple of people post their settings.db file on here so i can compare. thanks

I Get This Too!
For me it seems to only "remember" the devices that have phone capability turned on.
For instance, it never loses my Jawbone headset but it always loses my Kensington LiquidAux which I use to play music through my car's stereo.
But if I turn on the LiquidAux's phone option, the Captivate remembers it.
I've also paired it with the Motorola HT820 stereo bluetooth headset and it seems to remember that one as well but that has phone option too. I'll have to try turning off the phone function and see if it remembers then.

ozone777 said:
For me it seems to only "remember" the devices that have phone capability turned on.
For instance, it never loses my Jawbone headset but it always loses my Kensington LiquidAux which I use to play music through my car's stereo.
But if I turn on the LiquidAux's phone option, the Captivate remembers it.
I've also paired it with the Motorola HT820 stereo bluetooth headset and it seems to remember that one as well but that has phone option too. I'll have to try turning off the phone function and see if it remembers then.
Click to expand...
Click to collapse
yes that is the exact same problem I have, If i disable the phone option for the BT car stereo then in gets erased when i restart my phone but if i keep it enabled then it doesn't seem to get erased. WTF can someone provide a logical explanation for this or can someone who is rooted give a counter example

My phone is rooted and currently running the JH2 ROM.
But I have experienced this problem with the original ROM as well.
I've tested with three different Bluetooth stereo/phone devices and the result was the same with all three: remove phone option and the profile eventually disappears.
As long as you don't disable the phone option of your bluetooth device it should remain in the Captivate's profile list.

ozone777 said:
My phone is rooted and currently running the JH2 ROM.
But I have experienced this problem with the original ROM as well.
I've tested with three different Bluetooth stereo/phone devices and the result was the same with all three: remove phone option and the profile eventually disappears.
As long as you don't disable the phone option of your bluetooth device it should remain in the Captivate's profile list.
Click to expand...
Click to collapse
are you saying that the jh2 rom does not have this problem??

On the Contrary...
irus said:
are you saying that the jh2 rom does not have this problem??
Click to expand...
Click to collapse
No, I'm saying that it definitely DOES have the problem. So it does not appear to be ROM specific. There is a JH3 ROM out now that I think I will try today. I'll post my findings once I've had a chance to experiment.
Also, I'd like to know if anyone running any of the other modified i9000 ROMs, like JM5, is having the same problem.

Well, I just installed the JH3 ROM but the problem is still there.
Looks like we'll have to wait for Froyo and hope for the best.

Problem FIXED in froyo ji6
I just want to let everyone know who has had this problem that it is fixed in the leaked froyo build jfyi

I can't get the Captivate to connect via Bluetooth to anything other than my car.
It pairs with my Windows 7 computer, but will not connect.
I've even tried connecting via Bluetooth to Kies without success.
Is there a way to do file transfer via Bluetooth?

irus said:
Update. I have realized that this happens everytime i do a softreset using rebootnow app. Has anyone else had this problem? Thanks
Click to expand...
Click to collapse
Yup, I just found out that I have the exact same problem.

irus said:
I just want to let everyone know who has had this problem that it is fixed in the leaked froyo build jfyi
Click to expand...
Click to collapse
I'm running froyo and it's not fixed. I didn't have this problem with android 2.1, but noticed the problem after upgrading to froyo.

Bluetooth Media Issue

I've searched extensively and can't seem to find the specific answer I'm looking for. Ever since my phone updated to 5.1.1 my Bluetooth media connection won't work, just my call audio. This really pisses me off because I JUST bought a new head unit for my car so I could stream audio from my phone. My phone is not rooted and I wasn't planning on going through the hassle of rooting this one. Is there a fix without rooting? If not, will rooting and flashing a custom ROM fix the issue? I see there are some marshmallow ROMs already out.

I'm on 5.1.1 and have to power on and off my Bluetooth adapter half the time. Phone doesn't connect to data wifi or blue tooth in till adaptor is rebooted. Says it's connected.

I've tried it. Turned off bluetooth and turned it back on, as well as went into the bluetooth settings and turned "call audio" and "media audio" off/on multiple times. For less than a second if I have music playing it will play through the car and then the phone kicks media audio off again.

After I'm connected, I can take a call and music resumes. I've had problems with some apps that updates have fixed. But not what your describing. Maybe one of the auto connect apps from the play store?

dochab1 said:
I've searched extensively and can't seem to find the specific answer I'm looking for. Ever since my phone updated to 5.1.1 my Bluetooth media connection won't work, just my call audio. This really pisses me off because I JUST bought a new head unit for my car so I could stream audio from my phone. My phone is not rooted and I wasn't planning on going through the hassle of rooting this one. Is there a fix without rooting? If not, will rooting and flashing a custom ROM fix the issue? I see there are some marshmallow ROMs already out.
Click to expand...
Click to collapse
You cannot root the phone even if you wanted to because of the locked bootloader. Do you have the latest firmware update for your head unit? If not see if updating it may help. I have a top of the line Kenwood NAV head unit that worked without a hitch on my S4. When I got the S6 calls worked fine but I couldn't get audio to work. I found a solution on a Kenwood support site and now it works without any issues. Somehow settings were changed when I switch from the S4 to the S6. Also could there be an issue with your mobile data?

CM13.0 Bleutooth can't connecto to my car radio

Hi, i'm running CM13.0 nightlies on an Oneplus One and i can't connect to my handsfree system in the car with any CM13.0 nightly that i have access to.
Thats why i'm not creating an issue in the NIGHTLIES project in cyanogenmod's jira since i don't have a last known good nightly version and all other projects are for stable versions.
My handsfree system is a Android 4.4.4 car radio and supports Headset, A2DP, AVRCP and contact transfer. This all works with latest CM12.1.
Symptoms:
The phone tries to connect but each time it appears to connect to Headset service, it disconnects. It does this 3 times till finally it just gives up and lists "Connected (no phone)".
A2DP and AVRCP work after this but no phone or contact transfer.
CM12.1 works.
LG Nexus 5X running Android 6.0.1 works.
CM13.0 doesn't.
This is the log of the phone while i connect:
http://pastebin.com/wdMxc1CG
And this is the same log but for the android car radio:
http://pastebin.com/DHjTX1hn
Does anybody have a fix or the same bug ?
EDIT: Eh, can't edit title. Bleutooth -> Bluetooth and connecto -> connect

Same bug here...

works fine on my stereo but it aint android, music plays absolutely fine, phone calls work fine etc...

I've been running CM13 nightlies for a while and haven't had any issues with bluetooth and my car stereo. Just upgraded to the latest nightly last night, and the morning commute was fine.

I can play music and make calls from my car bluetooth without problems. I have noticed though on certain nightlies if CM makes bluetooth/firmware changes, I have to delete/forget bluetooth connections in car and phone, then re-pair it from scratch for it to properly work again.

Yep, it seems to be a problem with that specific device. I can connect fine to all other BT devices i have, but that one is very important because i can't be taking calls while driving without it.

Me too. Android car head unit.

undrwater said:
Me too. Android car head unit.
Click to expand...
Click to collapse
Similar problem. I was using an RK3188 Android head unit. The OPO could connect, but it would not stay connected. It seemed to be crashing the bluetooth on the stereo, as my OBD2 bluetooth dongle couldn't stay connected either.
Switched to my old Nexus 5, and all was well. Decided to take out the Android head unit and put my stock Fiat stereo back in, which worked fine also with the Nexus 5. Switched back to my OPO, and it can't even properly pair/connect with the factory car stereo. Two completely different devices, problem on both, it's the effin OPO.
Running official OPO build CM 12.1 btw.
I'm sick as **** of this phone. I hate and loathe it. I had to fight tooth and nail to find a modem version that didn't constantly lose signal and drain the battery. Now I realize the Bluetooth is broken, probably the modem again. Flashing anything to this phone is a nightmare due to the way they try to force you back to the stock bootloader. Last time I updated modems I ended up soft bricked, thankfully I had the right files backed up and was able to recover - but it took MULTIPLE tries and several hours to get the modem to flash correctly after that.
So the idea of going on another wild goose chase trying to fix the bluetooth.... *sigh*....
I may just do a full flash back to stock (if it will even cooperate long enough to do that) and ebay this POS. I will never buy a non-Nexus phone again.

I found a way to make the OPO and CM13.0 connect to the android car radio again.
Enable root access in Developer Options, open File manager and open the /system/etc/init.qcom.bt.sh and edit the following line:
setprop ro.bluetooth.hfp.ver 1.7
... to:
setprop ro.bluetooth.hfp.ver 1.5
... and save the file and reboot, and it works again for me. No problems till now.

stormlabs said:
I found a way to make the OPO and CM13.0 connect to the android car radio again.
Enable root access in Developer Options, open File manager and open the /system/etc/init.qcom.bt.sh and edit the following line:
setprop ro.bluetooth.hfp.ver 1.7
... to:
setprop ro.bluetooth.hfp.ver 1.5
... and save the file and reboot, and it works again for me. No problems till now.
Click to expand...
Click to collapse
This commit was merged in the 20160224 nightly: http://review.cyanogenmod.org/#/c/133778/
Does it fix your connection issue?

ryanmat said:
This commit was merged in the 20160224 nightly: http://review.cyanogenmod.org/#/c/133778/
Does it fix your connection issue?
Click to expand...
Click to collapse
No, i had to do the same patch to get it to work again.
Of note that if i simply comment out the hci_qcomm_init call in that same file, the phone also connects but then the MAC address will be wrong.

stormlabs said:
I found a way to make the OPO and CM13.0 connect to the android car radio again.
Enable root access in Developer Options, open File manager and open the /system/etc/init.qcom.bt.sh and edit the following line:
setprop ro.bluetooth.hfp.ver 1.7
... to:
setprop ro.bluetooth.hfp.ver 1.5
... and save the file and reboot, and it works again for me. No problems till now.
Click to expand...
Click to collapse
That solved the same issue for me. Thanks.

CM13 here on a GS5, connecting to an NR3001 Newsmy head unit running KitKat. I have all of the bluetooth functions except for Album Art. I'll give this a shot, see if it works.
Edit: welp, that file doesn't exist on my device. so I guess I'll keep looking

Just a small note: Since 2016-05-01 my Nexus6p running CM13 nightlies works with my HeadUnit!
Horray!

markusmuster said:
Just a small note: Since 2016-05-01 my Nexus6p running CM13 nightlies works with my HeadUnit!
Horray!
Click to expand...
Click to collapse
Yep, the 20160429 nightly fixed it for me.

ver 1.6
I changed my setprop to 1.7 to 1.5 and my car could not see it at all after that.
Looked into my other Oneplus one running Broken and noticed that both "setprop ro.bluetooth.hfp versions were 1.6.
Set to 1.6 now phone connects and reconnects perfect! Yeah!

I just saw this post and I'm wondering if this is the same issue I'm facing. When using my OPO with latest official CyanogenOS in my wifes BMW series1, everything seems to be working fine. However in my BMW X1 everything except phonecalls are working. The radio stops when a call is placed (which is good) but the audio of the phone is stuttering and seems to give up after 5 seconds while the line stays open I think. I then always need to enable the loudspeaker in order to have a conversation handfree but without using the carkit. picking up the phone via steeringwheel buttons or on the phone itself does not make any difference. Removing and re-pairing the device does not solve it. And everything started after a certain upgrade of CyanogenOS.

stormlabs said:
I found a way to make the OPO and CM13.0 connect to the android car radio again.
Enable root access in Developer Options, open File manager and open the /system/etc/init.qcom.bt.sh and edit the following line:
setprop ro.bluetooth.hfp.ver 1.7
... to:
setprop ro.bluetooth.hfp.ver 1.5
... and save the file and reboot, and it works again for me. No problems till now.
Click to expand...
Click to collapse
Add this fix to your main post and edit thread title to "solved" so that people having similar issues can lookout on your thread.

Cannot play audio over USB with the Mate 8? Is it possible?

Hey there, hopefully someone can offer some insight here. I just recently got a Mate 8 and something that I did frequently with the Note 4 I had before was play audio in the car via the usb connection to my stereo. I am not able to do this with the Mate 8.
It ACTS like it's playing audio, but there's just no sound coming from the stereo or from the phones speakers. I can still change songs and play/pause it via the car stereo controls, however, which is also weird. In the developer usb options it's listed as "Audio Source", and trying to choose a mode for file transfer from the notification just causes USB to disconnect and reconnect and go back to not having anything selected. It didnt work on unrooted, unmodified, stock firmware (chinese B156), and it still doesnt work after I fully wiped all data and flashed a custom rom (KangVIP Slim).
Any ideas? Has anyone else successfully played audio over usb with their mate 8? Thanks guys.

What head unit do you own?

themissionimpossible said:
What head unit do you own?
Click to expand...
Click to collapse
I own a Kenwood Excelon DPX791BH. It has two modes, one which plays local files using its android app and displays the song info on the unit and one which just plays back any audio from the phone at all, both do the exact same thing (act like they're playing, and respond to controls from the unit.) Interestingly, in the file playback mode the current time indicator on the head unit seems to run through the file at double speed. It happens with any audio, notifications or Spotify or local files, etc.

Have you tried with USB debug ON or OFF?

themissionimpossible said:
Have you tried with USB debug ON or OFF?
Click to expand...
Click to collapse
Yeah, I've tried both, it doesn't change anything. It still acts the same way.

Where are stored your audio files? Internal memory or microSD?

themissionimpossible said:
Where are stored your audio files? Internal memory or microSD?
Click to expand...
Click to collapse
the main thing i use it for is just the routing audio mode, which is independent of the location of the files. It basically functions like how a pair of headphones would if you connected it to the headphone jack and plays any audio that is produced by the phone. I've tried playing audio from the SD card and internal storage, however.

Have you tried the Mate 8 USB connection mode as MTP?

themissionimpossible said:
Have you tried the Mate 8 USB connection mode as MTP?
Click to expand...
Click to collapse
yeah, as I said in the initial post selecting either of the two USB connection options from the notification, MTP or PTP, causes the device to quickly disconnect and reconnect with neither selected.

Maybe there is an incompatibility with Android 6.
If you can you could try to connect another Android 6 smartphone.

themissionimpossible said:
Maybe there is an incompatibility with Android 6.
If you can you could try to connect another Android 6 smartphone.
Click to expand...
Click to collapse
That's what I was thinking is possible, but I haven't heard of anyone else having this problem. Has anyone used USB audio on the huawei mate 8 or any other android 6 phone? The only other phone I have is my old note 4 and that doesn't have android 6 on it.

aDarkBox said:
but I haven't heard of anyone else having this problem. .
Click to expand...
Click to collapse
The compatibility problem might reside in your car stereo, you might find other users of your same unit to contact on a Kenwood car stereo dedicated forum.

themissionimpossible said:
The compatibility problem might reside in your car stereo, you might find other users of your same unit to contact on a Kenwood car stereo dedicated forum.
Click to expand...
Click to collapse
If anyone else can confirm audio out via USB is possible on the mate 8, then that would be the next step, as the head unit has worked with other phones in the past, and still works with my note 4. Right now asking here seems like the best idea. Hopefully someone can confirm or deny usb audio out is a possibility with the mate 8

aDarkBox said:
Hopefully someone can confirm or deny usb audio out is a possibility with the mate 8
Click to expand...
Click to collapse
But with which car stereo or device?

Under developer options there's a setting to enable USB audio source. The toggle is under network then select USB configuration. Not sure if this will help but worth a shot
Sent from my HUAWEI NXT-L29 using Tapatalk

manook said:
Under developer options there's a setting to enable USB audio source. The toggle is under network then select USB configuration. Not sure if this will help but worth a shot
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
I've tried that one as well, it does the same thing as choosing an option from the notification bar

did anyone find a solution for this? ill be forever in debt if you share it, i buy this phone yesterday and i love it but if i cant make it work that way i throw it away :crying::crying::crying:

hdavid185 said:
did anyone find a solution for this? ill be forever in debt if you share it, i buy this phone yesterday and i love it but if i cant make it work that way i throw it away :crying::crying::crying:
Click to expand...
Click to collapse
No, sadly. Nobody has responded and it still doesn't work. Nobody has said they have been able to do it, either.

aDarkBox said:
No, sadly. Nobody has responded and it still doesn't work. Nobody has said they have been able to do it, either.
Click to expand...
Click to collapse
It seems to be Android 6.0 ive seen threads about the same issue with other phones that worked just fine before marshmallow.

hdavid185 said:
It seems to be Android 6.0 ive seen threads about the same issue with other phones that worked just fine before marshmallow.
Click to expand...
Click to collapse
Have you seen any threads where someone is actively working on this issue?

Pixel 3 a Q Beta 5 Android Auto Volume Low

Anyone have issues with low volume with android auto. My 3 XL works fine, proper volume etc....But with my 3a whenever I try and play music the volume is very low. I have to turn the head unit volume all the way up to even hear it.
I tried a different cable, resetting car and phone. etc
If yours is good are you on Pie?
Thanks

Direct connection or via Bluetooth?
If Bluetooth, there is a setting in the developer settings called "Disable absolute volume". Click that and it may fix your Bluetooth volume issues.

sic0048 said:
Direct connection or via Bluetooth?
If Bluetooth, there is a setting in the developer settings called "Disable absolute volume". Click that and it may fix your Bluetooth volume issues.
Click to expand...
Click to collapse
The issue is with direct connection. Bluetooth is perfect.

Reinstalled pie.... volume is fine..... anyone on Q beta 5 have good direct connection sound in Android Auto?

https://issuetracker.google.com/issues/139212436
Reported. Still an issue on DP6.
Edit: please star it if you experience the issue as well.

I have a Pixel 2 XL and have the exact same issue. Started having the issues in DP5 and it's continuing into DP6. I also just got my phone replaced yesterday by Google for a screen burn, so the first thing I did was update to Q and check to see if it was maybe the old phone, but nope, even with a straight from factory phone with new install of Q it's no different. Starred your post in issuetracker

Found a Reddit article with a work around for this issue. It worked for me so maybe it will work for you! In developer settings change the below Bluetooth setting to 1.6 and reboot phone and try again.

engle2192 said:
Found a Reddit article with a work around for this issue. It worked for me so maybe it will work for you! In developer settings change the below Bluetooth setting to 1.6 and reboot phone and try again.
Click to expand...
Click to collapse
Odd a Bluetooth setting fixes USB audio routing. Audio through BT is fine in the car, only when routing through USB it is low. Will try next time I drive my in-law's car.

Uzephi said:
Odd a Bluetooth setting fixes USB audio routing. Audio through BT is fine in the car, only when routing through USB it is low. Will try next time I drive my in-law's car.
Click to expand...
Click to collapse
I agree it is odd. However after thinking about it a little when using android auto it requires your phone to be connected via bluetooth at the same time. Even if you un-pair your phone and turn off your bluetooth android auto turns bluetooth back on and pairs your phone to your car.(Atleast with mine that is)
But I have been having success since Friday now after making that change so hopefully it helps you out as well!

I saw the suggestion of that during DP5 and tried that and there was very little difference for me switching to 1.6