General Run times / SOT with semi-active or mostly passive use - Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40

I know that many of you are satisfied to get through the day with one battery charge because you use the device permanently. At night, the smartphone is connected to the charger and that's it. If you belong to exactly this group of users, you can save yourself the further reading
Well, I am a bit different in this aspect. I sit in front of the PC for most of the day and use the smartphone comparatively rarely. I want to be reachable by phone, but I don't need to chat via Messenger all day. When I have time, I turn on WiFi or mobile data and retrieve messages manually. Generally, I only turn on all needed connections when I'm actively using them - the only exception is cellular for calls and text messages, that only gets turned off at night with flight mode. I also don't watch Netflix & Co via smartphone, in general I rather rarely watch videos on the smartphone. I also do not need to play games with the smartphone and if I do, then Sudoku or similar is enough for me For all these applications I have a PC, large monitors and an even larger TV as screen. Sounds oldscool, and yeah, that's me
I also have relatively few apps installed - only the ones I actually use. When possible, I use the mobile versions of websites rather than installing an app for them. This has the advantage that I only need one app for many things, and I need to keep it up-to-date: a browser.
In short: I am not interested in benchmark numbers of CPU/GPU. I need a reasonably good camera and a not too lame CPU for post-processing. In my free time, I am usually in the outback for several days/weeks without a power source (well, I have a small powerbank, of course), so a long runtime is mandatory. I want an enduring and reasonably smooth running phone that I don't have to charge every day or even every two or three days.
When I (not entirely voluntarily) switched from the F1 to the F3, I expected a lot because of the OLED screen and the larger battery. However, I had to realize that I have problems to even come close to the runtimes of my optimized F1.
I started logging the battery charges of the F1 purely out of interest.
A few relevant averages from 119 logged charges (in 787 days) are as follows:
Run time: 109 hours (so about 4.5 days).
SOT: 8 hours
Phone calls: 2.5 hours
I continued the log with the F3. The averages from 30 logged charges (in 111 days):
Run time: 62 hours (so just over 2.5 days).
SOT: 6.5 hours
Phone calls: 1.5 hours
Of course, AOD, pocket mode, DT2W, light sensor and all that stuff is disabled and I only use dark themes and 60 Hz. Just like on the F1, I don't use any Google services on the F3. Practically nothing changed in my usage behavior. However, the results are mighty disappointing...
I experimented a lot, other kernels, other ROMs, but it was practically the same/similarly bad everywhere. Now I'm running HavocOS with its own Kernel for the time being, because the idle consumption seemed to be lower than with other ROMs/Kernels. However, I made a few tweaks (all apps are available in the F-Droid Store):
1. Smartpack Kernel Manager: I lowered the boost clocks of the prime core and of the 3 main cores by a few 100 MHz.
2. Konabess: I undervolted the GPU and flashed the modified Kernel.
3. SuperFreeze: Most apps are frozen when the screen is locked. There are a few exceptions (Tidal, OsmAnd+, AntennaPod, etc.) that are allowed to run in the background until I force them to stop.
4. Autostart: I disabled the start triggers of almost all apps to keep closed apps closed.
Of course, my F3 does not break any benchmark records with this, but that is not my point. Everything still runs smoothly. With these things in place, I'm finally getting these averages from 3 charges:
Run time: 83 hours (so about 3,5 days)
SOT: 9 hours
Phone calls: 2 hours
That's still far from my original hope, but at least it's a significant increase. I very much hope that I have not yet reached the maximum.
TLDR
I would be interested to know if there are any people here at XDA who are similarly "passive". And if so, how satisfied they are with the F3 and/or what settings/tweaks they have made to achieve long runtimes and good SOT at the same time. I would be pleased about a few experiences and comparison values

I know this is probably the opposite of what you want to read, and I'm just a simple active user of my phone, but I'd say, don't get too frustrated with battery life / SOT. I'd say it just is what it is.
If you adjust your phone to as much battery saving as possible, it's probably not fun, because you have so many cool awesome features on the Poco F3, like 120 Hz and MEMC for YouTube etc...
I'd say if you want to keep Bluetooth on to receive notifications and calls on your smartwatch then just go ahead.
Instead of going for maximum battery saving, you could go for a balance of enabling some of the cool features and ditching the ones you don't want as much, like AOD or a 2. sim-card..
I don't know if this reply is any helpful, probably not, but what gives シ
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

dreamytom said:
I don't know if this reply is any helpful, probably not, but what gives
Click to expand...
Click to collapse
Haha, thanks for your answer
Indeed, I have set up the phone according to my needs and wishes and I am disappointed that contrary to the logical assumption (that a larger battery and an OLED display promise longer runtimes), the runtime has decreased significantly compared to the F1.
I'm not limiting myself, if that's how you understood my post. I have to limit the phone and turn off all the unnecessary stuff, because a smartphone is more a useful tool than a toy for me. I don't need permanent location tracking. Most of the time I know where I am and where I want to go. If not: It takes 2-3 seconds for the GPS to find me after switching on... I don't need 120 Hz, because I don't see any difference in my usecases... Beyond that, I don't need a smartwatch either. I'm glad I don't have to wear a watch anymore since there are mobile phones.... And after all, I don't need to be permanently available via chat. Whoever has something important to say can call me. Otherwise this one can wait for an answer... When my smartphone is locked, so the screen is off, it should be quiet, unless it is important or I explicitly want to get notified. If it's constantly blinking, vibrating or jingling, I would never get to work
I know, it sounds not very trendy: Many of the "innovative" features bring solutions to problems that I didn't/don't have.

Good idea. When I used mi 9 lite or poco x3 nfc I was able to use my phone from 3 to 5 days without chargeing. Now I have poco f3 and I have to change something. Ok, I use only LOS from years on all my devices ... maybe time to change ...
My way to manage battery was and is now is a script in Automagic. When I lock the screen I turn off interfaces like wifi, mobile data, locatin/gps, bluetooth, nfc, (cellular in tablets without card) and turn on when screen is unlocked. Never use airplane mode for cut LTE signal and smses. When the phone is locked more than 60 minutes I turn on battery saver mode.
Of course , each device has predefined which interface can be turned off ... Autostart I control in SDMaid. If I cut init signals app will not be able to start and use energy in background in exception I will call it. (The games are the best example to want do something in background what is absolutely not needed for me) I never freeze any apps neither overeclock cpu nor undervoltage gpu.
This what I see on my new F3 is no power after 40 hours of work. I found wakelock in LOS but blocking it in Optimus does not change many - I see deep sleep but 1%/h night lost is not very big difference when I had no deep sleep in LOS kernel. Baallam is empty of this problem but 1%-0.9% is the same result.
I have to say goodbye to LOS , I afraid.
Today I have active drain 8%/h, idle drain 0.86%/h (LOS 18.1 and baalam).

To be honest, I am OK with the battery backup of the F3. With all the modifications I could now at least manage to equalise the running time of the F1 (with LOS 16, Android Pie). But considering that the battery of the F3 is 500 mAh bigger than that of the F1, this is somehow quite bad.
Now, however, I have recently received a battery dump of my old F1, with Havoc 4 (Android 11, without major optimisations). The analysis shows a significantly lower runtime and at the same time a significantly lower sum of call time and SOT as it was with Android 9. This suggests that Android itself is a major contributor to the fact that consumption has increased significantly in recent years (with the same hardware).
@Tomek0000
I had the problem that the consumption in idle mode suddenly increased massively. After each restart everything was fine, but at a certain point the consumption was like hell. Although I could never find the cause, I found a solution: I was able to prevent this by freezing most of the apps as soon as I turn off the screen (with SuperFreeze). Now the idle drain keeps low over the whole runtime.
The last run with the F3 (Havoc 4.14, NOKernel 2.3 battery, CPU underclocked, GPU undervolted):
Run time: 158 hours (about 6.5 days).
SOT: 9 hours
Phone calls: 1 hour

