Tagged: reboot

Runaway Android apps

mailmail

My phone (Google Nexus 4) has been getting really hot lately, draining the battery in the process. I started monitoring running Android processes and services, and found out that several apps sometimes don’t close when I tell them to, but keep running and consuming CPU cycles and battery juice. The biggest offender is Instagram, followed by Facebook (which starts on boot and keeps running (and restarts itself after a force-stop, the nerve!)), Google Play Music (which seems to randomly start itself on a whim, or possibly gets launched by Google Drive), and MailDroid (as ).

[UPDATE May 17, 2014] Adding Snapchat to the list of runaway apps that must be force-stopped after every use.

My response:

  • Remove the Facebook app, which I have been threatening to do for a while. I am not leaving Facebook, just removing the app from my phone.
  • Scale back the use of the Instagram app, and force-stop the app after each use.
  • Scale back the use of the Google Drive app, and force-stop Google Play Music after each use (confirm cause-and-effect).
    • [UPDATE from a ]: “Google support told me to uncheck the box Settings > Accounts > Google > Accounts > [myemail]@gmail.com > Sync Google Play Music. I had sync checked before the update as well, but it caused no problems. In any event, this didn’t do all that much good. The app is like the freakin’ Terminator — force stops won’t kill it.”
    • [UPDATE from A.T.]: Disabled Google Play Music. Problem solved.
    • [UPDATE from A.T.]: Also wiped a ton of other Google shit off my phone. It felt great.
  • Stay away from the MailDroid app.
  • Monitor Android system activity regularly for runaway apps and force-stop them as needed.
  • Reboot my phone daily.
  • advertisement
Follow A.T. on these networks
rssrss

Snapchat exposes severe Android 4.3 bug

mailmail

[UPDATE April 29, 2014] The crashes continue. Who do you think is at fault — Snapchat or Google? Vote in this quick poll.

***

[UPDATE April 29, 2014] Snapchat just crashed and rebooted my Google Nexus 4 for the umpteenth time. This has been going on for 267 days and counting. Running all latest software versions, applying all patches as soon as they are released. Still crashing. Shame on you, Google and Snapchat, for not being able (or not willing) to work together to fix this!

***

[UPDATE February 7, 2014] Snapchat crashed and rebooted my Google Nexus 4 twice yesterday. This has been going on for OVER SIX MONTHS, and apparently neither Google nor Snapchat can or would do anything about it. Legitimizes my conspiracy theory perhaps?

[UPDATE December 21, 2013] Snapchat update this morning. Will this stop the Snapchat/Android phone crashes/reboots? And if it does, does that mean that this has been Snapchat’s fault all along? Come back in a few days to read my report.

[UPDATE December 23, 2013] Snapchat just crashed and rebooted my device.

[UPDATE December 24, 2013] Another Snapchat update. This doesn’t make any sense any more. Or does it… New blog post to follow. [UPDATE: Published.]

***

Android 4.4.2 does NOT fix Snapchat crash bug

[UPDATE December 18, 2013] Snapchat just crashed and rebooted my Google Nexus 4 running Android KitKat 4.4.2. So it is still happening. Quite disconcerting that Google hasn’t squashed that Android bug. This is undoubtedly Google’s fault, not Snapchat’s. The OS should not crash due to a “misbehaving” app.

No word from Google on when (or how) they plan to address this issue.

***

Android 4.4.2 is here

[UPDATE December 12, 2013] Last night my Google Nexus 4 updated itself to Android 4.4.2 (strangely skipping 4.4.1). Will this stop the Snapchat crashes? Come back in a few days to read my report.

***

Android 4.4 KitKat does not fix Snapchat crash bug

[UPDATE December 09, 2013] After a relatively smooth (no crashes) period, last night Snapchat crashed/rebooted my device again. It is disturbing that Android — after three updates — still allows itself to be taken down by a legit application that was already on the 4.2 device and operating smoothly until 4.3 came out and the crashes began. Imagine what a rogue, malicious app could do.

***

