What is it about Android that allows an application to "hard-crash" a device?

Question

I have a never-rooted Nexus 4 running latest stock (android 4.4.4). It has been "hard-crashing" lately. By "hard-crash" I mean the screen goes black and either the device restarts itself (I see the same splash screen that is displayed during boot), or I have to hold the power button for a long time to get it to start (longer than for a normal boot).

After evidence pointing to it being caused by Google's own "Google Now Launcher" app (even after a factory reset), I began to wonder what it is about an apk file installed from the Play store on a non-rooted device that could ever cause the phone to "hard-crash". I would think that the sandbox in which apps run would prevent any app from being able to hard-crash a device.

Well good, but I was assuming you had the problem after doing a factory reset, since that's what you actually said in your post. — Marty Fried, Aug 19 '14 at 21:04
Oops, you're right. Turns out I had a different problem, (which at first seemed to be the same problem) after factory reset. — Eddified, Aug 20 '14 at 03:42

score 0 · Accepted Answer · answered Aug 13 '14 at 07:22

Like on any OS, although the app code itself is isolated in its own process container, it's possible for the app to trigger problems in the OS itself or in the hardware. For example, if the crash you're seeing is caused by a hardware problem such as a damaged heatsink, then any heavy workload will make the hardware fail, and there's not much the OS can do to stop that. The least reliable part of most operating systems is the drivers, so if there's a bug in (say) the GPU driver, that could make the kernel hang regardless of which process caused the situation that triggered the bug.

In other words, it sums up to either a bug or faulty hardware. — Lie Ryan, Aug 13 '14 at 14:38

What is it about Android that allows an application to "hard-crash" a device?

1 Answers1