I have played with havoc yesterday and have results from the night. I moved my card to old x3 nfc and night lost of energy is 0.25% without freezing, down voltage or airplane mode. The havoc in F3 eats 1% of battery during each night hour and it was without using gsm card suppoort! I thought, havoc is better in this subject and additionaly has adaptive charging and wakelock blocker. No it is not better. Adaptive charging does not work and wakelock blocker blocks but not wakelocks. I did not find wakelocks on its list. I do not know what is on this list ... it is all but not wakelocks.
Ok I invested time in havoc and I will play with it some time, but card will be in x3, and ... LOS is better in the first sight.
I know, you will suggest additional apps (freezing ...) , but I will use it when I will decide which custom rom will be the best for it.
I think, I made a big mistake when I decided to buy new smartfon with snap 8xx. It should be 778 or 780. This is excelent lesson for the future.
Havoc has the same wakelock problem like LOS and it has to be result of MIUI 12.5.6.0 using as a base. Ironic ... build in wakelock blocker does not see it at all. When I will finish with Havoc I will have to use older MIUI as a base.

Let me know how you's go with this. I seem to have this same wake lock regardless of which ROM I use, losing 7-8% battery OVERNIGHT is far from normal.
I'm currently on HelluvaOS "HOS" 12 on base V12.5.6.0.RKHMIXM, as far as I recall the issue was present on older bases back from when I bought my F3 on launch.

The way to fix the wakelock is to block it. Havoc has not working wakelock block. You have to use optimus or ballam kernel. The both have working blocker. Optimus will block it but ( a supprise) ballam does not have this wakelock problem. This is my experience from time of use LOS 18.1. I tested N0Kernel 2.3 too, but it doubling energy use and does not have blocker.
Did you write, the c440000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smb5 problem exists from earlier versions of MIUI ? Is not only in 12.5.6.0 ?

Vulnerability said:
Let me know how you's go with this. I seem to have this same wake lock regardless of which ROM I use, losing 7-8% battery OVERNIGHT is far from normal.
I'm currently on HelluvaOS "HOS" 12 on base V12.5.6.0.RKHMIXM, as far as I recall the issue was present on older bases back from when I bought my F3 on launch.
Click to expand...
Click to collapse
Does this wakelock exists in earlier miui versions? Which version number has the oldest you tried?

Tomek0000 said:
I think, I made a big mistake when I decided to buy new smartfon with snap 8xx. It should be 778 or 780. This is excelent lesson for the future.
Click to expand...
Click to collapse
I totally understand!
The thing with these new Snappys is that although they might be more efficient than their predecessors, this advantage is thrown overboard by constant clocking at the limit. Unfortunately, a modern Snappy from a smaller series is not necessarily more efficient. They all seem to be maxed out...
Tomek0000 said:
I do not know what is on this list ... it is all but not wakelocks.
Click to expand...
Click to collapse
You cannot block every system/kernel wakelock because your system would break then.
Regarding a full cycle, my phone has
1.5 to 11 app wakelocks per hour
1500 to 4000 kernel wakelocks per hour
- depending on what I've done during the cycle.
The number of kernel wakelocks sounds a lot at first, but they do not necessarily mean to effect the idle drain of your phone. The cycle I mentioned above, shows 2,276 app wakelocks and 266,641 (!) kernel wakelocks in sum (runtime 158h). Both, the app wakelocks and the kernel wakelocks did wake the phone for about 2 hours each.
The exact wakelock you mentioned (c440000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smb5) didn't show up on my device at all. I've installed the latest EEA firmware (12.5.8).
Did you make a clean flash with formatting all data?

I have read more and this wakelock could be connected to ACC app. If you do not control your charging process maybe you do not see this problem. I do not use ACC in havoc , but initiated adaptive charge and adaptive battery. I have to decide if I use 12.5.8 or like LOS requires 12.5.3.

Yep, I don't use adaptive charging. I charge my F3 every 4 days (in average) with 12 W. The battery is full in less than 1.5 hours. That's ok... And I always charge up to 100 %. Within the >11 months I own the F3 I charged it about 100x (84 of which are protocolled; 34 of which with a full bugreport incl, battery dump).
I don't see the benefit of smart/adaptive charging. All my previous phones lasted 5 years or more with always full charging - it never was the battery which gives up. I still use my ZUK Z1 as mp3 player (always power on, about 1h per day active usage as mp3 player) and I have to charge it once in 2-3 weeks...
So, adaptive charging doesn't work in Havoc? Then turn it off and you're rid of the wakelock!

I always use battery charge limit but it did not worked with LOS on F3. Maybe when I change kernel it will start working. I use it for keep battery in good condition for additional 25% of live time. I be voice informed by script about 30% or lower and I connect charge for all night and charge will stop when level will be 85%. And it was enough for 3-5 days of using my previous smartfons.
I reinstalled 12.5.8 and April LOS and did not install ACC. No wakelock, very good power consumption during screen off.

In my experience, exposing the battery to heat/cold and/or charging/discharging excessively quickly is much more damaging to the battery than charging it gently up to 100 % and then unplug. But, of course, if you charge your phone overnight and it's plugged for hours, it might be useful to stay below 100 %.
However, in our case (charging only once every few days), it will probably be the lack of updates/features that drives us to switch the phone...
Tomek0000 said:
I reinstalled 12.5.8 and April LOS and did not install ACC. No wakelock, very good power consumption during screen off.
Click to expand...
Click to collapse
Great. Would you mind writing here how long your phone last on one cycle?

One cycle ? I am not sure how to check it. 95% deep sleep and FKM report 0.35%/h nightly lost using LOS kernel. Previous result was ~1.8% with ACC installed.

Tomek0000 said:
Does this wakelock exists in earlier miui versions? Which version number has the oldest you tried
Click to expand...
Click to collapse
I've had the phone since day 1 and have had this idle drain issue since. The oldest I've tried is whatever shipped with the first batch of phones

Interesting. I found this wakelock in LOS if I installed Acc and in Havoc when activated adaptive charge. If I do not use it , the problem does not exist. The use of Battery Charge Limit does not activate the wakelock too.
This is very interesting like kernels work. If the wakelock was a problem, the best result was with balaam kerenl. When no problem , the balaam seems to be the worst.

esszett said:
2. Konabess: I undervolted the GPU and flashed the modified Kernel.
Click to expand...
Click to collapse
Could you share your definition file ?
I used this app and idle lost jumped 250%.
Do you use version 0.16 or older?

