-
Notifications
You must be signed in to change notification settings - Fork 127
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
Widget is not refreshing correctly #338
Comments
The widget is configured to be updated automatically, even when nothing happens, once in several hours. Plus it updates, when several kinds of notifications arrive. The second way is unreliable due to Android design flaw, caused, as I understand, by desire to spend less device energy, see #298 Decreasing automatic refresh period is generally discouraged. But maybe this is the only way to have automatic refreshes more often... |
@Clubby2010 Regarding comparison with ToDo Agenda v.2. it would be very interesting to have such on the same device and at (almost) the same time. |
How can I test this (installing v.2 version in parallel)? |
@Clubby2010 I meant sequential testing,of course. |
How can I install version v2? |
Please download v.2.1.1 from here: #320 |
Tested with 2.1.1 but the error exists there also,maybe I didn't recognized it in the past because of previous Android Version. |
@Clubby2010 Thank you for testing. Regarding Android versions, first time I noticed that some scheduled processed aren't working for several hours, was with my Lenovo tablet with Android 7. There are "brute force" means to ensure constant app running like creation of a "service" always running in a background. But I thought that this would be an overkill for the widget. And will cause noticeable power loss and the ToDo Agenda's icon always present in notification bar. Or should I create such optional background service for ToDo agenda? |
@Clubby2010 If you find any open calendar widget that updates property on your device, please let me know. |
@yvolk In another project I'm working on, I've found the Job Scheduler API to work reliably on recent devices:
Edit: Never mind, turns out I was using an old version from f-droid. |
@SimenCodes "Never mind..." So what's your current suggestion for improvement? |
I'm not sure about the Background task. I'm currently testing the widgets: Your Calendar Widget, DigiCal and aCalendar+. |
@yvolk "Never mind" as in "version 3.0.11-532 from fdroid works for me". My suggestion for improvement if broadcasts are not being received for some people, is still to use the job scheduler. |
@Clubby2010 Today I compared refreshing of "Todo Agenda" vs "Your Calendar Widget" and "Schedule" widget of Google Calendar. So "Your Calendar Widget" doesn't use any better technique. Below screenshot shows that only Google's widget shows "Go2" event, and "Sleep" event in green color. I even lost patience and left my device while waiting for it to appear... |
On my smartphone I can't confirm your results. |
@Clubby2010 I understand that "notifications" on calendar events' changes don't work at all on your device. This is why only manual Refresh button tap works. So it looks like the only substantial difference between the two widgets is in a frequency of automatic and unconditional refreshes, configured for the two widgets. I think I will create another widget in the same app called e.g. "ToDo Agenda 1 minute refresh" (if the name isn't too long...) and allow users, who have problems with auto refreshing, add that widget to the screen. ?! Edited: I better use a configurable alarm for this: https://stackoverflow.com/questions/28072947/changing-androidupdateperiodmillis-programmatically |
No, for me the Your Calendar "seems" to be updated by notifications. Of course, I don't know, but it's really instant. I change an event, go back on startscreen, and it's updated. I never see any delay for this widget. You wrote, it's at least auto-refreshed at least each minute. I can't confirm this for my device. Currently I will compare battery consumptions between both widgets. |
As the ToDo Agenda is not updating on your device it should not consume ANY power. Another thought is that as you are using the "ACalendar+" Calendar app, it may send notifications directly to some "known" widgets. It that case that explicitly notified widgets will really update instantly. Just like recently we agreed with "Open tasks" developer to send us notifications explicitly for quick updates: dmfs/opentasks#822 |
@Clubby2010 Regarding one minute refresh in "You Calendar": please look at my screenshot above: |
I asked the developer of Your Calendar widget how it's refreshed,but get no feedback :( |
I just recognize that I closed this issue some days ago. This was accidently. But for me it can be stay closed even If the issue is still there. |
…t value of 10 minutes. The refresh (and corresponding alarm) is not fired, when a device sleeps. So it doesn't spend much energy.
@Clubby2010 @SimenCodes Listening to you :-) I improved automatic widget refresh via introduction of a configurable Auto refresh period (in Other Settings). Default refresh period: 10 minutes. The refresh (and corresponding alarm) is not fired, when a device sleeps. So it doesn't spend much energy. I see that it works. Please check v.3.1.7. Beta #320 |
Thanks for adding this new setting. |
Another potential cause of not refreshing/updating found: You can see outdated data, because ToDo Agenda gets it from "Calendar Provider" Android system service. This is that service that malfunctions (maybe doesn't sync in time...) As one of users confirmed:
|
I noticed several times that the widget is not refreshing correct automatically.
Example:
![Screenshot_20191020-224702](https://user-images.githubusercontent.com/55927536/67167078-ea69f500-f395-11e9-8828-605eb56bf6ac.jpg)
As you can see in the screenshot above, the current time is 22:47, but 2 issues:
After pressing the refresh icon (circle arrow) manually, the calendar is refreshed correctly:
![Screenshot_20191020-224721](https://user-images.githubusercontent.com/55927536/67167080-f05fd600-f395-11e9-8909-243eefee620b.jpg)
I didn't notice this issue with an older major version of the app.
The text was updated successfully, but these errors were encountered: