Since 4.0 came out I had nothing but problems. I had strange resets for no reason, Strava Segments crashed the Garmin, I would lose connection to my power meters and had random warnings for non-existent turns. The beta firmwares, along with gimping functionality by disconnecting it from my phone, fixed it mostly. Today I installed 5.0 and went out on a ride with it connected to my phone and with Strava Segments turned on. Everything was perfect! No crashed, no issues with Strava Segments and not a single freeze or lost signal on my power meter. Seems like 5.0 fixed everything for me so far.
Did a 153km ride today and Everything worked fine. Live track, sensors, connection to phone and Di2 (I have never hade any problem with my Di2 Before). Even autoupload worked.
No shutdowns on my 100 mile ride, which is an improvement. However, still cannot get it to sync a ride when connected to bluetooth to my iphone 7 ver 11.4. Ugh.
I had problems with shutdowns. One shutdown would reliably happen in the same place on every MTB ride. I suspect this is the "long segment name" bug.
The other issue I was having was that auto-uploads weren't working. This bug is also fixed for me.
Great progress Garmin ... thank you. Hopefully the competition from Karoo, Wahoo and Polar has lit a fire to get a product out the door 95% correct instead of 80% correct.
Rode with 5.0 today, only issue still remaining, but it wasn't mentioned in the release notes as solved, is the Garmin Edge Remote issue. If i turned off Phone connection it worked flawlessly, otherwise sporadic disconnects (red blinking light).
Spoke too soon, the Bluetooth remote still disconnects. I only ride when attached to my Galaxy s7 edge.
After miserable experience with 4.0. The 5.0 works much better, but still I dropped HRM signal once. And most strange thing is, Garmin 1030 upload two activities to my Strava which I only ride once. One shows the day I ride, and another one shows one day before.
On today's 120km ride everything worked flawlessly. Livetrack, bluetooth connection to phone, all sensors and Di2. At the end the ride was autouploaded.
The connection with my DI2 is also dropping and reconnecting every 3-4 minutes with the 5.0 firmware. I've got the R8070 version with the EW-WU111. Connecting my phone via bluetooth or disabling the phone connection doesn't solve the problem.
I should have done the obvious thing: I removed all sensors and added them back. All issues solved, no more sensor dropouts...
- BT connection to phone (Lenovo P2) only kinda works: connection must be manually reset and the whole finicky BT pairing protocol has to be re-done before each ride! To me, that's equal to not working - today had to manually connect the Di2 - today had to manually connect the cadence sensor - had one shutdown so far (also today)
So far, 5.0 is only marginally better than 4.0
I've been offered a RMA by Garmin Germany, after waiting weeks for a reply. I asked who pays for shipping and never got a reply back. I am reluctant to send the device in such a support black hole, how long before I get a replacement, if ever?!
