Last update: 7.10.13
{
"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"
}
This is the complete guide of how to handle your battery in the most efficient way possible.(GB/ICS/JB version).
This guide refers to Android users in general (Samsung, HTC etc..) in addition to SGS2 users.
ROOT: Yes.
ROM: Any rom will do.
Kernel: Siyah/Dorimanx is preferred but any other will be fine.
Human features: Patience
After an extensive research regarding 'how Android OS works' and reading hundreds of pages (yes 1000 pages in 1 thread) in XDA regarding topics such as: BBS (BetterBatterStats), MagicConfig by geko95gek, Kernel Info, Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs by droidphile etc, I have come to conclusion that there is currently no better configuration than mine.
I almost don't have wakelocks, during the night (7 hours sleep) I have between 3-4% drain which is really good, of course, you can get better drain ,for example, 1 % during a whole night BUT users like that turn off their data connection OR switch to airplane mode, I really don't like doing that but of course you could do that too and enjoy your 1% drain.
Before I wrote this guide I tried these configurations in 5 different infinite sgs2 mobile phones of my friends and Nexus devices, they all were blown away from the results they experienced from their battery.
I wrote this guide because XDA users have helped me a lot in all the aspects of Android, so now I can help the XDA community too.
Last update:7/10/13
Step 2 updated with solutions on the go.
Step 3 is now LBE version 5 compatible.
Step 4 updated for Dorimanx users as well.
Faq Updated
Post #1
Wakelocks: What is it ?
Monitoring the wakelocks
LBE security manager: internet permissions & prevent apps to be put in cached after a restart
ExTweaks/STweaks & governors - Siyah/Dorimanx kernel users ONLY!
Undervolting & Governors
Post #2
Freezing google/Samsung apps using Titanium Backup Pro
Screen Brightness
Accounts & sync
Fast Dormacy - Should/Can I disable it ?
Battery calibration - Should I do it ?
Network/operator modem support - How to tell if your modem meet your network standards
Variance
Learning to read the battery graph
Post #3FAQ
When you're done with the guide please do come back and share your results with us.
I'll try to simplify things as much as I can so the common user could understand.
Let's begin,
1. Wakelocks: What is it ?
When you develop an app in Android there are options for you (as a developer) to let the app start during a different time or a different change, sometimes it is really essential, for example our build in Alarm clock(Also: Widget/Music player), we need it to start the alarm in a specific time thus this process is important and it will open up by "it self".
Counter example is a simple game or a weather app, we only use it once in a while and after we use it we don't need the process anymore so we close it, but most of the time the developer add all sort of commands to start the process even when we don't use this exact process, for example if we boot the device/click on the media app button the app will go into cached processes (System settings->Applications->Running->Click on cached processes), but let's say it's an app we use once a week or a game we play once a week, there is no need to put this app in the cached processes (since it consumes the battery) so this is why we would like to close this option.
Notice – When you open an app and close it the process is still in the cached processes because if you open it again, it will open in a sec (since it's in the cached processes)and that’s a good and efficient thing, but if you close it from the cached processes you will only make things worse because when you open it AGAIN the Android OS will AGAIN, put the app in the cached processes and this is yet again will consume the battery.
How to tell if you can turn off or not in an app/game:
Basically the idea is this,
If we are talking about an app that the whole very existence is to do things by it self (Playing songs/Setting alarms/Auto-commands apps) then of course we won't turn anything off.
If we are talking about a type of apps that their whole process is to do something particularly which will take place only when we open the app (Bar-code scanner/Weather app/Shazam/Office apps/GPS apps/Games so of course we will turn everything off.
If we are talking about ROOT apps so I suggest not to touch anything.
First thing you will do is to download Gemini App Manager 2.6.0, this app will handle these wakelocks and as we already mentioned will give us full control over 'when to put/not to put the app in the cached processes/running services'.
DON'T UPDATE TO VERSION 2.7 - THE NEW VERSION HAS NO WORKING EXPERT MODE ! ! !
After you downloaded the app, open it,
Hit the option touch key (left to the home button) and go to 'Expert Mode', you will find there, all the applications your phone contains. What we are looking for is the orange icon the says 'AUTO' under each app:
once you find an app/game with this icon, think, and ask yourself "Do I need this app/game to open up by it self?" (See the examples with the clock app above).
If your answer is "NO!" (90% of the cases the answer is no-read above when the answer is YES), then press this app/game for about 2-3 seconds, a window will open and choose 'ConfigAutorun (root)'.
A new window will appear with all sort of commands: On package added, on app widget update, After boot etc, as you can tell the name of the command does what it says for example: 'On package added' -> if you added a package to the app, the app will be put in cached process.
Change to OFF all the commands:
and there you go, this app will never fool around!
2. Monitoring the wakelocks:
Download the app: BBS
BetterBatteryStats aka BBS: Why do I need this app ?
After you managed to finish step number 1, you can now install BBS on your system.
Once your done open it and choose partial wakelocks, we will focus on this section.
Charge your device to 100% and when it reaches 10% or so, open BBS hit the options touch key and choose 'Dump to file':
this will generate a .txt file with all the apps/games that did wake your phone and caused drains.
"BUT HEY I DON'T UNDERSTAND ANYTHING FROM THIS FILE AND THIS APP IS HARD TO UNDERSTAND!!!", first you need to relax and go to the BBS thread BBS, the developer is kind enough to let you put the file there and he will look it over and tell you what is the main problem you should focus, and decide if to remove the app or maybe change something in the setting of the app.
If you want to learn about this log file and understand it better just read the thread (like I did) it contains more than 1000 pages, so after 10-20 you will have some clue about this app.
Remember, this is the BEST application that can track your battery drains and tell even if your kernel is waking up the phone, just dig in BBS and you will see, there is no other alternative than BBS, remember that and don't ask for a substitute.
Q: How can I solve BBS wakelocks on the go ?
A: Get in here.
Also, if you have EventLog wakelocks here is the solution:
Download System Tuner. open the app and go to 'Startups' and look for 'Google service framework' and over there disable both 'checkin.EventLogService'.
Be advice EventLogService wakelocks only happens with stock Samsung ROMS.
ALSO, read the FAQ.
3. LBE security manager: internet permissions & prevent apps to be put in cached after a restart: version 5+
We all know that every time we go to the inet (not via wifi) we are starting to see an immediate battery drain.
The best way is to install a firewall app (which is MUCH more than that btw and it's free) that will control our inet pipe.
The user zagzag99 was kind enough to translate the latest version (4) of that app (Notice that in Play store it's version 3 ONLY) get it here: LBE Security
After you installed the app,
Tap on More -> Permissions -> All apps
Now you are looking at all your apps/games (including system app by tapping on 'Download' on the left and choosing 'System'), by clicking on one of the app/game you would see the permissions the app wants from your phone, if it is a game that you play offline then why does this game want to go online? More-than that, why the game wants to access my call records!?
This is why you won't allow it and eventually you'll close the inet pipe and the rest for each app/game you don't want to go online or even get your precious information.
After your done we will now deal with the auto start issue.
Repeat step a, and choose a random app, as you can see the first option in every app is 'On boot permissions' so you can turn it off or back on.
Now, this is very important, I only say it once, if you see an app/game that you don't even use or use once a week 'turn it off', but if you see an app/game that you use most of the time leave it as it is, why ? Obviously you didn't read step number 1.
4. ExTweaks/STweaks& governors - Siyah/Dorimanx kernel users ONLY! **Unless you can undervolt with your kernel**
Download STweaks, if you want to understand what each command/line does please read up: Here or you can just do what I tell you to and enjoy better battery.
First of all I want to thank geko95gek who inspired me a lot regarding STweaks .
Open STweaks,
CPU tab:
MAX OC FREQUENCY: 1000000Khz
CPU_UV tab:
You can undervolt here or in setCPU (See step 5).
Be advise #1: for some reason Siyah V6b5 doesn't save the changes after reboot BUT setCPU does.
Be advise #2: Dorimanx users are good to go.
GPU tab: - SGS2 users input - Different devices try to lower 1 step back.
Siyah steps:
GPU FREQ STEP1: 54Mhz
GPU FREQ STEP2: 108Mhz
GPU FREQ STEP3: 160Mhz
GPU FREQ STEP4: 200Mhz
GPU FREQ STEP5: 267Mhz
GPU VOLTAGE LEVEL1: 850mV
GPU VOLTAGE LEVEL2: 900mV
GPU VOLTAGE LEVEL3: 950mV
GPU VOLTAGE LEVEL4: 1050mV
GPU VOLTAGE LEVEL5: 1150mV
Dorimanx steps: (Basically the default)
GPU FREQ STEP1: 108Mhz
GPU FREQ STEP2: 160Mhz
GPU FREQ STEP3: 200Mhz
GPU FREQ STEP4: 267Mhz
GPU FREQ STEP5: 267Mhz
GPU VOLTAGE LEVEL1: 900mV
GPU VOLTAGE LEVEL2: 950mV
GPU VOLTAGE LEVEL3: 1000mV
GPU VOLTAGE LEVEL4: 1050mV
GPU VOLTAGE LEVEL5: 1150mV
You're DONE!
5. Undervolting& Governors:
Be advise: If your kernel doesn't support undervolting move to the next step, but I recommend to use a kernel that has support because when the phone is in deep sleep or on 200mhz (when you're not using it) you could save a lot of battery.
Be advise #2:I am going to recommend the use of setCPU and STweaks (Siyah/Dorimanx kernel only - if you don't have siyah you can do this step also as long as your kernel support undervolt), a lot of people wouldn't recommend the use of these apps together since they MIGHT conflict with each other, BUT if you will go through this step and read carefully it wouldn't be a problem in fact, it will work just fine
Download setCPU, if you want the latest version you can buy it in the Play store (support the developer).
Version 2.2.4 would be fine too, if you want to understand what each governor means and what is cfq please read up: Here and Here or (if you’re a lazy ass user) you can just do what I tell you to and enjoy your battery:
Open setCPU,
Main screen:
change to 200-1000 Mhz (it should be like it since you already changed it in ExTweaks) and tick 'Set on boot', also make sure 'ondemand' and 'ROW/CFQ' are chosen as governor/io :
Profiles:
Make a new profile and choose 'Add Condition -> Screen On/Off' and choose 'Screen off' and save.
Hit next and choose 200-500Mhz, tick 'Set the CPU governor' and choose 'conservative'.
Choose priority 50.
This profile will make sure while the screen is off there won't be any jumps to high frequencies.
Make another new profile and choose 'Add Condition -> Battery level' and choose '10%' and save.
Hit next and choose 200-800Mhz, tick 'Set the CPU governor' and choose 'conservative'.
Priority is 49.
This profile will let you squeeze the last 10% of the battery like they were 20% but the UI will lag.
Tick those profiles and tick 'Enable Profiles' at the bottom.
Results of step a & b :
Voltages Screen: (Only supported kernels)
Be advice: This stage is the most exhausting, annoying and irritating stage you could ever find but in the end it's worth every second.Since we put a range of 200-900Mhz we will focus on these frequencies only (of course if you decide to put the range between 200-1200Mhz you will focus on them only).
We will scroll down and look for 200Mhz, 1st white row represent the default mV that Samsung has put in order to max UI, and 2nd white row represent your mV change,but we are smarter than old Samy so we will start to change.
200Mhz – Is usually between 825-875mV it varies between each phone (each phone has different ROM/Kerenl)
So you ask yourself, which mV should I choose?
Well my friends, that’s the 1 million dollar question, let's say you chose 850mV:
Touch the 200Mhz and change it to 850mV afterwards hit the 'Right icon' next to the save icon
if your phone is still working and didn't get stuck go back to the 'MAIN' tab and choose 200-200Mhz (yes exactly like that) and then we will go to the 'INFO' tab, scroll down and choose 'Stress test':
if 'Sress Test' ran for about 4-5 mins and everything is still working, you can stop it by pressing the back key and it means we can continue to the next stage.
Download Stability Test
Open the app and choose Classic stability test – this will ensure the test of only the 200Mhz frequency.
If after step b&c your phone is still working that means that the undervolt you chose is working great. (It doesn't mean that your phone won't freeze-it might), you can undervolt more and see what is your limit.
Do the same process to all the frequencies, of course if you're in 500Mhz you choose the main profile (setCPU) 300-300Mhz in order to test only this frequency.
When you're done, change back in setCPU'MAIN' tab to 200-1000Mhz, go back to Stability test and now choose Scaling Stability Test, let it run for 10-20mins, if there are no errors you're good to go.
Play with the phone for few days, if it hasn't frozen go to setCPU 'VOLTAGES' tab and tick at the bottom 'Set On Boot'.
Notice: My recommendation is to set on boot in the end of the process because if you choose a really low MV your phone might be stuck in an endless loop, thus you tick 'set on boot', only, if you are sure your system is stable.
Final Result:
[img=http://imageshack.us/thumbnmail.png]
My voltages (SGS2 Device):
200Mhz – 850mV
500Mhz – 925mV
800Mhz – 975mV
1000Mhz – 1075mV
Notice: This undervolt method is the most aggressiveness method around, if you want the easy way and you have Siyah kernel you can open ExTweaks/STweaks and in the "Undervolting" choose -25 or -50, this will undervolt ALL the frequencies together with minus 25 or 50, if your brave you can try 75.
My method gives you a specific voltage to each frequency, in 200mhz you can have minus 75mV while in 500mhz minus 50mv, this will give you the best undervolt system.
Continued on next post...
6. Freezing google/Samsung apps using Titanium Backup Pro:
If you didn't buy the app yet, well, you’re an idiot: Titanium Backup Pro or you can use a free substitute (though I never tried it) Root Uninstaller
After you bought the app, open it and go to 'Backup/Restore' tab:
in there, you can see all your apps/games AND system apps, we will be focusing on the system apps.
NOTICE: If you're using CM rom you can skip this step since they did hell of a job in removing all Samsung/Android bloat-ware.
Our main goal is to freeze processes that common users don't use and don't even know they have, I won't write all the list of the apps you should freeze but I will write all the apps you will freeze that are consuming your battery like a *****:
Email 4.0 – this is stock mail full of bugs and infinite loops that go online and check for mail, if you don't have gmail account please use a 3rd party app like AquaMail/MailDroid that will give you minimum bugs for the check interval.
Exchane Service 3.1 – Belongs to Email 4.0
Kies via Wi-Fi – I wouldn't say it consumes your battery but it's an unsecured protocol by Samsung, use a 3rd party app like AirDroid
Maps – If you're not using it FREEZE THIS APP ASAP! If you do use I suggest unfreezing every time you need it and freeze again when you're not using it (sorry).
MAPService – Belongs to Maps.
Samsung Account – Do I really need to explain? (Including all the Samsung hubs and chats and whatever they come up)
SecPhone 1.0 – If you're using a different launcher rather than TW you can freeze it.
Software Update – We don't need it, we flash our ROMS
Street View – belongs to Maps.
Talk – I find that even if I freeze it (gtalk) it's still waking the phone so your choice.
Talkback – Samsung try to overtake Whatsapp.
Wi-Fi Direct & Wi-Fi sharing & Wi-Fi sharing manager – you don't need it.
Of course if you're using stock ROM you have A LOT of freezing to do, you can use this thread and of course this amazing list
Or you can Google for more apps that are safe to remove.
7. Screen Brightness:
If you don't know, the most battery consuming part of the phone is the screen.
Go to 'System Settings -> Display -> Brightness' and choose 'automatic brightness'.
For the users that want to maximize even more (YES WE WANT EXTREME!!) try to lower the brightness as low as you can, 20-30%.
Recently I've noticed that there are new apps that you adjust screen brightness by each pixel and a lot more, you can Google that, but I prefer to be able to see things crystal clear.
8. Accounts & sync:
Everyone is recommending, in order to save battery, to go to 'System settings -> Accounts and sync' and to turn it off, of course it will save A LOT of battery, but, if you have a gmail account and you want to be notified as soon as you get an email,you can't turn it off.
What you can do is:
Hit your @gmail.com account, and 'untick' everything except 'Sync Gmail', this will assure that you will get your emails via PUSH (PUSH is the most battery efficient protocol - at real time):
Don't forget to sync your contacts/calender once in a while or before you flash a rom.
If you don't want to get your emails instantly then remove your gmail account and download a 3rd party app like MailDroid/AquaMail and set interval for every hour or every 4 hours, this will assure that there will be absolute no wakelocks but only every 1 hour or 4 ( as you chose).
If you choose to keep auto sync there is one disadvantage:
If you don't have a good reception 'sync' option will go completely crazy and keep asking to go online and sync your email (since you're on PUSH) but it won't be able to, since you don't have a good reception and it will go like this in an infinite loop till you have a decent reception and as you can already understand while your screen is off, the phone is awake and trying to sync, so keep that in mind.
9. Fast Dormacy - Should/Can I disable it ?
First of all you need to understand that not every network/operator support FD (Fast Dormacy).
My network doesn't support FD thus if I'll disable or enable it, it wouldn't make any different, in fact if you disabled it and you think your battery is now "OMG FUKCING AMAZING" this is just a placebo effect, and yes I am 110% positive.
How do I check if my network support this tweak ?
The user JIMMYMCGEE from xda made an amazing guide you need to follow (in fact it's a video clip - which is easier).
She first explain what is FD and afterwards explains how to check if you have FD and if you do, how it can save you battery.
Follow this guide and all his steps here.
NOTICE: If the app that shows you your network stats (service mode) doesn't work and only opens your dialer, this is what you need to do:
This is the code for the service mode, write it in the dialer:
*#*#197328640#*#*
When you'r in the Service mode screen, hit: Debug screen->Basic Information and here you go, service mode.
Interested in more info regarding FD ? you can read what I have already read in here.
10. Battery Calibration - Should I do it ?
The answer is simple, if you are using ICS/JB you don't have too because every time you charge the battery to 100% all your data and stats are deleted and the service begins to collect info again from the beginning you can read all about it here and here.
As you can see for ICS/JB users it's a myth nothing more.
If your using GB then you do have to calibrate your battery, there are 2 methods:
Charge your phone untill you have reached 100% boot into recovery and delete battery stats ('Advance -> Delete battery stats').
Download battery calibration app and follow the steps that are mentioned in the 'Description' of the app and in the app.
11. Network/operator modem support - How to tell if your modem meet your network standards
CM USERS DON'T USE THIS STEP IT WILL BREAK YOUR RIL AND YOU WILL HAVE NO RECEPTION
Every network/operator support a specific version of modem, this means that if you will use their modem, 90% of the time your reception will be solid without any disconnections, if your modem doesn't support, then you will sure have disconnections which will lead into more battery drains (no receptions=phone will search for antennas even though there is one).
Notice: There is a chance that even though you have or don't have their modem you might have or might not have disconnections (confused ? me too.)
How to check:
Download GetRIL, Open the app and see if your RIL/Baseband (aka modem) is matching, if they are (written in green), your good to go and you can remove the app.
If they are not, here is what you need to do:
Under 'Baseband' you have 'recommended':
You can see that LQ6 & LPB are supporting my network, we will now tap this:
and look for LPB & LQ6, after we found it we will choose it and tap: 'Download & install'.
When your done restart your phone and check again (GetRIL) that now your modem is now supporting by your network, if so, remove the app.
12. Variance:
Play store app: Hit the option touch key and untick - 'Notifications' & 'Google AdMob Ads'
When the 'notification' is on, the app is consistently connecting to the server and checking for new versions.
When 'Google AdMob Ads' is on, the app is always checking your behavior and reporting back to the Google server.
'System settings -> Location services' untick everything.
'System settings -> back up and reset' untick 'Back up my data' and 'Automatic restore'.
NOTICE: I didn't apply this step for my own device since it only saves 5% battery more or less and it's a service I use, think, if you need it or not,
WiFi users: 'System settings -> Wi-Fi -> Advance -> Keep Wi-Fi on during sleep' choose - 'Only when plugged in'.
This will close the Wi-Fi connection when you turn off your screen.
Keep in mind that after you finished using your BT turn it off, since I have specific times I use the BT I use AutomateIt, it's a great app that can control even silent modes.
Don't use Facebook app, it drains your battery the most, instead add a shortcut in the desktop for facebook.com link and go to facebook via this link, it looks exactly the same as the app since Android users don't have a native facebook app yet.
Don't use live wallpaper
Don't use widgets
Don't use Haptic Feedbacks
Never ever use Task Killer or 'Clear memory' - Android has it’s own task killer that works better than your 'decision making' brain.
Screen time out - Don't forget to set it
No reception = major battery drains - use airplan mode.
Use Nova launcher or better code efficient luanchers.
Use ad-blocking app in order to prevent unnecessary network usage in downloading ads, I recommand using AdFree - Open the app and choose: 'Boot Normally' and afterwards choose 'Download& Install hosts', when your done restart your phone.
Always charge your phone untill it shows 100% and charge it only if it is below 20-30%
Automatic Date & Time option -> untick
13. Learning to read the battery graph:
This is the final step, come back to this step after you're done with all 12 steps, reading the FAQ (Post #3) and you lost at least 70% of your battery since you charged it.
So you’re here, go to 'System settings -> Battery' and hit the graph bar.
At the bottom you can see 'Screen on' and 'Awake' we will focus on these lines.
Our goal is to achieve 100% overlap between these 2 lines, meaning, when the screen is on, the phone will be awake and when the screen is off we don't want the phone to be awake since we don't use the phone (unless we are-downloading a file).
For example if you see a blue line in the Screen on bar I would like to see at the same time the EXACT size and width in the Awake bar if not, that means we have wakelocks so we need to go to step number 2 again and see who is waking up our phone.
It's really hard to achieve a 100% overlap between these 2 bars, even for me.
Example of a minor wakelock (squared in red):
For conclusion:
You need to be able to get a MINIMUM 3 hours screen time (System settings - >battery - >screen) if not, you're doing something completely wrong.
From my experience you can't get more than 3.5 hours screen time over total use of MORE than 24 hours uptime (Maximum up time I got with the phone is 4 days with almost 3 hours screen time and 1 hour of calls.), however, if you play non-stop with your mobile, from the time you unplugged it, you will get more then 4-5 hours screen time EASY over 5-16 hours uptime:
But of course most of the users don't "act" like that and most of them just "lose" battery over uptime when screen is off.
From my vast experience with battery usage, this is it, either your get 3 hours screen time over moderate usage (long uptime-2 days +) or you get 4-5 hours screen time with aggressive use (short uptime-16 hours top).
Don't let anyone tell you different.
• This is it for now, this thread will be updated with new tweaks and methods every now and then.
• Please, if you have any questions regarding this thread write them in this thread ONLY and don't send me a private msg.
• I love constructive criticism, so if you have any thoughts or you found a mistake (even in my grammer) PLEASE send me a private msg.
Credits and many thanks to:
droidphile – His amazing articles and threads regarding most of my steps, you helped me a lot!
geko95gek – Who inspired me a lot regarding ExTweaks.
JIMMYMCGEE - FD knowledge and guide.
If I forgot anyone please do let me know
If you love this article please do hit the Thanks button and rate this thread 5 stars,also you can hit the "Newsworthy Thread" in the first post if you think this article should get a higher exposure.
If you really appreciate this article you can always buy me some weed - makes me think clearly
Thank you.
FAQ:
Q: Which ROM and kernel you're using ?
A: I am using Wanam ROM (latest version) and Siyah kernel (latest kernel also) CM10.1.3 and Dorimanx 9.41.
After trying all sort of ROM's I can say that the most stable and reliable ROM's are Samsung based ROM's.
I am now recommending CM10.1.3 stable ONLY!
Q: After the tweaking and following your entire guide, does the UI will lag/Games will stuck or freeze/App will run slowly ?
A: Regarding the UI you might feel a little lag (if you were using stock frequencies and voltages) or you might not feel any lag (depends on your launcher), If you install Nova Launcher and use it instead of the TW you won't feel any lag since the Nova launcher is code efficient.
Regarding the apps, you won't feel any lag unless it's a graphic app or design/CAD app (even this is questionable).
Regarding the games, you won't feel any lag in most of the games, I played a lot of games for example Dead Trigger/Galaxy on fire 2/Shadowgun/Samuraio II and few more, I didn't feel any lag or what so ever, though I did feel that the loading steps took 1-2 more minutes.
Q: The most used (or 2nd) most used service/app in BBS is 'AuidoOut', how can I minimize it ?
A: You can minimize the 'Audioout' by unticking: 'System settings -> Sound' , under System, untick them all.
Plus, in the same window click on "Vibration intensity' and put 'Vibrate on screen tap' on the lowest (0).
Q: I keep getting "Shell have been granted superuser permissions" over and over again and it drains my battery, is there a solution ?
A: It's a known problem with SuperUser, install SuperSU give it root permissions via superuser, go to app info of superuser hit "Force Close" and afterwards hit "Disable", now SuperSU will handle your root privilege.
Q: I froze Secphone.apk and now I am having weird issues what should I do ?
A: Obviously you're an idiot since I specifically wrote next to SecPhone.apk: If you're using a different launcher rather than TW you can freeze it.
So don't freeze Secphone.apk if you are using TouchWiz launcher which is the official launcher by Samsung.
Q: How can I tell if my phone is going into Deep sleep and activates the setCPU profiles ?
A: In setCPU go to 'Info' tab and tap 'Time In State', you will find a pie chart, if your a common user-that most of the time his screen is off-, you should see that 200mhz has the biggest chunk, if it's not the case then check BBS what is waking your device.
Q: After installing Gemini App Manager I am unable to install/uninstall any app, what should I do ?
A: You are probably using Screen Filter app, for some reason the install button become unresponsive, disable Screen Filter when you need to install something and enable it again afterwards - Thanks Ryther.
Q: How can I solve BBS wakelocks on the go ?
A: Get in here.
Also, if you have EventLog wakelocks here is the solution:
Download System Tuner. open the app and go to 'Startups' and look for 'Google service framework' and over there disable both 'checkin.EventLogService'.
Be advice EventLogService wakelocks only happens with stock Samsung ROMS.
More to follow.
Great work dude. You gave me some good tips
Sent from my GT-I9100 using Tapatalk 2
gb.yolo said:
Great work dude. You gave me some good tips
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for your positive feedback.
Thanks
I can confirm getting about 3~4 hours of screen time at most during 16~24 hours of usage.
I noticed you wrote something about SetCPU working on stock kernel ... in my experience it does not work even if some people claims so.
SetCPU might be able to change between a limited amount of Governors, but setting Min and Max doesn't work even it looks so (I used some other tool to confirm this). I only tried this on rooted Stock GB, but I think it will be the same on ICS.
Does this work on jb rom?
Sent from my GT-I9100 using xda app-developers app
good tips
Thanx
Ben101 said:
Does this work on jb rom?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
It work on any rom
Mittaa said:
Thanks
I can confirm getting about 3~4 hours of screen time at most during 16~24 hours of usage.
I noticed you wrote something about SetCPU working on stock kernel ... in my experience it does not work even if some people claims so.
SetCPU might be able to change between a limited amount of Governors, but setting Min and Max doesn't work even it looks so (I used some other tool to confirm this). I only tried this on rooted Stock GB, but I think it will be the same on ICS.
Click to expand...
Click to collapse
Thank you for confirming though you could get more.
and I didn't say what you wrote, I specifically wrote:
If your kernel doesn't support undervolting move to the next step
Click to expand...
Click to collapse
Ben101 said:
Does this work on jb rom?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I didn't try with JB, but I'd love if you could follow each step and report back with results, in my opinion it should be the same.
soso_soso said:
good tips
Thanx
Click to expand...
Click to collapse
Thank you for the feedback, please do try all the steps and report back for success.
great tutorial, thank you for your effort!
I followed the steps but I can't find this one in LBE security:
"c.After your done go to the first window (swipe your finger right to go to the first screen)
d.Choose 'Speed boost -> Auto-Start' you will see all the apps that will be put in the cached process EVERY restart you make to your phone, now, this is very important, I only say it once, if you see an app/game that you don't even use or use once a week 'Disallow' it, but if you see an app/game that you use most of the time leave it as it is, why ? Obviously you didn't read step number 1.
"
trikpa said:
great tutorial, thank you for your effort!
I followed the steps but I can't find this one in LBE security:
"c.After your done go to the first window (swipe your finger right to go to the first screen)
d.Choose 'Speed boost -> Auto-Start' you will see all the apps that will be put in the cached process EVERY restart you make to your phone, now, this is very important, I only say it once, if you see an app/game that you don't even use or use once a week 'Disallow' it, but if you see an app/game that you use most of the time leave it as it is, why ? Obviously you didn't read step number 1.
"
Click to expand...
Click to collapse
Thank you for your positive feedback, please do come back with results and post them here.
As you can see in the picture, this is the first screen you see when you open up LBE,2nd raw is 'Speed Boost' just click it and it will show you new buttons, there you choose 'Auto-Start.
EDIT:
I have added pictures to the main thread for most of the steps and marked in red the specific step.
I got confused because in my app it says phone accelerate instead of speed boost
anyway, I'm using these mods since this morning so it is too early to say anything factual about battery life, but I think it is much better...
usually I would have about 60 or less % left at this time of day...
trikpa said:
I got confused because in my app it says phone accelerate instead of speed boost
anyway, I'm using these mods since this morning so it is too early to say anything factual about battery life, but I think it is much better...
usually I would have about 60 or less % left at this time of day...
Click to expand...
Click to collapse
Perhaps you downloaded even newer version than mine but I can see you figured it out.
If you used to get 60% and now it's 76%, of course this is an amazing change.
Don't forget to check your screen time before you charge it and make sure it's minimum 3 hours (if the total up-time is above 24 hours).
If you did follow all the steps and did everything as I wrote, I suggest to get into Recovery mode -> Advance -> and reset battery indicators.
or wait 1-2 charges and the battery meter is supposed to acclimate.
hyperbolic said:
From my experience you can't get more than 3.5 hours screen time over total use of MORE than 24 hours uptime
Click to expand...
Click to collapse
Well is that so?
Nice thread, but Gemini app manager block on "updating information" sometimes :x
MrMarques01 said:
Well is that so?
Click to expand...
Click to collapse
I saw really few users like your self that actually got that time, but I had never got more then 3.5-4 hours max screen time on uptime for more then 24 hours.
I even did EXACTLY what these users told me with their exact config (from 3 different users) but again, I got only 3.5-4 hours screen time max.
So this is my conclusion.
Kigsuha said:
Nice thread, but Gemini app manager block on "updating information" sometimes :x
Click to expand...
Click to collapse
Thank you.
Yea that's an annoying bug that is happening from time to time.
Just exit the app and open it again.
hyperbolic said:
I saw really few users like your self that actually got that time, but I had never got more then 3.5-4 hours max screen time on uptime for more then 24 hours.
I even did EXACTLY what these users told me with their exact config (from 3 different users) but again, I got only 3.5-4 hours screen time max.
So this is my conclusion.
Thank you.
Yea that's an annoying bug that is happening from time to time.
Just exit the app and open it again.
Click to expand...
Click to collapse
I found solution, it only happens when after taping "config autorun (root)" and switching fast thing to off.
So i have to wait :cyclops:
Kigsuha said:
I found solution, it only happens when after taping "config autorun (root)" and switching fast thing to off.
So i have to wait :cyclops:
Click to expand...
Click to collapse
Sometimes you just wait for too long but if you have patience for that..
hyperbolic said:
Last update:29/9/12
[*] If after step b&c your phone is still working that means that the undervolt you chose is working great. (
Click to expand...
Click to collapse
hyperbolic what do you mean by step b&c ?
There just core1 sucessful
core2 sucessful
Ram sucessful
Related
As android builds are getting more and more closer to being daily builds, one of the standing issues that remains is battery life.
This thread is where posts concerning How to Save battery should go. NOT Questions, but suggestions. If your suggestion is one to look into, it will be added to the OP.
UPDATE: You can now use ALL GOVERNORS For the CPU! (Read more to find out how) --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
SetCPU
SetCPU, is an app more commonly used for over/under clocking devices.
This short tutorial will show you how you get the app,
get it running, and of course save battery!
*YOU NEED A ROOTFS.IMG THAT GRANTS YOU ROOT ACCESS!*
1. Get SetCPU
A. Download it from *HERE*. (The only XDA thread I could find for it)
OR
B. Support this great application and get it from the Android market by searching for SetCPU.
-----------------------------------------------------------------------------
2. Getting the App working
1. Once you have the application installed, launch it from your drawer and either grant it Root Permissions or it may auto-configure.
2. Hit Auto Detect Speeds.
3. It should show you the speeds your device it currently running at, now move over to [Profiles] and click Enable and if you want click on Notification.
-----------------------------------------------------------------------------
3. Make your profiles
1. Sleep Profile - 384 Max/245 Min- Interactive setting
(It may seem high, but this keeps it so that your device wakes up quickly)
2. Battery < 30
Max 614/460 Min- Interactive/Conservative Setting
*Try out the SetCPU Widget!*
If you have any personal settings that you think might be better than these please do post!
-----------------------------------------------------------------------------
UPDATE 9/15 ALL CPU Governors!
To use the modules use this kernel built from the GIT, and hit auto detect speeds on SetCPU again. Under the main tab choose Your preferred setting..
You can find what all the the kernels differ in in the further pages of this thread, I will update OP later.
-----------------------------------------------------------------------------
Advanced Tab
20000 Sampling Rate
30-50 Up Threshold (THIS IS THE KEY: This means when your CPU load hits 30%, it will scale up the mhz. If the phone still responds too slow for your taste, set this lower)
http://forum.xda-developers.com/showthread.php?t=777921
Check Set on Boot (And Apply)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Turning off Background Services and Adjusting Brightness
Things like Bluetooth, WiFi, Sync, GPS, and excessive brightness can really kill your battery.
A quick way to manage these settings is to hold down to add a widget on your home screen and choose [Power Widget].
This stock widget allows you to quickly see the service's your using, and the farthest one to your right allows you to switch between four brightness settings.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Using that new kernel link provided, you'll get a nice boost in standby time too! Enjoy!
Additional battery saving tips:
* Don't use a live wallpapers
* Turn off 3G connectivity (Eclair-based ROMS need apps like APNDroid to do so)
* Turn off Background-enabled data transfers in the Sync page.
the app screebl is a battery saver for whenever you have your screen on.
MOD EDIT:
Screebl Pro is a PAID FOR APP..
Link deleted and warning given please do not post warez in the future.
Mark.
Is that a Paid application from the Market? If so it is warez. (Big No-No)
Shatterv2 said:
Is that a Paid application from the Market? If so it is warez. (Big No-No)
Click to expand...
Click to collapse
no it's donation-ware. You can find SetCPU in the G1 device section of the XDA forums for free...
http://forum.xda-developers.com/showthread.php?t=505419
Can we have on our hd2 a folder with Android Sdk ? Like in a rooted one ?
aussiebum said:
no it's donation-ware. You can find SetCPU in the G1 device section of the XDA forums for free...
http://forum.xda-developers.com/showthread.php?t=505419
Click to expand...
Click to collapse
Yes that was already stated in the OP
Shatterv2 said:
*YOU NEED A ROOTFS.IMG THAT GRANTS YOU ROOT ACCESS!*
Click to expand...
Click to collapse
Can you post one?
Ultimaex said:
Can you post one?
Click to expand...
Click to collapse
read here: http://forum.xda-developers.com/showpost.php?p=7088391&postcount=4
Thanks for the tips!
Ultimaex said:
Can you post one?
Click to expand...
Click to collapse
Rooted RootFS.img files by michyprima can be found *HERE* in the Installation Instructions section.
Mark.
SetCPU forcecloses on me with dan's froyo without sense. Anybody get this combo to work for them? Also, I did replace the rootfs file.
Strange, try the new froyo build by Darkstone.
reocej said:
SetCPU forcecloses on me with dan's froyo without sense. Anybody get this combo to work for them? Also, I did replace the rootfs file.
Click to expand...
Click to collapse
Yeah, I'm using SetCPU 2.01 with Dan's v1 vanilla froyo fine. When set to use "ondemand" CPU Governor and Autodetect speeds, getting much better battery life - it's only dropping ~1% every hour now EDIT: when idle, of course
aussiebum said:
Yeah, I'm using SetCPU 2.01 with Dan's v1 vanilla froyo fine. When set to use "ondemand" CPU Governor and Autodetect speeds, getting much better battery life - it's only dropping ~1% every hour now EDIT: when idle, of course
Click to expand...
Click to collapse
Happy to help!
Next thing (when I get around to it) is probably to try out the Conservative CPU Governor module... that will correctly scale CPU power according to load (ie. 245mhz => 384, etc) instead of like On Demand, where it jumps from 245mhz => 998mhz => lower....
ATK
My favorite Ap Right now: Advanced Task Killer - you can find it on market for free. With this you can kill tasks who run in backround etc.
RuffRap said:
My favorite Ap Right now: Advanced Task Killer - you can find it on market for free. With this you can kill tasks who run in backround etc.
Click to expand...
Click to collapse
Use Taskiller. Red Icon in the market. Free App is the exact same as the paid one. Kills tasks as well but detects tasks that ATK cant. Includes features like End apps once screen turns off and kill all apps 10sec's after boot. Great App IMO.
I've found out that JuiceDefender does a good job as well. If you buy the extension (UltraDefender?) it also has a CPU governer module which regulates your CPU speed based on usage.
maseo said:
I've found out that JuiceDefender does a good job as well. If you buy the extension (UltraDefender?) it also has a CPU governer module which regulates your CPU speed based on usage.
Click to expand...
Click to collapse
No need to pay - as I mentioned before, the "conservative" cpu governor module that is freely available (do a search!) will do exactly what you mentioned when used with SetCPU.
I have picked up lots of bits of information about how to maximize space issues and maximize battery life for those of us who are in love with these amazing new NAND builds....especially those of us with European HD2 phones who only have 512MB to play with
I have compiled them below for ease of reference - I claim no originiality for these ideas...I am just bringing them together...so MAJOR THANKS TO ALL THOSE OUT THERE! You know who you are...
I have already posted this on the DFT thread as I love that particular build, but they should (might!) work for other builds and I post it here for further reference as it took me a long time to sift through the threads to find it all.
Space
1. Before flashing your phone, using DFT Stock Desire, for example, you can edit the flash.cfg file and change the following line:
cache ya 40M >>to>> cache ya 15M
This reduces the cache by 25M with no discernible impact on the speed of the build (imo).
This should give you in excess of 130MB free after a clean flash on that particular ROM. Expect that to drop to around 100MB once Market, Flash and a couple of other apps update themselves.
Some NAND ROMs will not even have this as an option, and others may look a little different. You can read about how the flash.cfg file is structured here.
2. Immediate install Z4 to root your device. You will need to get it from here. (Note: it may get stuck on 'Rebooting'. Wait a minute or so and then manually reboot - it will work fine and SuperUser will now work after the reboot)
Put it on your SD card and then install a file manager from the Market to browse to it and then install and run. Follow the details on the thread...
3. Install Move2SD. You can get it from the Market. Full details are here.
This allows you to move most (not quite all) apps to SD. It is the best option I have found to move most of those awkward apps.
I have now installed pretty much all of my apps that I used to run on non-NAND builds and have moved about 90%+ of them to the SD card. At time of writing I have loads of apps installed and still have over 70MB free
Battery
1. Install Battery Monitor Widget or Current Widget from the Market so that you have a way of tracking your current usage.
2. Install Set CPU - free for XDA members from here, but also available on the Market.
After setting your Main Screen to 'OnDemand' and 'Set on Boot', assign SetCPU a couple of profiles. I tend to use:
>> Screen Off: Max/Min 245000, Scaling 'OnDemand', Priority 50%
>> Battery <25% Max 384000/Min 245000, Scaling 'OnDemand', Priority 50%
You can play to your hearts content here, but these give me consistently 7ma in Standby.
Also, you can reduced the sampling rate to 20000 and 'Set on Boot' in Advanced if you like.
3. Avoid power hungry background stuff like animated wallpapers and turn off GPS, Wireless etc. There are LOADS of apps out there that can do this automatically for you free from the market, but I have found that making sure my GPS is off (I have a widget to show me) plus SetCPU is plenty. It may work for you though.
4. Some have reported that Darkstone's suggestion makes a major difference to their power consumption:
"To fix high power drain / usage in standby (60mA or 70mA) disable 'Use wireless networks' in Settings>Location menu. You will now get 7mA or less constantly. I discovered this as the main culprit last night. Also works in other builds."
Anyway, there you go - a few consolidated thoughts - happy NANDing!
How to root Gauner HD V0.3 ? root not the same /system/...
Thank you !
dungphp said:
How to root Gauner HD V0.3 ? root not the same /system/...
Thank you !
Click to expand...
Click to collapse
Not sure I'm afraid...have you tried it? I tried it and Z4 got stuck on the 'Rebooting' screen, but when I manually reboot it had solved it...
dungphp said:
How to root Gauner HD V0.3 ? root not the same /system/...
Thank you !
Click to expand...
Click to collapse
isn't that the v0.3 itself already been rooted at the first place?
I installed Root Explorer and gotten root access immediately...
But can't check permission some folder to change themem or something !
When you do this
"To fix high power drain / usage in standby (60mA or 70mA) disable 'Use wireless
networks' in Settings>Location menu. You will now get 7mA or less constantly. I discovered this as the main culprit last night. Also works in other builds."
Click to expand...
Click to collapse
You will loose weather on main screen. It will say "To see local weather tap here"
SetCPU doesnt work on Nand ROM..Is there any similiar program like SetCPU for Nand ROM ?
well guys i really dont understand why everybody you complaining about nand build
well my nand build is nexus one and i get 2-3ma battery drain in standby
olso the spuset in on 1190smartass
i dont want to be a smartass guy, but please ram and rom is different
ram = random access memory
rom = read only memory
when i look at the thread title of couse i think about ram, not rom... and too much thread title have that 2 things mixed in and im sure that will make alot of people (including me) confused
btw i thank you for the info
Clubeer said:
SetCPU doesnt work on Nand ROM..Is there any similiar program like SetCPU for Nand ROM ?
Click to expand...
Click to collapse
It does for me Are you rooted?
aboveluna said:
i dont want to be a smartass guy, but please ram and rom is different
ram = random access memory
rom = read only memory
when i look at the thread title of couse i think about ram, not rom... and too much thread title have that 2 things mixed in and im sure that will make alot of people (including me) confused
btw i thank you for the info
Click to expand...
Click to collapse
You're quite right - too much 'New Year cheer' the day before I started the OP
Have changed it as you correctly point out - thanks.
This thread will only contain detailed but simple and easy to understand information and broken english because I'm Mexican and I live in Mexico.
This is my first thread in XDA, this phone is my first smartphone or touchscreen phone I got it a year a go when It came out and this post will have all my knowledge about SGS2 battery saving tips I've got from this year.
Some settings might sound dumb, like why would you disable a core if you paid for two, and why would you want lower brightness if you have a SAMOLED+ screen which is brighter than SAMOLED HD, well those settings are optional and you have to find which ones will help you when you need battery badly for an emergency or something.
First let's make a list of all the apps that you need to use and what they will do, all the apps and tips are optional but if you use all of them you will have some amazing battery life!
*This thread only contains free apps so you don't need to spend $ at all!*
#1 Screen filter: https://play.google.com/store/apps/...ch_result#?t=W251bGwsMSwxLDEsImNvbS5oYXhvciJd
This app is really useful because it allows you to go on lower brightness than what your phone allows you to! and if you have sensitive eyes it'll help at night, when I really NEED BATTERY I lower the brightness as much as I can (Don't go too low because you won't be able to see s**t.
while in use, screen filter make the install button in the package installer unusable; if you want to install an app, disable screen filter first
#2 Rescan Media ROOT: https://play.google.com/store/apps/...SwxLDEsImNvbS5hZGR6Lm1lZGlhc2Nhbm5lcnJvb3QiXQ..
This app will allow you to enable and disable media scanner whenever you want. Media scanner drains ur battery a lot specialy if you're using a JB ROM! I don't know if it'll be useful with GB/ICS because I only tested it on a JB ROM, by disabling media scanner you won't be able to see pictures or videos from your gallery but you're able to play music, use this when you really need to save battery and you're not gonna use gallery.
#3 https://play.google.com/store/apps/...sMSwxLDEsImNvbS5yb290dW5pbnN0YWxsZXIuZnJlZSJd
BE CAREFUL WITH THIS APP! IF YOU'RE NOT SURE OF WHAT YOU'RE DOING ASK AN EXPERIENCED USER OR JUST LEAVE IT!
Titanium backup has an option to uninstall system apps but this one is free, just use it to freeze apps that you don't use and are always running, the apps I disabled are:
*Maps (I enable em when I need them)
*TvOut
*AccuWeather
*Movie Studio
*TalkBack
*Apollo (I use PowerAMP)
*Sound Search
*Voice dialer (Useless IMO..)
*SIM Toolkit (I don't know if this is safe to remove for all users but I had no problem)
*Trebuchet (I use Nova Prime)
*News & Weather
And you can disable other apps that you don't use, those are the ones I disabled.
#4 Startup manager: https://play.google.com/store/apps/...wsMSwxLDEsImltb2JsaWZlLnN0YXJ0dXBtYW5hZ2VyIl0.
This is my favorite, I don't know how useful it is but I hate to have apps I don't use running or on the background.
With this app you can disable the user and systemapps that auto start when you turn on your phone, they will start without any problem when you need them!
This app will give you more free ram! I don't know if the RAM on phones consume as much energy as PC RAM but I used it anyway..
The system apps I disabled are the following:
*Youtube
*Clock
*Email
*Download manager
*Media Storage (I guess you don't need this is you disabled media scanner already with the previous app)
*Gallery
Those are only the system apps, remember to disable YOUR apps that are always running on boot and you don't need them to be running (I only kept facebook, facebook messenger, nova launcher and whatsapp) I don't suggest you to disable many google apps, I think it gives problems when trying to connect to google servers (NOT SURE) disable them if you want and if it give you any problem just enable them again.
#5 FastDormancy Toggle: https://play.google.com/store/apps/...W5tb3JhbC5mYXN0ZG9ybWFuY3l0b2dnbGUuaTkzMDAiXQ..
First do a google search and check if your carrier supports FD, my carrier doesn't support it so I disabled it and you can uninstall this app after disabling it if you want.
#6 AdFree: https://play.google.com/store/apps/...DEsImNvbS5iaWd0aW5jYW4uYW5kcm9pZC5hZGZyZWUiXQ..
This app gets rid of the annoying ads, they consume battery because they use 3G to load and they're annoying anyway, just install it and after it downloads the host files and installs them you can uninstall this app if you want, if you start to get Ads again just install it again and update the host files and uninstall or you just can keep it and let it download the new host files.
#7 GetRIL: https://play.google.com/store/apps/...t=W251bGwsMSwxLDEsImNvbS5zaWJib3IuZ2V0cmlsIl0.
Some users have better batterylife after matching their RIL with the current modem, you can uninstall this app after installing the right RIL but I think the RIL will keep changing everytime you flash a new ROM. This app is supposed to keep you away from RIL crashes, try it. and uninstall after using it.
Ok that's it now let's move to the tips, some of them might have you tired already but I'll put them for the new users.
#1 If you're not gonna browse, use facebook or any app that requieres 3G just disable it, I have 2G most of the time because I only use whatsapp and gtalk the most.
#2 Disable WiFi, GPS, Bluetooth and Sync if you're not using it.
#3 Disable google now (It improves battery a lot according to some users)
#4 If you're lazy to control your brightness just set it automatic, I use the notification bar slide brightness from CM10 and I always have it really low.
#5 Try not to have too many root apps running on start up because SU makes the phone laggy when it tries to enable too many root apps.
#6 If you have a weather app set "refresh manualy"
#7 If for some reason after using all the apps from above you still have unwanted apps running just stop them manualy, I check running apps really often and stop them.
#8 Some people have better battery life with different modems, I always use stock modems so try different modems and check which one suits you better
#10 Don't let your phone charging overnight
#11 If you're REALLY need battery and you're on a trip only listening music with the screen off, set your CPU to 200 Mhz or 500 Mhz if you want, Music player is a light app but some music players keep going from 100-200 mhz to 800-1000 ..
#12 Try to enable the skip track with volume key from CM10/AOKP, this will save battery as you won't turn the screen on everytime you want to skip track and If you use the 200 Mhz max frequency you won't have to go through the lag to skip a track (If your galaxy lags a lot at 200 Mhz, some phones don't lag that much at that frequency)
#13 Disable BLN
#14 If you're not using the internet at all put flight mode
#15 Use dark or black wallpapers and themes, our SAMOLED+ Screen saves energy if you use black/dark themes/wallpapers
#16 If you have facebook and you need more battery try to log off your facebook and facebook messenger, it'll save you some battery (credits to Obagleyfreer for this tip)
Now let's get into the ROMs and Kernel subject.
I'm using Dorimanx 7.3 and I'm using JellyBam ROM at the moment but I change ROMs really often, I think JellyBam has vsync enabled so I guess a ROM without vsync and Dorimanx 7.3 will have better batterylife.
ExTweaks settings:
Easy.. Just go to recovery and go into specific kernel options and put Battery profile.. If you have ExTweaks plus you'll be able to change the profiles from the app and you'll see the Extreme_battery profile, enable it if you have ExTweaks plus.
After you set battery profile go to the CPU tab and put second core always off if you're just chatting and listening music you don't need both cores enabled.
Oh yeah and undervolt your CPU/GPU in ExTweaks, I have CPU UV -75.
If you did a charge cycle and your phone is at 100%, unplug it and go to the MISC tab on ExTweaks and Reset Fuel Chip and charge it again to 100%, I usualy reset it like 10 times after flashing a ROM, I unplug and reset and plug and like that a few times.. I'm not sure if it helps at all but I do it anyway.
**I think some users reported that slower charge gives better battery, in ExTweaks MISC tab theres an option for charging voltages, set the lowest AC/MISC:550mA USD:450mA (I haven't tested it but I will do it soon**
I'm adding more info to this thread and giving credits in a few minutes I have to eat dinner.
As I explained I'm from Mexico and this is my first help/guide thread in XDA, If you liked how I shared all my knowledge and want to help me with a donation feel free to do it, I'm from Mexico as some of you know this country is really poor and even 30 cents or 1 USD will help me, 1 USD is like 13 mexican pesos.. feel free to donate if you want, any amount will do fine.
Ok after trying to discharge my phone using Max brightness, both cores enabled, screen on all time, PowerAMP on speakers all the time with max volume, 1.5Ghz, Extreme_Perfomance profile I got 3 hours 30 mins screen time.. I couldn't take a screenshot cause I took too long to take it and I had media disabled Now I'm going to try with my settings and post the results! Please if you tried my guide and got amazing battery life post a screenshot of your battery graph and screen on time or tell us the results!
Mexico loves xda <3
Reserved ~~~~
Great! Thank you!! I'll try it all!
Gesendet von meinem GT-I9100 mit Tapatalk 2
Netjoker said:
Great! Thank you!! I'll try it all!
Gesendet von meinem GT-I9100 mit Tapatalk 2
Click to expand...
Click to collapse
Thanks If you have any question feel free to ask, I'll add a FAQ question and more details to the thread if needed, this is my first thread and I'm really noob at this I hope you guys help me to make this thread perfect and maybe even get sticky! This ALL you need for good battery life, I forgot some stuff but I'll add it once I remember it xD
I need enable the other CPU core
Sent from my SAMSUNG-SGH-I727 using xda premium
Mervingio said:
I need enable the other CPU core
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
What do you mean? Both cores will run on your Galaxy when you need them but the second core isn't enabled all the time, only when you need it.
Great instructions.I am using JellyBam ROM 20121022 – i9100 daily [OUT DA SPACE REL] with siyah v5.0b1
Well i underclocked my device to 100-500 mhz with 2 cores running all the time... voltages as low a i can... gpu 40 66 100 mhz... the only thing i took from this thread is the screen filter,thanks for that! now i usually get 7 hours screen time 2 days running
Elistheman said:
Well i underclocked my device to 100-500 mhz with 2 cores running all the time... voltages as low a i can... gpu 40 66 100 mhz... the only thing i took from this thread is the screen filter,thanks for that! now i usually get 7 hours screen time 2 days running
Click to expand...
Click to collapse
Your welcome You should try the startup manager to get rid of the apps that auto start!
A handy tip to help battery life is remove Facebook app. It is a HUGE battery drain.
The best thing to do is to log onto the Facebook Mobile site then when you're on the homepage just save as a bookmark.
Now you can add the bookmark to your home screen as an icon.
It's just like Facebook app only faster, less bugs and battery friendly
Sent from my GT-I9100 using xda app-developers app
Obagleyfreer said:
A handy tip to help battery life is remove Facebook app. It is a HUGE battery drain.
The best thing to do is to log onto the Facebook Mobile site then when you're on the homepage just save as a bookmark.
Now you can add the bookmark to your home screen as an icon.
It's just like Facebook app only faster, less bugs and battery friendly
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I'll add it to the list of tips
Great post
One thing though: I would advice you NOT to fully drain your battery unless absolutely necessary. This will lower the full capacity of your battery. It's the same thing that happens to laptopbatteries. Many people let it run dry from time to time and this is one of the reasons people experience such a severe hit on laptop battery capacity over time.
This is also the reason why you phone will shut down before battery hits 0%. It's simply to spare the battery from degradation.
Sent from my GT-I9100 using xda premium
Thx !
abnesher said:
Great post
One thing though: I would advice you NOT to fully drain your battery unless absolutely necessary. This will lower the full capacity of your battery. It's the same thing that happens to laptopbatteries. Many people let it run dry from time to time and this is one of the reasons people experience such a severe hit on laptop battery capacity over time.
This is also the reason why you phone will shut down before battery hits 0%. It's simply to spare the battery from degradation.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
thanks, I removed the tip
nice!
here are some more facts about different batteries and their behavior. Remember that u have a lithium-ion battery in your smartphone:
h**p://batteryuniversity.com/learn/article/how_to_charge_when_to_charge_table
This supports also the posting from abnesher.
//sorry for masking the url with * but im not allowed to post urls cause i am new
thx alot i'll try it
Ingesting Read! But I suggest you to add this disclaimer to the Screen Filter section: "while in use, screen filter make the install button in the package installer unusable; if you want to install an app, disable screen filter first"
Hope it's useful for you
Sent from my GT-I9100 using xda app-developers app
PunkOz said:
What do you mean? Both cores will run on your Galaxy when you need them but the second core isn't enabled all the time, only when you need it.
Click to expand...
Click to collapse
System Tuner works like a charm
Thanks for the tip!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Ryther said:
Ingesting Read! But I suggest you to add this disclaimer to the Screen Filter section: "while in use, screen filter make the install button in the package installer unusable; if you want to install an app, disable screen filter first"
Hope it's useful for you
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Edited, Thanks!
Hi, finally here I am with my new Nexus 4. Through different devices that i disliked (like Acer LM, Nexus S in part), now I see a very good phone that does like everything. So here I wanna clear all my (and ours) main doubts regarding settings or tools that improves it. I red a lot in this and in a great italian forum, but some matter isn' t totally understood by people so informations may be subjectives and not in the same way.
So let's start
1- in the beginning of my history with android, 4 years ago, I thougt that 3g data with a good company works perfect with normal settings. But since 2 years I'm using a good and necessary app, Rom Toolbox. It also backup apps, but here it's important the set DNS function. In the past I saw improovements tapping Google DNS, internet was fast, but now, for example, using google search, it takes 2-3 seconds for showing results.
Why this "connection freezing"? Maybe other settings may be helpful for connection ?
ex."auto apply wifi/mobile network tapped, or improove dwd speed in some way...
2- A) I see that some rom users has wonderful battery experience. I would like me too , so I tried CodeFire X + matr1x 7.5 .
It has 10 days of life, but I would like to set everything, so : I need to do the undervolt fix, in addiction to the matr1x kernel (probably already undervolted), or this isn' t necessary?
Do you think that exists better ROMs regarding fluidity/battery improovements? Here I have 0 lag, for now (with a lot of apps installed with no notifications drains).
But I'm not very happy regarding battery: 2hours 22minutes, now 79% with 38% screen (46min), 32% phone calls (18min), 6% android and 4% firefox, connected with 3g (low use).
B) I tried Easy battery saver, i'm so uncertain regarding this kind of apps, because users opinion is so differents, like the choice (EBS, JD,2xB, Green Power). I choice this one only for download and stars rating.
But also Snapdragon may be good. For now, i found on them the lolzful situations: people that talks about 24 hours improovment(!!!) and a lot of people that is very happy, but on the other side others that says that process drains a lot of battery.
I think, at the end, that probably one of this apps may be good for battery, and you? If yes, I can't understand the best one.
3- A) android assistant: I can't understand if the "clear process" widget really free RAM or not. In the past I also red that task killing isn't good for android, but freeing RAM may be good (if apps are really closed, and don't re-open after memory release).
on nexus s I loved to close all processes with it's icon on the bottom of the screen. Now isn' t included (stock included, dunno why), so I can use Android Assistant as substitute?
B) boot assistant on AA really closes all app that i tap? I have everything blocked, like 10-15 processes ,unless sms and 2 widget.
4- I passed 4 hours for understand that dolphin can't import firefox bookmarks, it can't see folders. So I tried FF for android and now oviously they sync and passed everything. But I can't understand how to set FF bookmarks widget, no apps or ways to do it. If not, it's also perfect having a FF bookmarks shortcut
I red about a way to pass them on stock browser, ok , but after I can see on the stock widget all my folders and bookmarks inside?
5- FastGPS is always useful for improoving GPS signal?
please help!!
give me knowledge!!
4 years you have been using android and you still have not got it that battery life is 99% of the time kernel related...
Sent from my Nexus 4 using xda premium
persheshhater said:
4 years you have been using android and you still have not got it that battery life is 99% of the time kernel related...
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
seems to be a short answer for explaining all, but it only answer a half question - 2) B
I wrote 7 questions(5 +2), so there is much more to say than 20 words.
persheshhater said:
4 years you have been using android and you still have not got it that battery life is 99% of the time kernel related...
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Hi,
Wrong, it's 99 % user related... (CPU settings -> overclock / underclock / undervolt / governor, brightness, sync -> mails / meteo / social network, rogue apps, data -> Wi-Fi / 3g, reception, usage -> games / browsing or just sms, etc...)...
Yes sometimes a bad battery life can be due to the kernel (bad kernel wakelocks) like sometimes a custom kernel can correct some weird little issues with battery life compared to the stock kernel, but people tend to believe that the kernel or the rom that makes your battery life and ONLY this. It's mainly the user... at least at 95 % of the time.
Don't blame the kernel if you have a rogue app, if you don't know how to use / set your phone (or your CPU) / set your apps correctly for better battery life...
viking37 said:
Hi,
Wrong, it's 99 % user related... (CPU settings -> overclock / underclock / undervolt / governor, brightness, sync -> mails / meteo / social network, rogue apps, data -> Wi-Fi / 3g, reception, usage -> games / browsing or just sms, etc...)...
Yes sometimes a bad battery life can be due to the kernel (bad kernel wakelocks) like sometimes a custom kernel can correct some weird little issues with battery life compared to the stock kernel, but people tend to believe that the kernel or the rom that makes your battery life and ONLY this. It's mainly the user... at least at 95 % of the time.
Don't blame the kernel if you have a rogue app, if you don't know how to use / set your phone (or your CPU) / set your apps correctly for better battery life...
Click to expand...
Click to collapse
nice!
that was the reason because i asked theese questions.... so can i have your opinion?
still need help....
My background with android is long and rocky.
A long time ago in a galaxy far away, I had a Samsung Galaxy S, then a S2.
I can remember a Google Nexus phone in there somewhere.
Then at some point I switched over to Windows Mobile for many years.
A couple of hears ago I came back to android with a Samsung Galaxy S8+ and I hated it.
Recently I upgraded to a OnePlus 6T McLaren and here I am.
I had been expecting to see android happily use up 7, 8 or even 9GB of ram before the background task manager would begin to kill tasks.
Except that I seldom saw android use much more than 5GB of ram.
And worse, background tasks were being killed on a regular basis.
Widgets would stop working overnight, or even in just a few hours.
Spotify would close while a playing a playlist.
A quick search on XDA reveals that many users believe that Android will just use up as much ram as your phone has.
However, that is simply not true.
And so, I began my quest to have Android use as much ram as the phone could provide.
In my case, 10GB.
- I understand that there is an inherent trade-off between keeping background apps running and battery usage. I can live with extra battery usage in exchange for keeping my widgets running or Spotify running for an entire playlist.
- I realized very quickly that in order to achieve the results that I was looking for that the phone would have to be rooted. So rooting was one of the first things that I did.
Step 1.
I started with the basic stuff that a quick google search would provide;
- Settings -> Battery -> Battery Saver (off)
- Settings -> Battery -> Adaptive Battery (off)
- Settings -> Battery -> Battery Optimization -> widget app (don’t optimize)
- Settings -> Battery -> Battery Optimization -> Spotify (don’t optimize)
- Settings -> Battery -> Battery Optimization -> Advanced Optimization -> Deep Optimization (off)
- Settings -> Battery -> Battery Optimization -> Advanced Optimization -> Sleep standby optimization (off)
- Settings -> Apps -> Widget app -> Battery -> Background Restriction (app can use battery in background)
- Settings -> Apps -> Spotify -> Battery -> Background Restriction (app can use battery in background)
This helped but not enough to make the widgets or Spotify usable.
Step 2.
I supposed that my specific background tasks that I wanted to keep running were being killed because of the many other apps that were running in the background.
I searched for and found Tomatot DeBloater scripts for the Oneplus 6.
Excellent! Just what I was looking for.
I chose the Tomatot-Debloater-OOS-Light-2.3.zip and installed it.
This helped some more but not enough to make the widgets or Spotify usable.
Step 3.
I realised that there were still some apps running in the background that I didn’t use or want.
So I used Titanium Backup to freeze the following apps;
- Calendar
- Calendar Storage 9
- Contacts (O+)(I replaced with google contacts)
- Dashboard
- Drive
- Face Unlock
- Gboard
- Gmail
- Google
- Google partner setup 9
- Google play music 8
- McLaren AR
- Messaging (O+)(replaced with google messaging)
- OK google enrollment 9
- Oneplus system 1
- Youtube
Perfect! These apps were no longer competing for phone resources with the apps that I wanted to run.
This helped some more but not enough to make the widgets or Spotify usable.
This did make the phone feel faster and smoother.
The phone is much more responsive and fluid to my input.
This made me realize that the apps were being closed not due to a lack of phone resources, but a background task manager being aggressive.
Presumably for battery saving purposes.
I changed my focus to adjusting that background task manager.
Step 4.
Enable the recent screen ‘LOCK’ on the widget app and Spotify.
This didn’t do anything for me.
Everything that I’ve read on it says that it just stops the task from being killed when you click on kill all tasks.
The lock doesn’t lock the task from being killed by the background task manager.
Step 5.
Further google searching led me to believe that the OEM kernel was limiting background tasks.
I choose ElementalX-OP-3.09 and the EX Kernel Manager.
I had to read a lot of google university material to make any sense of the settings in here.
I’m not sure that I fully understand even now.
Eventually, I ended up with the following settings;
Memory
- Adaptive Low Memory Killer (disabled)
- dirty ratio (20)
- dirty background ratio (5)
- min free kbytes (12398)
- vfs cache pressure (100)
Memory -> Low Memory Killer
- apply on boot
- Foreground app (72mb)
- Visible apps (90mb)
- Secondary server (108mb)
- Hidden apps (200mb)
- Content Providers (587mb)
- Empty apps (783mb)
This helped a lot.
This almost made the phone usable to the state that I wanted.
But the widget and Spotify would still stop running overnight and by morning the apps would have to be reopened to get them to run again.
At least the apps would run most of the day without being killed.
Still not the behaviour that I expected from a phone with 10GB of ram.
Ram usage was still not going much over 5.5Gb even if I opened up many apps at once.
Can I ever get ram usage up to the 10Gb that I have?
Step 6.
The last thing that I tried yesterday afternoon was to increase the background task limit in the build.prop.
ro.vendor.qti.sys.fw.bservice_limit=5 (changed it to 60)
ro.vendor.qti.sys.fw.bservice_age=5000 (changed it to 10000)
Yes, I know that I am on PIE and there isn’t supposed to be any effect.
No, I don’t know yet if this had any effect.
I am hopeful.
The widget app didn’t close last night, but Spotify did.
I am getting closer!
This is the best that I could do on my own without asking for help.
So here I am posting my question and asking for help.
How do I get the apps that I want to run to not be killed by the background task manager?
OR
How do I get the phone to use the 10GB of ram?
I feel that I am missing something.
With any luck, one of you smarter persons will be able to point it out to me.
As an aside from all of these changes the phone feels very smooth and fluid.
Except for apps closing that I don’t want to, this phone is a great experience and a pleasure to use.
Apps that I want to run are staying open much longer then before I started.
It’s now just an overnight issue.
And getting the phone to use over 6Gb of ram.
I would suggest that I am 90% happy with it now.
KERNAL: ElementalX-OP6-3.10
ROM: STOCK OOS 9.0.11
PHONE MODEL: 6013 O+6T McLaren
Tomorrow I may try making this change to the build.prop file;
ro.vendor.qti.sys.fw.bservice_enable=true to false
Don't know if it will help or not.
Wow dude, interesting read, i will sign up for notifications from this thread hoping you get your answer because i have the exact same problem but with my work app, throwing it all out of whack and making me a target to big fines (in the $1,000's) and potentially reducing my marketability!
The attached screenies are from before i realized that the app getting killed in the background is what causes the problem (I've left it in the foreground HOURS a few times and it works perfectly!)
UPDATE:
Good news!
I seem to have solved my issue.
Time will tell for sure though.
But this morning and all day today, Spotify and the widget app have been running without closing.
AND I have seen memory usage up to 6.8GB used.
Here are the further steps that I took;
- ro.vendor.qti.sys.fw.bservice_enable=true (changed it to false)
I didn't really notice much of a change.
But then I noticed that perhaps the limit of 60 tasks was not high enough.
I seem to have that many apps open and limiting to just 60 may be an issue.
- ro.vendor.qti.sys.fw.bservice_limit=60 (changed it to 120)
THIS!
This seemed to have worked for me.
All apps seem to be open and be staying open.
Today I got a message/warning from android telling me that the widget app is consuming the battery in excess but I ignored the warning and android did not close the app or stop the widget from running.
I will keep an eye on the phone for the next few days to confirm that this actually solved my issues.
My next step will be to see what effect if any this has had on my battery usage.
I am curious to see if it's all that bad...
geeksquad2 said:
UPDATE:
Good news!
I seem to have solved my issue.
Time will tell for sure though.
But this morning and all day today, Spotify and the widget app have been running without closing.
AND I have seen memory usage up to 6.8GB used.
Here are the further steps that I took;
- ro.vendor.qti.sys.fw.bservice_enable=true (changed it to false)
I didn't really notice much of a change.
But then I noticed that perhaps the limit of 60 tasks was not high enough.
I seem to have that many apps open and limiting to just 60 may be an issue.
- ro.vendor.qti.sys.fw.bservice_limit=60 (changed it to 120)
THIS!
This seemed to have worked for me.
All apps seem to be open and be staying open.
Today I got a message/warning from android telling me that the widget app is consuming the battery in excess but I ignored the warning and android did not close the app or stop the widget from running.
I will keep an eye on the phone for the next few days to confirm that this actually solved my issues.
My next step will be to see what effect if any this has had on my battery usage.
I am curious to see if it's all that bad...
Click to expand...
Click to collapse
Nice find, I checked my build.prop and found this. No wonder my apps are killed
Code:
#ifdef VENDOR_EDIT
#[email protected] modify for app memory
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
#endif/*VENDOR_EDIT*/
EDIT: I see a lot of custom ROM's have "ro.vendor.qti.sys.fw.bg_apps_limit=60" to the build prop, I wonder if that going to make a difference
UPDATE:
I am a silly goose.
I broke a cardinal rule while troubleshooting.
I may have had a few too many wobbly pops and made two changes at a time, thus when change was affected, I was unable to determine properly which change caused the affect.
The rule is, "only make one change at a time when testing".
Yes, all of my apps stay open all the time.
I am getting the behaviour that I was looking for.
However it wasn't necessarily changing the build.prop bgservice_limit from 60 to 120 that did it.
Let me back up a bit.
Earlier I had suggested that locking an app to the recent screen didn't do anything for me, and that in my reading it only locks the app from being killed by you when you try to close it manually.
However in reading up on the oneplus framework-res.apk I found a reference to an oneplus whitelist of apps that will never be killed, and a reference to the recent screen app lock that suggests that oneplus will add a locked app to the whitelist and not kill it.
In the course of a single day, I had inadvertently edited the build.prop and locked the widget app to the recent screen thus breaking the one change at a time rule.
So the next morning and the following days when all apps were staying open I attributed it to changing the build.prop not realizing that it could also have been the app lock.
Last night I realized my mistake.
I unlocked the widget app from the recent screen and went to bed.
When I woke up this morning the widget app was not running for the first time in days.
Also the notifications that I was receiving about the widget app consuming excessive battery have stopped.
It would appear that I was wrong in my earlier observations regarding the app lock mechanism.
It appears to be very useful for keeping apps running all the time.
Did changing the build.prop have any affect on keeping apps open?
Maybe?
I have noticed that my battery life has gone for a complete ****.
I can barely get 24 hours out of the phone.
Worse is that it doesn't matter if the screen is on or not, battery usage remains the same.
i.e. with the screen off and the phone put down, battery life appears to be used at the same rate as when the phone is in use.
I had expected the battery life to be not as good, but I didn't expect it to go to for a **** that badly.
There must be a balance between aggressive app management and acceptable battery life.
The phone didn't display this behaviour until I changed ro.vendor.qti.sys.fw.bservice_enable=true to false.
I think that today I will change ro.vendor.qti.sys.fw.bservice_enable= back to true and observe the battery tomorrow.
kantjer said:
Nice find, I checked my build.prop and found this. No wonder my apps are killed
Code:
#ifdef VENDOR_EDIT
#[email protected] modify for app memory
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
#endif/*VENDOR_EDIT*/
EDIT: I see a lot of custom ROM's have "ro.vendor.qti.sys.fw.bg_apps_limit=60" to the build prop, I wonder if that going to make a difference
Click to expand...
Click to collapse
I think that ro.vendor.qti.sys.fw.bservice_limit= and ro.vendor.qti.sys.fw.bg_apps_limit= are essentially the same thing, except for android versions.
ro.vendor.qti.sys.fw.bg_apps_limit= is for Android 7: Nougat and below.
ro.vendor.qti.sys.fw.bservice_limit= is for Android 8: Oreo and above.
Someone more knowledgeable than me should chime in here though.
Do you think any of this could have to do with the way the phone keeps disabling push in Gmail? (Every other day I need to set my O365 exchange in Gmail back to push because it automatically changes to the default of checking every 30 mins.)
Any conclusion?
Did you guys manage to solve this issue please by editing the build prop?
Latest smurf kernel rc14b seems to have solved the RAM management issue. I haven't had any apps closing in background since using it.
thank you for the thread!
What did you find in the end?
How did you set this ?
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_limit=5
ro.vendor.qti.sys.fw.bservice_age=5000
So what's the verdict on the buildprop edits? Do they make a difference?
I notice that sometimes my on-going weather notification doesn't update, or gets killed off. I also have an app that controls rotation per app, and that also seems to stop doing it's thing after a while.
Just want to share. If you are rooted with Magisk, try appsystemizer module. System apps don't get killed by oneplus as aggressively. Tried it with accubattery and it works.
I am so glad I stumble across this, I just want to say, changing
ro.vendor.qti.sys.fw.bservice_limit=5 to 120
ro.vendor.qti.sys.fw.bservice_age=5000 to 10000
Keep apps in ram for much longer then original! For me the battery life is unaffected, might even be better.
scloss84 said:
I am so glad I stumble across this, I just want to say, changing
ro.vendor.qti.sys.fw.bservice_limit=5 to 120
ro.vendor.qti.sys.fw.bservice_age=5000 to 10000
Keep apps in ram for much longer then original! For me the battery life is unaffected, might even be better.
Click to expand...
Click to collapse
Also want to solve this issue.
On which OOS Version you are? (i am on 10.3.1)
Does this really work in newer OOS Versions?
I have read elsewhere that those settings dont work on newer versions, sadly, cant find the thread/source.
thx
pOpY
popy2006 said:
Also want to solve this issue.
On which OOS Version you are? (i am on 10.3.1)
Does this really work in newer OOS Versions?
I have read elsewhere that those settings dont work on newer versions, sadly, cant find the thread/source.
thx
pOpY
Click to expand...
Click to collapse
I'm actually Oneplus 6, OOS 9.0.9.
I also read that it doesn't work on Android 10 because magisk doesn't mount /system in Android 10, but there is a magisk module workaround that you can use. And hopefully magisk will update in the near future to fix that. Just google "Android 10 can't edit build.prop" and you'll find heaps of info.
This is what I have in my build.prop file and it seems to help. I have Oreo it works great on my phone I don't know about later versions of Oreo.
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_age=5000
ro.vendor.qti.sys.fw.bservice_limit=5
ro.sys.fw.bg_apps_limit=64