Tomek0000 said:
Could you share your definition file ?
I used this app and idle lost jumped 250%.
Do you use version 0.16 or older?
Click to expand...
Click to collapse
I use 0.14b... I only changed the voltages of the existing frequencies, saved and then flashed the modified kernel.
305 MHz --> MIN_SVS
400 MHz --> MIN_SVS
441 MHz --> MIN_SVS
490 MHz --> LOW_SVS_L1
525 MHz --> SVS_L0
587 MHz --> SVS_L0
670 MHz --> SVS_L2
Anyway, that doesn't affect the idle consumption at all, of course. It should only affect the SOT.
esszett said:
1. Smartpack Kernel Manager: I lowered the boost clocks of the prime core and of the 3 main cores by a few 100 MHz.
Click to expand...
Click to collapse
BTW: In the meantime I used FKM for that. But i stopped underclocking, because several tests with my phone showed me that underclocking is more or less useless. Although a significantly lower frequency was reliably applied, this did not reduce the consumption or at best minimally - but without any influence on the runtime... I now have uninstalled both Smartpack Kernel Manager and FKM.
I still only understand the consumption of the F3 to a very limited extent. While I now have the consumption in idle under control, the consumption remains very high during light and medium loads. For example, when I make calls with the F3 with LTE, the consumption is 1.5-2x as high as with the F1 with LTE. I just don't know how to lower the consumption

Thank you. I used config file from thread about optimum setting for overclock and downvoltage. It has to be not optimum solution.
Could you write your consumption during light and medium load for F1 and F3 ? (For compare possibility)
Have you ever thought about using runinbackgroundper1.5.apk ? I found it this week .
[APP][Root][7.0+]RunInBackgroundSetter v1.4 :: [25.07.2017]
Few hours ago explainAndroid posted article on xda main page onto how to use android's hidden RUN_IN_BACKGROUND permission to restrict app's background behavior. I made an app for that. Here's link to original article...
forum.xda-developers.com

Related

After 2 days of owning a defy ... my thoughts and a n00bs guide

I only got the phone 2 days ago, coming from a Nokia 5800 (which I loved), its worlds apart and a very worthy upgrade. I'm totally new to Android and everything about it, but I'm fairly sure I've digested enough information over the past 2 days to set my phone up properly.
So for any other n00bs, this is some of the info I've setup on mine.
Rooting
This is a must, the z4root (1.3 version) app will take care of your permanent rooting needs. Be sure to leave the "USB Debugging mode" on for ever.
Blur
Love it, keep it, I don't think there's any performance hit with it running. But if you don't like it, don't go to the lengths of removing all the apk's manually - just don't register/sign-up when the phone is very first turned on (or if the phone is set-up, then you can backup with TB and factory reset the data, but don't set-up Blur).
Overclocking and undervolting (ie. Battery!)
800MHz doesn't *quite* cut it, the phone is a little laggy and unresponsive. The app to get first is SetVSEL (on Android market), I've got mine setup and stable with:
300MHz / 26
600MHz / 34
1100MHz / 58
And a priority of 60%. Then enable the setting to limit to VSEL1 when the screen is off. A priority any higher than 60% makes the phone really lag when trying to turn the screen back on/answer calls etc. from an idle state.
This took the phone immediately from a 5hr maximum battery life on idle to over 13 hours (still not impressive, but miles better!).
Then upgrade the ROM to the JIT enabled version http://forum.xda-developers.com/showthread.php?t=893291
Backing Up
Titanium backup pro - worth it, get scheduled backups set up and sign up for a free dropbox account (link - http db.tt/fxOD4Zf) for online backup storage.
Must buy/install apps
1 VPN (VPN password saving/connect tool)
AdFree (Ad-blocker)
Angry Birds (Game)
Astro (File manager)
Barcode Scanner
ConnectBot (SSH client)
DropBox (Online storage) link - http db.tt/fxOD4Zf
Google Earth
Facebook
Google Goggles
Last.fm (Music streaming)
Layar (Augmented reality app)
PocketCloud (MSTSC/RDP client)
Quadrant (Benchmarking tool)
ROM Manager
SetCPU (although not neccessary with SetVSEL, but it does offer a little more fine-tuning)
ShopSavvy (Barcode scanner / price comparison tool)
Skype
Sports Tracker
Spotify
Stability Tester (Good for making sure VSEL voltages are stable)
System Monitor (Fairly basic overview of system status)
System Recovery (not available on Android Market) LINK http goo.gl/SSMpE
Titanium Backup Pro
Twitter
Vehicle Light
Voice Caller ID
Voice Recorder
z4root - LINK http goo.gl/CuRgz
Impoving battery
Disable live wallpaper
Disable smart screen brightness and manually reduce
Lower CPU voltage
Set low CPU speed when screen is off
Enable data saving
Disable GPS when not in use
Handy links
http://forum.xda-developers.com/showthread.php?t=893291
http://forum.xda-developers.com/showthread.php?t=833953
http://forum.xda-developers.com/showthread.php?t=853674
Thank you for the guide, especially the setvsel freqs.
5 hour battery life on idle... that's why people don't like Blur!
I don't use any Blur widgets at all - although I have't removed them - and on the stock ROM will easily get 2 days battery life on idle, hell I can get 2 days with moderate usage!
milesg said:
5 hour battery life on idle... that's why people don't like Blur!
I don't use any Blur widgets at all - although I have't removed them - and on the stock ROM will easily get 2 days battery life on idle, hell I can get 2 days with moderate usage!
Click to expand...
Click to collapse
Agree!
If you are coming from U.S. t-mobile, there is no way you can bypass Blur, other than flash to "foreign firmware".
Once you registered and use Blur, you got bunch of useless app running on the background, news/weather/social and etc that can NOT be stopped, unless you root and remove them. ( it seems to be constantly u/d link your status to the world, I rather have my own privatcy control )
Blur Contact also another quick way to confuse the crap out of my contact and produce annoying double list.
Plus, unless you are on Froyo, you don't get to disable "Data Enabled" under Data Delivery. ( yes, you can install APNdroi or similar app to stop Data access when not in used, but it will just be another program running on the background )
Anyway, I really appreciate all these genius in the forum who creats so many different custom ROM and firmware for me to "upgrade".
I don't think it is possible to skip the blur account setup.
Other then that I am not convinced that any deep customization is necessary to make the DEFY a great phone.
I rooted the phone to rename/remove some unnecessary apps (e.g. amazonmp3). but after the earpiece problem I got my phone back with the original firmware restored. because I was lazy I didn't bother rooting and renaming/deleting. just installed launcher pro and advanced task killer. result: same performance improvements as with the rooted one before!
I just run a quadrant benchmark: 1073 points!
note that my defy is not really de-blured. I just installed launcher pro to stop that terrible blur launcher. even my task killer settings are conservative.
battery life is also not that bad: weekdays it is just a bit over a day (~30h). weekends depending on what I do. this weekend I am sitting home and still have 40% battery after having it disconnected from charger on friday morning.
bottom line: rooting is recommended to do some maintenance stuff (backups, firewall, etc.). using an alternative launcher is a MUST (launcher pro works best for me, but there are others too). however, renaming or deleting apps is not a good idea because of the heavy system integration of blur crap motorola did.
blessani said:
This took the phone immediately from a 5hr maximum battery life on idle to over 13 hours (still not impressive, but miles better!).
Click to expand...
Click to collapse
hey just a tip, install recovery, or, as your phone is just very young.
connect it to a power plug everytime when charging (not pc-usb, real power supply) and let i load as long as possible (3-4 hours max is enough) try to repeat this process 3-6 times and you'll get the maximum battery life.
works great! :=)
i resetted my battery stats once after a rom upgrade and the battery lasted for about as u said, 3-5 hours... i thought that i had destroyed my phone or similar, but after these complete charges, everything worked as it should again
would suggest it for any power driven device
My handset has the custom Defy recovery installed already (first thing) as per http://forum.xda-developers.com/showthread.php?t=893291
Its only charged off mains power, but to be honest, I've only had it 3 days now, and I've been using it so much in the past day tweaking it, that I haven't had a chance to see what I'll get our of it.
Those talking about de-bluring, theres a really easy non-root method to do it http://forum.xda-developers.com/showthread.php?t=943134
You don't realyl need to OverClock unléess you're playing a game on PSX4DROID...
i use 1200 mhz @ 58 and it's quite stable tbh. Haven't done much testing but the temp stays at 42°c
I'm actually concerned about the temperature of CPU...how high can it go until cou is likely to get effected?
I am a noob too. I came from spica, so i used android before and flashed some roms, but i only playing for the Defy for a day and i have some question. I bought one with 2.21 DE with blur, the phone was fast but the unlock slider lagged like hell, and after a call, the call summary was displayed for at least 10-15 seconds.
I flashed a 2.51 CE firmware on the device and it is generally much faster, but the call summary is still locking the phone for too long time(I rooted the phone overclocked, factory reseted done everything, but nothing helps, somtimes it is better after restart). Does anyone knows why?
Another thing, i know that 2.51 is undowngradeable.I read that i cannot flash most of the cooked ROMS and the chineese and beta froyo ROMs, but th phone is fast, and i got enough of cooked and alfa, beta ROMs during my spica period, and no way i want to go back to 2.21 so that is not a problem, but when the official UK or CE Froyo comes out, i will be able flash the sbf with RSD lite or I am locked to that firmware forever? And if someone updated the Defy to 2.51 with OTA, not RSD lite made the Defy undowngradeble?
Sorry for the lot of talk and thank you for your answers in advance
Just a note if you update to the new Blur you won't be able to use z4root. You need Super1Click (ver 2.51). Here is a post on it from Moto. https://supportforums.motorola.com/thread/44255?start=0&tstart=0 And here is another from XDA. http://forum.xda-developers.com/showthread.php?p=11151470#post11151470
Thank you for your tips.
I came from 5800 either
Sent from my MB525
[UT] X-RAY said:
I don't think it is possible to skip the blur account setup.
Click to expand...
Click to collapse
Press the Menu button (the hardware button with the 4 squares) and a menu pops up with "Skip Setup" listed. ^^
very good info, will try Titanium Backup Pro
You can use the phone without being logged into Blur. Shut the phone off and then go to myblur.com and change your password. Follow the directions and when done turn the phone back on and you will get an error that either the user ID or PW is wrong. All the other functions will work. For me the phone seemed real laggy running like this as it was trying to call home all the time.
no clue said:
Agree!
If you are coming from U.S. t-mobile, there is no way you can bypass Blur, other than flash to "foreign firmware".
Click to expand...
Click to collapse
5hr maximum battery life on idle?
ABC_Universal said:
5hr maximum battery life on idle?
Click to expand...
Click to collapse
Yeah there is something wrong then if that is happening. I use a Defy and a DHD, and days I only use the DHD, and let my Defy just sit there, it can go three days before it even gets to 80%.
3 days before it gets to 80% ....yeah right
my defy eats 5-10% per 6hours in idle ... and thats at 300/16vsel setting, stock 2.1 rom, and skipped blur setup
and with moderate use ...i get around 48hours out of it
so how could yours be at 80% after 3days being idle is beyond me ...what rom are u using & what idle settings?
Mine only uses 4% battery when idle for 8 hours over night with the alarm clock programmed to go off so i guess that would be around 12% / 24 hours if left in standby / idle.
Running stock 2.1 but overclocked and undervolted with setvsel.
300 / 20
700 / 32
1100 / 56
75% threshold.
I also use droidwall to enable only what i want to access wifi or data but not sure if that would help when the phone is idle.
I use
300/16
600/36
1000/56
80%threshold
droidwall wouldnt help me since i dont have 3g connection set up and i only turn wifi on when i need it ...
does your 2.1 rom come with motoblur or without?
I wish my defy would eat only 4% per 8hours =/
Hi,
Yes mine has Blur installed & I normally only have the weather programme running.

