[Nexus One Android Development] ivanoff7:
Hey all,

In the process of improving this amazing ROM, I'd like to share the following:

sometimes my phone hangs for some time before doing what's beeing told. I have done a logcat of it (adb is so wonderful).

hereafter, an example with chrome.

I/Adreno200-EGL( 5050): <qeglDrvAPI_eglInitialize:294>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB.04.01.01.00.036_msm8960_JB_CL2644550_release_AU (CL2644550)
I/Adreno200-EGL( 5050): Build Date: 07/31/12 Tue
I/Adreno200-EGL( 5050): Local Branch:
I/Adreno200-EGL( 5050): Remote Branch: quic/master
I/Adreno200-EGL( 5050): Local Patches: NONE
I/Adreno200-EGL( 5050): Reconstruct Branch: AU_LINUX_ANDROID_JB.04.01.01.00.036 + NOTHING
I/ActivityManager( 1735): Process com.android.chrome:sandboxed_process1 (pid 9312) has died.
W/ActivityManager( 1735): Scheduling restart of crashed service com.android.chrome/org.chromium.content.browser.SandboxedProcessService1 in 5000ms
W/SandboxedProcessConnection( 9213): onServiceDisconnected (crash?): pid=9312
D/SandboxedProcessLauncher( 9213): stopping sandboxed connection: pid=9312
I/Choreographer( 5050): Skipped 31 frames! The application may be doing too much work on its main thread.
I/Choreographer( 9213): Skipped 77 frames! The application may be doing too much work on its main thread.
I/chromium( 9213): [INFO:child_process_launcher_android.cc(137)] ChromeProcess: Stopping process with handle 9312
D/SandboxedProcessLauncher( 9213): stopping sandboxed connection: pid=9312
W/SandboxedProcessLauncher( 9213): Tried to stop non-existent connection to pid: 9312
W/ThumbnailCache( 9213): Low Memory: Freed 0 textures from compression queue, 0 from write queue, 1 from the pinned list, 0 from the cache.
W/ManagedEGLContext( 9213): doTerminate failed: EGL count is 3 but managed count is 1
[COLOR="Red"][B]There, there was a hang for 5 seconds as indicated below[/B][/COLOR]
I/InputDispatcher( 1735): Window 'Window{416f72f0 com.google.android.apps.plus/com.google.android.apps.plus.phone.HomeActivity paused=false}' spent 5522.6ms processing the last input event: MotionEvent(action=9, deviceId=4, source=0x00001002)
I/InputDispatcher( 1735): Window 'Window{416f72f0 com.google.android.apps.plus/com.google.android.apps.plus.phone.HomeActivity paused=false}' spent 5523.1ms processing the last input event: MotionEvent(action=9, deviceId=4, source=0x00001002)
I/Choreographer( 5050): Skipped 336 frames! The application may be doing too much work on its main thread.
I/InputDispatcher( 1735): Window 'Window{416f72f0 com.google.android.apps.plus/com.google.android.apps.plus.phone.HomeActivity paused=false}' spent 5527.9ms processing the last input event: MotionEvent(action=7, deviceId=4, source=0x00001002)
I/InputDispatcher( 1735): Window 'Window{416f72f0 com.google.android.apps.plus/com.google.android.apps.plus.phone.HomeActivity paused=false}' spent 5368.2ms processing the last input event: MotionEvent(action=7, deviceId=4, source=0x00001002)
D/dalvikvm( 5050): GC_FOR_ALLOC freed 3058K, 20% free 22033K/27335K, paused 77ms, total 79ms
W/AndroidResourcesFactory( 9213): [chromesync#1319316392] Not running on internal thread since resources not started 68434, RegSyncHeartbeat:com.google.ipc.invalidation.ticl.RecurringTask$1@4155c968

Well I don't know how to make sense of it.Kernel issue? Graphics driver issue? Other?

If that can help...