it is one of the 2 or 3 things that make me keep MCapp as main app on Android, and SA as an app to be tested and launched occasionnaly (after each move to be up to date) but forced closed each time.
Was this ever investigated, or is it considered “fixed”?
I (briefly) installed SA, last week (v.4.2.4), and had a similar issue, it was pretty tough on the battery on two devices, an old Nexus 6P (Android 8.1), and a OnePlus 7 Pro (9.0, or Oxygen 9.5.8).
My device(s) are both Ambit3(Peak) models.
I was seeing a “bonus 12-15%/day”, which immediately reverted, when removed (the app).
Given that it was taking 5+ minutes, per-activity, to sync my Ambit3 anyway (still, it’s always been like this), making it largely impractical to sync after an activity, particularly if I had several rides to sync, I uninstalled it for a variety of reasons.
MovesCount isn’t really faster, but it also doesn’t
The battery issue makes the app unusable, IMO, given the impact it has on the phone/device, in-general.
@Dimitrios-Kanellopoulos Or are you saying that “10%/day” is considered “normal”, for SA?
Thanks for any info/update here.
I do see the same issue on my suunto spartan too. Max speed during cycling usually exceeds 171 km (i have one trainig with 300km even 😆). Altitude drops by 150 meters within few second (path i train has maybe 30 meters of elevation in total). What is strange hiking or walking data doesn’t show these peaks so far.
I don’t have the pod just the watch itself. Is there any solution planned? It’s a bit frustrating.