yashsingh1/xdaforums huggingface dataset:
[MTCB Software Development] agentdr8:
Ah yes. That's what [MENTION=3590033]Malaysk[/MENTION] was referring to. I'm downloading that rom now to see what has changed and will try to release an updated XMTC for it in the coming days.

EDIT: Apparently quite a bit has changed in MicrontekServer.java since the last time I updated XMTC. It will take some time to rewrite the module to support the new version. I may just fork the current code and have two separate versions; the current one for "legacy" roms, and a newer branch for roms going forward. Unfortunately I don't have a lot of free time at the moment, so it may take me a while to get this new rom installed on my GS and start updating code.
[MTCB Software Development] phil001:
Ok, thanks for the update, i'll leave it with you :)
[MTCB Software Development] espero0101:
Hello [MENTION=434511]agentdr8[/MENTION]. Do you also have a GS unit (as myself)? I didn't saw yet anybody here on the forum with GS unit...

Which is the resolution and the chipset version of your HU?
[MTCB Software Development] agentdr8:
I do. It's an 800x480 rk3066 unit.
[MTCB Software Development] espero0101:
Mine is 800x480 RK3188.
[MTCB Software Development] FordFocus2007:
What was the reason you disabled the backview function?

I for one ( probably the only one ) would like to launch my backview camera when i want it.. I thought of installing a switch in the car but that would be my last method, software should be able to help me out.

I'm going to try install a old version of your module, but probably there is something wrong with it ( why disable something that works right.. ) and i actually don't want to lose the BT-OBD override function. So that's also a bummer

Maybe someone knows another way of opening the backview-app or a workaround, i would not mind to give up a button for it ( mtc-keys )

All input on this would be appreciated
[MTCB Software Development] agentdr8:
It was disabled because it didn't switch the video input, which is something the MCU controls when it receives a +12V signal on the reverse camera wire. That can't be replicated with software, so a switch is likely the only way to control it.

You could get an internet-connected switch/relay (like the Switcheroo), and then use software to control that though.
[MTCB Software Development] FordFocus2007:
Thanks for the reply.

A switch it will be then, the switcheroo looks promising but still not available
[MTCB Software Development] kelvinnn:
Hi [MENTION=434511]agentdr8[/MENTION],

Thanks for the hard work, XposedMTC is truly a life saver! ;)

Anyway, I noticed that these headunits don't show all bluetooth devices, only certain ones such as mobile phones and in this case OBD adaptors. Since you managed to patch it to support non-"OBD" strings, I was wondering which .java file I could look at to enable viewing of all bluetooth devices?

I'm trying to get some LED Lights which are controlled via Bluetooth working, and yours was the closest to any working solution (well, at least for the bluetooth OBD adaptors)...
[MTCB Software Development] agentdr8:
Getting the headunits to pair to non-OBD adapters is easy enough, but the BT stack in these roms don't support all profiles (SPP, OBEX, HID, etc). Depending on what your LED lights use, it may or may not work, even if you can get around the pairing hurdle.

At any rate, take a look at these classes in MTCManager.apk and Settings.apk: com.microntek.bluetooth.BTDevice, com.android.settings.MtcBluetoothSettings, com.microntek.bluetooth.ui.SearchFragment
[MTCB Software Development] kelvinnn:
Thanks for the quick reply! I've taken apart MTCManager.apk and Settings.apk, and also my LED control's APK...

Noticed it used something called GATT. Something to do with Bluetooth Low Energy. Did a few string searches and don't see it. Do you mean that the BT stack for all these profiles were stripped intentionally? Or can we add it back from another RK3188 ROM? (i.e, TV sticks, etc)
[MTCB Software Development] agentdr8:
Generic ATTribute Profile. I don't know if these roms support that profile. I had issues getting my Valentine One (v1c) working, and it just uses SPP, which is pretty common. No such luck, even after pairing.
[MTCB Software Development] lincoln_dj:
hi guys. probably a noob question, but I dont seem to be able to get the timed screen dimming to do anything. I've tried setting the time manually so I can sit there watching it but get no brightness change. Clicking "start service" and "stop service" makes the program start and stop according to the status bar.

Maybe it is being over-rided by the system brightness? I've tried system brightness set to both Auto and light/dark.

I'm running the latest Malaysk rom on an RK3188 KLD6 "S07" head unit.

