Results 21 to 30 of 641
-
7th April 2019, 09:09 PM #21
In addition to my experinece in post #8 and to be clear. The problem is, that when you have a satellite fix, the time displayed is 0:00
Without connection to the satellites the time displayed is the correct time. Funny.
-
The Following 1 Users Say Thank You to 4Wheel For This Useful Post:
- [ Click To Expand ]
-
Alfred_ML (8th April 2019)
-
7th April 2019, 09:18 PM #22
My GO910 had NC 9.510 installed while two days ago I installed the 'Standard TomTom version of NC 9.5410 on my GO910 hoping that it would run?
I waited and waited for Merlin to come and wave his magic wand as the GO910 'stuck' on the start up screen and would not pass 'Go'!
Merlin didn't come, so that killed that try.......
Then I was provided with an LE version of NC 9.5410 and having gone back to NC 9.510 (YES I do keep complete backups, as I prefer not to be caught out with my trousers round my ankles and cannot move!!! Arrgh)
So I overwrote the 3 files I needed to with the LE files and now I have a GO910 which works OK with NC 9.5410 installed.
It has currently found 6 satellites, tells me the correct time and even if I change it and then press the 'Sync' icon it sets it back to the correct time again.
I currently have the Europe_1025_9386 installed.
After switching off and pressing the 'Reset' button nothing changes when I turn on the next time, but the battery is not 'drained' and stays as full as I left it when using the 'Reset' button.
-
The Following 1 Users Say Thank You to † Traveller63 For This Useful Post:
- [ Click To Expand ]
-
pe1agp (8th April 2019)
-
7th April 2019, 10:23 PM #23
I smell to trap this navcore 9.541
The GO920 has been hung several times and although I try to go back to 9.510, it does not work as before.
He has also created some files: clmdata and watchdogtrace.dat that he had not seen before and I do not know what purpose they have.
A fragment of the watchdogtrace.dat:
---- Report ----
Pid: 00509
Timestamp: 1554572643
Version: 9.541.3145439 (s3c24xx)
Received signal 14 [errno 0, code 128]
Fault address: (nil)
The stack appears to be corrupt.
-
8th April 2019, 12:31 AM #24
Clmdata and watchdogtrace.dat (after first use) you can find also in an older NC. Not really new...
But i'm also considering, if i not copy the 9.510 backup to the ONE3rd once again. I don't need this 9.541 trouble...
-
8th April 2019, 12:56 AM #25
Interesting experience from a guy "underground":-
Hi. My satnav time stopped working today, just reset to 12;00 and stayed there so I didn't get eta times on my satnav. (go live 750) I updated the device in tomtom home and then used fastactivator to re patch everything and all's good again now, so, yes I would say if you want the time to show correct on your TT then it's best to update and re-patch.
SPAM HUNTER/KILLER
Please do not just post "thanks" but use the "thanks" button bottom/right or the reputation star "*" bottom/leftS i m p l e s
-
The Following 1 Users Say Thank You to biggerdave For This Useful Post:
- [ Click To Expand ]
-
pe1agp (8th April 2019)
-
8th April 2019, 12:58 AM #26
Final conclusion TomTom One Third Edition.
Works well under Navccore 9,541 with the VocalizerTTS installed for voices.
A nice detail is that in the GPS status page the time is displayed correctly now 18:09:50 UTC and as local time 20:10, while there is no time known at the status bar.
Incidentally, the One refuses to show a demo route on receipt of only three satellites, but does calculate exactly how long the requested route will take under normal circumstances.
After each reset, the UTC clock starts at 00:00 hours, but with a good reception of only 1 satellite, the time is taken over.
The manually set time matches the local time with a difference of 2 hours and 1 minute, so the UTC time is almost 2 hours and 1 minute behind of the local manually set time.
By the way, my GO 950, which normally works, does exactly the same after a reset and the UTC time also starts at 00:00 hours, with the difference that it starts at 02:00 hours when receiving one or more satellites, but after recovered a few minutes with the real UTC time equal to that of my One Third Edition.
Provisionally enough for today, another test tomorrow with the One Third Edition.Last edited by pe1agp; 8th April 2019 at 01:21 AM.
-
8th April 2019, 01:44 AM #27
-
The Following 1 Users Say Thank You to Alfred_ML For This Useful Post:
- [ Click To Expand ]
-
pe1agp (8th April 2019)
-
8th April 2019, 01:52 AM #28
Hello,
You don't say how you installed NC 9.541.
If it was on a HDD or SDHC which was not formatted before you commenced the build then you might have a few bits of 'debris' left behind on the Media you use which might be causing your problems?
Secondly, again you do not say if when you try to go back to NC 9.510 from a Backup, either from a TomTom or Direct Backup made when your 9.510 was working OK.
So without that info I cannot recommend a possible solution for you.
Sorry.
-
8th April 2019, 02:19 AM #29
I have tried in an SDHC of 8Gb class 10, also in the 4Gb of the internal memory.
In both cases without garbage because I have executed clear_flash downloaded from this forum before installing.
I have already installed navcore 9510 and it works without problems.
-
8th April 2019, 02:36 AM #30
2023.Q2 Here Australia,New Zealand
Australia New_Zealand HERE 2024.Q2 please