Kostya Vasilyev wrote:
> Hello,
>
> I got my Milestone today and began updating my app for 2.1....
>
> When I change the device's orientation, I get this in the log:
>
> 05-16 23:38:44.619: INFO/ActivityManager(1271): Config changed: {
> scale=1.0 imsi=250/99 loc=ru_RU touch=3 keys=2/1/1 nav=2/1 orien=2
> layout=34}
> 05-16 23:38:44.674: DEBUG/PhoneApp(1330): updateProximitySensorMode:
> state = IDLE
> 05-16 23:38:44.674: DEBUG/PhoneApp(1330): updateProximitySensorMode:
> lock already released.
> 05-16 23:38:44.698: INFO/UsageStats(1271): Unexpected resume of <my app
> here> while already resumed in org.kman.SimpleTest
>
> The "unexpected resume", as I understand, should not be there. Sometimes
> my app crashes inside Android's native code shortly afterwards.
>
> Now here is some weird stuff.
>
> I made a simple skeleton application to test orientation changes. Just
> ran the new Android project wizard, added a text view to the default
> (empty) layout, and set debuggable to true.
>
> This skeleton application also generates the "unexpected resume" warning!
The "unexpected resume" message is benign. Please ignore it.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy
Android Development Wiki: http://wiki.andmob.org
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
