Related
I just got my infinity a few days ago, and before I unlocked and rooted I wanted to ask if the stock 4.2.1 rom was susceptible to random reboots? It's rebooting while running an app at least once a day, with limited use. I don't know if this is common or if I've possibly got a lemon. Before I void my warranty, I wanted to see if this was the norm. I don't have this problem with my phone or my old tablet (both running a cm10.1 rom) , which is why I'm a little concerned. Thanks in advance for any thoughts
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
psudeke said:
I just got my infinity a few days ago, and before I unlocked and rooted I wanted to ask if the stock 4.2.1 rom was susceptible to random reboots? It's rebooting while running an app at least once a day, with limited use. I don't know if this is common or if I've possibly got a lemon. Before I void my warranty, I wanted to see if this was the norm. I don't have this problem with my phone or my old tablet (both running a cm10.1 rom) , which is why I'm a little concerned. Thanks in advance for any thoughts
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
My Cromi 4.6.5 is fine. What custom rom do you use?
Bone stock, just came out of the box about 3 days ago. I upgraded to 4.2.1 but have yet to do anything else. I want to root and unlock to truly enjoy my tablet (i'm a "crack flasher" on my other devices), but the possibility of a hardware issue makes me not want to void my warranty yet
psudeke said:
I just got my infinity a few days ago, and before I unlocked and rooted I wanted to ask if the stock 4.2.1 rom was susceptible to random reboots? It's rebooting while running an app at least once a day, with limited use. I don't know if this is common or if I've possibly got a lemon. Before I void my warranty, I wanted to see if this was the norm. I don't have this problem with my phone or my old tablet (both running a cm10.1 rom) , which is why I'm a little concerned. Thanks in advance for any thoughts
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Factory reset and see if it runs OK without any additional apps added. Often, not always, but often enough people have issues with an app(s). If it frequently crashes in that state, I don't imagine it will hurt to exchange it.
faustus1005 said:
Factory reset and see if it runs OK without any additional apps added. Often, not always, but often enough people have issues with an app(s). If it frequently crashes in that state, I don't imagine it will hurt to exchange it.
Click to expand...
Click to collapse
+1 factory reset and report back.
Unfortunately some of the random reboots are issues with the stock kernel and some apps misbehaving. It'll be a software issue.
sbdags said:
Unfortunately some of the random reboots are issues with the stock kernel and some apps misbehaving. It'll be a software issue.
Click to expand...
Click to collapse
Without seeing a couple of last_kmsg, it's impossible to know.
Thanks for the advice, I'm going to try the reset first and see if it helps. As for the last_kmsg file, from what I've read it sounds like I can pull that via an without being rooted, is that correct? The first method I saw called for the su command in terminal emulator, which I'm assuming won't work without superuser access.
Thanks again, I'll report back on the reset in a couple of days
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
_that said:
Without seeing a couple of last_kmsg, it's impossible to know.
Click to expand...
Click to collapse
sbdags said:
Unfortunately some of the random reboots are issues with the stock kernel and some apps misbehaving. It'll be a software issue.
Click to expand...
Click to collapse
faustus1005 said:
Factory reset and see if it runs OK without any additional apps added. Often, not always, but often enough people have issues with an app(s). If it frequently crashes in that state, I don't imagine it will hurt to exchange it.
Click to expand...
Click to collapse
** Update **
I did a factory reset, however i did go forward with reinstalling my apps from the playstore, and immediately upon selecting "Nova Launcher" as my launcher, it crashed. I grabbed the last_kmsg and have attached it below. I'm new to the Transformer so I apologize if i've included too much or too little, The entire file was larger than what XDA would allow me to upload, so I took my best shot at it based on what i imagine is a time stamp. If you need more i've got the original, i can split it in half and upload it that way. I should also point out, I did also go ahead and root, initially i tried this in order to back up my apps with Ti, but wasn't able to successfully root until after i did the factory reset (overlooked a setting in security for MotoChopper to work). If Nova Launcher is the problem, I can live without it until i switch to another rom/kernel.
Thanks again for looking at this, I appreciate it tremendously. I'm ready to unlock and satisfy my flasher habit
psudeke said:
I did a factory reset, however i did go forward with reinstalling my apps from the playstore, and immediately upon selecting "Nova Launcher" as my launcher, it crashed. I grabbed the last_kmsg and have attached it below.
Click to expand...
Click to collapse
That doesn't look like a (kernel) crash, it's a usermode-induced reboot:
Code:
[17914.684201] Restarting system with command ''.
Interesting is this one, a few seconds before the reboot:
Code:
[17899.372183] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
Usually I get this message when I remount /system as rw (read/write), however that requires root access. I've read that if you try to overwrite certain files in /system with root access, the device would reboot.
There are also some situations in which Android decides to reboot by itself, e.g. when a critical service process fails to start, or crashes too often. I thought that this will always reboot directly to recovery, but I may be wrong.
So until now, it looks like a software issue, but not a common one. Maybe someone else knows more. Keep checking last_kmsg after the next unexpected reboot to see if it's the same pattern.
psudeke said:
** Update **
I did a factory reset, however i did go forward with reinstalling my apps from the playstore, and immediately upon selecting "Nova Launcher" as my launcher, it crashed. I grabbed the last_kmsg and have attached it below. I'm new to the Transformer so I apologize if i've included too much or too little, The entire file was larger than what XDA would allow me to upload, so I took my best shot at it based on what i imagine is a time stamp. If you need more i've got the original, i can split it in half and upload it that way. I should also point out, I did also go ahead and root, initially i tried this in order to back up my apps with Ti, but wasn't able to successfully root until after i did the factory reset (overlooked a setting in security for MotoChopper to work). If Nova Launcher is the problem, I can live without it until i switch to another rom/kernel.
Thanks again for looking at this, I appreciate it tremendously. I'm ready to unlock and satisfy my flasher habit
Click to expand...
Click to collapse
Highly unlikely that it's Nova causing the crash - it would be common knowledge by now if Nova was incompatible with the TF700.
It has to be some other app you have installed, maybe in conjunction with Nova (or any other launcher?) that is causing the crash.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
berndblb said:
Highly unlikely that it's Nova causing the crash - it would be common knowledge by now if Nova was incompatible with the TF700.
It has to be some other app you have installed, maybe in conjunction with Nova (or any other launcher?) that is causing the crash.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Yeah, it did crash another time yesterday when Nova was not running. Unfortunately I wasn't able to pull the last_kmsg file at the time, but if it happens again, I'll post the file. Thanks again for everyone's help.
I had another crash last night, it had been running relatively smooth for a few days, although i wasn't using it much. I believe this is the section of the last_kmsg that details the error. Let me know if this sheds any light, the previous errors noted were not found again
[ 3026.029216] Kernel panic - not syncing: Fatal exception in interrupt
[ 3026.029285] [<c0016438>] (unwind_backtrace+0x0/0x144) from [<c0711110>] (dump_stack+0x20/0x24)
[ 3026.029395] [<c0711110>] (dump_stack+0x20/0x24) from [<c0713290>] (panic+0x88/0x1b4)
[ 3026.029502] [<c0713290>] (panic+0x88/0x1b4) from [<c0013418>] (die+0xec/0x100)
[ 3026.029564] [<c0013418>] (die+0xec/0x100) from [<c0013454>] (arm_notify_die+0x28/0x60)
[ 3026.029669] [<c0013454>] (arm_notify_die+0x28/0x60) from [<c00082e4>] (do_undefinstr+0x148/0x16c)
[ 3026.029774] [<c00082e4>] (do_undefinstr+0x148/0x16c) from [<c000edc8>] (__und_svc+0x48/0x60)
[ 3026.029830] Exception stack(0xc0acfd68 to 0xc0acfdb0)
[ 3026.029931] fd60: c1712070 c1712070 00006000 c1712070 c0ace000 00000102
[ 3026.030036] fd80: c0bc1fe4 c0ad0080 c0ace000 c1712070 c1710060 c0acfdec c0acfdb0 c0acfdb0
[ 3026.030095] fda0: c0085900 c1712088 60000113 ffffffff
[ 3026.030197] [<c000edc8>] (__und_svc+0x48/0x60) from [<c1712088>] (0xc1712088)
[ 3026.030257] Rebooting in 10 seconds..
[ 3036.043426] Restarting Linux version 3.1.10-g9827b9a ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease)
Thanks again for your help, and let me know if there's anything else i can provide.
psudeke said:
I had another crash last night, it had been running relatively smooth for a few days, although i wasn't using it much. I believe this is the section of the last_kmsg that details the error.
Click to expand...
Click to collapse
Usually the lines before these contain more relevant information.
psudeke said:
I had another crash last night, it had been running relatively smooth for a few days, although i wasn't using it much. I believe this is the section of the last_kmsg that details the error. Let me know if this sheds any light, the previous errors noted were not found again
[ 3026.029216] Kernel panic - not syncing: Fatal exception in interrupt
[ 3026.029285] [<c0016438>] (unwind_backtrace+0x0/0x144) from [<c0711110>] (dump_stack+0x20/0x24)
[ 3026.029395] [<c0711110>] (dump_stack+0x20/0x24) from [<c0713290>] (panic+0x88/0x1b4)
[ 3026.029502] [<c0713290>] (panic+0x88/0x1b4) from [<c0013418>] (die+0xec/0x100)
[ 3026.029564] [<c0013418>] (die+0xec/0x100) from [<c0013454>] (arm_notify_die+0x28/0x60)
[ 3026.029669] [<c0013454>] (arm_notify_die+0x28/0x60) from [<c00082e4>] (do_undefinstr+0x148/0x16c)
[ 3026.029774] [<c00082e4>] (do_undefinstr+0x148/0x16c) from [<c000edc8>] (__und_svc+0x48/0x60)
[ 3026.029830] Exception stack(0xc0acfd68 to 0xc0acfdb0)
[ 3026.029931] fd60: c1712070 c1712070 00006000 c1712070 c0ace000 00000102
[ 3026.030036] fd80: c0bc1fe4 c0ad0080 c0ace000 c1712070 c1710060 c0acfdec c0acfdb0 c0acfdb0
[ 3026.030095] fda0: c0085900 c1712088 60000113 ffffffff
[ 3026.030197] [<c000edc8>] (__und_svc+0x48/0x60) from [<c1712088>] (0xc1712088)
[ 3026.030257] Rebooting in 10 seconds..
[ 3036.043426] Restarting Linux version 3.1.10-g9827b9a ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease)
Thanks again for your help, and let me know if there's anything else i can provide.
Click to expand...
Click to collapse
Kernel Panic - basically the OS has detected a fatal error from which it can't recover so the only option is for it to force a reboot...
We can't see the bit above to see what it was doing before that....
sbdags said:
Kernel Panic - basically the OS has detected a fatal error from which it can't recover so the only option is for it to force a reboot...
We can't see the bit above to see what it was doing before that....
Click to expand...
Click to collapse
_that said:
Usually the lines before these contain more relevant information.
Click to expand...
Click to collapse
Sorry, still am new to this type of issue and have a lot to learn. Assuming that the beginning of each line is a time stamp, here everything that happened immediately before what i posted earlier. Let me know if you need more and thanks again.
psudeke said:
Assuming that the beginning of each line is a time stamp, here everything that happened immediately before what i posted earlier. Let me know if you need more and thanks again.
Click to expand...
Click to collapse
Thanks, this is the relevant part (and yes, the number is a timestamp).
[ 3026.027729] [<c0085900>] (call_timer_fn+0x50/0x190) from [<c008665c>] (run_timer_softirq+0x150/0x2a8)
[ 3026.027837] [<c008665c>] (run_timer_softirq+0x150/0x2a8) from [<c007e3a8>] (__do_softirq+0xdc/0x278)
[ 3026.027938] [<c007e3a8>] (__do_softirq+0xdc/0x278) from [<c007ea6c>] (irq_exit+0xa8/0xb0)
I know this bug (but not how to fix it) - looks like corruption in the timer list, so the kernel jumps to an incorrect address and crashes. I've had the same crash every few weeks with 10.6.1.14.4, but not yet with 10.6.1.14.8 (both my own near-stock kernels).
_that said:
Thanks, this is the relevant part (and yes, the number is a timestamp).
[ 3026.027729] [<c0085900>] (call_timer_fn+0x50/0x190) from [<c008665c>] (run_timer_softirq+0x150/0x2a8)
[ 3026.027837] [<c008665c>] (run_timer_softirq+0x150/0x2a8) from [<c007e3a8>] (__do_softirq+0xdc/0x278)
[ 3026.027938] [<c007e3a8>] (__do_softirq+0xdc/0x278) from [<c007ea6c>] (irq_exit+0xa8/0xb0)
I know this bug (but not how to fix it) - looks like corruption in the timer list, so the kernel jumps to an incorrect address and crashes. I've had the same crash every few weeks with 10.6.1.14.4, but not yet with 10.6.1.14.8 (both my own near-stock kernels).
Click to expand...
Click to collapse
Thanks for the info! This is my third android device and i've never had to look into kernel issues before, so I greatly appreciate your help! I guess this is really the best possible news, as its my intent to unlock and test out some other ROMs and kernels. I'm going to stay on stock for another week or so and keep an eye on any crashes, and post the kmsg if they do (and are different from above).
Thanks again :good:
_that said:
Thanks, this is the relevant part (and yes, the number is a timestamp).
[ 3026.027729] [<c0085900>] (call_timer_fn+0x50/0x190) from [<c008665c>] (run_timer_softirq+0x150/0x2a8)
[ 3026.027837] [<c008665c>] (run_timer_softirq+0x150/0x2a8) from [<c007e3a8>] (__do_softirq+0xdc/0x278)
[ 3026.027938] [<c007e3a8>] (__do_softirq+0xdc/0x278) from [<c007ea6c>] (irq_exit+0xa8/0xb0)
I know this bug (but not how to fix it) - looks like corruption in the timer list, so the kernel jumps to an incorrect address and crashes. I've had the same crash every few weeks with 10.6.1.14.4, but not yet with 10.6.1.14.8 (both my own near-stock kernels).
Click to expand...
Click to collapse
So, two more crashes to report. One happened last night, i pulled the last_kmsg but couldn't find anything to suggest that it even crashed. today, on my way home from work, it did it again. when i pulled the last_kmsg i was surprised to see that instead of the normal 900kb file i've been getting, this one was only 16k. not sure when it resets the file, but i've attached the entire file to the post. i'm starting to think i've got a defective device, given the constant lag and reboots (its often slower than my old kindle fire) let me know what you think and much thanks for all your help.
Another crash and not much in the last_kmsg file (attached). I'm assuming the file is getting wiped on reboot? Is there any other files that might be useful? I did an adb debug, but there's so much information i don't know if there's anything in particular that i should be looking for. Any one have any thoughts?
Thanks!
**POSSIBLE SOLUTION** Please post below if it works for you.
You may be here because you are getting random reboots, maybe you installed TWRP and your cache took forever to wipe or maybe your phone is just rebooting for god knows what reason, maybe these will help you!
After contacting a developer and having them look at some logs I found, I am determined it is something with the kernel in the N5 which probably runs ONDEMAND and is causing this issue with some devices which I see as more sensitive to higher clocks.
Follow the instructions EXACTLY and configure the kernel exactly as below! This could work with any custom rom as long as you use a custom kernel or you can change the way the kernel in that rom behaves. The kernel from my experiences works best as follows:
Best Kernel Settings
Mode: INTERACTIVE
Min: 300 Mhz
Max: 1985 Mhz (or closest below 2000 Mhz)
CUSTOM ROM & KERNEL | Flash CM11 & Franco Kernel
I will provide you the steps but you need to full restore your phone to an RMA ready standpoint, that means running the google supplied files, and relocking. At that point you can then flash Clockworkmod (DO NOT flash TWRP, I love TWRP but their recovery I believe started my issue) after you unlock, flash CM11 & Franco Kernel. Leave the kernel settings stock.
***Reason - When I originally installed TWRP, it took about 5 minutes just to wipe cache, after that the reboots began, I use CWM on this device but TWRP is on my other devices. CM11 is super smooth, im running the nightlies, and the Franco Kernel I believe relieves some of the stress that is causing the kernel panics if you use the default clocks which are lower than the stock ones.
Steps: **MUST BE BOOTLOADER UNLOCKED TO DO THIS**
1) Flash ClockworkMod Recovery (latest version), no matter your current state (fastboot flash recovery filename.img)
2) Wipe & Format the entire device and all partitions that are safe to do so from the custom recovery (including the internal storage)
*Device should be unbootable at this point, there is no OS
3) Download google's method of returning to stock here https://developers.google.com/android/nexus/images#hammerhead (I used 4.4 then sideloaded 4.4.1 & 4.4.2 but get 4.4.2 if link works)
4) Unzip googles file
5) Put your device in the Bootloader (Turn off, hold power + vol down)
6) Connect to your computer securely, run flash-all.bat
*once its done, your device will reboot and be completely stock
7) Put your device back in the Bootloader
8) Relock your device (fastboot oem lock)
9) Reboot your device
10) Go into the device & go into Settings > Backup & reset and do a Factory data reset.
11) Put device back in the Bootloader
12) Unlock your device (fastboot oem unlock)
13) Device will reboot and be stock once again
14) Put your device back in the Bootloader
15) Flash ClockworkMod Recovery (make sure its the latest one)
16) Boot into Recovery (Wipe data/cache/dalvik)
17) Reboot device
18) Download CM11 & gapps as well as Franco Kernel.
CM11: http://download.cyanogenmod.org/?device=hammerhead (get the nightlies!)
GAPPS: http://wiki.cyanogenmod.org/w/Gapps (I guess the latest one for CM11)
Kernel: http://forum.xda-developers.com/showthread.php?t=2508284 (get at least r20 if its not still the latest)
19) Place zip files on device
20) Reboot into recovery
21) Do another Data wipe/cache
22) Flash CM11 & GAPPS
23) Reboot device
24) Reboot into recovery again
25) Finally flash Franco Kernel (ONLY if your on 4.4.1, if your 4.4.2 use CM kernel but use INTERACTIVE Min: 300 | Max: 1985 (or so).
It may sound redundant and there may seem to be waaaayyyyy too many steps but these are the exact steps I took and I no longer have the issue. *Fingers Crossed* It may not work for everybody and I cannot be held responsible if something was to happen to your device from following these instructions.
Now my cache wipes super quick with CWM
**UPDATED**
So my Nexus 5 worked fine for awhile and now it is rebooting randomly at several different times without notice. I originally had it on AT&T then swapped it to Sprint, and another user below chimed in having similar issues with T-Mobile. The device seems to work just fine in your hands and will not restart, unless your using an application that will freeze, Hangouts, GPS, Google Play etc. The device almost always will reboot during GPS navigation, but the strange part is the device will be just sitting on the table next to me, no one touching it, no applications running and it will just start rebooting. If I leave it be and not touch it, the device will contain to reboot several times. Google applications hang up a lot and cause reboots when actually in use and I've been rebooted during calls several times.
Info on the reboots:
These reboots do not seem to be the normal "hard reboot" its more like a "soft reboot" whereas the phone cuts off, you see google, then the animation for a split second and its back up within seconds bypassing any lock screen you may have in place.
Things I've tried:
1) Factory reset using the zip file provided on the google site (e.g. running flash_all.bat) which restored any and all partitions, and stock recovery
2) I've tried rooted, unrooted, custom roms, stock roms, unlocked bootloader, locked bootloader, it doesn't matter, nothing changes
3) When I did the last attempt at a factory reset (yes as crazy as it sounds I did this several times thinking I was crazy lol) I left out the sim, didn't log into google and purposely left off ALL 3rd Party applications, therefore only running GOOGLE installed default apps (updated of course), and STILL reboots.
It seems sort of a lost cause, I am almost sure it is hardware related and have already put in my RMA, the phone should be here shortly. In the meantime if anyone has any ideas or is experiencing this same thing please chime in.
Video of single reboot:
http://youtu.be/Ss_zDxnD6jc
Correction it will randomly reboot regardless of the carrier and I am unsure maybe it is when it is losing coverage or something but it is either a bug or possibly a hardware issue. I have even used the Google method of restoring the phone to factory settings which also removes the custom recovery so the next thing that I will try is to relock the bootloader after another factory refresh.
Sent from my Nexus 5 using xda app-developers app
ssconceptz said:
Correction it will randomly reboot regardless of the carrier and I am unsure maybe it is when it is losing coverage or something but it is either a bug or possibly a hardware issue. I have even used the Google method of restoring the phone to factory settings which also removes the custom recovery so the next thing that I will try is to relock the bootloader after another factory refresh.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I've got the same problem using T-Mobile. Can't figure out any common cause behind it and it seems to be completely random. Further it seems to not be a full reboot. My phone's data is encrypted so I have to enter my password on phone start-up but it never prompts me to do so whenever I experience these reboots. I was running logcat overnight to see if I could catch it rebooting, but it never did ... until a few hours after I unplugged my phone.
As an FYI, I'm running the stock ROM, rooted
I even reset my phone completely and had no 3rd party apps, still having the issue. I am having mine replaced. I am not factory ROM unrooted and locked bootloader, still having the issue.
Sent from my Nexus 5 using xda app-developers app
ssconceptz said:
Correction it will randomly reboot regardless of the carrier and I am unsure maybe it is when it is losing coverage or something but it is either a bug or possibly a hardware issue. I have even used the Google method of restoring the phone to factory settings which also removes the custom recovery so the next thing that I will try is to relock the bootloader after another factory refresh.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I agree when the reboots happen it comes back up really really quickly.
Sent from my Nexus 5 using xda app-developers app
ssconceptz said:
I agree when the reboots happen it comes back up really really quickly.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Sounds like a service or app is hanging in the background and causing the phone to do a hot reboot.
ssconceptz said:
I even reset my phone completely and had no 3rd party apps, still having the issue. I am having mine replaced. I am not factory ROM unrooted and locked bootloader, still having the issue.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Since you're RMAing it you should probably see if you can run some hardware stress tests to force it to reboot, if it turns out to not be the hardware you'll just run into the same problems with the new one
ssconceptz said:
I agree when the reboots happen it comes back up really really quickly.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
My original thought but how do you explain after having it RMA ready and then no 3rd party apps installed just straight up out of the box nexus 5 and still getting the reboots?
Sent from my Nexus 5 using xda app-developers app
dabbill said:
Sounds like a service or app is hanging in the background and causing the phone to do a hot reboot.
Click to expand...
Click to collapse
What do you recommend. I'm almost sure its hardware. The thing freezes on various apps and I've had the phone reset several times with no apps installed other than the ones that come on the device and it still does it. Even the guys at sprint reset it, laid it down and it just starts rebooting without anyone touching it or opening an app. I will make a video to have a but of proof to work from.
Sent from my Nexus 5 using xda app-developers app
Maybe it has something to do with what apps your freezing. Maybe even ART if your using ART?
Sent from my Nexus 5 using Tapatalk 2
Not using ART. Im not even rooted. I literally went to the Google site, downloaded the zip file, went to the boot loader, ran the flash all .bat file which completely restores the device. I then proceeded to wipe the device, relock the boot loader and even the internal storage was cleared.
After all was said and done, I booted the phone, didn't log in with my Google, went back into gmail and logged in and only updated the Google apps, did not install a single 3rd party app at all. I left the phone alone for awhile then the reboots started.
I went to the sprint store and on the way there (10 min drive) the phone was untouched and rebooted several times. I sat at sprint for maybe an hr, they reset it again and let it sit, same happened, they ordered a new one.
I wish I had a solution, I really do.
Sent from my Nexus 5 using xda app-developers app
I can say it happens during Google apps mainly so Maps during GPS every single time, Google Music, and Hangouts are the primary apps it occurs in and they freeze become unresponsive then it hot reboots.
Sent from my Nexus 5 using xda app-developers app
You have Sprint T-Mobile and At&t all at once?
Sent from my Nexus 5
LMAO good point. Phone was purchased and activated on AT&T simply by inserting my Sim card. I used it for awhile and this issue occurred. I then moved the device to Sprint by going into the store and getting a Sim. Issue still occurred and I've even tried swapping back between the 2. I thought it was sprint related but not the case. As for T-Mobile someone else chimed in and had an issue with that carrier. I could potentially remove that from the title.
Sent from my Nexus 5 using xda app-developers app
When you mean you downloaded the Google zip file, you mean the full android image installed through the bootloader?
Do you know how to format, install the android image from fastboot and replacing the recovery?
If not, just RMA the device. Probably physical, just wanted to factor out any possible software issues.
Sent from my Nexus 5 using Tapatalk
You say it reboots on T-Mobile and Sprint but not AT&T.
Are you in LTE coverage for all three? T-Mobile and Sprint both use higher frequency LTE (AWS & PCS). AT&T, in most areas, uses 700 MHz LTE. I wonder, then, if the culprit is some sort of hardware defect in just your unit, tied to higher LTE frequencies?
Sanity check: Try disabling LTE the moment the phone boots up. Lock it to 3G. Can you still get the reboots to happen now?
I remember way way back in the Nexus One days, I had the AWS model of the Nexus One and was running it on Rogers Canada. Whenever it was on 2G/EDGE and using data, it would behave as if I was slowly moving the trackball to the left. Some sort of funky electrical crosstalk. Faulty unit. With RMA I got one without the issue.
So I installed catlog so I could track down a reboot right after it happened and according to the log, Binder is segfaulting ... while trying to garbage collect ( or at least garbage collection got called by a malloc).
Code:
12-04 06:38:38.272 F/libc (7847): Fatal signal 11 (SIGSEGV) at 0x00000020 (code=1), thread 7857 (Binder_2)
Code:
12-04 06:38:38.472 I/DEBUG (13195): backtrace:
12-04 06:38:38.472 I/DEBUG (13195): #00 pc 000372d8 /system/lib/libdvm.so
12-04 06:38:38.472 I/DEBUG (13195): #01 pc 00028ef8 /system/lib/libdvm.so (dvmHeapBitmapScanWalk(HeapBitmap*, void (*)(Object*, void*, void*), void*)+100)
12-04 06:38:38.472 I/DEBUG (13195): #02 pc 00037784 /system/lib/libdvm.so (dvmHeapScanMarkedObjects()+44)
12-04 06:38:38.472 I/DEBUG (13195): #03 pc 000293dc /system/lib/libdvm.so (dvmCollectGarbageInternal(GcSpec const*)+348)
12-04 06:38:38.472 I/DEBUG (13195): #04 pc 00029e94 /system/lib/libdvm.so (dvmMalloc(unsigned int, int)+180)
The only thing I've modified on this device that should affect such low level components is using TWRP to add root capabilties (which I assume just installs an su binary somewhere)
Not sure this is the same problem as ssconceptz but assuming the code itself isn't faulty, it could be a memory problem, after all, the Dalvik VM is the thing that's crashing. This is probably why it's a hot reboot and not a full system crash since 'only' the java process is crashing.
I ran StabilityTest v2 for 15 minutes and nothing popped up -- I'll probably have to run it for longer to find any errors.
Does anyone know of any method of testing the RAM of a phone? I'm guessing there's no port of Memtest lying around somewhere.
At this point, it might not be a bad idea to assume it's the phone and begin the RMA process. It's a pity that I'm outside the 15-day return window as I might be tempted to just return it and get a Moto X.
ssconceptz said:
LMAO good point. Phone was purchased and activated on AT&T simply by inserting my Sim card. I used it for awhile and this issue occurred. I then moved the device to Sprint by going into the store and getting a Sim. Issue still occurred and I've even tried swapping back between the 2. I thought it was sprint related but not the case. As for T-Mobile someone else chimed in and had an issue with that carrier. I could potentially remove that from the title.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, it pretty much does it all for you but I know how to do it.
Sent from my Nexus 5 using xda app-developers app
chrisinsocalif said:
When you mean you downloaded the Google zip file, you mean the full android image installed through the bootloader?
Do you know how to format, install the android image from fastboot and replacing the recovery?
If not, just RMA the device. Probably physical, just wanted to factor out any possible software issues.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I need to update my original post. It happens on any carrier I've tried. I see what your saying but with sprint you don't set it to LTE you set it to Global.
Sent from my Nexus 5 using xda app-developers app
cmstlist said:
You say it reboots on T-Mobile and Sprint but not AT&T.
Are you in LTE coverage for all three? T-Mobile and Sprint both use higher frequency LTE (AWS & PCS). AT&T, in most areas, uses 700 MHz LTE. I wonder, then, if the culprit is some sort of hardware defect in just your unit, tied to higher LTE frequencies?
Sanity check: Try disabling LTE the moment the phone boots up. Lock it to 3G. Can you still get the reboots to happen now?
I remember way way back in the Nexus One days, I had the AWS model of the Nexus One and was running it on Rogers Canada. Whenever it was on 2G/EDGE and using data, it would behave as if I was slowly moving the trackball to the left. Some sort of funky electrical crosstalk. Faulty unit. With RMA I got one without the issue.
Click to expand...
Click to collapse
I tried several tests myself with no luck. I'd recommend doing what I did and go all the way back to stock and see if it occurs, it does for me and its a hot reboot as the phone comes back up fast bypassing the lock screen. Happens most often when I'm not using the device or during Google application use. Most if the time if its in my hand and it doesn't freeze there's no issue. Its very annoying though. I may root today to get a logcat before I return it.
Sent from my Nexus 5 using xda app-developers app
I have seen a few posts already with similar title but I didn't find anything useful. I am having random reboot problems and I am attaching my Last KMSG file with this post. Any developer out here can guide me better.. I have tried every f**** ROM available for the phone.. every possible solution people have mentioned.. The last lines of my Kmsg file read like below:
[ 717.602894] SMP: failed to stop secondary CPUs
[ 718.603385] wcnss crash shutdown 0
[ 718.603459] Rebooting in 5 seconds..
[ 725.167585] SMP: failed to stop secondary CPUs
[ 725.167750] Going down for restart now
[ 725.168465] Calling SCM to disable SPMI PMIC arbiter
Can anyone help me?? All kind of help is appreciated .. Thanks
Mods / Forum admins DOC file more than 88 KB not allowed.. and DOCX with 8 MB allowed.. Any reason?
emptyragnarok said:
I have seen a few posts already with similar title but I didn't find anything useful. I am having random reboot problems and I am attaching my Last KMSG file with this post. Any developer out here can guide me better.. I have tried every f**** ROM available for the phone.. every possible solution people have mentioned.. The last lines of my Kmsg file read like below:
[ 717.602894] SMP: failed to stop secondary CPUs
[ 718.603385] wcnss crash shutdown 0
[ 718.603459] Rebooting in 5 seconds..
[ 725.167585] SMP: failed to stop secondary CPUs
[ 725.167750] Going down for restart now
[ 725.168465] Calling SCM to disable SPMI PMIC arbiter
Can anyone help me?? All kind of help is appreciated .. Thanks
Mods / Forum admins DOC file more than 88 KB not allowed.. and DOCX with 8 MB allowed.. Any reason?
Click to expand...
Click to collapse
I am no developer, but have you tried flashing via fastboot?
All clean flashes of ROM's lead to the same crashes?? I would just try a clean flash using twrp to wipe system, data, dalvik and cache, then factory reset, and install cm11s from scratch again and see how that goes. If it still happens try getting a new phone from opo cuz it could be a hardware problem at that point I guess once software problems have been ruled out.
Don't try custom kernels either for a period of time
Sent From Lollipopified Bacon Goodness!
ek69 said:
All clean flashes of ROM's lead to the same crashes?? I would just try a clean flash using twrp to wipe system, data, dalvik and cache, then factory reset, and install cm11s from scratch again and see how that goes. If it still happens try getting a new phone from opo cuz it could be a hardware problem at that point I guess once software problems have been ruled out.
Don't try custom kernels either for a period of time
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
Hey first thxz for reply. I have tried every possible ROM I could, Every I kernel present in forums... On AK kernel it gave different error in KMSG. otherwise mostly I get same error I have attached.. But anyhow it has to restart! I am not getting it if it's h/w issue or s/w .. but I have installed CLEAN Stock 11s based 44S / 38R like 10~15 times by now.. but nothing has worked for me
I have been having the same issue, found the only way to get it to working was to flash rom no gapps reboot then let it settle down then flash gapps reboot and again leave it for a little while and then log in to google account last. For me it was only gapps that seemed to be causing problems and after I had logged into play store/account. Edit : also I didn't connect to wifi till later on,
I've had good experience with using PA gapps packages, try those instead, they do require a clean flash though
Sent From Lollipopified Bacon Goodness!
I tried almost all the methods listed everywhere.. nothing worked.. I m thinking that it's h/w problem may be :| I gave it in a service centre today .. let's see what happens
Guys I was so much frustrated that I have submitted my device in service centre.. don't know how much time is it gonna take.. but let's see what happens
others suffering from this, you should check this out first: http://forum.xda-developers.com/one...us-one-stock-cm11-t2839870/page5#post59362462
Looks promising for me so far!
Hi everyone, I hope someone can help me on that one.
In the last 3-4 weeks, I've seen my Nexus 5 rebooting here and there randomly. He's not stock into a boot loop, he works just fine and then 'pop', I can see it rebooting without reasons.
I'm running stock 5.1.1, kernel 3.4.0-gbebb36b, Build number LMY48B. The phone is rooted manually, no automatic trick.
Does randomly reboots means something? Is there a way to see what happens/what happened like an event viewer in Windows?
Thanks a lot.
You can use 'adb logcat' to see system logs.
a hammerhead wrote this.
pplante19 said:
Hi everyone, I hope someone can help me on that one.
In the last 3-4 weeks, I've seen my Nexus 5 rebooting here and there randomly. He's not stock into a boot loop, he works just fine and then 'pop', I can see it rebooting without reasons.
I'm running stock 5.1.1, kernel 3.4.0-gbebb36b, Build number LMY48B. The phone is rooted manually, no automatic trick.
Does randomly reboots means something? Is there a way to see what happens/what happened like an event viewer in Windows?
Thanks a lot.
Click to expand...
Click to collapse
It will die soon.
Sent from my SM-G920T
ambervals6 said:
It will die soon.
Sent from my SM-G920T
Click to expand...
Click to collapse
Is that a known behaviour to a knwon issue or you're just saying this like that?
pplante19 said:
Is that a known behaviour to a knwon issue or you're just saying this like that?
Click to expand...
Click to collapse
Happened the same to my old nexus 5 before it got stuck in bootloop and I needed a new motherboard.
Sent from my SM-G920T
ambervals6 said:
Happened the same to my old nexus 5 before it got stuck in bootloop and I needed a new motherboard.
Sent from my SM-G920T
Click to expand...
Click to collapse
Ok, thanks for telling me. I'm not yet stuck in a bootloop yet, but I hope it will be ok until the Nexus 5 2015 gets released.
Power button could be playing up. Have you tried completely wiping it clean, fresh install it from Google files and don't root and test it for a week or two in case it's just a software bug somewhere
Sent from my Nexus 5 using Tapatalk
For me it was the power button. But, I could see the power menu appearing sometimes before it powered off. If this is the case, bang the power button to a table side, it actually works Seriously, it does.
Here are others who fixed it by banging it to a table: https://www.reddit.com/r/Nexus5/comments/2rpfuj/nexus_5_broken_power_button_keeps_rebooting/
Hello I have a Galaxy S7 and since the update to Android Nougat 7.0, my phone restarts randomly, it can stay an entire week without restart and it can also restart 2 days in a row. It's totally random. I have reset to the factory settings and I have reinstalled only the most important applications (facebook messenger, viber, yahoo mail) but unfortunately about ten days after reset, the problem has reappeared. What could be the cause of this problem? For info, the firmware version installed on my phone is: G930FXXU1DQBO. Also, I saw on SamMobile that the countries that received the update later, had a new version. Could the problem come from that? Is this a bug in the firmware installed on my Galaxy S7. Thank you in advance for your help.
Have the same problem, I'm on G935FXXU1DQB1.
Sent from my SM-G935F using Tapatalk
Vichenec said:
Have the same problem, I'm on G935FXXU1DQB1.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply Do you reset your phone too? And what is the average frequency of restarts?
Didn't do anything as it doesn't bother me that much.
Sent from my SM-G935F using Tapatalk
Vichenec said:
Didn't do anything as it doesn't bother me that much.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
It is still binding Once I had this problem while I was on call!
I have a thread about this, it was unusual for me too, theese random reboots.
After the third reinstall, (first one everyday rebooting, second one reinstall marshmallow, upgrade to nougat, happened the same reboots, I made again a factory reset and now no reboots and way better battery life) everything is ok for now.
hekermeker said:
I have a thread about this, it was unusual for me too, theese random reboots.
After the third reinstall, (first one everyday rebooting, second one reinstall marshmallow, upgrade to nougat, happened the same reboots, I made again a factory reset and now no reboots and way better battery life) everything is ok for now.
Click to expand...
Click to collapse
Thank you for your reply I received the update in OTA. To reinstall I have to go through Odin? I can not simply reinstall the current firmware (Nougat) via Smart Swith for PC?
I have the same issue guys even if did an hard reset after nougat update. I experienced some reboots after the update (1 March) but very often in these last days. I enabled the pin code for the sim in this way we can see if it happens when don't "monitor" the phone.
I was getting random reboots at one point due to a kernel panic (something to do with Samsung's zswap implementation). It hasn't been happening for a while though. I think they probably fixed it in newer versions. I'm on DQCF currently.
rikiko1g said:
I have the same issue guys even if did an hard reset after nougat update. I experienced some reboots after the update (1 March) but very often in these last days. I enabled the pin code for the sim in this way we can see if it happens when don't "monitor" the phone.
Click to expand...
Click to collapse
I think this is a software bug. Hopefully Samsung will quickly realize and deploy a corrective update. For my part, I reported this problem by sending an error report via the application "Samsung Members".
CurtisMJ said:
I was getting random reboots at one point due to a kernel panic (something to do with Samsung's zswap implementation). It hasn't been happening for a while though. I think they probably fixed it in newer versions. I'm on DQCF currently.
Click to expand...
Click to collapse
I'm on DQBO, this may be why I still have this problem. Did you directly receive Android Nougant in DQCF or was it a patch update?
GeekTN said:
I'm on DQBO, this may be why I still have this problem. Did you directly receive Android Nougant in DQCF or was it a patch update?
Click to expand...
Click to collapse
Flashed full image from SamMobile and setup from scratch. I'm too impatient to wait for patches
having random freeze / reboot on a g930fd (dual sim) as well , since a few weeks
flashed several times, factory reseted several times, root or no-root ....
no solution ...
basile said:
having random freeze / reboot on a g930fd (dual sim) as well , since a few weeks
flashed several times, factory reseted several times, root or no-root ....
no solution ...
Click to expand...
Click to collapse
This may be a software bug. What is your firmware version?
build NRD90M G930FXXU1DQB7 is the latest rom
with the latest samsung security update
meanwhile I left root aside, as I noted a strange thing while working under twrp that being 'unable to mount' /data map
problem occurs after filling up the memory (yes a 32gb version) and making more and more apps working (under root)
so, considering the above, might it be a physical ram problem ?
reading searching the net I noticed that many people are having this problem
basile said:
build NRD90M G930FXXU1DQB7 is the latest rom
with the latest samsung security update
meanwhile I left root aside, as I noted a strange thing while working under twrp that being 'unable to mount' /data map
problem occurs after filling up the memory (yes a 32gb version) and making more and more apps working (under root)
so, considering the above, might it be a physical ram problem ?
reading searching the net I noticed that many people are having this problem
Click to expand...
Click to collapse
No, I do not think that's what caused the problem. If the problem appeared after the Andoid Nougat update, it is that it is a software bug. I have a Galaxy S7 duos (SM-G930FD) me too and my firmware version is the G930FXXU1DQBO and I also have a problem of random restarts that persists even after a factory reset. Apperently the latest firmwares do not have this problem. It is necessary to wait for the next corrective update. Otherwise, what is the frequency of the random reboots of your phone? My phone is once a week.
there is no linearity ... can happen once a day, a week or several times in one day
sometimes it completely gets stuck and I have to wait for the battery to fully discharge before being able to reboot to a working phone ...
basile said:
there is no linearity ... can happen once a day, a week or several times in one day
sometimes it completely gets stuck and I have to wait for the battery to fully discharge before being able to reboot to a working phone ...
Click to expand...
Click to collapse
Have you tried restarting your phone in secure mode to see if the problem is from an application that you have installed?
Same here, I though that was Fleksy that sometimes load the phone and I had to shut it down manually (Power button + volume - for 7 sec) for a restart. Sometimes it restart itself.
Very frustrating, I'm on G930FXXU1DQB1 (German model), and when i search for update it says "up to date : DQB3 / DQA8 / DQB1."
Irritating as well !
Greg2Lu said:
Same here, I though that was Fleksy that sometimes load the phone and I had to shut it down manually (Power button + volume - for 7 sec) for a restart. Sometimes it restart itself.
Very frustrating, I'm on G930FXXU1DQB1 (German model), and when i search for update it says "up to date : DQB3 / DQA8 / DQB1."
Irritating as well !
Click to expand...
Click to collapse
This problem of random reboots often happens to your phone? What is the frequency of these restarts?