[Q] Battery life - Stock, CM7, Pays

Hi there,
So I'd my Defy for a little over 2 months now and I have used the mentioned ROMs with it for at least a week each. It first had Eclair, I promptly changed that to a Pays version of Froyo and now i'm using Quarx CM7.
A lot of my friends have this phone and report battery life of over 24h. They do work in places where they can connect their phones to their laptops and car charger, and they are lighter users than me.
But I'm a med student so I get out in the morning around 6 am, unplug my phone and go to the hospital returning home around 8pm. 14h later my phone is already at 33% charge. I keep wifi turned off, 3G off and use my phone to check MedScape(a medical info repository) and e-mail/facebook 6 times a day and listen to music for 4h.
Is that a good battery life? i mean, for a new phone. I imagine that if I let my 3G i won't get to the middle of my afternoon without needing to recharge.
Around the forum I read about people with OVER 48h of battery life, HOW?
thanks in advance.
Also, as I know it will be asked. My signal reception is flawless all through my working environment.
The .sbf you flashed (for the kernel) is apparently a big factor in batterylife, which did you use under cm7 ?
Which version of cm7 are you running?
Also are you using setvsel?
My settings are 300/23, 600/33, 800/43, and i have gotten almost 5 days battery use on a single charge, with
-texting for atleast 48hr time, intervals of short(10min) periods as you would expect
-maybe 20 mins phoning
-wifi on for half the time when i forget it overnight etc(my profile disables wifi on screen off however-good for light, but battery drain if you lock phone a lot)
-Get the following: OSmonitor, Battery monitor widget.
These help to track what apps eat battery, and kill processes with minimal(1%) drain, that if you arent using then you may aswell take all the battery back that you can
What are your display settings? eg auto brightness, renderfx etc
Thanks
software
I'm using the latest CM7 by quarx 5.1 and for base i'm currently using 3.4.2-177 nordic Blurless.
I wasn't currently using any undervolting settings to make a baseline screening of the phone with CM7 but i'll try yours and install the apps you've mentioned.
i'm using auto-brightness because of the bugs involved in disabling them in CM7 5.1. And haven't messed with renderfx so far.
Ok firstly i have only tested on 4.0, 4.1 and 5.0 so these suggestions are very likely to work but if certain settings are different in 5.1 then they may negatively affect you- just a thought
Undervolting is actually incredible on cm7 and works a charm, its still super responsive and load times are still less than that of any 2.2 i have tested WITH overclock
Start on about 300/600/800, 30/45/50 and go down marginally-different phones may have different yields to this due to apps running, previous cpu stress etc
(Remember to untick 'start on boot')
Also, the medical database you mentioned- does it contain any 3d renders etc?
This may require you to raise the voltage a little to keep it stable for anything you may to run aswell-- all the apps i have tested such as angry birds, 3d racer games work perfectly btw
Ok, there are extra options that allow you to further change the auto brightness inside the CMsettings under >Display>Automatic backlight
You might wish to experiment if you have time (decrease sensor check-times, lower overall brightness etc), however it likely isnt worth pursuing as the new Quarx beta shows brightness fixes in the changelog already, so just wait is my advice if you are short of time
Ooh and renderfx seemed to drain my battery more on any of the n1 settings, however it may be mix/match to get it right
Hum, I've had bad experiences with undervolting in 2.2 but I'll be sure to try it.
As far as medscape goes, it's just text, no image whatsoever it's just a big list with descriptions "acetaminophen - what does it do, how, dosages and stuff" really useful though
will post back when I have more info from the apps you've mentioned. So far I had used watchdog and it hasn't barked at any of my apps
As long as you take it slowly, undervolting is no problem- also try and minimize the amount of useless apps you have, since many of them run in the background by default without a way to exit them, meaning you constantly waste resources on them and thereby limit the amount of UC/V'ing you could acheive.
Ok thats cool, i was just curious as you clearly need/use that app often
Alrighty then, hopefully you can get some better battery life out of it -good luck
i don't actually have that many apps installed
3g watchdog, only on when 3g is.
angry birds
battery monitor widget
chrome to phone
documents to go
dropbox
evernote
facebook
epicurious
foursquare
gmail
goggles
mnote
msn mercury
music junk
music
pulse
sms backup
soundhound
talk
wifi manager
youtube
well, not that I've written it out, they are quite a few.
He probably means you should use something to kill useless apps running in the background. Look for Advanced Task Killer at the market and install it so you can kill apps that are running in the background but that you're not using.
@Behemia 5 days is awesome in my experience, and you are using your device the same way I am
could you please tell us which kernel are you using (savaged Zen maybe?) and which baseband (if you changed it)?
thanks!
im using cm7 with 3.4.3-11 kernel, undervolted to 300/18-600/30-800/45, kill apps with es task manager quite a lot, 3g or wifi is constantly on, and brightness is set to medium (for some reason auto brightness doesnt relly work for me), and i still cant get one day out of it. battery calibration helped a bit though (i recommend that app to everybody having battery life issues!). is that normal?
Report
So, I've done some of the changes proposed. Undervolted to 300/28 600/41 800/47. Installed Battery monitor Widget, OSmonitor left the phone with 3g off and wifi off when not in use(most of the time) and right now I've got 1% of battery left. That's 1d09h30min after unplug.
Below are the times in ms from the applications that I've used according to battery monitor widgets.
sms 814409
facebook 518805
contacts 355178
dialer 212996
gmail 195103
winamp 67868
medscape 2728
And here battery use report according to system
display 21%
phone idle 18%
stanby 17%
voice calls 15%
OS 7%
media 4%
winamp 4%
gmail 3%
facebook 2%
I'm not saying that 33h isn't good. But my use in this time has been way below my average for myself and the way below most of what I see described here. Plus I don't see any bloatware running nor I do see my apps hogging my battery. Facebook and Gmail push notifications are set to occurs over 2h apart.
Any ideas?
Also, as I finish this thread the phone finally vibrates and dies. Let's put it back to charge and look for more ideas.
thanks in advance everyone.
@lionheartpl
which kind of sim card do you own? i mean an old 64k or a brand new 128k? i upgraded mine from 64 to 128 due to a mobile operator change and my battery usage (same mod, same apps, same usage, same baseband) dropped from 2-3% hour usage to 1% in more than 1 hour. So battery usage has dropped a lot...
Running stock UK 2.1 i could get 4 days standby if i was just texting and a few calls. with the stock UK 2.2 undervolted to 300/22 600/32 1000/52 i can get 5 days easily but i cant see the point in it cos you dare not really use it, i would rather drop down to 1 or 2 days and give it some usage.
Hello everyone,
I'm getting a very good perfomance with the barebones froyo 1.5.6, check this behavior at night:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's like 2% loss in almost 8 hours!!!
Right now I am using the version 1.5.1 because I was told it has a better perfomance than the 1.5.6. I'll post my results in a few days.
Also, I use my Defy to be connected to windows messenger network all the time. I'm trying a strategy in order to not drain battery so much:
http://loqueselocomparto.blogspot.com/2011/08/messenger-en-android.html
Check it out
Even i m not getting a good battery life on CM7 RC1 V1, latest Nightly(9th Aug)
using base band switcher as i m from India
i lost around 18 to 20% every night between 12 to 8am.
over with minimum usage i can get 24 hrs thats witout any music and games, call for 30 mins
not sure what to do
some one please help
I can get about 2 days out of a charge. I am using 300/35 700/42 1000/50 and have had no problems. I recommend using battery calibration! A trick that I have learned is to let it charge to 100% do a battery calibration and then leave it plugged in for a while (30 mins). I have my wifi on all the time and run the smartass profile in settings.
good luck!
Chem57guru

