You don't need to be an 'investor' to invest in Singletrack: 6 days left: 95% of target - Find out more
Against all of my instinct and better judgement based on bad experience with my old Garmin Edge 500, I bought a Garmin Forerunner 235 last weekend.
It seemed to tick all the boxes in terms of functionality, is discounted at the moment because it's end of line and there are at least 3 people I know at work with Garmin watches (2xForerunner235 & 1xForerunner35) who have never mentioned problems with the devices or app.
Looking around, there wasn't really anything else that ticked the boxes.
Anyway - I loaded Garmin Connect onto my phone last weekend and it immediately re-booted. No warning, just installed the app and immediately re-booted. It also seemed to take a long time to come back to life.
Since then it has re-booted 4x that I can recall. Every time completely randomly. I've just picked my phone up and it's sat waiting for me to put my pattern lock in before loading Android.
I haven't uninstalled the app to see if the problem goes away, but this phone virtually never crashes (perhaps twice in 2.5yrs) so I can't believe it's anything other than Garmin Connect.Maybe my previous experience with Garmin software has coloured my view?
Has anyone else seen this issue? I know there has been a few posts over the last year or so about purchases of Garmin smart watches.
I mainly only need Garmin Connect to sync my runs, but it is useful for analysing stuff too. If I can't resolve it, I'll probably take it off my phone and add it to my tablet (assuming it'll work on there?).
I used to have one. Not had that problem. But quite often it seemed to lose connection with the phone,requiring a reboot of the phone to reinstate.
I got rid of it since after a while It seemed to randomly forget the time, only remembering it when gps was activated. If you regularly partake in recording activities with gps then I guess this might not be an issue as it’s always refreshing the time, but I never bothered to test how long it took to forget - it was weeks rather than months. I didn’t think it was great to not be able to trust the time on it so sent it back.
Has anyone else seen this issue?
Nope. Had Garmin connect on my phone for ages (first for a 235 and then a fenix) and cant remember it crashing let alone taking down the entire phone.
That said I only tend to have bluetooth switched on for both the phone and the watch when I need it.
What phone is it?
muddyjames
Member
I used to have one. Not had that problem. But quite often it seemed to lose connection with the phone,requiring a reboot of the phone to reinstate.I got rid of it since after a while It seemed to randomly forget the time, only remembering it when gps was activated.
Hmmm. Not noticed either of those things yet, but only had it for a week & I've had the GPS on every other day for a run, so if there is an issue with it forgetting the time, I doubt I'll come across it.
But, I'll add it to the potential ballache list.
dissonance
Nope. Had Garmin connect on my phone for ages (first for a 235 and then a fenix) and cant remember it crashing let alone taking down the entire phone.
That said I only tend to have bluetooth switched on for both the phone and the watch when I need it.
What phone is it?
Hmmm. I suppose I could turn bluetooth off on the watch and just have it on at the end of the day to sync. Seems a bit of a pain though and I'l lose functionality such as the weather widget etc. which is nothing major, but one of the reasons I went for this watch, compared to the Forerunner45.
The phone is a Lenovo P2 and has been rock solid up until putting Garmin Connect on it.
My son’s phone did this with a FR 235 but getting connect and bluetooth to forget and reconnect seems to have solved it.
For the experience of the two watches we’ve got, allowing Connect to handle the bluetooth connection seems to be a none starter (It either fails to connect/ re-connect to Bluetooth or causes the phones to crash). I now connect the watch to the phone bluetooth manually then connected Connect which seems to have cured the problem (I have no idea why).
@Richie_B - that's interesting, thanks! I'll have a fiddle about with the Bluetooth later on today.