Day Map Color selection resets itself

Wed Oct 05, 2011 5:33 pm

Hello,

I'm using iGo primo 9.2.0.192885 version.

In day map colors, I choose "Minimal Guri" as my selection and map returns to this setting successfully. However my selection does not stick and when I turn off the device and open it back, day map color returns back to "Default Day Colors".

This happens when I set DISPLAY/Day SKIN THEME/ to "Default" or "Picto".

It cures when I set DISPLAY/Day SKIN THEME/ to dimka wa 1.3.6 day but I don't like this theme.

How can I fix this so that my theme is default and my color set is "minimal guri" and this sticks even after device is turned off and on?

TIA!

Wed Oct 05, 2011 5:42 pm

Does the Night setting stick if you change the night colors?

Thu Oct 06, 2011 6:24 am

Nope same thing happens with night setting. It reverts back to "default night" color.

Thu Oct 06, 2011 6:56 am

Changes are not being saved:
This could be one of a few things. The most likely suspects.......
[color="red"]1)[/color] Something in sys.txt is over-riding saved changes when Primo starts up.
[color="blue"]2)[/color] Something is corrupted in the Primo/Save folder.

[color="red"]1a)[/color] Post your sys.txt (copy/paste the contents)--this would be the first thing to look at.
[color="blue"]2b)[/color] Delete the Save folder and restart (this will be like setting up for the first time again and the Save folder will be recreated with all new settings saved as you make them)

Thu Oct 06, 2011 7:05 am

Possible 3):
After setting up things basic, save folder (or sd card) is write protected.

Thu Oct 06, 2011 7:23 am

Thanks for your assistence!

Here is my sys.txt:

[debug]
skip_eula=1
experimental_features=1

[interface]
show_exit=1
extra_settings=1
show_programs=1
drive_carefully=0
start_navigation_time=10
show_minimize=1
shutdown_time=0

[other]
demo_enabled=0

[vr]
disabled=1

[sound]
csv_voice_enabled=1

[music]
music="\SDMMC\mp3"

I don't know what "vr" parameter is for but apart from that, I don't think anything in there is causing this. You'll know better though so I appreciate your advice.

The sd card is not write protected. As a matter of fact, every other setting changes I do, sticks. It is just map colors that resets.

I checked save folder now and I can confirm files there are updated (Their datetime stamps belongs to time I last openned the device).

I'm also posting system.ini from save folder in case it helps:

[config]
last_saved_system_time="2011.10.05.|17:34:08.000"

[gps]
baud="57600"
gpstime="1317208293"
last_gps_date="2011.08.22."
last_gps_time="17:27:58.000"
port="1"

[http]
enabled="0"

[interface]
collect_statistics="1"
theme=""
theme_day=""

[keyboard]
panel_alpha="Default"
panel_custom=""
panel_ext_numeric=""
panel_geo="Geo"
panel_numeric=""
panel_phone=""

[lua]
calcgreenroute="0"
currentvoiceissupkmm="1"
currentvoiceissupmlf="1"
currentvoiceissupmly="1"
gotgps="1"
junctionviewon="0"
last_country="_TUR"
lastdestination="___"
overviewmodeon="1"
speedwarningalwaysvisiblechk="1"
trackshowonmap="1"
tripinfovisible="1"
vdeviceactivationfromgetextras="1"
veasycolormode="0"
veasynavmapmenuactive="1"
veasynavtripinfoopen="1"
veasyviewmode="1"
veasywizmodeonfirststart="0"
volume_unit="0"
vselectedtripinfonoroute="2"
weasynavtripinfoopenwithoutroute="1"
wselectedtripinfonoroute="1"

[map]
3d_dem="0"
auto_nightmode="0"
follow_gps="1"
rasterorder=""
rotation="0"
saved_nightmode="1"

[map_update_checker]
old_map_last_check="1317208293"

[mydata.tracks]
autotracklog_enabled="1"
filename_counter="247"
record_auto_track="1"
show_on_map="1"

[navigation]
autoreplan_action="AUTO"
watched_restrictions="49"

[oasis.pictures]
slideshow_time="5"

[other]
is_nighttime="0"

[other.highway_drive]
poi_search_category1="Parking"
poi_search_category2="Cafe_or_Bar"
poi_search_category3="Leisure"
ui_filtered_list="1"

[poi]
priority=""
priority_save=""
sort_order="Restaurant,Accomodation,Petrol_Station,Parking,Medical"
sort_order_save="Restaurant,Accomodation,Petrol_Station,Parking,Medical"

[power]
backlight_status="0"
powermgm_state="0"

[regional]
lang_path_hint="lang\Lang_English-us.zip"
language_key="english US"
language_lcid="1033"
units="1"
voice_key="Eng_aus_f2_lua"
voice_path_hint="voice\Voice_Eng-aus-f2-lua.zip"
weight_units="0"

[regional.timezone]
auto_index="311"
index="30"
last_auto_time_sync="2011.09.28.|11:26:48.000"
tzbias="-120"
tzdbias="-60"
tzdst="1"

[route]
route_type="FAST"

[screen]
nightmode="0"

[sound]
dynamic_volume_os_amplification_step="15513913"
os_muted="0"
os_volume="180"
voice_muted="0"

[traffic]
last_switchoff_time="1317881660"

[traffic.settings]
detour_acceptance_mode="1"

[warning]
speedcam_soundtype_0="0"
speedcam_soundtype_1="0"
speedcam_soundtype_10="0"
speedcam_soundtype_11="0"
speedcam_soundtype_12="0"
speedcam_soundtype_13="0"
speedcam_soundtype_14="0"
speedcam_soundtype_15="0"
speedcam_soundtype_16="0"
speedcam_soundtype_17="0"
speedcam_soundtype_18="0"
speedcam_soundtype_19="0"
speedcam_soundtype_2="0"
speedcam_soundtype_20="0"
speedcam_soundtype_21="0"
speedcam_soundtype_22="0"
speedcam_soundtype_23="0"
speedcam_soundtype_3="0"
speedcam_soundtype_31="0"
speedcam_soundtype_4="0"
speedcam_soundtype_6="0"
speedcam_soundtype_7="0"
speedcam_soundtype_8="0"
speedcam_soundtype_9="0"
speedcam_warning="1"
speedwarn_alt_tolerance="115"
speedwarn_tolerance="115"

Thu Oct 06, 2011 7:54 am

Logician wrote:I don't think anything in there is causing this.

You are correct. There is nothing in there causing that.
In doing a bit of research, however, I have read that the inability to save color schemes is a known bug that NNG has not bothered to fix.
The two major Skinners, however, HAVE fixed it, but you say you don't want to use a skin, so you really have two options:
1) Live with it as a minor annoyance
2) Edit data.zip to permanently change the default colors. This will work, but editing data.zip can be dangerous, and leave Primo in an unworkable state (which is why I am not listing the steps at this time--but I can, if you want to try that way). This way will not cure the 'saving' issue, just change the default. The only currently known way to cure the saving issue is to use (as you already found out), the diMka skin...of the GJA skin for Primo 1.2.

Thu Oct 06, 2011 8:32 am

Logician wrote:I don't know what "vr" parameter is

PS. VR is Voice Recognition, and to leave it disabled ("1") is correct, as it will not work anyway. "1" is the default, but in packages I put together...in hopes that VR would eventually become a viable option..I left that in sys.txt so it could easily be changed to "0" (enabled).

Also, good job on posting everything as you did. It could have been significant, but in this case, alas, it was not.

Thu Oct 06, 2011 9:03 am

Thanks for your detailed help, it is very much appreciated!

I wanted to ask if it is possible to put a line in sys.txt which will forcefully apply the color setting during the boot?

Regarding the data.zip editing, do you meant, it is dangerous to "edit" it if you are not careful or is it dangerous to use an edited version?

I understand it can tricky to edit this file without breaking things and I can try doing it by properly backing it up etc. But if you meant not the editing process but meant using a edited data.zip can make the device unstable, I wouldn't want to do that. :)

Thu Oct 06, 2011 9:14 am

I have a possible workaround. I haven't tried and am not sure about its effectivity, so back up first! Always back up before making major changes!
Bear with me now, I have no GPSdevice in front of me and no way to check the correct file names.
You know what scheme you want, so either
- delete the default schemes (and others you don't want) so there is no choice)
- rename the one you like to the default one and rename the default one to default.old (you know what I mean)

Thu Oct 06, 2011 9:43 am

nabi wrote:rename the one you like to the default one and rename the default one to default.old

Normally, that would be an excellent solution.
However, there is no such file as "default" in the content/scheme folder. The "default" color scheme is within data.zip, and the ones in the scheme folder are the alternatives which cannot be saved upon restart.

Thu Oct 06, 2011 9:53 am

Logician wrote:I wanted to ask if it is possible to put a line in sys.txt which will forcefully apply the color setting during the boot?

Not that I have been able to determine or find, but sys.txt is one of those files that really nobody knows all the possible options and switches, so there may be one.
Seriously...nobody. Not even most of the engineers at NNG.

Logician wrote:Regarding the data.zip editing, do you meant, it is dangerous to "edit" it if you are not careful or is it dangerous to use an edited version?

Could be both. Using a modified data.zip can compromise other future settings or features that may not yet be known, and yes, you must be careful to edit and save it correctly. Do not just unzip, change something, and zip it back up. That would be guaranteed not to work and break Primo. You would need to open the file in a utility such as winrar that allows editing and updating within the zip file without fully extracting it. Chances are that simply changing the default colors would not break anything, but a backup is essential, of course, just in case.
Let me know what color scheme you would (permanently) want for both Day and Night (they can be different if you like), and I will list the exact steps to accomplish that.

Thu Oct 06, 2011 11:20 am

Yurbuh Tuggly wrote:Normally, that would be an excellent solution.
However, there is no such file as "default" in the content/scheme folder. The "default" color scheme is within data.zip, and the ones in the scheme folder are the alternatives which cannot be saved upon restart.

As I said, I have no device on me to check file names.
I know that in a past release, I did change some colors in the default scheme (the famous 'black arrow' issue) and now you may shoot me but I won't confess what I changed where.

(I don't remember)

Thu Oct 06, 2011 11:43 am

nabi wrote:I know that in a past release, I did change some colors in the default scheme

The only way I know for Primo 1.2 is to edit the color.ini in data.zip/ui_igo9/scheme/day{and/or /night} which is a bewildering array of choices (copy/paste from an existing color.ini scheme is the safe way to go lest you create some totally bizarre Frankenstein default).
But that's not to say there might not be another way. I thought of maybe creating a ui_igo9 folder under {Primo}/, then a Scheme folder, then a Day and Night folder under that with the desired color.ini in it, but I am totally NOT sure that would work.

Thu Oct 06, 2011 12:04 pm

I forgot to add it was an (at that time) new iGO release, in which the orange arrows (on the road) that show the direction to follow were in an awful black.