So, last week I spent some time on hacking Ambient color maps for MIB2. If you didn't read about it, see here.
I continued the research, and found out some more interesting things:
— ambienceColorMap.res holds the default ambient color list.
— on VW the file determines which Screening (module 5F, byte 18) get what color profile
— there's a default color
— there can be a "no" color
— the ambienceColorMap.res can be swapped between brands!
— the color lists can be extended
So let's have a look at the first finding: the file holds the default ambient color list. A lot of people are modifying the ambient color list in the BCM (Module 9). However, you need a facelift BCM to be able to do this. Most of the screenshots online show me modified ambient color selections… however I found a youtube video (thanks Team BHP) which showed an unmodified ambient color map on Skoda firmware. The ambience map lines up perfecfly to the color selection, as you can see. Feel free to send me some pictures of your untouched ambient color selection, so I can see if it all matches up to the files :-)
My biggest question here is: Why does each color show up 3 times in the file?!. Maybe there are 4 zones that we can customize independently from each other? This needs some additional testing. If you want to try a modified ambiencecolormap, let me know!

Then the part about VW having specific color profiles for each "Screening" (5F, byte 18). GTI has red ambience coloring and HMI highlights by default, while all other models are blue. My car has "9" as a value, while GTI has "3". While looking at the values in the selected part, I saw some similarities:

So, the first, 0x39 (= 9 in ASCII), second 0x35 (= 5 in ASCII), third 0x37 (= 7 in ASCII) ad 4th 0x33 (= 3 in ASCII). I gave each profile a different color instead of the default blue:

And then I started changing the value for Screening. I saw the colors change accordingly:
value 9 gave me the 1st profile, value 5 the 2nd, value 7 the 3rd, value 3 the 4th. I was happy. Then I swapped the "33" for "39", and vice versa. Colors swapped accordingly. Conclusion: Screening value determines what color is used on VW. However… on Skoda and Seat this "table" is not used… I wonder if it works if we copy a VW ambiencecolormap to a Seat. Either way, I also found out there's a "default" color, in case the Screening is not in the table. This is the 0th color, which again is blue in VW's case.
After this I started modifying crazy stuff to see if I could tweak other settings. I ended up with a "stealth" theme with no color highlights at all:

I also tested some Seat and Skoda maps, which all had a positive result, everthing was loading as planned.
More research soon :-P


Comments 21
Is it possible to show Ambient menu on Technisat PQ with HMI from ZR?
I have turned on ambient menu in adaptations, connected unit to MQB BCM through 100 kbps — 500 kbps CAN-adapter but menu don't appears :(
Good question. I am not sure of that.
Skoda fw1163 .res
The colour layout in my Skoda Columbus is different, fw 1163.
… "golden china" at the moment only color ;))))
… but who knows ? ;))))
3. ori pq
… great job ;) but its not working on Technisat PQ unit ;(
… I tried many combination, swapped file from china sw (gold), mqb (blue), (Technisat) edited manualy, changed byte 18, still without effect ;)
… its looks like this bastard (Technisat) just ignoring this file
… very strange ;)))
Technisat is a bit different from the Harman MIB2 High units. I don't know how to replace any file on TS PQ units, but you might want to look for a way to restart and commit updated hashes and such.
I know mate is a different ;) but you may find some similar ;)
… for me is not problem replace this files on Technisat but as I wrote this unit just ignoring it ;) even after restart and recoding byte 18
… is on Harman some file with path to "ambience" or this unit (Harman) reading it straightaway ?
… on Technisat this "ambience" structure is different as Harman but why this f… ignoring it ? ;)))) have look ;)
1. china pq (gold dots)
The gold dots are not in this file. It's an additional set of files inside the images.mcf that holds the animation maps of the dots. I tried swapping the chinese file to the European firmware, it didn't boot anymore haha.
But… let's think. Maybe the ambience file is ignored, depending on your setup. If you have ambient lights, the file will be redundant, because the coloring is fixed somewhere else.
But… f*cking interesting stuff to look into!
… regarding "gold dots" I knowi it not keeping only in "ambience" ;) you are right even in pq unit parts of "dots" are in .mcf and the rest in "viewhandler.zip" and "view" I tested it as well and is no problem to run it on Technistat unit
… main problem is there are only "china" and "english" available ;)))
… now have to do some tests how to add other languages ;)
… regarding "ambience" you may have right as well ;)
… I will do some tests when I receive my "test" unit I will even delete this file to check what's happen ;))))
Nice, we are running the same road, except on different machines :-D
I have 1 MIB2.5 running as a chinese/english unit, only Navigation is causing some issues haha.
Cool research! :-D
daChillout
Technisat is a bit different from the Harman MIB2 High units. I don't know how to replace any file on TS PQ units, but you might want to look for a way to restart and commit updated hashes and such.
2. mqb (blue)
Hi, did you had any luck to modify the ambientcolor on Technisat, I also experimenting like you, I got boot loop two times, hate this ), I want to make blue color instead of red.
daChillout I will help in testing the moment I get my unit installed. Will you keep you posted.
Все понятно
🤣🤣🤣
👍