So hi again fellas.... thought I would have another try with all this truck map stuff. I've gone and formatted the internal storage to start with a blank device, then used Downunder35m's Universal Navcore Installer to install the 9.701 truck navcore (for 32mb devices) to this device - that was the easy part. Ran that Clear Flash tool just for the sake of the argument - no problem there. Copied across 'Australia_1120_12101' and 'Australia_TRUCK_1110_11881' KNOWING the 1120 car map was compatible (checked map compatibility chart beforehand) and thinking the 1110 truck map was compatible, ran FastActivate to patch meta.txt (checked meta.txt and saw an meta code entry for both 1120 car map and 1110 truck map), patched maps and all seemed well. Restarted device - took a couple of restarts. Was presented with a screen asking what type of vehicle I was using - selected truck. Was then asked specific dimensions of truck and weights - possibly entered wrong axle load weight (was trying to work out what kind of truck I drive - in this case an MR or medium duty truck with one drive axle with tare weight of 8000KG and load capacity of 8000KG for total of 16000KG) -
Length 7900mm - Width 2500mm - Height 3000mm - Tare weight 8000KG - Axle weights (I entered 4500KG - possibly wrong)
Had a moment where it seemed to work, then was presented with a screen declaring
"The current map does not contain truck attributes. Truck routing can therefore not be supported. Car routing will be applied"
At that point the device rebooted and got stuck in a reboot loop.
So now, 64 million dollar question - completely sure the 1120 car map works with this navcore on this device. I'm going to say the 1110 truck map DOES NOT WORK on this device. I've done a full backup of the previous 9.501 navcore and map which works just fine. Could you please put me out of my misery hahaha and shed some light on all this please. Would like to know if there is a truck map which will work on this device and has a corresponding meta code - from what I've been reading I could be out of luck. I will revert to the backup shortly if this has been a waste of time. Many thanks again!!!

Every variant of the 'Australia' map set is infected with viruses (including 'Australia_1105_11759' which is the map most referred to). Oh well, this forum was worth a shot to update my ancient One XL...

lostallday wrote:Every variant of the 'Australia' map set is infected with viruses (including 'Australia_1105_11759' which is the map most referred to). Oh well, this forum was worth a shot to update my ancient One XL...

Infected???? Have you not heard of False Positives" PS Why are you still trying to use v1105 from Feb 2023 when there are newer versions around including this weeks v1130?

So hi again Navitotallers... still having joy of nearly 20 year technology working with a fairly recent map on my TomTom One XL (v9)
(have the 1130 series Australian map which is 'Australia_1130_12306')
Still starts up fine from cold boot and warm boot. I gave him a name some time back - me good old mate Pauly - finds satellites as fast as he can, have had some instances where he seems to be be getting overloaded - 20 year old hardware, modern day etc. so reboots happen - little frustrating, to be expected I guess...
So anyway... still happy with Pauly. Rock solid.
Now, I've still got some questions with no real answers from reading posts here and the ****** and ******** sites which I've tried to make sense from and failed miserably - possibly because of somewhat contradictory information.
Starting with the good old time display issue. When 'Pauly' is on and no route selected, time displayed is always 12:00am
When planning a route, time stays the same.
When navigating with a selected route, time stays the same - only thing that does change is the trip time.
So question #1 - is this related to GLGPS or TTCONV or something else? Is there still a possible fix (have I put files in the wrong location maybe?)

Question #2 - not sure if this is anyway relevant - does this device require TTGO.BIF or TTNAVIGATOR.BIF (my original backup of the device contains both .BIF's)

Information from software when device is on:-
Device AKSZC CSD6J
App 9.510.1234792.1, OS 547200
32 MB RAM (free: 3.2 MB)
GPS v1.20, Boot 5.5128
Map: 'Australia_1130_12306' v1130.12306
Language: English UK

Information on sticker on back of device:-
S/N : RH***********
8EG0.025.00.7.52

Information on sticker on bottom of device:-
TomTom XL
4EG0.001.08

If there are some real answers out there it would be greatly appreciated. I realise I'm asking a bit considering how old this One XL is. I'm glad that I can still use it even in today's modern world. I would like just a bit more life from it until I have to retire the old bugger haha. Thanks heaps again!!
P.S if needing files to compare/upload, please let me know. Happy to provide any extra info. Thanks again!

