hi is few weeks now that i have daily random reboots whit my nexus 5,i tried a factory reset but nothing changed..it seems that there is an app that is going in conflict but no error log appear..is there a way to find the cause?? i think that after the factory reset it isnt solved bcs i restored the data backup that i made before it..
paxanto said:
hi is few weeks now that i have daily random reboots whit my nexus 5,i tried a factory reset but nothing changed..it seems that there is an app that is going in conflict but no error log appear..is there a way to find the cause?? i think that after the factory reset it isnt solved bcs i restored the data backup that i made before it..
Click to expand...
Click to collapse
Are u using a kernel with custom values like UV? You can use a logcat from your PC to identify the cause of your RRs.
Primokorn said:
Are u using a kernel with custom values like UV? You can use a logcat from your PC to identify the cause of your RRs.
Click to expand...
Click to collapse
im using the stock kernet whit the carbon rom,but now i've changed the baseband since i saw that i had the most issued version,let's see if it solve.
ill do a logcat if not solved
paxanto said:
im using the stock kernet whit the carbon rom,but now i've changed the baseband since i saw that i had the most issued version,let's see if it solve.
ill do a logcat if not solved
Click to expand...
Click to collapse
If it ain't solved yet here's this, I had the same issue when mid way throughout anything it would randomly reboot at random times. I found the cause and it was the cpu govner. I changed it from the govner I set it too long ago (on demand) and changed it to interactive and change the clock values back to default. That's what fixed my random reboots.
darkjake said:
If it ain't solved yet here's this, I had the same issue when mid way throughout anything it would randomly reboot at random times. I found the cause and it was the cpu govner. I changed it from the govner I set it too long ago (on demand) and changed it to interactive and change the clock values back to default. That's what fixed my random reboots.
Click to expand...
Click to collapse
for the moment i solved changing the kernel..no more reboots.
darkjake said:
If it ain't solved yet here's this, I had the same issue when mid way throughout anything it would randomly reboot at random times. I found the cause and it was the cpu govner. I changed it from the govner I set it too long ago (on demand) and changed it to interactive and change the clock values back to default. That's what fixed my random reboots.
Click to expand...
Click to collapse
cheers, i well try this. the problem has been giving me grief since 4.4.3 came out in June
Related
So I am running into the problem that my phone wont boot up if I turn my phone off, or it dies.
The only way around to getting it back on is getting CWM up and doing a "cache wipe".
The symptoms I am having when I try to turn it on is I do not get past the LG logo. The soft keys are lit and the screen back light comes on and off (black screen) with a 2-3 second intervals forever (have not went past 10min).
I am running xboards tweaked 2.3.3 with fauxes stock volt kernel, any more into?
Thanks guys.
No one? Really?..
Sounds like an errant app is causing you problems. Once you boot start uninstalling apps one at a time that you think are the culprit and try rebooting. Do this until your phone can boot again and then you'll have a good idea of the problem app.
Paul Nur said:
No one? Really?..
Click to expand...
Click to collapse
The only thing I can think of is maybe an issue with the custom kernel. Do you remember having the issue before you flashed Faux's kernel?
jboxer said:
Sounds like an errant app is causing you problems. Once you boot start uninstalling apps one at a time that you think are the culprit and try rebooting. Do this until your phone can boot again and then you'll have a good idea of the problem app.
Click to expand...
Click to collapse
.. and that. lol
jboxer said:
Sounds like an errant app is causing you problems. Once you boot start uninstalling apps one at a time that you think are the culprit and try rebooting. Do this until your phone can boot again and then you'll have a good idea of the problem app.
Click to expand...
Click to collapse
I installed fauxes OC (over clock), and its working fine now, I was having problems with SV (stock voltage), maybe that was the culprate?
P.S. After restarting my phone (I have been doing it every so often to test for stability) my home screen got reset to factory? I had all my apps and everything, it was just factory..??? Only happened once tho.
phburks said:
The only thing I can think of is maybe an issue with the custom kernel. Do you remember having the issue before you flashed Faux's kernel?
Click to expand...
Click to collapse
^^^^^^^^^^
Currebtly, I'm on AOSPA ROM.. After every reboot, the time and date reset to 1970. Any way to fix this?
use automatic date and time
Choose automatic date and time settings.
settings>>date and time>> automatic date and time
sladeslayer said:
Currebtly, I'm on AOSPA ROM.. After every reboot, the time and date reset to 1970. Any way to fix this?
Click to expand...
Click to collapse
Hit the thanks button if it helped!
srchared said:
Choose automatic date and time settings.
settings>>date and time>> automatic date and time
Hit the thanks button if it helped!
Click to expand...
Click to collapse
If that had worked, I wouldn't have posted here. :/
srchared said:
Choose automatic date and time settings.
settings>>date and time>> automatic date and time
Hit the thanks button if it helped!
Click to expand...
Click to collapse
It doesnt work :|
Sent from my C2105 using xda app-developers app
You have your SIM card in your phone?
If you have a SIM, then you should have it working.
Sena Ferdy said:
It doesnt work :|
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
sladeslayer said:
If that had worked, I wouldn't have posted here. :/
Click to expand...
Click to collapse
srchared said:
You have your SIM card in your phone?
If you have a SIM, then you should have it working.
Click to expand...
Click to collapse
It isn't working. That is why I had posted -_-.
Anyone else knows a fix for this ?
Not working on mine either.
Anyone knows how to see any log about this?
Enable automatic time and date and disable automatic time zone mine solved
Sent from my C2105 using Tapatalk
Hi, I have the same problem. It started after I flashed Thunderzap kernel. I've tried even Phantom kernel and it does the same. With stock kernel is everything about time ok, with Phoenix kernel was time after restart correct too. ROM was always stock .14
Disabling automatic time zone didn't helped..
Kosa02 said:
Hi, I have the same problem. It started after I flashed Thunderzap kernel. I've tried even Phantom kernel and it does the same. With stock kernel is everything about time ok, with Phoenix kernel was time after restart correct too. ROM was always stock .14
Disabling automatic time zone didn't helped..
Click to expand...
Click to collapse
See from this post to the end, me and @R.A.B discussed a bit about this problem, and he found a solution that not the kernel downgrade
DsvCdsSoftware said:
See from this post to the end, me and @R.A.B discussed a bit about this problem, and he found a solution that not the kernel downgrade
Click to expand...
Click to collapse
Kosa02 said:
Hi, I have the same problem. It started after I flashed Thunderzap kernel. I've tried even Phantom kernel and it does the same. With stock kernel is everything about time ok, with Phoenix kernel was time after restart correct too. ROM was always stock .14
Disabling automatic time zone didn't helped..
Click to expand...
Click to collapse
Amr5121 said:
Enable automatic time and date and disable automatic time zone mine solved
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
sladeslayer said:
Currebtly, I'm on AOSPA ROM.. After every reboot, the time and date reset to 1970. Any way to fix this?
Click to expand...
Click to collapse
Did you tried reflashing ftf ?/ I had faced this issue once but it got solved after reflashing fw.
Yes, I did and not just once. Right now I'm trying Omni (4.4.2) with Thunderzap and time is ok. It has to be mistake of stock ROM.
my problem is back again i know if i flash ftf again problem will solve( tried it once ) !but i don't want to flash my phone for this problem
meanwhile this time my time and date reset to 2009/01/02
running on dextroid
phantom ver7
Amr5121 said:
my problem is back again i know if i flash ftf again problem will solve( tried it once ) !but i don't want to flash my phone for this problem
meanwhile this time my time and date reset to 2009/01/02
running on dextroid
phantom ver7
Click to expand...
Click to collapse
The question is: (using Phantom as example cause I use it on my phone)
When I first installed the v7 of kernel, my time is OK. Because one of the freezes on my phone, I needed to pull out my battery. After this the problem occurred. Some time after, the time problems was solved by itself, but just for some time. Two or three reboots before the problem shows up again...
I don't know why, but I looked on logcat but no clue about a solution :crying:
Flash FTF again for the problem shows up again, its a lot of unnecessary work....
Due to freezes on last version, using v4.5 rocks. Waiting for a new version, cause @Shivam Kuchhal asked for some tester and I applied to testing it.
DsvCdsSoftware said:
The question is: (using Phantom as example cause I use it on my phone)
When I first installed the v7 of kernel, my time is OK. Because one of the freezes on my phone, I needed to pull out my battery. After this the problem occurred. Some time after, the time problems was solved by itself, but just for some time. Two or three reboots before the problem shows up again...
Click to expand...
Click to collapse
That's true. My phone for the first time with Phantom kernel was fine about time. Than I reflashed it and than it started. I think that it started after i installed kernels modules. Coz for the first time i didn't knew that it is important..
I am annoyed by this random reboot issue still being unsolved.
Please if someone can help with troubleshooting the errors in last_kmsg:
"unable to handle the NULL pointer dereference at virtual address...... "
"unable to handle the paging request at virtual address........"
I am not an expert but I have read on the Internet about Linux kernel "oops" leading to kernel panic and reboot.
Can anyone build a fix for the Android kernel to handle these oops errors and not panic? Or can anybody read these last_kmsg files and tell me what is causing this?
last_kmsg files attached.
im going to check them out shortly, but kernel panics can be caused by just about anything. even a simple derp, will lead to a kernel panic, which will lead to a reboot.
---------- Post added at 07:04 PM ---------- Previous post was at 06:55 PM ----------
Zaeem Adil said:
I am annoyed by this random reboot issue still being unsolved.
Please if someone can help with troubleshooting the errors in last_kmsg:
"unable to handle the NULL pointer dereference at virtual address...... "
"unable to handle the paging request at virtual address........"
I am not an expert but I have read on the Internet about Linux kernel "oops" leading to kernel panic and reboot.
Can anyone build a fix for the Android kernel to handle these oops errors and not panic? Or can anybody read these last_kmsg files and tell me what is causing this?
last_kmsg files attached.
Click to expand...
Click to collapse
if youre using avast security software, i think its causing it, or is playing a role in it. but thats my guess, not 100%.
simms22 said:
im going to check them out shortly, but kernel panics can be caused by just about anything. even a simple derp, will lead to a kernel panic, which will lead to a reboot.
---------- Post added at 07:04 PM ---------- Previous post was at 06:55 PM ----------
if youre using avast security software, i think its causing it, or is playing a role in it. but thats my guess, not 100%.
Click to expand...
Click to collapse
Thanks
I am currently using avast but these kernel_panics occur without any 3rd party app installed at all.
are you completely stock? the kernel panics occur not because of the kernel, it just reacts to the oops. anything, including rim, apps, data flow, your router, etc can cause them. sounds like you get them often, which you shouldnt. if rarely, then id say it was normal, but often isnt normal.
oh, i said avast because it shows up twice, right before stuff goes wrong.
simms22 said:
are you completely stock? the kernel panics occur not because of the kernel, it just reacts to the oops. anything, including rim, apps, data flow, your router, etc can cause them. sounds like you get them often, which you shouldnt. if rarely, then id say it was normal, but often isnt normal.
oh, i said avast because it shows up twice, right before stuff goes wrong.
Click to expand...
Click to collapse
Yes I am completely stock and yes I get reboots very often. Please guide me how to get to the actual culprit which is causing this. I have uninstalled avast.
I got 3 reboots in last 5 minutes here are the logs.
Zaeem Adil said:
I got 3 reboots in last 5 minutes here are the logs.
Click to expand...
Click to collapse
Flash some other kernel. If it doesnt work its either rom or hardware related
lolerpro8 said:
Flash some other kernel. If it doesnt work its either rom or hardware related
Click to expand...
Click to collapse
I have used Franco kernel on stock 4.4.4 and I even tried CM11 the problem persisted in both situations. Suggest me some better kernel I'll try it.
try without any custom kernel, stock kernel.. problem persists? go get an RMA, its not supposed to be happening. actually, i have never seen so many wdog bites!
Zaeem Adil said:
I have used Franco kernel on stock 4.4.4 and I even tried CM11 the problem persisted in both situations. Suggest me some better kernel I'll try it.
Click to expand...
Click to collapse
Flash factory images. If it doesn't work its hardware related
lolerpro8 said:
Flash factory images. If it doesn't work its hardware related
Click to expand...
Click to collapse
this. if still happening, go get it exchanged.
lolerpro8 said:
Flash factory images. If it doesn't work its hardware related
Click to expand...
Click to collapse
I flashed factory images and the issue is still there. There is an app named stability test on play store it runs several stress tests on the cpu at different frequencies and also on the ram. I ran it and during the tests the device temp got up to 45 degrees and even after 50 successfull cpu runs on all the 4 cores and 500 successful ram runs the device didn't reboot. If it is hardware related why does it pass the stress test over n over again? One thing more, the device reboots most of the time when it is connected to internet through wifi or mobile data. I am doubtful that it is something related to the modem drivers. I found stock flashable radio images n i flashed them but the problem is still there.
Zaeem Adil said:
I flashed factory images and the issue is still there. There is an app named stability test on play store it runs several stress tests on the cpu at different frequencies and also on the ram. I ran it and during the tests the device temp got up to 45 degrees and even after 50 successfull cpu runs on all the 4 cores and 500 successful ram runs the device didn't reboot. If it is hardware related why does it pass the stress test over n over again? One thing more, the device reboots most of the time when it is connected to internet through wifi or mobile data. I am doubtful that it is something related to the modem drivers. I found stock flashable radio images n i flashed them but the problem is still there.
Click to expand...
Click to collapse
When you talk about hardware problems you can only speculate. There is most likely cpu related. If it was software related, flashing other fitmware would fix the problem. Since it doesn't the only answer is hardware
https://www.dropbox.com/s/j7o39s38anhc7cy/2014-08-17_08.13.zip
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hey guys,
ive tried different roms (stock cm11s, mahdi, droidkang) with different kernels (stock, franco, ak).
I have completely wiped my device and set up everything new.
Still im getting reboots every now and then.
Mostly it happens to me while im surfing with chrome, but it also happened in the gallery, while watching movies and so on. Never had a problem while gaming.
Last_ksmg always says "kernel panic", followed by "failed to stop secondary cpus".
Please see the linked last_ksmg files.
https://dl.dropboxusercontent.com/u/16054199/last_kmsg6
https://dl.dropboxusercontent.com/u/16054199/last_kmsg7
Any help is highly appriciated, im getting really frustrated...
Are you using any kernel apps? What other apps are you using? Are you running Xposed?
The only app worth mentioning is lightflow, and i have changed dpi to 380 with texdroider.
thanks fir your reply
soulcrash said:
The only app worth mentioning is lightflow, and i have changed dpi to 380 with texdroider.
thanks fir your reply
Click to expand...
Click to collapse
Try reflashing everything through fastboot. Each individual partition, just to make sure everything is clear and wiped.
soulcrash said:
The only app worth mentioning is lightflow, and i have changed dpi to 380 with texdroider.
thanks fir your reply
Click to expand...
Click to collapse
I was having reboot issues will using both DPI changer and textdroider from the playstore. I would suggest getting rid of textdroider DPI and instead manually change it. Go into your file manger then system/build prop and look for LCD.density. It fixed my rebooting issues running Jedi Open Source rom.
Sent from my Oneplus one using XDA Free mobile app
Hey guys,
i have fastboot flashed the stock images of 25r, 33r and 38r, and even without installing one single app or changing any system settings, i get reboots.
Any ideas left, or is my hardware defect?
soulcrash said:
Hey guys,
i have fastboot flashed the stock images of 25r, 33r and 38r, and even without installing one single app or changing any system settings, i get reboots.
Any ideas left, or is my hardware defect?
Click to expand...
Click to collapse
Reboots are usually on the software level, but 38R actually had reboot problems. Best if you installed a custom kernel and tweaked it yourself, say AK.
Well, i have tried almost every possible rom-kernel-modem combination, including stock images with fastboot. I dont know where this could be a software problem...
soulcrash said:
Well, i have tried almost every possible rom-kernel-modem combination, including stock images with fastboot. I dont know where this could be a software problem...
Click to expand...
Click to collapse
Yes, but I and a couple of friends get those reboots too. It's a common problem, not easily diagnosed. If your last_kmsg gets written to, it's saying that a configuration has crashed and the software itself is requesting a forced reboot.
If the last_kmsg has nothing inside then it's obviously a hardware issue.
Sent from my OnePlus One using Tapatalk VIP
Hmmmm...
You say i should set up the ak kernel until it works on my device ... I have no clue what all these detailed settings, apart from mhz and voltage mean - can u recommend some "safe" settings for me?
soulcrash said:
Hmmmm...
You say i should set up the ak kernel until it works on my device ... I have no clue what all these detailed settings, apart from mhz and voltage mean - can u recommend some "safe" settings for me?
Click to expand...
Click to collapse
After you install ak, install UKM (flashable zip in recovery) and then install Synapse from the Play Store. Then go into Synapse and swipe the drawers to see these options.
CPU:
Set a safe non overclocking frequency
Governor: slim
Hotplug: CPU Boost by CyanogenMod
GPU Governor: msm-adreno-tz
Memory: Drop Caches Enabled
USB Fast Charge Disabled
Log Creation disabled.
Thanks for your help man, i still get reboots, im back at my nexus5 and wait if someone from the opo support answers me ... Frustrating.
have you the problem on all ROms after updating to R38? Some ppl are reporting that after R38 Update even other ROm Versions does the Random Reboot Bug....
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
I have the same problem with craching and rebooting on both Tab2`s in the house.
One completly stock and one with CM11.
Mabye an faulty app ?
Steveh8204 said:
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
Click to expand...
Click to collapse
Well, it is happening with everyone, the apps have become memory hungry and our devices lack RAM, andoid L, and our device kernel is full of bloatwares, our devs are trying very hard to overcome this, and we hope they will succeed in this too.
many people are of the view that android M has better management of ram, and I have seen in other devices that have confirmed they are experiencing better stability than lollipop. well on our device it's still in alpha stage, so wait and watch. till then keep your tab less burdened.
Steveh8204 said:
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
Click to expand...
Click to collapse
Try changing SElinux to enforcing.
It helped me in my P3110.
HIT THE THANKS BUTTON IF I HELPED YOU
Zte blade l said:
Try changing SElinux to enforcing.
It helped me in my P3110.
HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Hi, thanks for the reply but how the hell do you do that lol
Sent from my GT-P5110 using Tapatalk
Steveh8204 said:
Hi, thanks for the reply but how the hell do you do that lol
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
No need for that, just follow the original thread, bugs have been squashed. There are no more random reboots on latest builds.