I have a Lenovo A10-70F Android marshmallow tablet that is experiencing random full-system crashing. I've recently replaced the battery and factory reset the device yet the crashing continues.
The crashing behavior is not specific to a single app or a single use-case and seemingly happens at random times.
I've used
Code:
cat /proc/last_kmsg
to generate a logged account of one such crash, but I am new to logs and I'm not sure how to interpret the results. I've included a log in the link below, and I'd love some help making sense of it. I think it might have something to do with voltage in the CPU but I'm not too sure.
last_kmsg link — click to view
Related
I thoroughly enjoy my Galaxy Tab 10.1, but it's just not reliable.
Every now and again I'll awake my tablet from sleeping, only to find out it can't launch any process without crashing. Even the application error report system crashes.
Repro steps:
1) Open any application
2) See an application error report dialog
3) Tap the Report button
4) Tap the Send button on the report
See the error: "Could not save error report. no space left on device" (Settings->Storage confirms 26.59 GB free)
The only resolution is to restart the device until the whole thing happens again. It usually occurs once a day.
Model: GT-P7510MA (Galaxy Tab 10.1, 32 GB, WiFi)
Device is 100% stock. 1.4 GB of storage used for applications and ebooks.
All of my applications are from the Android Marketplace.
Running Services: Settings, Skype, Factory Test, Software update, SecPhone, Maps, Email, Android Keyboard
Sorry for the shaky video. You can see that I power it up, click on the browser and google talk, only to get crashes galore.
http : // youtu.be / UTKvrZ8hckg
Is anyone else having this problem?
Supplemental Info
I initially turned on disk encryption to keep my data safe.
After seeing the disk error from the Application Error Report dialog, I thought it might be a bug in encryption, so I performed a factory data reset and kept it standard.
I have had the 32gb wifi for over a week. Nothing like this. VERY sorry to hear. If you factory reset, just let it operate with defaults. Hold off on market apps that affect controls, performance, or substitute for existing core functions.
That way you can isolate if ot was a setting or app. If you're with in your return period I would for sure swap the unit. This is an isolated issue with this single unit would be my guess.
Sent from my GT-P7510 using Tapatalk
Called Samsung Support
Samsung Support wouldn't issue an RMA without having me going through and systematically installing each app, one at a time, and observing if the crashing occurs. A very logical request, but utterly annoying for me. Since the crashing is completely random, there is no way to definitely pinpoint the software issue without attaching a debugger (right?). I wish I could return this thing. There is not enough time in the day for this.
The support agent believes this is the behavior of a malicious software application and NOT defective hardware.
Are you beyond you return period from where you bought it?
Sent from my GT-P7510 using Tapatalk
i get the same thing everyday but when i hit send it says message sent
My tablet is beyond the return period, so I am relying on Samsung Support for an RMA.
I did another factory reset and used my old Google account that contained all of my previous apps. The TouchWiz update was applied as soon as it became available.
It's been 48 hours and no crashes. Maybe it was an OS bug that was patched during the update.
I've also ran Norton mobile anti-malware and a couple of other free scanners. Nothing malicious has turned up.
I frequently hear stories about people catching their dormant Android phones rebooting all of a sudden. They assume one of the apps working in the background might be the cause.
What can be done using its Linux subsystem to track down what exactly caused it to reboot?
Read a logcat in adb to see what causes the reboots. There's a low chance apps can actually cause it, it's most likely a Java fatal exception that requires a hard reboot to resolve.
adb shell
logcat gave me this screen shot.
I tried to install an app to just quickly read and save logcat files to SD card and it made the attached txt.
Which app is good to quickly give me a logcat file to post here?
Ok, so I wonder how to troubleshoot Android phone crashes, freezes, reboots, etc.
Maybe there are ways to troubleshoot these kind of events by looking at loggings to pinpoint the problem (like does a particular app cause this, or a hardware event, etc).
I see my HTC notices it recovered from an abnormal reset for instance, and asks to send logging to HTC HQ, so there seems to be ways that could tell more what is causing trouble?
Logcat is Android troubleshooting 101
Bat cave One
This problem started occuring recently, but I can't think of any particular triggers (updates or whatever).
What happens is that the Google Maps app randomly closes without any error. This usually happens when using the navigation mode. Sometimes it exits a couple seconds after opening the app, sometimes after multiple minutes.
Device: Jiayu S3 (cpu MT6752, gpu ARM Mali-T760 MP2)
ROM: Xtreme 1.3 (Android 5.1)
logcat excerpts:
Code:
--------- beginning of crash
F/libc (20534): Fatal signal 11 (SIGSEGV), code 1, fault addr 0xbaae in tid 20628 (mali-renderer)
I took two logcats, the fault address is not the same.
A bit earlier in the log I see a couple warnings like these two:
Code:
W/MALI (20534): glDrawArrays:714: [MALI] glDrawArrays takes more than 5ms here. Total elapse time(us): 8168
Code:
W/hwcomposer( 279): [JOB] (0) Timed out waiting for vsync...
Could it be a GPU issue? I have no problems when using other navigation apps such as Waze and HERE Maps.
One of the main issues is the device you are using. That chip is known to be sub par and cant handle long loads. Also as that is a China device there are a few times the satellite will kick it out and fc maps.
It worked fine before with the exact same usage scenario. I just ran this app (https://play.google.com/store/apps/details?id=com.into.stability&hl=nl), it has completed 200+ gpu passes with zero errors. The problem does not seem to have to do with long loads, as Maps will sometimes close after just a few seconds (after waking the device from sleep and opening Maps, no prior usage to speak of).
I forgot to mention what I have already tried:
Clearing cache and dalvik cache multiple times
Uninstalling and reinstalling Google Maps
Bonuman said:
It worked fine before with the exact same usage scenario. I just ran this app (https://play.google.com/store/apps/details?id=com.into.stability&hl=nl), it has completed 200+ gpu passes with zero errors. The problem does not seem to have to do with long loads, as Maps will sometimes close after just a few seconds (after waking the device from sleep and opening Maps, no prior usage to speak of).
I forgot to mention what I have already tried:
Clearing cache and dalvik cache multiple times
Uninstalling and reinstalling Google Maps
Click to expand...
Click to collapse
What did the logcat say. Also with those chips you can't trust tests. These devices are known to be changed to fool most standard tests as they don't use the hardware they say they do.
But pull a logcat. Troubleshooting 101
The logcat excerpts are in the OP. Do you need the whole file (it's 1.6MB)?
Bonuman said:
The logcat excerpts are in the OP. Do you need the whole file (it's 1.6MB)?
Click to expand...
Click to collapse
That is not a big file at all but what you posted points to issues with the chip. The Mali chip is crashing. Common happening after awhile with knock off devices.
I've attached the two logcats.
One I did with logcat -I, the other is unfiltered.
The problem seems to have resolved itself, possibly due to a Google Maps update.
good day everyone! i found this very helpful forum after searching for solutions to this problem I've been having and finding an eerily similar problem on a different Samsung device on a different thread:
https://forum.xda-developers.com/galaxy-note-8/help/stock-contact-app-crashing-want-to-view-t3686983
like the person in this post, i used the stock Samsung phone/contacts app. when i tap in a number, and then on info, the app stalls then gives me "contacts has stopped" and gives me the option to open the app again. none of the solutions in that thread seemed to apply to my version of the app/os/phone (no way to roll back updates if that's what's causing it) and none of the usual culprits seem to be effecting it (purged cache and storage, reboots, no overlay apps, removed theming, etc)
is anyone else having this problem or know what might be causing it? contacts app version is 3.8.01.20 on Android 8.
thank you for any assistance!