Why stock Roms have better battery life than Custom Roms - Defy Q&A, Help & Troubleshooting

Why stock Roms have better battery life than Custom Roms. I am on DEFY CM9. Froyo had a better life. I know that kernels are different. I wanna is there anyway to increase battery life like stock roms.

That may be your case. For me, CM9 has better battery life than CM7. Stock Froyo was so bad that I barely made it through the day with one charge. It's almost impossible to make a battery usage chart, since it depends mostly on independent variables (starting with the CPU, because each is different and not all can work with lower voltages, and ending with the main culprit, the user).
Trimis de pe Defy CM9

vap_66 said:
That may be your case. For me, CM9 has better battery life than CM7. Stock Froyo was so bad that I barely made it through the day with one charge. It's almost impossible to make a battery usage chart, since it depends mostly on independent variables (starting with the CPU, because each is different and not all can work with lower voltages, and ending with the main culprit, the user).
Trimis de pe Defy CM9
Click to expand...
Click to collapse
I hate Stock ROMs but motorola says. Defy has a standby back up of 400 hours but i am on CM9 it gives only 16hours of backup with minimal usage.

janeindiran said:
I hate Stock ROMs but motorola says. Defy has a standby back up of 400 hours but i am on CM9 it gives only 16hours of backup with minimal usage.
Click to expand...
Click to collapse
The quoted standby time is the maximum under 'ideal' conditions. Wanna check it, turn off your network data, no vibration, no video, no browsing, no music. I tested my defy+, and it lasted for almost 5 days on CM7.
Besides, battery consumption does depend on ROM and usage. A more performance oriented ROM will definitely use more battery. Good thing with custom ROMs, you can tweak the system as per your usage habits.

janeindiran said:
I hate Stock ROMs but motorola says. Defy has a standby back up of 400 hours but i am on CM9 it gives only 16hours of backup with minimal usage.
Click to expand...
Click to collapse
My friend, never trust the official values, given by the producer (this goes from phones to cars), regarding the battery life or consumption. They are recorded in an ideal environment, with strong signal, a certain value for the temperature and no usage at all. I get around 40 hours with CM9.
Trimis de pe Defy CM9

vap_66 said:
My friend, never trust the official values, given by the producer (this goes from phones to cars), regarding the battery life or consumption. They are recorded in an ideal environment, with strong signal, a certain value for the temperature and no usage at all. I get around 40 hours with CM9.
Trimis de pe Defy CM9
Click to expand...
Click to collapse
Got it. Thanks guys

Related

The differences in battery usage

