Problem with rendering on Nook Color 2nd try

sharky151 · June 30, 2011, 4:38am

Sorry for the Double post it didn’t upload the first time.

First I’d like to thank all the devs. - This is a really cool project.

Second, I’d like to report a problem with the render on Nook Color running android 2.3.

Nightly builds from 6-28-11 and latter show the stats (Framebuffer, texture, ect) alittle squished and when rotating the screen

sideways the app need to force close. This would not happen on builds before 6-21-11.

Here is a little of the logcat

D/dalvikvm( 1200): GC_CONCURRENT freed 388K, 50% free 3056K/6087K, external 603K/1079K, paused 2ms+2ms

W/WindowManager( 1131): Window freeze timeout expired.

W/WindowManager( 1131): Force clearing orientation change: Window{4079ba60 SurfaceView paused=false}

W/WindowManager( 1131): Force clearing orientation change: Window{4079b398 com.jme3.androiddemo/com.jme3.androiddemo.MainActivity paused=false}

W/WindowManager( 1131): App freeze timeout expired.

W/WindowManager( 1131): Force clearing freeze: AppWindowToken{40948880 token=HistoryRecord{405aab70 com.jme3.androiddemo/.MainActivity}}

W/SurfaceFlinger( 1131): timeout expired mFreezeDisplay=1, mFreezeCount=0

D/dalvikvm( 1910): GC_EXPLICIT freed 5K, 51% free 2682K/5379K, external 0K/0K, paused 71ms

D/WifiService( 1131): ACTION_BATTERY_CHANGED pluggedType: 2

W/WindowManager( 1131): Window freeze timeout expired.

W/WindowManager( 1131): Force clearing orientation change: Window{4079ba60 SurfaceView paused=false}

W/WindowManager( 1131): Force clearing orientation change: Window{4079b398 com.jme3.androiddemo/com.jme3.androiddemo.MainActivity paused=false}

D/dalvikvm( 1131): GC_EXPLICIT freed 342K, 47% free 5320K/9991K, external 2413K/3014K, paused 53ms

D/Email ( 1777): *** synchronizeMailboxGeneric ***

D/dalvikvm( 1200): GC_CONCURRENT freed 389K, 50% free 3053K/6087K, external 603K/1079K, paused 4ms+5ms

I/InputDispatcher( 1131): Application is not responding: Window{4079b398 com.jme3.androiddemo/com.jme3.androiddemo.MainActivity paused=false}. 12465.4ms since event, 5000.4ms since wait started

I/WindowManager( 1131): Input event dispatching timed out sending to com.jme3.androiddemo/com.jme3.androiddemo.MainActivity

I/Process ( 1131): Sending signal. PID: 3287 SIG: 3

I/dalvikvm( 3287): threadid=4: reacting to signal 3

I/dalvikvm( 3287): Wrote stack traces to '/data/anr/traces.txt'

I/Process ( 1131): Sending signal. PID: 1131 SIG: 3

I/dalvikvm( 1131): threadid=4: reacting to signal 3

I/dalvikvm( 1131): Wrote stack traces to '/data/anr/traces.txt'

I/Process ( 1131): Sending signal. PID: 1222 SIG: 3

I/dalvikvm( 1222): threadid=4: reacting to signal 3

I/dalvikvm( 1222): Wrote stack traces to '/data/anr/traces.txt'

I/Process ( 1131): Sending signal. PID: 1200 SIG: 3

I/dalvikvm( 1200): threadid=4: reacting to signal 3

I/dalvikvm( 1200): Wrote stack traces to '/data/anr/traces.txt'

D/dalvikvm( 1131): GC_EXPLICIT freed 531K, 45% free 5518K/9991K, external 2413K/3014K, paused 54ms

E/ActivityManager( 1131): ANR in com.jme3.androiddemo (com.jme3.androiddemo/.MainActivity)

E/ActivityManager( 1131): Reason: keyDispatchingTimedOut

E/ActivityManager( 1131): Load: 0.29 / 0.18 / 0.14

E/ActivityManager( 1131): CPU usage from 7099ms to 1070ms ago:

E/ActivityManager( 1131): 3.4% 1131/system_server: 2.3% user + 1.1% kernel / faults: 106 minor

E/ActivityManager( 1131): 1.6% 1200/com.android.systemui: 1.6% user + 0% kernel / faults: 62 minor

E/ActivityManager( 1131): 0% 1777/com.android.email: 0% user + 0% kernel / faults: 64 minor

E/ActivityManager( 1131): 0.2% 1910/com.svox.pico: 0.2% user + 0% kernel / faults: 54 minor

E/ActivityManager( 1131): 0.3% 3287/com.jme3.androiddemo: 0.1% user + 0.1% kernel

E/ActivityManager( 1131): 0.1% 4/events/0: 0% user + 0.1% kernel

E/ActivityManager( 1131): 0% 1178/tiwlan_wq: 0% user + 0% kernel

