Related
So I'm just wanting to increase my own understanding of how things work, plus I see people ask this question about specific rom's often. Given 2 different roms with identical kernels and identical setups, how do you explain different power usage and battery life?
In other words, why would you see a noticeable difference in battery life with one rom vs another, given all apps equal and kernels equal?
kingston73 said:
So I'm just wanting to increase my own understanding of how things work, plus I see people ask this question about specific rom's often. Given 2 different roms with identical kernels and identical setups, how do you explain different power usage and battery life?
In other words, why would you see a noticeable difference in battery life with one rom vs another, given all apps equal and kernels equal?
Click to expand...
Click to collapse
Hi,
I think it's a well known fact that not all phones are created equal.
Plus,no two people use their phone in the same way.
So,you will get variations all the time.
I think the OP is talking about 1 user and 1 phone having different results (different power usage and battery life) with roms that use the same base, kernel, etc.
I personally think that certain devs tweak some settings a little and the slight difference we notice comes from this. But since I'm not a Pro, I'm going to let someone else answer it, as I been looking for this answer.
Thanks OP for asking it.
rasco702 said:
I think the OP is talking about 1 user and 1 phone having different results (different power usage and battery life) with roms that use the same base, kernel, etc.
I personally think that certain devs tweak some settings a little and the slight difference we notice comes from this. But since I'm not a Pro, I'm going to let someone else answer it, as I been looking for this answer.
Thanks OP for asking it.
Click to expand...
Click to collapse
Hi,
Sorry, I mis-read.
You are right about the Devs doing their own thing,and tweaking every ROM differently.
They are always trying to squeeze every drop of improvement out of the ROM for the user.
Mike 1986 is a good example of this.
On every changelog of his are the words:
"Other minor changes and fixes"
rasco702 said:
I think the OP is talking about 1 user and 1 phone having different results (different power usage and battery life) with roms that use the same base, kernel, etc.
I personally think that certain devs tweak some settings a little and the slight difference we notice comes from this. But since I'm not a Pro, I'm going to let someone else answer it, as I been looking for this answer.
Thanks OP for asking it.
Click to expand...
Click to collapse
That's exactly what I'm asking. I'm not wondering why I get different results from you, I'm wondering why I get different results from one rom to the next with MY phone and MY same apps etc.
Hey!
I know this topic has been risen up many times because this is a very popular problem. So without going into generalazing, I am concerned with my problem.
I am a long time user of the ARHD sensation ROM. First ROM I've installed on my sensation and still am using. A little addicted to flashing.
So, what I have learned during these few months reading many threads about this:
When I was on all stock, it was fine, for the most part. When I switched to ARHD, everything was still fine. Just a few random reboots. This, of course varies from version to version. I had once found the perfect combination of ROM, kernel and everything that I didn't get RR's for some quite time ( week or two ). But then, one day it did the RR and I was thinking of upgrading, since many new versions had came out by this time.
But now I am fed up with all the reboots because many times the phone is unusable, so I'm looking for an answer.
When I install a ROM, I usually upgrade the FW, if it is necessary, then do a superwipe, install ROM. After that comes Google account and Apps.
But the thing is, no matter what I do, I always get random reboots.
So now I did the same exact thing: Superwipe, ARHD 6.6.2. no bravia, no supercharger, stock kernel, camera mod. My phone is clean of unnecesary things but I still get random reboots.
When I pull out the battery and then turn on my phone, it is fine for some time and then again - random reboots.
So, my question is: Where and how can I find out what is causing my phone to crash? Is there any file I can share with you that will pose at least a basic understanding of the cause of random reboots? If there is, where is it located?
Help would be greatly appreciated.
Tomekks said:
Hey!
I know this topic has been risen up many times because this is a very popular problem. So without going into generalazing, I am concerned with my problem.
I am a long time user of the ARHD sensation ROM. First ROM I've installed on my sensation and still am using. A little addicted to flashing.
So, what I have learned during these few months reading many threads about this:
When I was on all stock, it was fine, for the most part. When I switched to ARHD, everything was still fine. Just a few random reboots. This, of course varies from version to version. I had once found the perfect combination of ROM, kernel and everything that I didn't get RR's for some quite time ( week or two ). But then, one day it did the RR and I was thinking of upgrading, since many new versions had came out by this time.
But now I am fed up with all the reboots because many times the phone is unusable, so I'm looking for an answer.
When I install a ROM, I usually upgrade the FW, if it is necessary, then do a superwipe, install ROM. After that comes Google account and Apps.
But the thing is, no matter what I do, I always get random reboots.
So now I did the same exact thing: Superwipe, ARHD 6.6.2. no bravia, no supercharger, stock kernel, camera mod. My phone is clean of unnecesary things but I still get random reboots.
When I pull out the battery and then turn on my phone, it is fine for some time and then again - random reboots.
So, my question is: Where and how can I find out what is causing my phone to crash? Is there any file I can share with you that will pose at least a basic understanding of the cause of random reboots? If there is, where is it located?
Help would be greatly appreciated.
Click to expand...
Click to collapse
The Best solution is to have system Tuner app (by 3C) installed and run the logs(LOGCAT) on it
once you have a RR just save the log after rebooting and post the log file in the corresponding ROM thread and/or Kernel Thread (if you have custom Kernel) and then ask for a solution/reason which they can give pretty easily once they have this log
First question - Are there lock screen notifications for text messages, e-mails, etc.? I haven't been able to find them if there are.
Second question - Is there a way to stop getting VZWNMN messages after flashing to CM10 without blocking the number. So in other words, is there a fix for this?
Third question - Is there an official page with bugs noted by CM themselves? Rather than scrolling through threads reading what everyone else is saying.
Fourth - Haven't really been able to try it out much yet, but how is the battery life on CM10? I only have it rooted and on CM10 which means I have no special apps, kernels, whatever else installed. Is there anything recommended to install with CM10 besides GAPPS?
Hope someone can answer these questions!
1. Not that I have seen without third party app. But with slide being my only security setting I am able to utilize the notification pull down
2. There was a thread in the q/a section yesterday regarding this and you have to go to a Verizon based Web Page and change a setting (don't remember the exact details) and they should stop
3. I have not seen a "bug" list per say... But then again I haven't exactly searched for one either... Sorry I cannot answer this one
And I only flash rom gapps and kernel and then install my apps etc. Nothing else special
EDIT: http://forum.xda-developers.com/showthread.php?t=1901508 this should help with your second question. Sorry I didn't have the link handy with my first reply.
Re battery life, CM seems to give me lesser battery life than stock ROM. I ran stock for a couple of weeks, and with moderate to heavy usage (lots of playing with new phone, browsing, changing settings etc), I'd still have about 25pct left at bed time. Now, it's about to turn off around the same time.
I had Galaxy Nexus before this, and a Captivate before that, and had CM on both of them, and wouldn't always make it to the end of the day. S3 is better than both of those.
when I used cm10, the battery life was somewhat less than stock. I'm running Beans rom now and battery life is very good. Better than stock.
I have to say that i'm considering going back to CM10. Both rom's are smooth and fast. Everything works in Beans for the most, making it a daily for a lot of people.
On Bean's R9 and R11 with imoseyon's LK 0.5 I was getting 4.5 hours of screen on time. On 9/23 nightly, I'm getting 4 hours of screen on time. I can tolerate that difference as I prefer AOSP based roms.
Sent from my SCH-I535 using xda premium
Help with audio using CM10
I'm on the current nightly builds. This happens on all the builds I've used. At times, seems random to me, the phone will say 'audio' or 'resuming audio'. I've had this happen even when set to silent mode. Any ideas????????????
thanks,
Elliott
I first had the problem with Carbon and Leantastic, then switched to KT, then flashed to Paranoid Android and its kernel, then to AOKP and its kernel. All of these configurations work fine until I dip below 50% battery, when I start to experience constant random reboots no matter what I do. I tried flashing back to stock then flashing back to custom, different kernels, different firmware, wiping caches/factory resets, etc. and nothing has fixed the problem. The only commonality I can think of in each configuration is that the ROM or kernel is CM-based, because the problem is not present in stock. I've turned Google upside-down trying to find a solution, but haven't had luck. Anyone know what the problem could be?
virsago said:
I first had the problem with Carbon and Leantastic, then switched to KT, then flashed to Paranoid Android and its kernel, then to AOKP and its kernel. All of these configurations work fine until I dip below 50% battery, when I start to experience constant random reboots no matter what I do. I tried flashing back to stock then flashing back to custom, different kernels, different firmware, wiping caches/factory resets, etc. and nothing has fixed the problem. The only commonality I can think of in each configuration is that the ROM or kernel is CM-based, because the problem is not present in stock. I've turned Google upside-down trying to find a solution, but haven't had luck. Anyone know what the problem could be?
Click to expand...
Click to collapse
EVERY phone is different. Yours may not like the custom kernels you are trying to put on it.
z06mike said:
EVERY phone is different. Yours may not like the custom kernels you are trying to put on it.
Click to expand...
Click to collapse
I've never had this persistent of a problem until about two weeks ago, but prior to that I've been flashing ROMs/kernels since I got the phone in September. I'm not sure why it's having trouble now all of a sudden.
virsago said:
I've never had this persistent of a problem until about two weeks ago, but prior to that I've been flashing ROMs/kernels since I got the phone in September. I'm not sure why it's having trouble now all of a sudden.
Click to expand...
Click to collapse
Hmm strange. How far did you push the phone with the OC'ing?
z06mike said:
Hmm strange. How far did you push the phone with the OC'ing?
Click to expand...
Click to collapse
Nowhere. I've never OC'ed, but I have tried upping the minimum voltage. That didn't help either.
virsago said:
Nowhere. I've never OC'ed, but I have tried upping the minimum voltage. That didn't help either.
Click to expand...
Click to collapse
Upping the minimum voltage will cause you're battery life to suffer so I hope you meant undervolting.
reboot issues
virsago said:
I first had the problem with Carbon and Leantastic, then switched to KT, then flashed to Paranoid Android and its kernel, then to AOKP and its kernel. All of these configurations work fine until I dip below 50% battery, when I start to experience constant random reboots no matter what I do. I tried flashing back to stock then flashing back to custom, different kernels, different firmware, wiping caches/factory resets, etc. and nothing has fixed the problem. The only commonality I can think of in each configuration is that the ROM or kernel is CM-based, because the problem is not present in stock. I've turned Google upside-down trying to find a solution, but haven't had luck. Anyone know what the problem could be?
Click to expand...
Click to collapse
I had this happen with my Thunderbolt previously, rooted with Infected ROM. But it wasn't anything to do with the ROM. Happened when I got a "new" battery off EBAY. with the new battery, even though I charged it at one time for about 36 hours it continued to reboot randomly. Changed back to the old battery and it never did it again. Never really persued resolving it cause I just picked up the S3.
Hello.
I have a battery problem on my nexus 5. Seems like no matter what I do, my Nexus 5 discharges like it never sleeps. It first occured on Cataclysm with franco r32, I wiped everything and tried Cyanogen, same happened. Now with AOKP and Purity and Sanity - SAME PROBLEM.
What am I missing?
I am using multirom twrp.
Does anyone have any idea?
Thank you
miHah said:
Hello.
I have a battery problem on my nexus 5. Seems like no matter what I do, my Nexus 5 discharges like it never sleeps. It first occured on Cataclysm with franco r32, I wiped everything and tried Cyanogen, same happened. Now with AOKP and Purity and Sanity - SAME PROBLEM.
What am I missing?
I am using multirom twrp.
Does anyone have any idea?
Thank you
Click to expand...
Click to collapse
Unfortunately, as good as some on XDA are at troubleshooting, none of us can see your phone. Or what apps you have. Or battery stats. Or wakelock detection. I think you get the point. Just saying I have bad battery life is absolutely worthless without other details to explain what is going on. I'd suggest looking into the apps: Bettery Battery Stats and / or Wakelock Detector. Both of these, over the course of some time will be able to get you a better idea of what's up, or at least that and some screenshots posted here might be able to provide some more insight. If you can use that to track down some problem areas, it's possible the app Greenify can help hibernate it and keep it from making so much trouble.
es0tericcha0s said:
Unfortunately, as good as some on XDA are at troubleshooting, none of us can see your phone. Or what apps you have. Or battery stats. Or wakelock detection. I think you get the point. Just saying I have bad battery life is absolutely worthless without other details to explain what is going on. I'd suggest looking into the apps: Bettery Battery Stats and / or Wakelock Detector. Both of these, over the course of some time will be able to get you a better idea of what's up, or at least that and some screenshots posted here might be able to provide some more insight. If you can use that to track down some problem areas, it's possible the app Greenify can help hibernate it and keep it from making so much trouble.
Click to expand...
Click to collapse
I would tell you more about apps and wakelocks but the thing is I have been testing those roms i mentioned completely stock. I tried greenify with every rom, gsam reported 23min SOT with 7hours battery life when I checked (at 4% battery). So I tried another rom - I am on Vanir right now.. don't even have google account set up and still experiencing the same drainage.. 30% in 2hours idling..
Well, you could test till your fingers fall off, but if you don't share your findings, then how could we help you? I'm not saying that I can or can't help, but there are many here with a lot of experience with these issues and a breakdown of your findings might help someone point you in the right direction. Plus if there are other users in your situation, and they see your findings coincide with theirs, then that's more subject material to help troubleshoot. I've flashed dozens of roms and have not experienced anything similar, before or after sync. Not saying I haven't had battery issues, but usually brought upon by myself and playing with kernels and settings. Just haven't had that kind of drain through multiple roms and what not.