yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] ZeroZorro:
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 :eek:

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
[Android Head-Units] ZeroZorro:
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)
[Android Head-Units] ZeroZorro:
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
[Android Head-Units] ZeroZorro:
Usefull Links
[Android Head-Units] ikerg:
Need more data:

Discovering name for your obd2 bt device

Pin number for pairing

Enviado desde mi SM-G950F mediante Tapatalk
[Android Head-Units] ZeroZorro:
Okay, added to OP
[Android Head-Units] marchnz:
Revert to factory ROM.
[Android Head-Units] ZeroZorro:
Of course, did try that, several kinds. Started with the one i got when purchasing device and newer ones up untill the latest.
[Android Head-Units] ikerg:
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
[Android Head-Units] ZeroZorro:
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!
[Android Head-Units] marchnz:
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.
[Android Head-Units] mr_et2:
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.
[Android Head-Units] ZeroZorro:
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!
[Android Head-Units] pauloroxa:
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:
[Android Head-Units] ZeroZorro:
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...
[Android Head-Units] ZeroZorro:
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)
[Android Head-Units] pauloroxa:
That Pin is general?
[Android Head-Units] ZeroZorro:
yes, most of the times that is the one working. But there are others too like m123456 that work on some units
[Android Head-Units] ikerg:
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
[Android Head-Units] ZeroZorro:
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....
[Android Head-Units] pauloroxa:
Hi to all, news from BTooth issue with OBDLink LX...

Yesterday i enter in my Factory settings (pin 126) and change the BTooth module from the stocked working SD968 to WQ_BC5 , then i click button on OBD reader to be discoverable and open the BTooth app...it cames out identified and discover 7OBDLink LX with OBD symbol not the phone symbol and changes the device number 3000............

yeah...I give a jump from the seat :)...

NO, it doesn't work, still don't get paired :( i tried several times, with several codes and several names...NO LUCK

Note: with BC5 BT module can't pair anything nor my smartphone.

As anyone knows what might this be ? what it means?

[IMG="7obdlink lx"]https://s7.postimg.org/44wgtxgt7/7obdlink_lx.jpg[/IMG]
[Android Head-Units] pauloroxa:
Hi zorro

Now your working setup for OBDLink LX is running on 8.0 Oreo rom ?

---------- Post added at 03:16 PM ---------- Previous post was at 03:09 PM ----------

I can´t understand this, i have the same Head Unit px5 MTCE, the same Rom and the same SD-968 BT module, only difference is sold by Witson firmware MX 2.

BUT STILL DON'T GET PAIRED

---------- Post added at 03:20 PM ---------- Previous post was at 03:16 PM ----------

Hi ikerg

your VGate icar3 performs well ?

Did you notest that sometimes faulty connection between devices or too much lag on transmission information ?
[Android Head-Units] ZeroZorro:
I didn't upgrade to 8.0 oreo yet, too many unsolved bugs and i don't want to loose working setup yet. Will try it only if manage to get it rooted so i can perform a full backup from TWRP

In my case the first HU with exactly same spec AND same vendor didn't work too. I sent it back and received a refurbished one. That did work, but don't ask me why...:confused:
[Android Head-Units] soyoscar:
Hi [MENTION=1369996]ZeroZorro[/MENTION] Do you have news about ODB2 conectors in PX5 Android 8.0?

Regards: Óscar
[Android Head-Units] ZeroZorro:
Not yet, still making my mind up if i should upgrade to Oreo (Stock or Malaysk) at all....

Although i want to i think it's maybe a little early...but i will dive in soon!
[Android Head-Units] Trefford:
No Bluetooth anymore

After updating software and Mcu i dont have Bluetooth on my px5 device anymore. I use now hal9k mod 3.0 and it is still not working. Can anyone help me to fix it. Thanks.
[Android Head-Units] ZeroZorro:
You have to restore the MCU.cfg you have made before updating to remain the same settings. Otherwise you could select the right module in Factory Settings to enable Bluetooth again
[Android Head-Units] ZeroZorro:
Last week i finally updated from Android 6.0 Stock to Android 8 Stock ROM and I can confirm that Bluetooth is still able to connect with my OBDLink LX

Of course I had to pair again so I was holding my breath...but it still works ;)
[Android Head-Units] TT_Vert:
have that torque apk handy? My HAL9K rom does not have the apk in oem and I don't really want to download/extract from a joying ROM if i can avoid it.

