I have tried countless roms from 44s, cm11, slimbean and even the new lollipop builds.
They all have random reboot problems. 44s by far is the worst.
Here is a log cat from mahdi 2.9 fresh install :
http://pastebin.com/aAiGh2An
rebooted an hour later
What do i look for in these logcats to determine the culprit?
Unless you're running a catlog with adb while the device actually reboots you're not going to find anything. You're better off looking at the last_kmsg.
Transmitted via Bacon
Last kmsg or dmsg would be better.
Related
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Have you tried deleting the telephone system app?
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Free gift from Grimlock. It's the kernel that restarts 3 times before fully booting, right? As soon as I took it off my system, the problem vanished. Comes with the package. You like Grimlock, must learn to live with it. I don't like it That much.
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Updates have come that fix that problem. Same with Geass, if it's not fixed yet it will be VERY soon.
graphdarnell said:
Free gift from Grimlock. It's the kernel that restarts 3 times before fully booting, right? As soon as I took it off my system, the problem vanished. Comes with the package. You like Grimlock, must learn to live with it. I don't like it That much.
Click to expand...
Click to collapse
Or you could file bug reports with the devs, and guess what? They found the problem and fixed it! Instead of slagging people who are trying to improve our tablets, you could help them by letting them know about the issues you have.
The "free gift" is the kernel that's posted for a community. If you don't like it and don't want to help, and would rather tell others bad things about it, then take your nonsense somewhere else.
hardslog said:
Updates have come that fix that problem. Same with Geass, if it's not fixed yet it will be VERY soon.
Or you could file bug reports with the devs, and guess what? They found the problem and fixed it! Instead of slagging people who are trying to improve our tablets, you could help them by letting them know about the issues you have.
The "free gift" is the kernel that's posted for a community. If you don't like it and don't want to help, and would rather tell others bad things about it, then take your nonsense somewhere else.
Click to expand...
Click to collapse
I upgraded to the latest TWRP 2.7.0.1, deleted everything and started from scratch. Everything works great now and using new kernel that clocks to 1.8 is flying.
Seems I inadvertently killed my working CM11 opo with 9/30 Nightly
Factory Reset and wiped all data via twrp 2.8.0.1
Installed Nightly, Gapps, Gapps remover, franco r22 and cm11s app pack via USB-OTG
wiped dalvik/cache
reboot to "Unfortunately, the process android systemui has stopped working" > hit ok > infinite repeat
tried to revert to 9/25 and even the M9 snapshot to the same issue
I have a nandroid of when i first got the phone with cm11s on it but no efs backup.
I was using franco r20-updated to r21 just yesterday, Nightly 9/25 just fine with a few issues with certain apps. Figured waiting for a few more days in between nightlies would help with those issues.
Anyone got any suggestions as to what I can do to resolve this? Out of a phone at the moment so in a tough spot.
Factory wipe. Only flash CM11 nightly, flash each zip one by one. One of them is causing your phone to constantly fc.
Seems issue in last CM nightly 0930... Flash 0928 and wait for fix. Affected more (maybe all) devices.
Happened to mine as well. Though I still can't use the cm boot.img past 9/19 either lol
I flashed back 29 nightly and all works fine.
Same issue for me updating to the 09/30 nightly!
@zephiK 9/29 is offline apparently lol
9/28 seems to work (with no other zips done including gapps)
Samsung GS3 - Pulled battery to get control - boot to TWRP and installed 9/28 nightly. All is well. :good:
S5 30/09 can confirm SystemUI crash. On 28/9 atm and fully works.
Autobuilder placed bad commit and built it for all devices.
Good afternoon gents!
This is the first time I post on this forum so I apologize in advance if I am not going to provide all the details regarding my problem. I'll try to be as explicit I can with my issue.
A couple of weeks ago I bought a LG Nexus 5, second hand. After one day of use the device started to randomly reboot. The odd thing is that the reboots seem to be "soft". After the device restarts there is no data loss, even the recent apps are still there. The reboots are as random as I can get, when browsing with Chrome, checking emails, or playing a game.
I tried several fixes, including costum kernels, costum ROMs and so. The problem persisted with the official KitKat 4.4.4 and Lollipop 5.0, 5.0.1 and 5.1.
Currently I am running stock Lollipop 5.1 with stock kernel and TWRP 2.8.5.2 recovery and the device is rooted.
Below I attached a screenshot with the device's current configuration and a text file with the kmsg log from the last reboot.
Faulty power button.
Reboot phone into bootloader/fastboot.
If it random reboots in the bootloader too, it's likely the power button.
Nope, I already tested this. The device reboots during use, either heavy or simply browsing the menu.
Sent from my Nexus 5 using XDA Free mobile app
I noticed this in your Log
"<6>[ 0.514020] [email protected]: Power-off reason: Triggered from UVLO (Under Voltage Lock Out)"
Just curious, Are you undervolting?
I don't know exactly what undevolting implies. Could you give me more details please?
vektor1993 said:
I don't know exactly what undevolting implies. Could you give me more details please?
Click to expand...
Click to collapse
Lowering the voltage the CPU runs at, at certain frequencies.
I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?
vektor1993 said:
I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?
Click to expand...
Click to collapse
Try posting another log if it happens again.
I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.
vektor1993 said:
I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.
Click to expand...
Click to collapse
This log shows a kernel panic.
My n5 reboot today without any reason
That was the only thing I understood from the log too. Do you have any idea what's the reason for these kernel panics and a possible way to fix them?
I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance
vektor1993 said:
I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance
Click to expand...
Click to collapse
Same problem as this guy
http://forum.xda-developers.com/showpost.php?p=59551481&postcount=8615
having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.
Good day lads!
I tried since the last post more possible fixes, and the only thing that showed some resuslt was downgrading to 4.4 bu the device still resarts exactly once a day. I am going to switch to another phone.
having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.
Click to expand...
Click to collapse
If you just recieved a new device and you have the possibility to RMA it, I suggest doing it. I went as far as page 30 on google searching possbile fixes and came up with no valid result.
I decided a few days ago to downgrade my phone from 5.1 version of android to CM12. Did so successfully by flashing 5.0 bootloader and radio, then CM12. As soon as it booted I noticed the processor or battery mode is stuck on power saver and will not switch. Yesterday I updated to the new 12.1 nightly and still same problem. Would like to be able to toggle to balanced or performance. Is this a known problem or does something cause the bug?
Clean flash. If it still happens then it may be a ROM/kernel issue, or just user error.
Clean installed, went as far as formatting /system. Problem still persists. What can I do to report this bug?
KentuckyGuy447 said:
Clean installed, went as far as formatting /system. Problem still persists. What can I do to report this bug?
Click to expand...
Click to collapse
No point formatting /system since it does that in the flash script anyways.
Report it in the CM bug tracker if you are certain it doesn't work. I recall others having the same issue previously, maybe they just haven't fixed their profiles yet.
I got my OPO a week back, unlocked bootloader, installed TWRP and flashed OxygenOS right out of the box. I have been getting pretty good battery life for my needs except a problem. The phone randomly hot reboots. It may be while I am using it or maybe while it is lying in my pocket. No significant increase in temperature was noticed. I have attached the last_kmsg for the phone to this post. Can someone please help me in finding out what's up with my phone ?
abesh said:
I got my OPO a week back, unlocked bootloader, installed TWRP and flashed OxygenOS right out of the box. I have been getting pretty good battery life for my needs except a problem. The phone randomly hot reboots. It may be while I am using it or maybe while it is lying in my pocket. No significant increase in temperature was noticed. I have attached the last_kmsg for the phone to this post. Can someone please help me in finding out what's up with my phone ?
Click to expand...
Click to collapse
Just to say "me too", but only with OxygenOS. I never had random reboots with any CM variants (including the latest 12.1 nightlies), just with OxygenOS.
I'll save my last_,kmsg next time it happens and compare with yours.
mijkz said:
Just to say "me too", but only with OxygenOS. I never had random reboots with any CM variants (including the latest 12.1 nightlies), just with OxygenOS.
I'll save my last_,kmsg next time it happens and compare with yours.
Click to expand...
Click to collapse
@mijkz thanks for chiming in I am relieved to see that I am not the only one. I have never been on any of the CM roms. Flashed OXOS right out of the box. Clean install. I have a niggling doubt though that this might be hardware related, specifically the internal memory (after seeing the last_kmsg logs)
mijkz said:
Just to say "me too", but only with OxygenOS. I never had random reboots with any CM variants (including the latest 12.1 nightlies), just with OxygenOS.
I'll save my last_,kmsg next time it happens and compare with yours.
Click to expand...
Click to collapse
If it helps, you can find your old last_kmsg logs in the following folder : /data/system/dropbox.
They should be in the following format : [email protected]
abesh said:
If it helps, you can find your old last_kmsg logs in the following folder : /data/system/dropbox.
They should be in the following format : [email protected]
Click to expand...
Click to collapse
Great, thanks