[BUG] Widget does not update itself

[HarriBuh]

Not sure whether this is intended or not, but the widget (a daily calendar in my case) does not seem to update ever, which is a mess.
Please make it update itself.

[peterfajdiga]

Hi, thanks for the report. No, this is not intended.
Does this happen with all widgets (I think the easiest to test would be a clock)? Which Android version are you running?

[HarriBuh]

My guess is that it happens to all apps. Just recognised another bug: The widget doesn't seem to scale properly, as seen in the screenshot:

I noticed this happening to other apps as well (like not being able to scroll through my task list- this starts randomly after some time, sometimes directly after I set up the widget).

I will look further at the update issue and report back.

[HarriBuh]

I tested it with a weather forecast app- no self updating here either. Seems very much lime a permanent issue then.

[peterfajdiga]

Which version of Android are you running?

[HarriBuh]

Sorry, I overread that. 14, on a Pixel 7

[peterfajdiga]

I can't reproduce it on Android 14 with built-in widgets. :(
Which app's widgets did you try?

[HarriBuh]

1. "WarnWetter" (de.dwd.warnapp) from Play Store
2. "Fossify Calendar" (org.fossify.calendar) from F-Droid
   While I think this could be a battery saver issue from Android (I always have the "light" saving mode on), at least the Calendar widget would update itself on other launcher apps.

[peterfajdiga]

I've tried the widgets of Fossify Calendar and I've tried to turn on the battery saving mode, but I still can't reproduce the issue.
Do the widgets get frozen immediately when they're created? Does it happen every time? Or do they only get frozen in specific scenarios?

[HarriBuh]

It will happen every time. I wouldn't call it "freezing", the widgets just won't update to any changes I've made to the original app.
I think I've had this issue with other launcher's widgets in the past, too. Even with other smartphones, on other Android versions

[peterfajdiga]

@HarriBuh Is this issue still occuring for you? Or did it stop? Did you find a workaround?

[HarriBuh]

It's still occuring, but it looked like there won't be any solution to it. That's why I chose to close it.

[peterfajdiga]

Thanks for the update. Unfortunately, you're right, I can't reproduce it, so I can't fix it. But I prefer to keep such issues open in order to keep track of them.