Ottonavi HU: How to customize (a bit) the UI

Not sure about if it is listed all the time; depends on the Windows version.
But it should be listed if the card is inserted for sure.
That's what we want to know. And try with different sd cards to make sure.

Reset should only cold reboot the HU; you can also remove the Radio fuse for 2 minutes and reinstall.
Should not loose any settings unless your HU is customized by your dealer.

Here we are just trying to find out if the problem is software or hardware.
If it is temporary software problem, a reboot might fix it; sometimes Windows lost the device status.
If it is permanent software problem, a Windows reinstall might be necessary (in which case you might lose some files).
If it is permanent hardware problem, then you may have to talk your dealer.
In fact, if you just bought the unit maybe you should talk to your dealer first (warranty...).

 

Ah thanks; very nice info.

For creating new skins, you might also want to check our German friends at http://www.china-rns.com/application-software-suite/4691-roadrover-skin-aendern.html

The used our hacked tool to create lots of skins; they also provide a lot more information about the Roadrover HU.
They also have a very nice download section with plenty of stuff. And other interesting threads!

Enjoy!

 

Yes it should let you interact; you should be able to go to all the menus; change skins, for testing obviously.
You can even select and play music.
But not all functions will work obviously; things like radio, car functions, etc.

If I remember, you have to let it run for 1-2 minutes before starting to interact with it.
Not sure why; give it a try again.

I never tried under Windows 10 so not sure if it is related or not.

 

Hi Kiat, (replying to your PM in this thread since this info might be useful for others...)

Yes it always takes a while for the blue bar to appear; emulator is slow.
If the main screen does not appear it's because the version of manager.exe you are using is not compatible with the emulator.
Manager.exe is actually running but it is stuck in the input loop somehow; some versions of manager.exe do this; not all the time.
Starting another copy of manager.exe doesn't help because now you can see the main screen but the input loop is still hold by the first instance.
To get around this, try using a different UI version (hence a different manager.exe) with your new skin and it will work.
Again, as long as you are only testing cosmetic changes to the RRUI file, you should be fine; emulator cannot test other car functions anyway.

The *wire* frame version is actually a default version provided by manager.exe in case something goes wrong with the RRUI file.
So my guess is your RRUI file got damaged somehow by the RRUIEditor; it happens sometimes when dealing with new RRUI files.
The RRUIEditor was done way before the new generation of skins so depending on what you change, newer functions or IDs may not be recognized by the RRUIEditor.
There is no fix for that; only thing you can do is make small incremental changes to the skin and test (in emulator preferably).
If the RRUI file is broken, then the wireframe version will appear.

You can always use the RRUITool instead to make the skin changes but it's a real pain (you have to use hexadecimal input).
But at least, it can do whatever you want.

 

Yup; lots of bruises here...
Go through post #1; there are a couple of UI shell you can use I think. Take the latest.
Do not just copy the manager.exe; copy the whole I9 folder in the emulator sd folder along with your RRUI file in the skin folder.
Then start the emulator and then the new manager.exe and load your skin.
Should work.

 

I'm glad you were able to finally run it. At least you can test some of your changes this way.

Some background info.
The RRUI file contains all the possible screens for all the possible HU in the world.
But some screens are actually activated only if the HU has the right hardware that supports it.
As for the the emulator, it is in fact just a WindowsCE app emulator. It has no knowledge of Roadrover HU at all.
So therefore it has no MCU firmware either.
(MCU provides the basic hardware functions like radio, audio settings, TPMS, climate control, video,etc.)
Normally manager.exe calls the MCU functions to find out which HU model you have and which functions it supports.
Under the emulator, since there is no MCU software available manager.exe defaults to whatever is defined inside manager.exe.
This explains why under the emulator you might not see the same screen as on the HU.

So to answer your questions:
1) Without hacking manager.exe, I don't think there is an easy way to point it to ID_APP_RADIO_ADVANCE.
2) Depends on your HU MCU; ask your dealer which functions should be available. (my guess is if you don't see it it doesn't have it)
ID_APP_CAR_TPMS: this is not car or obd dependant. You need to buy special hardware (try EBay) and make sure it can communicate with the HU via USB or Bluetooth. I never tried with my HU; you will have to do your own research; should be possible. Also check with dealer.
ID_APP_VOICE: it is for voice recognition. And we know this is working on some HU. But you need the right shell UI version and probably some MCU specific version as well. Your version doesn't have it. Ask your dealer to give you the latest UI and MCU updates for your specific HU model.
DO NOT USE OTHER CARS MCU UPDATES; YOU MIGHT BRICK YOUR HU!!!!

 

Exactly, the RRUI skin file has no version number attached to it; bad Roadrover design decision imo.
The UI shell version is actually the version number attached to manager.exe (the shell).
Obviously, each new version supports new hardware or software features.
Over the years, Roadrover has built several versions of manager.exe, some customized, for each car.
So when they release a new UI Shell (manager.exe), they also release new or revised skins (usually).
And this is where it gets bad because here they released new skins with the same name but with no versions number.

This is also why any recent version of manager.exe can read any RRUI skin; because skins have no versions; so it doesn't check.
(On the other hand note that older versions of manager.exe cannot read recent skins because RRUI files also have a generation version.
But that's a different topic. The RRUITool can handle this.)

 

Hello Graeme,
start by reading post #1 for more information about your device, tips and tools.
Then you can read the other posts to find the latest tools if you want.
Look for the RRUIEditor program; this is the somewhat Roadrover *official* version for editing skins.
Be aware that it does not always work especially for newer skins.
If it's the that case then you can also use the RRUITool (it can do anything) but it's a lot more work.
Another possibility for you is to visit our German friends at http://www.china-rns.com; they are very knowledgeable too.

 

Hi Mert,
may be it's possible; depends on your skin version.
Can you upload it so we can take a look?