Hi,
I have an activity using a surfaceView for drawing various objects
onto, and have observed different behavior when running the app in the
emulator and on the handset. The handset is a G1, running Android rev.
1.5, and the emulator is also a rev. 1.5 AVD.
When the app is running in emulator and the "lock-screen" key is
pressed, the onSaveInstanceState() method is invoked - this is the
behavior I would expect. When the same is performed on the actual
handset onSaveInstanceState() is also invoked, however followed by
onDestroy(), and a cycle through the acitivity life cycle:
02-01 11:36:26.531: INFO/com.spigo.balloons.Balloons(22453):
onSaveInstanceState()::called
02-01 11:36:26.531: INFO/com.spigo.balloons.BalloonsGame(22453):
saveState():called
02-01 11:36:26.531: WARN/com.spigo.balloons.Level(22453): saveState
()::balloonsInLevel==null
02-01 11:36:26.541: INFO/com.spigo.balloons.Balloons(22453): onPause
()::called
02-01 11:36:27.531: INFO/WindowManager(90): Setting rotation to 0,
animFlags=0
02-01 11:36:27.551: INFO/WindowManager(90): Config changed:
{ scale=1.0 imsi=0/0 locale=en_US touch=3 key=2/1/2 nav=3 orien=1 }
02-01 11:36:27.591: INFO/WindowManager(90): Config changed:
{ scale=1.0 imsi=0/0 locale=en_US touch=3 key=2/1/2 nav=3 orien=1 }
02-01 11:36:27.951: WARN/InputManagerService(90): Starting input on
non-focused client android.view.inputmethod.InputMethodManager
$...@439cf618 (uid=1000 pid=90)
02-01 11:36:28.151: INFO/com.spigo.balloons.Balloons(22453): onDestroy
()::called
02-01 11:36:29.701: WARN/InputManagerService(90): Starting input on
non-focused client android.view.inputmethod.InputMethodManager
$...@439cf618 (uid=1000 pid=90)
02-01 11:36:32.581: WARN/SurfaceFlinger(90): timeout expired
mFreezeDisplay=1, mFreezeCount=0
02-01 11:36:32.681: WARN/WindowManager(90): App freeze timeout
expired.
02-01 11:36:32.691: WARN/WindowManager(90): Force clearing freeze:
AppWindowToken{43c60f20 token=HistoryRecord{43ab26f0
{com.spigo.balloons/com.spigo.balloons.Balloons}}}
02-01 11:36:33.481: INFO/com.spigo.balloons.Balloons(22453): onCreate
()::called - SIS is non-null
02-01 11:36:33.531: INFO/com.spigo.balloons.Balloons(22453): onResume
()::called - thread state: NEW
02-01 11:36:33.531: INFO/com.spigo.balloons.BalloonsGame(22453):
restoreState():called
02-01 11:36:33.541: INFO/com.spigo.balloons.Level(22453): restoreState
():called
02-01 11:36:33.571: INFO/com.spigo.balloons.Balloons(22453): onPause
()::called
02-01 11:36:33.571: INFO/com.spigo.balloons.BalloonsGame(22453):
saveState():called
The manifest states: android:screenOrientation="landscape", hence the
activity is forced into landscape nomatter the orientation.
A comparison report of the two logs is available at
http://dl.dropbox.com/u/253720/Report.html , the left hand side being
the emulator and the right being the handset.
Can it be related to the "Low Memory: No more background processes."
or the "App freeze timeout expired."?
"Verbose" logs are furthermore available at
http://dl.dropbox.com/u/253720/logEmulatorFull.txt
and http://dl.dropbox.com/u/253720/logHandsetFull.txt
Any ideas?
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
