Update worked, but I lost the TTS on my device (XXL IQ routes, which didn't have TTS with original navcore) - I had a SE navcore before. Any idea how to get TTS back?

JuliusC wrote:Update worked, but I lost the TTS on my device (XXL IQ routes, which didn't have TTS with original navcore) - I had a SE navcore before. Any idea how to get TTS back?

Place the folder LoquendoTTS from your backup in the root from the XXL IQ routes and try if it works.

well, tomorrow will be the day. I'm wondering what will happen.
Until then, a big thanks to holyhead, that TomTom One compatible firmware seems to work for me.

I have a number of TT520s, which I upped the original Navcores to version 9.400 some years ago, yesterday I upped one to 9.541 and this morning I put both on to see if the 9.400 version would fail, and the 9.541 would work.

Surprise - when both locked on with the same times and location and using the same satellites. I will be taking both out this morning to see if both perform normally.

FYI I downloaded the 9.541 cab, then extracted the files directly over the current ones in the internal directory (ovewrite) as the cab file was not to my mind a full Navcore file, then I ran fastactivate to patch the ttsystem file, restarted and all maps were OK. Note I DID backup the complete directory first.

I see on the TT website that their support is open today (Sunday) ! - must be expecting a lot of calls.

UPDATE

9.400 only works intermittantly, sometimes will not lock any satellites.

9.541 works fine in 520.

Interesting...thank you for the feedback

I got some inspiration from aerostar2, and tried to extract the cab directly over my existing Rider version, 9.500 I believe.
Device crashes after boot. I won't be surprised if it's related to the skin.

Hm, I've tried the 9.541 on my One v3 today, and it no longer works.
One XL has same problem: the 00:00 time issue.

I wonder if it could be the chipset. I guess maybe the navcore was only updated for the newer chipsets.

firefoxie wrote:Hm, I've tried the 9.541 on my One v3 today, and it no longer works.
One XL has same problem: the 00:00 time issue.

I wonder if it could be the chipset. I guess maybe the navcore was only updated for the newer chipsets.

We're all still trying to pin down exactly which devices are causing the problem...

So far it looks like all sirf star chipped devices are ok, it's the first level Global Locate that seems to have issues

Try updating with GPSFix as some people have reported that it fixed their clock problem...no promises though

Tomtom Rider3 equipped with the navcore from Tomtom Home is having the same problem:
Time 00:00
No way to set the clock correct.
Wonder why I updated that one, it worked with clock 00:00 and the patched navcore 9.500
No navigation test done yet.

Update on the time issue on the tomtom Rider3.
Actual navcore 9.205 downloaded directly via Tomtom Home and patched.
Actual map: Western Europe (made smaller) 1025.9386
When powering up, I have the correct time on the screen for about 3 to 4 minutes
after that it jumps to 00:00
When doing the GPS Fix through Tomtom; even at startup time is than 00:00
I see that when GPS Fix is done, a additional file is added in the map Ephem (3 files instead of 2 files)
Bit ennoying, but not mortal.
I just delete the time from the screen and look at the bike what time it is.

fredderf wrote:We're all still trying to pin down exactly which devices are causing the problem...

So far it looks like all sirf star chipped devices are ok, it's the first level Global Locate that seems to have issues

Try updating with GPSFix as some people have reported that it fixed their clock problem...no promises though

I have a One v2 somewhere, if I remember correctly it has a Sirfstar chipset.
I'll try the new navcore on that thing and see if I can confirm anything.

The One v3 and One XLhave a Hammerhead AFAIK, the new navcore seems to add nothing to counter the 00:00 issue on these devices. I've tried them this morning to work. GPS reception seems limited to just 3 satellites at any time. I'm quite sure I used to have more. When starting up it loses fix quite often, after half an hour it seems to have a (somewhat) complete list to quickly keep switching.

Charlie62 has posted a possible fix that could be useful here...it hasn't been tested on a Rider or a One & I don't have either to test myself?

Obviously, backup your current setup first...

Then try this...download the following glgps file found inside the NC 9.541 bin folder and replace the same file in your own navcore...disconnect & test

Any good?

Hidden Content

This board requires you to be registered and logged-in to view hidden content.

fredderf wrote: Then try this...download the following glgps file found inside the NC 9.541 bin folder and replace the same file in your own navcore...disconnect & test

Does this mean that we should replace the initial GLGPS (in for exemple NC 9400) file by the one in NC 9.451
or
should we use NC 9.451 and replace that GLGPS file by the one we had in our initial NC (ex 9.400 for Rider3) ?

dkn9230 wrote:
Does this mean that we should replace the initial GLGPS (in for exemple NC 9400) file by the one in NC 9.451
or
should we use NC 9.451 and replace that GLGPS file by the one we had in our initial NC (ex 9.400 for Rider3) ?

Yes, this one

As far as I test with a Rider 3, the before mentionned "solution" don't work for 100%.
If I use NC 9.400 with the new GLGPS file, the GPS works, it find his sattelites, but again.....
at startup the clock shows the correct time, but .....
after a couple of minutes the clock shows 00:00.
This is identical if I use the new patched NC 9.451 (from TT Home),
clock correct at startup, but after 2 to 3 minutes it goes to 00:00
as mentionned in previous posts.