1

Ocassionally when I use my phone, it crashes.

EDIT:

From analysing the pictures posted, we can conclude that the OP has an Asus Zenfone 2 (probably ZE551ML) running Lollipop 5.0 LRX21V.

This is very annoying if I play Clash of Clans and stuff. Imagine, in the middle of a war and then crash!

Fortunately I knew a way to get the system log.

I installed Airdrop Detector. It crashes on any phone. When it crashes it gives me an option to report the crash. I wonder if there is another way to get that.

Here are some of the screen shots.

Click images to enlarge

IMG:

IMG:

IMG:

It says fatal signal hardware test.

The store I bought the phone from has a history of problems with the devices I bought from them. The first phone I bought had a Chinese ROM in it. The second phone has these constant ads. They managed to fix that. However, the original problem, namely that apps often crash is still there.

There are some error that complains about OpenGL:

Click images to enlarge

IMG:

IMG:

Please help me verify if the phone is hardware damaged or not.

I found a bug and I post the video on youtube

https://www.youtube.com/watch?v=JzAuaIw4RT0

  • Some OEMs offer hardware testing option under stock recovery? Did you check to see if you have such option, by booting into your stock recovery? See recovery, if needed. – Firelord Nov 20 '15 at 5:33
  • Please provide us with information about your device, such as make, model, Android version, etc. Also, what you need is to run adb logcat. I can assume that you have ADB set up, if you don't then refer here: android.stackexchange.com/questions/33216/… – Tamoghna Chowdhury Nov 20 '15 at 7:26
  • The first error indicates a segment fault probably, as the process was forcefully aborted. That might indicate a fault with RAM, but only as an extreme case. You should try a factory-reset to see if that helps. The second, I'm not really sure. Maybe the app needs an OpenGL version higher than that supplied by the OEM? Refer this: stackoverflow.com/questions/3413166/… – Tamoghna Chowdhury Nov 20 '15 at 7:35
  • It'z zenfone 2. I already updated the OS to the latest version. – user4951 Nov 20 '15 at 11:07
  • Also, a phone uses an eMMC or NAND flash for storage, not a hard drive. – Tamoghna Chowdhury Nov 20 '15 at 15:40
3
+25

A few things to note:

Answer compiled from comments

  1. A SIGABRT signal/error generally indicates that the system forcefully stopped a process from executing, via the syscall abort(). Refer this SO question.

  2. OpenGL ES libraries not found: It could be that your OEM does not or has not provided the OpenGL ES libraries which this app requires or has provided them in a non-standard location(usually OpenGL ES 3.0 is not provided on some devices (see this Android developer's resource), and library locations can change with kernel versions, an app relying on Kitkat's library location may not work on Lollipop).

  3. Crashes can be due to a number of issues, usually due to battery power issues or overheating, although either of these may not be immediately apparent.

You could try the following:

  1. A . This should help with any problems that are due to user misconfigurations.

  2. You could test (log) the temperature of your device with a suitable app such as CPU-Z or 3C Toolbox until you get a crash. If the device temperature goes above 70 degrees Celsius, overheating could be a cause of this behaviour.

  3. Similarly, you could also check the battery output current using CPU-Z, I am not exactly sure but from personal experience I can say that a battery draw voltage of less than 2000 mV at 40% to 60% charge level can lead to power issues and crashes. (Thanks to my old Micromax Canvas Magnus, which had a similar issue which I so diagnosed, and a battery replacement fixed it).

  4. As you yourself suggested, checking out customer service and user forums for the product might be a good idea.

  5. Also, as @Firelord suggested, you should check if your recovery offers some hardware-testing facilities, which some manufacturers provide.

  • For many/most non-deterministic hardware problems, it's nigh on impossible to have a "sure-fire" way to diagnose it. – Stefan Nov 26 '15 at 14:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.