I first posted this in Q&A on the home forum. There doesn't seem to be any interest so I thought I'd post it here again. Below is what I wrote on the original post.
"If you’ve been supremely annoyed with the AOS bug like I have , here’s some interesting information I’ve found (Did a search and it appears no one else has found this yet). It’s a paper written (in 2010)by Rafael J. Wysocki which touches deep into the subject. What I hope is that it will help some developers understand this bug and ultimately integrate a work around / fix as soon as possible. Hopefully this will help some users understand what is going on with their phones as well.
I have and Epic 4g Touch and all the ROMS I’ve tried have this bug but according to the article, looks like a kernel problem. My suspend / events/0 processes runs for a long time, eating up cpu and I don’t have it as bad as some people but thought it's worth mentioning.
Basically what I get from the paper is that…
1. The suspend (and by association the events/0 process) process is Google’s implementation of a power management system, an add on to the Linux Kernel
2. That the wakelock / suspend feature is , to make a long story short , not working the way it’s supposed to.
3. “Poorly” written apps, or apps that are written without the inner workings of how suspend /wakelocks work, will trigger this bug. This can be ANYTHING.
4. Supposedly, kernel version 2.6.37 will fix this. The Epic 4g Touch kernels are all .35 as far as I know which explains the fact that so many Epic 4g Touch owners complain about this.
Would love for the smarter than me people to give their take on this?
Since this is my first post, it won't let me post a link. Do a google search for Rafael Wysocki suspend_blockers.pdf and it should be the first link that shows up."
Hopefully there's more interest here!