Cheers.
[MTCB Software Development] agentdr8:
Here's what I would try: verify in Settings that the system date/time is set to proper time and timezone, and not set to auto. Set the dimming start time to current time +1 minute. Set dimming end time to sometime in the morning (5AM). Set the dimming amount to 10. Close out of XMTC prefs. Wait for 1-1.5 minutes and the backlight should change.

If it doesn't change, enable debugging in XMTC prefs and reboot. Then repeat the test and post the Xposed Installer logs.
[MTCB Software Development] gb37270:
i have problem with XposedMTC.

when I select Music to my favorite music app (mymusic), application crash .

if I choose another app (jetaudio, poweramp) , does it work .

For MyVideo and myRadio, all apps works...just MyMusic crash
[MTCB Software Development] Us-Marshal:
I have an interesing issue with XposedMTC when using my steering wheel controls/buttons.

I've used it for the past year on my Coudu ROM without any issues, but recently installed an RK3188 and the latest MAL ROM. If I install XposedMTC, I get odd 'double' key presses in Poweramp and it advances/rewinds two tracks at a time and mutes the audio.

I uninstall it and everything works, but I REALLY like the ability to override the source/mode selection rotation list using my steering wheel source/mode button.

Any ideas?
[MTCB Software Development] agentdr8:
Are you also using Headunit Service? There's a few different mods installed by default on Malaysk roms that might conflict or provide similar functionality.
[MTCB Software Development] Malaysk:
Hi agentdr8! The new firmware Chinese programmers completely redesigned ( Smali) MTSManager.apk - and now your module XposedMTC does not work (MODE button resets the unit) . Here are this file
[MTCB Software Development] 2shaelib:
Im having the same issue. Really enjoyed this.

I would love to see this app get updated with better controls of what apps should open, in what order. Which one should be killed completly (for example nav apps should be allowed to run in the background but audio apps should be killed if a new one is switched to.

I would also like to see a UI Popup that would show what it is about to change to rather than actually changing. only if you stop pressing the switchmode button should it then switch to the highlighted app from the list.
[MTCB Software Development] holofury:
Try using "MediaPlayer" instead of "MyMusic".

MediaPlayer is the standard media player on these devices.

MyMusic afaik is just a little app which stops other media sources and then starts the app which you have selected. When it tries to start itself, it gets into a loop and crashs. :)
[MTCB Software Development] vuquan:
Hello Malaysk,

I have this issue with the March, 09 update ROM.

The downloaded file is zip file, not apk file. Can I install it without the TWRP recovery? Or can I rename it's extend to apk and install it normally?

Thank you & sorry for my stupid questions!
[MTCB Software Development] agentdr8:
This was the direction I was taking the module, but haven't made much progress. Too many other commitments, so I haven't had time to work on it at all.
[MTCB Software Development] agentdr8:
Malaysk just posted the updated MTCManager package from the newer roms, so that I would have some reference code to base an updated XMTC on. I haven't had a chance to update it yet though.
[MTCB Software Development] vuquan:
Sorry, I do not understand your comment.

The downloaded file is MTCManager.zip, not is MTCManager.apk. And I need your help that how to install it without the TWRP recovery?

Thanks!
[MTCB Software Development] agentdr8:
The short answer is, you don't. If you want an updated MTCManager, then flash the latest Malaysk rom. Manually updating just the MTCManager on older roms will result in all sorts of issues.
[MTCB Software Development] vuquan:
Thanks for your help!

I using latest Malaysk rom (March release). The issue has happened since I install XposedMTC. It is the Mode button resets the HU.

Which version of MTCManager can solve this?
[MTCB Software Development] agentdr8:
None. The XposedMTC module needs to be updated to work with the newer MTCManager versions, not the other way around.
[MTCB Software Development] 2shaelib:
Is your code on github? Can i help towards the project?
[MTCB Software Development] agentdr8:
It's currently on bitbucket, but I may migrate it over to github, as I have less and less free time these days to work on it.

