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.
In addition to my earlier post to this thread (see below), I experienced a full power-off shutdown with a really weird navigation track while stopped for 5 minutes on a street to make a phone call (screenshot attached). I never had any of these problems prior to v5.0. I've downgraded to v3.9 and things seem to be functioning normally again... I hope.
Auto LiveTrack was a bust for me on today's ride. I never received an email (to self) nor was there a notification of it starting (no icon and lack of labeling in pull down menu). But about two hours and halfway into my 70mi ride I stopped for a coffee. Two minutes after the 1030 went into auto-pause, I received an email while standing in line for my coffee! I clicked on the link and it displayed my starting position there at the coffee shop. So far, I'm not impressed. I never had the problems reported here prior to 4.0/5.0.
Nav worked ok, but the Sharp Turn warnings are excessive -- normal 90° turns, on private, residential streets, resulted in warnings.
Yes, in my Edge (fw 5.00) there is also a problem with Di2 like you and there is still a problem. Every now and then, Di2 is turned off and on again throughout the entire activity. I can not set 10 data screens. It's 9 and when I set tenth it does not show up. Every now and then he breaks the connection with the phone (S9 + android 8.0.0).
I haven't had any problem before or after (on today's 150km ride it worked flawlessly). Just on little thing with the "low Power" warning nothing else. Do you have your Di2 system up to date regarding firmware's? Especially the bluetooth unit? Are you using the EW-WU111 or the old EW-WU101? Think the latest firmware for the EW-WU111 is 4.3.6 and the same for the EW-WU101. Shimano did som tweaks in the latest firmware regarding D-fly.
During today's ride, Edge every time I lost the downturn with Di2 and lost connection with Varia Vision two or three times (fw. 3.50). Today I did not notice that Edge lost connection with Galaxy S9 +.
I haven't had any problem before or after (on today's 150km ride it worked flawlessly). Just on little thing with the "low Power" warning nothing else. Do you have your Di2 system up to date regarding firmware's? Especially the bluetooth unit? Are you using the EW-WU111 or the old EW-WU101? Think the latest firmware for the EW-WU111 is 4.3.6 and the same for the EW-WU101. Shimano did som tweaks in the latest firmware regarding D-fly.
What Di2 system are you using?
I use Ultegra Di2 6870, I have the latest firmware installed in all components. I use the BT / ANT + module - EW-WU111.
During today's ride, Edge every time I lost the downturn with Di2 and lost connection with Varia Vision two or three times (fw. 3.50). Today I did not notice that Edge lost connection with Galaxy S9 +.
I use Ultegra Di2 6870, I have the latest firmware installed in all components. I use the BT / ANT + module - EW-WU111.
Ok. I use the R8070 with the EW-WU111 but there shouldn't be any difference. My connection between the edge and the Di2 is stable.
Second ride today with FW 5.0. 112KM ride, no problems at all. 4 hour ride, still 70% battery left. (so that would calculate to approx 13 hours on 1 battery?) Everything works fine, including live track and auto upload. Very happy with the Garmin device and software. For others with problems, maybe a factory reset will work? Be sure to back up your statistics etc, there is a post on how to do that.
Long 8hr + ride with no sensor drops. Only strange thing was GPS position seemed to be about 25m out through out the ride - very evident on elevation page.
Separate question is it possible to show power target (I use Best Bike Split) in a field? It does show up as a message at the bottom of the 1030 but text is too small.
If the gps is out that far and would be generic to all units on this firmware then is that why today my Strava live segments data was up and down like a yoyo? Im ahead,im behind,im confused! Did a sprint for a KOM and took it on time but got no usual sound or symbol to say i had. Only when i uploaded my ride did it say i took it by 5 seconds. Really hard to measure your effort when its not very stable with segment time data.
Two rides with 5.0 so far (55 km and 100 km). Auto uploading appears fixed, my riding partner suffered a software crash post ride when the unit was sleeping (it rebooted itself).
First ride problems:
-Device did not automatically pair with my Samsung S6 edge+.
On the second ride:
-I lost 10 minutes of cadence data because the sensor dropped and had to be manually reconnected. -Device did not automatically pair with my Samsung S6 edge+
Not fully pleased as a sensor dropped out and bluetooth LE pairing appears to remain broken. Garmin still has lots of work to do on this unit.
If the gps is out that far and would be generic to all units on this firmware then is that why today my Strava live segments data was up and down like a yoyo? Im ahead,im behind,im confused!. Really hard to measure your effort when its not very stable with segment time data.
I am seeing this too, but it is not specific to 5.0.....it also happened for me in the last few released 4.x versions
Two rides with 5.0 so far (55 km and 100 km). Auto uploading appears fixed, my riding partner suffered a software crash post ride when the unit was sleeping (it rebooted itself).
First ride problems:
-Device did not automatically pair with my Samsung S6 edge+.
On the second ride:
-I lost 10 minutes of cadence data because the sensor dropped and had to be manually reconnected. -Device did not automatically pair with my Samsung S6 edge+
Not fully pleased as a sensor dropped out and bluetooth LE pairing appears to remain broken. Garmin still has lots of work to do on this unit.
I can confirm that Edge 1030 doesn't connect automatically with my LG G5 SE since firmware 5.0. Everything else seems working ok, even Edge Remote. But it's annoying to always reboot my phone to make it connect with 1030.