Thanks

Dave
[Android Head-Units] ZeroZorro:
I will have a look if I can find it ..
[Android Head-Units] TT_Vert:
Thanks I ended up just downloading a joying ROM and extracting it.

Dave
[Android Head-Units] ttoton:
Here is very simple solution to make my OBD II device work on MTCE PX5 Android 8.0 device with BC6 bluetooth module:

1) I connected OBD to my smartphone first, to check its PIN code, turned out to be 1234.

2) Disconnect smartphone from headunit by simply turning off Bluetooth in phone.

3) Changing the PIN in the Bluetooth app from factory 0000 to 1234

4) Refresh devices and connect (in Bluetooth app)

5) In Torque Options - OBD devices - pick the paired OBD (it only showed MAC address, not its name), disabled the "Try fast connection" option.

6) Rebooted the device (just in case, it did work without reboot, but I have impression the connection was faster after one).

Hope this helps someone.

Cheers!
[Android Head-Units] sattech200:
Hi Everyone,

I just received my replacement OBD adapter the other day after being down for a year. I came across this post looking for something else and thought I should get this setup, didn't realize there might be issues with it. My hardware might be a little different then what's addressed in this post and I apologise for that. Since it's working successfully I thought I would post it here in case it might help anyone. If anyone needs to know anything specific I'll be more then happy to try and help. Just send a msg or leave a post here.

Machine status:

Author Firmware:

Maley

Model: px3 (1024x600 S)

Android Version: 7.1.2

Build number:

px3-Malaysk 7.1.2 NHG47L eng.hct.2018.02.06.132152 test-keys

MCU Version:

MTCD_ZYC_V2.55_1

June 23 2017 13:46:58

Bluetooth Device:

OBDLink MX+

Firmware Version: 4.5.15 (Was updated yesterday to the latest.)

Apps:

OBDLink

Version: 5.0.0 (Downloaded an hour ago.)

Torque Pro: (was downloaded from 3rd party on internet.)

Application Version:

1.8.205

I rooted it following a guide here if I remember correctly. Everything seems to be functional although I do notice/have a lag in response whenever I try to do something. I would like to tweek the setup a lot more but for now everything seems to be working. (Feel free to share any info/tweeks/etc on this head unit.)

So after installing Torque I couldn't get the units to connect. I then downloaded and installed Torque Pro but it was unable to connect.

Basically all I ended up doing was:

1) power cycled both OBD adapter and head unit.

2) Set adaptor to discovery mode (pressing button on device for a second.)

3) opened up the BlueTooth app where it was listed. I tried to connect but no-go.

4)Went into settings of obd app and changed the password to 1234

Back to devices and the OBDLink was listed and was able to connect successfully.

Launched both OBD apps and they were able to connect instantly....overall was a pretty easy and painless setup.

Again, if anyone has any questions or needs any specific info feel free to shoot me a message or post here.

Thank you
[Android Head-Units] Rawb1:
Hi! I have the obdlink LX and am having problems pairing. Regarding your post you write:

I can't find anywhere in the obdlink app to change password?
[Android Head-Units] lotherius:
Did you ever find a way to get your OBDLink LX reliably working with a head unit?

I'm about to have to replace my aging OwnIce C500 which would connect intermittently with the OBDLink with some work. In the past I've tried to ask about better ways, but most people don't seem to understand the issues, or think kludges are a good idea. I can't/won't use a Chinese bluetooth dongle because I do datalogging that has to have a higher datarate than those dongles can support. My tuner needs that higher sample rate to see what's going on. Currently in my other car I have to use a phone to connect to the OBD2 despite having an Android head unit.

