Develop Bugs

Disable Volume Wake Galaxy Nexus 4.0.4 Leaked ROM

Ever since I've flashed the leaked "stock" 4.0.4 ROM the volume buttons will wake the screen as well as the power button. (I'm told stock doesn't do this so someone has been playing around....?) I don't recall which 4.0.4 ROM I downloaded but regardless - if your Nexus does this and you don't like it, here is how to fix it.
Navigate to /system/usr/keylayout/ with Root Explorer or such and mount as read/write.
Make a backup of tuna-gpio-keypad.kl -- just in case
Then open tuna-gpio-keypad.kl in a text editor.
You will see 3 values after all of the header text information:
key 114 VOLUME_DOWN WAKE
key 115 VOLUME_UP WAKE
key 116 POWER WAKE
Delete the "WAKE" from the buttons you wish NOT to have wake the phone.
Save the file and restart.
FINALLY! No more accidental unlocking. I'm not sure why one would want the volume keys to unlock the phone when the power button does already but to each their own.
Consequently... if you wanted your stock phone to wake on volume you could maybe open the file and add in the "WAKE" - or the whole lines if they aren't already there. No guarantees on that though. Also no guarantees on this either - of course.

Why would anyone want that? Because its less wear and tear on the power button. I almost always only used the volume for audio. So allowing it to wake the device is allowing me to use volume and power buttons more evenly.
Sent from my Galaxy Nexus using xda premium

That doesn't happen on stock anyway, even if leaked. Not unless someone enabled it before you flashed it.

davidstech11 said:
Why would anyone want that? Because its less wear and tear on the power button. I almost always only used the volume for audio. So allowing it to wake the device is allowing me to use volume and power buttons more evenly.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The big problem for me is I use Tasker to automatically switch to different volume modes based on where I am. Having such a big button on one side seems to almost daily get triggered and then my ringer isn't where I want it or I miss calls/texts because it got on silent (one volume press down from vibrate). I've also done weird things accidentally because I'll reach in my pocket and touch a volume button and as I'm pulling it out things get touched on the screen.
I should probably also mention I'm not using a lock screen - that's probably also part of what makes it such a pain having it accidentally pressed.
Again, to each their own. I found it annoying for my situation so I'm sure someone else will as well and will appreciate the tutorial.

adrynalyne said:
That doesn't happen on stock anyway, even if leaked. Not unless someone enabled it before you flashed it.
Click to expand...
Click to collapse
Right. Which is why I'm wondering why a "stock" 4.0.4 ROM had this messed with.... I wish I remembered which ROM it was because I think it was mis-labeled... lol

Must have been
I've heard this a couple times, but I flashed my wife's phone with IMM30B (the ota, not a rom) when it leaked, and it has never existed this behavior.

Mah-ha! Googled the kernel version and found it.
http://forum.xda-developers.com/showthread.php?t=1481613
I only got the "Rooted,De-odexed,Zip-aligned ROM With Stock Insecure Boot Image Without Radios & Bootloader" and the "Native Tethering Hack".

davidstech11 said:
Why would anyone want that? Because its less wear and tear on the power button. I almost always only used the volume for audio. So allowing it to wake the device is allowing me to use volume and power buttons more evenly.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Here's another reason. The pogo pins are on the same side as the power button. So when the phone is in the horizontal desktop dock you can't unlock the phone. At least not with anything less than 4.0.4 and I'm not sure how they do it because I don't have it yet. It may very well be with that change to the power button. That may be why they did it in 4.0.4.

NCguy said:
Here's another reason. The pogo pins are on the same side as the power button. So when the phone is in the horizontal desktop dock you can't unlock the phone. At least not with anything less than 4.0.4 and I'm not sure how they do it because I don't have it yet. It may very well be with that change to the power button. That may be why they did it in 4.0.4.
Click to expand...
Click to collapse
Doubt it as the method in 4.0.4 doesn't work with slide unlock. It only works when the os is not locked.
So the volume only wakes the screen if not locked. If it is locked, it does not work.

I can confirm that the volume buttons wake the device on a 100% stock Sprint Galaxy Nexus. I checked the file and sure enough, both buttons on the volume rocker have WAKE next to them. Kind of annoying when the phone constantly wakes throughout the day due to my slightly-snug case. I was going to wait and see how long I could go before rooting, but this may just be a deal breaker.

so i can add the volume wake in a stock rom by entering those lines?
edit: those lines are there.. but volume doesnt wake

