Database Users

Bluetooth Pairing Not Possible With Car / ROM: cyanogenmod

Hi community,
I'm using my Samsung Galaxy S4 GT-I9505 with the cyanogenmod nightly build 11-20140830-NIGHTLY-jflte.
Works perfect except bluetooth and headset connection with my car.
Connection between S4 and a laptop (win7) works fine.
Car bluetooth is BMW E61 from 10/2006 without any modifications.
Symptoms: S4 and car find each other, PIN/Passphrase is transmitted correctly, car says connection established correctly, S4 says pairing not possible.
If I install build 11-20140724-NIGHTLY-jflte my S4 and car bluetooth works fine.
So what has been changed in the bluetooth development between these two versions?
Anyone with ideas?
Rainer

Got about the same problem with my Peugeot 508. Check the BMW website to see if your radio is compatible with the S4.
Maybe ask your garage for a software update.

Trancicted said:
Got about the same problem with my Peugeot 508. Check the BMW website to see if your radio is compatible with the S4.
Maybe ask your garage for a software update.
Click to expand...
Click to collapse
Thanks for reply, but that's not the solution.
An earlier build (11-20140724-NIGHTLY-jflte) works fine without any necessary updates from BMW.
Rainer.

rainer777 said:
Thanks for reply, but that's not the solution.
An earlier build (11-20140724-NIGHTLY-jflte) works fine without any necessary updates from BMW.
Rainer.
Click to expand...
Click to collapse
Then the problem is related to Cyanogenmod. Revert to a stable option or wait for a new release. Btw, you better report the bug to the developers over there. https://forums.oneplus.net/threads/...ture-requests-improvements-to-cyanogen.41858/

