Hi!
In general MTCE units have Bluetooth 4.0, which is also BLE compatabile.
Have anyone tried to use it with BLE devices?
Various BLE information apps says that there is BLE framework, but BLE scanner cannot find any device.
Best regards,
Karol
Hi!
Did anybody have experience of connecting BT4.0 BLE device to MTCE PX5?
I have a BT4.0 BLE remote control, it is recognized by OnePlus 3T, but my headunit doesn't see it
I need info of this too
I have two BLE devices both are engine Battery Monitors.
My Xtrons unit can not detect either of them so I would be very interested in finding out if an MCU update or 3rd party tool is available to fix this assuming the MX5 actually supports BLE?
Hi, I just got TPMS sensors planning to view all the info through my PX5 MTCE head unit but there was no way I could make it detect them. I am also following up on this.
No.
Related
Hi All,
I now own a Joying RK3188 1024x600, which I am really loving.
One issue I am having though, is using my Moga Controller with the unit.
The bluetooth will see the device, but will not pair/connect to it.
It is as if the Head Unit will only connect to mobile devices with audio output.
Is there anything I can change, or a patch to alter how the bluetooth operates?
I would really love you suggestions.
I am currently running the rooted rom suggested on the Joying website (http://forum.xda-developers.com/showpost.php?p=60591423&postcount=12068).
Thanks.
Read HERE.
Bumping an old thread. I have a moga controller and when scanned both A and B mode show up but I cannot pair with it on either mode. I tried the info in the link above but I still cannot get it to pair. It shows up as a phone icon instead of a controller on my Bluetooth settings.
Any help?
Edit: it's a 3188 model Android 4.4.4 on latest Malay ROM and 1024x600
OK I added the moga Bluetooth strings in the xposedMTC Bluetooth settings and it now shows up as an obd device. Followed the link posted 2 replies up and I don't think the exposedMTC will fix the issue. I'll try decompiling the Bluetooth files and manually adding them if that's possible.
Following this ^^^ I have tried a bluetooth keyboard and mini bluetooth SNES controller and while I can see it I can't pair with it. Is that a hardware shortcoming or bluetooth.apk shortcoming? I would love to be able to use this SNES controller, I have a SNES emulator installed with a few ROM's but no way to play them. I have a USB wired 360 controller that I am going to take out to my VW and try shortly but bluetooth is how I would like to do it. Thanks.
Id liek to know this as well. I have some devices that I can see but not pair with also.
Dave
Also interested in getting any of my bluetooth controllers to work with my unit. They show up, but won't connect.
What is the pin on those controllers, if there is one?
Is there an update on this thread? I am really interested in connecting 8bitdo controllers to my Pumpkin head-unit. Like everyone else i can see the devices but wont connect.
In a reddit post, someone made it with usb but is there any way to connect via bluetooth?
i also own a joying unit with malaysk rom (RK3188 / 1024x600 / 06.2016) since a few days and also i am not able to connect my 8bitido SNES controller.
- installed XposedMTC / Override BT OBD device string with SNES controller BT name (didn't enter full name because of space character
and pairing worked!
- did pair as OBD device
- didn't recognize as input device
so the controller doesn't work yet
would be interesting if the controller would work in original joying / pumpkin ROM?
=====================================================================
EDIT: after reading some time in malaysk rom thread it seems that BT functionality is trimmed from the manufacturerers... and so no support for numerous BT devices.
I'm currently working with a software developer who produces an OBD2 reader and the associated app (Hondash). The device and app work perfectly on conventional Android devices, but not our awkward headunits. The OBD2 device connects and pairs to the headunit, however the app cannot detect it. It seems that the headunit's Bluetooth hardware is not visible to the app. The developer says he "don't know how or why the system doesn't deliver a Bluetooth device list to my app when requested". He goes on to say "For some reason the head unit doesn't expose a device list to my app, and without it it's blind and not able to initiate a connection"
My understanding is that the Bluetooth hardware is handled by the MCU part of the software, rather than Android itself.
Does anyone know of a way to convince the system to expose the Bluetooth device list? Or has anyone got access to the programming documentation for the head unit Bluetooth API?
What is puzzling here is that apparently Torque works on our headunits. Torque is compatible with our Bluetooth so it does seem possible. I assume that Torque isn't the only OBD2 reader app that is compatible, there's probably other too, so any tips on how he could get his app to work would be appreciated.
Other than Torque, what other OBD2 apps using Bluetooth have been confirmed to work correctly with our MTCB and MTCD headunits?
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!
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?