I/O Summary: App Permissions

Rumors regarding the new app permissions system have been floating about the internet for weeks now. … more

NVIDIA Launches SHIELD Android TV at Google I/O

Since Android TV was announced at Google I/O 2014, there has been very little activity … more

Devs Beware – Automatic Backup Privacy Risks

One new feature of “Android M” (speculation on potential names welcomed … more

Android M to Bring New App Drawer

It has now been seen that Android M will receive a new app drawer as part of the stock … more

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

Thanks Meter: 24,281
By simms22, Recognized Contributor on 3rd January 2013, 08:31 PM
Thread Closed Subscribe to Thread Email Thread
4th February 2013, 06:17 AM |#41  
ak's Avatar
Recognized Contributor
Flag Ak Land Valley
Thanks Meter: 57,712
Donate to Me
I dont know what is the changelog for r1.2 but i have install rasbean and i dont have problem ... 2 days on.
12th February 2013, 02:55 AM |#42  
MaLiXs's Avatar
Senior Member
Flag Montreal QC
Thanks Meter: 289
Re: Replicating 4.2.X "sod" and what it means..
It now fine for me no more faux sod.... Perhaps because i have set the animations to 0.5 or it New rev.... Someone here have tested it without any animation?

Envoyé depuis mon Galaxy nexus avec XDA premium
13th February 2013, 04:05 PM |#43  
Thanks Meter: 19
If I'm reading the 4.2.2 changelog correctly, setting all animation scales to zero would trigger the SOD bug:


commit 9dd9e0c99dcb2db98ffbcf9ad97e58fab8d38640
Author: Craig Mautner <>
Date: Thu Nov 15 14:25:14 2012 -0800
Fix math errors causing black screen. DO NOT MERGE
Turning off animations in the Developer options creates a ValueAnimator
duration scale of 0. This is used as the denominator in RampAnimator
which, if the numerator is also 0, sets mAnimatedValue to NaN. Rounding
NaN to the nearest int produces 0 which is then assigned to
mScreenBrightness in DisplayPowerState.
A copy mistake which assigned mTransitionAnimationScale as the default
value for mAnimatorDurationScale in WindowManagerService is also
fixed here.
Bug 7515609 fixed.
Change-Id: I39f8d0a7abdd5a1fe70d757fe95fbddaf7a0ed51

Fixed three months ago.
The Following 2 Users Say Thank You to MondoMor For This Useful Post: [ View ]
13th February 2013, 07:52 PM |#44  
Senior Member
Thanks Meter: 92
Can anyone confirm that the latest Cyanogen Nightlies do not have the "sod" anymore? Also how would you disable the screen off animation without setting the animation scale to 0?
15th February 2013, 07:46 AM |#45  
osm0sis's Avatar
Recognized Developer / Recognized Contributor
Thanks Meter: 15,720
Originally Posted by MondoMor

If I'm reading the 4.2.2 changelog correctly, setting all animation scales to zero would trigger the SOD bug:

Fixed three months ago.

Perfect, yeah, JDQ39 appears to somehow be from late November if the kernel build date is anything to go by.
Last edited by osm0sis; 15th February 2013 at 07:49 AM.
25th March 2013, 10:53 PM |#46  
franciscofranco's Avatar
Recognized Developer
Flag Mountain View, CA
Thanks Meter: 96,471
Donate to Me
I think we can close this, Google fixed this ****. Thanks for the contributions guys.
The Following 7 Users Say Thank You to franciscofranco For This Useful Post: [ View ]
Thread Closed Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes