[Samsung Infuse 4G] PlacidCat:
Hope you all don't mind my poking my head in here. I'm a Vibrant user with a similar issue and qkster posted on a thread I started in the Vibrant Q&A section that basically mirrors this. Having been directed here and reading through the thread, I'm hoping some additional observations from my camp might help others discern a pattern in their own activity - ultimately I hope this helps uncover the root cause. First some info on my current setup:

- Samsung Vibrant (T-Mobile, 3G)

- SKANG JellyBro build 231 (Jelly Bean)

- Devil Kernel 1.0.4 test 3

- No data plan (data usage attempts forced off using APNDroid)

- WiFi set to stay on when display is off

- Exchange account updates every hour

- Widgets running: stock calendar, Google Voice inbox, Beautiful Widgets battery monitor

- Default settings for Devil Kernel

- more info on request...

I was running Froyo for well over a year without any real drain issues. My phone could easily go 16 hours and still have 40%+ left. Last week I switched to the above ROM and kernel - my use of APNDroid, Wifi policy, widgets, etc. are the same now as they were on Froyo. I started to notice the battery drain mentioned here after a day or so. After looking at the battery monitor, I saw Android Services was chewing up battery by keeping my device awake. Rebooting solved the issue.

I will have to keep an eye out to see if it is related to my bouncing between WiFi hotspots - I originally thought it was related to my charging overnight and removing the charger in the morning. Now I can see it might be due to my leaving WiFi service as I drove from my house to work.

Here's the big difference I've noticed between Froyo and Jelly Bean, however, and I wonder if anyone else noticed this and if it perhaps factors into the issue. When running Froyo, I never had Android System go nuts on me like this. That said, when hopping between WiFi hotspots, my phone would occasionally "forget" to connect to a recognized hotspot, even when I was within range. Cycling WiFi immediately solved the issue and WiFi service was restored. This was something that happened at least once daily. When running Jelly Bean, I've not once had this issue - WiFi hotspots have always been "found" and connected automatically. I've not had to recycle the WiFi once since I installed JellyBro 5 days ago.

So... could the change in behavior of moving from hotspot to hotspot with gaps in between have been an attempted fix that, in the end, caused a new issue? Anyone else remember if they had any WiFi issues on Froyo that required cycling WiFi power after a gap in service?

---------- Post added at 12:22 PM ---------- Previous post was at 12:17 PM ----------

And, yes, this is most certainly true if you have an AMOLED display. AMOLED displays require power on a pixel-by-pixel basis. LCD backlit screens require consistent power, regardless of the brightness of an individual pixel. Consequently, changing a color theme on an AMOLED display to a darker scheme will improve battery life. On an LCD backlit screen, no dice - the backlight is always at the same intensity regardless of theme and only lowering the brightness of the backlight will lower consumption.