king23adrianc said:
so i can add the volume wake in a stock rom by entering those lines?
edit: those lines are there.. but volume doesnt wake
Click to expand...
Click to collapse
So adding the "WAKE" doesn't cause the volume buttons to wake the phone? Interesting.

c0mp13371331337 said:
I can confirm that the volume buttons wake the device on a 100% stock Sprint Galaxy Nexus. I checked the file and sure enough, both buttons on the volume rocker have WAKE next to them. Kind of annoying when the phone constantly wakes throughout the day due to my slightly-snug case. I was going to wait and see how long I could go before rooting, but this may just be a deal breaker.
Click to expand...
Click to collapse
It won't wake if the phone is actually locked.

adrynalyne said:
It won't wake if the phone is actually locked.
Click to expand...
Click to collapse
I have my device set to lock with a pattern, if that's what you mean. I press the power button to lock the device and turn the screen off, then when I press either button on the volume rocker, the phone's screen turns right back on and prompts me to enter the pattern, just as pressing the power button would.

Huh...Sprint must have changed the behavior, because AOSP 4.0.4 only works that way if it is not locked.

adrynalyne said:
Huh...Sprint must have changed the behavior, because AOSP 4.0.4 only works that way if it is not locked.
Click to expand...
Click to collapse
They must have; the only reason I can think of would be, as I believe someone else mentioned in the thread, the upcoming (current?) availability of an official dock would mean that the phone can't be woken up without the volume keys, unless you physically remove it from the dock, press the power button, then re-dock it.

The pros way outweigh the cons with the Galaxy Nexus. Especially if your not rooting. Because you could easily change the volume wake feature.
You go to another phone because you don't want to root and change a feature-and then get a phone with “skin" over ICS? You also get all kinds of crapware from the manufacturer and carrier. Again, the GN stock is still a better choice than a lot of other devices.
Sent from my Galaxy Nexus using Tapatalk 2

c0mp13371331337 said:
I can confirm that the volume buttons wake the device on a 100% stock Sprint Galaxy Nexus. I checked the file and sure enough, both buttons on the volume rocker have WAKE next to them. Kind of annoying when the phone constantly wakes throughout the day due to my slightly-snug case. I was going to wait and see how long I could go before rooting, but this may just be a deal breaker.
Click to expand...
Click to collapse
The pros way outweigh the cons with the Galaxy Nexus. Especially if your not rooting. Because you could easily change the volume wake feature.
You go to another phone because you don't want to root and change a feature-and then get a phone with “skin" over ICS? You also get all kinds of crapware from the manufacturer and carrier. Again, the GN stock is still a better choice than a lot of other devices.
Sent from my Galaxy Nexus using Tapatalk 2
Sent from my Galaxy Nexus using Tapatalk 2

chjade84 said:
The big problem for me is I use Tasker to automatically switch to different volume modes based on where I am. Having such a big button on one side seems to almost daily get triggered and then my ringer isn't where I want it or I miss calls/texts because it got on silent (one volume press down from vibrate). I've also done weird things accidentally because I'll reach in my pocket and touch a volume button and as I'm pulling it out things get touched on the screen.
I should probably also mention I'm not using a lock screen - that's probably also part of what makes it such a pain having it accidentally pressed.
Again, to each their own. I found it annoying for my situation so I'm sure someone else will as well and will appreciate the tutorial.
Click to expand...
Click to collapse
I see. With you NOT using the lock screen it makes sense for not using the volume wake feature. I do use the lock screen. It feels great having all these options with our Android devices.
Sent from my Galaxy Nexus using Tapatalk 2

davidstech11 said:
The pros way outweigh the cons with the Galaxy Nexus. Especially if your not rooting. Because you could easily change the volume wake feature.
You go to another phone because you don't want to root and change a feature-and then get a phone with “skin" over ICS? You also get all kinds of crapware from the manufacturer and carrier. Again, the GN stock is still a better choice than a lot of other devices.
Click to expand...
Click to collapse
Oh for sure. I'm by no means saying that I'm turning in my Galaxy Nexus because a button does something that I don't want it to do. Eventually I'll root it and just edit the file to suit my needs.
I completely agree that the pros outweigh the cons on the GN. Hell, I stuck with a Samsung Moment for two and a half years, despite all of its craptastic bugs, issues, and painful nuances.
I was merely pointing out that this is my biggest gripe with the phone thus far, and given that it's a pretty minor one, I'd say we're all doing pretty well with the device.

[Q] Alternative to Power Button to turn screen on / off

