TomTom Eclipse / DUO AVN2210p Rebooting Issues Tue Nov 06, 2007 9:13 pm
This is (hopefully) a continuation of the conversation that started on the TomTom Eclipse page about the rebooting issues.
I think I might have just figured out one piece of the puzzle. I thought it was strange what you guys were saying about the undocked DUO constantly rebooting.... something I myself had not seen. So I started thinking about what might be different. And then I figured it out.
I deleted the application, ran the clear flash tool a few times, then reinstalled the application from TomTom HOME version 2.1. Bang... constant reboots when un-docked.
So I went all the way back to version 1.6 of TomTom HOME (on my Mac) and reinstalled the application. No more un-docked rebooting.
So at least part of the puzzle stems from what version of HOME (or perhaps which OS) you are installing from... At least that seems to determine which rebooting issue you end up with.
Finally. I don't think they should use letters/numbers that look similar to each other.
I never tried much of this with 2.1 as I didn't like the layout of the software. With 1.6 I'm currently good with 6.550 and 6.553 (pending car test). With not so functional bluetooth on any official releases.
So you were getting the constant reboot issue under 6.552 when it had been installed under HOME version 1.6? If so then perhaps that means the constant rebooting issue is somehow related to the Windows version of HOME, and not necessarily the version number.
Okay, what I'll try to test is to see if there is a difference installing it on 1.6 under my Mac and installing it under 1.6 on my PC. So far the only way I've gotten the continuous reboot is when using a PC.
Well, everything worked great on the way home including bluetooth calling. I get home, turn the car off and remove the unit. Go inside and a minute later hear the voice telling me I have arrived. Turn it off, it comes back on. It seems somehow docking screws it up. Back to 6.550 I guess.
Yes, I've had an interesting experience this evening as well. After finally finding the "continuous reboot" issue as opposed to the "spontaneous reboot" issue, it seems I can't quite get back to where I was before.
I'm thinking of going through the SD card file by file to see what might be there that perhaps is not supposed to be there, backing it up, and wiping it out. I'm also going to delete the extra Guam map, extra voices, and extra POIs to free up as much space as possible in case the "running out of memory" theory has any impact until I get another stack of SD cards.
I'm really puzzled by the sudden appearance of the 6.553 update.
Yes, I did check the Eclipse devices they had on display... I wanted to validate what Eclipse had been telling us that the 6.552 update was for Europe only... I wanted to make sure I didn't see 6.552 on those units. Of course perhaps they just didn't take the time to upgrade the display devices, but I'm glad to have not seen 6.552 there.
Same thing again this morning. Flawless in the car, but as soon as I remove the unit it will power back on in 30 or so seconds and repeat any time it is turned off until a reset.
A little off topic, but is there a way to have it display the road you are currently on when you are navigating to a route? It only seems to show what the next turn will be in the upper right and lower section, but when you aren't navigating somewhere it will tell your current street.
Unfortunately it doesn't, I've had that on from the start. Having that on just shows the next turn on the bottom as well as on the top. It seems like a goof to me, but I have never used another unit so I'm not sure if it is normal.
Hmm, no edit button for posts it seems. Anyway, after having been docked the unit is now back to not powering off without rebooting. Even after a reset and waiting - the next power on won't fully power down. Going back to 6.550 right now.
Well, I'm not sure exactly which part was the final fix, but as of right now I have my DUO running 6.553 without any reboot issues.... docked or un-docked. Here is what I did... I wish I could be more specific on a few of the items. And I'm sure the fix might have been only one tiny part of what I did... but I wouldn't know which part.
Connected to HOME 1.6 on my Mac. I deleted the application from the device, removed all Itineraries, removed all extra voices, removed all extra color schemes, etc. Basically I removed everything except one voice, a few custom POI files, and the maps.
I then ran the clear flash tool a few times. (For some reason I recall a TomTom support tech telling me it can help to run it a few times.)
After that-- and here is the scary part-- I went through the drive and started deleting text (not binary) files that looked like they would just store configuration settings. This is where I should have taken more notes, but I really didn't think it would work and I'm sure I deleted a whole bunch more than I needed to. But any file on the device that was text based (not binary) that looked like it just stored config settings I copied over to my computer. I also completely removed the 'home images' and 'TomTom-Cfg' folders from the DUO. (And crossed my fingers I didn't remove anything critical that might be difficult to put back.)
After that I put 6.553 back on the device, and booted it up. When I first booted it up I hit the revert to factory settings option, then shut the DUO down.
Un-docked, everything was working properly. Normal shutdown, it stayed off, and didn't reboot on its own.
Back to the car, made sure the DUO was off, and I docked it. It started up fine, and when I turned off the ignition it shut off just fine. I waited 90 seconds and it didn't reboot itself. (Previous reboot issues happened at about 27 seconds after shutdown.)
So right now... as far as power issues go... everything is working perfectly. Interestingly, I still here a soft "popping" noise at 27 seconds after shutdown when it is docked... precisely the time when before it would start itself back up.
Of course I don't know which file (if any) might have been causing the issue, or if I could have had the same results with other versions of the firmware. But for now things are working as they should. (For the power issues anyway.)
Continuing to try to nail down the cause... Do any of you NOT frequently use the USB music feature? Here's what I'm thinking.
My DUO worked fantastic most of the day. I did discover what I think might be a new bug in 6.552 and 5.553... If the CD player is being used and I turn off the car, the DUO always freezes. But that might be beside the point.
Even after that freeze, my DUO continued to power on and off properly-- docked and un-docked. I used the USB music player once or twice too and it continued to work okay.
Until.... once when I connected the USB drive it didn't scan for music. I kept taking the USB drive in and out of the connector, and it never started to scan the drive. And wouldn't you know it.... that very same use the next time I turned off the car the DUO turned off and then rebooted itself 27 seconds later.
In my case the 6.552 reboot problem was happening too. So I went on to purchase a brand new 2G Sd Card and a reader/writer yesterday just to give the 2G method a try. Copied everything from the original card to the new one. And I have been happy since. The rebooting problem is gone. Docked or undocked.
Thanks for the idea guys.
I am still using v6.552 since v6.553 is not coming up as an available update in T.T. Home, for some reason. The only minor annoyance is that when undocked, the bluetooth connection will not get established automatically but manually and even after that it gets disconnected right away.
Joined: 06 Nov 2007 Posts: 85 Location: Wolverhampton, UK
Wed Nov 07, 2007 10:04 pm
So I went on to purchase a brand new 2G Sd Card and a reader/writer yesterday just to give the 2G method a try. Copied everything from the original card to the new one. And I have been happy since. The rebooting problem is gone. Docked or undocked.
Thanks for the idea guys.
The fact that copying the files to a new SD card, or in my case deleting a few files or just freeing up some space... seems like it should be a clue to something. I'm going to try the process I did earlier, but leave less free space to see what difference that might make.
I think though there are still a couple of possibilities. (1) Some invisible files that don't get copied to a new card, or in my case that I erased from the card, or perhaps that don't get installed by TomTom HOME... and one of those files is causing the issue. Or (2) It needs more free space.
raistlin295 - How exactly did you copy the files from one card to another? I'm thinking since my problem eventually came back that free space might not be the issue. Perhaps some of the invisible files didn't get copied in your process and perhaps those were some of the same files I deleted that fixed my issue.
Is anyone here able to set a 4-digit password with TomTom Home? I am running TomTom Home 1.5 Build 106 on my mac and when I select My TomTom Eclipse there is a message on the top saying:
At this time there is no component available that is compatible with your TomTom device.
I have no idea how to set a password on the device and would really like to be able to do so. The instructions on the TomTom device itself don't seem to work.
BTW... Tim, thanks for your awesome review. You completely sold me on the Eclipse AVN2210p and I am really happy with it so far. It paired with my iPhone and transfered all my contacts without a hitch.
jrebeiro - I know what that error message means... For each device there is specific software that TomTom HOME needs to download to be able to operate/control the device from your computer. Some of those are not yet available for Macs, however I was able to get the component on my Mac. The only thing I can think of to try is to reinstall TomTom HOME.
raistlin295 - Thanks. Do you know if you had hidden files available for viewing in Windows Explorer when you copied them back and forth? If not, then there is a chance it was a hidden file that was causing the issue.
Well, your setback (and all of ours) might help in figuring out what the problem is. If anything your setback seems to indicate that it might not be an issue pertaining to the amount of free space. And since you are not checking for hidden files then it could be a hidden file that for some reason is being created that is causing the issue... Which could also explain why things worked well for me yesterday.
I think my car, my DUO, and my laptop might have a date for a little while this afternoon for more research.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum