Canbus problem with Xtrons (8core, 4gb ram, oreo)

Canbus problem with Xtrons (8core, 4gb ram, oreo) - Android Head-Units

Hi fellow xdeans,
I recently bought and installed one of the latest Xtrons units (specific for volkswagen). Its been two months and so far so good. Almost nothing to complain besides the usual - as read in other threads : Bluetooth loses connection sometimes and the internal mic isn't the best.
But one issue that is really bothering me is the can bus that works 5% of the time : i can then not count on the head unit to gather car info, but also to show if a door stayed open on the unit itself, and MOST IMPORTANTLY, the automatic screen brightness dimming (when headlights are on) + hardware buttons led's lighting up are not functional.
Do you guys know if there is a way to fix that (by replacing the can bus reader maybe?) ??
Additional question, how efficient are the usb connections when it comes to charge a phone, as I'm going to add usb3 extension cables).
To all, thanks very much in advance.

Anyone?

Can gateway coding
Make sure your CAN gateway is coded for Radio (digital)
I had the same issue: the head unit almost always got 1 frame of data when switched on (or key in slot), but only worked properly <5% of the time
If you have VCDS, it should have the long code helper, if not these should get you started:
7 byte CAN gateways: BYTE 04 (5th pair of hex digits)
9 byte CAN gateways: BYTE 05 (6th pair of hex digits)
10 byte CAN gateways: BYTE 05 (6th pair of hex digits)
bit mapping is the same for all:
0 Radio Digital
1 Radio Analogue
2 Telephone
3 Aux heater
4 Position Sensing
5 Operations
6 Instrument cluster
7 Can gateway (standard)
Example:
My CAN gateway (7 byte) required setting 1 bit (BYTE 4, bit 0):
BYTE 0 1 2 3 4 5 6
old code 3f fd 3c 06 c0 20 02
new code 3f fd 3c 06 c1 20 02
BYTE 4 (0xC0):
BIT num 7 6 5 4 3 2 1 0
old code 1 1 0 0 0 0 0 0
new code 1 1 0 0 0 0 0 1

Related

S160 - Android 4.4.4 Head Unit

