When sliding open to wake while locked over the 2.1 3d Launcher homescreen, auto-dismiss freezes on the screen occasionally about mylockforandroid HOT 3 CLOSED

Here is the log illustrating resume occurring but not gaining focus till next 
screen 
off

03-30 09:10:18.693: VERBOSE/screenoff(7118): Screen just went OFF
03-30 09:10:19.107: DEBUG/dalvikvm(1097): GC freed 4137 objects / 221440 bytes 
in 
236ms
03-30 09:10:19.592: DEBUG/dalvikvm(1097): GC freed 2409 objects / 114504 bytes 
in 
138ms
03-30 09:10:20.706: INFO/WindowManager(1097): Setting rotation to 1, animFlags=1
03-30 09:10:20.732: INFO/ActivityManager(1097): Config changed: { scale=1.0 
imsi=310/4 loc=en_US touch=3 keys=2/1/1 nav=2/1 orien=2 layout=34}
03-30 09:10:20.842: VERBOSE/RenderScript_jni(5933): surfaceDestroyed
03-30 09:10:20.842: VERBOSE/RenderScript(5933): setSurface 0 0 0x0
03-30 09:10:20.896: DEBUG/KeyguardViewMediator(1097): wakeWhenReadyLocked(26)
03-30 09:10:20.959: VERBOSE/RenderScript_jni(5933): destroyRenderScript
03-30 09:10:20.959: VERBOSE/RenderScript(5933): Context::~Context
03-30 09:10:20.959: VERBOSE/RenderScript(5933): RS Thread exiting
03-30 09:10:20.959: ERROR/libEGL(5933): call to OpenGL ES API with no current 
context 
(logged once per thread)
03-30 09:10:20.959: DEBUG/RenderScript_jni(5933): MessageThread exiting.
03-30 09:10:20.959: ERROR/libEGL(5933): eglSwapBuffers:1364 error 300d 
(EGL_BAD_SURFACE)
03-30 09:10:20.959: VERBOSE/RenderScript(5933): deinitEGL
03-30 09:10:20.959: VERBOSE/RenderScript(5933): setSurface 0 0 0x0
03-30 09:10:20.974: VERBOSE/RenderScript(5933): RS Thread exited
03-30 09:10:21.021: VERBOSE/RenderScript_jni(5933): createRenderScript
03-30 09:10:21.029: VERBOSE/RenderScript(5933): RS Launching thread
03-30 09:10:21.029: DEBUG/KeyguardViewMediator(1097): handleWakeWhenReady(26)
03-30 09:10:21.045: DEBUG/KeyguardViewMediator(1097): pokeWakelock(10000)
03-30 09:10:21.045: INFO/power(1097): *** set_screen_state 1
03-30 09:10:21.092: DEBUG/Sensors(1097): using sensors (name=sensors)
03-30 09:10:21.592: DEBUG/SurfaceFlinger(1097): Screen about to return, flinger 
= 
0x14c530
03-30 09:10:21.717: DEBUG/dalvikvm(1097): GC freed 1914 objects / 88424 bytes 
in 
195ms
03-30 09:10:21.842: VERBOSE/screenon(7118): Screen just went ON!
03-30 09:10:21.849: VERBOSE/acquire(7118): **Wakelock acquired
03-30 09:10:21.904: INFO/ActivityManager(1097): Starting activity: Intent { 
flg=0x50040000 cmp=i4nc4mp.myLock/.AutoDismissActivity }
03-30 09:10:22.021: VERBOSE/dismiss(7118): creating dismiss window
03-30 09:10:22.029: VERBOSE/dismiss(7118): resume occurred
03-30 09:10:22.115: INFO/ActivityManager(1097): Displayed activity 
i4nc4mp.myLock/.AutoDismissActivity: 191 ms (total 7759 ms)
03-30 09:10:22.232: DEBUG/skia(1097): purging 191K from font cache [12 entries]
03-30 09:10:24.092: DEBUG/dalvikvm(1097): GC freed 3056 objects / 141104 bytes 
in 
145ms
03-30 09:10:25.464: DEBUG/WindowManager(1097): I'm tired mEndcallBehavior=0x2
03-30 09:10:25.701: INFO/power(1097): *** set_screen_state 0
03-30 09:10:25.714: DEBUG/SurfaceFlinger(1097): About to give-up screen, 
flinger = 
0x14c530
03-30 09:10:25.740: DEBUG/Sensors(1097): using accelerometer 
(name=accelerometer)
03-30 09:10:25.748: VERBOSE/dismiss(7118): pause occurred
03-30 09:10:25.795: VERBOSE/screenoff(7118): Screen just went OFF
03-30 09:10:26.029: DEBUG/dalvikvm(1097): GC freed 2585 objects / 151384 bytes 
in 
109ms
03-30 09:10:27.896: INFO/power(1097): *** set_screen_state 1
03-30 09:10:27.912: DEBUG/Sensors(1097): using sensors (name=sensors)
03-30 09:10:27.935: VERBOSE/dismiss(7118): resume occurred
03-30 09:10:27.967: WARN/WindowManager(1097): Rebuild removed 7 windows but 
added 5
03-30 09:10:28.045: VERBOSE/dismiss complete(7118): gained focus, doing finish 
broadcasts
03-30 09:10:28.052: INFO/ActivityManager(1097): moveTaskToBack: 220
03-30 09:10:28.092: VERBOSE/screenon(7118): Screen just went ON!
03-30 09:10:28.099: VERBOSE/release(7118): **Wakelock released

The issue is in the Launcher2 itself. It appears the dev is backing out from 
further 
development of that exact implementation, and it is not in the latest cyanogen 
builds. The issue never occurs in HelixLauncher (1).