Related
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?
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
Hello, I bought a Leeco Le Pro 3 X720, and I have a Hyundai car, so I tried to connect to my car to use Android Auto but it doesn't work, with the ROM stock EUI 5.9 only started to charge the cellphone, never started android auto when I connected in the car.
I searched in google and could to read that the ROM stock with MM it doesn't work with AA, so I installed Lineage OS 14.1 (Android 7.1.2), this ROM can initialize AA, but when sync it, after 5 minutes the screen is freeze, yesterday I installed AICP 12.1 with android 7.1.2 (aicp_zl1_n-12.1-NIGHTLY-20171017.zip), but I have the same issue.
I used the original leeco usb cable.
Anybody have the same issue? or anybody could fix this?
Do you know some ROM that supports AA? or some usb cable compatible?
Thank you in advance.
Sorry for my bad english.
dacast91 said:
Hello, I bought a Leeco Le Pro 3 X720, and I have a Hyundai car, so I tried to connect to my car to use Android Auto but it doesn't work, with the ROM stock EUI 5.9 only started to charge the cellphone, never started android auto when I connected in the car.
I searched in google and could to read that the ROM stock with MM it doesn't work with AA, so I installed Lineage OS 14.1 (Android 7.1.2), this ROM can initialize AA, but when sync it, after 5 minutes the screen is freeze, yesterday I installed AICP 12.1 with android 7.1.2 (aicp_zl1_n-12.1-NIGHTLY-20171017.zip), but I have the same issue.
I used the original leeco usb cable.
Anybody have the same issue? or anybody could fix this?
Do you know some ROM that supports AA? or some usb cable compatible?
Thank you in advance.
Sorry for my bad english.
Click to expand...
Click to collapse
I am currently using the stock ROM, it works with Android Auto.
tsongming said:
I am currently using the stock ROM, it works with Android Auto.
Click to expand...
Click to collapse
Can you post your Android version and eui? Please
Do you have an special cable or is the original leeco cable?
Thank you for your response
dacast91 said:
Can you post your Android version and eui? Please
Do you have an special cable or is the original leeco cable?
Thank you for your response
Click to expand...
Click to collapse
No problem, I am still using stock Android 6.0, EUI 5.8.21s. FYI, I don't connect the cable, since my car is not compatible. Sorry to disappoint, but I use Android Auto using just the phone alone, attached to a phone mount. However, I am willing to test with a cable to verify that it works. My brother owns a 2017 compatible vehicle and I can let you know by Saturday afternoon EST.
Have you considered that your issue could be with the cable? I read that the Android Auto Team recommends several different types of cables to resolve similar issues. Such as, Anker USB-C to USB 3.0 Cable
Thank you for your response, yes I think that is the cable, actually I bought 2 cables (no Anker) but aren't working, today I will try with other cable to try fix this issue.
I'm waiting your comments.
Thank you.
Update
dacast91 said:
Thank you for your response, yes I think that is the cable, actually I bought 2 cables (no Anker) but aren't working, today I will try with other cable to try fix this issue.
I'm waiting your comments.
Thank you.
Click to expand...
Click to collapse
Sorry for being late with getting back to you.
I tried using Android Auto with my Le Pro 3 x727 attaching it to my brothers 2017 Chevrolet Equinox. ( Also: I used a 3rd party high quality USB-c cable) and unfortunately it still did not work. However, we called the dealership and found that his Equinox will support Android Auto. But, it requires a dealer installed update ( go figure! ) Next, we were told that the update is simply updating their My-link software so it will support Android Auto.
Regarding your vehicle, I just read on the Hyundai' US website that Hyundai' also require software updates to support Android Auto...so maybe that is the resolution to solve your issue? On the other hand, If you have already updated your Hyundai software. Perhaps, you still need a better cable.
Good Luck!
Thank you very much for your response.
I will ask to Hyundai for the update the next week.
Other test that I did was change the USB cable to a Moto Z1 original cable, and Android auto worked better, sometimes I can use it at least 20 minutes, after that I have the same issue but it's an advance.
If you can do a new test with the update could be great, thank in advance for your time to response.
Other thing, my Hyundai car supports Android auto since I bought it, with my old phone (LG G2) works perfectly, that's why I think that is a issue with Le Pro 3, but an update could be help.
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....
Hello,
I am curious to see if anyone else had or still has this issue and if there is a fix for it.
Devices involved:
Phone - Samsung Galaxy S10 Plus (SM-G975F) Android Version: 10.0 Build Number G975FXXU4CTC9
Watch - Samsung Galaxy Watch 46mm (NO LTE)
Before rooting with Magisk I was able to pair the watch to the phone using the Galaxy Wearable App and use the watch with no problems. (And it still connects with my unrooted Xiaomi mi 9T)
After rooting my s10+ with Magisk (latest stable and also previous version) I was no longer able to pair the watch. It would start out fine by showing a matching passkey on both devices. I accept the code and they would begin to pair. Once the watch displays "Use phone to complete setup" is when the problems presented.
The Galaxy Wearable app will say its pairing the devices but shows nothing and keeps sending a notification saying it sees the watch and asks to connect or cancel. I tap connect and I get a white screen with a spinning circle. After 3-5 seconds the white screen goes away and 3-5 seconds later I am asked to connect the watch again.
If I go to Settings>Connections>Bluetooth (on the phone) I can see the watch is paired but the app will not complete setup. (I can pair to my car Bluetooth and JBL Xtreme speaker with no problems)
I am using Magisk Hide on the Galaxy Watch Plugin, Galaxy Wearable App, and Samsung Accessory Service but that hasn't helped. Nor does uninstalling and reinstalling Galaxy Wearable App.
Any thoughts?
Please help me, im messing around with this crap since 4 days. (I restored the phone about 20 times with odin an retryed again and again)
Could it be related to tripping knox through rooting (i.e. then some of the Samsung apps will not work e.g. Samsung Health)? I am unable to register S.Health and Wearable (on my rooted S7 edge) will not work.
However, working fine on non-rooted S10+.
Does this help?
https://forum.xda-developers.com/galaxy-s10/how-to/guide-samsung-health-knox-0x1non-root-t4075853
Boot into TWRP and flash @ianmacd's multidisabler
I have the same issue with not rooted s10+ and gear s3
Xenenon said:
Hello,
Exactly Same problem!!!!!
Stuck badly!!!
Any solution!!!!
Ahmed
Click to expand...
Click to collapse
xBrownieCodez said:
Boot into TWRP and flash @ianmacd's multidisabler
Click to expand...
Click to collapse
I did but the problem remains the same!!!
My Galaxy S3 Frontier works fine on Stock rooted + Lineage OS 17.1 .
there is a mgaisk module you can try called "Bluetooth Libary Patcher". Find it in Magisk -- Downloads -- and search for it there (just type bluetooth in search panel on top)
as i said, my watch works as it should.
and for Samsung helath: if youre rooted you just have to add one line in build.prop: ro.config.tima=1
lladwein said:
My Galaxy S3 Frontier works fine on Stock rooted + Lineage OS 17.1 .
there is a mgaisk module you can try called "Bluetooth Libary Patcher". Find it in Magisk -- Downloads -- and search for it there (just type bluetooth in search panel on top)
as i said, my watch works as it should.
and for Samsung helath: if youre rooted you just have to add one line in build.prop: ro.config.tima=1
Click to expand...
Click to collapse
oops! It did not work on mine S10+
Getting frustrated day by day!
I think the era of Rooted Devices is over!!!!!
Xenenon said:
Hello,
I am curious to see if anyone else had or still has this issue and if there is a fix for it.
Devices involved:
Phone - Samsung Galaxy S10 Plus (SM-G975F) Android Version: 10.0 Build Number G975FXXU4CTC9
Watch - Samsung Galaxy Watch 46mm (NO LTE)
Before rooting with Magisk I was able to pair the watch to the phone using the Galaxy Wearable App and use the watch with no problems. (And it still connects with my unrooted Xiaomi mi 9T)
After rooting my s10+ with Magisk (latest stable and also previous version) I was no longer able to pair the watch. It would start out fine by showing a matching passkey on both devices. I accept the code and they would begin to pair. Once the watch displays "Use phone to complete setup" is when the problems presented.
The Galaxy Wearable app will say its pairing the devices but shows nothing and keeps sending a notification saying it sees the watch and asks to connect or cancel. I tap connect and I get a white screen with a spinning circle. After 3-5 seconds the white screen goes away and 3-5 seconds later I am asked to connect the watch again.
If I go to Settings>Connections>Bluetooth (on the phone) I can see the watch is paired but the app will not complete setup. (I can pair to my car Bluetooth and JBL Xtreme speaker with no problems)
I am using Magisk Hide on the Galaxy Watch Plugin, Galaxy Wearable App, and Samsung Accessory Service but that hasn't helped. Nor does uninstalling and reinstalling Galaxy Wearable App.
Any thoughts?
Please help me, im messing around with this crap since 4 days. (I restored the phone about 20 times with odin an retryed again and again)
Click to expand...
Click to collapse
Anything you figure out!
Please do share with me!!!!
I flashed Beyonde Rom 6.7 it comes based on the latest April Patch.
This fixed all my problems
No Bugs yet with this rom
https://forum.xda-developers.com/ga...pment-exynos/rom-beyondrom-v6-0-t4017921/amp/
Flash with TWRP
Health works
Bcs of magisk all my banking works fine (Sparkasse germany)
I LOVE IT
GeekSiddiqi said:
Anything you figure out!
Please do share with me!!!!
Click to expand...
Click to collapse
Beyone Rom 6.7
If you have questions better go to reddit and ask for help
XDA is dead
any update on this issue ?
Xenenon said:
Beyone Rom 6.7
If you have questions better go to reddit and ask for help
XDA is dead
Click to expand...
Click to collapse
But do you lose the Samsung stock camera with this Rom? I have the same exact problem as you. When I was running the Evolution X custom Rom I could connect. But I wasn't happy with the camera that Rom provided. The stock camera on this phone is so amazing and one of the main reasons I bought the phone. I feel cheated when I have to give that up
nasheednashy said:
any update on this issue ?
Click to expand...
Click to collapse
I was having the exact same issue. I just activated magisk hide. And also installed the magisk module, Bluetooth library patcher. Now mine paired up first try. Not sure which helped or if it was a combination of both. But I'm paired up now.
Having same issue too. Tried changing props, tried multi disabler. Tried editing rules.
Now the app can enter but watch not connected
synite said:
Having same issue too. Tried changing props, tried multi disabler. Tried editing rules.
Now the app can enter but watch not connected
Click to expand...
Click to collapse
Did you found a way to connect them?
Inviato dal mio Pixel 3 utilizzando Tapatalk
Hi! Given a Samsung Galaxy Watch Active 2 (LTE) watch and a rooted Galaxy S10 (Android Q). Bluetooth pairing starts but does not end. Two Magisk modules id have been installed but I can't pair them. Is there anything you can bring together? So much for all the stupidity to read, but no answer or stupidity throughout. I can't install Viper4android on the same phone under Android 10. Magisk 21.4, but the 2.7 Viper doesn’t go up. It is installed by plugin, but not among applications. Can these be solved somehow? There was no problem under Android 9. Unfortunately, for the latest Android Q version, XEH version November 27, 2020, TWRP is not trable either. I download the right version, with Magisk, I boot into the AP with Odin, then start button, and odin closes immediately. Nothing goes on this ****ty Android Q. I am waiting for help together or separately! Thanks!
Any update on this issue?
I have problem pairing my Galaxy S21 Ultra and Galaxy Watch Active 2.
No pairing issues before rooting (stock firmware). After rooting using both stable Magisk V22 and Canary 22005, it stuck on Finalizing Pairing screen. I also noticed that the Bluetooth and Samsung accessory icons briefly shown on the notification bar (appear part of the screen) and then disappear.
I hope someone has solution to this.