E/ActivityManager( 1131): 9.3% TOTAL: 6.8% user + 2.3% kernel + 0.1% irq

E/ActivityManager( 1131): CPU usage from 405ms to 916ms later with 99% awake:

E/ActivityManager( 1131): 1.5% 3/ksoftirqd/0: 0% user + 1.5% kernel

E/ActivityManager( 1131): 1.9% 1131/system_server: 0% user + 1.9% kernel

E/ActivityManager( 1131): 1.9% 1164/InputDispatcher: 0% user + 1.9% kernel

E/ActivityManager( 1131): 1.9% 1289/Binder Thread #: 1.9% user + 0% kernel

E/ActivityManager( 1131): 2% TOTAL: 0% user + 2% kernel

I/InputDispatcher( 1131): Dropping event because the pointer is not down.

I/InputDispatcher( 1131): Dropping event because the pointer is not down.

D/dalvikvm( 1777): GC_EXPLICIT freed 173K, 46% free 3446K/6343K, external 325K/513K, paused 39ms

W/ActivityManager( 1131): Force finishing activity com.jme3.androiddemo/.MainActivity

I/ActivityManager( 1131): Killing com.jme3.androiddemo (pid=3287): user's request

I/Process ( 1131): Sending signal. PID: 3287 SIG: 9

I/ActivityManager( 1131): Process com.jme3.androiddemo (pid 3287) has died.

I/WindowManager( 1131): WIN DEATH: Window{4079b398 com.jme3.androiddemo/com.jme3.androiddemo.MainActivity paused=true}

I/WindowManager( 1131): WIN DEATH: Window{4079ba60 SurfaceView paused=false}

W/InputManagerService( 1131): Got RemoteException sending setActive(false) notification to pid 3287 uid 10038

I/CmStatusBarView( 1200): isStillActive returns false - CallerProcess: com.jme3.androiddemo CurrentProcess: android.process.acore CallerActivity:ComponentInfo{com.jme3.androiddemo/com.jme3.androiddemo.MainActivity} CurrentActivity: null

I/CmStatusBarView( 1200): isStillActive returns false - CallerProcess: com.jme3.androiddemo CurrentProcess: android.process.acore CallerActivity:ComponentInfo{com.jme3.androiddemo/com.jme3.androiddemo.MainActivity} CurrentActivity: null

I/CmStatusBarView( 1200): Fullscreen Attempt ProcessName: android.process.acore

I/CmStatusBarView( 1200): Fullscreen Attempt Top Activity: null

larynx · June 30, 2011, 11:00am

Tnx for notice. This is a bug in the app lifecycle. I will try to fix it soon.

larynx · June 30, 2011, 6:44pm

Fix is committed.

sharky151 · June 30, 2011, 11:49pm

I just tried your fix r7791 and it works perfectly!!!

No more force close, when rotating the screen.

Thank you !!

p.s. I'm still getting squished letters on the stats at the bottom and the performance is a little slower(26 FPS instead of 33 FPS)
---I'm going to do a little digging myself on that one, If I find anything, I'll let you know.

clear:
http://i1139.photobucket.com/albums/n543/sharky151/squished.jpg

squished:
http://i1139.photobucket.com/albums/n543/sharky151/squished.jpg
http://i1139.photobucket.com/albums/n543/sharky151/squished.jpg
http://i1139.photobucket.com/albums/n543/sharky151/squished.jpg

larynx · July 1, 2011, 6:53pm

If the problem persists please try to post a screenshot.

Edit 09.07.2011:

I dont know why i cant add a post to this thread, so i answer here.

I want to solve this, because 26 vs 33 fps is significant and could possible affect other devices too.

I added the config chooser because the old solution was hard coded, which worked on most devices,

but not on all. So i plan to add this hardcoded config again which then can be used by setting

ConfigType.LEGACY.

sharky151 · July 3, 2011, 3:41pm

Here is a picture of the clear stats.

http://i1139.photobucket.com/albums/n543/sharky151/clear.jpg

Here is a picture of the squished stats.

http://i1139.photobucket.com/albums/n543/sharky151/squished.jpg

Its a little difficult to see in the pictures, but if you look at the V in Vertices and the parentheses the look jagged all most like they are a different font or not smoothed. - The squished letters doesn’t really matter that much but the diminished performance(FPS) does matter.

As far as I can tell It has something to do with the AndroidConfigChooser - I’ve tried fastest and best - I’ve done some custom builds using the r7755 fix - But the chooser seems to be landing in a different mode than before there was a AndroidConfigChooser- 26 fps instead of 33 fps.

In the end its not a hugh deal - the nook color is not a very high end device, but the price is right - $249.00

thanks again.

sharky151 · July 15, 2011, 2:49am

ConfigType.LEGACY. works perfectly on the Nook Color — cyanogenmod android 2.3

No more squished fonts on the stats, and a increase performance (fps) in the apps.

Thanks you so much - - this engine just keeps getting better and better !!!

larynx · July 15, 2011, 8:53am

ConfigType.LEGACY is available now