Infotainment Display Buick to Opel

[Uniqez]

GM’s Step-By-Step Instructions For In-Vehicle Development & Testing

 

[dmr02]

Much prefer the Opel system. Drove one not long ago when I was over there. If we could covert it over it would sure be cool! And make it feel even more so unique

 

[Anaduff]

The inside (hardware) story.

BE2817 INFO3 CSM External Photos High - Harman Industries, .

INFO3 CSM High - External Photos details for FCC ID 2AHPN-BE2817 made by Harman International Industries, Inc.. Document Includes External Photos High - External Photos

fccid.io

I've tried several USB bridge cables, two different computer (tower w/ Linux Mint & laptop with Windows 7) & a couple of different ADB configurations to talk to the INFO 3 module--I would have had the same success rate if I had used a manual typewriter and a garden hose. I would have to say the software gods smiled upon 'Blitzschnell' during his probing session (either that, or I needed to sacrifice an 8" floppy disc on the grill to get their attention). Was looking forward to seeing the results of: adb shell find / -name *.png -fprint <file name> to see where & what the image were located/contained.

On the plus side; I have heard from White Auto & Media that they have made progress working with Harman to get into the system so maybe soon...

 

[Uniqez]

The inside (hardware) story.

http://[URL]https://fccid.io/2AHPN-BE2817/External-Photos/High-External-Photos-3129175

[/URL]

I've tried several USB bridge cables, two different computer (tower w/ Linux Mint & laptop with Windows 7) & a couple of different ADB configurations to talk to the INFO 3 module--I would have had the same success rate if I had used a manual typewriter and a garden hose. I would have to say the software gods smiled upon 'Blitzschnell' during his probing session (either that, or I needed to sacrifice an 8" floppy disc on the grill to get their attention). Was looking forward to seeing the results of: adb shell find / -name *.png -fprint <file name> to see where & what the image were located/contained.

On the plus side; I have heard from White Auto & Media that they have made progress working with Harman to get into the system so maybe soon...

Do you need to have HMI connected to it as well, to be able communicate? So you can see what is going on with the module?

 

[justiz00]

On a side note, the 2020 encore I used as a loaner still had the windows based Intelilink system from the red needle cars.

 

[Uniqez]

What about this? I'm downloading random open source software to my computer, trying to see what's inside.

 

[Anaduff]

I've looked at that--as far as I can tell, that's the code used in the 'NG' series [as in NG 2.0, NG 2.5] HMI modules--usually installed in the 'red needle' cars. The Harman INFO3 code is (maybe) this:

harman-dev - Overview

harman-dev has 35 repositories available. Follow their code on GitHub.

github.com

To answer your earlier question, the USB port in the centre console connects directly to the Harman unit (the HMI in the 'white needle' cars) so that if the HMI unit has been put into 'developer mode' is should allow the ADB software to communicate with the unit--I understand that the HMI has to be powered-up but I did try it both ways. I did unplug the black USB cable on the HMI to make sure that is was connected to the console USB (it was), the blue USB cable connects to the touchscreen. Not sure where the USB cable on the instrument cluster connects to.

 

[Anaduff]

Much prefer the Opel system. Drove one not long ago when I was over there. If we could covert it over it would sure be cool! And make it feel even more so unique

Seeing that you (most likely) have the Bosch NG2.5 unit, Coastal Flash may be able to sort that out...

HMI Archives – Coastal Flash

Custom HMI Unlocks

coastalflash.com

 

[Blitzschnell]

At the risk of repeating myself: digging through the provided source code files is not going to give anything useful with regard to changing the splash screens-- or anything else-- on the head units. Those files are OS components that Harman reused under public license; they will not include the (wholly proprietary) items Harman built on top of the OS, such as the animation engine... and still less would they include picture files containing trademarked logos.

It seems some folks are having trouble connecting to the Android head unit to poke around. I've done it many times and have had no trouble; perhaps it's simpler than it sounds? In any case, here's the how-to:

