Unstable Bluetooth Connection issue PX5 MTCD/MTCE Android 9 - MTCB Android Head Units Q&A

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?

Related

Problem with WiFi

Hi,
I have problem with Malaysk ROM. I have 3 units....
1. KLD for RAV4
2. KGL for Zafira
3. KLD 2DIN (for now with stock ROM)
All are QuadCore unit 1024px.
Problem is with WiFi after update from stock to Malaysk ROM.
Problem is only with some Phones. For Example my Lenovo VibeShot don`t work. My wife Lenovo k3Note (MIUI) works great. Sony Z3 works. Iphone 5s dont work with Hedunit.
HeadUnit see Wifi hotspot. I can write password. But when is connecting signal strenght drop to one line and couldn`t connect.
I record screen from test. Problem is on KLD and KGL then it`s not hardware problem.
youtu.be/DgfRLAIqUfo
I test Hotspot on laptop and works great on my phone and this Iphone 5s.
Please help me. I want flash 3th unit but dont want loose Wifi
Best Regards
Tom
Edit: Today I install Malaysk ROM on 3th 2din unit. Problem also exist but HU connect to Hotspot itself for about 1-5 minute. When i click manually "connect" effect is the same as on 1th and 2nd unit. Range drop down and couldn`t connect.
I've noticed the same on mine with a mifi device - wifi seems to drop everynow and then,
Hi,
Same issue, latest Malyask ROM (28 Dec?).
Can see hotspot, but does not connect, tries and constantly drops back again.
Checked password is fine.
Phone is Nexus 6P, 6.0.1.
Cheers
jupi83 said:
Hi,
I have problem with Malaysk ROM. I have 3 units....
1. KLD for RAV4
2. KGL for Zafira
3. KLD 2DIN (for now with stock ROM)
All are QuadCore unit 1024px.
Problem is with WiFi after update from stock to Malaysk ROM.
Problem is only with some Phones. For Example my Lenovo VibeShot don`t work. My wife Lenovo k3Note (MIUI) works great. Sony Z3 works. Iphone 5s dont work with Hedunit.
HeadUnit see Wifi hotspot. I can write password. But when is connecting signal strenght drop to one line and couldn`t connect.
I record screen from test. Problem is on KLD and KGL then it`s not hardware problem.
youtu.be/DgfRLAIqUfo
I test Hotspot on laptop and works great on my phone and this Iphone 5s.
Please help me. I want flash 3th unit but dont want loose Wifi
Best Regards
Tom
Click to expand...
Click to collapse
Same here. I'm running latest Malaysk ROM (Jan 2016) on AN RK3188 1024X600 JOYING (JOYOUS) heading. WiFi was ok for bench testing but it will connect with full bars then drop after a short time (30s-3min). Not sure how to fix it because for a week it was fine... Won't connect to home wifi (in the house beside my computer) or my iPhone 5 hotspot 5cm from unit. Anyone have some ideas?
On my GA2114 WIFI sometimes wifi doesnt turn on at all
relevant ??
newt_dunbarton said:
Same here. I'm running latest Malaysk ROM (Jan 2016) on AN RK3188 1024X600 JOYING (JOYOUS) heading.
Click to expand...
Click to collapse
Same here on an RK3066 with latest Malaysk ROM.... first connection was fine. Then after 2h and 300km drive dropped the connection and no way to reconnect. Tested on Sony Z5 compact, Acer Z103 and iPhone 5s. Connection to regular APs works fine (McDonalds, Homerouter).
same for me. but my wifi disconnect from AP and don't connect after few minutes of working FM Radio
same here s07 mtcb-mx-v2.72 rk3066
everybody posting their wifi problems. no one can solve this????
i found something else.
yes hotspot alwasy drop connection. reconnecting is very hard. turn off wifi. turn off hotspot. turn on hotspot. turn on again wifi from unit. it will connect.
but after a while connection icon goes to dark. on unit if you check connection it looks like connected. when i check my g3 phone, no any machine connected. it shows 0/8 (0 connected in 8 machine).
i drive car to my workplace and parked close to door. when i connect to my modem no any problem left. it is connecting, connection is not drop, when i start car it is auto connecting. everything is looks like fine.
is this machine have problems with hotspot internet?
what is going on?
so we need real help. please hear some one here. thank you.
Have the same issue. Problem started after updating to FUSE technology on Malaysk ROM. WIFI drops connection after few minutes of using. Not sure if it can be fixed by ourself. It should be reported to Malaysk.
On Malaysk ROM 02-07-16 (version 2) on RK3188 800x480 HZC. Had the drop out issue on the stock android 4.4.4 but also on Malaysk ROM - very, very weird indeed... Would nive to have it fixed.
Hi mas618, did you get an solution. Got the same "wifi drop issue" with stock ram and also with malaysk rom.
Same to me. Any fix available?
Wifi corrected
Hi
Finally i found problem. Thank me if it is useful.
Problem is not software problem. It is just harware problem
I just take out unit from car. Opened 2 screws top of dvd and removed metal lid.
Wifi cable has 2 wire in 1 wire. Middle is the + outside wire is ground. So both is soldered very badly to signal point. I was able to solder ground side to ground but i just changed wifi antenna with wire from laptop antenna.
You can just solder it. Or you can chane it.
In first picture you can see very bad solder.
In second picture you can see new antenna with wire soldered.
You can solder outside wire any place of ground.
My wifi is now very good works. Not drop anymore. And bluetooth audio is not drops too.
I saw the cpu is not have any cooler. The last pictures show cooler is planted to rk3066

Bluetooth OBD Adapter not connecting after malaysk rom

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

MTCC RK3188 KLD6 Bluetooth for calls problem

I'm looking for help to resolve my 'Head Unit to Handset' Bluetooth calling problem.
My handset is a Sony Xperia XZ Premium (G8141) running Nougat 7.1.1 (O2 Stock ROM build 45.0.A.5.1)
My head unit is an Autopumpkin 11-RQ0546-UK-A (MTCC RK3188) currently running Malaysk 5.1.1 ROM and KLD6 V2.83 MCU with Microntek Head Unit Service V2.18
My HU and Handset are paired and media audio plays fine (with the Bluetooth app open on the HU).
When the devices first connect the phone shows 'Connected for Media and Calls' and the HU bluetooth app shows all of the options available (media, calls, phone book etc) but only for 1-2 seconds then they all become unavailable and the phone changes to 'Connected for Media'. When my phone rings nothing happens on the HU and my phone does not show the bluetooth speaker option in the phone app.
This HU worked great for calls with my previous handset (Xperia Z3 Android 6) and I was running Malaysk 4.4.4 ROM but it wouldn't work with my XZ Premium so I tried the following: -
Malaysk 4.4.4 ROM with MCU KLD6 V2.83
Malaysk 5.1.1 ROM with MCU KLD6 V2.83, V2.85 & (even a KLD9 MCU by mistake)
Microntek HU Service as included in ROMS but also newest version from XDA thread (both Bluetooth settings from this app)
all different MCU System settings for Bluetooth that are available (about 5 or 6 from memory).
Nothing seems to make things work. Some settings disable the bluetooth altogether but mostly the same thing happens, connection with all options available for a few seconds then just media audio.
Due to the length of time required to flash various combinations of MCU/ROM/HU service/settings I was hoping that someone could suggest a quicker way to fix this?
Thanks for reading, Thintin
Nobody?
Update: my Xperia XZ premium has updated to android 8 and now Bluetooth works as expected.
I got Bluetooth calls to work
I have an Eonon GA5180F with a rk3188 processor. It came with Android 4.4. I wanted to upgrade it to add more apps. I used Malaysk's ROM 5.1.1. All was well, but the Bluetooth calls did not work. The bluetooth music worked. I fixed this by going to settings, then to factory settings, then entering code 126 (or what ever your factory code is), then going to application, to BT and then changing it from IVT_BT to WQ_BC6. I saved it and then rebooted. The calls worked after that.

Unstable Bluetooth Connection issue PX5 MTCD/MTCE Android 9

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!

Dasaita wifi & bluetooth connection issues

I have PX6-HA5393-MAX10-CP updated with the VIVID10. Loving everything about that, however I purchased a Cobra SC201 dashcam with 5.0 Bluetooth and dual band 2.4ghz & 5 ghz wifi. My head unit cannot recognize either of the dashcam's Bluetooth or wifi networks to connect. The dash cam is visible and accessible with other devices such as phone and laptop. Only the head unit can't detect the dashcams wifi or Bluetooth networks to connect. The head unit is 2.4 ghz wifi only and the dash cam claims it's dual wifi (2.4/5.0 ghz). Both claim 5.0 Bluetooth. I have tried manually adding and connecting to dash cams wifi using different encryption keys with no success. Same issue before update to VIVID10 also.
LSmith3rd said:
I have PX6-HA5393-MAX10-CP updated with the VIVID10. Loving everything about that, however I purchased a Cobra SC201 dashcam with 5.0 Bluetooth and dual band 2.4ghz & 5 ghz wifi. My head unit cannot recognize either of the dashcam's Bluetooth or wifi networks to connect. The dash cam is visible and accessible with other devices such as phone and laptop. Only the head unit can't detect the dashcams wifi or Bluetooth networks to connect. The head unit is 2.4 ghz wifi only and the dash cam claims it's dual wifi (2.4/5.0 ghz). Both claim 5.0 Bluetooth. I have tried manually adding and connecting to dash cams wifi using different encryption keys with no success. Same issue before update to VIVID10 also.
Click to expand...
Click to collapse
- The Bluetooth is crippled and only works for phones and certain obd adapters
- The max10 can't do 5ghz... only 2.4
- The camera software will not do wifi cams.
Bob_Sanders said:
- The Bluetooth is crippled and only works for phones and certain obd adapters
- The max10 can't do 5ghz... only 2.4
- The camera software will not do wifi cams.
Click to expand...
Click to collapse
Bob,
Thanks for the follow up! Has anyone been able to successfully bypass the internal wifi/Bluetooth with USB wifi/Bluetooth adapter installs on these Android head units. I've read rumors of wifi bypass of others that know someone, but have yet to find any helpful links. Also not sure I follow regarding the camera software not doing wifi cams. Are you referring to Dasaita's DVR camera apps?
LSmith3rd said:
Are you referring to Dasaita's DVR camera apps?
Click to expand...
Click to collapse
As far as I know... yes. The app is trained to look for cams on usb and on the dedicated dvr cam plugin. I have not been able to get it to look elsewhere for cameras.
From what I understand, some people have had LIMITED success with usb bluetooth adapters. Some have managed to get them recognized, but then they operate in the same crippled fashion. The bluetooth regardless of what bluetooth system you use, will only recognize phones and some basic obd2 adapters and as far as I know, no one has been able to work around that.... and this is not just Dasaita... but pretty much all of them.
would rooting fix this limitation?
Bump - anyone out there was able to get Bluetooth for anything other than phones/OBD devices to work with any of these Android head units?
I have tried three off-the-shelf Bluetooth dongles and playing with the BT "drivers?" in the list for BT under Factory settings (i.e Head Unit > Settings > Car > Factory Settings > BT).
No luck!
shailentj said:
Bump - anyone out there was able to get Bluetooth for anything other than phones/OBD devices to work with any of these Android head units?
I have tried three off-the-shelf Bluetooth dongles and playing with the BT "drivers?" in the list for BT under Factory settings (i.e Head Unit > Settings > Car > Factory Settings > BT).
No luck!
Click to expand...
Click to collapse
No, you cannot. See above posts.
UIS7862 FYT based units work, including BLE.

Categories

Resources