|
|
Post by RobertoCavalli on Feb 13, 2022 7:12:01 GMT
Normally new caches are released at full hours, so it might be useful to trigger 1min after the check.
So defining a set of user defined triggers might be better for battery performance and quicker alerts are possible.
|
|
|
|
Post by Admin on Feb 13, 2022 9:27:47 GMT
The release schedule is probably depending on the specific reviewer. However, it would indeed helpful to have a different type of notification profile. Currently you can pick timeslots with an interval. As I understand correctly you want to deviate from that pattern, and use one in which you can specify a fixed time (and optionally an interval) at which the application checks for new caches. Would that help?
Update: Currently, repeating alarms are used. Adding a specific moment to start the cycle will be added, but as of Android 12 this will be tricky. Android 12 further improves battery life by executing repeating alarms with a certain variance of at least 10 minutes and up to one hour. More exact will be precise but also battery draining...
|
|
|
|
Post by wolv007 on Feb 28, 2022 1:21:49 GMT
I also like this idea.
In our region caches are published in general at 8AM if no special publish day and/or time has been wished by the owner.
You are right sometimes caches are published during different times, but in this case the trigger interval should recognize them later on.
But nervertheless most caches are published at full hours or half past to the full hour.
So setting dedicated trigger times 1min after full and half hour might be great.
In addition the user could decide to just trigger the check especially during this times, this will result in 48 checks per day and saving battery power.
|
|
|
|
Post by Admin on Mar 19, 2022 14:30:29 GMT
The new version is published (will take some time). I'll investigate precise notification for the next release. Let me know what you think.
|
|
|
|
Post by wolv007 on Mar 24, 2022 6:24:16 GMT
For now the new version seems to run really stable!
But when checking the log, sometimes there are gaps between the entries:
... attachment removed by admin ... I defined a 5min interval for all notifications from 00:00 till 23:59. Could you maybe add the seconds into the log, so we could see if the new starting time is working as well?
Thanks for now,
Cheers Wolv
|
|
|
|
Post by Admin on Mar 24, 2022 20:44:07 GMT
Hi. Thanks for reporting!
The issue of skipping some intervals is due to a heartbeat process to check if the process is still running. This has been slightly changed in version 5.7.x to prevent the hickups. Still testing if this solves the issue completely.
I could add the seconds in the log, but due to the standard Android power optimizations the timing will never be exact. Google's mechanism may delay the action up to 10 minutes. The next version will allow for exact notification on intervals of 30 minutes or more, but even this would not be exactly on the second (about 10-20 seconds accuracy).
|
|
|
|
Post by Admin on Apr 9, 2022 12:29:15 GMT
Just released 5.7.0 with exact triggering (if interval is 30 minutes or up) and a fix for the missing heartbeat. Have fun!
Due to Google policies, the efficiency of having exact triggering on small intervals and the strain on battery usage, the interval treshold of 30 minutes is choosen.
|
|