Time to open a new thread, because I can't find anything about this new Pure Android 4.4.4 S160 HeadUnit.
I think there is much to discuss about this unit. Help me to complete this thread.
==============================================================================================================
After the arrival of the S100 and S150.... now there is the Android S160 Head Unit.
There are several companies that bring the S160 on the market:
RoadNav Software Manufacturer
Witson
etc..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
==============================================================================================================
Known issues so far:
Tested on model W2-M085
The errors from above appear only in version later than September 2015 for example:
Build number: rk3188-eng 4.4.4 KTU84Q eng.rks160.20151121.162340
Build number: rk3188-eng 4.4.4 KTU84Q eng.rks160.20151021.161502
==============================================================================================================
How to upgrade your firmware?
1 Download the RoadNav Android S160 firmware for your model here
2 Extract and Copy the files into the SD card and insert the SD card into the GPS Slot (it must be this slot)
3 Power OFF your radio (turn car key to OFF position)
4 Wait about 5-10 minutes for SRC light to go OFF
5 Hold the SRC button and turn car key to ON position. You should hear a beep, keep holding than it beep twice, then loose the source button.
6 Upgrade will start automatically.
7 After about 5 minutes a message at the bottom says Installation complete. BUT, that's not the end of the upgrade.
8 The radio screen goes black and beeps for 1 minute (this is normal, don't touch it !!)
9 After some more updates the "installation is complete please remove card"
10 Remove the SDcard and the radio automatically reboots.
==============================================================================================================
If this information was valuable.. press the Thanks button
Regards,
BockyWocky

Hi!
I agree. There is a huge amount of information on the S150, but alas, very little for the S160. I installed one of these in my Renault Megane 3 about a week ago and the first impressions are very good. Fits into the car perfectly and in the ROM and software in general seem quite stable. I installed Sygic which runs okayish with a few crashes every now and again. At the time of writing Sygic 15.5.9 is still quite fresh so I hope there will be some improvements in regards to stability in the foreseeable future.
The rest of the pre-installed software is fine and almost everything works out-of-the-box. The CAN bus adapter is also ok and I can see outside temperature, opening of doors, mute on reverse etc...
My only issue is with the Steering Wheel Controls. Volume UP and Volume DOWN as well as MUTE are working fine. My car has a Jog dial for skipping to the next / previous song and unfortunately this is not working. Also I cannot set any SWC button on the settings page. I read a couple of things about ADSet.xml but so far have no concrete idea how I could possibly get the jog dial to work. If anyone has ideas, help would be much appreciated.

janvantonder said:
Hi!
My only issue is with the Steering Wheel Controls. Volume UP and Volume DOWN as well as MUTE are working fine. My car has a Jog dial for skipping to the next / previous song and unfortunately this is not working. Also I cannot set any SWC button on the settings page. I read a couple of things about ADSet.xml but so far have no concrete idea how I could possibly get the jog dial to work. If anyone has ideas, help would be much appreciated.
Click to expand...
Click to collapse
Try to use "RK3066 HeadUnit", search on Play Store!

I just bought the S160 M049 for my Audi A3
As far as I can see there seems to be very information on this unit.
Looking to flash the firmware with root embedded if possible.

disk0360 said:
I just bought the S160 M049 for my Audi A3
Looking to flash the firmware with root embedded if possible.
Click to expand...
Click to collapse
You can do a request on the RoadNav forum
Could you all share what build number is installed on your device?

bockywocky said:
You can do a request on the RoadNav forum
Could you all share what build number is installed on your device?
Click to expand...
Click to collapse
here ya go
MCU Version
0151160.A
Build number
rk3188-eng 4.4.4 KTU84Q
eng.rks160.20151121.162340.WQ.TP000

OS Edition: S100-UNI.A20140721-B2.2
APP Edition: S100-V1.10.9.0P
MCU Edition: M0NP S00I C238
DVD Edition: 3200 V100 7706
BT Edition: ZH_2014/11/03_V06
CAN BUS:
OEM Info: A002
HELP ME *_*

maxetere said:
Try to use "RK3066 HeadUnit", search on Play Store!
Click to expand...
Click to collapse
using this will get the jog wheel to work? looking forward to buy this unit and the steering wheel controls ist a MUST!

Works for me!

M019 differences
Hi guys,
I keep finding units with different code names like M019 , M019-2 and M019-g . Does anyone know the differences between this devices ?
Thanks

Hi all,
Thanks for posting this. I have an S160 and have since found some issues, which I have some questions about:
Is everybody's WIFI terrible? Mine can not get wifi unless it is from my phone hot-spot sitting inside the car, and then it depends on where I place the phone inside the car, and then it will still drop out very often. Basically the WIFI is unusable.
Is there a fix for the terrible wifi? I was thinking I should use an external wifi dongle? Or can I install an external wifi antenna? Or is there a software fix?
Does anybody use an external 4G dongle? Which type?
The radio reception is terrible, is there a fix for this? I was thinking about an antenna booster.
In my car (2013 Ford Ranger) there is a button that says "Phone". When I press it, it tries to play music from my phone, but fails. I would rather have this button go to the phone bluetooth menu. How do I reprogram this button?
Mine uses BT 2.0, some things I want to pair with use BT4.0,
I haven't tried this as I haven't installed the 2nd monitor yet, but If I want to play a movie from the SD card or USB stick, can I send video and sound to the external monitor, and leave the normal interface on the main screen?
Is this the same as when I play a DVD?
Does anybody know of any custom interfaces, or how to customise the standard interface? What about removing the interface all together, and just customising the android UI the way I like it.
How can I change which screen/interface starts on boot, but still have the radio turn on?
Is there a way to speed up boot times?

I can't find the firmware for my unit on the RoadNav site, linked by OP. I can find my MCU version, but not the Model number
Further details of my unit:
To get in to the factory settings on mine, I go to the phone call screen and type "##0323"
Model:
M245-1
Kernal:
3.0.36+
[email protected]#1
Thu Aug 13 16:59:13 CST 2015
APP version:
Part 9 2015-07-31 10:50
MCU version:
01508310
Flash version:
A004
DVD Version:
3200
CAN BUS Version:
WAV2.02F00P
Build number:
rk3188-eng 4.4.4 KT084Q
eng.rks160.20150824.174135

Just installed mine into an ix35 with canbus (digital ampifier and sub onboard).
First impressions - works well. Boot times are long, a couple of issues with the aux in and usb, but I think those are an issue with the car's wiring, because the aux in was flakey with the stock headunit too.

rapboyhed said:
Hi guys,
I keep finding units with different code names like M019 , M019-2 and M019-g . Does anyone know the differences between this devices ?
Thanks
Click to expand...
Click to collapse
The M number refer to the model for your car brand.
S/N Model No. Fit for car Available for production Web Link
1 M001-1 Nissan universal OK www.Roadnavi.com/M001-1
2 M003I-2 Ford Mendeo, Focus 2007-11 OK www.Roadnavi.com/M003
3 M005I Skoda Octavia OK www.Roadnavi.com/M005
4 M006-1 Hyundai Azera <2011 OK
5 M008I Hyundai Santa Fe OK www.Roadnavi.com/M008
6 M009I Honda CRV OK Roadnavi.com/M009
7 M010-1 Toyota General OK www.Roadnavi.com/M010
8 M012 Mazda 6 OK www.Roadnavi.com/M012
9 M015 Cherry A5 OK
10 M016-HJ Honda Jazz, CR-V, City, Fit, Odyssey, Civic, 97-06 OK www.Roadnavi.com/M016HJ
10 M016-1 VW Passat B5 w/o can OK www.Roadnavi.com/M016
11 M016-2 VW Passat B5 w can OK
12 M017-2 Peugeot 307 OK
13 M018I Toyota RAV4 OK
14 M019-2 Opel Astra H OK www.Roadnavi.com/M019
15 M020I-2 Chevrolet Captiva OK www.Roadnavi.com/M020
16 M021 GMC/Chevy OK www.Roadnavi.com/M021
17 M023-1 Kia Series OK www.Roadnavi.com/M023
18 M024I-1 Hyundai I30 low version OK
19 M034I Mazda 3 OK www.Roadnavi.com/M034
20 M035 Toyota Highlander OK www.Roadnavi.com/M035
21 M037 Mitsubishi Lancer OK www.Roadnavi.com/M037
22 M043I-1 Hyundai I30 High version OK
23 M044-2 Honda Civic OK www.Roadnavi.com/M044
24 M045 Chevrolet Cruze OK www.Roadnavi.com/M045
25 M047-2 Hyundai IX35 2.0L 2.4L OK
26 M053I Suzuki Vitara OK
27 M062-1 Subaru Forester OK www.Roadnavi.com/M062
28 M065 Toyota Prado 2010 OK
29 M067I Hyundai Verna/Accent OK
30 M068I Mercedes A/B OK
31 M071 Toyota General OK
32 M074-1 Kia Sportage R OK
33 M075-2 Hyundai Sonata OK
34 M086 Kia Ceed OK
35 M087 Benz Smart Fortwo OK
36 M091 Kia K5 Optima OK
37 M092-2 Hyundai Elantra3 OK
38 M093I Mercedes C Class OK
39 M096I Mercedes SLK OK www.Roadnavi.com/M096
40 M097I-1 Mazda CX7 OK www.Roadnavi.com/M097
41 M106-1 Kia K2 public OK
42 M107 Chevrolet Aveo public OK
43 M111I-1 Honda CRV 2012 OK www.Roadnavi.com/M111
44 M115 Cherry Ruihu OK
45 M124 Isuzu SX4 OK www.Roadnavi.com/M124
46 M131 Toyota Camry 2012 OK
47 M131-1 Toyota Camry 2013 JBL function OK
48 M132 Honda Civic OK
49 M133 Toyota Verso OK
50 M140-1 Ford Old focus public OK www.Roadnavi.com/M140
51 M148 Ford Exploer OK
52 M153 Toyota Camry 2012 USA OK www.Roadnavi.com/M153
53 M158-1 Ssangyoung Actyon/Kyron OK
54 M159 Ssangyoung Korando OK
55 M171I Benz old C class OK
56 M172I Hyundai I40 OK
57 M179 SUZUKI SWIFT OK
58 M196 Nissan Slphy OK
59 M198I Lifan X60 OK
60 M202 Chrysler Sebring OK www.Roadnavi.com/M202
61 M203 Chevrolet colorado / s10 OK
62 M204I KIA Rio OK
63 M209 Hyundai IX45 OK www.Roadnavi.com/M209
64 M212 Mazda CX5 OK
65 M213 Mecerdes SLK OK
66 M215 Mecerdes R class OK
67 M216I Kia Ceed 2013 OK www.Roadnavi.com/M216
68 M220I Mecerdes S class OK www.Roadnavi.com/M218
69 M222 Ford F150 OK
70 M223 Mazda CX5 OK www.Roadnavi.com/M223
71 M230I Mitsubishi Outlander 2013 OK
72 M231I GMC Yukon 2013 OK
73 M232I Ford Ecosport OK www.Roadnavi.com/M232
74 M233 Hyundai H1 OK www.Roadnavi.com/M233
75 M246I Seat Ibiza OK
76 M247I Toyota RAV4 2013 OK
77 M249-1 Hyundai IX35 OK
78 M250 Fiat Bravo OK
79 M252 Jeep Compass OK
80 M259-3 Hyundai Sonata 8inch OK
81 M278 Kia Carens 2013 OK
82 M279 Skoda Octavia 2013 OK
83 M284 GMC Alcadia OK www.Roadnavi.com/M284
84 M305-2 VW Sagitor OK www.Roadnavi.com/M305
85 M307 Toyota Corolla 2013r OK
86 M309 Chev Trax OK
87 M325-1 Kia Sportage 2013r OK www.Roadnavi.com/M325
88 M327 Fiat Strada OK
89 M332I Chev Spin OK
90 M337I Suzuki SRS OK
91 M345I Kia Optima OK
92 M347I Toyota Prado 2014 OK
93 M353-1 Nissan Qashqai 2014 OK www.Roadnavi.com/M353
94 M359I Hyundai Elantra 2014 OK
95 M360 Hyundai Elantra 2012 OK
96 M361-1 Hyundai Tucson 2015 OK
97 M370-2 VW OK
98 M385 Kia K3 RHD OK
99 M417 Hyundai Sonata 2015 OK
100 M026-1 Mitsubishi ASX 20 days lead time
101 M028 Toyota Auris 20 days lead time
102 M030 Hyundai I20 20 days lead time
103 M038 Kia Forte 20 days lead time
104 M041-2 Kia Soranto 20 days lead time
105 M042 VW Touareg 20 days lead time
106 M046 Kia Cerato 2010 20 days lead time
107 M049 Audi A3 20 days lead time www.Roadnavi.com/M049
108 M050 Audi A4 20 days lead time
109 M052-1 BMW E46 20 days lead time
110 M056I Mitsubishi Outlander 20 days lead time
111 M061-3 Subaru Lagecy 20 days lead time
112 M063 Toyota Altis/ Corolla 20 days lead time
113 M064 Toyota Camry 20 days lead time
114 M066 Rongwe 350 20 days lead time
115 M072 Opel Astra J 20 days lead time
116 M076 Kia Soul 20 days lead time
117 M078 AUDI TT 20 days lead time
118 M082 BMW E39 20 days lead time
119 M085 Peugeot 206 20 days lead time
120 M088 Citroen C4 20 days lead time
121 M090 Mercedes E class 20 days lead time
122 M094 Mitsubishi L200 High 20 days lead time
123 M094-1 Mitsubishi L200 Low 20 days lead time
124 M095 BMW E90 20 days lead time
125 M098 Megane II 20 days lead time www.Roadnavi.com/M098
126 M102 Audi A6 Old 20 days lead time
127 M104 Hyundai Azera 2012 20 days lead time
128 M109-1 Chevrolet Captiva 2012 public 20 days lead time
129 M112 BMW E90 MAC 20 days lead time
130 M117 Mazda 5 20 days lead time
131 M143 Toyota New Hulix 20 days lead time
132 M145 Megane III(The new one) 20 days lead time
133 M146 Toyota Yaris 20 days lead time
134 M150 Ford Focus 2012 20 days lead time
135 M151 Peugeot 405 20 days lead time
136 M154 Nissan Patrol 20 days lead time
137 M155 Chev Orlando 20 days lead time
138 M157 Renault Duster 20 days lead time
139 M161 Mazda 3 old 20 days lead time
140 M169 Chev Malibu 20 days lead time
141 M170 BMW E class 20 days lead time
142 M182 Toyota Landcruizer 20 days lead time
143 M217 Kia Picanto 20 days lead time
144 M218 Kia Soul 2012 20 days lead time
145 M224 Sorento 2013 20 days lead time
146 M227 Ford Exploer 2013 20 days lead time
147 M228 Ford Taurus 2013 20 days lead time
148 M234 Toyota Etios 2013 20 days lead time
149 M235 Opel MOKka 20 days lead time
150 M236 Ford Kuga 20 days lead time
151 M237 Kia Cadenza 2012 20 days lead time
152 M238 Holden Comodore/Chevrolet Caprice 20 days lead time
153 M239 Hyundai HB20 20 days lead time
154 M241 Citroen C4L 20 days lead time
155 M242 Nissan Teana/Altima 20 days lead time
156 M245-1 Ford Ranger 20 days lead time
157 M254 Ford Explorer 2013 20 days lead time
158 M263 Jeep Grand CherOKee 20 days lead time
159 M269 Ssangyoung Lester 20 days lead time
160 M274 Nissan Livina 20 days lead time
161 M276 Ford Taurus 2013 20 days lead time
162 M279-1 Skoda Octavia 20 days lead time
163 M280 Kia K3/Cerato 20 days lead time
164 M286 Dodge RAM1500 20 days lead time www.Roadnavi.com/M284
165 M294-3 Peugeot 301 20 days lead time
166 M308 Toyota Auris 2013r 20 days lead time
167 M317 Toyota Yaris 2014 20 days lead time
168 M323 Peugeot 3008 20 days lead time
169 M324 Honda Pilot 20 days lead time
170 M342 Ford Taurus 2011 20 days lead time
171 M352 Toyota Corolla 2014r 20 days lead time
172 M355 Ssangyoung Korando 20 days lead time
173 M362 Ford Kuga 20 days lead time
174 M374 Peugeot 2008 20 days lead time
175 M379 Opel Vectra 20 days lead time
176 M380 Toyota Venza 20 days lead time
177 M381 Toyota Landcruiser 20 days lead time
178 M383 Honda Fit 2013 20 days lead time
179 M395 BMW E39 8 inch 20 days lead time
180 M396 Honda City 2014 RHD 20 days lead time
181 M414 Seat Ibiza 2014 20 days lead time
182 M422 Honda HRV/Vezel 2014 20 days lead time
183 M424 Toyota Avalon 2014 20 days lead time
184 M435 SUKUZI D-MAX 20 days lead time
185 M439 VW FOX 20 days lead time
186 M439-1 VW Lamando 20 days lead time
187 M442 Kia Sorento 2014 20 days lead time
188 M802 2 Din universal 20 days lead time
189 M804 2 Din universal 20 days lead time
Under developing models which will come in next few months.
S/N Model No. Fit for car Status
1 M229 Ford Edge Under developing
2 M255 Ford Edge Under developing
3 M393 Ssangyoung Rodius Under developing
4 M409 Kia Cadenza 2014 Under developing
5 M267 Ford F150 2013 Under developing
6 M306 Seat Leon 2013 Under developing
7 M394 Peugeot 406 2013 Under developing
8 M219 BMW X1 Under developing
9 M257 VW Golf 7 Under developing
10 M316 Citroen C3 Under developing
11 M331 VW Gol 2013 Under developing
12 M207 Peugeot 207 Under developing
13 M378-1 Chev Insignia 2013 Under developing
14 M392 Citroen Aircross 2013 Under developing
15 M138 Renault Meganne II Under developing
16 M315 Fiat 500 2011-2015 Under developing
17 M329 Renault Kleo 2014 Under developing
18 M101 Honda City 2012 Under developing
19 M163 Citroen C4 Under developing
20 M164 Citroen C5 Under developing
21 M190 Peugeot 308 Under developing
22 M257-1 VW Golf 7 Under developing
23 M433-1 Honda City Left 2013 Under developing
24 M445 Toyota Highlander 2015 Under developing
25 M023I-2 Kia Series Under developing
Thanks to RN_Tao from RoadNav !

nwitham said:
I can't find the firmware for my unit on the RoadNav site, linked by OP. I can find my MCU version, but not the Model number
Click to expand...
Click to collapse
Ask for an original firmware from your store.
Then only replace the sdupdate.img with every other later version dowloaded from Roadnav and see if this will fix some of your issues.
Please be patient.
New Stable Firmwares for S160 are due to be posted in March.
Regards,
BockyWocky

bockywocky said:
Ask for an original firmware from your store.
Then only replace the sdupdate.img with every other later version dowloaded from Roadnav and see if this will fix some of your issues.
Please be patient.
New Stable Firmwares for S160 are due to be posted in March.
Regards,
BockyWocky
Click to expand...
Click to collapse
I added a request to their request thread, so will see what comes up.
What features can I expect in the march updates?

nwitham said:
I added a request to their request thread, so will see what comes up.
What features can I expect in the march updates?
Click to expand...
Click to collapse
I really don't know.
I'll also let surprise myself

bockywocky said:
The M number refer to the model for your car brand.
Click to expand...
Click to collapse
Thanks for the reply @bockywocky but I was talking about M019 in particular, I keep finding different model on different markets various M019 models. By the way , maybe you guys can help me , I was talking to RN_Tao the other day about the fact that my car is an Opel Vectra C 2004 HALF CAN , will the roadnav product m019-2 work on my car without any other adapters ? , in the last email he suggested an SWC interface solution and offered an website . Do you guys know more about this kind of stuff ? .
Now I got a half can radio NCDC 2015.

Does anybody know how to get root on it?
I just bought M362 (Ford Kuga II) and want to tranfer some apps from phone (via TitaniumBackup, so need root). Tried Baidu, Farma and etc - no result.
BTW, M362 have too much bugs. Ford SYNC have no sound at all, cannot re-assign buttons on DVD dashboard (there is app only for steering wheel resistant buttons, dashboard buttons keykodes goes by CAN BUS).

root?
guys, have anyone found a way how to root the unit? I have received fw update from my seller but after flashing that fw I can't install some apps that I had on previous fw, getting error code 24. Need to root and remove residual files from previous version. Any advice please?
cheers

Eonon MTCD causing drain in Audi a3

Hi all,
My car is a 2008 audi a3 8p with BOSE
I am having the age ole battery drain problem... and I wonder if anyone has any solutions
The car comes with an OEM Symphony II+ radio - no navigation which works with no problems
I installed the EONON ga6157f which is supposed to be for this car:
http://www.eonon.com/Android-Car-GPS...S/GA6157F.html
This has built in CANBUS decoder and everything on it works well except for the battery drain...
I have turned dip switch III off that is meant to solve the battery drain, but no luck...
Just did a VCSD scan and found these two particular faults... I wonder if there anything that anyone can say that will help...
cheers
gB
CANBUS not working properly:
Address 19: CAN Gateway Labels: 1K0-907-530-V3.clb
Part No SW: 1K0 907 530 L HW: 1K0 907 951
Component: J533__Gateway H15 0180
Revision: H15 Serial number: 1400K0762785FC
Coding: ED827F070003022102
Shop #: WSC 06314 000 00000
VCID: 307707133A23A682AF80C65-8064
1 Fault Found:
00469 - Infotainment Databus in Single Wire Operation
012 - Electrical Fault in Circuit
Freeze Frame:
Fault Status: 01101100
Fault Priority: 3
Fault Frequency: 1
Reset counter: 172
Mileage: 150791 km
Time Indication: 0
Date: 2016.12.26
Time: 21:05:59
RADIO CANNOT BE REACHED:
Address 56: Radio
Cannot be reached

Help for others
This may help other people
http://wiki.ross-tech.com/wiki/index.php/Navigation_System_(RNS510)_Retrofitting

PhopsonNY said:
This may help other people
http://wiki.ross-tech.com/wiki/index.php/Navigation_System_(RNS510)_Retrofitting
Click to expand...
Click to collapse
Definitely a canbus compatility issue.
I may have a working solution
Sent from my SAMSUNG-SM-N910A using Tapatalk

Here is the possible solution
Battery drain Canbus H Relay cut solution
Any thoughts?

Droid Head Unit Discussion

This thread is really to help me choose which Android 8.X head unit to install in my Nissan 370z but I am running into some unanswered questions that I really want answered in order to make the right decision. I already did some research and I am cutting and pasting that down below from another forum. Hopefully in the process this could help others decide on a double din Andriod 8.X HU.
With that said my questions:
1) Has anyone been able to figure out what the preamp voltage is for these units? In my research literally only 2 companies have posted there voltage and not for all of there units. For example Joying...I only saw the voltage for one of the units which was 2 volts but ATOTO on the other hand states most of the late/New units have 4 volts. All other brands don't mention a thing.
2) Do these built in DSP's actually make a difference or is it marketing?
3) Would I need an adapter for the 370 z to keep steering wheel controls?
4) Is there a way to modify an ATOTO A6 with gesture for example to use a 15 band EQ as apposed to the stock 10 band?
5) Can you use any USB DVD/CD player with these units to play music? Or does it have to be a specific one? I ask cause I have a USB DVD player laying around.
6) Does anyone know what the audio frequency response is for the units mentioned below?
Research:
I decided to share my research with the community to save others time that I clearly invested way to much of looking into the right setup. Here is some data I accumulated while comparing all the Android OS based head units. Note I was only looking for head units with Android 8 or above & I leaned towards the units with no buttons when available due to ascetics so this is not an end all be all list.
Note: the following head units have the following in common unless otherwise pointed out...Android 8, DVR & Reverse Camera options, OBD scan tool option, iPhone Mirror, 4 GB of Ram, WiFi Hot spot, Resolution of 1024x600, and RGB Buttons.
1) Xtrons TE706PL:
- Audio Frequency Response 30-15000Hz
- 4 volt PreOut UNKNOWN
- Split screen multitasking
- 2 yrs of warranty
- NO 5 GHz WiFi
- External DVD option UNKNOWN
- Reviews (Amazon 3.5 stars)
2) Seicane H203G:
- Audio Frequency Response 42-20000Hz
- 4 volt PreOut UNKNOWN
- NO Split screen multitasking
- Warranty UNKNOWN
- 5 GHz WiFi UNKNOWN
- External DVD option
- Reviews...None I would consider reliable
3) Pumkin ND0289B:
- Audio Frequency Response UNKNOWN
- 4 volt PreOut UNKNOWN
- UNKNOWN Split screen multitasking
- Warranty UNKNOWN
- 5 GHz WiFi UNKNOWN
- NO External DVD option
- Reviews (Amazon averages between 3.5 & 4 starts)
4) iDoing HTTY031:
- Audio Frequency Response UNKNOWN
- 4 volt PreOut UNKNOWN
- Split screen multitasking
- Warranty UNKNOWN
- 5 GHz WiFi UNKNOWN
- UNKNOWN External DVD option
- Reviews...None I would consider reliable
5) ATOTO A6YPro-G (Model number truncated):
- Audio Frequency Response UNKNOWN
- Only unit to CONFIRM 4 volt PreOut
- Only 2 GB of RAM
- UNKNOWN Split screen multitasking
- Warranty UNKNOWN
- 5 GHz WiFi CONFIRMED
- UNKNOWN External DVD option
- Only unit to have gesture controls
- Reviews Amazon 4 stars
6) Android AutoShop XV8 7 inch:
- Audio Frequency Response UNKNOWN
- 4 volt PreOut UNKNOWN
- Split screen multitasking
- Warranty 1 yr
- 5 GHz WiFi UNKNOWN
- UNKNOWN External DVD option
- Dedicate DSP chip
- Reviews...None I would consider reliable but they run out of Europe and source Chinese head units
7) Eonon GA2171S:
- Audio Frequency Response UNKNOWN
- 4 volt PreOut UNKNOWN
- Split screen multitasking & Picture in Picture
- Warranty 2 yrs & 60 day money back guarantee
- 5 GHz WiFi UNKNOWN
- NO External DVD option
- Dedicate DSP chip
- Reviews Amazon 4 stars
8) Joying JY-UO128N4G:
- Audio Frequency Response UNKNOWN
- 4 volt PreOut: Note some of the units state 2 volts & a youtuber tested one of the new 10 inch models and actually got 1.2 volts
- Split screen multitasking
- Warranty 2 yrs
- 5 GHz WiFi UNKNOWN
- NO External DVD option
- Dedicate DSP chip
- Reviews Amazon 4.5 stars
It is also worth noting that Joying has come out with some new units with SPDIF interfaces for better sound quality & intel processors but those units would need to be ordered directly from the China warehouse.
What you see above is a combination of whats on various websites and even some emails to the vendors. It may not be 100% accurate but it's the only place you will see all this info in one spot as far as I am aware. If any of the info is incorrect please let me know and I will correct it on this page but make sure to post a link to the info for reference.
Thanks!

