Related
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
What kernels have been used with the roms?
Sent from my HTC Sensation Z710e using XDA App
The used kernels were default kernels of the roms I used. Problem started wen using CM7 alpha. and now using Android Revolution with Faux123
Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Same for me, but ONLY with Revo HD ROM...
SadMac said:
Same for me, but ONLY with Revo HD ROM...
Click to expand...
Click to collapse
You don't have it in any other ROM?
I had the same problem before, I changed my kernel to bricked 0.91 and the problems are gone now.
I'm downloading Insertcoin rom now. I'll report back if the problem still occurs.
Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Change kernels. Go from 1.5ghz to 1.2 via daemon controller or another CPU adjuster.
The bricked 0.91 also fixes most issues too as stated above
Sent from my HTC Sensation in UR-Quan subspace.
Before you suspect Hardware.. Check first your software.. I'f i were you, i'll back up all my roms.. full / super wipe, then check it on by one.. lets say IC for first 2 days then ARHD on the 3nd-4th day.. If it does not shut down, it only means one thing, its not HARDWARE, it can be software.. Check also your chosen Kernel on your flashed ROM.. there might be an incompatibility running multiple different roms and kernels..
hope i'd help.. click thanks if i enlighten you so far..
Okay, I'm back from a weekend away.
What I did before I went away (Friday afternoon) is:
- Reboot to Recovery
- Wipe cache, wipe dalvik, wipe data
- install zip: Super-wipe (just to be sure)
- Install zip: InsertCoin 3.3.0
- install zip: InsertCoin 3.3.1
It all went well until Saturday evening. It was off when I got it out of my pocket. i tried to turn it on and it booted up. If it is on there is no problem at all. It stays on all the time...... Until I unlock my sim with my personal code. 2 seconds atfter that the phone turns off...
Since the problem reoccurred I tried the following things:
- Wipe cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, Super-Wipe, re-install rom, reboot (problem still exists)
Is there a way to test the hardware to rule it out? The problem occurred in three different roms and got worse. I really can't see how this could be a software problem.
I'm now going to download the latest stock rom and see what happens...
I had the same problem I'm on tmobile sensation 4g in the us and I think all us sensations have the problem... When I was using any rom that was based on the experimental sense 3.5 base my phone would turn off/crash I tried all different Roms but the problem still occured, I though about it and installed revolution hd with sense 3.0 and still on the old base and the problem is gone. I'm waiting for the official release of the new sense 3.5. Hope it helps
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Frazzy said:
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Click to expand...
Click to collapse
I am having the same problems. I tried all of the same roms you have tried and as of last week I have decided to unroot my phone and return it to stock rom and recovery. after a week I am still getting the same random reboots. the only non stock part of my phone is that it is still S-Off, but I think im going to have to learn how to put stock S-On and go yell at the T-mobile guys to see if I can get a new phone.
If you can come up with anything better I would be willing to try it. the reboots are killing me.
This issue sucks. I'm glad I'm not the only one that has it though lol. I've also gone back to stock rom, no root/S-ON etc. Just to rule out the possibility that it's something funky going on with custom roms, kernels etc. So far I do still have random shutdowns, possibly a little less than I did before, but still there nonetheless. To get S-ON again, flash the RUU appropriate for your phone, then get into fastboot and type
fastboot oem writesecureflag 3
and then
fastboot reboot-bootloader
More on all this is here: http://forum.xda-developers.com/showthread.php?t=1201773
As far as logs to track down what is going on, I think it might be in lastkmsg. Unfortunately I don't know exactly where to find that or what to look for exactly.
And as stated twice before me, the problem still exists. I'm going to undo all changes to the Sensation and see what happens. If the problem is still there the phone will go back for warranty.
And again my old trustworthy HD2 saves the day as a backup...
I've never experience having a reboot with a super wipe then flashing a custom rom.. i do it almost everyday.. maybe its already a hardware since software installation (roms, and kernels) are clean when you do the flashing.. Has your phone experience some accidents? like fell on the ground?
Not that I know of.
I'm not new to flashing and I'm a real flashoholic. Nothing ever went wrong with flashing. Where other people would have problems with a certain ROM I could always enjoy the Rom without trouble.
I installed the eu version of the shipped roms. the problem seems to be different again. Nof it shuts down far less then before but I have to pull the battery to get it to boot up again.
I hope I have enough time today to S-on the phone. Does anybody know if the box states which version number it was shiped with? I know it's EU but there are different version numbers. (or is that not impotant)
Thanks for your help everybody.
I think the problem is the battery. I bought a new battery, the evo3d batery and so far I have not had this issue again.
Problem is solved. I got a free board swap and now everything is working again. So it was a hardware defect.
Thanks for the help all.
Hi all!
I was trying some kernels and the last one was Bricked 1.36 and ViperS 1.1.0 ROM, wifi and other things worked, but today morning i woke up and wifi says "turning on" for 1O minutes, so i restart it. Still turning on. So i reflasherd kernel. Still turning on. So i clear cache, wipe dalvik and fix perimissions. Still turning on.So i flashed whole ROM with kernel Bricked 1.4 and did full-wipe. Still turning in. So i flashed come CM ROM with their own kernel. Still turning on....After some time for try turn it on, it says something like "fault, Fail..."(i am using other language, than english)
My vacation starts just great...
I am of cource S-OFF, HBOOT 1.27, Rooted, Sensation XE.
Can someone give me some advice? i am at the end of my experiences. Thanx!!!
EDIT: wifi was not working about half a hour...but than...voila!!! It is for no reason back working the phone was just liyng on the table, than i took it and just set wifi on, "what if"... that´s really strange, but. But great! Now go back root, s-off and some awesome custom rom
lord5619 said:
Hi all!
I was trying some kernels and the last one was Bricked 1.36 and ViperS 1.1.0 ROM, wifi and other things worked, but today morning i woke up and wifi says "turning on" for 1O minutes, so i restart it. Still turning on. So i reflasherd kernel. Still turning on. So i clear cache, wipe dalvik and fix perimissions. Still turning on.So i flashed whole ROM with kernel Bricked 1.4 and did full-wipe. Still turning in. So i flashed come CM ROM with their own kernel. Still turning on....After some time for try turn it on, it says something like "fault, Fail..."(i am using other language, than english)
My vacation starts just great...
I am of cource S-OFF, HBOOT 1.27, Rooted, Sensation XE.
Can someone give me some advice? i am at the end of my experiences. Thanx!!!
Click to expand...
Click to collapse
Have you tried to restore the stock ROM?
http://forum.xda-developers.com/showthread.php?t=1529941
I agree I would recommend flashing the full ruu to take you back to stock Rom I did the same thing to get rid of my problem and flashing the full ruu did the trick I'm now s off Revolutionary style and flash 4ext custom recovery and su file and custom Rom the correct way
Sent from my HTC Sensation 4G using xda premium
Finaly i am here
I have flashed RUU 3.33.401.106 firmware and, did full-wipe and flash stock odexed ROM, but still the same issue :-/
and now i have HBOOT 1.29 and status *LOCKED*....
lord5619 said:
Finaly i am here
I have flashed RUU 3.33.401.106 firmware and, did full-wipe and flash stock odexed ROM, but still the same issue :-/
and now i have HBOOT 1.29 and status *LOCKED*....
Click to expand...
Click to collapse
Hi,
I believe THIS PATCH will restore your hboot to 1.27 and not "LOCKED"
Silly question,did you try rebooting your router?
malybru said:
Hi,
I believe THIS PATCH will restore your hboot to 1.27 and not "LOCKED"
Silly question,did you try rebooting your router?
Click to expand...
Click to collapse
will try your patch, thx
EDIT: it says -Revolutinary- and HBOOT is 1.27.1100 Thanks!
router works, coz we are using several phones and notebook @home...
I am afraid the worse scenario...burned chip or motherboard.
Or maybe if i get back to S-ON, unroot and restore complete stock...?
lord5619 said:
will try your patch, thx
router works, coz we are using several phones and notebook @home...
I am afraid the worse scenario...burned chip or motherboard.
Or maybe if i get back to S-ON, unroot and restore complete stock...?
Click to expand...
Click to collapse
Hi,
The other thing worth considering are the 2 gold pins inside the phone,just above the camera lens.
GENTLY lift them to make a better contact.
malybru said:
Hi,
The other thing worth considering are the 2 gold pins inside the phone,just above the camera lens.
GENTLY lift them to make a better contact.
Click to expand...
Click to collapse
I am afraid, even this is not working. Pins definetly have some resistance and resting to its place. :-/ when i return from vacation, i´ll take my precious Sensation XE to a doctor, he will know perhaps.
I have this problem too. I've been using ViperS 1.1.0 for a few weeks without any wifi problem. Yesterday, the wifi was working like normal then in the evening I flashed HyperNonsense 3.3 just to try it. Didn't like it, so I restored nandroid of my ViperS, then flashed yank555's faux123 kernel v2.52. I only realised wifi is not working today morning. It just shows "Turning On", but nothing happens. Could it be kernel issue? Previously i was using yank555 v1.9 without any issue thoguh.
i also have the same problem with the wi fi turning on for 10 mins then it shows error
mine came with the initial ics ota update a very common problem i see on the net not only wifi but bluue tooth also not work
i installed the latest ota a week or so ago which cured a few bugs but still no wifi or bluetooth
so.... i did jb s offf , root etc installed CM9 this fixed the blue tooth and made the screen move reactive and smooth this is one cool ROM BUT still no wifi
any and all suggestions welcome but please consider i am a noob http://forum.xda-developers.com/images/smilies/confused.gif and may need a few signposts
thanks in advance
alphaz1 said:
I have this problem too. I've been using ViperS 1.1.0 for a few weeks without any wifi problem. Yesterday, the wifi was working like normal then in the evening I flashed HyperNonsense 3.3 just to try it. Didn't like it, so I restored nandroid of my ViperS, then flashed yank555's faux123 kernel v2.52. I only realised wifi is not working today morning. It just shows "Turning On", but nothing happens. Could it be kernel issue? Previously i was using yank555 v1.9 without any issue thoguh.
Click to expand...
Click to collapse
I honestly don´t know, i thought, wifi is (almost)only kernel related, but now i see, that it is not :/ It is almost exactly my problem, i was using ViperS and changed kernel...but it didn´t suit me, so i restored the previous one...than i woke up and wifi is gone i cant solve it for now, i don´t have any freetime at this moment for making full stock condition.
i have tested stock rom with stock kernel, with some other HBOOT but still the same.
bhma said:
i also have the same problem with the wi fi turning on for 10 mins then it shows error
mine came with the initial ics ota update a very common problem i see on the net not only wifi but bluue tooth also not work
i installed the latest ota a week or so ago which cured a few bugs but still no wifi or bluetooth
so.... i did jb s offf , root etc installed CM9 this fixed the blue tooth and made the screen move reactive and smooth this is one cool ROM BUT still no wifi
any and all suggestions welcome but please consider i am a noob http://forum.xda-developers.com/images/smilies/confused.gif and may need a few signposts
thanks in advance
Click to expand...
Click to collapse
Your wifi stops working through an official update? You should claim it! it is not your fault...for me, everything works, except thing about wifi like tethering etc., thats a serious problem, even reflasing the whole phone (rom, radio, hboot, kernel) doesn't help :/
I had Xperia Arc before Sensation XE and reflash always helps, no matter what happens.
lord5619 said:
Your wifi stops working through an official update? You should claim it! it is not your fault...for me, everything works, except thing about wifi like tethering etc., thats a serious problem, even reflasing the whole phone (rom, radio, hboot, kernel) doesn't help :/
I had Xperia Arc before Sensation XE and reflash always helps, no matter what happens.
Click to expand...
Click to collapse
i read that the wifi tether(hot spot)......phone company pressure:cyclops: wont work on any htc phone with ics
dont know if its true though
yes wifi problems after the official update seems quite common and from what ive read htc dont seem to want to know about it
please remember im a noob:fingers-crossed: i installed jb hboot and cm9 rom but that rom is based on 3.33 i think
ill try another rom on the weekend and see what happens
thanks for your reply
cheers bhma
bhma said:
i read that the wifi tether(hot spot)......phone company pressure:cyclops: wont work on any htc phone with ics
dont know if its true though
yes wifi problems after the official update seems quite common and from what ive read htc dont seem to want to know about it
please remember im a noob:fingers-crossed: i installed jb hboot and cm9 rom but that rom is based on 3.33 i think
ill try another rom on the weekend and see what happens
thanks for your reply
cheers bhma
Click to expand...
Click to collapse
I thing, if you changed rom, kernel etc. and wifi is still not working, another rom will be no help i am afraid but take your chances! it is not working for me. I can flash any ROM, any Kernel and the result is the same...
lord5619 said:
I thing, if you changed rom, kernel etc. and wifi is still not working, another rom will be no help i am afraid but take your chances! it is not working for me. I can flash any ROM, any Kernel and the result is the same...
Click to expand...
Click to collapse
Originally Posted by Zeustopher
Wanted to update on my progress. I solved the issue on my phone:
I was messing around with it today while waiting for a meeting to start and I found where the wifi settings, etc are stored. It ended up being a corrupt/invalid wpa_supplicant.conf file. All I had to do was pull that file out from the directory and turn on wifi and *poof* it worked again. When I turned wifi on it created a new file and everything has been great so far this afternoon.
In case anyone wants to give it a shot who is having wifi issues you can find the wpa_supplicant.conf file in /data/misc/wifi/ directory on your phone. Simply cut/rename the file and put it somewhere else. If you have wifi passwords you want to save, you can open the original file using a text editor and copy the settings over to the new file.
I believe the cause of my issue was actually Titanium Backup. Looking at the last time it backed up my wifi settings was back when I wasn't running ICS yet. Yesterday I did restore an app using it and must have accidentally restored that old backup. Their formats are different from Gingerbread to ICS apparently and it was causing errors.
i found this on another post dont know if it will help but it could be the problem with the ota update from gb to ics
now the silly noob question how do you access the directory ????http://forum.xda-developers.com/images/icons/advanced/sign.png
i got into the directory but it doesnt seem to work in another thread someone got it to work with a virtuous rom
ill try that on thr weekend
enjoy your vacation
hmmm thats iteresting, but if you do full-wipe and flash some rom and kernel, these files are rewriten...but because i am curious i tried it and!!! it is not working for me :-/
And how to get into this directory?Simply... download dome file manager from Play Market(i lika Total Commander), but you can use whatever you like, set in options "root function everywhere" and allow superuser. than you can go in any directory and read/write/change
EDIT: ou, now a see whole post, ignore my instruction i am mega-sleepy
alphaz1 said:
I have this problem too. I've been using ViperS 1.1.0 for a few weeks without any wifi problem. Yesterday, the wifi was working like normal then in the evening I flashed HyperNonsense 3.3 just to try it. Didn't like it, so I restored nandroid of my ViperS, then flashed yank555's faux123 kernel v2.52. I only realised wifi is not working today morning. It just shows "Turning On", but nothing happens. Could it be kernel issue? Previously i was using yank555 v1.9 without any issue thoguh.
Click to expand...
Click to collapse
I fixed it by doing a full wipe, flashed ViperS 1.2.1, reboot, use the phone for a few minutes, then flashed Yank v2.52.
alphaz1 said:
I fixed it by doing a full wipe, flashed ViperS 1.2.1, reboot, use the phone for a few minutes, then flashed Yank v2.52.
Click to expand...
Click to collapse
Yank v2.52? hmmm that´s kernel by Faux?
lord5619 said:
Yank v2.52? hmmm that´s kernel by Faux?
Click to expand...
Click to collapse
yep
alphaz1 said:
I fixed it by doing a full wipe, flashed ViperS 1.2.1, reboot, use the phone for a few minutes, then flashed Yank v2.52.
Click to expand...
Click to collapse
No help for me still the same "turning on"
I'd like to get the feedback from XDA masters on this issue I had.
Here's the steps that led to the problem.
Flashed ROM(Dr No V2), Decide i didn't like it after a day, the wifi was orking.
Entered 4ext recovery did a full wipe.
Used restore to flash my previous fully functioning ROM (EnergyROM-RCMIX)
Rebooted.
After reboot received the message in settings>...>Wifi "error"
I went through a bunch of steps, lots of reboots.
Try restore of an earlier backup - no fix
Reflashed from Zip the original RCMIX ROM, and fastboot flashed boot.img - no fix
Went into recovery and factory reset only. - no fix
Restored the last working ROM (RCMIX) and just fastboot reflashed boot.img
Still not fixed
More reading tried rename of the wpa_supplicant file. nope
One more fastboot flash of boot.img --
Then... turned on "Airplane Mode" for a few minutes. After turning it off Wi-fi "error" was gone and was able to turn it on.
The error changed to "unable to scan for networks"
Rebooted
Went back in and renamed wpa_supplicant.conf 1 more time.
reboot
When I enable wifi this time it scanned and connected.
I left some steps out, but they were just repeats of the ones I listed.
My question after all that is what went wrong?
Lots of threads about the problem but solutions seem to vary.
Is there something in there that I did incorrectly?
Aren't the drivers for the hardware located in the boot.img (as it contains kernel)?
Is there a better way to do this?
trying to get better at this; Insights, advice, comments appreciated.
I do need to get familiar with logcat.
Clean flash a stock-ish ROM like Android Revolution HD. Is the problem still there?
bananagranola said:
Clean flash a stock-ish ROM like Android Revolution HD. Is the problem still there?
Click to expand...
Click to collapse
Wifi seems to be stable now. Running the restored RCmix. Rebooted a couple times and no issues. I'm interested in gaining some insight into the source and solution of the problem. My next step was to run a stock RUU I have, but your suggesting something close to stock might have worked?
Why didn't a re-flash of the previously functioning ROM (RCmix, zip on sdcard & fastboot boot.img) fix the issue? I did full wipes each and every time. Even full wipes before doing Restores from recovery. Restore should be a straight forward process from recovery, right?
The problem started right after a restore, and I'm not sure what step it was that fixed it. The last thing was renaming the wpa_supplicant.conf file. I left out the part where my restored ROM got stuck in the boot animation. There was something going on with the boot loader. Re-flashing boot.img fixed it.
But the wifi...? Any thoughts.
I'm a little hesitant to flash another ROM for fear of losing wifi again. I use it a lot.
Cremnomaniac said:
I'm looking for some intelligent feedback. Any thoughts on my OP?
Click to expand...
Click to collapse
I already answered you...and also, why are you renaming wpa_supplicant.conf? Are you making any other changes?
bananagranola said:
I already answered you...and also, why are you renaming wpa_supplicant.conf? Are you making any other changes?
Click to expand...
Click to collapse
Thanks, but your first comment offered a possible solution, and solutions are important, but as indicated in the title it had been solved. There aren't any comments on the questions I specifically asked. At the least, I was hoping that someone with greater experience could provide insight into the possible causes of loss of wifi (steps, incompatibility of ROM, freak thing, etc.) so I can avoid it in the future.
The renaming of wpa_supplicant.conf came from threads in the XDA forums where similar wifi problems had been encountered. It was a solution with zero risk.
Here: http://forum.xda-developers.com/showthread.php?t=1965812&page=3
Here: http://forum.xda-developers.com/showthread.php?t=1662805
Here: http://forum.xda-developers.com/showthread.php?t=1988190&highlight=wifi+error
Here: http://forum.xda-developers.com/showthread.php?t=703105
If I made any other changes I would mention it. I can see that you may be the only one monitoring this forum, which is unfortunate. You exhibit a lot of patience, but unlike some of the questions posted, I do the research and read directions carefully. The reason I ask questions is to learn, not to have my hand held. And someone posting "ddpo" is a waist of bandwidth. If no one has any comments to my questions, we'll leave it at that.
Because stock is most stable, flashing a stock-ish ROM will reveal whether the problem is a hardware one or a software one. If the problem still exists on stock, your hardware is probably messed up. If the problem doesn't exist on stock, something is up with your ROM. That is why flashing stock is still relevant: for the first step in diagnosis. Other than that, you can look into getting S-Off and flashing an updated radio, but that's up to you.
And I already reported the "ddpo."
Hello All,
I've been getting random reboots on my phone and just went ahead to take the kmsg. I'm not really sure how to go from here so any help would be great. The Kmsg is attached (slightly lengthy). Thanks!
Yeah mine has exactly the same problem. I can tell you that another kernel doesn't work. I've tried both the AK and the franco kernel. None seem sto change anything.
Apart from that - sometimes my phone is unable to enable WiFi or mobile data after crashing, and it won't work until I reboot it again. Maybe I should try another radio - are there updated versions out there?
I'll keep you updated if anything happens. Until then - Who can help out?
Thanks for responding! I'm not sure if I should start flashing different modems but I'd like to wait until someone with more experience on this places some input. I don't know if this is a hardware issue or a software one.
Update: The modem/radio of the Oppo Find 7 possibly did the trick. Haven't had any reboots since a couple of hours.
Maybe it works for you.
http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
Edit: The reboots are back - didn't fix
xbenbox your kmsg actually points to the modem... Try reflashing it using one from the following thread and see if you have any luck.
[REF] [RADIO] OnePlus One Modem Collection
What ROM are you using? Yeah it points to the modem but your phone is having a kernel panic.
Have you tried other ROMs? Have you verified that the modem is the correct MD5 Hash?
MasterMind33 said:
xbenbox your kmsg actually points to the modem... Try reflashing it using one from the following thread and see if you have any luck.
[REF] [RADIO] OnePlus One Modem Collection
Click to expand...
Click to collapse
zephiK said:
What ROM are you using? Yeah it points to the modem but your phone is having a kernel panic.
Have you tried other ROMs? Have you verified that the modem is the correct MD5 Hash?
Click to expand...
Click to collapse
Thanks for the help guys. I was going to flash the modems but wanted to make sure that it would be okay before I did so. To be honest I'm not sure if it's the correct md5 hash. This phone shipped to me with stock 33R and I ended up putting 25R on it. I didn't do any changes to the modem after that. I haven't tried other roms yet since I'm hoping to stay with cm. Also I thought that other roms tend to use the roms from cm as well.
I flashed the 33r modem and it still seems to be restarting every once in a while. The kmsg read exactly the same as the one I posted before. Any chance that it's not the modem?
xbenbox said:
I flashed the 33r modem and it still seems to be restarting every once in a while. The kmsg read exactly the same as the one I posted before. Any chance that it's not the modem?
Click to expand...
Click to collapse
I am having SAME situation. I have this phone for a week, and sod-s every day. Two days ago phone restarts and now in the loop of logo 1+. Same error, MODEM time out.
Tried ROMS: Mahdi ,CM11
Kernels: Franco r18, r19, stock from both..
Can not get out of the loop.. I have wiped all partitions, formated all of them, clean flash of ever rom... nothing.
And yes, tried all modems...
Updated to 33R with the same rebooting issues although the kmsg now reads differently. Dalvik and Cache were wiped as well and same issue still occurs.
Still need help - bumping with my newest kmsg.
I doubt anyone on XDA has the solution to this problem. I would suggest for all others to go to Jira Cyanogenmod under the issue labeled Bacon-213 for progress checks and uploading last_ksmgs. This may be a hardware issue as not a lot of people are reporting having this issue.
My Nexus 5 which I upgraded from a 5.01 to the 5.1 (stock Google rom, without wipe) has a very big battery problem: the device never reaches deep sleep.
I have some years experience in identifying wakelocks, but this wakelock is new. And the strange thing is: I can't even find a thing on Google. Nothing!
The wakelock is a kernelwakelock (PowerManagerService.Wakelocks). I investigated at partial wakelocks which wakelock it is. It's a wakelock called 'ProxyController'. It's related to the phone process/app.
I wiped cache, tried different Kernel (elementalx). Changed CPU gov, wiped dalvik, changed network, refreshed some settings. Disabled unused apps. I even reinstalled the image and other files through recovery. But nothing helps.
Also I noticed, it might be related, that sometimes my phone reboots or it looses sim and signal. (Which worked perfect in 5.01!). All problems started after 5.1 upgrade.
Ofcourse I can do a full wipe, or revert back or try a custom rom. But I hope it is possible to fix, because besides these weird problems it was / is perfect!
Edit: Important, I couldn't be called either. Also calling someone was difficult and the phone process kept freezing. My phone (and then the phone part) was totally broken! Radio of 5.01 did fix. Read comments below!
Have you tried flashing an older radio.img version and/or a clean flash?
Elluel said:
Have you tried flashing an older radio.img version and/or a clean flash?
Click to expand...
Click to collapse
I tried a clean flash now. I didn't only have a wakelock but nobody could call me either.
Also sometimes the phone process did get frozen.
Now I tried a wipe and totally clean install with other installer (The Google original images and installer!). I did not install any other new unneeded apps. And I still have the problem.
I think I will try an older radio now. Very strange... My phone became unusable after the upgrade from 5.01 to 5.1. This looks to be some major bug.
cognosco said:
I tried a clean flash now. I didn't only have a wakelock but nobody could call me either.
Also sometimes the phone process did get frozen.
Now I tried a wipe and totally clean install with other installer (The Google original images and installer!). I did not install any other new unneeded apps. And I still have the problem.
I think I will try an older radio now. Very strange... My phone became unusable after the upgrade from 5.01 to 5.1. This looks to be some major bug.
Click to expand...
Click to collapse
If it happens with a completely clean flash with nothing installed, and with every radio version, then it could be a hardware problem.
But yeah, try an older radio version.
Elluel said:
If it happens with a completely clean flash with nothing installed, and with every radio version, then it could be a hardware problem.
But yeah, try an older radio version.
Click to expand...
Click to collapse
Yes I fear that too.
However, it started immediately after the 5.1 upgrade, before all was good...
It also seems there might be a link with screenoff/standby. When it's in standby and I switch the device on I see it has no connection or is reconnecting. As if something goes wrong with the connection then. Maybe important information.
I will investigate further. Ofcourse all new tips, ideas and infos are welcome. I will also keep you updated.
Update:
Flashed 5.01 radio into my 5.1. Now it SEEMS to be fixed. Phone goes to deep sleep, I can call people without crashing and I can be called. For now. But don't cheer to early, I have only tested for 10 minutes.
So it seems to be something completely wrong in this radio in combination with my device or simcard or provider. I am using Vodafone NL.
Update: a few days later. Running 5.1 rom with 5.01 radio and all seems ok and fixed!
cognosco said:
Update:
Flashed 5.01 radio into my 5.1. Now it SEEMS to be fixed. Phone goes to deep sleep, I can call people without crashing and I can be called. For now. But don't cheer to early, I have only tested for 10 minutes.
So it seems to be something completely wrong in this radio in combination with my device or simcard or provider. I am using Vodafone NL.
Click to expand...
Click to collapse
Hi,
I'm having exactly the same problem. Did the "new" radio fix it? Which radio did you flash?
Thanks,
Regards,
DarkSorcerer said:
Hi,
I'm having exactly the same problem. Did the "new" radio fix it? Which radio did you flash?
Thanks,
Regards,
Click to expand...
Click to collapse
Hello. I am running this Radio (2.0.50.2.22) since my last post, A couple of days. I am experiencing no problems as far as I can tell. It seems to work well and the big problems seem to be gone.
I can advise you to flash this Radio from the 5.01 packages. Big chance your problems will be fixed.
Strange that there is only one other person for now. I am thinking what we could have in common. What is your provider?
cognosco said:
Hello. I am running this Radio (2.0.50.2.22) since my last post, A couple of days. I am experiencing no problems as far as I can tell. It seems to work well and the big problems seem to be gone.
I can advise you to flash this Radio from the 5.01 packages. Big chance your problems will be fixed.
Strange that there is only one other person for now. I am thinking what we could have in common. What is your provider?
Click to expand...
Click to collapse
Hi,
Thank you for your quick answer. I'll try it first thing in the morning.
It is weird indeed.. My provider is the equivalent of Orange. As with you, it only started to happen after the update to 5.1.
I'll report back. Thanks!