Trying to figure out if there's a particular radio on the market now that I can depend on actually working correctly with Bluetooth OBD devices. Advertising and support departments (such as Joying) always lie and say it works, so asking them is pointless.
[Android Head-Units] ZeroZorro:
Can't help with choose of hardware , didn't find an all-in solution but got it working...

With the ROM from Hal9K (I am on 4.0.2) it works fairly well.

It always works with OBDLink app from Playstore.

It almost always works with Torque

It hardly works with Realdash.

For me, my PX5 seems to have temperature and bad USB connector issues causing all my USB devices disconnect/connect randomly. I think Bluetooth is unreliable too with makes it even harder to pin down the real problem. With my phone I have no issues, so i rule out the OBDLink LX as the source of the problems....

In the past I was using Graser's Tool to rename ONDLink and got it recognized by the Android Car device and obtain the OBD logo in my status bar. Doesn't work anymore for me.... So no, sorry, issues not resolved...
[Android Head-Units] cleverdicky:
Dash command ?
[P8lite General] MARCOSOFT:
This tutorial was done by

haky 86

, I just made a small adaptation for dual SIM.

All credits go to

haky 86

, thanking any corrections.

How to lock the own bootloader Huawei P8 Lite ALE-L21 before sent to warranty for reparation?

Well, he found a way for this enigma and let's see together what should we do.

Requirements:

- Unlocked bootloader;

- TWRP recovery;

- ALE-L21C432B049 (B052 for dual SIM);

- ALE-L21C432B595 (B596 for dual SIM);

- ALE-B895 (B896 for dual SIM) (it's the Emui 4.1). Thanks to surdu_petru for uploading.

This rom should be installed and running before "lock the bootloader" so pay attention about the steps I did and what I mean.

Locking Bootloader:

- Do a factory reset by wipe all partition from recovery.

- Reboot to Bootloader.

- Flash via fastboot C432B049 (B052 for dual SIM).

fastboot flash boot BOOT.img

fastboot flash recovery RECOVERY.img

fastboot flash cust CUST.img

fastboot flash system SYSTEM.img

- Do a factory reset from settings once the device is running and don't worry if you see unlocked bootloader.

- Now extract the UPDATE.APP from C432B595 (B596 for dual SIM), create a dload folder on sdcard and paste that update file inside it.

- Reboot the device by press vol up + vol down together and release them when update process is starting up.

- Now sit and drink something because update process can take some minutes with many automated reboots.

- Run OTA update as latest step.

- Now your bootloader should be "LOCKED" and not "RELOCKED" like the following image, happy locking..

[IMG="Lock Bootloader"]http://1.bp.blogspot.com/-uRCeIEl986w/WY4CuLNouWI/AAAAAAAAWs0/36F9-SW9aBkAn5wpvrv8Twu2tswdvaUTwCLcBGAs/s1600/IMG_20170811_204559.jpg[/IMG]
[P8lite General] Gwozdem:
Thanks! Will try that in a few days, when I get my new Mate 10. I don't want to mess up and be without a phone right now :D
[P8lite General] D1stRU3T0R:
Hi, i have my last days in warranty, after i lock my bootloader how can i brick it to send it to the reparation, hopefully they change my phone to a brand new one, or at least mainboard etc...
[P8lite General] Gwozdem:
I guess you can't brick your phone with locked bootloader. This phone ain't that bad xD
[P8lite General] D1stRU3T0R:
Flashing a wrong boot.img will brick it? I mean old esal 2.2 for emui 4.1...Than if they don't accept it back, i will repair it.
[P8lite General] Gwozdem:
I think you can't flash anything if you don't have unlocked bootloader.
[P8lite General] XTutorials:
Download some destructive malware and they will change it for sure xD:p
[P8lite General] haky 86:
Nice, I did similar thing with the p8 lite 2017 ;)
[P8lite General] D1stRU3T0R:
You have an ideea how can i brick it with locked bootloader? And than so it can be fixable if they don't accept it at service...
[P8lite General] haky 86:
They accepted my phones 2 times with booth unlocked bootloader with twrp, but why you need to brick it again if your bootloader is locked?
[P8lite General] Ahmedoov:
I don't think you will ever find a way to do it because whatever you do it will be solved with just reflash firmware. Sorry but you can't get another one that easy especially with locked bootloader
[P8lite General] DarkJoker360:
Just by f****king up the oem info, imei... It s not hard :)
[Google Pixel 2 XL Questions & Answers] markp99:
Today I am unable to see my Pixel 2 XL listed among my older Android devices. Was there, now missing when viewed from PC:

