SysConfig Tweaks

holty · March 28, 2012

yeah that works, when i change the volume setting for voice/beeps, i hear nothing. ugh.

430HP70 · March 28, 2012

if you have the files restored theres no reason the voices wouldnt work. id give walt or advent a call and figure it out.

holty · March 30, 2012

Apparently the .exe on my sd card got corrupt, Walt fixed me up, thanks guys

holty · April 2, 2012

If anyone is interested, I am able to recreate or duplicate the missing NAV voice so for now at least i know how to avoid that problem. It seems as if ANY time i modify the data.zip file, regardless of what i change, it causes some sort of corruption where the NAV voices no longer work. At least i know now how the problem happens, just dont know how to prevent it. For example, if i take a 100% completely stock sd card and go into the data.zip and edit the drive_carefully=1 to drive_carefully=0, then close and save changes, the NAV voices quite working. Even if i go in and reverse my changes to drive_carefully=1 the NAV voices will not work until i restore a stock/oem/default (whatever you want to call it) data.zip file. Luckily, all i really care about is that the Altitude works and that the drive_carefully=0 works (which i can change both in the sys.txt) and of course the NAV voices work. Since i can accomplish this by only modifying the sys.txt, i'm happy for now.

EDIT: I wonder if Winzip is the problem that is causing the corruption? Are you guys using Winzip, version 14.5?

parshal · April 2, 2012

Holty, I checked and my voices work. It seems my .exe didn't get corrupted.

skicrave · April 2, 2012

Use WinRar instead.

08G8V8 · April 6, 2012

I had a LONG conversation about this issue with the Advent engineer on Thursday. He's adamant that to maintain any kind of stability in the system, they cannot load navi automatically due to quite a few factors. When booting up, it goes through quite a few processes in order:

Loads the operating system for the unit and starts the bootup process

Reads from and reports to the CAN for chimes and vehicle required warnings

Determines what source was on and attempts to start up that source again (AM/FM is by far the easiest on the processor)

If not AM/FM, then it has to: if iPod/iPhone - it has to reindex before it starts playing, if XM - reads and interprets XM data before it will play, if Bluetooth - has to pair, then restart the source, if CD/DVD - it has to spool up and start playing.

Once it has all that done, it can start any other task such as navi and not take a hit on the memory available

The problem with all this is that there is no set time frame that will accomplish all these tasks, so they did not allow anything other than the "Auto switch to GPS".

Having said this, I installed my navi in my Tahoe Thursday night and with some tweaks, my system auto-boots to navi:

http://vimeo.com/39119557

I'll outline the changes when I can verify this is stable...

Has this been verified to be stable yet? I'd really like to know how to get this working.

Thanks

wottenad · April 6, 2012

I had a LONG conversation about this issue with the Advent engineer on Thursday. He's adamant that to maintain any kind of stability in the system, they cannot load navi automatically due to quite a few factors. When booting up, it goes through quite a few processes in order:

Loads the operating system for the unit and starts the bootup process

Reads from and reports to the CAN for chimes and vehicle required warnings

Determines what source was on and attempts to start up that source again (AM/FM is by far the easiest on the processor)

If not AM/FM, then it has to: if iPod/iPhone - it has to reindex before it starts playing, if XM - reads and interprets XM data before it will play, if Bluetooth - has to pair, then restart the source, if CD/DVD - it has to spool up and start playing.

Once it has all that done, it can start any other task such as navi and not take a hit on the memory available

The problem with all this is that there is no set time frame that will accomplish all these tasks, so they did not allow anything other than the "Auto switch to GPS".

Having said this, I installed my navi in my Tahoe Thursday night and with some tweaks, my system auto-boots to navi:

http://vimeo.com/39119557

I'll outline the changes when I can verify this is stable...

Has this been verified to be stable yet? I'd really like to know how to get this working.

Thanks

Actually, between the beta versions of the new software and the iGo bootup mod, it's been anything BUT stable. The last version of the firmware should be out very shortly and I should be able to nail this down once and for all. Advent was right in stating that, for most customers, this WILL NOT be a good solution since there are so many operations going on in the background at bootup time that you have no control over - all of which affect how the internal memory gets allocated and how fast or slow each operation completes its job.

