Old Fart At Play
Member
Hello there...
Since around the end of January, any ride I have recorded in ebike connect shows an unchanging altitude, or sometimes changing by just 1 or 2 metres ( for eg 200m ascent). In case anyone else is puzzled by similar behaviour, it seems that it is because of an error in Google Services, specifically the FusedLocationProvider API. The same problem (unchanging altitude) shows up in other apps, eg Osmand and Maps.Me. However some apps work, eg Accurate Altitude, because they use a different google API (specifically the older LocationManager API) to get their altitude.
Apparently Google are hoping to release a fix around 7th March.
Cheers, John
Since around the end of January, any ride I have recorded in ebike connect shows an unchanging altitude, or sometimes changing by just 1 or 2 metres ( for eg 200m ascent). In case anyone else is puzzled by similar behaviour, it seems that it is because of an error in Google Services, specifically the FusedLocationProvider API. The same problem (unchanging altitude) shows up in other apps, eg Osmand and Maps.Me. However some apps work, eg Accurate Altitude, because they use a different google API (specifically the older LocationManager API) to get their altitude.
Apparently Google are hoping to release a fix around 7th March.
Cheers, John