It's been something that has bothered me ever since I bought my Galaxy Nexus. The existence of just one physical button to switch the screen on and off makes me question the lifetime of Power Button.
Does anyone know of any apps, mods, whatever for this? My first thought was to enable the Volume Keys to wake up the screen, I have also read about the proximity sensor but I don't think having the sensor active all the time is a good approach. Another way could be shaking the phone to turn it on.

Taken from a google search .... "There's an app called "No Lock" that will wake the Nexus One using the Volume rocker"
May work on the Galaxy Nexus too maybe but i dont know

Yea, I've seen that app too but it doens't do exactly what I want. Plus it disables entirely the lock screen which is certainly something I do not want. :\

look for smart screen on app, it enables you to turn your device on and off with the proximity sensor
Sent from my Galaxy Nexus using xda premium

stevesmind said:
I have also read about the proximity sensor but I don't think having the sensor active all the time is a good approach.
Click to expand...
Click to collapse
grognaz said:
look for smart screen on app, it enables you to turn your device on and off with the proximity sensor
Click to expand...
Click to collapse
Please read the OP next time :-/

Cm9 has volume rocker wake. It also has a notification toggle that turns off the screen.
Sent from my Galaxy Nexus using Tapatalk 2

stevesmind said:
It's been something that has bothered me ever since I bought my Galaxy Nexus. The existence of just one physical button to switch the screen on and off makes me question the lifetime of Power Button.
Does anyone know of any apps, mods, whatever for this? My first thought was to enable the Volume Keys to wake up the screen, I have also read about the proximity sensor but I don't think having the sensor active all the time is a good approach. Another way could be shaking the phone to turn it on.
Click to expand...
Click to collapse
Screen off & Lock works fine & cuts the wear & t4ear on the power button in half. I halve it set up as swipe action in Nova launcher.

AOKP had volume rocker wake in the ROM Control too.

Can try this app "Smart screen on"
it uses the proximity sensor to wake the phone..

Leion said:
Can try this app "Smart screen on"
it uses the proximity sensor to wake the phone..
Click to expand...
Click to collapse
He said he doesn't want to keep the proximity sensor on.
Have you tried "ShakeOff"? Turn the screen off/on with a shake. I haven't tested it on the GN but it used to work on my old phone.
Sent from the future.

Volume rocker. You have warranty anyway for a year.
Also, you do realize there's only one way to accelerate in a car right? Are you worried that the pedal won't work everyday so you'll need to find an alternative way to drive?
Sent from my Galaxy Nexus using Tapatalk 2

theking_13 said:
Volume rocker. You have warranty anyway for a year.
Also, you do realize there's only one way to accelerate in a car right? Are you worried that the pedal won't work everyday so you'll need to find an alternative way to drive?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
that's a nice analogy. now consider this:
car's are made to last, let's say, for 10 years.
smartphones and electronics/gadgets in general aren't.
not even going to mention the "years of expertise" behind the mechanics on a car.
thanks - everyone - for the replies I will try those!

I will say the power button on this phone is we made and I'm sure it will last just fine
I've had worse. Like my thunderbolt
Sent from my Galaxy Nexus using Tapatalk 2

AOKP can do what you request.

my power button on my GN stopped functioning after 6 months of use. It requires me to press in very hard to get a response now or none at all. I'm in the process of backing everything up and beginning the warranty process with expansys. Have to say, I considered this to be the best phone I've ever had and this just leaves a bad taste in my mouth.

You could always try PGM Nexus (free). It allows you to unlock your phone by sliding your finger across the screen.

spovat said:
my power button on my GN stopped functioning after 6 months of use. It requires me to press in very hard to get a response now or none at all. I'm in the process of backing everything up and beginning the warranty process with expansys. Have to say, I considered this to be the best phone I've ever had and this just leaves a bad taste in my mouth.
Click to expand...
Click to collapse
Sounds personal...
Sent from the future.

SocialReject said:
Sounds personal...
Sent from the future.
Click to expand...
Click to collapse
how so? I'm not one to nitpick small flaws, every phone has them. the power button failing is a major issue though. I would've still attributed it to a defective exception if I hadn't see many more people reporting the same thing. I did start using the volume rocker wake in cm9, but probably a bit too late

3rdstring said:
Screen off & Lock works fine & cuts the wear & t4ear on the power button in half. I halve it set up as swipe action in Nova launcher.
Click to expand...
Click to collapse
I have used this for a couple months and it works really great!

Even i worry a lot about the power button thingy. I use PGM nexus free version and it partially does the job. But for screen off i still have to use the power button.
Had a very bad experience with my moto milestone regarding the power button.
Sent from my Galaxy Nexus using XDA

On/Off Button Placement

