Maybe someone knows something about this. Running cm 4.3.1 and currently I can view and hear incoming text messages via bluetooth in my car (ford sync). While running a kk rom although it asks to confirm bluetooth map access but I never see any incoming messages and settings indicate that my phone doesn't support this feature but of course it does since it works with 4.3.1 just fine. is this a known issue with kitkat?
Related
My car has bluetooth for for phone conversations, but not for media, so I also use a Blackberry Bluetooth Adapter. TW Roms consistently only auto connect to one of these devices and I have to manually connect to the 2nd. AOSP roms will always auto connect to both without intervention.
I know there have been apps like "Bluetooth Auto Connect" that help address the issue, but they still require you to turn on/off bluetooth. It's tough to seamlessly automate this in Tasker.
Is this something that can be addressed by devs of TW roms? It works just fine in AOSP!
I recently loaded Quantum v3.21 & QuantumKernel 1/14. Afterwards I noticed that once I connect a bluetooth device, I loose all ringtone and notifications. Disconnect the bluetooth device and everything sounds off again like normal.
I've also noticed that out of all of the notification sounds in my BBM list, the only one that will sound is the default BBM tone. All of the others are silent. Is there a fix for any of this?
Thanks
on kernel 1/21 now and still no sound from main speaker when bluetooth is connected
up to version 3.27 and kernel 1.27 and still having the same BT issues...
from reading other forums... It seems to be a toss up between CM and 4.4.2
Now I need instructions on downgrading from 4.4.2 to 4.3
Hi,
I have a Moto G and I would like to use it with my Audi A3 bluetooth kit (This is a kit that I rewired from another car to work with mine, nothing too complicated). It includes a single button on the dash that should answer calls, end calls, voice dial and redial last number (long press).
This worked great with my iPhone 4, not so well with my Moto G. The system answers incoming calls, redails and ends calls. But I cannot get the voice dial working very well.
I have tried using bluetooth launch to point at specific voice dialling applications, but it cannot work from the lockscreen. Also, the stock voice dialler is flaky at best, and requires google now to be open on the phone.
Any suggestions welcome please...
Thanks,
Rich
Same issue with my moto x and my jvc bluetooth deck.
With 4.2.2 Jellybean it worked flawlessly.
Updated to 4.4.2 last night and now I get a "not supoorted" error on the deck when I try to initiate voice dialing.
A similar problem with my XT1033 on android 4.4.2 and Toyota Prius '05. When a call sends from the car's native bluetooth kit, works fine. But when dialing on the phone or get an incoming call, the car system doesn't recognize that the call have started.
Hello together,
I am new here, my name ist Michael and come from germany so I hope you can understand my problem/question.
I have a Nexus5, rooted and tried some diffrent custom roms. I found that mahdi works as the best. Fast, good styles and menues etc.
But I have a problem with bluetooth audio. I use soundabout-TTS app which allows to route the sound e.g. from navigation to the cars handsfree system.
With the stock-rom and cm11 it works as epected, with other roms (e.g. PA, SlimCat, and more) I have BT connection probs with my car (Ford Sync Gen1 -Sony). At least I had to reset my car audio system to work normaly
With mahdi I have two other major problems.
1. the first 3 or 4 seconds of the text is missing ...
Normal text to hear ..... Thank you for using soundabout.
With mahdi-rom............ ------------------------------------bout
2. the car shows me an incoming call ... thats good
i hear the text cuted voice from N5
BUT the call did not stop, the cars handsfree still hold the call and did not go back to e.g radio or disk.
Is there anything to adjust audio-buffer or aomething like this?
I like mahdi-rom but with this issue I cannot use it.
Michael
Maybe post in Mahdi thread
I just flashed the OTA update for Android 6.0 last week on my Nexus 5 and I noticed that with the new update, phone calls no longer get routed through Bluetooth on my Mazda3. It is able to pair fine with the car and can stream music through Bluetooth, but calls do not go through.
Here is what happens:
When I place a call, the audio automatically gets routed back to the phone. If the other person picks up, calls will continue going through the phone speaker unless I manually select route through Bluetooth. Sometimes this works and sometimes it doesn't, but it does get frustrating trying this workaround especially while driving.
I tried unpairing and re-pairing bluetooth with the car, cleared the data and cache of the Bluetooth app on the phone, and even tried a factory reset, but the problem still persists. Anybody else run into the same issue and found any possible fixes?
For the record, when I did this with Lollipop 5.1.1, it worked without a hitch.
Thanks!
I am having a similar problem trying to connect my Nexus 5 running Android 6.0 to my JVC car stereo. It continually complains of an invalid key, albeit both phone and car head unit show the correct key.
I am unable to make a bluetooth connection at all with the stereo. I had no issue with my Nexus when it was running 5.1, and my iPhone 5 continues to pair with the stereo.
I had this issue on the last preview but haven't seen it yet on final 6.0. For either regular calls or Hangouts calls.
I just rolled back to 5.1.1 and Bluetooth calls work fine with the car now. So it appears that it is a problem that is resident in 6.0.
Same here, but a little different: It pairs and when I start a call from the menu it goes down but the call is still up on the phone. When the other person picks up the call is re-routed to the car speakers... very strange behaviour!
Same behavior as what you are seeing when paired to a '15 Accord but works fine on a '14 Camry.
im at 6.0.1 and has the same problem, streaming music through bluetooth is ok but no voice call...
Any news on this? My wife's nexus has same problem. Nexus 5 with Android 6.0.1. compiling version M4B30Z.
I read on a different site to disable wireless scanning in location. Just tied that and have been able to make and receive calls from the car. Will be interesting to see if it continues to work.