I tested using that method and it seems to be able to go back into deep sleep with TheOCv1.7.20 kernel. I'd like to see someone take Whyzor's latest kernel, revert the 2 sensor commit (like mantera did) so we can have the latest but still a working in-call sensor.
If you flash my final build, then theOC kernel on afterwards, you'll have the latest build w/ working in-call sensor (for your phone), but possibly wakelock issues.
I would suggest trying to be patient and methodical about applying & reverting changes. Here's what I've noticed so far:
- Originally I noticed "event" wakelocks, others have confirmed it too. I dug around, found a fix for it. Checked it in, then no reports of wakelocks, battery life better for everyone.
- Recently lots of people have same problem of screen not waking up during phone call. It could be kernel or something in recent ROMs. I didn't notice this issue on my phone.
- Mantera reverts the event wakelock fix in theOC kernel, you say it's fixed, someone else (Bruce777) reported it only worked for 2 hours, then problem is back. I think we need more confirmation one way or another this works. Reverting it also likely will bring back the 'event" wakelocks left around as I and others have confirmed in the past. So far there hasn't been enough time to confirm the wakelock issue is gone in theOC, if it is, then that means my original fix & others reporting the wakelocks originally was some special fluke & due to something else that magically disappeared in recent builds.
- In my final build I still couldn't reproduce the the proximity sensor problem on my phone.
Basically going forward (if g60madman takes over), people should chime in when things work & also don't work with details, otherwise changes will be commited that could break things or cause complications.