Hi Folks
I have a strange problem with my Samsung note 4's. When I pair to my Chevy Mylink in my 2017 Silverado 1500, the pairing works, my phone shows it is paired as both Media and Phone device, but if I try to initiate a call from my truck, it says there are no phones connected. The media stream works and I can play music through the trucks system from the phone. But incoming calls go into limbo and I can not place calls from the truck hands free.
The behavior is identical with two different Galaxy Note 4 W8's. I have tried, Lineage OS 15.1, Lineage OS 16, RR 6.1.0, RR 7.0.1. It seems like any Lineage OS based, android 8 or 9 rom behaves this way. I have not experienced any other bluetooth issues with any of my many other bluetooth devices and these roms.
I flashed the Marshmellow based Note4UXEdge_V10 rom and it behaves correctly when logging into the Truck's MyLink system. I can make and receive calls as expected.
Has anyone seen this behavior or anything similar? Anyone have any suggestions?
Thanks in advance
Related
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.
The phone with Lineageos 14.1 connects with my hands free car system and starts dialing but there is no communiction possible. I also have my gear s3 connected to the phone without any problem.
Taking an Iphone i have good connection and communication over the car radio.
Is there anything known about a corrective measure?
errut said:
The phone with Lineageos 14.1 connects with my hands free car system and starts dialing but there is no communiction possible. I also have my gear s3 connected to the phone without any problem.
Taking an Iphone i have good connection and communication over the car radio.
Is there anything known about a corrective measure?
Click to expand...
Click to collapse
Also having the same issue with my phone running latest Lineage OS. Trying to connect to my trucks Bluetooth. It's a Uconnect system. Plays music fine but can't make phone calls.
Even though I'm a big fan of AOSP, I suggest you to stick with official Samsung's firmware.
However, if you really want a fix, perhaps you should talk to LOS dev.
All best
Hi,
I've tried some of Oreo builds for klte and all of them have the same problem - randomly disconnecting bluetooth devices.
I've tried 2 Pie build as well and this problem still occurs.
Is there any Oreo or Pie build not affected by this BT bug?
I'm affected by this too. I've not yet found any ROMs which are ok. I've tried nougat roms: lineage, resurrection remix, crdroid, havoc.
I have my mi band 2 (Bluetooth low energy device) connected constantly and my headphones connected most of the time. What happens for me is that Bluetooth actually crashes and is temporarily unavailable, causing client devices connections to drop.
I have the same problem. Usually it is with my 2005 car and I thought perhaps it was the fact that an old bluetooth standard not being compatible. I was wrong.
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.
I installed GSI Roms like Pixel Experience, RR both ROMs have issue when using bluetooth call.
Tried with Skype or Whatsapp call, sound will go to phone speaker.
Bluetooth audio (non call) is fine though.
I tried to do bluetooth call from my pc using the same headset and it works normally.
Anybody having the same issue ?
Need help please
It's a massive issue with Android 9, not the Nokia 6.1 plus in particular. I'm returning my 6.1 plus tomorrow due to this problem. It cost me more than the phone to have my car's Bluetooth firmware brought up to be fully 5.0 compliant, but it made no difference.
Google completely **** the bed with Bluetooth on this release, and from what I can see online there's no fix in sight. Android die hard users are jumping ship to Apple all over the place due to this problem.
Short answer, if you want working Bluetooth calls on this device, flash an 8.1 Oreo build, then it will work.
Fazz1977 said:
It's a massive issue with Android 9, not the Nokia 6.1 plus in particular. I'm returning my 6.1 plus tomorrow due to this problem. It cost me more than the phone to have my car's Bluetooth firmware brought up to be fully 5.0 compliant, but it made no difference.
Google completely **** the bed with Bluetooth on this release, and from what I can see online there's no fix in sight. Android die hard users are jumping ship to Apple all over the place due to this problem.
Short answer, if you want working Bluetooth calls on this device, flash an 8.1 Oreo build, then it will work.
Click to expand...
Click to collapse
I suspect the same thing.
I saw phhuson have bounty for GSI bluetooth call issue.
https://github.com/phhusson/treble_experimentations/issues/374
Punch your symptoms into google "android 9 bluetooth call problems" or "android 9 bluetooth car problems" and you'll get hundreds of forum listings with thousands of examples of the same or similar behaviour, usually but not always associated with a stock android device such as any android one handset, or the pixel etc... Some 3rd party builds are also affected, OnePlus and Samsung users are reporting problems.