1) Download the SDK Tools zip from the Android developer site. (Search "download ADB" in Google.) Extract it to a folder on your PC.
2) Start Powershell in that folder and type ".\adb devices". You should get a message showing an empty list of devices, if adb is working.
3) Go sit in the passenger seat of your car. Turn it on (ignition only, no need for the engine to be running) and wait for the radio to boot up.
4) In the head unit, go to Settings->System and activate USB debugging. You need to do this each time the radio's been power cycled.
5) Plug your USB data cable to the car and to the laptop. Wait until your laptop makes its "new device" ding, and then type ".\adb devices" again. You should see a list of devices with one gobbledygook number in it. That's your car's head unit computer.

I have found that, while I can shell into the head unit and interact with it like a typical posix machine, without root privileges access is quite limited indeed. Perhaps someone else will find something I have overlooked.

Good luck!

 

[Uniqez]

At the risk of repeating myself: digging through the provided source code files is not going to give anything useful with regard to changing the splash screens-- or anything else-- on the head units. Those files are OS components that Harman reused under public license; they will not include the (wholly proprietary) items Harman built on top of the OS, such as the animation engine... and still less would they include picture files containing trademarked logos.

It seems some folks are having trouble connecting to the Android head unit to poke around. I've done it many times and have had no trouble; perhaps it's simpler than it sounds? In any case, here's the how-to:

1) Download the SDK Tools zip from the Android developer site. (Search "download ADB" in Google.) Extract it to a folder on your PC.
2) Start Powershell in that folder and type ".\adb devices". You should get a message showing an empty list of devices, if adb is working.
3) Go sit in the passenger seat of your car. Turn it on (ignition only, no need for the engine to be running) and wait for the radio to boot up.
4) In the head unit, go to Settings->System and activate USB debugging. You need to do this each time the radio's been power cycled.
5) Plug your USB data cable to the car and to the laptop. Wait until your laptop makes its "new device" ding, and then type ".\adb devices" again. You should see a list of devices with one gobbledygook number in it. That's your car's head unit computer.

I have found that, while I can shell into the head unit and interact with it like a typical posix machine, without root privileges access is quite limited indeed. Perhaps someone else will find something I have overlooked.

Good luck!

I was digging through the code to see, if I can spot at least reference for make or model. If you have model 1, you would use this logic and so on.
For android, I've seen this:
1st boot logo changing service

 

[Anaduff]

Re: Uniqez "For android, I've seen this: 1st boot logo changing service"

Well, that looks like an interesting read (hope 26 of the 29 pages aren't 'can you add [brand] to this?').

Re: Blitzschnell "...Plug your USB data cable to the car..."

I've tried 3 of 'em; two different bridge cables & one 'universal' cable. SOMETHING should have worked, but no acknowledgement from the Android that anything was connected nor anything listed under 'adb devices' on the computer side. Other than enabling USB debugging in developer mode on the HMI, I can't see any other options that would enable or inhibit communications--so I'll focus on the next project, replacing the instrument cluster with the 'upscale' version & revisit the HMI branding afterwards.

 

[Anaduff]

This thread seems to detail the process (and image parameters) fairly well:

[Guide] Change Boot Logo

Please note that this has only been testing on MTCB Head units. As with all mods, do so at your own risk. I take no responsibility if you brick your unit. The instructions set out below work for me and I have done been successfully using this...

forum.xda-developers.com

(With credit to Uniqez.)

 

[Blitzschnell]

This thread seems to detail the process (and image parameters) fairly well:

[snip link]

(With credit to Uniqez.)

Indeed. Unfortunately our cars do not have Chinese MTC-type head units, which are the focus of those linked threads and which are aftermarket items.

 

[Anaduff]

In retrospect, I wondered why if there was only a single boot logo, how @NEPAtourx would see the Opel logo on a Buick system--there must be something like the [old] MS-DOS 'config.sys' file that contains the 'BootLogo=Buick.PNG' or some similar 'on startup, do' command.

NEPAtourx: "My car displayed the opel logo for a few seconds at startup in my DIC yesterday for anyone who doubts that the programming is hiding in there somewhere...."

 

[Blitzschnell]

there must be something like the [old] MS-DOS 'config.sys' file that contains the 'BootLogo=Buick.PNG' or some similar 'on startup, do' command.

Yes, when you are successful in getting ADB to work, you will see that. I noted this back in post #26 above.