I dont know what is the changelog for r1.2 but i have install rasbean and i dont have problem ... 2 days on.

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

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 <cmautner@google.com>
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.

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?

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.

I think we can close this, Google fixed this ****. Thanks for the contributions guys.