@asprin624
He's clearly turning it off fully as his pics in post #24 show the splash screen then warning screen before the card format message.
@asprin624
He's clearly turning it off fully as his pics in post #24 show the splash screen then warning screen before the card format message.
@Butters and @aspirin624 I have to aplogise as I have found the source of my problem, two sdcard slots. I have only ever used the dashcam sdcard and did not realise there was another slot on the bottom of the unit. I have therefore successfully downgraded to 5.40. Many thanks for your patience and perseverance with my problem, very much appreciated
@mmain
Easy error to make. I see the thread's been marked "Solved" by staff. Have you tested the downgraded device for RTL Trap location shutdowns already?
@Butters I am pleased to report a successful outcome at both 'black spot' locations and bluetooth is also working just fine. Many thanks once again
@mmain
You're welcome.
Keep in mind that GarminExpress may insist you update fw before allowing further Lifetime Map updates. I'd allow it to update only if it's a later version than V5.90 otherwise your problem is most likely to return. If you need to load new maps you can still allow a fw upgrade to V5.90 and then use the card again to downgrade back to V5.40 after the map update. Any version of fw after V5.90 most likely will not cause the same errors as V5.70 & 5.90.
To use the card again you must first remove the file named "last_id.bin" that has been created in the 2270 folder. The other newly created file in there named "update.log" can remain.
@Butters it seems my announcement of success was premature as the problems have recurred today. I will describe chronologically what has happened.
6th Sep
20:00 – Firmware revision 5.40 successfully loaded
7th Sep
06:50 – Leave home
07:10 – Passed through morning location without problem
07:20 – Arrived at work and reconfigured Bluetooth (had been cleared by firmware update)
17:00 – Leave work
17:10 – Passed through evening location without problem
17:30 – Arrive at home and set Home location on Garmin using Current Location option
8th Sep
06:50 – Leave home
07:10 – Garmin crashed at usual morning location
07:20 – Arrived at work
17:00 – Leave work
17:10 – Passed through evening location without problem
17:11 – However, Garmin crashed at location 1 km further than usual
I am now thinking this is all Bluetooth related, but once configured, disabling Bluetooth does not eradicate the problem
One cell (or more) in the memory chip is defective.
@mmain,
Are you putting in the location to drive to work and back home as favorites or use using the Garmin as info on the screen as you drive?
I would delete the favorites if you set that up.
Then make new ones.
But use the Garmin just as info on the screen and not a location to go to first.
If it crashes that way then there is a memory problem like Boki_Srb points out.
As I do not know if your Garmin is still under warranty it might be better to send it back to be recondition.
Even if it will cost you.
Plus forget about using any of the Garmin app links.
In fact I would remove them from your phone as you are testing the Garmin.
Garmin Smartphone Link has lots of problems........
Here is one quote:
Quote:
I despise this app! It never keeps my phone and GPS connected. I've tried unpairing, uninstalling, resetting, absolutely EVERYTHING I can and it refuses to stay connected. Even though it says it's active, my phone is connected to my GPS, both my phone and GPS say Smartphine Link is active, it still won't stay connected. What is the point if i have to repeat all of these steps each time I want the traffic data for my GPS?? I give up and am done with Garmin.
@aspirin624 no I am not setting location to go to work, just for info as you say
If the mapfile is occupying the defective area in internal memory, then this might explain the repeatability of this problem
If I was to load a copy of the map onto an sdcard and use this in preference to the map in internal memory, this might help confirm?
Sure, try ...