Very interesting -- the last few days, my Galaxy Nexus has started rebooting a few times a day when pushing the app to it using Eclipse.
I cannot think of a trigger event that started this behavior. On Tuesday, May 1, 2012 4:13:36 AM UTC+8, ThomasWrobel wrote: > > Ok, I am using a HTC Legend. > The crashes didn't start when I started using the 3D, so I don't think > its a specific command thats doing it. Maybe a OpenGL related memory > leak. > > Anyway, using adb pull /proc/uptime I get > 65.94 18.30 > > The phone takes a good 20 seconds to reload, most of the time spent on > a HTC logo (first a static one for a long time, then it flashes and > then a animated one for a shorter time) > > If its hardware related I guess there isnt too much I can do about it, > but perhaps by figuring out the exact point it happens I can minimize > its occurrences. > > > On Apr 30, 8:26 pm, Chris Stratton <[email protected]> wrote: > > On Apr 30, 11:34 am, ThomasWrobel <[email protected]> wrote: > > > > > I also use the JPCT 3D library in my app, as well as using the camera > > > preview as a background, so the app is pretty heavy overall. > > > > My first hunch would be issues in the platform openGL implementation > > that probably uses. > > > > It would be worth doing some web searching on the phone model - it's > > possible others have found the same issue. > > > > Also you may want to figure out if you are getting a kernel reboot, or > > an android runtime framework crash & restart while the kernel > > continues running. Once you get adb working, look in /proc/uptime > > shortly after a crash - if it's a low number of seconds, your kernel > > rebooted, if it's a high number likely just the framework crashed and > > restarted. (You'll probably also see a bootloader splash screen after > > a power-on or kernel reboot, before the more lengthy startup animation > > that runs while the android runtime framework gets itself going.) > > > > It goes without saying, that if the platform is working as intended, > > there is nothing an app can do to cause a reboot, so the fact that it > > is happening means something is broken with the device/android build. -- 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
