View previous topic :: View next topic |
Author |
Message |
whiskysav Occasional Visitor
Joined: Feb 28, 2006 Posts: 1
|
Posted: Sat Dec 08, 2007 4:09 pm Post subject: warn when near poi |
|
|
I have updated my go 700 to 7.162 and now when i change the sounds on warn when near in poi they always revert back to the default setting when i turn my device off and on again. does any body else have this problem ? or can anyone advise on a fix |
|
Back to top |
|
|
Andy_P Pocket GPS Moderator
Joined: Jun 04, 2005 Posts: 19991 Location: West and Southwest London
|
|
Back to top |
|
|
spannersatcx Regular Visitor
Joined: Mar 17, 2006 Posts: 60 Location: Cheshire
|
Posted: Sun Dec 09, 2007 2:20 pm Post subject: |
|
|
Report it to TomTom, perhaps the more that report the small chance is they may actually understand that since the update they have caused this problem, but I very much doubt it, they blamed the poi's from PGPSW! |
|
Back to top |
|
|
mullengers Occasional Visitor
Joined: Mar 02, 2006 Posts: 15
|
Posted: Sun Dec 09, 2007 2:52 pm Post subject: Re: warn when near poi |
|
|
whiskysav wrote: | I have updated my go 700 to 7.162 and now when i change the sounds on warn when near in poi they always revert back to the default setting when i turn my device off and on again. does any body else have this problem ? or can anyone advise on a fix |
I've had this problem since 7.161 I think. I use a GO910 and like "Beep 5" for all speed cameras (Tomtom subscriptions and PGPS subscription). I like "Polite 1" for the Red Light cameras.
I find that it remembers the Red Light "Polite 1" just fine.
It always reverts my selection of "Beep 5" for PGPS speed cameras back to the first "Bell 1" sound.
Putting OGG sound files in the \sounds directory doesn't work either - it forgets them too and goes back to "Bell 1".
The only work around I can find is to extract the sounds (I used oggsplit.exe to get the OGG files with funny names and then Nero to listen to them all until I found the right ones) from the data.chk file (to say "Beep5.ogg" for example).
Then make multiple copies of them and rename them to the same names as the OV2 files for the POI you want - PGPS speed cameras in my case.
There is an interesting bug in 7.161 and 7.162 too that when you do this you still have to select "Warn When near POI", distance and "Sound Effect" for the POI you want and then answer "YES" to a blank sound file name and "Is this the sound you want to select?" question.
A second bug is that if you select an inbuilt sound from data.chk ("Polite 1" for the red light cameras) and don't have a .ogg file saved for it then the blank message retains the name of that inbuilt sound next time you try to select a sound for a POI with an .ogg file associated with it - programming error where Tomtom are not re-initialising the "sound name" variable properly. Basically everything looks like it becomes "Polite 1" until the next inbuild sound is selected from data.chk! It does actually assign the correct .ogg sound fiules to POIs though!
I'm abit sick of reporting bugs to Tomtom as they mechanically tell me to (1) reset my device - then after I update the call (2) delete settings.dat - then after I update the call (3) delete everything in the root of my GO 910 to solve software bugs... you get the picture. They have been doing this for the night-to-day switch failure that I reported in detail to them in 7.161 and still breaks in 7.162.
I think they should release a "settings.dat" integrity checker program if they think it is corrupt. Like a mini database checking tool. |
|
Back to top |
|
|
|
Posted: Today Post subject: Pocket GPS Advertising |
|
|
We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
|
|
Back to top |
|
|
|