So I have used the stock ROM, Sense and Cyanogen and now MCR 1.9. On stock, the display usage was always >40% in the battery stats. When I went to Sense and Cyanogen, the display usage was at the bottom of the list. Sometimes it was <10% or even 5%. I just went to MCR today, and my display usage is at like 73%. I haven't seen much difference in actual battery time between all of these so what gives? Why the differences?
Wrong section for this post... this is ONLY for dev stuff... this should be in Q&A or general...
craigacgomez said:
Wrong section for this post... this is ONLY for dev stuff... this should be in Q&A or general...
Click to expand...
Click to collapse
Ok sorry - i thought it WAS dev related since it was related to multiple ROMs and the way they handle power differently. Mods - if necessary, can you move?
hah2110 said:
So I have used the stock ROM, Sense and Cyanogen and now MCR 1.9. On stock, the display usage was always >40% in the battery stats. When I went to Sense and Cyanogen, the display usage was at the bottom of the list. Sometimes it was <10% or even 5%. I just went to MCR today, and my display usage is at like 73%. I haven't seen much difference in actual battery time between all of these so what gives? Why the differences?
Click to expand...
Click to collapse
A thought..
When you were on stock rom phone was new, you were "using" it all the time (waking screen up, scrolling thru screens/apps etc), hence the > 40%
By the time you were using sense/cyanogen the "newness" wore off, you weren't just waking it up for the hell of it anymore.
Since you only flashed MCR today, and those stats are based off of since last time unplugged, it's hard to make any real comparison with that 73% display usage. See how it averages out over time (assuming your phone use doesn't change much).
I can confirm the OP's observation. CM and Emomther's roms have very low display %s compared to Stock and MCR. I haven't used Paul's Desire rom long enough to confirm if it follows the same pattern or not.
I'm not sure what the difference is (persistent processes active in one rom, but not the other?), but the best battery life is from the MCR or Stock roms.
I've had the phone long enough, and changed roms often enough, to know that my usage habits have stabilized and the 'newness' is not the cause.
Yes, I agree. CM has much lower Display %age (<10%) than did stock (~50%).
Well.. maybe CM's way of reading the display power usage is 'better'? AMOLED should use less battery than LCD-screens...
I can confirm that the Desire ROM also lists display battery use much lower: 13% right now for me, and this has been consistent across all of Paul's alpha builds.
Don't think it actually improves battery life any, though, just different readings.
Been off the charger for about 2 hours and it says display usage of battery 69%
Anyone???????
I have also noticed this exact thing, the 'newness' theory is a good one exept I've had the phone for two months and am still using it excessively; not to mention all the new goodies to play with on each new ROM that gets flashed.
Would love to know what the cause of this is.
Based on that I don't think a certain ROM can make the display consume less battery (I can be wrong and I would like to) I understand these percentages a bit differently.
For me lower battery usage % from the display in one rom means that other parts are consuming more juice than in a stock rom, thus the % of said "parts" goes up and consequently the screen one goes down.
The higher the battery use % the screen takes (with the same phone usage of course) the better.
danimar1 said:
Based on that I don't think a certain ROM can make the display consume less battery (I can be wrong and I would like to) I understand these percentages a bit differently.
For me lower battery usage % from the display in one rom means that other parts are consuming more juice than in a stock rom, thus the % of said "parts" goes up and consequently the screen one goes down.
The higher the battery use % the screen takes (with the same phone usage of course) the better.
Click to expand...
Click to collapse
Very true.
It really seems like cell standby and phone idle are achieving much higher values when compared to the readings I remember getting from the stock ROM. Android system is at 16% I can't remember what it was stock.
Is there anyone running a stock ROM ?? What are your battery use values for light/moderate/heavy use?

Best ROM for battery life...

