Feed Sponge v1.4.7 or Two year old bugs, dim screens and you - a cautionary tale.
March 11, 2011, 11:38 p.m.
I discovered this Android bug and its workaround when I first created Feed Sponge:
Bug ID 2059
That isn't my bug report dated February 2009, but I had the same issue on my brand new Incredible in 2010. Today on March 3 2011 the bug persists as does my workaround.
The short version of the bug is that without retaining a PowerManager.SCREEN_DIM_WAKE_LOCK (I'm not yelling, that is the flag's name), you cannot download very quickly or reliably. Using a WiFi lock is ineffective. It is also not limited to the Nexus One as it happens on my Incredible and many other phones.
Click the image for a full size version.
Essentially the wifi is capped and
unpredictable unless you have the screen
Ok, so I knew about this bug and why I turn on the screen. Now we come to a bug report that makes me play with the sync feature and the screen wake lock in depth. Only now it isn't dimming the screen, it is running the entire auto download process at normal brightness. After troubleshooting this for quite some time, I discover that it is because I have enabled automatic brightness adjustment. Automatic brightness adjustment is now one more bug in that it doesn't allow the screen to dim in the wake-lock mode required to work around the WiFi bug.
The workaround for the automatic brightness bug is to disable it unfortunately.
There is an integrated download service in Gingerbread (Android 2.3) but almost nobody has Gingerbread right now. It also has a feature that will probably prevent podcast download over carrier networks. So that doesn't really help us.
Hopefully this version resolves whatever bug mzo was experiencing. I have reverted a trivial change in RSS processing that may have been the issue, but I cannot be sure without more info.
tags( #code #feedsponge #android ) Tweet