Bump

Anyone :laugh:

YT9218c 8227L Steering Wheel Controls and CANBUS hardware support

Hi All,
I have a 10.1" Android Head Unit and it has two wires for steering wheel control. I thought this unit had CAN or CANBUS capabilities but its Key 1 / Key 2 for the steering wheel controls.
How do other units interface the CAN BUS?
What hardware do they use?
Is it standard SLCAN (can over serial) or native can0?
Does can-utils work on other units?
I'm looking at adding the hardware myself if it uses some kind of common hardware.
My car (Mazda 3) and a friends (Volvo XC90) have the steering wheel controls on the CAN bus.
My plan was to code together a canbus to SWC but if I can get native CAN on the device that would be great.
I2C, SPI, USB, Serial... do we know anything about the chips used for decoding the CAN?
I'd really like something and I will do hardware and program code as long as it's not java!
YT9218C_AHD_00005_V004_20190522_HIFI
Android 6.0 kernel 3.18.22
no canbus-V4.7.2-disconnect
A7 1.3GHz x 4
NXP6851
AC7315 45W x 4
1024*600
HW8227L-3.3-SW0-3.1
Thanks for any info,

O.i.D said:
Hi All,
I have a 10.1" Android Head Unit and it has two wires for steering wheel control. I thought this unit had CAN or CANBUS capabilities but its Key 1 / Key 2 for the steering wheel controls.
How do other units interface the CAN BUS?
What hardware do they use?
Is it standard SLCAN (can over serial) or native can0?
Does can-utils work on other units?
I'm looking at adding the hardware myself if it uses some kind of common hardware.
My car (Mazda 3) and a friends (Volvo XC90) have the steering wheel controls on the CAN bus.
My plan was to code together a canbus to SWC but if I can get native CAN on the device that would be great.
I2C, SPI, USB, Serial... do we know anything about the chips used for decoding the CAN?
I'd really like something and I will do hardware and program code as long as it's not java!
YT9218C_AHD_00005_V004_20190522_HIFI
Android 6.0 kernel 3.18.22
no canbus-V4.7.2-disconnect
A7 1.3GHz x 4
NXP6851
AC7315 45W x 4
1024*600
HW8227L-3.3-SW0-3.1
Thanks for any info,
Click to expand...
Click to collapse
Hi, I have same version of software as you. My HU have a "Raise" CAN bus adapter/converter and wires SWC1 and SWC2 on iso audio connector are out, then i suspect it take steering wheel controls orders form canbus.
Canbus adapter are wired on connector [ C ] of head unit, see next draw
[ A ][ B ]
[ C ][D][ E ][ F ]
https://cs5-1.4pda.to/15659740.jpg
https://cs5-1.4pda.to/15659744.jpg
I'm a beginner with canbus, without knowledge about it, but very interested.
---------- Post added at 05:26 PM ---------- Previous post was at 05:10 PM ----------
Here a picture of a similar device and wires.
https://es.aliexpress.com/item/3294...chweb0_0,searchweb201602_1,searchweb201603_52

