Version 5.2.1 for SDK5 devices has been approved and published on the Fitbit App Gallery.
Hello Marin, many thanks for reporting. Are you using BETA version of Sleep as Android? I did ask @jiri-urbandroid to look into the issue⦠Can you please use menu - report a bug and send us some details?
Yes, I use Beta Version of Sleep App.
Actual Version is 20210215.
I will do tomorrow morning a Bug Report if it is the same issue.
It appears the HR tracking on the Versa 2 has stopped again. I can see the heart rate on the watch when I enable it, but the data after the sleep session includes no heart rate data. Reported version is 20210118
How do I get into this beta test? I cannot get my versa lite and sleep to connect
The companion App of my fitbit ionic does not close after closing sleep cycle.
I exit it always manually since a few weeks.
Iāve experience the same thing for the last few weeks on my Fitbit Versa 2 as well. Iām on Android beta version 20210326.
Iām happy to report that every time since March 31, the android app has been closing after stopping the sleep function on my Versa 2. Appears to be working correctly again.
No, on my Ionic the companion app does not close anyway.
Another issue is the massive battery usage. Yesterday the battery of the ionic was about 50% today in the morning it was empty.
If it is fully loaded in the evening it needs to be recharged at the morning because it has about 70% left.
Same here Martin. App doesnāt close after a sleep cycle still, and battery usage is terrible.
Since a few days, I think last update, itās closing the companion app. And battery usage not as bad as before.
Now itās working normal.
Yes, mine as well. There was a Fitbit app update which I downloaded just after I posted. Thus seems to have fixed the outstanding issues!
Since updating on mine and started using again every night Iāve noticed battery usage not real good. Before when I paused using it, I was getting about 5.5 to 6 days out of a Versa 2 charge, now itās barely 4 days. Still not bad, guess I got spoiled.
I have a Fitbit Sense, recently Iāve found that when I start sleep tracking on the phone it stops after a very short period (often just seconds), and I have to restart it. The Fitbit app still shows that itās tracking, and I have to exit the app on the Fitbit and restart to reconnect to the phoneās new tracking session. Is there any troubleshooting I can do or logging I can provide?
Iām on the latest beta (20210527) on a OnePlus 7T Pro.
Is there a special version of the app that is beta? When I use the link in the first post, I only get to a page that tells me that ācan be installed from the app storeā but from the App Store, I only see version 5.3 of the app, updated on April 14thā¦
Just upgraded to a Versa3 and Iām having similar issues to johnu. Testing the wearable without starting sleep tracking does not work at all, it always times out. The same problems mentioned above occur when attempting to start actual sleep tracking: the companion app and the phone app will connect and track for approximately five seconds and then jump to the Save screen. Iāve taken multiple routes trying to start the tracking (starting the companion on the watch first, starting the phone app, starting tracking from the widget on the phone, starting it from within the full app, etc) and I cannot find any specific method that works better than others, it often takes multiple tries and just seems to be a case of luck when it finally works.
Currently using 20210616 Premium on my LG G8 running Android 10 (G820UM20j) and companion app version 5.3 on the Versa3 running firmware 36.128.5.49. Are there any further troubleshooting steps you need that could show the reason for the premature tracking termination?
Seems the helper app on my Versa2 intercepts the SpO2 so it doesnāt displayed on my watch after sleeping. Is that the way it has to work?
To further explain, the SpO2 has only shown a few times on my watch since Fitbit added the functionality to the Versa2. When it showed up a couple of times in the last month, I realized it was after nights when I neglected to start the helper app before going to bed. The way itās functioning now, I get a choice of using SleepAsAndroid on my watch or having the SpO2 data appear on my watch - not both.
I totally cleared the data from the app (and stopped it redownloading settings from the cloud). This seems to have improved things a bit, but it still happens fairly often. It seems to be the app on the watch thatās crashing out. Would be happy to provide any info for troubleshooting.
Fitbit Sense here. Been trying to find a device that actually works with SAA⦠(using SAA continuously since 2017) HR tracking is looking good, but the Sense isnāt vibrating with the alarm. Similarly, the SPO2 data isnāt showing up; and with the app running on the watch, it also seems to be blocking the recording of SPO2 by the Sense itself, making the sensor a bit useless⦠Any chance we will be seeing an update to the SAA Fitbit app soon?
(also only seeing a āthis beta program is fullā when trying to join the SAA beta?)