Having refresh problems with my click widget on LLX homescreen.
Having refresh problems with my click widget on LLX homescreen. The clock widget is stuck at 9:43PM. Same for another world clock widget which is added to a folder. Same for Messaging widget – new messages are not being shown in the messaging widget. I have “Keep Lightning Running” option selected in the General settings menu.
The problem is resolved when I remove and add the widgets again. But after sometime (not sure about the duration), all the widgets stop refreshing automatically…
Please help.
]]>« FolderSetting.Box.Padding is not saved in style. (Previous Post)
(Next Post) What do you guys think about my home screen? »
D5 Creation
< ![CDATA[
be sure the widgets are set to auto-refresh. if they are not then yes you will need to manually refresh each widget. if thats not where the problem is it might be a new bug i never seen before. im still yet to see that happen.
]]>
< ![CDATA[
Well… the clock and messaging widgets are “stock” widgets in Samsung Note 2… no additional options at all… is there any general way of setting “auto-refresh” for widgets?
]]>
< ![CDATA[
if its stock widgets then the system should have had that taken care of. what the hell? you make me wanna add a stock clock widget now to see if i get the bug. give me 10 minutes to check into this
]]>
< ![CDATA[
so far im not seeing the bug. was there a recent os update?
]]>
< ![CDATA[
ok… I have now re-added the widgets… lets see if I can find any specific ways to reproduce this… no recent OS updates…
]]>
< ![CDATA[
i wish my os would update but whatever lol but yeah thats weird your system should be refreshing the widgets
]]>
< ![CDATA[
The widget manager is stuck, meaning that it disables all updates toward the launcher. This can happen in case of overflow (too many widgets, or one of them is too complex)
]]>
< ![CDATA[
Pierre Hébert its new to me im yet to see that problem even with 13 widgets…. or would i need more?
]]>
< ![CDATA[
it may be triggered with only one widget. In fact the issue is described here: https://code.google.com/p/android/issues/detail?id=28216 (comment #100 is interesting)
]]>
< ![CDATA[
Try disabling Keep in Memory.
]]>