[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
Anand gets 6 hours stock kernel screen on time. Look, asking someone to show 6 hours screen on time. Like what are you trying to prove? I'm not saying Franco kernel is bad. I'm just saying users showing 6 hours of SOT here doesn't mean much. Your 6 hours SOT is different from my 6 hours SOT, assuming 6 hours is easily reachable. You might be busy chatting while I'm reading news articles. Our usage patterns are different. So yeah, some people can only achieve 2 hours SOT because they're busy gaming or whatever. I only get 1.5 hours SOT playing Ingress. Does that mean my Nexus 4 sucks?

http://xdaforums.com/showthread.php?t=2013383

There's users there reporting 6 hours.

Look I'm not trying to troll, the data is out there. It's possible to get 6 hours SOT on stock.

They don't know what they're doing? They have controlled testing. You're right, they can't replicate what you do for normal use.

How is your own non-scientific use of your phone a better test? How do you control your usage so its the same day to day? You can only at best approximate. Plus things change day to day. Do you control 1 email per 30 minutes? 3 facebook messages per hour? 3 SMS per hour? Standing in exactly the same spot for the same reception?

I'm not doubting that Franco is better than stock. But I have never seen a controlled test done comparing battery life across custom kernels. Maybe I'll make it my goal now and just not use my N4 for a few weeks. I don't know.

How does my stuff not make sense regarding the N4? It's scientific reasoning. I'm not new to the N4 and I have seen posts about users who claim to have a proximity sensor. But how can you take half the posts on XDA seriously when half the posts here are about how good battery life is on r118 only 3 hours into the release, or people going "zomg no i want r111." Half the posts here about bug reports aren't even in legible sentences--this goes for the proximity sensor complaints also. The only person who tried to document this has a video that's clearly flawed and highly suspect. On the other hand there is a video with someone running a screen protector showing his N4 works WITH the screen protector.

I've had TWO N4s now both with the SGP screen protector without cutouts. I had the initial shipment and because I didn't believe some of those complaints I didn't switch it out to the new ones with cutouts. I actually have the protectors with teh cutouts they shipped me but am holding on to it until I really need them. For now I'm just using the ones without cutouts. I have NEVER had proximity sensor issues. The only proximity sensor issue I have is that the screen doesn't turn back on after calls. HOWEVER, that is a documented bug and is related to Touch Control and nothing to do with the screen protector. Uninstalling touch control returns proximity sensor back to normal in calls.

I know MANY users here use Touch Control, and before we blame the screen protector, I think it's worth making sure that the user isn't experiencing the Touch Control bug. There may be other apps out there too that could cause issues that I'm not aware of. I'm just asking for good logical reasoning from you guys here. We're in a developer forum. Act with a bit of intelligence. Debugging isn't just shooting in the dark.

Anyway, off to a totally different topic, but what's the init.d command to set the screen off max frequency?