Anybody else bugged by the fact that they put the on/off button, like, the least reachable place on the phone?
I always have to juggle the phone around in my hand to reach the button, and then I have to juggle it back to reach the unlock ring. I mean, the two things I do most, pressing the on button and then sliding the unlock ring, are placed as far apart as possible. It's oddly cumbersome for such an elegant device. It's just a matter of time until I drop the damn thing. (I guess that way HTC sells more replacement screens... )
The volume buttons are where my thumb is, but I never use them. They are mostly in the way and I press them more by accident than on purpose.
Any idea whether there's a way to switch the on and volume buttons? There's probably no mod that can currently do this, but is this technically possible?

That is where the purpose of volume button to wake comes in handy. And yes, it is possible to do that.

Naah... not with me..
Yes it was a little bit difficult... but now I've become used to it....

there's a a mod for that
volume buttons to wake up the phone
use rc 3.0 or else search its thread
ckpv5 posted a long time ago
ummm... try searching -apm+ volume to wake
Sent from my HTC One V

I am using the volume wake thingie. But it will, you know, change my volume setting if I listen to any audio. Which I do a lot.
Also, you can't lock the phone with it. Which precludes my main use of the button: unlock phone, check clock or notifications, lock phone.
Anyways, I wondered about the technical possibility of just switching the buttons.

BirthdayDog11 said:
I am using the volume wake thingie. But it will, you know, change my volume setting if I listen to any audio. Which I do a lot.
Also, you can't lock the phone with it. Which precludes my main use of the button: unlock phone, check clock or notifications, lock phone.
Anyways, I wondered about the technical possibility of just switching the buttons.
Click to expand...
Click to collapse
paresh kalinani pls change your signature
the diffrent colours + size is hurting my eyes
@birthdaydog lolss..i wanted the volume keys to be the camera key just when we start the cam as to click self photos easily
quite diff to click self by touching screen

paarthdesai said:
@birthdaydog lolss..i wanted the volume keys to be the camera key just when we start the cam as to click self photos easily
quite diff to click self by touching screen
Click to expand...
Click to collapse
Well, then there is public interest in finding a way to mod the keys, right?
Try a two second timer.

I have somewhat large hands, and the placement doesn't bother me. I can reach the button with my index finger and reach the ring with my thumb.
I do really miss having an external camera button.

yeah its not too much of a problem for me. i can hit the power button, and then use the unlock ring, but it requires a bit of stretching. i dont have to move the placement of the phone in my hand though.

Home button vs lock button press when screen is locked and no lock screen security

Hello,
I've been using my new note 2 for two weeks now.. and I like it so much
I also used sgs2 and 3 before.
I'm not new to android.. I flashed roms, know every single setting in the device, rooted my sgs2 and tried lots of apps to customize them.
Regarding my issue, I like to set my device to none screen security because I always manually lock it with a press on the lock screen button after I do whatever I want to do with it, and to unlock I always press Home button to get back to where I was immediately without the need to swipe the lock screen.
The problem is when I lock it and there is an app running and then press the home button the screen goes to home default screen and do not just unlock the screen and keep it there where I was last, this was not the case with my sgs2 or sgs3.
If I press the lock screen button instead it does what I want but I prefer to use home button because its much easier.
Its not a big issue but its annoying sometimes because sometimes I get popup notification windows while the phone is locked (whatsapp for example) and I press the home button to see it and instead of just turning on the screen to see the window it goes back to home screen and the popup is gone, or in cases where I'am writing an email or reading something and meanwhile talking to somebody, if the screen gets locked, If I press the home button everything is gone. So I have to switch tasks to open my activity again.
I don't know if this is a jellybean issue or hardware (homebutton).
I know its not a big deal but I would appreciate if somebody can help get around this
Sent from my GT-N7100 using xda premium

It seems to be a jellybean feature no way around unless a mod comes out...
All jellybean roms in Note I had this feature and i remember seeing this thing on SGS III jellybean too

Just install the S Voice app , "voicetalk_NLI.apk".
In S Voice, set "double click active S Voice" will fix the issue.

This actually worked! Thanks
But the problem is that i use another app (home2) to control home button which makes me able to control what app runs when double clicking home or even use a combination of home with back or menu.
Its a very good app if you want to try it.
This leaves me with trying to deal with my original issue tho or just return to old factory setting
Sent from my GT-N7100 using xda premium

ghellxh said:
Just install the S Voice app , "voicetalk_NLI.apk".
In S Voice, set "double click active S Voice" will fix the issue.
Click to expand...
Click to collapse
thanks man! used to annoy me so much having to open the app again
edit. There's one slight problem, now it lags a bit to return back to the home screen..

