Dear forum,
really looking for some help with the bluetooth connection and/or some pointers into the right direction.
Before anyone asks, yes I have searched the forum(s) and googled days in a row, tried several builds and found a lot of bluetooth questions/issues but not this specific issue nor a solution.
Have a S4 i9505 which has a perfect bluetooth connection with my Renault Carminat system using the stock rom. As I had other issues with the stock rom, I rooted and upgraded the phone to Optimized LineageOS 14.1 (7.1.2). When pairing the phone to the car, it all works fine (it doesn't disconnect - which is a commonly reported issue). media streaming works fine, the car audio system also responds to the phone (and vice versa), contacts are imported etc. The big issue is however that there is no sound (nor receiving nor sending) when a call is received and/or intitiated.
In my quest to resolve this issue I let the dealer upgrade the firmware of the car audio system, tried with at least two different (but similar) S4 i9505 phones on custom roms, tried several other custom builds (from CM12 to CM14), tried an older but also the latest modem/BL for my region (XXSPQA1), tried some nightly builds but in all cases the exact same issue remains. Only when I go back to the stock rom, I have again a perfect bluetooth connection. A S5 (with stock Android 6) can connect to my system without issues as well.
So my thoughts are that the issue lies within custom roms as even a custom rom based on the same Android version as stock rom doesn't work properly.
Any thoughts what I can do more? Is it possible to copy the BT files from the stock rom and copy it to the custom rom? Any ideas? If it can help to post certain logs I will absolutely do so. Phone is on stock rom again now.
Thank you for your support!
I have exactly the same issue on my I9505, every time i connect to bluetooth (previous car, new car bluetooth speaker calling seems to work , but ther is no sound (only the end of call beep. and also, after disabling bluetooth, the sound is still not working ... i have to reboot my mobile to be able to call again. i hope this issue can be resolved
( when connecting to a bluetooth device for playing media blutooth works )
Same here. I hear a distortion sound when a call is made though. Worked fine with 5.X and broken in 8.0 and 8.1. I tried various modems as well. I even changed codecs in the developer options and didn't find one that worked. i9505
Related
Hey all,
Recently got my n4 and am currently running cm10 nightlies on it, but today I picked up our new car (Hyundai i30 premium) which has bluetooth built into the audio system and I can't get my n4 to sync with it properly. My partners Desire HD syncs no problems and all her contacts phone book everything shows up fine. My n4 wouldn't even sync originally then I just kept retrying and eventually it synced but nothing really works, music won't play through the speakers (the audio system just sits there waiting for music and nothing happens) my phonebook etc don't show up (after me allowing them permission) I can't even make calls.
I have heard that the n4 has some bluetooth problems but nothing this bad, anyone have any suggestions that I can try? Happy to go to another ROM if that will help??
Thanks,
Hosh
this build has serious BT issues. i can't even find a mouse that works. wait and see what the 4.2.2 update brings.
I own a Hyundai Elantra GT which is the US version of the i30 - I didn't seem to experience any issues when I paired it this morning, but I"ll double check when I get out of work this afternoon that the contact sync is working. I am, however, on the stock rom.
I own a 4 day old Dodge Journey and it pairs with no issue to Uconnect.
Try a different rom?
If thats not it, then its your hardware.
The new bluetooth stack in Android 4.2 is causing a lot of issues. Personally, I don't have any problems connecting to UConnect (Jeep Grand Cherokee) or my SmartMini (bluetooth music streaming).
I am waiting on delivery for my MetaWatch, there have been complaints that 4.2 isn't connecting well with it but I guess we'll see. CM10.1 users don't seem to have as many problems. I'm running Xylon w/ Franco r53.
I had the same problem with Chevrolet captiva until I have installed custom ROM and is working perfect now.I have tried every custom ROM and is OK with all.
I have this problem but there is a way around it (for me anyway).
Download Bluetooth file transfer from the market.
Delete the connections with your car. Both on the phone and your car.
Open Bluetooth file transfer. Select the Bluetooth screen.
Make a connection. The default android Bluetooth will ask for a password. Don't enter it. Instead go to your recent apps and select Bluetooth file transfer. Put the password in the request screen the app supplies.
Bluetooth file transfer should pair the devices and make a connection.
Once done. Kill Bluetooth file transfer as you won't be able to exit.
You can then uninstall Bluetooth file transfer if you want (although I tend to keep it for when I change ROMs or have to do a factory reset etc).
Hope this works for you
Sent from my Nexus 4 using xda premium
Hey all,
Sorry for the late reply, been away for the weekend. Thanks for all the advice, tried them all and no luck. Will try out a mates n4 tomorrow and see if he has any luck syncing with the car, if he does might just flash roms again.
after flashing a new rom, I had problems pairing w/bluetooth and connecting w/wi-fi. I fixed the problem by restoring my system settings w/titanium backup thanks to someone's suggestion.
Seems the only thing that worked for me is when it asks to sync my phonebook I have to say no, if I say yes it seems to freeze the whole thing. Makes me think if I click yes I might just need to give it 10-15 mins to sync, might try that tomorrow. But for the moment at least it's half working!
I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.
Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?
Blazing angel said:
I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.
Click to expand...
Click to collapse
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.
BassBlaster said:
Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?
Click to expand...
Click to collapse
It is a rev_11
paul c said:
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.
Click to expand...
Click to collapse
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !
Mine is also a rev11, 303k. I guess that rules out hardware issue
Blazing angel said:
It is a rev_11
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.
I'm experiencing exactly the same problems than Blazing angel.
Bluetooth is unusable in my car, "Unfortunately, the process com.android.bluetooth has stopped" being displayed repetitively.
I suspect it's not hardware related as I do not have problem using the stock or paranoid ROMs. Unfortunately, my favorite ROMs (AOKP, CN or Carbon) are causing problems.
Do you think it's possible to pickeup some files in the paranoid files and inject them to Carbon to solve the problem ?
Thanks in advance for your help !
paul c said:
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.
Click to expand...
Click to collapse
Great ! I was able to bypass my bluetooth problem using this Android 4.4.4 rom, without loosing great features of Carbon or Pac-ROM ! :victory:
Thanks for sharing this ROM Paul ! :good:
OK,
So I'm trying to get some help regarding this issue. I will continue to try different ROM's and what not to see if it can be resolved. I'm simply at a loss to where the issue lies though, however as of today, every custom ROM has been giving me trouble. My plan for today is to flash a stock ROM via Odin and then if that works go for Imperium, however I'm hoping with your help I may be able to solve it on something like CM12 or what not because I prefer the flexibility of a proper custom ROM.
OK, so the issue I have:
I have a car head unit which has bluetooth built-in. Music plays fine through Bluetooth, no jitters or issues. However, when I try and call someone and I'm listening to the radio or something non-Bluetooth, the phone does not send the signal (?) to the head unit to switch to Bluetooth. This means the call will be made via the dialer app and while the audio IS being routed through the bluetooth channel, the head unit does not know about it because it hasn't received the signal to switch to Bluetooth. I can switch it manually to Bluetooth and make and receive calls, but this isn't convenient at all and probably quite dangerous when I'm driving a car. The same applies when receiving a call.
Here's the thing, if I go into Bluetooth, select CAR KIT and go configuration, if I disable Media Audio, then it works fine! The phone correctly sends the signal to switch to Bluetooth and the head unit does so. The call goes through and it all works fine. This is repeatable.
Therefore, the issue I'm having lies in the fact both Media and Phone Audio are enabled at the same time. Has anyone else had this issue and does anyone have a suggestion to fix it?
Before someone suggests "just disable media audio". My answer is no, this isn't convenient at all. I use Bluetooth media quite a lot, and simply disabling and re-enabling it everytime simply isn't an option.
So far, I've had this issue on:
CM12.1 Optimized
CM12.1 Nightly
Mokee ROM
DirtyUnicorns
CM12 Nightly
I'm yet to try a stock Lollipop ROM. I know for a fact however, that stock KitKat DOES work.
I really could do with some help here, so any suggestions would be awesome.
all the roms you have tried are aosp....aosp is not designed for the s4 as its not an officially supported device (its not a nexus) so things like bluetooth and the camera will always be broken as the required stuff needed is proprietary to samsung
go back to stock and your problem will be solved
DSA said:
all the roms you have tried are aosp....aosp is not designed for the s4 as its not an officially supported device (its not a nexus) so things like bluetooth and the camera will always be broken as the required stuff needed is proprietary to samsung
go back to stock and your problem will be solved
Click to expand...
Click to collapse
The Bluetooth itself is fine. Audio quality is fine. Call quality is fine. It just seems like a tiny little thing that's causing all these issues for me, because if it could trigger my car head unit to switch, I wouldn't even dream of stock. Also the camera seems fine to be fair?
I'm not keen on going back to stock.... at all, so I'm thinking Imperium. It's a shame though because apart from this BT issue, CM12 is fantastic on this device. Takes a 2 year old phone and makes it feel like a brand new phone.
I really hope someone can fix that Bluetooth bug in CM12.1. I may even look myself, it must be something pretty small from a coding perspective because as I said, the functionality is clearly there as evidenced by the fact it works with Media audio turned off.
Regardless, thanks anyway
Changing the modem did not solve my problem.
When did you try the Optimized and the nightlies? There have been a lot of fixes lately regarding bluetooth.
Hello,
Where my bluetooth previously worked on Android 5.0, ever since upgrading my i9505 to 6, Bluetooth does seem to connect, but calls still go though the speaker and I cannot change it to Bluetooth mode (my car, however, sees it). And when hanging up the phone, the phone will say "Hanging Up" yet still stay connected for what seems to be an indefinite amount of time - or until I restart the phone. Needless to say, callers on the other end cannot hear me. And, when playing music, the car's head unit does show that it's playing but again, music comes through the phone's speaker only.
Any advice? I've already tried flashing AOSP 6.0 and Kushan CM 13.0 and it's the same thing on both.
Thanks.
DJRepresent said:
Hello,
Where my bluetooth previously worked on Android 5.0, ever since upgrading my i9505 to 6, Bluetooth does seem to connect, but calls still go though the speaker and I cannot change it to Bluetooth mode (my car, however, sees it). And when hanging up the phone, the phone will say "Hanging Up" yet still stay connected for what seems to be an indefinite amount of time - or until I restart the phone. Needless to say, callers on the other end cannot hear me. And, when playing music, the car's head unit does show that it's playing but again, music comes through the phone's speaker only.
Any advice? I've already tried flashing AOSP 6.0 and Kushan CM 13.0 and it's the same thing on both.
Thanks.
Click to expand...
Click to collapse
Simple
6.0 Rom bugs.
Wait until they are fixed
They all are based on the same code. So if one roms has it they all have it.
Keep in mind that MM is brand new so you just have to be patient for it to be fixed.
DJRepresent said:
Hello,
Where my bluetooth previously worked on Android 5.0, ever since upgrading my i9505 to 6, Bluetooth does seem to connect
Thanks.
Click to expand...
Click to collapse
In a strange coincidence, I had all sorts of trouble on my i9505 with Bluetooth on 5 but is mostly resolved on 6 (CM 13 official).
mr.b00tl00p said:
In a strange coincidence, I had all sorts of trouble on my i9505 with Bluetooth on 5 but is mostly resolved on 6 (CM 13 official).
Click to expand...
Click to collapse
same here, but now i have new one's like connecting my mi band at all :/
I also had problems with BT with the CM13 Official Nightlies, and also with the Resurrection Remix.
But I now use the JDCTeam 6.0.1 ROM, and I don't have BT issues, I only use my BT in car, but I can send and receive phone calls, and also stream my music via BT.
Furthermore, almost everyone complains about the no sound with the calling issues.
I also had those issues back to the official CM13 and the RR 6.0.1 versions.
For me, this ROM is really good, you would maybe give it a try.
I use an old bootloader, the FNB8, but it seems to work pretty fine.
Greetings,
my father owns a Samsung Galaxy Note 3 LTE (hlte) and we've flashed Lineage OS 14.1 some months ago. The device runs great, but he has issues with the bluetooth car connection.
What works:
connecting the device via BT to his car
playing audio
receiving calls (and probably making calls)
copy phone book (by exporting the contacts list and share the .vcf file via BT)
What does not work:
accessing contacts on the smartphone (without copying them)
incoming calls do not show the callers name in the car display, only the phone number
We've tested everything with two car audio devices of different manufacturers, both of them are unable to access the phone contacts. If I'm hooking up my Pixel (stock Android 9) everything works great, so the problem is clearly caused by LineageOS on the Note 3.
Is this a known bug and is there any way to solve it?
Current installed LOS version is: lineage-14.1-20181209-nightly-hlte-signed
Thanks in advance!
Yes if you read BT has bugs .
FLASH STOCK ROM FOR WORKING BT.
Devs are working on it long time.