Battery life stats and questions

What's a good figure for battery life on the GS3? The best I've got is about 31 hours using on demand and bfq. Any one got better life using other settings? I heard someone getting about 43 hours life but that seemed to be a little unbelievable. Let me know what your getting
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
What you reported is definitely "the average". Most actually only get a day, if they're lucky of moderate use and have to plug in before sleep every evening and get going on charge in morning. So its more like 15 hours actually. And your 31 max is very common high end for people who've stretched it out.
I'm not sure if you're stock rom or not and if rooted either but that makes a big difference.
I'm rooted ( and would ALWAYS RECOMMEND ROOT FOR EVERYONE EVEN UF NOT FLASHING ANY ROMS AND STAYING ON STOCK. The ability to have full control is important.
Changing kernels and more importantly, undervolting, will give you that longer life you're looking for.
I'm currently on KyanROM with either Ktoonez or Faux kernel (heavily tweaking and testing both) and have this phone beautifully undervolted to exceptionally low and very stable mv numbers! Thus getting me that lovely 36-45hour average (you mentioned you saw posted elsewhere - yes it is possible and many are doing it). I basically only need to plug in every OTHER EVENING or night between 6pm and midnight depending on usage and I'm a moderate to heavy user (with a lovely 3-5 hours of screen time as well) AND I also have my phone overclocked to 1.8Ghz! Surprisingly, the oc doesn't make much battery life impact at all because the phone isn't constantly having to run at high levels, only in short spurts. Actually, due to rooting and kernel change I'm able to have my phone run as low as 192Mhz during much of its general activity and deep sleep ( which I get a ton of as my phone basically always goes into it when the screen goes off). This saves me A LOT of battery life.
I also use LTE, which is actually one of the biggest if not the largest battery hog, next to screen time of course. But with that being said I only use it when needed and have it turned off when not in use.
As for my peak I was able to squeeeeeze out 87 hours once, on my stock battery BUT that was with some abnormal(for me) measures that really help conservation. Ie, no LTE, under clocked to 1.2Ghz for good part of the three days, much less then normal screen time over the period of which I used it at lowest level with even further reduction via screen filter, I actually used airplane mode during my three overnight sleeps (which I seldom use but if you can hack it, do it! It can really save battery overnight. My current setup basically SIPS MY BATTERY AT 1% EVERY 3.5-4 HOURS OVERNIGHT WHEN IN AIRPLANE MODE), mobile data was off for most of time but did use my wifi at normal level (wifi uses less especially if good signal with few reconnects/scans), used my typical low UV numbers, kept my notification updates/syncs/wakelocks to a minimum and lastly kept my memory virtually clear if unnecessary background apps.
Doing ALL of this allowed me to get OVER THREE DAYS BATTERY LIFE. But keep in mind I seldom do many of these battery saving tips on a regular basis but some do and if you can, they WILL work to extend your life substantially!
To wrap up (this long winded post/reply) I'll give you my general UV mv range numbers and the typical everyday simple battery saving methods I use.
1.My voltage at lowest clock of 192mhz=800mv with gradual (smooth and almost linear curve) increase up to a mere 1200mv at a whopping 1.890Ghz clock.
I use NOOP scheduler with ONDEMAND governor most of the time, sometimes SmartassV2.
My screen off and deep sleep use this lowest 192 clock speed and with no wakeup lag.
2. I use my screen at 0% brightness most of the time (except when outside or in high lighting environment). I use the brighrness widget app to control this as it is easier and works better then stock settings. I actually even further reduce my brightness with Scree Filter App. That app is awesome and often use it solely for brightness control because it has full control and can dim it to basically full black if wanted. Which is MUXH lower then stock control. Fyi I use my phone a LOT more at night or in dark environment thus allowing me to dim screen HEAVILY yet it still is actually plenty bright with ample contrast in dark environments to do everything. This saves on my battery HUGE!
3. I use LTE when needed and GSM/HSPA+ when not. Seldom turn of mobile data altogether. I do turn off wifi when out and only using mobile data.
4. I use Screebl app to have screen turn off when not in use. Its great liitle app. Basically let's you turn down screen timeout to 15 seconds or less so screen is never unnecessarily on but it always stays on when in use due to the accelerometer and it knows when the screen is not flat on table! Its very annoying when browsing or doing stuff where screen isn't touched for long periods and the screen goes to sleep! But this stops that! So its always on when upright or in use and when phone down it turns off immediately.
5. Very important step and can take some time and research but making sure to keep partial wakelocks and apps keeping device awake to a bare minimum! DEEP SLEEP IS VERY IMPORTANT TO SAVE BATTERY! You basically want it to go into that every time your screen goes off and to stay in it uninterrupted for as long as possible. And many users phones are NOT making it into deep sleep due to partial wakelocks and they don't even know it or how to fix it. Not getting deep sleep can unnecessarily kill your battery!
I use a few tools here: Better Battery Stats/GSAM Battery Monitor/Battery Monitor Widget from within System Tuner Pro (which is my also my main and highly recommended tuner app for CPU oc/uc and UV,etc.).
These apps really help to determine what, if any, apps are causing partial wakelocks ( displaying in wake number amounts and overall wake time) allowing you to determine what to do to fix the problem and let the phone gets as much battery saving deep sleep as possible.
6.I'm not big on auto app killers and actually recommend against them as Android ICS does this already very effectively but do keep in mind that the more active background memory that is used, the more battery the battery is drained. So I personally kill unnecessary apps myself from the background whenever possible to save a little battery here and there. Using the apps listed above in #5 can really help to detect a nasty background app or service that is quite possibly unknowingly using a ton of CPU and/or memory, thus draining more battery and also often just slowing down your phone!
7. For those who can use it Airplane Mode is a big saver! Try overnights if wanted as long as missing notifications, emails, calls, updates, etc is alright for you. I seldom use it but it does help.
8. I almost never use my Bluetooth and GPS but when I do that is the ONLY time they are on. They get turned off immediately and really be careful with the GPS in particular because you might be surprised how many things on your phone will use it in the background, sucking your battery!
9. Be careful with sound and vibration levels. Haptic feedback too. I don't do much here but its anotherctip nonetheless.
10. Lastly is treating and charging your battery right! I found an amazing site linked down below in a couple of articles that really explains these batteries and how they work in a very in depth technical level this is still not too hard to follow. Aside from the two links I posted check out the others on the left menu as there is a ton of useful and educational info!
http://batteryuniversity.com/learn/article/how_to_increase_the_runtime_of_your_wireless_device
http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
OK I've rambled on waaay too long here. Maybe I'll take this and post a battery savings tips thread with it lol. "10 points"!
Btw I've just received both my 3300mAh and 4400mAh capacity batteries. So I have much testing to do on those too and I plan on reporting back on them as well. Also with screenshots for data and proof...I can and will also post screenshots for all of the numbers and stats I've posted here today with my personal phone/battery accomplishments.
Hope this helps some of you out there because yes this phone can be known for terrible battery life but it CAN be tweaked to SUBSTANTIALLY IMPROVE that life to high standards and keep up with the best of them!
Sent from my SGH-I747M using xda premium
On Stock battery - Kyan Rom/Ktoonez kernel (at this moment)
Seems about right. My phone is completely stock and if I really wanted to I could even use it for 2 work days. I usually charge it over night though. I used it for 2 days though while at work, and with 3 hours of screen on time I was down to 7% battery. Around 40 hours on.
I was stocked rooted using Sammy kernel. On demand BFQ. I'll try on demand noop and see if that helps. My screen was about 35% brightness.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Can I hijack a little here? My battery seems to be atrocious. It was okay stock after my first 3 full charges I was getting about 12 hours and 2.5 screen time.
Here is what I've done with my phone since:
Flashed to debloated stock Rom
disabled remaining unneeded apps (example ATT wifi app)
disabled Wifi
disabled bluetooth
disabled GPS
disabled GPS autorun states
disabled 4g
disabled autobrightness, set to 15%
disabled location reporting
disabled Push email with Exchange
disabled Motion
disabled auto google backup
disabled keytones and vibrate on all button presses
disabled touch key lights
disabled Svoice
disabled streaming on googleplay, only plays from memory card
disabled Google Now
fixed the cell standby bug (even though it may not impact battery figured wth)
Uninstalled FB
Set all Autosync accounts and email to sync only once per day
No widgets (only Google play music, Smemo note, flashlight, and folders)
Running save power mode for low power screen, no haptic, and auto adjust screen to blacks
Running mostly black wallpaper, No live wallpaper.
Running medium intensity vibration
I ran battery stats and got a lot of wakelocks from googlemaps and exchange so I disabled the push email and set it to once a day. Google maps I disabled latitude, and shut down the autostarts with gemini.
It's getting to the point where the phone is basically a dumbphone just so the battery can make it while it sits next to me at work. Today I have 48% after 8 hours and 50 minute screen time and 20 minutes of google play (only playing from on SD card not streaming).
Any ideas? It seems like I'm getting less than average.
All I did was also flash debloated rooted stock. Set to top out at 1.5ghz power save on. On demand BFQ schedule. Screen brightness as low as I can to still read. And got 32ish hours. I'm going to try OnDemand and noop like the other guy said and UV a lot more and see how close to 40 hours I can get
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
chrisj22 said:
All I did was also flash debloated rooted stock. Set to top out at 1.5ghz power save on. On demand BFQ schedule. Screen brightness as low as I can to still read. And got 32ish hours. I'm going to try OnDemand and noop like the other guy said and UV a lot more and see how close to 40 hours I can get
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Can u link me on the bfq? Having troublefinding what that is.
Also, is that the built in power save that limits the processor or some other software?
I believe if you flash Sammy kernel it has bfq. I am on task's CM10 and kernel and battery life seems poor compared to CM9 or stock rooted
Sent from my SGH-I747 using xda app-developers app