t3l3m4k0 said:
Hi, I have same version of software as you. My HU have a "Raise" CAN bus adapter/converter and wires SWC1 and SWC2 on iso audio connector are out, then i suspect it take steering wheel controls orders form canbus.
Canbus adapter are wired on connector [ C ] of head unit, see next draw
[ A ][ B ]
[ C ][D][ E ][ F ]
https://cs5-1.4pda.to/15659740.jpg
https://cs5-1.4pda.to/15659744.jpg
I'm a beginner with canbus, without knowledge about it, but very interested.
---------- Post added at 05:26 PM ---------- Previous post was at 05:10 PM ----------
Here a picture of a similar device and wires.
https://es.aliexpress.com/item/3294...chweb0_0,searchweb201602_1,searchweb201603_52
Click to expand...
Click to collapse
Hi!
Thanks for the information! I will check today and see if I have any connection on the CAN pins.
I've been poking about the factory setting and seeing the different cars and in car supported systems. Really interesting.
Hopefully the pins are connected to a can controller.
Regards,

other link with wired canbus decoder wired.
https://es.aliexpress.com/item/32904642849.html?spm=a219c.12057483.0.0.1a531be3TWLwde

On factory settings, there is a option (https://4pda.ru/forum/dl/post/15184101/Screenshot_20190128-030741.png) "Canbus information" that shows some bus messages like this: https://dl.xda-developers.com/4/7/5/1/6/2/7/03.jpg?key=pjd1FmblWQjFmFe11abA6A&ts=1564507515

Thanks for the info. I've been poking around with the oscilloscope and a CAN bus tool but nothing. I'm wondering if it's actually serial transmission instead of can but all the other pins match 100% with my unit.
Are you from Spain, since the links are in Spanish?
Ah... I really want to know how these CAN decoders work! Do they decode the CAN and send as Serial? Or do they filter CAN messages?
Sorry, can't see the last link, Error 401!
I'll go look for more info on these decoders. For now my oscilloscope is showing nothing and the can sniffer is silent!
Thanks!

Ok, looks like I found something.
On the 8 pin connector "C" when I go through the list of "decoder protocols" the message changes as well as the baud rate.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On the 6 pin connector "E" it looks like it spits out serial data during boot on the "CAN" pins.
The device lists a dev/tty, ttyGS0 to ttyGS7, ttyMT0 to ttyMT4, ttyS0 to ttyS3, ttyp0 to ttypf. So lot's of ports to try.

Yes, I come from Spain.
I suspect my canbox converts canbus signals to serial levels and filter messages.
Probably devices to monitor are ttySX. Have you rooted your device?
This is the previous broken link
https://forum.xda-developers.com/showpost.php?p=79443358&postcount=62
There is no much info about this canbox converters.
https://forum.xda-developers.com/android-auto/mtcd-hardware-development/canbox-versions-t3763383

t3l3m4k0 said:
Yes, I come from Spain.
I suspect my canbox converts canbus signals to serial levels and filter messages.
Probably devices to monitor are ttySX. Have you rooted your device?
This is the previous broken link
https://forum.xda-developers.com/showpost.php?p=79443358&postcount=62
There is no much info about this canbox converters.
https://forum.xda-developers.com/android-auto/mtcd-hardware-development/canbox-versions-t3763383
Click to expand...
Click to collapse
In that case, Hola!
Thanks for the info. I've poked around the threads and have made a post over at https://forum.xda-developers.com/showpost.php?p=79991391&postcount=61. Hopefully they can provide some more details as it looks like they have also been looking into CANBUS-MCU communications.
Today I will try to setup some serial terminals instead of the oscilloscope and logic analyzer to check try and find the ttySx ports.

Status update.
Connector "E" CanL is RX and CanH is TX. TTL 3.3V 912600baud N/8/1. This spits out a long stream of information during boot;
Code:
Some serial data:[HIDE]
RM2 BC] ERROR BCCustomEntry MetaZonebufRead[312]=0
RM2 BC] ERROR BCCustomEntry MetaZonebufRead[313]=0
RM2 BC] ERROR BCCustomEntry MetaZonebufRead[314]=0
RM2 BC] ERROR BCCustomEntry MetaZonebufRead[315]=0
RM2 BC] ERROR BCCustomEntry MetaZonebufRead[316]=0
RM2 BC] ERROR BCCustomEntry MetaZonebufRead[317]=0
RM2 BC] ERROR BCCustomEntry MetaZonebufRead[318]=0
RM2 BC] ERROR BCCustomEntry MetaZonebufRead[319]=0
SS][arm2] DpEngine_COLORonInit
EDS]ARM2: mt65xx_backlight_on
RM2 Dualarm] backcar_dualIsr Start!
RM2 BC] INFO ARM2 Detect Android Ready
RM2 BC] INFO arm1 is ready, close arm2 backcar!
RM2 BC] INFO arm2 notify arm1 arm2 will exit
RM2] Sleep!
[/HIDE]
Code:
Cleaner output:[HIDE][ARM2] ARM2 Cmain enter++
[ARM2 Dualarm] temp_offset = 0x40000 , g_u4Arm2MemoryOffset 0x90000000
[ARM2 Dualarm] g_u4MemorySize 0x40000000
[ARM2] ARM2 get ADDr ++
[ARM2 Dualarm] ARM1PHY2ARM2UCV u4ARM1phyadress: 0x93400000
[ARM2] _pArm2Log: 3400000;_uArm2LogSize 180000
[ARM2] arm2 start time get_timer(0) = 707,TickCount = 0
![ARM2] power mode: 0x82278227
[ARM2] Power mode: normal!Show logo at main loop task
[ARM2 Dualarm] ARM1PHY2ARM2UCV u4ARM1phyadress: 0x90F00000
[MTZ][ARM2] Metazone init success. The dword index 0x10001 value is (22B)
[DSS]disp_path_ddp_clock_on
[DSS]DISI_MODULE_DPI0
[BLS] bls mutex check(0x688)
[BLS] disp_bls_init : srcWidth = 1024, srcHeight = 600
[BLS] disp_bls_init : BLS_EN=0x10000, PWM_DUTY=409, PWM_DUTY_RD=1023, CG=0xFFF00000
[BLS] disp_bls_config_full, width=1024, height=600, reg=0x2580400
[DSS][arm2] DpEngine_COLORonInit
[ARM2] Task num [2]
[ARM2 BC] INFO ARM2 VER is 01-02-01
[ARM2 BC] INFO BackCar_Init +, at TickCount (58)
[ARM2 BC] INFO normal boot
[ARM2 BC] INFO mdp_from_metazone enter
[ARM2 BC] INFO mdp is enable
[ARM2 BC] INFO rotation is 0, video rect is (0,0,1024,600)
[ARM2 BC] INFO mdp_from_metazone exit
[ARM2 BC] INFO before CustomUIInit
[ARM2 BC] INFO using gpio pin: 51
[ARM2 BC] INFO backcar_frame_base:0x93200000, backcar_frame_size:0x200000
[ARM2 Dualarm] ARM1PHY2ARM2UCV u4ARM1phyadress: 0x93200000
[ARM2 BC] INFO video FrameBuf addr is 0x3200000
[ARM2 BC] INFO BackCar_Init -, at TickCount (278)
[ARM2 BC] INFO BCCustomEntry enter, at TickCount (279)
[ARM2 BC] E OR BCCustomEntry MetaZonebufRead[0]=100
[ARM2 BC] ERROR BCCustomEntry MetaZonebufRead[1]=2
[ARM2 BC] ERROR BCCustomEntry MetaZonebufRead[2]=3
[ARM2 BC] ERROR BCCustomEntry MetaZonebufRead[3]=18
[ARM2 BC] ERROR BCCustomEntry MetaZonebufRead[4]=0
[ARM2 BC] ERROR BCCustomEntry MetaZonebufRead[5]=40
[ARM2 BC] ERROR BCCustomEntry MetaZonebufRead[6]=100
[ARM2 BC] ERROR BCCustomEntry MetaZonebufRead[7]=4
[ARM2 BC] ERROR BCCustomEntry MetaZonebufRead[8]=4[/HIDE]
Connector "C" RX(Chinese text then TX) is RX and TX(Chinese text then RX) is TX. TTL 3.3V 38400baud N/8/1. This is where the CANBOX or CANBUS decoder goes.
I have tested with the example command from @JeeBee87 post at https://forum.xda-developers.com/showpost.php?p=69712351&postcount=37;
"For example, to increase the volume (VOL+) the box send 46, 32, 2, 1, 1, -37 (command)"
I'm using realterm to send the serial data so the data is "46 32 2 1 1 219" as realterm doesn't send negative numbers.
I have tested this command with the following "Protocol settings" (I only went down the list of car brand/model until one responded and moved to the next decoder brand);
RAISE, Volkswagen, Toyota, Nissan, Honda, Ford.
BNR, VW.
XBS, VW.
XINPU, VW.
Daojun, Nissan.
Oudi, M Benz.
Ruishengwei, BYD.
HCY, BYD.
Ansheng, BYD.
Anyuan, M Benz.
NFCK, Chery.
CML, Dongfeng. This one didn't increase the volume, it was similar to pressing home or toggle between app's.
Time to start testing commands!