Ok, I have removed references to other GPS sites from your post as it's considered bad forum etiquitte. Secondly, I've removed most of the serial number.

Question 1: The clock issue is probably due to the well known WNRO problem as discussed here. You can install the patch or you can update the navcore with an updated & specially modified one which will fix this issue, the problem with the device rebooting will also get fixed at the same time as the navcore has a swap file built in. The reason it happens is because the map you are using has more features than a 32MB RAM device can handle. Your post above says that the device has '32 MB RAM (free: 3.2 MB)' which is not enough free RAM for the device to operate reliably. I did tell you about this before here. To fix it you can either install a lower featured map or try the updated navcore I referred to.

Question 2: Only a TTGO.BIF is required.

I will provide the navcore for you below but the usual disclaimers apply as well as the advice to make a full backup before you make any changes to your device so you can revert it back to it's original state if needs be.

Hidden Content

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

Hi again fredderf. Many thanks for getting back to me - sorry for taking a week - usual life tasks get in the way, can't find ten minutes lately to properly thank someone immensely... Better late than never...
Also humbly apologise for referencing the other GPS forums. As I had said, I had gone through those sites getting more confused with conflicting information - should have stayed and will stay with Navitotal from this point as all the users here know their GPS units inside and out and have fantastic support from the likes of yourself and biggerdave - we would all be screwed without you guys!!

So onto my case - I took your advice and grabbed the modified 9.541 navcore from here, did a backup to start with, did a fresh format of the internal 1GB drive on this TomTom One XL v9, used the ClearFlash tool once, copied the navcore across, copied what I thought was the last compatible 'Australia' map onto the device (Australia_1130_12306), copied TTActivator across as well as Fastactivate - wasn't too sure which would be better - ran TTActivator, it found the map and generated a meta from the updated meta.txt I got from here, gave Pauly a reboot, and complete success!!
Pauly started up, took a couple of minutes to find some satellites (had to sit out near my garage - couldn't find satellites while sitting inside - no big deal), found satellites and my location and away we went! Sorted!
Checked all other settings, clock issue resolved itself - displayed correct time at that point, so I figured I would go for a short drive - all functions functioning correctly. I've had a laugh at Pauly because like me he's a bit slow on the uptake so as I drive past a side street, he's lagging behind by about 100 meters or 1.5 seconds but I can live with that. He is bloody perfect and I won't change him hahaha
And thank you for clarifying the .BIF issue. Not sure where the TTNAVIGATOR.BIF file came from - as I said, my original backup that I had done contained that file as well as a TTGO.BIF so I was a little confused. I really appreciate the feedback.

So my last question(s) - I have attempted to use the 1150 series 'Australia' map (Australia_1150_12729) that's been provided through here. To my surprise it has been accepted on my TomTom. Thought my device would be too old to run it (bought this unit back sometime around 2008 or 2009). Does that maybe mean I can still keep putting updated maps on it, assuming that there will be updated maps with the corresponding meta codes?
Last of the last questions (this is it - I swear hahaha) - and this is purely a cosmetic thing. My previous navcore was from biggerdave's archive (9.501)
This navcore (I'm pretty sure) didn't have an up to date WNRO patch did it? So did I need to find a patch? The navcore operated just fine - just had that pesky clock issue - and I was able to still navigate around. Any ideas on this one?(also no offence to biggerdave, absolute legend in my opinion!!)
Master fredderf, thank you honestly for all the advice, feedback and opinions. How do I go about 'thanking' you here on Navitotal (haven't worked that out yet haha)
Many, many thanks and long live Navitotal!!!

You should stick with the navcore I gave you. It's no offence to biggerdave but his NC was probably an older build that wasn't WNRO compatible so it would need patching to get the clock working correctly, it also has no swap file which is why you were having rebooting problems. NC 9.541 is the updated version of 9.510 anyway.

Yes, you can still update your device but you will have to use NAV3 maps as those are the only ones we have meta codes for now.

You can use the thumbs up button on a members post to thank them which is next to the quote button in the top right corner of their post.