Poor battery life

Dears,
I bought a G3 phone just a month ago and, apparently, the battery was lasting almost a whole day in the first two weeks, but, after that, the battery became to last less than half day. Of course I've installed some applications since then, but it's very strange because the Android doesn't report any abnormal processing load of any application, so I'm presuming the OS is causing the high battery consumption. After I bought the phone, I upgraded the OS to Lollipop almost forthwith. I'd like to know if it's a known issue of G3 with L version and there is something I can do to increase the battery life.
I've installed some applications that utilize the location services, but Android doesn't claim those applications are draining the battery. According to what Android reports, the screen and the OS are main things that are consuming more battery ( 24% for screen and 16% for OS )
Thanks in advance
nasordev said:
Dears,
I bought a G3 phone just a month ago and, apparently, the battery was lasting almost a whole day in the first two weeks, but, after that, the battery became to last less than half day. Of course I've installed some applications since then, but it's very strange because the Android doesn't report any abnormal processing load of any application, so I'm presuming the OS is causing the high battery consumption. After I bought the phone, I upgraded the OS to Lollipop almost forthwith. I'd like to know if it's a known issue of G3 with L version and there is something I can do to increase the battery life.
I've installed some applications that utilize the location services, but Android doesn't claim those applications are draining the battery. According to what Android reports, the screen and the OS are main things that are consuming more battery ( 24% for screen and 16% for OS )
Thanks in advance
Click to expand...
Click to collapse
You should root your LG G3, then install xposed, greenify amplify and powernap. Those apps will control your wakelocks and alarms. This will also improve your battery life.
May I also suggest to reduce screen DPI. Reduced mine from 640 to 534, added about 45-60 mins of SOT
Are you talking screen on time? Or idle battery drain. Because these are two very different things. Quite often it is the way you are using your phone and the applications installed that will cause your battery life to become worse.
Of course you have the obvious things such as disabling data when you aren't using it and wifi and so on. Through my experience I have found amplify to be of little use if you are generally cautious about the apps you install. Facebooks apps are terrible. Any instant messager will be causing some sort of drain. The problem definitely arrises from these things and while you can install many other apps to limit these things. I often find it is best to address the problem at the source. Perform a factory reset. Then begin installing your apps one by one and seeing when the hit comes. Thats my advice. Then find an alternative to the problematic app. That or BBS to find what is causing wakelocks. Remember, if you are gaming the processor is going to eat battery.
To follow up on orcam he is in the perfect rite direction as for reducing the dpi its a placebo effect you can read up on it on many threads and sot is in most case 7 to 12 min longer reduce britghness get rid of carrier iq is a big battery hog debloat the system apps like facebook and all the other bloat that lg uses is bad on battery life
The best way to get better battery:
1. Root
2. Debloat - delete useless app's and files from root directory!
3. 3845*#855# (855 its international model, put your model: 851, 852, etc) and search for Thermal Daemon Mitigation OFF, then click and enable it, and search Fast Dormancy and turn off, and in High Temperature Property OFF enable it too and turn off your phone for atleast 40 seconds, turn on and wait 1 minute with screen on to update those things.
4. Xposed with Greenify
5. TricksterMOD and set the CPU freq. to min. 300Mhz and max to 1.540MHz (if you use the phone normally, and dont play games).
6. in TricksterMOD set the GPU to 330Mhz for powersave.
7. Developer Options active the "Force GPU to 2D graphics"
8. Use brightness according with your needs, not only keep it in 100% (i know in 100% looks beautyful but screen is a battery beast).
This is what i have in mine and i can guarantee if you use moderate it can go up to 3 day's, mine got 5 hours and 20 minuts in On Screen Time so...