Great to know!!!
For codes i suggest you to take a look at openbcd github.

t3l3m4k0 said:
Great to know!!!
For codes i suggest you to take a look at openbcd github.
Click to expand...
Click to collapse
Sorry, can't seem to find the relevant Git. Do you have any more info on that?
Here is what I've found so far;
Code:
Action DEC HEX
Vol+ 46 32 2 1 1 219 2E 20 02 01 01 DB
Vol- 46 32 2 2 1 218 2E 20 02 02 01 DA
Next 46 32 2 3 1 217 2E 20 02 03 01 D9
Back 46 32 2 4 1 216 2E 20 02 04 01 D8
BT connect 46 32 2 5 1 215 2E 20 02 05 01 D7
Mute/Unmute 46 32 2 6 1 214 2E 20 02 06 01 D6
Home/Switch app 46 32 2 7 1 213 2E 20 02 07 01 D5
Front left door 46 65 2 1 1 186 2E 41 02 01 01 BA
Front right door 46 65 2 1 2 185 2E 41 02 01 02 B9
Rear left door 46 65 2 1 4 183 2E 41 02 01 04 B7
Rear right door 46 65 2 1 8 179 2E 41 02 01 08 B3
Trunk 46 65 2 1 16 171 2E 41 02 01 10 AB
Parking brake 46 65 2 1 32 155 2E 41 02 01 20 9B
Wiper fluid level 46 65 2 1 64 123 2E 41 02 01 40 7B
Seat belt 46 65 2 1 128 59 2E 41 02 01 80 3B
Closes decoder soft? 46 34 1 0 0 220 2E 22 01 00 00 DC
Still trying to decode the messages from the head unit so I can send the messages to the OEM LCD in the car. Missing phone buttons, play/pause, mode....
Would be great to find other commands but even when dumping prepared hex filed this is very slow... :silly:

