andrew wrote: > But there have a problem,my activity will be keepped on calling by > service, so this activity will do the thing:hiding and redisplaying > the locked screen endless.
This would seem to be a bug in your code. Fix this bug, and your problems will go away. Alternatively, provide us with a good justifiable reason why Android needs to support "hiding and redisplaying the locked screen endless". > After the activity being called thirty or much more times,an exception > was thrown like this: > > dalvikmv-heap 28900-byte external allocation too large for this > process . > VM won't let us allocate 28900 bytes. This means either the keyguard ran out of memory or at least had enough heap fragmentation that it could not allocate the requested amount. > Oh,as a fact,I have tried for more than five times like this: > Click endcall to lock screen,and then click menu to unlock screen. > Just do this again and again,about more than sixty or seventy > times,the exception: > "dalvikvm-heap 28900-byte external allocation too large for this > process . > VM won't let us allocate 28900 bytes."will be shown! > > That is to say,the exception is not caused by my activtiy! No, but it *is* caused by unexpected input. While there is probably a bug here that should get fixed, most users will not attempt to lock and unlock their device "sixty or seventy times" in succession. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android App Developer Training: http://commonsware.com/training.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
