sreich
commented
1 month ago So, isn't this just a matter of us handling shutdowns gracefully?
I mean obviously fixing crashes would be great but reality is Android apps have to be designed for their activities to die at any point in time, with little warning
Our settings and data should be prepared and persisted for such situations, I recall Android having mechanisms to help facilitate this imo
As you might be aware many chinese firmwares quit the apps in background no matter you removed battery restrictions. I'm on MIUI and same thing happens. By luck sometimes I can complete a session of 2 hours and sometimes the app is force stopped after 80-100 minutes.
The problem here is that you actually don't know how much time you spent on the session if you set a session for like 150 minutes, and you actually don't know the average of the session completed.
So please add a log option(maybe hidden somewhere or in the settings) which would log requests and the session duration along with time (maybe every 2-3 minutes) so that if the app gets terminated, users can calculate the time on their own and add it manually.
For example I started a session at 2:00pm and took few breaks in between, so I actually don't know the time spent without the break(the time I paused the session). So if the app crashes maybe around 3:08pm and it would have generated a log somewhere about 3:04 or 3:05 or 3:06. And then I'll calculate the remaining time myself and add the session manually.
It will also help us to see how much time we're spending on breaks rather than focusing on our work. Will be pleased to hear from you soon.
Thank you.