• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Clock widget is late

R

rawfa

Well-Known Member
Hi,

My wife got a Milestone some weeks ago and we've noticed that the clock widget keeps getting late (the system clock is always perfectly in time) if the phone is inactive for some time or if it's been used a lot. I've installed another clock widget and the same thing keeps happening. I've tried both widgets on my Samsung Vibrant and this doesn't happen. Did this happen to anyone else?

thanks

Rafa
 
There should be an 'ignore' option in the task killer which will prevent apps to be auto killed by the app. Add the clock widget to that list and your problem should be solved.
 
It turned out it wasn't that. We uninstalled the app to test it and the issue still happened.
 
Did you check Android's inner memory management system?
What are the clock widgets you're using? I can try them out on my Milestone to see if they are working or not.
 
Thanks! That is very nice of you. My wife has tried Digital Clock Widget and Clock Widget (which is basically a clone of the former).
 
Which Digital Clock Widget is it? There are many on the market with that name, better give me the developper's name as well.
 
We've just realized that all clock related apps are progressively getting late. The phones' stock clock is always on time, but all other apps are late. Any thoughts on where the issue is? We've tested several clock widgets and also calendar snooze. At first these apps/widgets work perfectly, but little by little the clocks start getting late.
 
My idea is that it's Android's interal task killer that is closing the widget.
Is your phone rooted or not?

Anyway, rooted or not you can check the settings by downloading 'Autokiller Memory Optimizer'. Post your settings (Foreground app, Visible app, ...) here.
If you are rooted you will be able to change them, or change the priority of the clock widget (Process tab > long press on the process of the widget > Lower oom value).
My settings are: Foreground: 12MB, Visible: 25MB, Secondary: 1MB, Hidden: 80MB, Content: 88MB, Empty: 96MB. You can try these since i don't have problem with clock widgets.
 
Well, if you can fix it this way, why not? :)

I still think it is the internal task killer. You never said if you were rooted or not?
 
IMO this is all caused by the setting to have network set the clock up and going into flight mode.
 
Yeah, you could be right. Though i tend to think that it should affect the android clock as well, and not only the widget. And Fancy widget shouldn't be working either.
I don't have the same problem he has and my phone is set to use the network as well for the time, but I hardly ever switch to airplane mode.

My best guess is that Fancy Widget has a lower oom value and doesn't get killed so fast by the system.
 
Alta1r said:
Yeah, you could be right. Though i tend to think that it should affect the android clock as well, and not only the widget. And Fancy widget shouldn't be working either.
I don't have the same problem he has and my phone is set to use the network as well for the time, but I hardly ever switch to airplane mode.

My best guess is that Fancy Widget has a lower oom value and doesn't get killed so fast by the system.
Click to expand...

I really think you would have to have lots of apps running in the background in order for the widget to be killed.

If you want to check, install a task killer but set it up not to kill anything and just check from tie to time if the widget is still running or not.
 
You must log in or register to reply here.
Back
Top Bottom