Like the title says, on every 5.1 ROM I keep getting random reboots. They happen indiscriminately, with no clear reason at all. Other people report no issues at all. On 5.0.2 I have no issues at all. I have no idea what causes it could be or no knowledge on how to diagnose it...I want to use 5.1, but if this keeps happening I don't think I can ?.
I've not had any issues with random reboots, been running euphoria rom (updating with each new build) and glitch kernel for weeks with no issues.
Assuming you're doing clean flashes, with no extra mods, and not restoring system data, yes? Its even possible that restoring app data from backups can cause weird things to occur at times. If you haven't yet, wipe everything and clean flash, restore apps only from play store, and see if it still happens.
Otherwise, maybe a specific app is causing problems? You could try and grab some logs to narrow down the cause, but I know that's very tough to do if the issue is intermittent and seemingly random. Still it is the only way to tell for sure what's happening.
Here's a guide on how to grab the different logs if that helps at all: http://forum.xda-developers.com/showthread.php?t=1520508 .
LucentBirch said:
Like the title says, on every 5.1 ROM I keep getting random reboots. They happen indiscriminately, with no clear reason at all. Other people report no issues at all. On 5.0.2 I have no issues at all. I have no idea what causes it could be or no knowledge on how to diagnose it...I want to use 5.1, but if this keeps happening I don't think I can ?.
Click to expand...
Click to collapse
The random reboots are caused by outdated 5.0.2 binaries, if you update to 5.1 it should mend it random reboots. Also if your ROM developer might or will update the ROM to 5.1 with the updated binaries!
Killah1994 said:
The random reboots are caused by outdated 5.0.2 binaries, if you update to 5.1 it should mend it random reboots. Also if your ROM developer might or will update the ROM to 5.1 with the updated binaries!
Click to expand...
Click to collapse
Well I know for a while that some 5.1 roms were using the 5. 0. 2 binaries because the 5.1 weren't released yet... And they never really said whether or not they updated the binaries or if they were even released...I updated my tablet to a 5.1 R_5 this morning and it hasn't rebooted all day...so maybe they have?
LucentBirch said:
Well I know for a while that some 5.1 roms were using the 5. 0. 2 binaries because the 5.1 weren't released yet... And they never really said whether or not they updated the binaries or if they were even released...I updated my tablet to a 5.1 R_5 this morning and it hasn't rebooted all day...so maybe they have?
Click to expand...
Click to collapse
5.1 binaries and factory image for this device were just rolled out today. This may indeed resolve your issues, but give the custom rom devs some time to catch up, they'll need to grab the latest source and post new builds for the latest binaries to be included.
Same thing here
I excitedly loaded up the 5.1 build on my 2013 wireless today. SAME ISSUE. I can't do anything .
I didn't wipe the device when I upgraded. I was rooted - unrooted / flashed / rooted using the Nexus Root Tooklit as I have since Jelly Bean. I used the option to use NO WIPE MODE to try and keep my apps intact.
Any help appreciated.
mrdrumsc said:
I excitedly loaded up the 5.1 build on my 2013 wireless today. SAME ISSUE. I can't do anything .
I didn't wipe the device when I upgraded. I was rooted - unrooted / flashed / rooted using the Nexus Root Tooklit as I have since Jelly Bean. I used the option to use NO WIPE MODE to try and keep my apps intact.
Any help appreciated.
Click to expand...
Click to collapse
in that case you should try wiping then flash the 5.1 factory image and see if it works.
PrizmaticSmoke said:
5.1 binaries and factory image for this device were just rolled out today. This may indeed resolve your issues, but give the custom rom devs some time to catch up, they'll need to grab the latest source and post new builds for the latest binaries to be included.
Click to expand...
Click to collapse
cm12.1. rebooted once today while using chrome.
Reboots better!
I concur with the messages I've been seeing. After several app updates over the weekend, culminating in some Chrome updates, the tablet seems stable. I haven't re-rooted it yet.
I wonder if something has to do with the "notification crash" error listed in the changelog for 5.1.1.
Either way, looking forward to 5.1.1!
Related
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.
As the title states, the camera on my Nexus 5x is completely unusable. My bootloader is unlocked and I'm running MHC19J. This issues happens on MHC19J and on Android N 90% of the time. When it does work, both cameras works fine. I'm am currently on MHC19J with no applications installed and the phone crashed and rebooted. After the reboot the camera works but I have no confidence it's going to stay this way. I have noticed another user on this has the same (or at least similar issue) which was caused by ditry-flashing MHC19J however, I have flashed the factory image from Google.
This issue started a few days ago. I think the issue started after flashing elementalX (eas preview version) on a stock rooted MHC19J.
If you think it's related to the kernel grab logs and post them in the kernel thread since you clean flashed to begin with. I'm sure flar would like to see them if it is the cause. I'm using the same kernel on Omni without that issue.
You can also return to stock (and potentially to a different version) completely and see if it occurs again.
Keithn said:
If you think it's related to the kernel grab logs and post them in the kernel thread since you clean flashed to begin with. I'm sure flar would like to see them if it is the cause. I'm using the same kernel on Omni without that issue.
You can also return to stock (and potentially to a different version) completely and see if it occurs again.
Click to expand...
Click to collapse
Thank you for the reply. I cannot get the logs becuase I have since flashed many different factory images. However, even on completely stock, the issue still occurs.
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Oyongx said:
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Click to expand...
Click to collapse
I'd try using the latest wild kernel.
g0at1 said:
I'd try using the latest wild kernel.
Click to expand...
Click to collapse
well i think i did try wild kernel with cm12.1 latest nightlies. The issue gotten worse. More random reboot occured.
Currently on slimLP with his zerkernel v1.7. I thought this one is perfect, but then out of nowhere the random reboot occured again. It's not as frequent as before but still happen.
Right now I'm using Mokee with wild kernel and everything is going well.
Oyongx said:
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Click to expand...
Click to collapse
Random rebooting is a common issue with all the cm 12.1 based ROM for lg ogp. The cm12. 1 in my opinion was never fully stabilized even by the time the devs were starting to switched to the newer hardwares. If you keep the number of apps you unstated to minimum, you may be able to keep random rebooting down, but this just my observation. I thought the latest bliss pop 4.03 had the rebooting issues sloved, but it rather just had the occurrence down to where it's less. But there are other issues such as the device getting extremely hot, which in turn causes shutdown. To the point where I give up on using LP once again on this device, and move back to kk. The kk may be an older rom, but at least it's stable. With the LP, I think issues with it unable to find the sim card, GPU issues that cause screen to flicker and blackout, all are never fully fixed. Rather, those issues were patched and rigged to make the rom run, but not smooth enough where you see issues such as rebooting and overheating.
Sent from my LG-E980 using XDA-Developers mobile app
hawkwind212 said:
Random rebooting is a common issue with all the cm 12.1 based ROM for lg ogp. The cm12. 1 in my opinion was never fully stabilized even by the time the devs were starting to switched to the newer hardwares. If you keep the number of apps you unstated to minimum, you may be able to keep random rebooting down, but this just my observation. I thought the latest bliss pop 4.03 had the rebooting issues sloved, but it rather just had the occurrence down to where it's less. But there are other issues such as the device getting extremely hot, which in turn causes shutdown. To the point where I give up on using LP once again on this device, and move back to kk. The kk may be an older rom, but at least it's stable. With the LP, I think issues with it unable to find the sim card, GPU issues that cause screen to flicker and blackout, all are never fully fixed. Rather, those issues were patched and rigged to make the rom run, but not smooth enough where you see issues such as rebooting and overheating.
Sent from my LG-E980 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, i think the issue are only on cyanogen based ROM. When i use the lolipop such as Super Mini V6.5 by henrypham91 and lgviet team, it's all good. Deep sleep normaly, no sound delay when game on 2D graphics, and all. But then again, it's noticeably slower if you compare against CM head to head. I really love CM or AOSP based rom because they are so fast.
g0at1 said:
Right now I'm using Mokee with wild kernel and everything is going well.
Click to expand...
Click to collapse
Never heard about Mokee. I'll look maybe and try that. Thanks Edit: it is an AOSP based rom! Might try that. Hopefully my phone survive lol
Oyongx said:
Never heard about Mokee. I'll look maybe and try that. Thanks Edit: it is an AOSP based rom! Might try that. Hopefully my phone survive lol
Click to expand...
Click to collapse
Mokee is a Chinese CM based rom.
g0at1 said:
Mokee is a Chinese CM based rom.
Click to expand...
Click to collapse
The download link seems invalid. I don't understand chinese but on the downlaod the url there's an error 404 written. :silly:
Oyongx said:
The download link seems invalid. I don't understand chinese but on the downlaod the url there's an error 404 written. :silly:
Click to expand...
Click to collapse
Their website has an English version. There should be a British flag on the upper right side. Then download their history zip which is a kind of final release.
Hi, minor issue but annoying. I sideloaded and uodated to the latest U firmware for Europe this morning. All went smoothly. Now I keep getting the android system update notification. Any way of fixing this?
Thanks in advance
nbhadusia said:
Hi, minor issue but annoying. I sideloaded and uodated to the latest U firmware for Europe this morning. All went smoothly. Now I keep getting the android system update notification. Any way of fixing this?
Thanks in advance
Click to expand...
Click to collapse
Theres is L and X ota too, perhaps it wants one of those?
That would be odd? I'm in the UK running the H build originally. From what I understood, the U build was for Europe.
Good point though. Is there anyone in the UK on the EE network that has let the phone update via the network push. If so, what build got pushed? Cheers
A quick update. I let it install (expecting it to fail). And it worked? Even though I was rooted and running elemental x kernel. I've more ended up on the V build. It gets stranger. I checked the kernel and it was now stock. I panicked thinking they may have locked the bootloader, so I rebooted to check and thankfully still locked. What was strange through is that after the last reboot, I was back on elemental kernel and rooted again?? The build was still V. Everything working fine... I'm just confused
Another update. I've rebooted a few times now to see if anything changes between different boots. Looks like I'm running stock V build evertime. Root and elemanntalx kernel lost which I'll flash later. I'm still surprised the OTA for the network push worked even though I was rooted running a custom kernal.
nbhadusia said:
Another update. I've rebooted a few times now to see if anything changes between different boots. Looks like I'm running stock V build evertime. Root and elemanntalx kernel lost which I'll flash later. I'm still surprised the OTA for the network push worked even though I was rooted running a custom kernal.
Click to expand...
Click to collapse
“Curiouser and curiouser!” Cried Google (they were so much surprised, that for the moment they quite forgot how to speak good Android).”
Hi,
Since I got the latest Oxygen OS update (I'm on Oxygen OS 9.0.4) . My Phone App has started crashing if I make a outgoing call or get one. First the Phone App crashes and then the system UI Crashes. The Phone was working fine till this update.
Thinking this is an issue with the Oneplus Oxygen OS update, i tried to move to Pixel Experience OS. The version I installed worked well but again when i did a OTA upgrade the same issues started recurring. There I also faced crashes if I used the camera app.
Frustrated I moved back to the Stock Rom.. But the Problem of the Calling app still exists. I"ve tried installing alternate diallers but its the same effect. I'm attaching my log file here : https://drive.google.com/file/d/1nLldKekVd_ZLWRghbPeJP94cdimQpsf6/view?usp=sharing
Can you guys help figure out whats happening ?
coolparth said:
Hi,
Since I got the latest Oxygen OS update (I'm on Oxygen OS 9.0.4) . My Phone App has started crashing if I make a outgoing call or get one. First the Phone App crashes and then the system UI Crashes. The Phone was working fine till this update.
Thinking this is an issue with the Oneplus Oxygen OS update, i tried to move to Pixel Experience OS. The version I installed worked well but again when i did a OTA upgrade the same issues started recurring. There I also faced crashes if I used the camera app.
Frustrated I moved back to the Stock Rom.. But the Problem of the Calling app still exists. I"ve tried installing alternate diallers but its the same effect. I'm attaching my log file here : https://drive.google.com/file/d/1nLldKekVd_ZLWRghbPeJP94cdimQpsf6/view?usp=sharing
Can you guys help figure out whats happening ?
Click to expand...
Click to collapse
try clean flash any beta version of oos , or use unbrick tool to restore all firmware to factory setting.
Hi
Would this be the unbrick tool ? https://www.google.com/amp/s/forum....5t-unbricking-tool-confirmation-t3733012/amp/
Seems like a very old version ?
Hello
I tried doing the clean flash to the latest Beta.. But still getting the crashes. Will try un bricking now.. However is there a chance its related to the hardware ?
coolparth said:
Hello
I tried doing the clean flash to the latest Beta.. But still getting the crashes. Will try un bricking now.. However is there a chance its related to the hardware ?
Click to expand...
Click to collapse
no, perhaps its related to software. are u using any mod or theming?
Hi,
Currently none. The phone was on Stock Oxygen till 3 odd months ago and was working fine. After one of the OTA Updates, this problem started happening. Since I could not find any consistent users reporting the same issue on Oxygen, I decided at that point to try using a different ROM and switched to Pixel experience. The phone worked ok for 2 weeks or so post that. Again after a new OTA came and I upgraded it started crashing again.
In the team time i saw another update to Oxygen had come so it thought i'd try going back to stock.. But not avail. Its still crashing.. Its only the Phone App that acts up. Everything else works fine. However the first time this issue came video playback was also freezing.
The logs that i have posted show these crashes but I dont have enough knowledge as yet to understand the reason.
After the above response to try clean flashing the latest Beta. But the issue persists..
Try see if the phone app is set as standard app for handling phone calls.
Hi
Tried that ..it is set as default.. The latest trial I did is cleanflashed an older version official ROM v5x of Oxygen OS... Problem is still the same..
Infact worse.. now I've got the settings app crashing and random reboots in addition to the phone app crashing !
I'd thought if this issue is due to post 9.02 upgrades this would solve it . But it's made it worse..
Parth