Seriously, what does your phone running 100s of apps like TikTok, Browers, Facebook and everything else have to do with a closed system like car infotainments?
It's like saying that Linux will be crashing while driving SCADA systems because you've seen your KDE desktop crash a few times.
C'mon you guys are supposed to be engineers, think a bit -_-
"Android regularly crashes in part because it's very complex, but also in part because there's really not much of a problem if it crashes occasionally. Cars have much stricter requirements."
I don't remember a single Android crash or freezes in recent memory (various Samsung Galaxy S-series). Not that my iPhone crashes either.
If you think that Android doesn't crash, you must have never used it. My Samsung Android phone crashed on me so consistently on a daily basis - I couldn't even use apps like Google Maps or WhatsApp because they ALWAYS crash the system. Trust me, it isn't any better.
Nitpick: there's a big difference between an app crashing (which is what this sounds like) and an app crashing your phone (rendering it unusable or forcing a reboot).
May be more directly related to the CPU/etc load and HW age rather than software. If the phone's battery is older, it may not be able to keep up with the bursty power draw, which can cause the phone to crash.
The Android devices I've had the displeasure of using (Galaxy S2, Nexus 4) reboot/crash/hang on a more regular basis than any Windows computer I've used in the last ~10 years. I used WebOS devices for a while before switching to Android, and I don't remember the last time either of those crashed or needed to be power-cycled. My iPhone 1 was an unreliable piece of garbage, though, so I guess I can't specifically shit on Android here.
Anyway though, 'people don't want their phone to BSoD' seems a rather unsupportable statement: modern 'big seller' Android phones suffer from surprisingly poor quality control, especially if you install the OS updates on a regular basis. If they're not introducing some sort of hang/crash bug, they're breaking one or two of the built in applications. I remember one of the recent Nexus 4 OTA updates broke one of the built-in preferences panels under Settings - how do you ship an OS release without testing that?
Ultimately cool new features and apps are more compelling to people than actual stability, judging by how many of my smartphone-owner friends complain about phone crashes and hangs. They're still using those phones and buying the latest models...
I remember how I had once unimportant android service crashing that was set to instantly restart the service. And always gave the warning and you had to click ok - made the whole phone unusable until factory reset. Ok, half a second later ok. It was system. Couldn't be disabled - not that you could even get to the apps menu.
What kind of team of engineers thought that this kind of stupidity was a good idea.
In the middle of a long browser session with multiple tabs open and I receive a phone call boom. BSOD !
The phone restarts and the browser tries to reload all the tabs but the session is lost.
It bugs me even if this is once a week event. iPhone has been around for 6+ years and by now it should be mature enough to not go kaput when a piece of code misbehaves. Android (nexus 4) doesn't do that. They support hundreds of devices. Apple had only a handful and that too with much less diversity.
As an example, Facebook Messenger has become almost completely unusable on Android phones because the OS keeps killing the process despite the user specifically telling it to don't.
My Android phone started crashing mysteriously under load. I was so fed up after a while I switched to iPhone. I now assume that the degraded battery without throttling was responsible for the crashes.
Why is that not a problem with Android phones? Does Google have more accurate crash detection? Or is it just because much less Android phones with crash detection (such as the Pixel phones) are in use?
Once I was stuck with a ridesharing car opened and off in -20C because my old samsung s8 throttled so bad I couldn't even reboot it. It was completely unresponive with the flashlight still on discharging it even faster.
I couldn't leave the car too, being responsible for damages during the rent.
After a bit of time I remembered that to force shut down newer androids you have to hold volume down and power. Why would they not keep it as a long press is beyond me.
These sorts of anecdotes always appear. Here's mine -- Currently have a Galaxy S3 and a Nexus 4. Previously had a Galaxy S2 and Galaxy Glide. Prior to that had a Nexus One. Prior to that had a HTC G1 and G2.
The last time there was any system instability at all was early in the life of the Nexus One. The OS has been absolutely rock solid since.
Of course apps crash on occasion, just as they crash on my 3rd gen iPad and 5th gen iPod Touch. The system stability ruse, however, is noise.
It's like saying that Linux will be crashing while driving SCADA systems because you've seen your KDE desktop crash a few times.
C'mon you guys are supposed to be engineers, think a bit -_-
reply