Question High battery consumption on idle

My phone is usually on idle and not used due to my job. But Im noticing extreme battery consumption even when Im not using it. Never had this issue with other phones. Last night I checked the batter before sleep and it was at 67% at 1 AM, today its 62% at 7 AM so there must be an issue because it should only drain 1 or 2 percents during idle.
In battery settings the top app using the battery is phone idle.
Im on xiaomi.eu 12.5.6 rom but I had the same issue with stop 12.5.3 so I dont think it's because of rom.
I had great battery life with my last phone which was poco x3 nfc with the same settings and apps so it's not because of any third party apps either.
Anyone else experiencing the same problem?
With AOSP ROMs, I even had worst experience when I installed one of the custom kernels because they somehow didn't put the phone into deep doze correctly. But yeah, the idle consumption is quite high - even on stock Kernel.
Currently I use HavocOS and its stock Kernel - and SuperFreeze (from F-Droid store) to freeze most apps right after screen lock. Idle consumption has dropped to 0.1-0.2%/h as a result. I made a thread some days ago regarding this topic... see here.
Thanks. Im gonna try your guide but it's not the most noob friendly guide I've seen
Just Kidding, thanks for your time.
Oh, my thread wasn't meant to be a guide... I did put it in "Question" like you did, but a mod seems to have moved the thread to "General"
My "solution" is only temporary - at least I hope there are still developers out there who value a low idle drain more than fast charging and benchmark numbers...
esszett said:
... and SuperFreeze (from F-Droid store) to freeze ...
Click to expand...
Click to collapse
Sorry for the OT, could it be that the app. is called SuperFreezZ?
Have you noticed any good battery life gains with this app.?
Yeah, sorry, SuperFreezZ: https://f-droid.org/en/packages/superfreeze.tool.android/
For several months I had the problem that from a certain moment, the consumption at idle suddenly increased enormously (from 0.1-0.2 % to 2-3% per hour). Even if I manually forced all apps to stop, In Android's battery info "Android OS" and "Android System" showed up with double-digit percentages. I could only get the phone back to its previous behavior with a restart.
To date, however, it is not clear to me what triggered this. I suspected GCam for a while, then Osmand+, but I couldn't ever confirm that because the problem didn't start whenever I used those programs, just sometimes.
I never found a real solution for this, but SuperFreezZ did.
The best thing I've used for years now is Greenify, its hasn't received an update in more than a year but still works perfectly
Do we need root to use these apps? I remember using greenify before onmy older devices with root but havent used it for a while. Gonna see how much it drops tonight and then try to tweek some things and recheck it tomorrow night.
Weird thing is, I was getting an awesome battery life out of poco x3 nfc, could it be because of the cpu idle? Because that's the only thing that seems different between the 2 devices. (X3 even had an lcd which is supposedly less battery friendly)
Kianush said:
Do we need root to use these apps?
Click to expand...
Click to collapse
Yes.
Kianush said:
I was getting an awesome battery life out of poco x3 nfc
Click to expand...
Click to collapse
Unfortunately, hardly anyone notices this because most users do exactly what the F3 was designed for: Playing games.
I came from a 2.5 years old F1 and it lasts easily longer than the F3 although it has a smaller battery and a LCD screen... The F3 behaves anything but fully developed. These latest high-end SOCs (870, 888) are really powerful, but unfortunately not equally power-efficient. That's the reason why I throttled the CPU and undervolted the GPU. This dropped the active drain from ~8 %/h to <5 %/h on my device and my usecases.
esszett said:
Yes.
Unfortunately, hardly anyone notices this because most users do exactly what the F3 was designed for: Playing games.
I came from a 2.5 years old F1 and it lasts easily longer than the F3 although it has a smaller battery and a LCD screen... The F3 behaves anything but fully developed. These latest high-end SOCs (870, 888) are really powerful, but unfortunately not equally power-efficient. That's the reason why I throttled the CPU and undervolted the GPU. This dropped the active drain from ~8 %/h to <5 %/h on my device and my usecases.
Click to expand...
Click to collapse
Yeah. I used to underclock the cpu on my old phones but I dont know about undervolting. wouldnt it cause issues? I just used 3c toolbox app to set a lower max clock and a lower min clock for cpu cores. I read somewhere that rooting xiaomi.eu rom breaks some functions so I havent rooted it yet. do you have any info on that?
Kianush said:
Yeah. I used to underclock the cpu on my old phones but I dont know about undervolting. wouldnt it cause issues?
Click to expand...
Click to collapse
As long you don't push too hard with undervolting, it works quite well. See attached image (it's not mine, but I have oriented to it).
Kianush said:
I just used 3c toolbox app to set a lower max clock and a lower min clock for cpu cores.
Click to expand...
Click to collapse
I've never heard of it... This seems to be a powerful tool! Nice!
Kianush said:
I read somewhere that rooting xiaomi.eu rom breaks some functions so I havent rooted it yet. do you have any info on that?
Click to expand...
Click to collapse
Konabess doesn't need root, afaik. Extract the boot.img of your ROM and copy it into a folder of your device. Then use Konabess to modify the settings and repack it into a modified boot.img. This file you can flash with TWRP. No guarantee that it works for xiaomi.eu, but it works for AOSP (at least it worked for me).
Kianush said:
My phone is usually on idle and not used due to my job. But Im noticing extreme battery consumption even when Im not using it. Never had this issue with other phones. Last night I checked the batter before sleep and it was at 67% at 1 AM, today its 62% at 7 AM so there must be an issue because it should only drain 1 or 2 percents during idle.
In battery settings the top app using the battery is phone idle.
Im on xiaomi.eu 12.5.6 rom but I had the same issue with stop 12.5.3 so I dont think it's because of rom.
I had great battery life with my last phone which was poco x3 nfc with the same settings and apps so it's not because of any third party apps either.
Anyone else experiencing the same problem?
Click to expand...
Click to collapse
I'm ont he same rom as you and let me explain my experience.
My battery has been insanely good. Even with heavy usage over a period of 4 hours, which included 1.5hrs of SoT and pandora playing though bluetooth all 4 of those hours with dolby and viper enabled. Was at 100 and dropped down to 94%. So It may be an app or setting that you have installed causing problems and draining battery. The only battery saver addition I have installed is Universal GMS doze. Idle time for me It takes me about 5 hours to drop down 1%.
Zaiaku said:
I'm ont he same rom as you and let me explain my experience.
My battery has been insanely good. Even with heavy usage over a period of 4 hours, which included 1.5hrs of SoT and pandora playing though bluetooth all 4 of those hours with dolby and viper enabled. Was at 100 and dropped down to 94%. So It may be an app or setting that you have installed causing problems and draining battery. The only battery saver addition I have installed is Universal GMS doze. Idle time for me It takes me about 5 hours to drop down 1%.
Click to expand...
Click to collapse
Well if there is an app that is causing this, it should be shown in the battery settings. But the only thing that is eating up my battery is phone idle. So it might be a service or something. Im out of options right now unless I find a way to root this rom without facing new problems.... Worst thing with miui is that you cant do things like rooting as easy as other roms.
Btw, would you please tell me the settings and xiaomi.eu version you are on? Im on 12.5.6 stable and using 120hz + vivid color scheme and most of my apps are on blcok background activity except my messaging app. And Im losing battery on phone idle not the screen on time!
Ss below.(dropped from 92 to 82 woh only 30mins screen on time doing nothing but checking xda!) And 7hrs of those 9hrs I was asleep and the phone was on airplane mode + gps off!
You could try BBS or similar apps. Maybe it's an app which prevents the phone to go to deep doze (wakelocks).
BTW: MIUI sucks
Kianush said:
Well if there is an app that is causing this, it should be shown in the battery settings. But the only thing that is eating up my battery is phone idle. So it might be a service or something. Im out of options right now unless I find a way to root this rom without facing new problems.... Worst thing with miui is that you cant do things like rooting as easy as other roms.
Btw, would you please tell me the settings and xiaomi.eu version you are on? Im on 12.5.6 stable and using 120hz + vivid color scheme and most of my apps are on blcok background activity except my messaging app. And Im losing battery on phone idle not the screen on time!
Ss below.(dropped from 92 to 82 woh only 30mins screen on time doing nothing but checking xda!) And 7hrs of those 9hrs I was asleep and the phone was on airplane mode + gps off!
Click to expand...
Click to collapse
I switch my screen refresh rate down to 60hz but since your phone is idle it really shouldn't come into play unless you have always on display or turn screen on for notifications.
Rooting this phone is amazingly easy. Takes like 5mins if that. My Mi 9 lite took longer to root then this phone.
As far as an app draining battery, It more then likely not it since you saying phone idle, which in the past people have said if you phone has problems with signal this can drain a battery. For me this has been a major issue. With AT&T service I would loose double the amount of battery over night (I play pandora through out the night when sleeping). Also if you have apps that are heavy internet usage (unsure where you at but things like facebook and messenger drain tons and yet don't register battery drain on most analytics. And since you using a xiaomi.eu rom I know alot of those bg services are disabled or removed.
Zaiaku said:
I switch my screen refresh rate down to 60hz but since your phone is idle it really shouldn't come into play unless you have always on display or turn screen on for notifications.
Rooting this phone is amazingly easy. Takes like 5mins if that. My Mi 9 lite took longer to root then this phone.
As far as an app draining battery, It more then likely not it since you saying phone idle, which in the past people have said if you phone has problems with signal this can drain a battery. For me this has been a major issue. With AT&T service I would loose double the amount of battery over night (I play pandora through out the night when sleeping). Also if you have apps that are heavy internet usage (unsure where you at but things like facebook and messenger drain tons and yet don't register battery drain on most analytics. And since you using a xiaomi.eu rom I know alot of those bg services are disabled or removed.
Click to expand...
Click to collapse
Yeah thanks for the info. I used to root my devices easily by flashing magisk but it seems they have changed the method, though I found the method on a post on xiaomi.eu website and rooted my device.
Tried to lower cpu frequencies a little and use superfreez app. It seems better now but not as good as what you say...
Gonna play with settings a little bit more and wait for another xiaomi.eu stable update to see if it's a bug on this version.
Kianush said:
Yeah thanks for the info. I used to root my devices easily by flashing magisk but it seems they have changed the method, though I found the method on a post on xiaomi.eu website and rooted my device.
Tried to lower cpu frequencies a little and use superfreez app. It seems better now but not as good as what you say...
Gonna play with settings a little bit more and wait for another xiaomi.eu stable update to see if it's a bug on this version.
Click to expand...
Click to collapse
Someone made a auto script for it, but you will have to reflash rom and factory reset data. You really shouldn't have to change cpu feqs. Also uploading a screenshot of my last 2 hours. I know its only 21min of SoT but also 2 hours off charger but playing pandora as well as some other app usage but still at 100%
esszett said:
As long you don't push too hard with undervolting, it works quite well. See attached image (it's not mine, but I have oriented to it).
I've never heard of it... This seems to be a powerful tool! Nice!
Konabess doesn't need root, afaik. Extract the boot.img of your ROM and copy it into a folder of your device. Then use Konabess to modify the settings and repack it into a modified boot.img. This file you can flash with TWRP. No guarantee that it works for xiaomi.eu, but it works for AOSP (at least it worked for me).
Click to expand...
Click to collapse
Konabess without root won't start, any idea?
thanks
tojdvd said:
Konabess without root won't start, any idea?
Click to expand...
Click to collapse
Ah, ok... I thought you could load a separate boot.img - my fault, sorry!
Then you've to have root for Konabess...
Just to show what's possible with HavocOS 4.9 and 12.5.6 EEA firmware, see atached screenshot... It's with the stock kernel of HavocOS, but with the modifications I did mention here.
Running for almost 2 days
~8 hrs SOT (2 hrs of which with 120 Hz and 2 hrs of which with 100 % brightness, otherwise 60 Hz and brightness between 25 and 50 %) and still 50 % battery left.

Categories

Resources