No but some people do reckon its underpowered and mod them to have more power using a powered usb hub, look in either the hardware mod section or the original HuiFei thread for info.
October/September (2016) Firmware for MTCB and MTCC Units
- Thread starter dsa8310
- Start date
- Status
Has anyone successfully managed to update the version of Xposed either on Booroondook's 5.1.1 ROM or DSA's 5.1.1 ROM?
On a side note, it seems Booroondook has borrowed DSA's modified version of Xposed.
On a side note, it seems Booroondook has borrowed DSA's modified version of Xposed.
You mean the Xposed version that spoofs the MCU check and makes the sound mod work ?
Right well it was dsa that made some mods that got Xposed working on these units months back, so in effect they ALL use that version.
I think I can remember him managing to get it to work on 5.1.1 months back. So I assume it's not upgradable.
If I recall there was a bit of a "disagreement" between @dsa8310 and @doitright - dsa did the slight mods need to get it to work as doitright suggested, but he didnt add the changes to github, so doitright added them himself. That means now that all versions of Xposed should now have them.
Oh right, so in theory, all 5.1.1+ versions of the Xposed Framework on the Xposed website should be MTC headunit compatible since they carry DSA's mods?
Theoretically yes, but I dont know how long it takes for all the code to be merged. Try it and see.
Not quite. The thing is, the patches will *never* be accepted into upstream xposed, since they are pretty much a device specific hack. Essentially, it is pulling in a commit from Android 6.0.
So I've forked the repository and cherry-picked the appropriate commit into my personal repository here;
https://github.com/lbdroid/android_art-1/commits/xposed-lollipop-mr1-rockchip
No, to get the links I would have to search the original thread and then the Hardware mod forum same as you, they are there cos I remember reading them, just a case of finding them.
Well now I'm totally lost. The issue I'm having is that a specific function (OBD) of Xposed-MTC-manager does not work under 5.1.1, or Booroondook's 5.1.1 ROM at least. The Xposed-MTC-Manager OBD hack does work under 4.4.4 tested on two headunits. So I believe it's either a problem with Xposed running on 5.1.1 or Booroondook's ROM?
I've tried both version 1.8 and 1.12 of Xposed-MTC-manager.
I've tried both version 1.8 and 1.12 of Xposed-MTC-manager.
Last edited:
I have 2 OBD2 Bluetooth devices and both works on my HU with any ROM I used.
Currently on Boonoorooks (spelling) and will (as usual) flash a different ROM probably today.
Interesting... Do your OBD devices have 'OBD' in their Bluetooth ID? I assume you're running 5.1.1?
One the OBD2MX I needed to change the pass to 1234 on the radio.. then it hooked up.
Yep, I've tried that. Do you know if the Bluetooth IDs of your OBD devices have the characters 'OBD' in them? Or did you have to use an Xposed module such as Xposed-MTC-Manager or XposedMTC to get the devices to pair?
I will check soon, will add the MX OBD2 and see how it is called out on Booroondook
---------- Post added at 01:23 PM ---------- Previous post was at 12:26 PM ----------
OBDLinkMX.
works after setting to 1234 with xposed not enabled. will check on the way home, i have just enabled it and had to return to work
You won't need an Xposed module for that as Bluetooth devices with OBD in their ID are accepted by default.
- Status
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone