This site uses cookies to offer you a better browsing experience. Find out more about how to manage cookies, or dismiss this message and continue to use cookies.
Spontaneous reboots with Drivesmart 55
I bought a new Drivesmart 55 and started getting reboots while navigating. Because of Amazon's return policy I sent it back and was sent a replacement. This one started doing the same thing. I called Garmin's customer support and they worked with me on trying to figure this out. They couldn't have been more helpful. They finally decided to replace my second unit with a third. So that was done and now it has happened again. But it seems to only happen when I'm navigating and using the Garmin app "Drive" on my iphone 8. I don't think I've ever had a reboot with Bluetooth turned off. Anyone else experience this kind of thing? Thanks.
Comments
The thing about it not happening when you don't use the Garmin Drive Bluetooth app doesn't necessarily eliminate the issues with the vehicle power supply either. When using bluetooth, the device is using more power. So it is then more susceptible to the possibility of going below a threshold power that causes the reboot.
However the result of rebooting also does not quite sound right for the above either. I don't think my drivesmart really reboots. It just goes to sleep, seemingly because it comes right up when power is re-established and after answering the liability disclaimer, continues the current planned route. I never see the splash screen with the loading software as I do with other garmin devices when I power it on. With the exception of updates and connecting to my computer.
Maybe your devices battery is going dead because it's not getting enough power to charge. Possibly that forces a re-boot when power is re-established.
Anyway..... let us know if any of the above was worthless, helpful or suggested other possibilities to you.
At this point, I don't have enough time with any of the three units to say for certain what happens when. My belief is that it is an issue with the Drive app and/or Bluetooth and if it is I won't be sending this unit back. I don't really need to use the app; it was a matter of convenience. And while I believe things should work the way they were designed to work, this unit is so good I will not complain if it is the app. But I intend to keep experimenting to see what shakes out and will report my findings here (if I remember to, I'm 71).
Thanks for the response, privet01 .
At this point it certainly appears that the Drive app and/or Bluetooth is related to the rebooting. As you point out, MustangGT, you always use the SmartLink app (Bluetooth) and you experience rebooting. Thank you for responding.
I had a problem with Alerts not going away (e.g. Curve Ahead) when I first got the Drivesmart 61, and as with you, the first level support people are quick to recommend replacing the device. It took a lot of effort of trying to convince them it wasn’t a hardware problem and to pass the problem to the next level support. Eventually it got fixed two software versions later.
My Drivesmart 61, still occasionally gets into a reboot cycle of 4-5 reboots. There’s been no recent update for the 61.
I contacted Garmin, they sent me a refurbished Drivesmart 61, it too has problems, but slightly different than my original one. It has spontaneously shut down on me when I was driving, it shut down on me adjusting the brightness, but lately it can be fine for about an hour, and the suddenly drop to 40% brightness. If I try to increase the brightness, it says something like, use a proper cable..... After unplugging and replugging it back in a few times, it’s fine for a while. I’m using the original Garmin12 volt adapter. I’ve tried various chargers and cables, sometimes they work for a while, and then it misbehaves.
I tried a Drivesmart 65 a few months ago, it too rebooted on me, also using its original cable. I returned the unit for a refund.
I’m reluctant to buy the 65 again, unless I know for sure that the problem has been resolved. Garmin seems unaware of people having this problem.
Your particular problem(s) sounds to me like a hardware issue.
Good luck with this and let us know the outcome.