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.

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

update bluetooth share with 7.1.2 one

Hello, I am currently running B04 (N 7.1.1) and I have issues with in car Bluetooth... according to google, these pb could be fixed with 7.1.2 version of Nougat... I downloaded the 7.1.2 APK of Bluetooth share component but do you think I can update if, not rooted?

wrong section why it's not in Q&A .....
any reason.........................................

well it's related to the ROM as there is currently no plan to deliver 7.1.2 official ROM and my bug is known with all Nougat ROMs... but I wondered where to post this...

What is the issue you are having. I have been having some wierd behavior in different roms when it comes to connecting with my car and can't pin it down.
Sent from my ZTE A2017U using Tapatalk

well I can pair, but in/out calls don't use the speakers and if I switch off the bt on the phone, it remains connected according to the car...

no idea to solve my problem? ;(

Road to a working Bluetooth OBD2 on MTCD PX5

The title is self-explaining: I know it can be done, cause i once had a working setup on my device.
Problem is i can't get it to work again anymore after some firmware flashes and MCU updates.
I did a lot of research, read a huge amount of posts and tried several solutions which did work for other people.
Maybe some people find it stubborn, some say i can't be done period, but the fact that i had it working once is eating me up
There are a lot of posts about this, most of them in threads about MCU, firmware, custom-ROMS's etcetera so not easy to find for everyone.
At the same time some threads are couple of thousands of posts and very hard to read through.
I hope to get all the useful information bundled somehow and work towards a final solution....! :fingers-crossed:
I'll start of with my devices and what i can and cannot accomplish.
Hopefully some folks out there have a working setup, please share information like what Firmware, MCU, OBD2-device and so on.
Post #2 is where I want to sum up solutions i found so far that could do the job for those with similar problems
Post #3 Hopefully is growing with working and proven setups.
Okay, my setup:
Head Unit: GS 7.1
MCU: MTCE GS 2.72
Bluetooth Module: SD-968
ROM: Malasyk 6.2
(Seller: Xtrons, sold as TB706APL)
OBD2: Scantool OBDLink LX, firmware 4.3.0
BT-name: OBDLink LX (sometimes recognized as 4OBDLink LX)
PIN: 1234 (should work with this device but if i pair with phone it is a changing 6-digit code
It's a work in progress so far from complete, i will try to gather all useful information so it can be a good starting point for others too.
Topic is for the time being only about MTCD PX5 in combination with Bluetooth to get it sort of clean and readable.
So....have a suggestion that can help us solve it for once and for all??? Let us know!!!
Cheers
My Personal Progress
I can see my OBD2 device from Bluetooth-app, but pairing does not work.
I can find same device with my phone and pair, no problem
When i use RealDash it asks for permission to Enable Bluetooth which i grant, after that it freezes. The problem seems to me that external apps (Torque, Realdash etc) are not able to 'use' Bluetooth module.
I have read that only the MCU can access the Bluetooth-module

Possible Solutions, Fixes, Tips
. Revert to factory ROM
. Physical disconnect Head Unit from power (after flashing firmware), attach again, boot and try to pair
. Use Graser's Dasaita Tool and add the BT-name of your OBDscanner to the Whitelist, reboot
. Always use BT-app instead of Setting>Bluetooth>Pair
. Delete all other pairings and shutdown all other BT-devices except for HU and OBD-scanner. If possible start with fresh ROM
. Use a modified Torque.apk from older Joying ROM and use that for first BT-Connection instead of BT-app (i still think i used that when i managed to get it going so i keep that APK safe
.
.
.
Under Investigation[/U (I did not try this yet)]:
. You need rooted phone, then delete any paired phone then pair it with obdii and you need to copy that folder in /data/misc/bluetoothd/macaddress to your PC and you need to copy the same folder from your car HU and then combine them in your PC and push it back to HU and owner after pushing it should be Bluetooth
>> Did not work for me cause there is no 'bluetoothd' folder in /data/misc/ or somewhere else in root folder
>> There is an app called Pairs that can backup and restore your Bluetooth settings, i asked the maker if he could share where the config file can be found but i got no answer (few weeks after PM now)

Working Setups (Confirmed by users)
Obd2 device: vgate icar3
Pin: 1234
Discovery name: VLINK
Headunit: Dasaita v600 series for Mazda cx5
Rom: latest stock Rom from Nov. 2017
Bluetooth Module: ?
MCU version: ?
_____________
Obd2 device: ELM 327
Pin: 1234
Discovery name: OBDII
Headunit: px5 MTCE_MX2- All in one w/Android 6.0.1 for Kia Cee'd 2011
Rom: latest stock Rom from 19/12/2017
Bluetooth Module: SD-968
MCU version: MTCE_MX2_V2.275_1 - Dec. 19 2017
____________
Obd2 device: Scantool OBDLink LX
Pin: 1234
Discovery name: OBDLink LX
Headunit: px5 MTCE sold as Xtrons TB706apl
Rom: px5-userdebug 6.01 MXC89L user.hct.20171023.175918 test-keys (STOCK)
Bluetooth Module: SD-968
MCU version: MTCE_GS_V2.70_1 - Oct 22 2017

Usefull Links

ZeroZorro said:
The title is self-explaining: I know it can be done, cause i once had a working setup on my device.
Problem is i can't get it to work again anymore after some firmware flashes and MCU updates.
I did a lot of research, read a huge amount of posts and tried several solutions which did work for other people.
Maybe some people find it stubborn, some say i can't be done period, but the fact that i had it working once is eating me up
There are a lot of posts about this, most of them in threads about MCU, firmware, custom-ROMS's etcetera so not easy to find for everyone.
At the same time some threads are couple of thousands of posts and very hard to read through.
I hope to get all the useful information bundled somehow and work towards a final solution....! :fingers-crossed:
I'll start of with my devices and what i can and cannot accomplish.
Hopefully some folks out there have a working setup, please share information like what Firmware, MCU, OBD2-device and so on.
Post #2 is where I want to sum up solutions i found so far that could do the job for those with similar problems
Post #3 Hopefully is growing with working and proven setups.
Okay, my setup:
Head Unit: GS 7.1
MCU: MTCE GS 2.72
ROM: Malasyk 6.2
(Seller: Xtrons, sold as TB706APL)
OBD2: Scantool OBDLink LX, firmware 4.3.0
It's a work in progress so far from complete, i will try to gather all useful information so it can be a good starting point for others too.
Topic is for the time being only about MTCD PX5 in combination with Bluetooth to get it sort of clean and readable.
So....have a suggestion that can help us solve it for once and for all??? Let us know!!!
Cheers
Click to expand...
Click to collapse
Need more data:
Discovering name for your obd2 bt device
Pin number for pairing
Enviado desde mi SM-G950F mediante Tapatalk

ikerg said:
Need more data:
Discovering name for your obd2 bt device
Pin number for pairing
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
Okay, added to OP

Revert to factory ROM.

marchnz said:
Revert to factory ROM.
Click to expand...
Click to collapse
Of course, did try that, several kinds. Started with the one i got when purchasing device and newer ones up untill the latest.

ZeroZorro said:
Okay, added to OP
Click to expand...
Click to collapse
In my case:
Obd2 device: vgate icar3
Pin: 1234
Discovery name: VLINK
Headunit: Dasaita v600 series for Mazda cx5
Rom: latest stock Rom from November
I used to have it working by using graser's app but I now realized that it works as stock (I have to double check this)
Enviado desde mi SM-G950F mediante Tapatalk

ikerg said:
In my case:
Obd2 device: vgate icar3
Pin: 1234
Discovery name: VLINK
Headunit: Dasaita v600 series for Mazda cx5
Rom: latest stock Rom from November
I used to have it working by using graser's app but I now realized that it works as stock (I have to double check this)
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
Thanks, would you mind sharing how you paired those in the first place?
I believe in there we could find the main issue (aside from maybe having trouble to use/call it after pairing by some apps)
Also the Bluetooth module is worth mentioning, i read several solutions, but some does not fit all modules....
I'll add this combo to the list once you have double checked and confirmed!

ikerg said:
In my case:
Obd2 device: vgate icar3
Pin: 1234
Discovery name: VLINK
Headunit: Dasaita v600 series for Mazda cx5
Rom: latest stock Rom from November
I used to have it working by using graser's app but I now realized that it works as stock (I have to double check this)
Click to expand...
Click to collapse
That's my experience too - I have a generic 'odb-2', and the October HA PX5 works without any modification.
Initially I couldn't pair, but after proper reboot, it paired witout issue and handfree with my phone at same time.
You could try disconnecting unit from power first.

I'm having a similar issue... I currently have a XTRONS pb65wrjp (PX5, android 6.0, MTCE, custom fit for Jeep) running stock, and a bluetooth OBD2 adapter that I also purchased from XTRONS. The HU recognizes it fine and the pre-installed Torque app works fine with it. However, I would prefer to use DashCommand. DashCommand tells me that bluetooth is turned off and tries to turn it on, but then freezes. I also tried a USB OBD2 adapter and that isn't recognized by DashCommand either. Very aggrivating.

Well, i am afraid that most problems are hardware related somehow. I ended up sending back my TB706APL and received a refurbished one a week later.
Of course i couldn't resist and upgraded from Android 6.0.1 (20171023) to Android 8.0 (20180118) with no problems.
The only thing i changed after upgrade was the PIN-code (from 0000 to 1234) and opened the blue BT-app from the home-screen (I turned off the BT on my smartphone first).
Then i remembered that OBDLink LX was easier to detect when it was fresh-on and indeed. After a couple of hours (i went working) i got back in the car, started it all up. Pushed the pair button on the OBDLink LX, opened the app and tapped the Search icon. This time it worked in 3 seconds, paired automatically! #Yeah!!!
Also i turned off my car a couple of times and it auto-reconnects, no issues so far...
Bottom line... i can't test any more cause i am too afraid i will break things. First thing i am gonna do now is backup the complete setup and just to be sure also the Bluetooth pairing i finally managed to make!

ZeroZorro said:
Working Setups (Confirmed by users)
Obd2 device: vgate icar3
Pin: 1234
Discovery name: VLINK
Headunit: Dasaita v600 series for Mazda cx5
Rom: latest stock Rom from Nov. 2017
Bluetooth Module: ?
MCU version: ?
Click to expand...
Click to collapse
Another working setup
Obd2 device: ELM 327
Pin: 1234
Discovery name: OBDII
Headunit: px5 MTCE_MX2- All in one w/Android 6.0.1 for Kia Cee'd 2011
Rom: latest stock Rom from 19/12/2017
Bluetooth Module: i think it's a SD-968
MCU version: MTCE_MX2_V2.275_1 - Dec. 19 2017
BUT WHAT I REALLY WANT TO WORK IS FOR Scantool OBDLink LX :crying:

pauloroxa said:
BUT WHAT I REALLY WANT TO WORK IS FOR Scantool OBDLink LX :crying:
Click to expand...
Click to collapse
Thing is that i have my OBDLink LX working now on my PX5 Stock ROM and without any changes except for setting pin to 1234. So no exposed module or anything else needed to got it working.
I am not flashing any other ROM (altough i wish to) afraid as i am loosing my precious BT-pairing...

pauloroxa said:
Bluetooth Module: i think it's a SD-968
Click to expand...
Click to collapse
If you go into Setting>>Factory Setting (pin 126) you can find the BT-module mentioned on the first post (if you did not change that obviously)

ZeroZorro said:
If you go into Setting>>Factory Setting (pin 126) you can find the BT-module mentioned on the first post (if you did not change that obviously)
Click to expand...
Click to collapse
That Pin is general?

pauloroxa said:
That Pin is general?
Click to expand...
Click to collapse
yes, most of the times that is the one working. But there are others too like m123456 that work on some units

ZeroZorro said:
Thing is that i have my OBDLink LX working now on my PX5 Stock ROM and without any changes except for setting pin to 1234. So no exposed module or anything else needed to got it working.
I am not flashing any other ROM (altough i wish to) afraid as i am loosing my precious BT-pairing...
Click to expand...
Click to collapse
I don't think you are going to loose anything...I have been changing Roms at the moment they are being released...and my obd2 device is working everytime...
In my case my bt module is md725
Still on android 6....as I am.waiting for a new coreboard and will try the upgrade on the old coreboard..
Enviado desde mi SM-G950F mediante Tapatalk

ikerg said:
I don't think you are going to loose anything...I have been changing Roms at the moment they are being released...and my obd2 device is working everytime...
In my case my bt module is md725
Still on android 6....as I am.waiting for a new coreboard and will try the upgrade on the old coreboard..
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
I am sure you are right, but i have spent way too much time trying to make it (BT-pairing) work that i first want to figure out how to root this stock ROM. If achieved, i can make a full backup and secure that on at least 3 physical separated locations :cyclops:
Or...if it's rooted i can use Pair, a Bluetooth backup app and i will dive in....

UltraOcta-T8 upgrade to Android 8.1

Hi all
I have a 9" UltraOcta-T8 (I think it is the AllWinner) and it is running Android 7.1.2
Is there an upgrade path to Oreo at all.
Here is a pic of the About screen showing MCU and System version ( for some reason I cannot upload an image)
MCU version: 5.3. 19-63-84-C06101-170705
System Version: V9.2.2_20171013. 154052_TW2-FD
Thanks
Lance

I was hoping you had a solution too, I love the head unit but I think it could be a better experience with 8.0 on it, it's been over a year without a reply on this thread.

dj_hallucn8 said:
I was hoping you had a solution too, I love the head unit but I think it could be a better experience with 8.0 on it, it's been over a year without a reply on this thread.
Click to expand...
Click to collapse
Yes, there is an upgrade path using Phoenix Suite. I upgraded from 7.1 to 8.1 around 2 weeks ago and the head unit now feels snappier and it hasn't crashed yet when using various sat nav apps which it used to sometimes on 7.1. Boot time is slightly faster and I've found it connects via bluetooth to my phone automatically every time I get in the car. Under 7.1 it was quite sporadic.
There is a post on the main T8 Allwinner thread which you will have to look for. You'll need a laptop, Phoenix Suit, 8.1 ROM which is in the post (I've now flashed the JP variant of 8.1 which is stable), Male to Male USB cable to connect laptop to head unit.
The instructions in said post are a little hard to understand, but it only took me about 15 minutes after I'd downloaded the software and ROMs.

Goof757 said:
Yes, there is an upgrade path using Phoenix Suite. I upgraded from 7.1 to 8.1 around 2 weeks ago and the head unit now feels snappier and it hasn't crashed yet when using various sat nav apps which it used to sometimes on 7.1. Boot time is slightly faster and I've found it connects via bluetooth to my phone automatically every time I get in the car. Under 7.1 it was quite sporadic.
There is a post on the main T8 Allwinner thread which you will have to look for. You'll need a laptop, Phoenix Suit, 8.1 ROM which is in the post (I've now flashed the JP variant of 8.1 which is stable), Male to Male USB cable to connect laptop to head unit.
The instructions in said post are a little hard to understand, but it only took me about 15 minutes after I'd downloaded the software and ROMs.
Click to expand...
Click to collapse
Thank you, this got me pointed in the correct direction, only thing I'm worried about is losing BT capability since I read that happens a lot.

some high-tech may support upgrade
most devices can't upgrade from 7 to 8 version. It depends on whether your head unit support upgrade. need to reach out to seller.

dj_hallucn8 said:
Thank you, this got me pointed in the correct direction, only thing I'm worried about is losing BT capability since I read that happens a lot.
Click to expand...
Click to collapse
That was one of my concerns also, I had no issues though. Just make sure you take note of the config in the extra settings. Once you've flashed your final ROM, check the settings are the same and reboot the head unit 3 or 4 times (not sure why, but seen it said a few times).
---------- Post added at 07:13 AM ---------- Previous post was at 07:07 AM ----------
Arkright said:
most devices can't upgrade from 7 to 8 version. It depends on whether your head unit support upgrade. need to reach out to seller.
Click to expand...
Click to collapse
You can upgrade from 7.1 to 81 on the UltraOcta T8 AllWinner devices. It's just a bit of pain as you need to use laptop etc... but once you have everything together it's quick and easy.
The only thing I'm not sure on is the downgrade path (8.1 to 7.1) should you need it. Thankfully I've found 8.1 (v9.3.1_20181109.180710_JP3-FD) to be much more stable than 7.1 (9.2 JP1-FD).

Which thread did you say the instructions were in?
I can't seem to find the thread when i search for allwinner t8 update
dj_hallucn8 said:
Thank you, this got me pointed in the correct direction, only thing I'm worried about is losing BT capability since I read that happens a lot.
Click to expand...
Click to collapse

Can I get some help identifying which image I need ot be using for this? Also is this the latest version?
Note: why the hell do they make this so hard to update?

[email protected] said:
I can't seem to find the thread when i search for allwinner t8 update
Click to expand...
Click to collapse
thegreaterswan said:
Can I get some help identifying which image I need ot be using for this? Also is this the latest version?
Click to expand...
Click to collapse
[SOLVED] How to update Android version (6, 7, 8, 9) on HU with Allwinner T8 (firmware v9.1.1, v9.2.2, v9.3.1, v9.4.1)
How to update Android version (6, 7, 8, 9) on HU with Allwinner T8 (firmware v9.1.1, v9.2.2, v9.3.1, v9.4.1) Attention! You can update Android version only from PC! [/SIZE][/B] [/SPOILER][/SPOILER][/SIZE][/B] On the Car settings screen, select...
forum.xda-developers.com