Bug #430
widgets mis behaving
| Status: | New | Start: | 02/03/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | sweeterhome | % Done: | 0% |
|
| Category: | BlockWidget | |||
| Target version: | Preview 2 |
Description
Since the last update my droid has been a bit buggyer. after a restart I find that the widgets do not update until I enter edit mode then exit. This is similar to the first round and was corrected in the 2nd update.... seems to be back now
History
Updated by milrtime83 almost 2 years ago
I have this problem with widgets not updating until I go into edit mode as well. Setcpu is one specifically that does this.
Google Scoreboard is another, but that one doesn't even update when I switch to edit mode.
Updated by trs almost 2 years ago
Reducing my bitmap limit has significantly improved widget performance; see issue 417
http://www.sweeterhome.com/issues/417
widgets/images use the android system's built in graphical handler to process.
the sweeter home processes everything else
colour processing is ambiguous to me (unsure which does it); Im guessing it is sweeter home.
I think sweeter home may handle some processes like retrieving the images but I'm not sure.
The bitmap limit is the standard set by the application to safely run sweeter home smoothly.
Reducing this file will improve widget handling, by attributing more to the android system
But IT CAN FARK UP SWEETER HOME; Do regular backups of your sweeter home package file
Be prepared to do uninstall/reinstalls; that said I haven't had problems yet
I do not believe this is a bug,
I believe this is how widget processing is handled by sweeter home; opening and closing apps also causes widget refresh.
Please read my posts on the thread concerning my hardware/firmware/software and my trials with reduction; I have since those posts reduced all the way to 3,000,000 from a limit of ~4,300,000+
Updated by trs almost 2 years ago
ALSO: CRACKPOT THEORY
I also found that when I reduce my bitmap limit lower than half, the system gets worse rather than better; this could be a perceptual/cognitive bias on my part but I think this might be happening because sweeter home can't support the widget when the widgets processes or set of processes can't function in excess of sweeter homes limitations
Picture a bottleneck effect if you will;
Sweeter Home: Wiget Placeholder = Single Process [Macro Function]
Android System: Widget = 100 Processes (Example) [Micro Function]
Sweeter Home views the widget placeholder commiting 100 processes as one, giant process.