Well, I know that most ROMs claim to have better battery life and yada, yada, yada. But which one do you believe is the winner? I have only tried Fresh other than stock and I can't complain. But for you, which one do you feel offers the best battery life performance?!
Thanks in advance...
I got great battery life in DamageControl, but I dumped that for CyanogenMod.
This may not be the exact answer you were looking for, but I've found that using an underclocking kernel I get great battery life, even with the latest cyanogen nightly. You might want to try using SetCPU if you haven't done that already.
DamageControl
DamageControl v3.2.3 using DConfig with the profile set to battery Saver. My battery last for days (moderate use).
I believe t0ast3d de1ight has the best battery
Sent from my PC36100 using XDA App
All very subjective but I've been reading that Baked Snack is specifically geared towards battery life.
like above poasts state, rom does not matter, undervolt kernal + setcpu/phone setting settings does
cm heavy usage > 18 hours regular use 36 hours idle for days
Best I had was baked snack 9. 7 I got al most 24 hours on a charge with normal usage
Ava 2. 2v3 I. Got 18 hours
Cm6 barely 8 hours
sent with my evo from a secret place
Doofenshmirtz said:
DamageControl v3.2.3 using DConfig with the profile set to battery Saver. My battery last for days (moderate use).
Click to expand...
Click to collapse
I second this. I was using this setup before updating to official 2.2. I was getting about 5-6 hours of usage(I.e. When you're actually using your phone--Screen on browsing the web, using apps) plus around 20 hours of "Uptime" (standby, screen off).
I am getting equal or better battery life with the official 2.2 update. I am surprised I'm not seeing more people mention just how good battery life is with it.
BakedSnack with 3rd kernel did miracles for me
zeuzinn said:
I second this. I was using this setup before updating to official 2.2. I was getting about 5-6 hours of usage(I.e. When you're actually using your phone--Screen on browsing the web, using apps) plus around 20 hours of "Uptime" (standby, screen off).
I am getting equal or better battery life with the official 2.2 update. I am surprised I'm not seeing more people mention just how good battery life is with it.
Click to expand...
Click to collapse
I also have been having good battery life on the official pre-release, just about on par with what I had running baked snack 9.6, which underclocked a good amount for battery life. Very pleased with the new release, I haven't had any problems going from a fresh wipe to this update.
I would bet most people haven't really noticed how good the battery life has been because they've been busy trying to restore backups, apps, and test out the camera functionality.
Best battery life I had was DC 3.2.3 with Battery config, SetCPU w/ undervoltage kernel, JuiceDefender, and Autostarts configed. Got about 26 hours moderate usage. I still get excellent battery life using the same setup on CM6, around 20-24 hours.
I'm getting great battery life with the leaked, stock 2.2
I think it is almost impossible to prove a rom has the best battery life when there are so many options/tweaks that can be done to every rom and all phones won't necessarily act the exact same.
Choose a rom based on functionality and features that appeal to you and then figure out how to obtain the battery life you want through different tweaks/usage. They all can have great battery life.
DanBergundy said:
I think it is almost impossible to prove a rom has the best battery life when there are so many options/tweaks that can be done to every rom and all phones won't necessarily act the exact same.
Choose a rom based on functionality and features that appeal to you and then figure out how to obtain the battery life you want through different tweaks/usage. They all can have great battery life.
Click to expand...
Click to collapse
I believe people that have tried multiple ROMs can accurately assess which is better/worse in terms of battery life. Obviously there can be variations due to tweaks, apps, and usage, but it isn't difficult to get a sense of where you stand. I know I noticed a drastic increase coming from stock to Fresh.
akarol said:
I believe people that have tried multiple ROMs can accurately assess which is better/worse in terms of battery life. Obviously there can be variations due to tweaks, apps, and usage, but it isn't difficult to get a sense of where you stand. I know I noticed a drastic increase coming from stock to Fresh.
Click to expand...
Click to collapse
True, what I should have said was without testing yourself and keeping variables the same, you can't just take the word of others.

Battery life

I've noticed significantly better battery life on sense roms (especially senseless gingersense roms) as compared to AOSP roms. On AOSP, my cellular standby tends to be over 40% of my battery life, while on sense roms its under 3%. What would cause that?
I've tried evodeck 1.3, cyanogen 7.1, and cyanogen 7.2 rc1, with savaged zen, and tiamat kernels.
Also on AOSP roms, if I undervolt 50mv or more, my phone locks, but I can run the lionfish aggressive kernel completely smoothly.
As to sense roms, I've had the best luck on SOS N with universal aggressive lionfish 1.8
This disappoints me because I like the AOSP messenger, and AOSP dialer/contacts.
Is there a way to get the AOSP dialer, and AOSP messenger on a sense rom? I tried backing them up with titanium backup, and then restoring, but I have was having issues with the contact list, and when I opened the messenger from contacts (even with the HTC contact list), it wouldn't carry the number over, and I'd have to search for the person to text.
Try tommytomatoe's classic sense rom. I remembered one of his senseless roms had aosp dialer and contacts.
Sent from my PC36100 using XDA
After some looking, I found what you're refering to
however, there have been some important updates done since that build was released... these 2 things drew my attention
Completely rebase of apks
Completely re-optimized pngs
Wouldn't that cause some performance issues not having that done?
Would it be reasonable to take the newest sense build (supermagic), install go launcher on it, and remove rosie?
Dont know if this helps, but I have been running cyanogen 7.2 rc1 w/ tiamat for months now.
I like to run Smartassv2, and let SetCPU control my overclocking based on situations (charging, etc).
I dont see major dives in battery life, and have been very happy with the results.
My cpu usage isn't the problem. Its the cellular standby. I don't understand why its consistantly so rediculously high on AOSP roms for me.
TT's classic is equipped to be either Sense, non-Sense or a hybrid of the two.
It includes Launcher2, Stock GB launcher, as well as both Sense and AOSP dialer and contacts.
You could easily use it with GoLauncher and have even more options then.
As for the cell standby, are you speaking of the percentage shown in battery stats? Remember those are percentages and don't indicate that something is using "more" but that it is using a greater portion.
I have noticed that cell standby is usually at the top followed by display, then a few other things. What I can say is that Sense has many more operations and is probably just taking more battery than the cell standby, though your actual usage is probably the same. Can you say for sure that your battery life is worse on AOSP? I know I cant beat CM 7.2 with stock kernel and all stock CPU settings. Believe me I've tried it all.
As of right now, I'm at 55% display, 20% cell standby, 6% facebook, 5% wifi, 4% google services, 3% android system, 3% browser, 2% phone idle, and 2% android OS. I'm 150mv undervolted, using 128-384mhz ondemand screen off, and 128-576mhz screen on with smartass v2.
Most of the time, I'm over 75% display usage and under 3% cellular standby, but I'm in an area with near zero signal right now. When I had cyanogen 7.2 RC1 with the tiamat kernel (which is an undervolted cyanogen kernel), I was about 40% display, and 40-45% (sometimes even past 50% for cellular standby).
The display, even at 5% brightness, is the biggest draw, by far on sense, and comes in 2nd on AOSP.
That would conflict with your idea that it's sense that is burning my battery up (especially since I'm using sense-removed roms that are sense based)
I'm using swagged out stock 2.0.9 N, which comes by default with the go launcher, instead of sense, but uses sense kernels.
As of right now, I'm at 55% display, 20% cell standby, 6% facebook, 5% wifi, 4% google services, 3% android system, 3% browser, 2% phone idle, and 2% android OS. I'm 150mv undervolted, using 128-384mhz ondemand screen off, and 128-576mhz screen on with smartass v2.
Most of the time, I'm over 75% display usage and under 3% cellular standby, but I'm in an area with near zero signal right now. When I had cyanogen 7.2 RC1 with the tiamat kernel (which is an undervolted cyanogen kernel), I was about 40% display, and 40-45% (sometimes even past 50% for cellular standby).
The display, even at 5% brightness, is the biggest draw, by far on sense, and comes in 2nd on AOSP.
That would conflict with your idea that it's sense that is burning my battery up (especially since I'm using sense-removed roms that are sense based)
I'm using swagged out stock 2.0.9 N, which comes by default with the go launcher, instead of sense, but uses sense kernels.
I'm barely using any power on my CPU, due to the heavy undervolt and underclock. This issue is purely cellular connection based, which is significantly worse on AOSP for me.
I didn't say Sense was using more battery, I said it has more processes.
The question is does your battery actually last longer on Sense vs AOSP?
Your battery gets used, and each process uses a percentage. When there are less processes the percentages on each are higher, though they still only equal to 100% of your battery.
Also, the different roms use different methods of collecting those stats and display the differently. Just how AOSP displays signal based on the actual dbm and sense displays call quality.
Sent from my PC36100 using xda premium
I do notice significantly slower battery drain with sense. I'm not just staring at measurements.
That MAY have to do with the fact that I'm using setcpu on sense, while setcpu doesn't work properly with most AOSP kernels, due to HAVS.
Honestly, I have never had such a jitter free experience either. Every rom I've tried felt slow to me except SOS N... Maybe they are working some kind of wizardry
Angelus359 said:
I do notice significantly slower battery drain with sense. I'm not just staring at measurements.
That MAY have to do with the fact that I'm using setcpu on sense, while setcpu doesn't work properly with most AOSP kernels, due to HAVS.
Honestly, I have never had such a jitter free experience either. Every rom I've tried felt slow to me except SOS N... Maybe they are working some kind of wizardry
Click to expand...
Click to collapse
HAVS has nothing to do with the cpu speeds so its unlikely that its not compatible (i know because i used it all the time on both aosp and sense) all HAVS does is let you change the voltages of your cpu. but if it isn't working well i would recommend using the system tuner app (free version in market) and over/under clocking in that. its much better from what i have observed. when you do it click boot settings right next the the sliding cpu speed bar and make it re apply cpu setting via init.d script and reboot. also try using the mason g .15 test build kernel. im currently using it in miui and i haven't experience battery like this since tiamat 3.3.7 (the god of tiamat kernels) and the performance is amazing!
have you been calibrating the battery? and i dont mean just wiping battery stats i mean charging it fully (at night/evening) then letting it go over night and then you really will stretch out the battery life. I have seen 30 plus hours on decks 1.3 with tiamat kernel.
if battery calibration was an issue, wouldn't it still be an issue when I flop back to a senseless sense rom?
I always have better battery life on Sense ROMs too, even with Rosie active still. I haven't tried SOS N yet because Go SMS doesn't behave well with the poor reception at my house.
Maybe the improved performance has to do with go launcher, zipalign, odex, and the pngout improvements
Maybe its the SIO scheduler... who freaking knows...
SOS N doesn't natively use go SMS... it uses HTC messenger, and HTC dialer, with go launcher
Angelus359 said:
As of right now, I'm at 55% display, 20% cell standby, 6% facebook, 5% wifi, 4% google services, 3% android system, 3% browser, 2% phone idle, and 2% android OS. I'm 150mv undervolted, using 128-384mhz ondemand screen off, and 128-576mhz screen on with smartass v2.
Most of the time, I'm over 75% display usage and under 3% cellular standby, but I'm in an area with near zero signal right now. When I had cyanogen 7.2 RC1 with the tiamat kernel (which is an undervolted cyanogen kernel), I was about 40% display, and 40-45% (sometimes even past 50% for cellular standby).
The display, even at 5% brightness, is the biggest draw, by far on sense, and comes in 2nd on AOSP.
That would conflict with your idea that it's sense that is burning my battery up (especially since I'm using sense-removed roms that are sense based)
I'm using swagged out stock 2.0.9 N, which comes by default with the go launcher, instead of sense, but uses sense kernels.
I'm barely using any power on my CPU, due to the heavy undervolt and underclock. This issue is purely cellular connection based, which is significantly worse on AOSP for me.
Click to expand...
Click to collapse
Dude, USE THAT SWAGGED OUT STOCK!
Angelus359 said:
150mv undervolted, using 128-384mhz ondemand screen off, and 128-576mhz screen on with smartass v2.
Click to expand...
Click to collapse
For real? Save up some loot and get an extra battery and an outlet charger and you'll only have to worry about charging both batteries at night -- one in the plugged in phone and one in the outlet charger. Crank it up to 1ghz, Install JuiceDefender, You will get 3-4 hours of on screen time (autobrightness) out of each battery, so even if you are putting the phone through heavy use you will still be good throughout the day.
My daily is SOS X/ODEX , Underworld .5, 128/1152 smartassv2, no undervolt, no profiles. I use juicedefender ultimate. With heavy use i have to change batteries throughout the day, but with moderate use, the battery lasts 18ish hours. I wish I had screenshots, but i don't, the phone is fully charged right now so taking one now won't do much.
http://www.amazon.com/Battery-Travel-Charger-Incredible-Verizon/dp/B003ZBWLW6/ref=pd_cp_cps_1
Juice defender annoyed the crap out of me, and didn't do what I wanted, since I often go a long period of time with ALL data completely off. I'd rather have complete manual control.
Overclock is pointless to me, since even at 576mhz, my evo doesn't feel slow to me. Higher clocks just aren't helping. I have everything else optimized enough that any CPU delay becomes irrelevant. I had it at 768mhz, and lowered it to 576mhz, because I couldn't feel a difference.
I had issues when I used to use governors that were not smartassV2 but once I got that, there was no purpose to me having the higher on screen clock.
Thats what happens when you have SOS N with components stripped out that you don't use
Autobrightness actually screws your battery up by putting too much load on your CPU with polling
I still get a full day of charge on SOS N, I just don't on AOSP. I made this post trying to figure out why I'm having issues with AOSP.
I'm trying smartass from 128 to 768 with ideal freq set to 384... Works much better!
You said you don't use set CPU with aosp cuz of the havs kernels.
1) don't worry about the havs, not an issue
2) you don't need set CPU with aosp roms, control is built into the settings
sent from 2yr old Evo on ICS
I use setcpu for screen off profiles.
Can't do that with stock.
I recently tried smartass, setting ideal, awake, and sleep freq to 128 (works surprisingly well), and screenoff, ondemand 128-285
Seems to work well.

