DNS series head unit (new generation dual core RNS-510 alternative)

[swyner]

Sandy, have you been able to test the HD Link unit with an Android phone? I haven't had time to take a screen shot for you but wondering if you (or anyone else) has used this yet. My first impressions are that the interface is NOT 480p which is what the DNS screen resolution should accept. The whites are more of a gray color and the colors are washed out. So far this "mirroring" unit is not impressive but would like to see if anyone else has had a chance to use it.

Also, have you inquired about the timeline for the OBDII unit? 3G modem?

[DkN]

New problem found.
driving with Sat Nav on, pressed the FM button to turn the volume up on the radio,
turned volume up and then I changed station to check the RDS was working.
After changing stations it locked up and was stuck on that station and was unable
to do anything.
Had to pull the fuse to turn it off.

This is an isolated incident, correct? This kind of lock-up really shouldn't be happening anymore without a hardware issue, but I will confirm.

On another note if you change the GPS volume setting in menu -> system so that it is set on 30 or something instead of "manual", you don't need to exit GPS in order to change the volume of the background application whether it is radio or SD or something else.

Anyone else notice that the radio will mute itself when you sound the horn. Got cut off yesterday and gave a quick honk of the horn, and the radio muted. Interesting! I drive a MK6 with Kessy, if it matters.

Speaking of that, I have a new test MCU that is supposed to fix all radio muting issues. Apparently some people still experience radio muting when starting the car though this no longer happens in my car - that is what this MCU is meant to fix. Would anyone with radio muting issues please test and report back (since mine is already fixed before this MCU for some reason). Link is in first post, under firmware section.

Sandy, have you been able to test the HD Link unit with an Android phone? I haven't had time to take a screen shot for you but wondering if you (or anyone else) has used this yet. My first impressions are that the interface is NOT 480p which is what the DNS screen resolution should accept. The whites are more of a gray color and the colors are washed out. So far this "mirroring" unit is not impressive but would like to see if anyone else has had a chance to use it.

Also, have you inquired about the timeline for the OBDII unit? 3G modem?

I received an response saying that the low quality you are experiencing is not normal, but I don't have the module with me to test for myself. I'm waiting for confirmation from a US customer who may be receiving a replacement unit with an added mirroring module much like yourself very soon, so we can get a comparison.

I still need to follow up on OBD2 and the 3G availability though software-wise 3G has already been enabled.

[asa572]

This is an isolated incident, correct? This kind of lock-up really shouldn't be happening anymore without a hardware issue, but I will confirm.

On another note if you change the GPS volume setting in menu -> system so that it is set on 30 or something instead of "manual", you don't need to exit GPS in order to change the volume of the background application whether it is radio or SD or something else.

Maybe an isolated incident as I tried to replicate tonight and it didn't happen.
The muted radio on start up is still happening though.

[DkN]

Maybe an isolated incident as I tried to replicate tonight and it didn't happen.
The muted radio on start up is still happening though.

Just to confirm, are you starting the car before or after the unit is booted into radio? If you are starting the car before the VW logo shows up, radio should not be muted. If you start after the VW logo disappears (or just before the VW logo is about to disappear) and the radio interface is displayed, you might mute the radio in the old firmware. This is what the new test MCU should fix. Your issue could be a different one altogether if you are saying your radio starts up muted regardless of whether you are starting the car straight away before the unit boots.

[woweriux]

For the people who had iGO preloaded on their unit form the factory, what are you sys.txt settings? Has anyone figured out what the optimal variables would be to use for this unit (ie memory, cache, driver, etc.)?

Also, a way to replicate the monsun.exe error (with the latest firmware):
1. start listening to music from the SD card
2. turn on navigation, set a destination and then go
3. once on your way, switch back to the SD card while the navigation is going on in the background
4. the memory error will come up after a couple songs or if your press next song a few times. Having SD on shuffle and switching from Nav to SD a few times helps to have the error occur quicker.

[LD_mart]

We any closer to a date for the rest of us getting our unit Sandy?

[polski_ogurek]

My unit did a funny thing yesterday( after being in the sun on a 30+ degree day). It randomly rebooted. And was missing all the info in the FM screen. Came back a few mins later.

I also still have the no radio after startup issue. Hasn't been helped by the most recent update.

Sent from my galaxy spaceship

[asa572]

Just to confirm, are you starting the car before or after the unit is booted into radio? If you are starting the car before the VW logo shows up, radio should not be muted. If you start after the VW logo disappears (or just before the VW logo is about to disappear) and the radio interface is displayed, you might mute the radio in the old firmware. This is what the new test MCU should fix. Your issue could be a different one altogether if you are saying your radio starts up muted regardless of whether you are starting the car straight away before the unit boots.

I start it before the logo shows up.

[DkN]

For the people who had iGO preloaded on their unit form the factory, what are you sys.txt settings? Has anyone figured out what the optimal variables would be to use for this unit (ie memory, cache, driver, etc.)?

Also, a way to replicate the monsun.exe error (with the latest firmware):
1. start listening to music from the SD card
2. turn on navigation, set a destination and then go
3. once on your way, switch back to the SD card while the navigation is going on in the background
4. the memory error will come up after a couple songs or if your press next song a few times. Having SD on shuffle and switching from Nav to SD a few times helps to have the error occur quicker.

That would be the SD / satnav system resource conflict issue that AS is working to fix. I should have an estimate on how long this will take soon.

We any closer to a date for the rest of us getting our unit Sandy?

I'm waiting on these issues before ordering the unit:

1. SD / navigation running at the same time causes a conflict where SD music playback may stutter / song switching may take excessive time. Some optimisation of the SD decoding will be required to fix this issue.

2. current method of SD music loading will always start from the beginning and take 15-20 seconds to load a ~4 minute song, though playback starts once ~30 seconds have been loaded. The issue here is if the song memory is at something like 3 minutes on startup, or you just started a song and want to skip to 3 minutes. The issue is more pronounced if you have a larger file / longer song. A different method of loading the song will be required to fix this issue (e.g. one that is able to load the song from whichever point rather than from the beginning every time).

3. navigation volume and SD volume have a conflict sometimes reducing the SD volume - this is due to navigation using the system volume same as SD, and should be an easy fix just by switching navigation onto a separate volume on its own.

and now some people are saying the radio muting thing on startup is not fixed, though the latest firmware worked for my unit

My unit did a funny thing yesterday( after being in the sun on a 30+ degree day). It randomly rebooted. And was missing all the info in the FM screen. Came back a few mins later.

I also still have the no radio after startup issue. Hasn't been helped by the most recent update.

Sent from my galaxy spaceship

Can I just confirm that by most recent update you mean the 140104 test MCU? If so I'll have to tell the tech that it didn't seem to work.

I start it before the logo shows up.

So your radio just randomly has no sound on startup, or always has no sound on startup, or is there a pattern?

[woweriux]

Any news from AS regarding updated firmware?