Related
HI All,
im trying to make my steering wheel controls working my mkV 2009 Jetta SE. i retrofitted the steering wheel and as far as i can tell its coded correctly to the car.
however only one side of the steering wheel controls work with the android head unit. (the volume, and mute buttons). ive tried to set it up using the steering wheels control app and it doesn't seem to detect it.
At this point im not sure if its a canbus decoder error, a software issue or the coding of the wheel to the car.
does anyone with a mkV jetta have this working?
attached pics of the wheel and the canbus decoder which seems to be an RZ-07 by Raise.
any ideas?
Raptor
Hello
You can check in factory setting, that You have set canbus for you car. If you set and it will not help, You can use:
https://forum.xda-developers.com/an...ease-mtcdtools-control-music-players-t3436789
pitu120 said:
Hello
You can check in factory setting, that You have set canbus for you car. If you set and it will not help, You can use:
https://forum.xda-developers.com/an...ease-mtcdtools-control-music-players-t3436789
Click to expand...
Click to collapse
Thanks,it was set to VW&SKODA 01. i also tried everything related to VW and nothing changes.
i will try that other tool.
raptor_demon said:
Thanks,it was set to VW&SKODA 01. i also tried everything related to VW and nothing changes
Click to expand...
Click to collapse
Mate,
Have you updated your mcu to the latest one? If not yet, do it!
Ps: these cheapest canbus comes with the hu are not so perfect (one click sys and that's it!) , but the pac one is much much better and re-programmable.. unfortunately is expensive one!
Success.
:good:
BrGd
Madyen
Madyen said:
Ps: these cheapest canbus comes with the hu are not so perfect (one click sys and that's it!) , but the pac one is much much better and re-programmable.. unfortunately is expensive one!
Madyen
Click to expand...
Click to collapse
It is not the matter of any canbus decoder. The problem is inside MCU. Data sent from cabus decoder are received by MCU, then MCU through a serial port sends it to the MTCManager. It is 7 bytes frame, two last bytes are key code (unsigned short). MTCManager simply creates an intent, puts a key code and sends the intent through the broadcast.
Actually, MCU sends two types of key codes - irKey and HCTKey. HCT key codes are used in case of learning procedure (by factory settings app or by SWC Wheel app). Type of the key code depends on parameter rpt_key_mode (possible values are normal or key) set to the MCU via AudioManager. Learned key codes are stored in MCU - it is done by setting of the cfg_key parameter via AudioManager. For some reason, MCU sends HCT codes only for particular keys. It means that you are not able to change action of some SWC keys or panel keys, and some just simply do not work.
As you can see above - solution for the key codes done by the manufacturer is one big crap. AudioManager as an "communication bridge" with MCU - what the hell AudioManager has got to do with key codes ?
If some key codes do not work, it won't work until manufacturer (NOT THE RESELLER) fix this. And probably manufacturer will not fix this because no one know who is the manufacturer . Joying, Xtrons, Erisin and others are just resellers, they do not have access to the source code, so asking them for the fix is useless. It does not matter if you will buy an HU from Joying or from Xtrons - it will have the same bugs.
f1x said:
I it is done by setting of the cfg_key parameter via AudioManager. For some reason, MCU sends HCT codes only for particular keys. It means that you are not able to change action of some SWC keys or panel keys, and some just simply do not work..
Click to expand...
Click to collapse
So can i see whats coming from the car by looking at that cfg-key parameter?
how do i check my MCU version?MTCD_KGL_V1.87_1 is what the radio says.
Raptor
raptor_demon said:
So can i see whats coming from the car by looking at that cfg-key parameter?
Click to expand...
Click to collapse
Actually it is done by "Pannel Key Study" in Factory Settings. Factory Settings app read the value of this parameter, parse it and display on the screen as an icons grid. There is nothing to do with the "raw" value.
Edit:
Anyway, if you want to play with some "reverse engineering", some time ago I prepared an app to read data from serial port, lookup the keys broadcast and audio manager parameters.
Go to the "Lookup broadcast", press keys that do not work for you, and let me know if some digits appears on the screen.
If no, go to the "Set audio parameter" and type rpt_key_mode=key, then tap on set parameter. Then go to the "Lookup broadcast" and press keys that do not work for you once again, and let me know if some digits appears on the screen.
Afterwards set the rpt_key_mode=normal or just reset the device.
f1x said:
It is not the matter of any canbus decoder. The problem is inside MCU. Data sent from cabus decoder are received by MCU, then MCU through a serial port sends it to the MTCManager. It is 7 bytes frame, two last bytes are key code (unsigned short). MTCManager simply creates an intent, puts a key code and sends the intent through the broadcast.
Actually, MCU sends two types of key codes - irKey and HCTKey. HCT key codes are used in case of learning procedure (by factory settings app or by SWC Wheel app). Type of the key code depends on parameter rpt_key_mode (possible values are normal or key) set to the MCU via AudioManager. Learned key codes are stored in MCU - it is done by setting of the cfg_key parameter via AudioManager. For some reason, MCU sends HCT codes only for particular keys. It means that you are not able to change action of some SWC keys or panel keys, and some just simply do not work.
As you can see above - solution for the key codes done by the manufacturer is one big crap. AudioManager as an "communication bridge" with MCU - what the hell AudioManager has got to do with key codes ?
If some key codes do not work, it won't work until manufacturer (NOT THE RESELLER) fix this. And probably manufacturer will not fix this because no one know who is the manufacturer . Joying, Xtrons, Erisin and others are just resellers, they do not have access to the source code, so asking them for the fix is useless. It does not matter if you will buy an HU from Joying or from Xtrons - it will have the same bugs.
Click to expand...
Click to collapse
Mate,
Short story..
As you can read in my topic; bought xtrons.. that I xtrons not resented but the company one who sold the canbus to xtrons,
so why pac has no problems with the swc button at all then?
this means that PAC has a decent programmed the canbus decoder.. right?
with the PAC one you get no mcu file with it at all
Summary: buy a pac canbus
BrGd
Madyen
Madyen said:
Mate,
Shor story..
As you can read in my topic; bought xtrons.. that I xtrons not resented but the company one who sold the canbus to xtrons,
so why pac has no problems with the swc button at all then?
this means that PAC has a decent programmed the canbus decoder.. right?
with the PAC one you get no mcu file with it at all
Summary: buy a pac canbus
BrGd
Madyen
Click to expand...
Click to collapse
It is just an workaround. I suppose it is connected to the "key" wires. But why units for ~350$ need this?
f1x said:
It is just an workaround. I suppose it is connected to the "key" wires. But why units for ~350$ need this?
Click to expand...
Click to collapse
Asking them.. Not me!!
f1x said:
Actually it is done by "Pannel Key Study" in Factory Settings. Factory Settings app read the value of this parameter, parse it and display on the screen as an icons grid. There is nothing to do with the "raw" value.
Edit:
Anyway, if you want to play with some "reverse engineering", some time ago I prepared an app to read data from serial port, lookup the keys broadcast and audio manager parameters.
Go to the "Lookup broadcast", press keys that do not work for you, and let me know if some digits appears on the screen.
If no, go to the "Set audio parameter" and type rpt_key_mode=key, then tap on set parameter. Then go to the "Lookup broadcast" and press keys that do not work for you once again, and let me know if some digits appears on the screen.
Afterward set the rpt_key_mode=normal or just reset the device.
Click to expand...
Click to collapse
Thanks for this, what port and baud should I use?
raptor_demon said:
Thanks for this, what port and baud should I use?
Click to expand...
Click to collapse
You do not need this, because you do not need to read from the serial port. Just use "set audio parameters" and "lookup broadcast"
f1x said:
You do not need this, because you do not need to read from the serial port. Just use "set audio parameters" and "lookup broadcast"
Click to expand...
Click to collapse
Thanks, I set the audio parameter to key and I only get data when I push the buttons on the radio: com.hct.key.study 9136 is the phone hang up button for instance.
The steering wheel buttons report nothing, even the ones that work now (volume and mute)
Kinda strange
raptor_demon said:
Thanks, I set the audio parameter to key and I only get data when I push the buttons on the radio: com.hct.key.study 9136 is the phone hang up button for instance.
The steering wheel buttons report nothing, even the ones that work now (volume and mute)
Kinda strange
Click to expand...
Click to collapse
It means that irKey codes are hardcoded inside the MCU. There is no possibility to override/learn them. You just have to wait for the fix from the manufacturer (if any will be released).
Madyen said:
Mate,
Have you updated your mcu to the latest one? If not yet, do it!
Ps: these cheapest canbus comes with the hu are not so perfect (one click sys and that's it!) , but the pac one is much much better and re-programmable.. unfortunately is expensive one!
Success.
:good:
BrGd
Madyen
Click to expand...
Click to collapse
f1x said:
It means that irKey codes are hardcoded inside the MCU. There is no possibility to override/learn them. You just have to wait for the fix from the manufacturer (if any will be released).
Click to expand...
Click to collapse
Oh well, thanks for your help! i might try and arduino to read the keys and somehow change the head unit...
raptor_demon said:
Oh well, thanks for your help! i might try and arduino to read the keys and somehow change the head unit...
Click to expand...
Click to collapse
Have you tried to use MTCDTools? I have a Seat Leon (it is a spanish car from VW and use golf settings). The controls in the right side did not work, but with MTCDTools I can use them now.
paniqueado said:
Have you tried to use MTCDTools? I have a Seat Leon (it is a spanish car from VW and use golf settings). The controls in the right side did not work, but with MTCDTools I can use them now.
Click to expand...
Click to collapse
hi,
yes i did ,thanks, it didnt solve the issue
i wrote to the company that sold it to me and they said it wont work because those are supposed to contorl the car.
Raptor
Can anyone advise on how I could ho about changing the list of apps that gets started by the Mode function on my Xtrons unit (MTCD GS PX5 oreo)?
I know someone has done something similar with a Joying unit, but as far as I can see, they replaced the "Sofia-1-C9-Server... apk) with an alternative version.
I've pulled all the system apps to my PC via ADB (root) via WiFi, and I can see apps like MTCControlSettings.apk and MTCContolInfo.apk but there are no apks with "server" in their name
So I'm not sure where to start looking for the APK which handles the steering wheel control "Mode" handling.
Does anyone know how this is handled ?
are you able to resolve it? im having the same problem. btw my unit is a MTCE_CSN thanks
slidefriday said:
are you able to resolve it? im having the same problem. btw my unit is a MTCE_CSN thanks
Click to expand...
Click to collapse
I've not had time to investigate this.
For the moment, I've just set my Mode button to be the Home button, as thats better the cycling through a load of useless "modes" like the AV input and their useless audio and video players.
I did try to work out how the radio communicated with the system apps, but I'm having a lot of difficulty de-odex'ing (decompiling) even the radio app. Because the apps are Oreo versions, and most of the decompilers don't fully support Oreo odex (compiled application program) files
I did post a question to the general Dev part of XDA about de-odex'ing Oreo files but didnt get any responses
I would be interested in this if you figure it it out as I'd like to get dab in the list of apps it cycles through.
RogerClark said:
I've not had time to investigate this.
For the moment, I've just set my Mode button to be the Home button, as thats better the cycling through a load of useless "modes" like the AV input and their useless audio and video players.(
Click to expand...
Click to collapse
That would be enough for me, but with onboard apps or settings i haven't found a way to change it. I can use my Wheel control for changing volume and skipping music in any music app I am using, but the mode button always switches throug radio, ac input, mediaplayer and dvd.
The app for steering wheel control which was preinstalled on my head unit, doesn't react to any button and the firmware settings only to the hardware buttons of my head unit.
So, how did you do it?
nadkp said:
That would be enough for me, but with onboard apps or settings i haven't found a way to change it. I can use my Wheel control for changing volume and skipping music in any music app I am using, but the mode button always switches throug radio, ac input, mediaplayer and dvd.
The app for steering wheel control which was preinstalled on my head unit, doesn't react to any button and the firmware settings only to the hardware buttons of my head unit.
So, how did you do it?
Click to expand...
Click to collapse
In the Settings, ( think its in the Car) section, is the setting (app) which allows you to associate specific steering wheel buttons with specific actions.
I thought all generic units had this app, because the steering wheel button for each car operate differently.
My Subaru only has one wire from the steering wheel, and has 6 buttons. Each button has a different electrical resistance, and you have to press each button, and then associate a Short Press and a Long Press, on that button, to a specific action.
The controls like Volume + and - and Track + and - and Mute are pretty standard.
The only other button I have is the Mode button, and I assigned that to the "Mode" action in the settings. However the Mode operation, cycles though a predefined list.
So I simply reassigned the Mode button to the Home action.
I did try a few other things, like seeing if I could press 2 buttons at the same time e.g Mode and Track +, but it either treated this as a press on the Mode button or a press on the Track + button. So that didn't work.
If I get time, I'll have another go at decompiling the system apps, but last time I tried to do that, I could not see anything that looked like the list of apps.
If I had programmed it, I'd probably put the app names into a string resource, but goodness knows what the programmed did who wrote the system apps in these units.
RogerClark said:
In the Settings, ( think its in the Car) section, is the setting (app) which allows you to associate specific steering wheel buttons with specific actions.
Click to expand...
Click to collapse
Thanks for the quick reply. I already tried the factory settings but my steering wheel buttons won't work there. I only can set action to the buttons on my radio. Sadly I have to wait for any other solution. But thanks again for sharing your experience :good:
What brand and model of HU do you have?
Hey,
Opel/Vaux/Chevy cars have canbus hard mapped buttons.
Mine can't be configured through the in-built apps or factory settings either.
One would have to examine the canbus.apk / MTCManager to maybe update the xposed for MTCDTools.
MTCD Tools can see the button codes (3 digits), but can't map any other function or even intercept.
---------- Post added at 16:43 ---------- Previous post was at 16:43 ----------
Hey,
Opel/Vaux/Chevy cars have canbus hard mapped buttons.
Mine can't be configured through the in-built apps or factory settings either.
One would have to examine the canbus.apk / MTCManager to maybe update the xposed for MTCDTools.
MTCD Tools can see the button codes (3 digits), but can't map any other function or even intercept.
RogerClark said:
What brand and model of HU do you have?
Click to expand...
Click to collapse
I have a Xtrons PB78QSFP-B which is designed for a Ford Focus and came with a standard canbus adapter for ford. But I have the old model of the HU which has only 2GB Ram not 4.
My guess is, that Ford has hard mapped buttons too, like Xorit said it about Opel/Vaux etc
update guys! mtcdtools will do the trick! though the old mapping will flicker but still the newly assigned actions will prevail.
i can live with this already. maybe ill just find the solution to delete the factory set MODE actions :laugh:
slidefriday said:
update guys! mtcdtools will do the trick! though the old mapping will flicker but still the newly assigned actions will prevail.
i can live with this already. maybe ill just find the solution to delete the factory set MODE actions :laugh:
Click to expand...
Click to collapse
Did your have to root your unit or install anything like Xposed etc? Or does it just work with the stock firmware?
works with stock fw. im not yet doing any firmware mods
slidefriday said:
works with stock fw. im not yet doing any firmware mods
Click to expand...
Click to collapse
Good to know
Hey guys. About a year ago I installed a Teyes T-Pro in my '14 Focus ST, and while its better than the ST1 radio I had with a 4" screen, I hate this thing. An entire 1 inch vertical segment of the screen does not work, the screen does not turn on when the ambient temp is below 50 degrees F (until it heats itself up, takes like 25+ min in winter), subwoofer pre out doesn't work, and many many more stupid issues.
The reason I'm posting, though, is I would like to remap one of the steering wheel keys. The built in app to do this, of course, does nothing. Apps like button remapper also do nothing, probably bc the buttons function over CAN-Bus. When I press the microphone button on my steering wheel it opens an app called "car-info" which also does almost nothing. I am wondering if there is a way to have another app (google assistant) open right after this "Car-info" app opens. Also, if anyone has any experience with the T-Pro any input would be very appreciated. TEYES Tech support never responded to my multiple messages, of course, and I can't seem to find a head unit that sucks less and I don't want to roll the dice on another Teyes product.
Any input would be greatly appreciated...
Thanks a ton
Anyone got anything?
perrymike15 said:
Anyone got anything?
Click to expand...
Click to collapse
Contact TEYESAustralia, Hopefully they can give you a solution
What kind of car do you have (year, make, model, etc)?
Did you install the T-Pro yourself?
Do you have schematics for your car? If so, how do your steering wheel buttons connect to the old head unit?
Can you tell from the schematics if the buttons are resistive or not? Only resistive buttons can be remapped.
If your SWC are resistive, then you should be able to directly connect those buttons to the T-Pro inputs...I believe they are labelled key1 and key2. If the SWC are not resistive, I don't believe there is anything you can do about remapping them.
I've installed MTCE_GS_V3.01_3 head unit, and while steering wheel buttons work fine, the central panel buttons are no go.
I'm certain I've connected every cable that was connected on the original installation.
I've seen some suggestions on youtube to reset the panel button list, and then choose key study to add all buttons anew, however that does not help.
Right now Can bus type is set to 55 GM Simple, and that's probably the only one that works with steering wheel buttons.
I've tried changing knob type and other settings to no avail - I do full restart after the change, but when in key study no button press makes a difference.
Are there any suggestions what other settings should I try changing, or is there a way to check if a buttons press sends any signal at all?
You seem to be mixing/confusing steering wheel key assignment with the touch key assignments. These are two very different things. Canbus has nothing to do with the touch keys.
There is a touch sound setting that will cause the unit to beep every time one of the touch keys are touched. Please have a look at my instructional tutorial on how to set the touch keys:
How to reset the touch buttons instructional
This thread is not asking how to reset the touch buttons down the side of the panel screen. First go to Settings... Car.. Factory settings.. password 126 Then touch Key study category at the top Next Touch Key Study First the system will want...
forum.xda-developers.com
Hope this helps.
jlbooth said:
You seem to be mixing/confusing steering wheel key assignment with the touch key assignments. These are two very different things. Canbus has nothing to do with the touch keys.
There is a touch sound setting that will cause the unit to beep every time one of the touch keys are touched. Please have a look at my instructional tutorial on how to set the touch keys:
How to reset the touch buttons instructional
This thread is not asking how to reset the touch buttons down the side of the panel screen. First go to Settings... Car.. Factory settings.. password 126 Then touch Key study category at the top Next Touch Key Study First the system will want...
forum.xda-developers.com
Hope this helps.
Click to expand...
Click to collapse
I'm not sure we're talking about the same things, correct me if I'm wrong.
I'm talking about these buttons basically:
https://a.allegroimg.com/original/033b49/7f4f25564315ad7abd6afb6da117/PANEL-RADIA-OPEL-INSIGNIA-CD300-13273252
To my understanding (until now) they should be configured using Panel key study?
elmmm said:
I'm not sure we're talking about the same things, correct me if I'm wrong.
I'm talking about these buttons basically:
https://a.allegroimg.com/original/033b49/7f4f25564315ad7abd6afb6da117/PANEL-RADIA-OPEL-INSIGNIA-CD300-13273252
To my understanding (until now) they should be configured using Panel key study?
Click to expand...
Click to collapse
That looks like the control panel for the original radio.... and probably connected DIRECTLY to the original radio. Unless they operate through can bus, I don't think you can configure those.
I've seen them working on YouTube videos and such.
Agree with @Bob_Sanders on this. I was under the impression that it was just touch buttons off to one side of the head unit screen like many of these head units.
I suggest reaching out to the manufacturer of the radio with your question regarding the button panel.
elmmm said:
I've seen them working on YouTube videos and such.
Click to expand...
Click to collapse
Then it's possibly connected through can bus and you MIGHT get it working if you connect up your Key1 and Key2 wires and try the key study again.
I'm not sure if you have a can bus box on there already. If you do I'm not sure if you can run the box AND the key1/2 wiring at the same time. Try it though.
Bob_Sanders said:
Then it's possibly connected through can bus and you MIGHT get it working if you connect up your Key1 and Key2 wires and try the key study again.
I'm not sure if you have a can bus box on there already. If you do I'm not sure if you can run the box AND the key1/2 wiring at the same time. Try it though.
Click to expand...
Click to collapse
Can you clarify please what do you mean by "the box"?
Hello everyone.
I could not find a MTCE section and was unsure where to post, so I am posting this to the MTCD/MTCB/Android Head-Units threads. Sorry mods, please close or merge as you see fit.
I have a PX5 running Android 10. MCU version is MTCE_HXD_V3.62e_1 and would like to assign a phisical button (preferably a steering wheel button) to open TorquePro.
I found the remap function on factory options, but there are two problems with this:
First, only the volume buttons on my steering wheel show up on the buttons list, and not the "mode" button I wanted to use for this. Maybe this has something to do with CAN-Bus configurations? Or should I reset and map the buttons manually in order for them to show up? I think they all work. This "mode" button I don't use currently cycles between radio, media player and DVD and the skip track buttons also function as supposed, although being absent from the list.
Second, even if I forget about the steering wheel and try to map it to one of the buttons on the unit itself (like the DVD button I don't use) I can only map preset functions, like navigation, DVD, mute, etc. and not individual apps.
So I need either a third-party app that allows me to map Torque to a button, or a way to add torque to the mapable funcions on the factory options.
Any thougts on how to do this?
BTW, I tried MTCDtools but it doesn't seem to work. All I get from it is a "app keeps crashing" error message.
Thank you all!
Yes mtcE is an mtcD type. So you're in the right place.
All right, one step in the right direction. Yet MTCDtools didn't work. I installed the APK and it doesn't even open, all I get is a crashed app error message everytime I try starting it...
Any ideas what is going wrong here?
Have you tried the modified version 1.10, from AirOne70? #493
Not yet, just the one from f1x's GitHub. Will try it today. Thank you.
Pavel-71 said:
Have you tried the modified version 1.10, from AirOne70? #493
Click to expand...
Click to collapse
I have tried it, and it worked, so thank you!
Although it was just a partial success. I have a "source" button on my steering wheem which is used to cycle through radio/DVD/media player/etc. and managed to make it open Torque, like I wanted. The problem is that it also mantains the original function, so it launches Torque AND changes the media source on the same time.
I guess I need to "disconnect" the original functio. Any ideas on how to do this?
Thank you!
DC69 said:
I have tried it, and it worked, so thank you!
Although it was just a partial success. I have a "source" button on my steering wheem which is used to cycle through radio/DVD/media player/etc. and managed to make it open Torque, like I wanted. The problem is that it also mantains the original function, so it launches Torque AND changes the media source on the same time.
I guess I need to "disconnect" the original functio. Any ideas on how to do this?
Thank you!
Click to expand...
Click to collapse
Unfortunately, I can't help you with that, try reading the thread, maybe someone has already solved it.