[Q] best rom for battery life?

I will be going away soon to a location where i won't have access to any Mains , any advice on what rom offers the best in terms of battery life?
http://forum.xda-developers.com/showthread.php?t=1752221
Battery Life Comparison of several Roms
Defy ICS- In your face MOTO
the post from above link does not mention miui series.
in my opinion, wiui 2.5.27(the stable one) does a good job also.
Im on ics from quark and when not doing mutch with my phone it takes like 10 percent a day with stock cpu clock, wifi off.
Sent from my MB526 using xda app-developers app
Questions go in the Q&A section
You should consider using either Walter's MS2Ginger rom or use Defy+ CM7 with walter's kernel. I see that if left alone the phone drains at approx 3% every 8 hours... so standby time increases. I get 2-3 days with moderate use. Of course if you're a heavy user (wifi, 3G, games etc) then it won't matter much.
defydent said:
You should consider using either Walter's MS2Ginger rom or use Defy+ CM7 with walter's kernel. I see that if left alone the phone drains at approx 3% every 8 hours... so standby time increases. I get 2-3 days with moderate use. Of course if you're a heavy user (wifi, 3G, games etc) then it won't matter much.
Click to expand...
Click to collapse
Not bad! I cant get out of my defy more than 5 - 6 hours, and i am using it for 1 hour max (browsing). And phone is heating up when badly when im using it or charging. I'll try rom, that you suggested, cuz now im on cm9 epsylons 14.07 buld...