sorry, i make a mistake
opendbc
https://github.com/commaai/opendbc

I was looking into this for my HU, it seems that a number of people have bought a number of off the shelf SWC decoders $40-120 that either do not work or have limited functionality. It is great you researching this-I hope you success. Apparently CAN-BUS coding is car model specific.
Arduino (or other) with CAN coding specific for your car would be ideal.
Alternatively, Euro cars have simpler coding down Steering column to CAN terminal at base.
i.e.
1-button presses on steering wheel to
2- LIN then send it through the rotating joint
3- receive it as LIN at base box
4- covert it back to button presses
5-send the button presses to the CAN processor to get converted to CAN to be sent on the CAN bus.
So button presses are available in steering wheel, encoded LIN bus, decoded separately at base box, then re-encoded to CANbus
Hope this helps.

One alternate solution if your HU supports IR remote-Ebay has for <$10 a learn-able IR remote control gizmo that attaches to the steering wheel, or could be incorporated inside the steering wheel using existing buttons...

Pxdev said:
I was looking into this for my HU, it seems that a number of people have bought a number of off the shelf SWC decoders $40-120 that either do not work or have limited functionality. It is great you researching this-I hope you success. Apparently CAN-BUS coding is car model specific.
Arduino (or other) with CAN coding specific for your car would be ideal.
Alternatively, Euro cars have simpler coding down Steering column to CAN terminal at base.
i.e.
1-button presses on steering wheel to
2- LIN then send it through the rotating joint
3- receive it as LIN at base box
4- covert it back to button presses
5-send the button presses to the CAN processor to get converted to CAN to be sent on the CAN bus.
So button presses are available in steering wheel, encoded LIN bus, decoded separately at base box, then re-encoded to CANbus
Hope this helps.
Click to expand...
Click to collapse
Pxdev said:
One alternate solution if your HU supports IR remote-Ebay has for <$10 a learn-able IR remote control gizmo that attaches to the steering wheel, or could be incorporated inside the steering wheel using existing buttons...
Click to expand...
Click to collapse
Hi Pxdev,
Thanks for the input and support
For my car (Mazda 3) the steering wheel buttons are resistors/a voltage divider so I was able to connect one end to ground and the other to KEY1.
For my car I am still pushing to get the original car LCD to work as I don't have any clock or trip/consumption information. I have found the commands for the LCD text area and enable the clock.
For my friends car I still need to implement the steering wheels and hopefully other functions. I have found most of the CAN commands.
I'm currently fighting with an MCP2515 and it's weird register filters for the CAN bus. I should have some free time these days to move this forward!
I will then need to learn how to write an app for android again as the last time I made an app was about 8 years ago...

