Related
dwmcqueen said:
Hello,
I just recently purchased this - http://www.amazon.com/gp/product/B0...tailpage_o04_s01?ie=UTF8&psc=1#productDetails
A couple of notes:
1. It appears to be another HuiFei model - specs all align with what is said in this thread (including the Developer password).
2. MCU says MTCB-GS-V1.91
3. I am having a real hard time having my ELM327 connect - scanning for new Bluetooth devices yields nothing.
4. There is no "Extra Settings" - so not sure where I go to map the physical buttons (I want the Navi button to map to Google Maps).
Other than that, seems to be working nicely.
Click to expand...
Click to collapse
I have the same unit its MCU 2.02 though but only certain BT ELM works.... I found on that works fine... I will include more info in my write up....
antiguangenius said:
I have the same unit its MCU 2.02 though but only certain BT ELM works.... I found on that works fine... I will include more info in my write up....
Click to expand...
Click to collapse
By default, these headunits only recognize and pair with BT OBD adapters that have the name "OBD". I've removed this limitation with the latest experimental release of the XposedMTC module.
makkan00 said:
Bit worrying. I have this unit hardly for 2 months and it has developed another fault.
When I hit speed bumps, it automatically changes to previous track / radio station.
Click to expand...
Click to collapse
It seems that the rotary encoders used for volume and tuning are sometimes susceptible to vibrations/bumps. I've had issues where the volume randomly goes up or down while driving. After spinning the knob up and down a few times it goes away.
agentdr8 said:
It seems that the rotary encoders used for volume and tuning are sometimes susceptible to vibrations/bumps. I've had issues where the volume randomly goes up or down while driving. After spinning the knob up and down a few times it goes away.
Click to expand...
Click to collapse
Thanks. I will try it.
With regards to obd, how do I take out the restriction on obd adapters which my unit can use?
Thanks.
makkan00 said:
Thanks. I will try it.
With regards to obd, how do I take out the restriction on obd adapters which my unit can use?
Thanks.
Click to expand...
Click to collapse
You can either decompile the MTCBluetooth3.apk and Settings.apk, modify the smali files to remove the restriction and recompile, or you can root your headunit (check out the first post), install the Xposed Framework, and install the XposedMTC module.
agentdr8 said:
You can either decompile the MTCBluetooth3.apk and Settings.apk, modify the smali files to remove the restriction and recompile, or you can root your headunit (check out the first post), install the Xposed Framework, and install the XposedMTC module.
Click to expand...
Click to collapse
I have xposed mtc and framework and this is a year later. It still does not see my bluetooth ODB as it is not named ODB. It is named CBT
Shagman68 said:
I have xposed mtc and framework and this is a year later. It still does not see my bluetooth ODB as it is not named ODB. It is named CBT
Click to expand...
Click to collapse
Compatibility also seems to depend on the version of the adapter; the generic ELM327 readers come in many versions. I haven't correlated which versions work and which ones don't, but my adapter, which also shows up as "CBT" is a v1.2, and the override within XMTC does work.
I'm assuming you've already set the XMTC preference to "CBT" and rebooted? Make sure the pairing pin in the stock BT app matches that of the OBD adapter (e.g. 0000, 1111, 1234), and try pairing from within the BT app.
agentdr8 said:
You can either decompile the MTCBluetooth3.apk and Settings.apk, modify the smali files to remove the restriction and recompile, or you can root your headunit (check out the first post), install the Xposed Framework, and install the XposedMTC module.
Click to expand...
Click to collapse
hey @agentdr8 , I've managed to install Xposed, but cannot install the module itself... tried several versions and it still not working on my 4.1.1 Head Unit.
can you help?
agentdr8 said:
By default, these headunits only recognize and pair with BT OBD adapters that have the name "OBD". I've removed this limitation with the latest experimental release of the XposedMTC module.
Click to expand...
Click to collapse
Man i tried that Xposed option and no luck..... its there something specific you need to do? i did the following
- Turned option on Typed Name of ODB adapter.... in my case "Carly Adapter"
- Turned option off
neither worked for me... am i doing something wrong? my HU has passcode set to 1234 which is the same for ODB adapter this one is specially made for BMWs
staticx1 said:
hey @agentdr8 , I've managed to install Xposed, but cannot install the module itself... tried several versions and it still not working on my 4.1.1 Head Unit.
can you help?
Click to expand...
Click to collapse
If you're using a Malaysk rom, the module comes preinstalled, and just has to be enabled in Xposed Installer->Modules. If not, make sure you're installing it to internal storage; some roms default to installing to sdcard and it won't work that way.
xterm305 said:
Man i tried that Xposed option and no luck..... its there something specific you need to do? i did the following
- Turned option on Typed Name of ODB adapter.... in my case "Carly Adapter"
- Turned option off
neither worked for me... am i doing something wrong? my HU has passcode set to 1234 which is the same for ODB adapter this one is specially made for BMWs
Click to expand...
Click to collapse
Try using just "Carly" as the name (it's a string comparison using a String.contains). Leave the option enabled, and then restart the headunit.
i left it as Carly Adapter it worked just needed to reboot after activation of xposed but sadly it soft brick my HU everytime so system enters recovery and erase everything to restore defaults.... this is using Stock pumpkin firmware. So i think i just gonna go ahead and install custom ROM instead
Hi, I', not able to connect to my OBD adapter. It's a Vgate 3 and the bluetooth name is V-LINK. I've the last Malaysk rom (April 2016), I've installed Xposed framework and Xposed bluetooth module. I've tried to set every combination of strings that could match V-LINK (rebooting) but nothing seems to work. I've also set the bluetooth pin to 1234 (matching my adapter pin). My unit is a Pumpkin 1024x600 quad core RK3188. Any help?
Lyhaku said:
Hi, I', not able to connect to my OBD adapter. It's a Vgate 3 and the bluetooth name is V-LINK. I've the last Malaysk rom (April 2016), I've installed Xposed framework and Xposed bluetooth module. I've tried to set every combination of strings that could match V-LINK (rebooting) but nothing seems to work. I've also set the bluetooth pin to 1234 (matching my adapter pin). My unit is a Pumpkin 1024x600 quad core RK3188. Any help?
Click to expand...
Click to collapse
Is your OBD adapter paired to your phone by any chance? If so, unpair it, and try again
Sent from my XT1575 using Tapatalk
brbarnyard said:
Is your OBD adapter paired to your phone by any chance? If so, unpair it, and try again
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. I'll try, during my tests it was paired but If i remember well the phone bluetooth was off.
Hi everyone, I have a joying rk3188 1024x600 head unit and recently flashed the most recent malaysk rom. Before the flash, obd dongle would pair fine. Now I cannot get out to connect. I can connect my phone to the headunit, can connect my phone to the obd dongle, but cannot connect the obd dongle to my headunit whatsoever. It shows up in "available devices" and can be clicked then click "yes" to connect, but it doesn't connect.
I've tried to play around with xposedmtc but no luck.
Anyone have any ideas?
Thanks!
did you click enable xposedmtc in xposed?
TRY disable xposed-bt or manager in xposed
and roboot will be done
Yes, all are activated in xposed. And tw0119, I will give that a try.
Malaysk‘s rom Dec.2015 on my JY-HU clould pair fine ,but Feb.2016&Jan.2016 roms could not.
So i try disalbe all Xposed modules ONLY enable Xposed mtc ,OBD dongle works after roboot
Tw0119, perfect, works now. Did you go back and reactivate the modules again or no?
Thank you so much btw!
dannyboy223 said:
Tw0119, perfect, works now. Did you go back and reactivate the modules again or no?
Thank you so much btw!
Click to expand...
Click to collapse
NO,if you reactive the XposedManager module it would be down.
So i think somethings wrong with the Framework,maybe Malaysk could TEST for it
tw0119 said:
NO,if you reactive the XposedManager module it would be down.
So i think somethings wrong with the Framework,maybe Malaysk could TEST for it
Click to expand...
Click to collapse
No XposedBT whit OBD.
Prob is that there are number of overlapping Xposed modules, conflicting with each other and even underlying ROM features.
Until Malaysk and module devs coordinate their activities you have to experiment and make compromises. In order to get something you have to drop something.
I had the same problem: my bluetooth OBD2 / OBD adapter were being detected, but I could not pair them. My OBD2 adapter has a pin number and I was never asked for the pin to pair. Also, the device was being scanned and shown with the phone icon instead of the OBD icon. Had this problem with March and January 2016 versions of Malaysk ROM (which is awesome, btw!). How I solved the problem:
1. Opened the stock bluetooth app, removed the device which already appeared paired
2. Set the default pairing PIN to the PIN of my device
3. Disabled XposedMTC and XposedBT in the Xposed module manager
4. Rebooted
5. Scanned for the device, checked that it appears as OBD (icon) and paired again. No pin was requested, but it paired correctly and it works.
Hope this helps! Cheers,
C.
i have 2 adapters and neither will work for me. one will not pair no matter what combination of things i choose in xposed but works great with my phone. the other adapter works so good i don't even have to put in the pass code when using my deck, but it will not communicate with my 2001 fords ecu.
Hi
Not working bluetooth. Not scaning anything
Which BT chip sellected? WQ BC5 ,WQ BC6, IvtBt,Sd bt, WQ BC6B. My sytem rk3066 arm vortex 1.6 dual core .
April 2016 malaysk rom.
I tryed xposed disable combination but not working bluetooth
Help pls
Sytem starting i see pop-up bt connecting,version2
OBD adapter
Unfortunately I have the same problem with the OBD adapter are connected may not apply to find and get information...
The machine is KLD2-RK3188 1024x600 machine with the latest of Rom Malaysk 21/1/2017 (21 version)
I have tried all the above solutions but still not the OBD program works.
OBD connection Joying
Can somebody tell me where to get to "Xposed module manager" in Joying system please? For OBD bluetooth issue
i had same problem but solved it.
Don't use the bluetooth menu in system settings but use the bluetooth app instead (which came with the rom (android 6)).
Using the bluetooth app search here and here pairing worked without any problems for me, after pairing it worked as normal again.
cheatman said:
I had the same problem: my bluetooth OBD2 / OBD adapter were being detected, but I could not pair them. My OBD2 adapter has a pin number and I was never asked for the pin to pair. Also, the device was being scanned and shown with the phone icon instead of the OBD icon. Had this problem with March and January 2016 versions of Malaysk ROM (which is awesome, btw!). How I solved the problem:
1. Opened the stock bluetooth app, removed the device which already appeared paired
2. Set the default pairing PIN to the PIN of my device
3. Disabled XposedMTC and XposedBT in the Xposed module manager
4. Rebooted
5. Scanned for the device, checked that it appears as OBD (icon) and paired again. No pin was requested, but it paired correctly and it works.
Hope this helps! Cheers,
C.
Click to expand...
Click to collapse
That worked for me. But found also additional tips are needed to check:
1. If adapter name is not OBDII per default then in BT app settings (last tab) set exact name. This option is available in modded BT apps in Malaysk ROM (4.4.4), dunno for other ROMs. So there is no need for any exposed modules, just change adapter name in app.
2. Adapter with correct name can pair even if pin code is incorrect! Looks like paired but will not work in apps. So check that pin code in BT app settings is correct for your adapter.
3. In Torque, if you had any other adapter used before, clean all app data (in Android app info). Also noticed that even after app data cleaning, old Mac address is shown instead of new one paired in BT app. Looks like MCU somehow wrongly saves and provides old, even removed from BT app, adapter Mac address. But new paired adapter is working. So there is some mess with MCU and BT and Torque... Not sure where is the issue, but noticed that latest Torque ver listed something about 'improved listing of BT devices'. So it may be known issue on Torque side....
I had the same problem (obd bluetooth not working) using Pumpkin Android 7.1.2 with malaysk ROM 4.1 and found the following solution:
Go to app settings, select "show system apps" an delete data+cache of all (4 in my case) apps regarding bluetooth.
Then connect your devices again. Enjoy
Hi guys,
I am using an A-Sure Android Quad RK3188 radio with the latest Malaysk Firmware.
MCU Version is 2.83. A few months ago, Bluetooth worked from time to time.
Now it doesn´t find Bluetooth devices anymore – I don´t know why.
I also tried different firmwares..nothing helps
Maybe it´s damaged…would it possible to use another Bluetooth pcb?
If yes.. do you have any recommendations?
Thank you in advance..
Regards
Carbonskin said:
Hi guys,
I am using an A-Sure Android Quad RK3188 radio with the latest Malaysk Firmware.
MCU Version is 2.83. A few months ago, Bluetooth worked from time to time.
Now it doesn´t find Bluetooth devices anymore – I don´t know why.
I also tried different firmwares..nothing helps
Maybe it´s damaged…would it possible to use another Bluetooth pcb?
If yes.. do you have any recommendations?
Thank you in advance..
Regards
Click to expand...
Click to collapse
Try changing BT type in Factory Settings. After FW updates id may change to other type by itself. Happened to me. It looks like if works (yes you can get in BT app and it shows like working but searching and connecting doesn't work).
pa.ko said:
Try changing BT type in Factory Settings. After FW updates id may change to other type by itself. Happened to me. It looks like if works (yes you can get in BT app and it shows like working but searching and connecting doesn't work).
Click to expand...
Click to collapse
Thanks for your reply. I tried several BT Types but nothing changes. (It is an A-Sure RK3188 Radio for Vauxhall)
I also tried several firmwares from Malaysk. The best one for me is from may 2016.
Does anyone tried to solder another bluetooth stack on the main pcb?
Thank you all in advance.
Regards
Carbonskin said:
Thanks for your reply. I tried several BT Types but nothing changes. (It is an A-Sure RK3188 Radio for Vauxhall)
I also tried several firmwares from Malaysk. The best one for me is from may 2016.
Does anyone tried to solder another bluetooth stack on the main pcb?
Thank you all in advance.
Regards
Click to expand...
Click to collapse
What is your phone Andorid ver? There is known bug on 7.1 (confirmed by Google) preventing pairing/connecting to car systems.
pa.ko said:
What is your phone Andorid ver? There is known bug on 7.1 (confirmed by Google) preventing pairing/connecting to car systems.
Click to expand...
Click to collapse
It doesn´t depend on the phone I think (I don´t use nougat version.) I tried it with different android phones - also with 3 OBD devices.
Hey guys.
I'm on a Xtrons TE103AP which is basically a PX5 MTCD/MTCE unit. I was previously on stock Android 8.0, had no issues with OBD Bluetooth pairing and running ECU based programs off of it. Moved to Malaysk's 8.0, no issues as well. MCU back then was the MTCD the unit came with, GS 2.71 if i remember correctly
I took the plunge and moved to Android 9, first with Hal9k's v4.0, then Stock Android 9 for GS units (the most recent release). I tried these 2 combinations with different MCU's from GS 3.00 right up to GS 3.44 (latest). While i'm able to pair with my BT OBD2 Adapter with no issues, i'm unable to maintain a connection. The bluetooth OBD icon on the task bar connects and randomly disconnects causing programs (torque and hybrid asst etc) to drop connections with the ECU.
The behavior is constant. I've tried changing selecting different bt drivers from the factory menu, to no avail.
Anyone can shed some insight?
Thanks!
dingmel said:
Hey guys.
I'm on a Xtrons TE103AP which is basically a PX5 MTCD/MTCE unit. I was previously on stock Android 8.0, had no issues with OBD Bluetooth pairing and running ECU based programs off of it. Moved to Malaysk's 8.0, no issues as well. MCU back then was the MTCD the unit came with, GS 2.71 if i remember correctly
I took the plunge and moved to Android 9, first with Hal9k's v4.0, then Stock Android 9 for GS units (the most recent release). I tried these 2 combinations with different MCU's from GS 3.00 right up to GS 3.44 (latest). While i'm able to pair with my BT OBD2 Adapter with no issues, i'm unable to maintain a connection. The bluetooth OBD icon on the task bar connects and randomly disconnects causing programs (torque and hybrid asst etc) to drop connections with the ECU.
The behavior is constant. I've tried changing selecting different bt drivers from the factory menu, to no avail.
Anyone can shed some insight?
Thanks!
Click to expand...
Click to collapse
What BT type? Is it still OK on Android 8?
marchnz said:
What BT type? Is it still OK on Android 8?
Click to expand...
Click to collapse
Thanks for replying!
It was on WQ_BC6 by default. That was on android 8 (stock) and on Malaysk. I tried reflashing back to Android 8, but on the new MTCE MCU's. Problem persists.
Could it be the MCU causing issues? I've tried almost all the GS MTCE MCU's and they all produce the same issue.
Other Bluetooth functions work fine. A2DP and phone sync is perfect.
dingmel said:
Thanks for replying!
It was on WQ_BC6 by default. That was on android 8 (stock) and on Malaysk. I tried reflashing back to Android 8, but on the new MTCE MCU's. Problem persists.
Could it be the MCU causing issues? I've tried almost all the GS MTCE MCU's and they all produce the same issue.
Other Bluetooth functions work fine. A2DP and phone sync is perfect.
Click to expand...
Click to collapse
How have you tested your OBD adapter to confirm ithe adapter isn't the issue? Is it a genuine OBD adapter or knockoff?
marchnz said:
How have you tested your OBD adapter to confirm ithe adapter isn't the issue? Is it a genuine OBD adapter or knockoff?
Click to expand...
Click to collapse
Already tested. Its a rebadged ELM from Xtrons. They charged a premium for it, moreover it works fine on my android tablet. No connection drops or the sort. The exact same OBD was working fine with Android 8 as well prior.
A new update. I just realized that while i'm able to pair my phone and stream A2DP, and sync contacts with my phone, incoming calls route no audio or voice. Incoming calls trigger a prompt and i'm able to answer, but there's no sound or pickup from the microphone. weird....
I've tried selecting BC8 and BC6 in the factory settings... not quite sure what i'm dealing with. I'm on GS3.30bd, the BD modded MCU. Will see if an unmodded MCU fixes the voice issue.
@marchnz I flashed an unmodded GS 3.44 MCU and bluetooth audio worked properly. the OBD connection was still intermittently dropping. I then moved back a step to GS 3.40bd (soundpatched) and had no issues as well with bluetooth audio. I suppose the bluetooth issue was from the modded 3.30 MCU.
The Bluetooth OBD connection drop still hasn't been resolved however.
Any suggestions?
Hello, i had zlink on my android unit on my car.
i accidentally deleted the app.
i tried to download several ZLINK virisions but none of them work.
can someone please help me and guide me in order to get tapp work again?
Factory reset/reload Android.
marchnz said:
Factory reset/reload Android.
Click to expand...
Click to collapse
I cant get the 4 digit code for the factory reset on the screen...
Usually is 126
tome12121 said:
I cant get the 4 digit code for the factory reset on the screen...
Click to expand...
Click to collapse
Is the device an MTCD/E
marchnz said:
Factory reset/reload Android.
Click to expand...
Click to collapse
I accidentally deleted the zlink on my device
Is there any way I can get it back??
Hello, I have recently bought an off market MMI for my Audi and I am having issues connecting my phone with Zlinks, the phone is successfully connecting via Bluetooth but the Zlinks app just displays WAITING. I would appreciate help and advice on how to fix this. Thanks
Hi, I have android 10 head unit and Zlink app. But my zlink have wired and wireless carplay. But I have xiaomi smartphone. Zlink setting have android auto but not have android auto. I want to wired or wireless add this zlink app. How do I?
Hi I have a android head unit and cannot get zlink stabilized. Some days it works some days not at all. I usually get the error message Hardware err no MTI #. I bought the C usb cable but where do you put it? Please help this is so frustrating. Is there a way to fix the zlink software? Thank you
Mimix3 said:
Hi I have a android head unit and cannot get zlink stabilized. Some days it works some days not at all. I usually get the error message Hardware err no MTI #. I bought the C usb cable but where do you put it? Please help this is so frustrating. Is there a way to fix the zlink software? Thank you
Click to expand...
Click to collapse
Is it an MTCD head unit. What does seller suggest when using hacky zlink
It looks like this. The seller doesn’t say anything no help. Is there an alternative to zlink?
Mimix3 said:
It looks like this. The seller doesn’t say anything no help. Is there an alternative to zlink?
Click to expand...
Click to collapse
If you're wanting to do Android Auto, there is an app called "Headunit Reloaded" developed by XDA developer @Emil Borconi. There is a free version of Headunit Reloaded that you can install to verify hardware compatibility before purchasing the full version. I have purchased the full version and can confirm that it works quite well as an alternative to ZLink.
[Android 4.1+] HeadUnit Reloaded for Android Auto with Wifi
This Threader is a Spin-off of the original: [Android 4.1+] Headunit for Android Auto - 160117 - Self Mode+ other fixes, x86, 720p by the late :crying: @mikereidis. App links: https://www.b3itlabs.com/prod.php?id=1 PlayStore...
forum.xda-developers.com
jlbooth said:
If you're wanting to do Android Auto, there is an app called "Headunit Reloaded" developed by XDA developer @Emil Borconi. There is a free version of Headunit Reloaded that you can install to verify hardware compatibility before purchasing the full version. I have purchased the full version and can confirm that it works quite well as an alternative to ZLink.
[Android 4.1+] HeadUnit Reloaded for Android Auto with Wifi
This Threader is a Spin-off of the original: [Android 4.1+] Headunit for Android Auto - 160117 - Self Mode+ other fixes, x86, 720p by the late :crying: @mikereidis. App links: https://www.b3itlabs.com/prod.php?id=1 PlayStore...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for the help. Greatly appreciated.
Mimix3 said:
It looks like this. The seller doesn’t say anything no help. Is there an alternative to zlink?
Click to expand...
Click to collapse
Yes - here; https://www.android.com/auto/compatibility/#compatibility-stereos
I have a Android radio the uses the zlink app, that I use my apple carplay, this wireless connection is very unstable and drops regularly. sometimes it does not connect at all.
The cable is beter but does also just randomly drop.
I have tried other iphones, cables and even looked for newer firmware, but says we have latest version on.
I purchased the Carlinkit device to see if this will work but also no luck.
Can someone maybe advice me?
PATMAN93 said:
I have a Android radio the uses the zlink app, that I use my apple carplay, this wireless connection is very unstable and drops regularly. sometimes it does not connect at all.
The cable is beter but does also just randomly drop.
I have tried other iphones, cables and even looked for newer firmware, but says we have latest version on.
I purchased the Carlinkit device to see if this will work but also no luck.
Can someone maybe advice me?
Click to expand...
Click to collapse
Use the android head unit as android head unit or buy genuine AA or Carplay unit based on need.
These Chinese knockoffs emulate and are problematic as emulator.
See post above