[UPDATE October 14, 2013] Android still allows itself to be taken down by Snapchat. This began on August 5, 2013 with the release of Android 4.3, and continues to this day. Just how secure is Android?

***

With a message to users delivered with their most recent Android update, Snapchat goes on the record to say that the Nexus 4 device restarts, seemingly caused by Snapchat, are due to a bug in the Nexus 4 Android 4.3 operating system — an issue that is out of Snapchat’s control.

Some history: As soon as my Nexus 4 phone updated itself to Android 4.3, Snapchat started crashing. And not just crashing the app itself — it took the device down with it. This was annoying, but also troubling. Why would an OS upgrade allow a previously-installed app to crash the device? Subsequent updates to Android 4.3 (this is not a typo — Android 4.3 updated itself to Android 4.3) did not fix the problem.

I was not alone in this experience, which generated . I maintained that a robust OS shouldn’t allow an app — rogue or legit — to take down the device. I was in the minority. Many were quick to blame Snapchat, because this can’t be Google’s fault, right? Wrong!

Below is a screenshot of the Snapchat message to users, and a full transcript. I hope Google fixes the bug soon, and goes on the record to explain what had happened.

Snapchat message Nexus 4 Android 4.3 bug
Snapchat message Nexus 4 Android 4.3 bug

Dear Nexus 4 user,

Recently, you may have experienced device restarts while using Snapchat. Unfortunately, this behavior is caused by a bug in the Nexus 4 Android 4.3 operating system and is out of Snapchat’s control. If you would like to let Google know that this issue is important to you, please visit Nexus 4 support. Thank you for your patience.

  • advertisement
Follow A.T. on these networks
rssrss

Android 4.3 “improvements”

mailmail

[UPDATE October 14, 2013] Android still allows itself to be taken down by Snapchat. This began on August 5, 2013 with the release of Android 4.3, and continues to this day. Just how secure is Android?

***

[UPDATE October 9, 2013] Snapchat points the finger at Google, says a bug in the Nexus 4 Android 4.3 operating system — an issue out of Snapchat’s control — is to blame for the device crashes and reboots.

***

[UPDATE September 13, 2013] Snapchat still crashes the phone, after 3 Snapchat updates and one Android update. Phone vibrates for about ten seconds, like it’s in the throes of death. Then reboots. Why is it so easy to crash the phone?

***

As a proud owner of The Google Phone (a.k.a. Nexus 4), I was excited about the release of Android 4.3 (codename “occam”), and promptly installed it. So far I have seen the following “improvements”:

  • Snapchat crashes and reboots the device (as described and discussed in )
  • Some Instagram filters have adopted a weird green hue, as seen in the image below [UPDATE August 8, 2013] Instagram relased an update this morning, and the green hue is gone
  • No other damage so far
  • [UPDATE August 23, 2013] Three (three!!!) Snapchat updates after the release of Andriod 4.3, and the crashes seem to have disappeared. I applaud Snapchat, but keep wondering why Google/Android hasn’t taken any action. It seems to me that now Snapchat knows how to crash Android but chooses not to. Android watches idly and passively.
  • [UPDATE August 24, 2013] Snapchat crashed and rebooted the phone.
  • [UPDATE August 27, 2013] Android 4.3 updated itself to 4.3. Weird numbering sequence, but whatever. As long as the device stops crashing and rebooting, I’m cool. Snapchat hasn’t crashed since the 4.3 to 4.3 update, but I haven’t used it much. Unconfirmed reports from another Nexus 4 user indicate that the crashes still occur, although less frequently. Same user reports that friend with iPhone 4 also complains about Snapchat crashing their phone.

Now before you say that Snapchat and Instagram are silly and don’t I have anything better to do, let me say that this is not about Snapchat or Instagram or any application per se. I am bewildered that an advanced OS like Android would allow a previously-installed application to repeatedly crash the device following an OS upgrade. No matter what the cause of the crash, it’s not the app’s fault.

  • advertisement
Follow A.T. on these networks
rssrss