Well,
Now that I have some free time I whipped up Version 1 of the device. Basically it converts the CAN bus codes from the Volvo XC90 steering wheel to SWC for the Android head unit.
I've also added 4 extra outputs to control reverse, brake, illumination and whatever else can be found on the CAN bus.
Now to work on getting my Mazda's original LCD to display at least display the fuel information again. Should be easier as I have access to my car!

O.i.D said:
Well,
Now that I have some free time I whipped up Version 1 of the device. Basically it converts the CAN bus codes from the Volvo XC90 steering wheel to SWC for the Android head unit.
I've also added 4 extra outputs to control reverse, brake, illumination and whatever else can be found on the CAN bus.
Now to work on getting my Mazda's original LCD to display at least display the fuel information again. Should be easier as I have access to my car!
Click to expand...
Click to collapse
Nice & professional job.
I was looking for IDs and only think i was found is the structure message between Canbus Box Converter and MCU
1rst byte: 2E ->start
2nd byte: XX -> request ID
3 byte: NN -> number of data bytes length
4 to NN+3 bytes: DD ... DD -> data of request
NN+4 byte: cheksum from second byte to NN+3 byte complement 2
I'm looking at android apk's but i don't know java and how Android packages structure works

t3l3m4k0 said:
Nice & professional job.
I was looking for IDs and only think i was found is the structure message between Canbus Box Converter and MCU
1rst byte: 2E ->start
2nd byte: XX -> request ID
3 byte: NN -> number of data bytes length
4 to NN+3 bytes: DD ... DD -> data of request
NN+4 byte: cheksum from second byte to NN+3 byte complement 2
I'm looking at android apk's but i don't know java and how Android packages structure works
Click to expand...
Click to collapse
Thanks, it still needs some hot glue to hold everything together from the vibrations but I hope the hardware doesn't need any revisions. Hopefully all upgrades can be run from a laptop.
Looks like the controller you have has a very similar protocol. There are lot's of makers and for different car models the communication protocol varies so I'm glad it's similar to what I found
Good luck with the Java, I need to look into it again soon... but so many things to do...
On the other hand, looks like the Mazda LCD is rather straight forwards! I'll Tidy up the info I have and post it later. Now to make another similar box for my car. :fingers-crossed:

