MTCC RK3188 KLD6 Bluetooth for calls problem - MTCB Android Head Units Q&A

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.

Related

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

Bluetooth issues with car stereo

Hello there. I've been experiencing a problem with my OP3, regarding the BT connection to my car stereo.
I recently bought a new head unit for my car, a Pioneer MVH-X580BT unit, it Works fine. However, when i connect my phone to it, it allows me to playback áudio, but i won't allow me to use it for hands-free calling. The Bluetooth menu on the phone says "MVH-X580BT - Connected (no phone)". It happens with any CM-based rom that i've tried so far.
However, when i install a stock rom (Oxygen OS, Freedom OS also works), it works just fine, both audio and phone mode.
Is there something in custom roms that changes some sort of parameters in the ROM that makes the phone refuse a phone mode connection from the radio?
Any tips i can use?
Thanks!
logcat of the incident:
Here.
Hope it helps.
I've had the same problems. It's an issue with the LOS BT stack. I've created several unofficial versions of my favorite ROMs using a different BT stack that fixes this problem for me. Let me know if they work.

chinese android head unit problem Play Store and Bluetooth

hello everyone,
I just installed a SEICANE chinese android head unit in my Fiat Ducato from 2017.
I connected the ISO port directly to the 2 connectors from the car, I've first tried to use a power harness including the CanBus decoder, but then the HU is dead. Without harness , the HU works (I guess the car already has a CanBus built in?).
The radio works very well. Also Wifi works well, I can surf on the Internet. But some apps I can not download (using Play Store). For example when I try to download TomTom GO, the HU tells me that there is no Wifi (although there actually IS Wifi!). Other apps are no problem to download (I've "fixed" this problem by installing Sygic i.o. TomTom).
I paired my Samsung XCover3 via Bluetooth and also problems: when I try to make a phone call, sometimes it goes to handsfree (like it should), but sometimes it does not (although the phone display opens on the HU). I did the pairing 10 times , but no difference. I also tried to make an Internet connection using Hotspot or tethering, but that also does not work.
I resetted the HU, but no improvement.
Does somebody knows these problems (and has sollutions to it)?
Regards,
Peter

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!

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!
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?

Categories

Resources