> No, but it *is* caused by unexpected input. While there is probably a > bug here that should get fixed, most users will not attempt tolockand > unlock their device "sixty or seventy times" in succession. >
Thanks for your answer! I known the users may not attempt to lock and unlock their device like this, and as now,maybe no other people known it has this problem except me! But that is to say,there mybe a bug,why and what caused the exception: "dalvikvm-heap 28900-byte external allocation too large for this process . VM won't let us allocate 28900 bytes." If I do other things like this one hundred or even more,nothing will happen! And only doing lock and unlock sixty or seventy times is a simply way for testing,in order to find wether the exception is caused by my application,or it is the API BUG. I have to do other things rather than lock and anlock the screen, in this condition,maybe the phone will reboot only do this less than ten times. So,I hope it can be resolved,and want to know the reason too. And due to this problem it has now,I have to try other way to avoid conflicting with the problem I have found. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
