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

MaLiXs · Jan 9, 2013

i cant replicate your issue simms perhaps i have thos strange awake "sod" most of time i got it randomly , while texting reading a post in xda tweaking an setting in kernel tool (specific app or trickster) i have tested some kernel (trinity,franco, lean and stock) and all have those freaky annoying thing. Yesterday i revert my GNEX to stock Yakaju JOP40D with google package (bone stock os is boring ....) and today i triggerred it simply by switching off auto brightness

i got same issue in auto or manual brightness whatever kernel or rom i use.

spacemanr · Jan 9, 2013

peikojose said:
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

I never ever used auto brightness and had sod. It started just one day without any connection with anything

.

MaLiXs · Jan 10, 2013

another issue : i was at home leaving my phon a minute to start some music on my pc ... xda was open and the screen goes off while not touching the phone ....

i was in manuel brightness

EDIT : 2 more time tonight... A réal sod while inactive, and second one while using quickpic...

On my Galaxy it seem to be realy random too much to made any conclusions yo this problem... My back cover gonna break one Day....

spacemanr · Jan 12, 2013

MaLiXs said:
another issue : i was at home leaving my phon a minute to start some music on my pc ... xda was open and the screen goes off while not touching the phone ....

i was in manuel brightness

EDIT : 2 more time tonight... A réal sod while inactive, and second one while using quickpic...

On my Galaxy it seem to be realy random too much to made any conclusions yo this problem... My back cover gonna break one Day....

Try with dax's kernel, it helped me. No sod for three days now. Wohoo.

MaLiXs · Jan 12, 2013

spacemanr said:
Try with dax's kernel, it helped me. No sod for three days now. Wohoo.

can i have a link of this ?

if it not work I'll made it simple .... reverting back to 4.1.2

spacemanr · Jan 12, 2013

MaLiXs said:
can i have a link of this ?

if it not work I'll made it simple .... reverting back to 4.1.2

I had to search for my self and couldn't understand why nobody has the link in bookmarks

. Well i saved it

.

http://xdaforums.com/showpost.php?p=36221996&postcount=26936

MaLiXs · Jan 12, 2013

spacemanr said:
I had to search for my self and couldn't understand why nobody has the link in bookmarks . Well i saved it .

http://xdaforums.com/showpost.php?p=36221996&postcount=26936

that will be my last try berfore reverting back to 4.1.2

spacemanr · Jan 12, 2013

MaLiXs said:
that will be my last try berfore reverting back to 4.1.2

It should work 100%

squidder · Jan 14, 2013

@mondo

No need to unlock just hold power button from lock screen its the same thing.

Sent from my Galaxy Nexus using xda app-developers app

MaLiXs · Jan 14, 2013

I'm final back to 4.1.2.. I'll waiting Google to release a New version to give another try

Envoyé depuis mon Galaxy nexus avec XDA premium

spacemanr · Jan 14, 2013

MaLiXs said:
I'm final back to 4.1.2.. I'll waiting Google to release a New version to give another try

Envoyé depuis mon Galaxy nexus avec XDA premium

You mean that this kernel didn't work for you?

MaLiXs · Jan 14, 2013

spacemanr said:
You mean that this kernel didn't work for you?

No and any other

Envoyé depuis mon Galaxy nexus avec XDA premium

spacemanr · Jan 16, 2013

MaLiXs said:
No and any other

Envoyé depuis mon Galaxy nexus avec XDA premium

Strange, you are the first one

.

Howie Dub · Jan 19, 2013

I'm not a dev, but could the culprit be disabling scroll cache? I was on mmuzzy's for a while and it seemed like I only started getting SODs after he included the disable scroll cache mod in his ROM. I'm currently on Xenon 2.0 using AirKernel #470 and haven't had a SOD with this combo. Went to AirKernel #483 and had one, so it seems like it could be a combo of the ROM and kernel that's causing the SODs. Iceandfire only lists scroll cache as being improved, so maybe it's not fully disabled? I have window animation and animator duration off with .5x for transition animation.

akira02rex · Jan 19, 2013

How many licks does it take to get to the center of a lollipop?
1... 2... 3...
The world may never know!

WEM97 · Jan 26, 2013

simms22 said:
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?