PM me, and I'll notify you when the migration is done, and you can contribute as you see fit.
[MTCB Software Development] Malaysk:
Dear agentdr8, we all look forward to your module, it is very bad without him :crying:
[MTCB Software Development] wdkrus:
Thats true, XMTC has the best dimmer implementation, too bad it is not working on latest FW.
[MTCB Software Development] iateshaggy:
im not able to get the bt overide to work. i'm using the latest malay ron on an rk3188. xposed it updated and enabled and i'm using module v1.4.2. my devise is named CHX and i added that in the module and reboot but the hu still wont even give me the option to put in my pw when i hit connect. any ideas? also, i have disabled all other modules.
[MTCB Software Development] agentdr8:
The current version of XMTC (1.4.2) does not currently work on the most recent malaysk rom. I do plan on updating it, just not sure about when.
[MTCB Software Development] victorvtr:
Many of us expect it, thanks for your work
[MTCB Software Development] iateshaggy:
what was the last malay release that did work? i tried the previous version as well without any luck.
[MTCB Software Development] wdkrus:
It was Feb 2016 release.
[MTCB Software Development] agentdr8:
I haven't updated my GS since last Sept. I know the oem rom builder updated the MTCManager.apk sometime near the end of 2015/early 2016, so whatever version was before that should still work.
[MTCB Software Development] TT_Vert:
For the time being could we pull an old MTCManager.APK from a pre-Sept ROM to resolve this?

Dave
[MTCB Software Development] agentdr8:
That's likely to cause either FCs or possibly boot loops. Most everything in the rom depends on MTCManager, and if you swap it out with one that doesn't have classes or methods that other processes are expecting, all sorts of bad things will occur.
[MTCB Software Development] TT_Vert:
Fair enough, will wait it out, thanks.

Dave
[MTCB Software Development] iateshaggy:
i've rolled back to the january malay release, set the decks pin to the same as my obd2, activated the override and set the name to CHX (same as my obd2) and have not installed any other modules. it still hangs after i hit pair & connect without asking for a pin. is there any thing i'm missing or it this adapter just not going to work with my deck? i've tried using the bluetooth app and the bluetooth settings to connect.
[MTCB Software Development] agentdr8:
Can you post the xposed installer log? Not all BT OBD adapters will work, even with the override.
[MTCB Software Development] staticx1:
thanks, it looks awesome but - I cannot install it on my generic HU 4.1.1... :crying:

it there any compatible apk?

thanks
[MTCB Software Development] 1-2-Hak:
[MENTION=434511]agentdr8[/MENTION] appreciate your work over the time and have loved your module. Unfortunately my update to the latest malaysk has broken the volume mod as well :(

If you ever get a time to review and update that would be awesome.
[MTCB Software Development] agentdr8:
4.1.1? Try one of the older builds...like 1.2.8. I take that back; I don't believe I ever had a 4.1.1 device. My headunits all started at 4.2.2, so I have no idea if the module will work on JB 4.1.1. Is your headunit based on one of these roms? If it doesn't use the same type of MCU & OS, this module will likely do nothing.

Yeah, a whole bunch of stuff is broken in the module right now on the newer roms. The good news is that I've pulled my headunit out of my car, and it won't likely be going into my new car, so I'll be able to dev easier with it on the bench.
[MTCB Software Development] staticx1:
Can you post a compatible version so I can try if it's working?

My unit is generic - Cedric 3 aosp... I cannot find information beyond this...

Thanks a lot
[MTCB Software Development] agentdr8:
I can guarantee it won't work. From this page, it shows cedric as an Mstar device, which is not based on the Rockchip 3066/3188 like these headunits are.
[MTCB Software Development] staticx1:
Yes it is an Mstar device... So what can I do...? Why is it a cpu dependent but not android dependent?
[MTCB Software Development] agentdr8:
The roms that these particular headunits use are built around the rk cpus, and this module targets a specific package called MTCManager, which is only part of these roms. The MTCManager interacts with the Android OS and the MCU. This interaction is different or non-existent on different headunits, and that's why this module won't work.
[MTCB Software Development] iateshaggy:
http://pastebin.com/TrzapQFv

thanks for checking it out for me.
[MTCB Software Development] agentdr8:
You have a few different modules that likely modify the same classes/methods:

Loading modules from /system/app/[B]xposed-mtc-bt-1.2.apk[/B]
Loading class com.mvgv70.xposed_mtc_bt.Main
Loading modules from /system/app/[B]xposed-mtc-manager-1.4.apk[/B]
Loading class com.mvgv70.xposed_mtc_manager.Main
Loading class com.mvgv70.xposed_mtc_manager.Bluetooth
Loading class com.mvgv70.xposed_mtc_manager.Settings
Loading modules from /system/app/[B]XposedMTC_v1.4.2.apk[/B]
Loading class com.dr8.xposedmtc.MTC

Try disable all, and then enable one at a time, test, and if it doesn't work, disable, enable a different one, test, etc etc.
[MTCB Software Development] iateshaggy:
i tried that, and every combination of 2 and all 3 bluetooth modules and still nothing.
[MTCB Software Development] agentdr8:
Did you enable debugging for XMTC in the preferences? Try that, reboot, and then repeat your BT pairing, and repost your xposed installer log.
[MTCB Software Development] iateshaggy:
http://pastebin.com/jxK5YkqF
[MTCB Software Development] wdkrus:
You've got a lot of errors from com.mvgv70.xposed_mtc_manager, disable it.
[MTCB Software Development] iateshaggy:
thats the one module i need. my obd2 is named CHX and my hu will not connect to it or is there a way to disable just that part of mtcm?
[MTCB Software Development] lysiong:
Hi [MENTION=434511]agentdr8[/MENTION], is that possible to fix the XposedMTC in Malaysk April rom? as cant change the default music player to 3rd party player
[MTCB Software Development] agentdr8:
Yes, it's on my list of things to do.
[MTCB Software Development] pyraxiate:
This might be an odd question but will this module allow Bluetooth audio calls over all channels for an android car radio? I think they are set to use the front channels only by default but my canbus adapter is only connected to this rear output because I'm using a factory amp. Long story short, either I need to pull the head unit out and swap front / rear wiring or find a way to remap the Bluetooth to play on rear or all 4 channels for call audio. Bluetooth music plays perfect ... Just not calls. Thanks!!
[MTCB Software Development] agentdr8:
Nope. Not sure why your call audio is only over the canbus output.
[MTCB Software Development] pyraxiate:
The canbus is output to my factory amp. I'd have to hack and splice a ton of wires otherwise. The canbus adapter is only capable of 2 Channel output and it chooses the rear....not sure why. I may wind up running all new wires to the factory amp when I get time.

Meantime, the Bluetooth call audio which is routed to the front speakers won't work. I don't think bluetooth music audio will suffer if I swap front and rear at the harness.
[MTCB Software Development] pyraxiate:
Update on my previous issue.

Problem fixed with my call audio. I just flipped front and rear at the harness. All good now. It was the canbus after all. It only used the rear input for all 4 channels. Now its using the fronts for all 4 and call audio is routed to all the speakers.

Going to get an inline driver for the sub. Should help amplify things a bit. My MTCB has no sub out line adjustment. I added an external line level knob up front to help control the gain but its still too low unless the volume is up to at least 3/4 max. Otherwise I can't hear the sub. At full volume it hits decently but I don't want to push my other speakers that hard to compensate.
[MTCB Software Development] royalhawk2002:
I am on the last Malaysk ROM (23/04/2016) and I have notified that is I enable the XposedMTC module in the Xposed, then pressing the "Mode" button on the SWC the unit goes in to bootloop.

Same issue has been reported on the forum from some other user.
[MTCB Software Development] wdkrus:
Just wait for update from agentdr8, current version of xmtc is incompatible with roms released after February.

I really missing dimmer feature, so all we can do is to wait patiently.
[MTCB Software Development] TT_Vert:
newest rom fixed the dimmer feature from what people said.

Dave
[MTCB Software Development] Malaysk:
Yes, there is a problem. For MODE button - use module Xposed-mtc-manager- paragraph 7 - http://xdaforums.com/android-auto/mtcb-software-development/xposed-modules-units-t3263966
[MTCB Software Development] wdkrus:
Hmm, thanks, I'll try it. Maybe chinese developers reverted something related to brightness control in FW core.
[MTCB Software Development] agentdr8:
If anyone wants to test, I've made a few edits to see if XMTC will at least load in the newer firmwares. I commented out the mode switching, as the whole implementation would need to be rewritten, and MVG70's implementation seems like a good alternative.

Keep in mind that this is a super-alpha build, may crash/bootloop, and most likely won't do what everyone wants it to do. But I'd appreciate someone trying it out, with debug enabled, and post experience/logs here. I'm currently out of town, so I've no way to actually test it.

Please uninstall any previous versions of XMTC first before installing this one.
[MTCB Software Development] the-unknown:
Very nice App, hope the things you plan for the future will be there soon :) that are the things I am waiting for ;)

Is there a possibility to donate?

Gesendet von meinem Nexus 5 mit Tapatalk
[MTCB Software Development] agentdr8:
The future plans will most likely involve me open sourcing the project. I don't foresee having the time to maintain the module for much longer.

Thanks for the donation offering, but at this point, you may want to send it to a more actively-developed project.
[MTCB Software Development] agentdr8:
If this is with the previous (current "stable" release) version of the module, it's because it doesn't work with newer firmware. Try the alpha version I posted a few posts up and see if that works. If you can, enable debugging in the module preferences, and then post the Xposed Installer logs here.
[MTCB Software Development] vidalzone:
Hi friend!