Well, here are the codes needed to control the LCD.
Quite a few more ID's are needed to fill in the data from the car. I ended up using ID's;
0x433 (for Ambient temp),
0x2A0 (for HVAC),
0x285 (car key ignition),
0x400 (Trip computer for fuel consumption and speed).
Below are the the ID's for;
0x28F (LCD control A),
0x290 (LCD control B),
0x291 (LCD control C),
0x2A0 (HVAC control).
Code:
Mazda 3 ID DLC Example data Byte HEX BIN Description
LCD A 28F 8 80 00 00 22 20 00 00 00 B1 80 10000000 b8 must be 1 to enable
[INDENT][INDENT][INDENT] 81 10000001 AF
82 10000010 RDM
84 10000100 RPT
88 10001000 DOLBY
90 10010000 ST
A0 10100000 MD IN
C0 11000000 CD IN
B2 10 00010000 AUTO-M
20 00100000 TP
40 01000000 TA
80 10000000 PTY
B4 01 00000001 Disables ID 0x28F?
02 00000010 "." between character 10 and 11
04 00000100 "." between character 11 and 12
10 00010000 Minutes and seconds symbols
20 00100000 ":" between character 3 and 4
B5 02 00000010 Send 3 times to perform LCD selftest
08 00001000 INFO button, toggle with 0x20
10 00010000 CLOCK button, toggle with 0x20. Wait a few seconds to enter clock settings.
20 00100000 No button press. Must be sent after INFO or CLOCK to resend button press.[/INDENT][/INDENT][/INDENT]
LCD B 290 8 C0 31 32 33 34 35 00 00 B1 C0 11000000 Can be swapped with ID 0x291 0X85
[INDENT][INDENT][INDENT] B2 31 00110001 ASCII HEX character 1 "1"
B3 32 00110010 ASCII HEX character 2 "2"
B4 33 00110011 ASCII HEX character 3 "3"
B5 34 00110100 ASCII HEX character 4 "4"
B6 35 00110101 ASCII HEX character 5 "5"[/INDENT][/INDENT][/INDENT]
LCD C 291 8 85 61 62 63 64 65 66 67 B1 C0 11000000 Can be swapped with ID 0x290 0XC0
[INDENT][INDENT][INDENT] B2 61 01100001 ASCII HEX character 6 "a"
B3 62 01100010 ASCII HEX character 7 "b"
B4 63 01100011 ASCII HEX character 8 "c"
B5 64 01100100 ASCII HEX character 9 "d"
B6 65 01100101 ASCII HEX character 10 "e"
B7 66 01100110 ASCII HEX character 11 "f"
B8 67 01100111 ASCII HEX character 12 "g"[/INDENT][/INDENT][/INDENT]
HVAC 2A0 4 A1 22 83 B0 B1 b8 must be 1 to enable. b0 and b1 cannot be both 1.
[INDENT][INDENT][INDENT] 80 10000000 No temp displayed
81 10000001 HVAC Temp displayed
82 10000010 AMB Temp displayed
84 10000100 A/C+RECTANGLE
88 10001000 ECO
90 10010000 AUTO
A0 10100000 AIR RECIRCULATION
C0 11000000 EXTERIOR AIR CIRCULATION
B2 00-99 Treat as decimal temperature, no HEX allowed, only 0-9
B3 01 00000001 Air to face
02 00000010 Person icon
04 00000100 Air to windshield
08 00001000 1 LSB of decimal temp
10 00010000 2 bit of decimal temp
20 00100000 4 bit of decimal temp
40 01000000 8 MSB of decimal temp
80 10000000 Decimal point
B4 08 00001000 1 Fan icon lvl 0
10 00010000 2 Fan icon lvl 1
20 00100000 4 Fan icon lvl 3
40 01000000 8 Fan icon lvl 7
80 10000000 Air to feet[/INDENT][/INDENT][/INDENT]

Android Head Unit VCDS Fault Codes

Hi guys,
So, I've installed a DASAITA Android 10 Head Unit on my Golf 7 and of course some fault codes appeared.
The faults have been successfully reset via VCDS but 2 continue to remain in the Instruments module:
Code:
Address 17: Instruments (J285) Labels:| 5G0-920-XXX-17.clb-SRI3
Part No SW: 5G1 920 740 A HW: 5G1 920 740 A
Component: KOMBI 207 7640
Coding: 07AD19002B80000801083A001400000000000000
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_DashBoardJCIMQBAB 009005
ROD: EV_DashBoardJCIMQBAB_009.rod
VCID: 244759972FDBF6A657-8070
2 Faults Found:
16777018 - Function Restricted due to Interrupted Communications
U1110 00 [008] - -
[New feature! Extended UDS fault detail is only supported by current gen. interfaces]
Intermittent - Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 1
Reset counter: 2
Mileage: 57253 km
Date: 2020.09.16
Time: 17:24:20
16777020 - Function Restricted due to Interrupted Communications
U1110 00 [009] - -
[New feature! Extended UDS fault detail is only supported by current gen. interfaces]
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 2
Reset counter: 217
Mileage: 57253 km
Date: 2020.09.16
Time: 17:24:30
I've searched the interwebs quite a bit and its clearly related to the infotainment module and wanted to confirm it with you guys and also maybe help others with the same problem.
I've actually discussed this with an electrician before and he asked me if any faults appear because the car will not recognize the head unit as OEM, and after checking with VCDS I can confirm it.
What about your fault codes?
Best regards,
P.S. Cant wait for Android 10 ROMS !!

Database Users

welcome