Play Store

Find My Device

Any suggestions to get this device added back to the list?

I can d/l apps from play store no problem from the Pixel 2 XL itself.

Thanks!

v8.0

w/Magisk root
[Google Pixel 2 XL Questions & Answers] markp99:
Google Chat Support, level 2, is stumped. On to level 3 specialist.
[Google Pixel 2 XL Questions & Answers] markp99:
Level 3 failed. They ended the call claiming the issue has been escalated up the chain and I would be contacted by email.

We'll see.
[Google Pixel 2 XL Questions & Answers] galaxys:
Wow, very unimpressive Google support! It can only get better...
[Google Pixel 2 XL Questions & Answers] markp99:
Ultimately, their escalated response was to perform a factory reset.

I'm usually game for this little exercise, plus it's probably bring an 8.1 update along. So, I complied.

The reset did return Pixel 2 XL to my devices list. The 8.1 update OTA was received, and Magisk re-applied.

I am good to go.
[T-Mobile LG G4] pizzaboy192:
I live in a market where Band12 and VoLTE are required to be able to reliably call\text. All the Nougat ROMs don't support VoLTE and I can't find any information on MM based custom roms.

Does Lineage 13 MM support VoLTE? Are there modified stock roms that support it? The LG Crapware is starting to annoy me.
[T-Mobile LG G4] barcodelinux:
Any Nougat rom can flash the universal VOLTE patch via TWRP --> AOSP based VoLTE Patch

Hope this helps.
[T-Mobile LG G4] pizzaboy192:
your link is a little broken. What's the part in between WWW and .com?
[T-Mobile LG G4] barcodelinux:
giz dev (one word)
[T-Mobile LG G4] pizzaboy192:
That is for the Redmi Note 3, is it confirmed working on the g4?
[T-Mobile LG G4] barcodelinux:
I flashed the universal patch zip file and no modem at all. Not even bluetooth or wifi.

It's going to need some tweaking to get it on the G4 but it could be done.
[T-Mobile LG G4] pizzaboy192:
https://xdaforums.com/2015-moto-g/themes-apps/osprey-volte-patch-android-n-roms-t3527635/

I'm about to throw this at my phone to try it out. We'll see what happens. Going to test using SlimRoms 7.x for 811.

Edit: broke LTE. 3G, Bluetooth, Wifi, etc work still. This is an improvement. Unfortunately since this is my daily use device I cant do any more testing. Maybe I'll buy a 2nd H811 in the future.
[Samsung Galaxy S8 Questions and Answers] jonasmckee:
Every time my Ring App notifies me, it turns on my screen, the problem is if i ignore it and it stays in my pocket, the screen will stay on while moving around in my pocket. Other notifications will sound and vibrate but not wake my screen.. i looked thru the Notification settings, but still cant figure it out.

any help is aprreciated, thanks
[Samsung Galaxy S8 Questions and Answers] kingersj1:
I have the Ring app, and never had that problem.
[Samsung Galaxy S8 Questions and Answers] jonasmckee:
Interesting, so if you are looking a your phone with the screen off and trigger your Ring Doorbell.. your phone screen stays dark?

Maybe i need re-install the app.. hmmm
[Samsung Galaxy S8 Questions and Answers] kingersj1:
I've tried looking into my settings but I can't seem to find notification settings in the actual Ring app. I believe the usual behavior is the screen goes from AOD to with lock screen, if I interact with it it goes back to AOD. I don't know if the screen goes on when in my pocket, but it's never on when I take it out even after a motion detection