A good stable rom for battery backup?

Hi all
I thought I'd ask the experts about what are in your opinion some good roms for battery backup?
I'm currently on stock MIUI Global 11.0.5.0 (PFGMIXM) but I'm not much satisfied with the battery backup (5-6hours SOT).
I need some stable firmware since I use my phone mostly for work, no gaming, no social media, just phone calls, messaging and some light youtube usage.
Thanks!
Ion OS is brilliant, especially for battery - sourceforge.net/projects/i-o-n/files/device/xiaomi/lavender/ Around 10-11 hours SOT.
Anyone can compare MIUI vs Xiaomi.eu VS Pixel?
flaviopac said:
Anyone can compare MIUI vs Xiaomi.eu VS Pixel?
Click to expand...
Click to collapse
Miui right now just being laggy and jerky sometimes with animation, thus pixel based cutom rom just some having like miui and some is dont. I prefer evolution x on latest build, which smooth operation per my multitasking usage(on stock kernel obviously), whilst the battery just doing better other than resurection remix, pixel experience etc.
flaviopac said:
but I'm not much satisfied with the battery backup (5-6hours SOT).
Click to expand...
Click to collapse
Could you be more specific about how long the battery lasts, I mean that if you are using your phone for like 4-5 days then 5-6h of SOT is quite normal for this phone but if you meant just one day then it should be about 10-11h of SOT as there will be less energy consumed by things like cellural network.
I had pretty good battery backup with POSP by AmulayaX but i found out that slow-motion isn't working so i switched to StagOS (unofficial EAS by Jimgsey) and i like this rom but i have some small issues and i consider switching to official.
cieciu89 said:
Could you be more specific about how long the battery lasts, I mean that if you are using your phone for like 4-5 days then 5-6h of SOT is quite normal for this phone but if you meant just one day then it should be about 10-11h of SOT as there will be less energy consumed by things like cellural network.
I had pretty good battery backup with POSP by AmulayaX but i found out that slow-motion isn't working so i switched to StagOS (unofficial EAS by Jimgsey) and i like this rom but i have some small issues and i consider switching to official.
Click to expand...
Click to collapse
5-6h SOT in 2 days. I'm not playing games I only use my phone for calls, whatsapp, emails and web navigation.
I'm on dual sim though.
I could never achieve 10h SOT in stock. Any hints for some good rom that can do that?
Thanks
flaviopac said:
5-6h SOT in 2 days. I'm not playing games I only use my phone for calls, whatsapp, emails and web navigation.
I'm on dual sim though.
I could never achieve 10h SOT in stock. Any hints for some good rom that can do that?
Thanks
Click to expand...
Click to collapse
Someone already suggested you to try Ion Official for Redmi Note 7 as it is EAS & feature rich also. But for more you can try Bliss ROM as well. Last but not the least LineageOS 17.1 Official. I'm currently using Bliss ROM. It is the best in all others upto now i have tried.
flaviopac said:
5-6h SOT in 2 days. I'm not playing games I only use my phone for calls, whatsapp, emails and web navigation.
I'm on dual sim though.
I could never achieve 10h SOT in stock. Any hints for some good rom that can do that?
Thanks
Click to expand...
Click to collapse
U can't reach 10 h SOT by 2 days on battery.
Calculate 0,5 %/h idle drain
2 days 48h - 5 hours Active drain = 43 h idle time
43 x 0,5 = 21,5 %
so round about 20% battery is lost in idle time
so 80 % for active drain.
Charging battery at 15%
80-15 = 60% left for active drain
On mostly all roms i tested i get an active drain by 10% per hour
Wud be for u 6 hours SOT
Seems normal drain with ur MIUI
But aosp roms are so much faster and mutitasking so much better compared to MIUI.
I only got 3 GB model and there no way back to MIUI
I gave PixelE+ a try but I'm experiencing less battery backup than stock (and some random freezes too).
I'll try ION or Xiaomi.eu in the coming days.
Meanwhile what about changing kernel? Any good recommendations please?
I gave PixelE+ a try but I'm experiencing less battery backup than stock (and some random freezes too).
I'll try ION or Xiaomi.eu in the coming days.
Meanwhile what about changing kernel? Any good recommendations please?
for me changing kernel isnt a game changer
its all about SOT, screen brightness for sure and good working deep sleep.
Screen is biggest power consumer.
Kernel maybe change covernor and undervolt cpu. sure this brings a lil power. but trust me it makes just a very lil differece. u cant compare ur drain because ur usage isnt same.
if wanna judge a kernels power consumtion u have to do all the same.
watching 2 hours youtube, play same game aso with same screen brightness with same wifi state aso.
i bet theres no "big" difference.
matthias1976 said:
for me changing kernel isnt a game changer
its all about SOT, screen brightness for sure and good working deep sleep.
Screen is biggest power consumer.
Kernel maybe change covernor and undervolt cpu. sure this brings a lil power. but trust me it makes just a very lil differece. u cant compare ur drain because ur usage isnt same.
if wanna judge a kernels power consumtion u have to do all the same.
watching 2 hours youtube, play same game aso with same screen brightness with same wifi state aso.
i bet theres no "big" difference.
Click to expand...
Click to collapse
I'm currently on Pixel and I can make 4h SOT in 2 days. I don't play games or use YouTube. Just phone calls, whatsapp, browser, emails and I'm always on dual sim.
With stock MIUI I used to reach 5-6h SOT in 2 days so with my personal usage Pixel is worse in battery life compared to stock MIUI.
I'm thinking of trying something like Xiaomi.EU now since it's based on MIUI stock...
As i say, for me there are just few differences in battery life from rom to rom.
Miui is slow and bloated compared to non miui based custom rom.
When u just installed new rom u have more drain cause of trying out the rom. U have more usage compared to ur old rom. Lets get rom settle for a while before judge.
At least all rom take power. All rom need display. I think display always takes same power in every rom when u got same brightness.
At home in ur wlan mostly watching YouTube u get better battery (maybe under 8% per hour drain maybe less) than navigating in the sun with mobile data (cost 12% per hourand more) battery
matthias1976 said:
As i say, for me there are just few differences in battery life from rom to rom.
Miui is slow and bloated compared to non miui based custom rom.
When u just installed new rom u have more drain cause of trying out the rom. U have more usage compared to ur old rom. Lets get rom settle for a while before judge.
At least all rom take power. All rom need display. I think display always takes same power in every rom when u got same brightness.
At home in ur wlan mostly watching YouTube u get better battery (maybe under 8% per hour drain maybe less) than navigating in the sun with mobile data (cost 12% per hourand more) battery
Click to expand...
Click to collapse
I'm with you however I'm currently on Xiaomi.eu 11 (debloated) and battery backup is much better than Pixel. I hit 6h SOT on the first run, expected to improve in the coming days after a few charging cycles.
Same usage, the exact same apps running.

Categories

Resources