I think its confined to a few certain kernels in the way that it works. I have been running anarchy Dummy (Beta v) the latest versions for the last few months with nothing turning up. This does lead me to believe that your hypothesis is correct. It isnt a kernel issue, but that some kernels are more suceptible to it than others.

blackhand1001 · Jan 27, 2013

I think it may be related to the brightness adjustment smoothing they added in 4.2. Prior to 4.2 when you moved the slider it would instantly go to the brightness that you selected. In 4.2 it slowly adjusts to whatever brightness you set. Has anyone tried find this in the source code and reverting it to the 4.1 behavior. They also screwed up the screen off animation pretty badly. Its badly delayed and may be part of the culprit as well.

I don't know why google made the smoothness change. Having it instantly adjust to the brightness is superior as it makes it much faster to adjust it to desired brightness. They made quite a few changes in 4.2 that actually made certain tasks take longer.The new recents apps animation is another huge one and having it leave the current app adds quite a bit of time to entering the recent apps menu. Another strange bug/slowness is when opening the keyboard in an app. In 4.1 and earlier it would instantly resize the app and layout. In 4.2 it waits almost a full second before resizing.

simms22 · Jan 27, 2013

during one of these so called sod..
also it seams like the brightness gets set to 0 and doesnt adjust up.

D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 102ms
D/BluetoothAdapter( 751): 1112730840: getState() : mService = null. Returning STATE_OFF
D/LightsService( 389): Excessive delay setting light: 67ms
D/dalvikvm( 1164): GC_CONCURRENT freed 413K, 6% free 8951K/9444K, paused 5ms+2ms, total 34ms
D/dalvikvm( 751): GC_CONCURRENT freed 392K, 5% free 9877K/10376K, paused 5ms+2ms, total 37ms
D/BluetoothAdapter( 751): 1112730840: getState() : mService = null. Returning STATE_OFF
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 100ms
D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 68ms
D/LightsService( 389): Excessive delay setting light: 101ms
I/PlumeService_46000( 1525): start service from boot now
V/Plume_46000( 1525): prepare the clock to check the outbox service in 2 minutes
D/LightsService( 389): Excessive delay setting light: 99ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/dalvikvm( 668): GC_CONCURRENT freed 577K, 13% free 10890K/12404K, paused 3ms+2ms, total 25ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 65ms
D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 65ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/dalvikvm( 951): GC_FOR_ALLOC freed 316K, 6% free 9538K/10108K, paused 55ms, total 55ms
I/dalvikvm-heap( 951): Grow heap (frag case) to 9.402MB for 65552-byte allocation
D/dalvikvm( 951): GC_FOR_ALLOC freed 0K, 6% free 9602K/10176K, paused 16ms, total 16ms
D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 65ms
D/LightsService( 389): Excessive delay setting light: 65ms
D/dalvikvm( 751): GC_CONCURRENT freed 386K, 5% free 9877K/10328K, paused 4ms+1ms, total 22ms
D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/dalvikvm( 495): GC_CONCURRENT freed 10210K, 36% free 18901K/29136K, paused 6ms+5ms, total 59ms
D/LightsService( 389): Excessive delay setting light: 64ms
D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 65ms
D/LightsService( 389): Excessive delay setting light: 67ms
D/LightsService( 389): Excessive delay setting light: 64ms
D/LightsService( 389): Excessive delay setting light: 65ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 64ms
D/LightsService( 389): Excessive delay setting light: 66ms
D/LightsService( 389): Excessive delay setting light: 65ms
D/LightsService( 389): Excessive delay setting light: 65ms
D/LightsService( 389): Excessive delay setting light: 64ms

osm0sis · Feb 1, 2013

It's been suggested that Content Adaptive Brightness is faulty now in 4.2 causing reboots and other issues, so the screen getting turned off from 0 brightness could also make a lot of sense if it was involved with those screen-off "awake of deaths" as well.

MaLiXs · Feb 2, 2013

I would like to know know if Someone here have tested the New rev (like rascarlo build)

What about faux SoD's?

Envoyé depuis mon Galaxy nexus avec XDA premium

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

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Recognized Contributor - R.I.P

Senior Recognized Developer / Contributor

Senior Member

Similar threads

Top Liked Posts