Hi,
I have paranoid android (2.1.1) and morfics Trinity kernel (111) running on my n7.
Sometimes when I come home from work and pick up my nexus it is warm and I have to press the power button for 10 seconds to reboot device as it won't wake up. After powering on, the battery level is much lower than it should be and battery usage tells me that the android os used up a lot.
I wondered if there is a way to track these freezes or whatever they are to find out what is causing them.
Could anybody give me some advice on that?
Thanks,
Nimdastas
nobody?
Nobody can help me on this?
try raising your voltages slightly. the tsvz series of trinity kernels are undervolted, it might be too much undervolting for your device. try upping your voltages slightly until you find a stable place for your device. or try a ts trinity kernel, they arent undervolted. a96 is one of my favorite.
Nimdastas said:
Hi,
I have paranoid android (2.1.1) and morfics Trinity kernel (111) running on my n7.
Sometimes when I come home from work and pick up my nexus it is warm and I have to press the power button for 10 seconds to reboot device as it won't wake up. After powering on, the battery level is much lower than it should be and battery usage tells me that the android os used up a lot.
I wondered if there is a way to track these freezes or whatever they are to find out what is causing them.
Could anybody give me some advice on that?
Thanks,
Nimdastas
Click to expand...
Click to collapse
I use BetterBatteryStats from the play store to track exactly what keeps my N7 from deep sleep mode.
Sent from my Paranoid Nexus 7
RockNrolling said:
I use BetterBatteryStats from the play store to track exactly what keeps my N7 from deep sleep mode.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
he's experiencing sod, not a problem with deep sleep.
simms22 said:
he's experiencing sod, not a problem with deep sleep.
Click to expand...
Click to collapse
Thanks for clarifying. But what do you mean by sod? Is that an abbreviation? I would think BetterBatteryStats could help diagnose whatever is draining his battery, regardless of what it's called.
Sent from my Paranoid Nexus 7
RockNrolling said:
Thanks for clarifying. But what do you mean by sod? Is that an abbreviation? I would think BetterBatteryStats could help diagnose whatever is draining his battery, regardless of what it's called.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
sod is an abbreviation, sleep if death. its when you turn your screen off then it won't turn back on when you try to turn it on. mostly its a symptom of too much undervolting for the device.
simms22 said:
sod is an abbreviation, sleep if death. its when you turn your screen off then it won't turn back on when you try to turn it on. mostly its a symptom of too much undervolting for the device.
Click to expand...
Click to collapse
Thanks for explaining! I understand now. I find it odd that different Nexus 7s would respond in very different ways to Trinity TSVZ a111. I'm running that kernel on my N7 with absolutely no issues.
Sent from my Paranoid Nexus 7
RockNrolling said:
Thanks for explaining! I understand now. I find it odd that different Nexus 7s would respond in very different ways to Trinity TSVZ a111. I'm running that kernel on my N7 with absolutely no issues.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
actually, every device differs. some can overclock or undervolt more than others. I had issues when with some games on a110 because it was slightly too undervolted for me, while others had no problems, and some had sod. a111 runs perfect for me now, since the core voltages were slightly raised, but some still have sod. bumping the voltages up slightly helps most.
simms22 said:
actually, every device differs. some can overclock or undervolt more than others. I had issues when with some games on a110 because it was slightly too undervolted for me, while others had no problems, and some had sod. a111 runs perfect for me now, since the core voltages were slightly raised, but some still have sod. bumping the voltages up slightly helps most.
Click to expand...
Click to collapse
Well, I definitely learned something new today. Thanks for sharing your expertise!
Sent from my Paranoid Nexus 7
thanks
Thanks for the explanation, finally I know what sod in the main thread means
And concerning the logging, even if I don't need it anymore, the battery stats app should help me? I suspect that it won't be able to log much when it comes to such deep issues.
Thanks,
Nimda
Nimdastas said:
Hi,
I have paranoid android (2.1.1) and morfics Trinity kernel (111) running on my n7.
Sometimes when I come home from work and pick up my nexus it is warm and I have to press the power button for 10 seconds to reboot device as it won't wake up. After powering on, the battery level is much lower than it should be and battery usage tells me that the android os used up a lot.
I wondered if there is a way to track these freezes or whatever they are to find out what is causing them.
Could anybody give me some advice on that?
Thanks,
Nimdastas
Click to expand...
Click to collapse
Answering the question, yes, there is a way to track/log the freezes. There is decent summary here : http://code.google.com/p/tegraowners-ics-rom/wiki/How_to_get_logs
You could also download an app like bootleg uptime to grab logs for you.
Thanks all for your help, and thanks irishrally for the tip!
Related
So I have had my Nexus 4 for 7 exact days, was suffering from a terrible battery life of 1:30 hrs MAX screen-on. Until I flashed CM10.1+Franco's latest kernel and my phone has a 3:30 hrs of screen time on ! - I tried AOKP with Faux and some other rom combinations...Any one can explain why?
And clearly the battery life on WIFI surpasses the one on 3g.
It probably has a lot to do with the "msm_hsic_host" kernel wakelock that is present on the stock kernel. Flashing to either franco or faux kernel is supposed to be a great way to fix it and increase battery life
Because Franco Kernel is like magic?
Edit: oh hey! you're the same guy from yesterday I suggested Franco Kernel to and pm'd me for additional tips
Ensifolk said:
So I have had my Nexus 4 for 7 exact days, was suffering from a terrible battery life of 1:30 hrs MAX screen-on. Until I flashed CM10.1+Franco's latest kernel and my phone has a 3:30 hrs of screen time on ! - I tried AOKP with Faux and some other rom combinations...Any one can explain why?
And clearly the battery life on WIFI surpasses the one on 3g.
Click to expand...
Click to collapse
1:30 screen time Max? Damn.... Do you use your phone as a satellite? And WiFi IS ALWAYS better on the battery than 3g, that goes for any phones.
Sent from my Mako Nexus quattro using Tapatalk 2!
barondebxl said:
1:30 screen time Max? Damn.... Do you use your phone as a satellite? And WiFi IS ALWAYS better on the battery than 3g, that goes for any phones.
Sent from my Mako Nexus quattro using Tapatalk 2!
Click to expand...
Click to collapse
Wasn't even using my phone for anything but Browsing/Facebook/Whatsapp! LOL - And thanks guys for the reply, and yes Im the guy who pmd you man! Thanks a lot! Will give Faux a go right now And check how things will work....
Ensifolk said:
Wasn't even using my phone for anything but Browsing/Facebook/Whatsapp! LOL - And thanks guys for the reply, and yes Im the guy who pmd you man! Thanks a lot! Will give Faux a go right now And check how things will work....
Click to expand...
Click to collapse
I suggest using https://play.google.com/store/apps/...yLDEsImNvbS5iaWdleWVzMHgwLnRyaWNrc3Rlcm1vZCJd with those kernels. I use Franco's paid app but Trickster is a good free alternative!
zephiK said:
I suggest using https://play.google.com/store/apps/...yLDEsImNvbS5iaWdleWVzMHgwLnRyaWNrc3Rlcm1vZCJd with those kernels. I use Franco's paid app but Trickster is a good free alternative!
Click to expand...
Click to collapse
Thanks for the suggestion. Tinkering with phone settings is not in my priority list, but knowing what the kernel is doing with my phone is definitely useful if I decide to tinker later.
And free phone state knowledge is priceless (as in it has no list price :cyclops
KyraOfFire said:
Thanks for the suggestion. Tinkering with phone settings is not in my priority list, but knowing what the kernel is doing with my phone is definitely useful if I decide to tinker later.
And free phone state knowledge is priceless (as in it has no list price :cyclops
Click to expand...
Click to collapse
Not sure if it has the ability to disable logging and events (i think it does). You can disable those two features for better battery life (very insignificant but every bit helps, right?) and you can disable fsync if you choose to (more IO speed, less stability mainly if your phone was to randomly reboot).
Plus the free color changing is always nice to have.
3 to 4 hours with screen on is normal battery life for a stock Nexus 4.
It sounds like you were running something that was draining the battery.
When you updated the phone, the new ROM turned off the culprit.
The battery drain is not necessarily caused by an app, it could be one
of the Google services or bad reception. Even changing the phone's default
settings can result in much better battery life.
This might be a stupid question, but could switching from stock kernel/ROM fix my antenna radio reception bull**** issues?
Sent from my Nexus 4 using xda app-developers app
It didn't used to be like this. But now I get a pretty bad drain from Android System. It would be the second highest battery consumer, and would be using the CPU for quite a lot.
I'll post my battery screens and BBS stats soon. But for now, anyone else getting this issue? I'm on CM10.1 M1, tried different nightlies but still getting this f*cking problem. It's driving me crazy.
starscream92 said:
It didn't used to be like this. But now I get a pretty bad drain from Android System. It would be the second highest battery consumer, and would be using the CPU for quite a lot.
I'll post my battery screens and BBS stats soon. But for now, anyone else getting this issue? I'm on CM10.1 M1, tried different nightlies but still getting this f*cking problem. It's driving me crazy.
Click to expand...
Click to collapse
try a different rom besides for cm, or try a different kernel. no such issue here with the rasbean jelly rom/trinity kernel. android system stays between 2-6% here.
simms22 said:
try a different rom besides for cm, or try a different kernel. no such issue here with the rasbean jelly rom/trinity kernel. android system stays between 2-6% here.
Click to expand...
Click to collapse
Alright, I'll give Rasbean Jelly ROM a try.
If you look at my attached screenshot, you'll see what apps are included in Android System. Maybe you use one of those apps a lot? What % is your Android System at by the way?
Sent from my Nexus 4 using xda premium
android88 said:
If you look at my attached screenshot, you'll see what apps are included in Android System. Maybe you use one of those apps a lot? What % is your Android System at by the way?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I have the exact same list of packages for Android System. Right now my phone's been on for an hour and it's at 21%, with a CPU total of 15 mins and it kept my phone awake for 4 minutes.
I dunno why it's like this all of a sudden. A week ago it was completely fine.
The thing is, I did clean re-flashes already and it still does that. I even wiped system. How do I properly reset my phone to get a clean slate? Should I RMA my phone if this issue doesn't go away?
Edit:
Just flashed MiNCO v6, and the drain seems to subside a little bit, but I need more time with my phone to judge better. Sigh, I'm missing CM's quick reply feature already!
starscream92 said:
I have the exact same list of packages for Android System. Right now my phone's been on for an hour and it's at 21%, with a CPU total of 15 mins and it kept my phone awake for 4 minutes.
I dunno why it's like this all of a sudden. A week ago it was completely fine.
The thing is, I did clean re-flashes already and it still does that. I even wiped system. How do I properly reset my phone to get a clean slate? Should I RMA my phone if this issue doesn't go away?
Edit:
Just flashed MiNCO v6, and the drain seems to subside a little bit, but I need more time with my phone to judge better. Sigh, I'm missing CM's quick reply feature already!
Click to expand...
Click to collapse
It's not a hardware issue. The longer the phone is on, the lower % the Android System will be at (obviously lol) because the other stuff is averaging it out. You can also ry changing your kernel.
About the messaging quick reply, just replace MiNCO's mms.apk with CM's.
Sent from my Nexus 4 using xda premium
android88 said:
It's not a hardware issue. The longer the phone is on, the lower % the Android System will be at (obviously lol) because the other stuff is averaging it out. You can also ry changing your kernel.
About the messaging quick reply, just replace MiNCO's mms.apk with CM's.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for all your suggestions!
Apologies if this is covered elsewhere, but I have been struggling to trawl through all 1000 pages on the relevant thread as I can't get the search terms to get the info!
Basically, when I leave the phone overnight charging, in the morning I cannot turn it on unless I press and hold the power button and volume down to reset the device.
Other than this it is great in terms of being able to adjust the colours and the battery life seems better.
I have tried both the nightly and stable versions..
What ROM are you using?
Sent from my Nexus 4 using xda premium
murtezahu said:
What ROM are you using?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I am currently using the stock ROM but could change to a custom... (I am learning as I go at the moment...)
Sounds like your phone is having trouble to wake after a deep sleep. I'm guessing it's caused by a (probably: too) low cpu frequency.
Did you use any app to change the cpu frequencies while asleep, or did you undervolt your cpu?
Also, which version of the kernel are you using? I suggest you stick to M1 for more stable results.
And after all, it might be a bug in the kernel. The people in franco's thread are more than willing to help you if you supply as much information as you possibly can. Kernel version, your adjustments to it if any, etc. I haven't seen this problem happen to anyone before in the last days (oh yea, I read every page of that thread...), so don't be afraid to ask for some help. But for now, I suggest you update to M1. If you're already on M1, feel free to ask your question in the thread.
LOL
Sent from my Nexus 4 using xda premium
sounds like a classical case of sod. do you undervolt?
and rolmply
simms22 said:
sounds like a classical case of sod. do you undervolt?
Click to expand...
Click to collapse
No, I do not undervolt. The only changes I made were to gamma settings. Having said that I did change the power setting but changed it back. I have rebooted the phone so I will see if it happens after the next deep sleep.
Thanks for the help so far, much appreciated!
vindikleuk said:
Sounds like your phone is having trouble to wake after a deep sleep. I'm guessing it's caused by a (probably: too) low cpu frequency.
Did you use any app to change the cpu frequencies while asleep, or did you undervolt your cpu?
Also, which version of the kernel are you using? I suggest you stick to M1 for more stable results.
And after all, it might be a bug in the kernel. The people in franco's thread are more than willing to help you if you supply as much information as you possibly can. Kernel version, your adjustments to it if any, etc. I haven't seen this problem happen to anyone before in the last days (oh yea, I read every page of that thread...), so don't be afraid to ask for some help. But for now, I suggest you update to M1. If you're already on M1, feel free to ask your question in the thread.
Click to expand...
Click to collapse
Thanks for the reply.
I am currently using milestone 1.
As far as I am aware I only made changes to the colour as I am still learning the controls as I go. I have restarted the phone to see if it helps.
The only app that I am using that could be to blame is battery guru, so if it persists, I could try disabling that.
goldeneye243 said:
No, I do not undervolt. The only changes I made were to gamma settings. Having said that I did change the power setting but changed it back. I have rebooted the phone so I will see if it happens after the next deep sleep.
Thanks for the help so far, much appreciated!
Click to expand...
Click to collapse
do you use the pgm slide to wake app?
simms22 said:
do you use the pgm slide to wake app?
Click to expand...
Click to collapse
No, I don't - Should I, or is it possibly what is could have caused the problem?
goldeneye243 said:
No, I don't - Should I, or is it possibly what is could have caused the problem?
Click to expand...
Click to collapse
its a possible cause of sod if you had it installed.
goldeneye243 said:
Thanks for the reply.
I am currently using milestone 1.
As far as I am aware I only made changes to the colour as I am still learning the controls as I go. I have restarted the phone to see if it helps.
The only app that I am using that could be to blame is battery guru, so if it persists, I could try disabling that.
Click to expand...
Click to collapse
You're using the exact same set-up I am, and I'm haven't had any of the trouble you talk of. Disabling battery guru might be a good idea. As it's an app from Qualcomm itself, I wouldn't be surprised if it's set to mess around with the stock kernel's settings. If that's the case, then your kernel is obviously not the kernel that Battery Guru was programmed to mess with! Uninstalling it to see what happens next would be a good step :highfive:. From my experience, you wouldn't need any battery management apps when you're on franco's M1 anyway - using common sense to save your battery should suffice.
vindikleuk said:
You're using the exact same set-up I am, and I'm haven't had any of the trouble you talk of. Disabling battery guru might be a good idea. As it's an app from Qualcomm itself, I wouldn't be surprised if it's set to mess around with the stock kernel's settings. If that's the case, then your kernel is obviously not the kernel that Battery Guru was programmed to mess with! Uninstalling it to see what happens next would be a good step :highfive:.
Click to expand...
Click to collapse
I will do that if I have not already got it fixed with the reboot. Battery guru is still in learning mode so possibly isn't messing with the kernel yet but is the next thing to try...
Alrighty, let's hope it'll get figured out.
vindikleuk said:
Alrighty, let's hope it'll get figured out.
Click to expand...
Click to collapse
Well, it turned on OK this morning, so hopefully fixed...
I guess I will only know in a few days time when I have got more confidence...
I had another SOD so I have reset all settings (installed nightly version 110) and started again -
The only changes I have made are to the gamma settings and changing the governer to conservative to see if that gives me a longer battery life.
Will see how it goes....
I had some more SODs with 110/111 so I changed to 121 and the battery life did not seem as good.
Takes a while to work out what is going on when it only happens once a day...
I still get occasional SODs with battery guru disabled so i guess it is either the kernel or possibly the ROM... I will try on the support thread....
Hi all,
I've been having problems recently with my phone not having good battery life. Although, I don't even think I've ever noticed good battery life recorded for it.
At this point in time, I'm struggling to get to 2 hours screen on time, with as the screenshots below showing at I'm at 20% with 1 hour 45 screen on time. I've seen screenshots of people recording at least 4 hours screen on time, yet that doesn't seem to be the case for my specific phone.
I've tried Franco's kernel's and I've still not noticed a difference in the battery life, it still seems to hover around 2 hours screen on time. Checking the wakelocks with the wakelock detector app, and it shows that my device doesn't seem to sleep as much as it should.
Does anyone have any ideas on what I can do to stop these wakelocks? And/or improve my battery life? I'm currently doing everything you would expect (of the basic recommendations)
I'd greatly appreciate the help if someone knows what the issue is, or has had similar issues.
Thanks!
1.You can try undervolting.
2.Use Greenify to hibernate apps like facebook.
3.Calibrate your battery by draining it completly then charging it to 100% in one run, so no disconnecting from charger.
Good luck!
Sent from my Nexus 4 using xda app-developers app
xJakeyy said:
Hi all,
I've been having problems recently with my phone not having good battery life. Although, I don't even think I've ever noticed good battery life recorded for it.
At this point in time, I'm struggling to get to 2 hours screen on time, with as the screenshots below showing at I'm at 20% with 1 hour 45 screen on time. I've seen screenshots of people recording at least 4 hours screen on time, yet that doesn't seem to be the case for my specific phone.
I've tried Franco's kernel's and I've still not noticed a difference in the battery life, it still seems to hover around 2 hours screen on time. Checking the wakelocks with the wakelock detector app, and it shows that my device doesn't seem to sleep as much as it should.
Does anyone have any ideas on what I can do to stop these wakelocks? And/or improve my battery life? I'm currently doing everything you would expect (of the basic recommendations)
I'd greatly appreciate the help if someone knows what the issue is, or has had similar issues.
Thanks!
Click to expand...
Click to collapse
Clearly in your screenshot Google Services is keeping awake your phone. Solution here:
http://forum.xda-developers.com/showthread.php?t=2385843
You can ask for help there. Also, for more battery life, try to UV and UC. I recommend Matrix kernel for excellent battery life. You don´t even have to tweak it, it already comes tweaked with perfect values by default.
Galaxo60 said:
Clearly in your screenshot Google Services is keeping awake your phone. Solution here:
http://forum.xda-developers.com/showthread.php?t=2385843
You can ask for help there. Also, for more battery life, try to UV and UC. I recommend Matrix kernel for excellent battery life. You don´t even have to tweak it, it already comes tweaked with perfect values by default.
Click to expand...
Click to collapse
Totally forgot about that! Thank you Is Matrix working with Paranoid Android 4.3 do you know?
xJakeyy said:
Totally forgot about that! Thank you Is Matrix working with Paranoid Android 4.3 do you know?
Click to expand...
Click to collapse
It is not compatible with PA, because PA changed to JW branch on latest update. For now, I think that Franco is the only working.
:silly:
try different rom ?
test it for few days see if that solves anything.
go with any jss rom and matrix kernel. its the best combo for very long battery life.
Hi.
My nexus 4 was rooted with twrp installed. Everything was ok, then few days back i decided to try custom kernal, downloaded faux overclock kernal. Phone booted up fine, then it started to act wierd.
When I keep phone idle and check after sometime, it dosent come up, I have to hold powerbutton for few seconds and leave, then phone boots up.
It was causing problems, so I have flashed back to google factory image. Pure stock rooted with twrp installed.
I dont understand, but my phone is still acting same. please help.
i am total stock now.
Looks like phone is not coming up when it is deep sleep.
this is called sleep of death or SOD, it happens when the CPU sleeps and won't wake up without a "battery pull" or a hard reboot like what you did...
a workaround for this is to make the minimum frequency of the CPU a little higher.
Sent from my Nexus 4
Thanx mate.. what would be recommended min freq to prevent this..
As i also face the same issue post update to kitkat
Riro Zizo said:
this is called sleep of death or SOD, it happens when the CPU sleeps and won't wake up without a "battery pull" or a hard reboot like what you did...
a workaround for this is to make the minimum frequency of the CPU a little higher.
Sent from my Nexus 4
Click to expand...
Click to collapse
kishorev said:
Thanx mate.. what would be recommended min freq to prevent this..
As i also face the same issue post update to kitkat
Click to expand...
Click to collapse
anything 400MHz+ is good, try not to lower it too much. it'll consume more battery, but at least it won't die sleeping
Sent from my Nexus 4
Ha ha will try that.. thanks again.. will definitely ping u if that doesnt solve it
Riro Zizo said:
anything 400MHz+ is good, try not to lower it too much. it'll consume more battery, but at least it won't die sleeping
Sent from my Nexus 4
Click to expand...
Click to collapse
Hey man
Tried putting it at 484 MHz using trickster Mod.. still have the same problem
The funny thing is it works well for other older android versions.. only for this it dies like this
Let me know if you think there may be any workaround or will switch it back to 4.3
Riro Zizo said:
anything 400MHz+ is good, try not to lower it too much. it'll consume more battery, but at least it won't die sleeping
Sent from my Nexus 4
Click to expand...
Click to collapse