I have installed the alpha but crashed when I try to start the app.... crash from app and from module... can you see the video:

[YOUTUBE]2dx8UTXqilc[/YOUTUBE]

Thanks for all ;)
[MTCB Software Development] the-unknown:
Oh....

Hope there will be someone then who will work on the app in the future.

Thanks than for a great basic :)

Gesendet von meinem Nexus 5 mit Tapatalk
[MTCB Software Development] agentdr8:
Thanks for the video. It's likely crashing on something I commented out.

I'll resume work on it this weekend, and try to get it to a semi-stable place.
[MTCB Software Development] vidalzone:
Thanks agentdr8! once works i will send you the logs ;) I will waiting for a new version
[MTCB Software Development] filegator:
NEW ver. xposed-mtc-music

New version of xposed-mtc-music from MVG-V70 __ 4pda.ru

- Minor bugs fixed

- New future added

The new future allows you to change duration of pop-up toast window

The pop-up window will show the album artwork works with modified players only.

There are two durations available short (approx. 2sec) and long (approx. 4sec)

Short is the default.

To change duration edit your mtc-music.ini file

[music]

# duration of pop-up window: long (~4sec) or short (~2sec), default short

toast.duration=long
[MTCB Software Development] Wolverine_DH:
Sorry can you get this player from 4pda.ru, i can not registry me!

http://4pda.ru/forum/index.php?showtopic=704299&st=2080#entry48910685

Thanks
[MTCB Software Development] vidalzone:
Hi agentdr8, some news??
[MTCB Software Development] LRail:
"it doesn't work with newer firmware"

What is considered "newer firmware" ?

Which firmware works correctly with the last stable version of XposedMTC?
[MTCB Software Development] masri1987:
I know it's a MTCB module,, but MTCD recently gained xposed ability... hoping to see this on MTCD
[MTCB Software Development] masri1987:
Anything I can do to help or encourage one to be developed for MTCD?
[MTCB Software Development] agentdr8:
Probably not. I don't have access to an MTCD device, and I haven't even finished updating it for the MTCB devices. I'll likely just open source the code any anyone who wants to take it (or pieces of it) can feel free to do so and modify it as they see fit.
[MTCB Software Development] royalhawk2002:
Any solution for the "Mode" SWC button rebooting the unit if pressed ? I can't enable the module because it will reboot the unit if the Mode button on SWC is pressed....
[MTCB Software Development] jbleasdale:
No and it seems unlikely to get fixed.

I suggest moving on to alternatives instead, for example using MTC-Keys for button re-mapping.
[MTCB Software Development] Tumke32:
Guys,

i recieved a new MTCB lollipop firmware from my reseller. My question is, is there already a new firmware released since the release of lollipop for MTCB devices? And is there a way to analyse the firmware in a tool to see if the sended firmware is for a MTCB device and if its for the good resolution etc? I thought i saw a tool for it this thread but i cant find it.

I don't want to brick my device..

edit: i found the tool, the rk3066 mod tool. I extracted the build.prob you can download it here https://drive.google.com/file/d/0B9a-tOFUEeEBb2JtTC1xenE4dlU/view?usp=sharing

I found this in the first lines:

ro.build.display.id=rk3188-userdebug 5.1.1 LMY48Y eng.root.20160718.203622 test-keys

ro.build.version.incremental=eng.root.20160718.203622

ro.build.version.sdk=22

Can we use it as a base?
[MTCB Software Development] royalhawk2002:
Ok the use of MTC-Keys for button remapping, but what about other functions, like the screen brightness automation ?
[MTCB Software Development] agentdr8:
[MENTION=6041319]dsa8310[/MENTION] had a script that used to handle auto brightness. Not sure if it still works, but probably worth a shot.
[MTCB Software Development] agentdr8:
As much as it pains me to not support something long-term, the time commitment just isn't viable at this point with everything else that I've got going on. Coupled with the new MTCB releases, and the refactoring involved, the best I can offer is the source code, and hope someone else takes it on or at least can use it as a starting point.

I'll post it up to my github when I'm back in town and link it on the OP.
[MTCB Software Development] jbleasdale:
Many thanks for this.

For the avoidance of doubt, I hugely appreciate the effort that you were able to put into this and suggesting alternatives wasn't meant to be a slight.
[MTCB Software Development] agentdr8:
No worries. I'm all for suggesting alternatives and hope something can take its place in the future.