Hi,
I found the solution by myself and the help of cyanogenmod-forum
I deleted cache and data files under settings->apps->->all apps->bluetooth file sharing (I don't know the exact english name for it)
and I also have to use a 6 digit pin instead of a 4 digit pin.
Happy weekend!
Rainer

Hello fellow phone lovers.
Just found out why the Pokemon go plus accessory wouldn't connect to any ROM Ive ever used. Managed to get it to connect on my s4 with resurrection remix 6.0.1 ROM... You need to enable smart lock and add Bluetooth as a trusted device for it to connect properly
Your welcome.

Also forgot to add I'm using magisk v6 systemless and I had to make sure in super su that
*Enable su is ticked
*Enable su during boot is ticked
*Mount namespace separation is un-ticked ! (Main reason for not connecting)
*Trust system user is ticked
Pokemon plus Bluetooth device works flawlessly and connects as fast as it should where as before all this it would either, take ages to connect or not connect at all.

Bluetooth issue on connecting with rk3188 HU(KGL) using Android 6.0 or higher

Hi everyone,
i got a problem connecting my Android device to my rk3188 HU via Bluetooth.
My devices:
Google Nexus 5 : Android version - 6.0.1 cyanogenMod
rk3188: Android Version - 4.4.4 Malaysk rom(newest)
Display - 1024x600
To my problem: i can pair my phone to the hu. No problem, but when i want to connect my phone to the rk3188 device it says, that it is connected but telephon is not possible. After that it disconnects itself. The connection breaks up. I tested it on several devices with different Android Version like 4.4.2 and 5.1.1 and it works just like it should. Seems like its an Android 6.0 and higher problem. Is there somebody with the same problem and know how to solve this?
Thank you!

Hi,
i can´t help, but i have similar problems...
My Devices:
LG G4 (Andoid 6.0)
Erisin ES2046B (rk3188 / 1024x600 / newest Malaysk Rom 4.4.4)
I can pair my Android phone to the HU, but when i try to sync my contact list it breaks up the connection.
I tested several MTCBlueTooth.apk (by Malaysk and other) but still the same problem.
I also changed the way of sync in the phone contact list options and tried to send the contacts manually,
but nothing really works.
I also tested another phone (Samsung Galaxy Note 3) a few months ago and it worked like a charm.
Now after an update to Android 6 it seems like the same problem like yours, its still paired but it randomly
breaks the connection.
I´m still holding out hope for a solution and thanks for reading...

Kuba791 said:
To my problem: i can pair my phone to the hu. No problem, but when i want to connect my phone to the rk3188 device it says, that it is connected but telephon is not possible. After that it disconnects itself. The connection breaks up. I tested it on several devices with different Android Version like 4.4.2 and 5.1.1 and it works just like it should. Seems like its an Android 6.0 and higher problem. Is there somebody with the same problem and know how to solve this?
Thank you!
Click to expand...
Click to collapse
Hi,
I have experienced the same issue with CM13 on N7100 and i9506. Appears to be a CM13 issue - perhaps post logcats on CM forums?
-M

marchnz said:
Hi,
I have experienced the same issue with CM13 on N7100 and i9506. Appears to be a CM13 issue - perhaps post logcats on CM forums?
-M
Click to expand...
Click to collapse
i don't know, i still think that it is an android 6.0+ issue. A friend of mine has a android m stock rom and it appears the same problem.

I have an LG G4 6.0 and it works fine with my Joying rk3188. But to be honest I haven't done more than make sure I can stream music and test out the hands free calling features.

I thought I was the only one!....I got a Lenovo zuk z1 with android 6.0.1 and the same problem.....you even can listen to the streaming music through you android car radio, but nothing about calls,.It seems can't synchronize with your contacts.Any help?

My Huawei Mate 8 with Android 6.0 connect perfectly via Bluetooth (phone calls, contacts, music) to my Eonon RK3188 4.4.4.

To all of you who don't have any issues with Bluetooth connection, which Rom have you installed on your HU?

G2110F stock rooted.

Still running the stock ROM it came with. Will give the ROM number next time I get in my car.
Sent from my Nexus 7 using Tapatalk

I can't make any promises, but I'm willing to look into logs from your phones (especially CM13 devices) as I have the same issue. Phone shows up as "Connected (no phone)" and Bluetooth media works fine. Grab a logcat or a bug report and attach or post on pastebin.com and I'll see what I can find.
Sent from my SM-N910P using Tapatalk

Pardon my ignorance here (still learning) but nothing in the "About machine" is labeled as the ROM so I will list the following:
MCU - MTCB-JY-V2.73
Android version - 4.4.4_25082015
Kernel version - 3.0.36+
Build number - rk3188-eng4.4.4.25082015.12:15:58
One thing I did notice when I was pairing my G4 was that the HU was trying to control the pairing where as every other Bluetooth pairing was controlled by the phone. I stopped the HU and used my phone to control the pairing. And I did confirm that all features work properly. I loaded up my directory, controlled music, etc all from my HU.
Sent from my Nexus 7 using Tapatalk

i solved this problem flashing cm12.1 (android 5.1.1) back to my nexus 5. Now everything ist working like it should. I'm little upset to downgrade, because some features are missing which were very important to me. @nivron: i try to find some time to flash to cm13 again and get the logs. After that i will try to post it here or on pastebin.com or both.

nivron said:
Grab a logcat or a bug report and attach or post on pastebin.com and I'll see what I can find.
Click to expand...
Click to collapse
Hi! I have same problems with connecting my OnePlus One (CM13) to HU (RK3188, Android 4.4.4).
I grab logs as you ask. Attached logs represent new connection attempt - I remove all devices and run search. I prepared both log from my phone and HU.
Thanks!

Bodun said:
Hi! I have same problems with connecting my OnePlus One (CM13) to HU (RK3188, Android 4.4.4).
I grab logs as you ask. Attached logs represent new connection attempt - I remove all devices and run search. I prepared both log from my phone and HU.
Thanks!
Click to expand...
Click to collapse
Problem is fixed with latest cm13 nightly... But be aware of the launcher problem! So I would suggest to wait one day! Launcher fix is already added but not in a build!
Cheers

gismo2004 said:
Problem is fixed with latest cm13 nightly... But be aware of the launcher problem! So I would suggest to wait one day! Launcher fix is already added but not in a build!
Cheers
Click to expand...
Click to collapse
It's just a great news! I'd like to thank you for info and great job!

which CM13 will fix the problem? I under 28 and same...

gismo2004 said:
Problem is fixed with latest cm13 nightly...
Cheers
Click to expand...
Click to collapse
I confirm - now BT paired as expected.
Checked on cm-13.0-20160501.
Thanks!

What about those of us not running cyanogen? I have a Nextbit Robin and its bluetooth functionality is heavily impaired thanks to the changes in android marshmallow.
Is there any fix or app to downgrade the bluetooth protocol or something?

Same issue since Marshmallow update
Hi
I have a rooted RK3066 4.4.4 unit and and Xperia M5. Since the Marshmallow update on my M5 i can no longer connect my phone to my headunit. I pairs fine but just connects the reconnects. Has anybody found a solution to this problem?

Nexus 6P and Mini Cooper S

Hi friends!
I used to be on Dirty Unicorn and ElementalX kernel. I was able to pair the bluetooth with my mini cooper so that I am able to make calls or answer calls in my car handsfree.
Today i decided to flash Paranoid Android. I did a clean flash by wiping everything except internal storage, followed by flashing PA, then supersu, then elementalx. When i went for a drive later at night, I realised that my bluetooth was unable to pair with Mini. It was able to find the Mini in the bluetooth list, but clicking on it it will say pairing and then it stopped, as if i have never clicked on pairing. Repeated attempts gives same result. I am just unable to pair with my Mini cooper.
Is there anyway I can make it pair? Was it my bluetooth driver or something (which i highly doubt). Im on the latest June security update, it was also working with the latest june security update before.
Although im not hopeful that this problem could be solved, just wanna try my luck and see if there happen to be any mini cooper owner or anyone who understands and can offer me advise. Thanks!

sp0rky said:
Hi friends!
I used to be on Dirty Unicorn and ElementalX kernel. I was able to pair the bluetooth with my mini cooper so that I am able to make calls or answer calls in my car handsfree.
Today i decided to flash Paranoid Android. I did a clean flash by wiping everything except internal storage, followed by flashing PA, then supersu, then elementalx. When i went for a drive later at night, I realised that my bluetooth was unable to pair with Mini. It was able to find the Mini in the bluetooth list, but clicking on it it will say pairing and then it stopped, as if i have never clicked on pairing. Repeated attempts gives same result. I am just unable to pair with my Mini cooper.
Is there anyway I can make it pair? Was it my bluetooth driver or something (which i highly doubt). Im on the latest June security update, it was also working with the latest june security update before.
Although im not hopeful that this problem could be solved, just wanna try my luck and see if there happen to be any mini cooper owner or anyone who understands and can offer me advise. Thanks!
Click to expand...
Click to collapse
If I had a guess it's PA is only early development for them so that could be it

jaythenut said:
If I had a guess it's PA is only early development for them so that could be it
Click to expand...
Click to collapse
oh well...

sp0rky said:
Hi friends!
I used to be on Dirty Unicorn and ElementalX kernel. I was able to pair the bluetooth with my mini cooper so that I am able to make calls or answer calls in my car handsfree.
Today i decided to flash Paranoid Android. I did a clean flash by wiping everything except internal storage, followed by flashing PA, then supersu, then elementalx. When i went for a drive later at night, I realised that my bluetooth was unable to pair with Mini. It was able to find the Mini in the bluetooth list, but clicking on it it will say pairing and then it stopped, as if i have never clicked on pairing. Repeated attempts gives same result. I am just unable to pair with my Mini cooper.
Is there anyway I can make it pair? Was it my bluetooth driver or something (which i highly doubt). Im on the latest June security update, it was also working with the latest june security update before.
Although im not hopeful that this problem could be solved, just wanna try my luck and see if there happen to be any mini cooper owner or anyone who understands and can offer me advise. Thanks!
Click to expand...
Click to collapse
I had a similar issue with mine, but I were able to make it pair from my car(making the pairing request from my multimedia) and not from the phone.

zopostyle said:
I had a similar issue with mine, but I were able to make it pair from my car(making the pairing request from my multimedia) and not from the phone.
Click to expand...
Click to collapse
I only have AUX and USB under my multimedia option in mini visual boost... i think i gonna flash back to Dirty Unicorn

Nougat 7.1.2 Bluetooth issues

I just dirty flashed Resurrection Remix 5.8.3 ROM on top of 7.1.2 and so far it has been great except, when I connect the Bluetooth in my car it shows up as connected (no phone) on my phone. Audio streaming works but when trying to make a call it says there's no phone connected. I tried the trial version of Bluetooth Phonebook but when I connect the phone with the app installed it does the same thing, anyone knows any fixes?

Hi, can't say about your problem since didn't test any 7.1.2 yet.
But I would like to ask you if it has been solved the drops of network signal when pairing bluetooth on Nougat ROMs before stabilizing? (and sometimes rebooting). Thank you

To fix this problem this is the solution.
but you should know, bluetooth with 7.1.2 is not stable. .
Enable root , open file manager and open the /system/etc/init.qcom.bt.sh and edit the following lines:
Setprop ro.bluetooth.hfp.ver 1
... To:
Setprop ro.bluetooth.hfp.ver 1.5
Click to expand...
Click to collapse

MAJED.y said:
To fix this problem this is the solution.
but you should know, bluetooth with 7.1.2 is not stable. .
Click to expand...
Click to collapse
Hi,
i have a another problem with bluetooth. I'm on RR 5.8.3 from 07.05.17 unofficial, i did clean install over firmware oos 3.5.8. I can connect with bluetooth to my car and make calls and hear music, but it dont show the name from the Song on the display from my car.
Bevor that i was on RR Marshmallow rom and there working everything.
Hope you can help me, do you know a solution?
Thanks

Bluetooth call issues with every AOSP rom

Hello everyone,
Sorry if this is obvious or a known bug but i've searched through a dozen of AOSP threads and found nothing satisfying.
So here's the story :
- I have clean flashed LineageOS 14.1 official 20180110 a week ago but i have those distorted voices when called over any bluetooth device (tried car and BT Speaker). On their thread someone says that it actually has been fixed in 20180103 build but the problem is still present though we're already one build ahead since then.
- Anyway, I decided to change my rom and try out AOKP. I clean flashed it today. Working fine, except for that exact same bug.
- Tried AOSPExtended, same thing.
So do all AOSP roms have this bug? I can't believe it since apart from 1 or 2 posts in Lineage's thread nobody seems to care in any AOSP rom.
If (and i hope so) the answer is no : could a kind soul show me some good AOSP rom without this problem?
Thanks for caring

Same for me on Galaxy S7 (herolte G930F).
Tried newest LineageOS and AOKP - directly after setup. No other changes made. Music over bluetooth works as expected. Phone calls imposible.
I found a Video here which shows exactly what happens:
Google: "s7 edge lineageos bluetooth Youtube":
https://www.youtube.com/watch?v=utDsXrCY5N0
Also some other People seem to have the same problems. See other thread (Post #1999):
https://forum.xda-developers.com/ga...ial-lineageos-14-1-galaxy-s7-t3529197/page200

Thanks for the infos !
I didn't see the post 1999 is LOS thread, seems like the build.prop is a good fix but unfortunately it doesn't work on latest LOS build.
Will try on AOSPExtended with the same editing on audio_hal property.
EDIT : Works on AOSPExtended ! Didn't try AOKP yet

Hi can you please explain how did you fix this ? happen exactly the same for me, thanx