What I have noticed is that, if on bootup you have other things going on with the deck like re-indexing your iPod, pairing BT, reading a USB stick, reading XM data, etc), AND booting the iGo system up in the background, there are all kinds of ways this unit will run out of memory and start throwing errors. The most reliable way to get this thing to "play nice" and work every time is to boot up into the AM/FM radio and not switch to another source until you know everything has finished.

So, if you mainly listen to talk radio, booting iGo in the background may not be a bad thing. However,if the first thing you do when you get in is to plug in your 160GB iPod and start playing movies and pairing up your iPhone at the same time, it may not be a great idea...

430HP70 · April 6, 2012

it still seems that their boot order needs to be worked out. if "auto switch to gps" can work, they should be able to write it in so that the nav boots before all that other stuff happens. i understand the can bus and xm need to happen first, but theres no reason that the ipod cant sync 15 secs later and after the nav boots. i still cant understand how the factory unit can do it, but the aftermarket cant. ive never had any delays with the wifes nav. one thing ive noticed with the factory unit is that when i open the door to get in, it sounds like the nav is doing something. whether its starting its boot process in the background before entering a key or just turning the cd/dvd, im not sure.

wottenad · April 7, 2012

it still seems that their boot order needs to be worked out. if "auto switch to gps" can work, they should be able to write it in so that the nav boots before all that other stuff happens. i understand the can bus and xm need to happen first, but theres no reason that the ipod cant sync 15 secs later and after the nav boots. i still cant understand how the factory unit can do it, but the aftermarket cant. ive never had any delays with the wifes nav. one thing ive noticed with the factory unit is that when i open the door to get in, it sounds like the nav is doing something. whether its starting its boot process in the background before entering a key or just turning the cd/dvd, im not sure.

If you look at it from Advent's standpoint, since there are about a hundred different variables that can affect the user's experience on this deck, they have taken the safe route that will work 100% for everyone, rather than cause problems for a small percentage of customers.

Having said that, I think that if we clarify what will affect the process, and educate everyone about the unintended consequences of doing the bootup mod, then you can do whatever you want and if it blows up, at least you were warned.

What you CAN'T do is call Advent tech support and ask them to fix something they never allowed you to do in the first place...

looch10 · April 28, 2012

Could some please either explain which file to edit to get the altitude to work and how to get rid of the drive safe screen. Also is there a way to make it load up so when i hit nav it doesn't start to load then.

If need be to make it easy just tell me which post. I saw most about making the drive safe screen go away. but not sure which for altitude.

Last, is there a way to make it so when i have XM on and its telling me to turn or beep that it doesn't cut the music off?

Thanks.

looch10 · April 28, 2012

Has anyone done anything with the speedcamera setting yet? Want to know how to install those and the POIs.

Bill in Niantic · June 10, 2012

How do you get the screen with the speedometer, compass, and atitude info in lieu of the map?

redjewel2ss · July 10, 2012

alright i'm reviving this thread! i've looked at previous replies and i still haven't figured out what exactly deletes the warning page and fixes the altitude. could someone please tell me specifically what to change in what file to correct these? thanks!

madadd · July 17, 2012

alright i'm reviving this thread! i've looked at previous replies and i still haven't figured out what exactly deletes the warning page and fixes the altitude. could someone please tell me specifically what to change in what file to correct these? thanks!

You will need to change your sys.txt file in the root directory. This is my sys.txt file feel free to copy and past.

[debug]

experimental_features="1"

skip_eula="1"

[device]

sdcard_name="SDMEM"

type="Audiovox_USA_OE"

[interface]

extra_settings="1"

drive_carefully="0"

This will bypass the warning page, and menu. It takes you directly to the map.

I kinda skimmed the thread and noticed some people have altered the .ini files that really should not be neccessary (probably mentioned in the thread and i just missed it) those are written by the program on the fly. Just ajust the sys.txt file and after a few times of booting up and using the nav you should get the desired results you make in the sys.txt file.

Before playing with anything on your microSD card make sure you make a complete copy of the card on your computer. Not just the sys.txt file. This was the first thing I did when I got my Advent from Walt and I can't tell you how valuable a backup of the orginal microSD card was in saving me from myself and faulty SD card reader on one of my computers.