Howdy!
After the latest firmware update (8.10) when I start livetrack I get every time the following error: "Can't start livetrack. Error code 18". I'm using an Android phone, Connect app ver. 4.44. Any thoughts?
Howdy!
After the latest firmware update (8.10) when I start livetrack I get every time the following error: "Can't start livetrack. Error code 18". I'm using an Android phone, Connect app ver. 4.44. Any thoughts?
I tried with the latest ver. of Connect 4.45. and it still doesn't work. I downgraded to Connect ver. 4.29 and its still a no go. When I started LiveTrack with mobile data turned off it started to work. But the moment mobile data were back on LiveTrack stopped. I guess the problem lies within Edge 830 firmware.
GCM ~ System Build Flavor vanilla Build Type release Build Ver. Name 4.45 Build Ver. Code 6047 Build Debug false Environment PROD Auth Lib. Ver. 5.0.1
Android Device ~ General OS Android Ver. Release 8.1.0 Ver. SDK 27 Ver. Codename REL Manufacturer motorola Brand motorola Model Moto G (5) Plus
I had live-track error 24 for some while. I've found that it was related to my Edge being connected to my indoor bike while standing outside ready for a road ride. So my Edge had GPS, was connected to my road bike and indoor bike, and that crashed the live track. Turning off my indoor bike or move away from the house solved the issue.
Could be something alike for you?
Hello, i just got an Edge 830: upgraded to latest firmware 8.20, connected with my iPhone and done all the setup with Garmin Connect app. I have already setted up the emergency contacts for incident alerts and configured Livetrack but Livetrack fails with error code 18 while trying to send a "emergency request" to contacts just says "Impossible to send SMS".
As this is new I can't compare to having previous firmware on it: people with Livetrack error 18 - can you try to send an incident help request sms to see if that is still working for you or both these funcions stopped with this update?
Has this been sorted yet as im still getting the same issue, any way around it ?