On Fri, Dec 28, 2012 at 7:34 PM, Nathan <nathan.d.mel...@gmail.com> wrote: > Here are a few things I suspect might cause these things: > Firmware/hardware errors in the device:
"Device or storage overheats" is a duplicate of this, IMHO. This category should cover 100% of device-freeze situations, at least if "OS bugs" are considered "firmware errors". There's nothing an SDK app should be able to do in its own process that can lock up the device that isn't some sort of low-level issue, AFAIK. While most of these will be problems originating from the device manufacturer, modded ROMs can also introduce firmware errors or trigger hardware problems (e.g., overclocking and runaway heat buildup). > Runs out of memory: "Event loop gets full" is a duplicate of this, IMHO -- leastways, I am unaware of another bound on the queue used by Looper and kin. I don't think that this will cause a device freeze, though I could certainly be wrong about that. > Any sure fire technique you have found for freezing an Android, let me know > and I will try to *not* do it. I'd stay away from the liquid nitrogen. :-) -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Aqui estão alguns sites onde você pode perguntar ou responder dúvidas sobre desenvolvimento de aplicações para Android: http://www.andglobe.com -- 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
