Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Thread Closed

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

OP simms22

3rd January 2013, 09:31 PM   |  #1  
simms22's Avatar
OP Recognized Contributor
BROOKLYN!
Thanks Meter: 22,915
 
27,538 posts
Join Date:Joined: Jun 2009
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?
The Following 13 Users Say Thank You to simms22 For This Useful Post: [ View ]
4th January 2013, 01:30 AM   |  #2  
simms22's Avatar
OP Recognized Contributor
BROOKLYN!
Thanks Meter: 22,915
 
27,538 posts
Join Date:Joined: Jun 2009
maybe someone using another kernel/rom can try to reproduce this?
The Following 3 Users Say Thank You to simms22 For This Useful Post: [ View ]
4th January 2013, 04:26 AM   |  #3  
Senior Member
Thanks Meter: 98
 
610 posts
Join Date:Joined: May 2012
More
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/show...8#post35205418
http://forum.xda-developers.com/show...4#post35496824
The Following 2 Users Say Thank You to peikojose For This Useful Post: [ View ]
4th January 2013, 01:21 PM   |  #4  
pietropizzi's Avatar
Senior Member
Flag Vienna
Thanks Meter: 57
 
249 posts
Join Date:Joined: Aug 2008
Check my post here:

http://forum.xda-developers.com/show...ostcount=26638

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.
The Following User Says Thank You to pietropizzi For This Useful Post: [ View ]
5th January 2013, 04:07 PM   |  #5  
Ashtrix's Avatar
Senior Member
Thanks Meter: 345
 
1,249 posts
Join Date:Joined: Dec 2010
More
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 )
Last edited by Ashtrix; 5th January 2013 at 04:09 PM.
5th January 2013, 06:04 PM   |  #6  
OtavioMalzone's Avatar
Senior Member
Thanks Meter: 36
 
106 posts
Join Date:Joined: Jun 2012
More
Quote:
Originally Posted by Ashtrix

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 )

Maybe because OMAP is abandoned at 3.0.
5th January 2013, 06:06 PM   |  #7  
simms22's Avatar
OP Recognized Contributor
BROOKLYN!
Thanks Meter: 22,915
 
27,538 posts
Join Date:Joined: Jun 2009
Quote:
Originally Posted by Ashtrix

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 )

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).
5th January 2013, 07:20 PM   |  #8  
Jessie-James's Avatar
Senior Member
Flag BOURNEMOUTH
Thanks Meter: 378
 
1,022 posts
Join Date:Joined: Mar 2011
Donate to Me
More
Quote:
Originally Posted by simms22

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).

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
6th January 2013, 12:03 AM   |  #9  
simms22's Avatar
OP Recognized Contributor
BROOKLYN!
Thanks Meter: 22,915
 
27,538 posts
Join Date:Joined: Jun 2009
Quote:
Originally Posted by Jessie-James

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

if your device wakes, even after a few presses, its not sod.
6th January 2013, 04:05 PM   |  #10  
Ashtrix's Avatar
Senior Member
Thanks Meter: 345
 
1,249 posts
Join Date:Joined: Dec 2010
More
Quote:
Originally Posted by simms22

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).

we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?

Thread Closed Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes