When NS is connected to my car audio system, it randomly disconnects and then re-connects after a few seconds.
This does not happen with other android phones I have tried.
I'm running AOKP ICS Milestone 6 rom.
Is this related to the radio(modem) being used or is it ROM related ?
Related
Hi Guys,
I'm having issues with my Desire S disconnecting from my car randomly after a call has been placed (it doesn't happen everytime). Only the phone part disconnects and not the media part, i have to turn bluetooth on and off on the phone to get it to re-connect and the car doesn't realise that the phone has disconnected itself.
I used to have issues with bluetooth on my old desire which would disconnect after a few seconds, it was the main reason i sold it. I've had no bluetooth issues with any other androids that ive owned/own (Optimus One, Moto Defy, Sony Ericsson Xperia X8/X10Mini, ZTE Blade).
Has anybody else had bluetooth issues, or know of any fixes?
Problems, yes - fixes, no.
Even had to pull the radio fuse to get the radio back a couple of times. I think the DS Bluetooth implementation is rather broken.
Not having any problems using my bluetooth headset although i have not tried any other devices.
The problem I am referring too is bluetooth devices not automatically connecting to AOSP 4.X.X roms. This happens with my bluetooth 4 out of 5 times I try to connect it. My bluetooth is a Blackberry Stereo Gateway (hereafter referred to as BSG) that I use in my car. I have seen this bluetooth behavior on every 4.X.X AOSP rom I've ran so far, including any cm10 roms that have been floating around. I am currently running CM9 for stability over cm10. Afaik AOSP kernels are basically interchangeable between ICS or JB, my cm9 rom has linux 3.0.43.
I just logged some bluetooth connections using ddms. These are not full logcats, they were captured in real time so I could offer more specific information. I am not a kernel developer, but I am a power user. Any other types of bluetooth need logging I can pull it off.
bluetooth connect crash.txt: I had just powered on the bluetooth in the phone, then I powered on the BSG. On the phone it showed Connecting, followed by Connected. Then it dc'd. The bluetooth icon showed blue briefly.
bluetooth power on dmsg.txt: Just a log of the bluetooth turning on.
bluetooth a2dp connect failed.txt: Powered on the BSG after the phones BT had already been on for a while. Phone says Connecting and then nothing. no bt icon changes. This one is the most common problem.
bluetooth a2dp connect succede.txt: Both phones BT and the BSG have been on. Connection initiated from the phone by tapping on the BSG's entry in the bluetooth screen. This one was logged right after the failed connection.
NEW bluetooth a2dp autoconnect success cm9.txt: Got in my car tonight and for once it auto connected. Pulled the log when I got home.
I am running CleanROM 7 (touchwiz basec ICS ROM) on my S3 and I've been using it in my car with a tunelink auto BT adapter that outputs to my aux port.
Lately, for seemingly no reason, the phone has stopped connecting the tunelink to media audio. The device is paired but never connects to media audio. When I have both devices on, under the BT menu on the phone I go to the tunelink device settings and try to check the box that says "media audio" it blinks for a second, sometimes it will say "connecting..." but then just stops and the check box never sets and it never connects to the device (the BT icon in the status bar never turns blue)
I just tried installing the latest firmware (modem) with no luck. I've rebooted, fixed permissions, with no luck. I just gave up in a battle to get BT audio to work with AOSP based ROMs (it was distorted and skipping) so I've just about had it with BT problems. I went back to CleanROM because I had been using it before I tried AOSP for a very long time with no issue. Does anyone have any ideas how I can fix this? Any insight is appreciated!
Any luck with this? I have a new Nexus 6 that I'm having the same problem with. Before my old Nexus 5 I had no issues.
I have a d2vzw running cyanogenmod CM, build M11. I recently bought a new car, a Mazda 3 with full infotainment system.
Frequently, while on a phone call through bluetooth, the call will stall (dead on both ends) and the infotainment screen will reboot. I have taken the car to the dealer and they say it is likely to be my modified phone that is the culprit since they show no issues with stock firmwear.
It is also common for the sound system to stop and not allow BT or USB audio through. It still lets FM radio, though. The screen does not reboot in this case, though.
So, the question: Is it possible/likely that this is my phone causing the reboots? So far, I have only noticed the reboots and stalls when connected via BT, but that has been most of the time.
And second: is there anything to be done other than going back to stock on my phone?
Has anyone else had this issue?
CM13 Bluetooth Issues
I'm running the latest nightly of Cyanogenmod 13 on my HTC One M8 Verizon phone, ran a clean install wiping all partitions and updating to the latest firmware. For some reason my Bluetooth turns off when the screen is locked. Any help?
There has been many issues with Bluetooth. I had constant disconnecting while streaming. The only option is to look at the change log for each nightly & look for Bluetooth fixes.
I'm also running the latest nightlies of CM13 on my verizon m8. I have clean flashed each version (probably 10 days in January). So far I have noticed the following issues:
I see Bluetooth audio stuttering - where the streaming connection to car (ford sync), headset, or speaker (bose) gets quite choppy. 3 seconds of silence, burst of audio, then more silence.
It appears to me to happen when connections change - If i drive away from my house and lose wifi or if I am underground on the subway and gain cell service for a moment, or I drop cell service in an area of sporadic coverage. In every case a reboot solves the problem until the next "connection change". When I am static, or in constant coverage, I have no issues streaming for hours.
Version CM 13.0-20160201-nightly-m8
Baseband 1.12.20.1211
Kernel 3.4.0-gf52bf8c