Replicating 4.2.X "sod" and what it means..

As we all know(or should know if you read around the forums) that there is an issue with "sod". Now these sods are not the same as the sod i was familiar with before 4.2. Before 4.2, the device(s) were for all intensive purposes not alive. Sure you could connect to adb, but the device was "dead" until you pulled the battery and rebooted. But with these 4.2 "sods", the device is alive, with the exception of the screen not being able to turn on. Phone calls and messages still come in. notification sounds still play, and you can use the volume buttons to raise/lower the volume. But you still have to pull the battery and reboot for the screen to come back on. Running logcats via adb doesnt seem to show anything related. Well, ive found a way to reproduce these 4.2.X "sods" while the device is awake with the screen on. I can reproduce it at will, and have had other users confirm this. What i do is this.. I go into the main settings, display, then brightness. Turn off automatic brightness if its on. Now adjust the brightness, up, then down, then up(back and forth, but take your finger off the slider when you go up then down). now press ok to set the brightness. Go back into the brightness setting and repeat. Eventually(sometimes seconds, sometimes minutes) the screen goes completely black, like its off, but the device is completely awake. same as these 4.2 sods, phone calls and messages come in, notifications sound, etc. Only difference is the device screen is on when it goes black instead of it being off. The symptoms are the same. This behavior leads me to believe that it most likely isnt a kernel issue like many believe. I believe that its related to some coding that controls the screen. As we know, every rom/kernel has shown this behavior, even stock and unrooted(some more, some less). Personally, i had 3 of these sods last month(trinity kernel/rasbean rom), but i know that some users have them many times a day unfortunately. What could it mean that i can replicate this behavior on an awake device? Any more thoughts about this?

maybe someone using another kernel/rom can try to reproduce this?

I haven't tried your method yet. I'll and post my results here. I was able to replicate it using another program (check the links below)
But reading your post, I'm sure now that SOD has to do with autobrightness or brightness control (knowing that, maybe it is easy to solve?)
Check my posts:
http://forum.xda-developers.com/showthread.php?p=35205418#post35205418
http://forum.xda-developers.com/showthread.php?p=35496824#post35496824

Check my post here:
[URL="http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638"]http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638[/URL]
whre I answered to that phenomen. I was on RBJ + franco r348 that time
I can't reproduce (force) it now with RBJ + franco r360, I tried about 100 times.
Just wanted to post my results, maybe it's too early to tell as r360 is too young.

Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )

Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
Maybe because OMAP is abandoned at 3.0.

Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).

simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app

Jessie-James said:
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
if your device wakes, even after a few presses, its not sod.

simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?

Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
pressing and holding the power button for 10-20 seconds will force reboot those devices.

A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)

MondoMor said:
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
Click to expand...
Click to collapse
wouldnt it be easier to just pull the battery? thank you for your observations btw.

simms22, I actually think it is a kernel issue. I only experience SOD problems when i use a custom kernel. Also yesterday I flashed stock 4.2.1 and tried for 10 min to replicate SOD using your method - I could not. Today I tried again - nothing.

simms22 said:
wouldnt it be easier to just pull the battery? thank you for your observations btw.
Click to expand...
Click to collapse
My phone is in an Incipio case, and it's more of a pain to separate the case, especially if I'm in my car or out hiking or whatever. I've gotten pretty good at doing it blind. Also, years of running Windows have made me anal about doing orderly shutdowns. :laugh:
Forgot to add earlier: I was unable to replicate with the technique described in the OP. But as long as someone can get this to happen on demand, it ought to be solvable.
Edit: although I got the SOD in normal usage a few minutes after trying the technique in the OP. Maybe the display SODs on some specific number of brightness changes? That would explain it happening more often with autobrightness, also.

Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
Just hold down the power button for several seconds. Continue to hold down the power button until the screen blinks off and the boot logo appears.
We are flooding here.. lets discusse this other place and leave the devs alone here

i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod

andQlimax said:
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
Click to expand...
Click to collapse
When I was running the first few nightlies of CM10.1 it still did the "sod" on me. By default the animation settings are at 1.0. Not sure if it's different on stock.

I've had several sod's daily for last few day's and today finally flashed RBJ from the beginning plus dax's modified kernel and now i'm in watching phase. So far so good.

I have time without any sod... Maybe because I'm trying not to use auto brightness or because of the lastest versions of Francos kernel... Stock ROM
Sent from my Galaxy Nexus using xda app-developers app