-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TestFlight builds 2024.13 - 2024.21 battery reports #54
Comments
I'm running 3 devices, my study has extremely rapid timer intervals and all data streams enabled, it should record data ~50% of the time and reliably test edge cases like creating and uploading hundreds of files. Using heartbeat as my proxy for persistence, will look at data stream persistence later. as of version 2024.18 I am seeing two instances of evidence for basically-perfect background persistence. Heartbeats come in almost perfectly regularly, and data files are uploaded perfectly. I am not actively monitoring upload lag or actual data quantities due to just time in the day.(my old phone)
Red Phone
Primary phone
|
Hassan
I installed v2.5 (2024.15) last Thu, 2/29/24 evening with a nearly full battery. I did anecdotally notice significantly increased battery drain - see screenshot which shows ~75% over 7 hours and 100% over 12 hours. Note I was using my phone quite a bit during this period (heavier than during the workday). Interestingly, since I installed v2.5 (2024.18) I haven't noticed anymore significant battery drain as compared to prior to v2.5. I will pull a screenshot similar to the above this evening. |
|
Thank you everyone for your time and attention on this, 2.5.0 was a really important release. I am closing this issue now. |
This issue is open to anyone running Testflight builds 2024.13 - 2024.20 to report your experience of the app.
(ignore versions 2024.9-2024.12, I made a bunch of dumb mistakes.) This issue will be updated or retired to reflect updated build numbers if/when they appear.
Please edit previous messages with updates instead of posting a new comment, do not remove old entries.
You do not need to include Beiwe ids or the exact Beiwe server in use.
(I am working on automating recording some of this information)
2024.18 is looking really good, but:
I think this cannot go to the app store until "reachabliity" - detecting if the device has network access - does not appear to work. #45 is resolved because it would destroy limited data cellular accounts because persistence is too good.ok that is finished as of build 2024.19The text was updated successfully, but these errors were encountered: