Related
I have dell voice on my phone, most awesome thing since sliced bread btw look it up.
I want this program to stay running no matter what but it times out after an hour or so and shuts down.
Is there an android program out there that can stop other programs from closing?
No, no apps can stop other apps from closing. Some apps, however, can stop the phone from sleeping. If your app closes because your phone goes to sleep, it may help.
what you want is to change the OOM process priority of the app, you can both view it and temporarily change it using AutoKiller Memory Optimizer. However...you might be able to alter things more permanently using v6 supercharger script(bulletproofing) or just the command line. Doesn't take long to learn once you know what to look for, i'd tell you how but i haven't needed it since i had my milestone and i've forgotten.
Also, changing the OOM priority requires root access.
Ok thanks for the tips guys
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
For the sake of completeness (most of you will have noticed this app already): For a change, Samsung have done a fantastic job and released a great app called "Game Tuner". It's simple to use, doesn't even need root, and renders all of the stuff I wrote below obsolete!
What it does is, it renders each game at an individual screen resolution, frame rate, and texture quality (texture quality only working for me since MM upgrade).
All you have to do is install Game Tuner from Google Play (above link), start it, follow the instructions to install GameMode through Galaxy Apps, and you're good to go. Create a custom profile, set default values (e.g. 75% resolution=1080p), activate the profile. Set different resolutions for other games. And if you want to control apps other than games, tap top left menu, and chose "Apps".
I've done the same benchmarks as with the method below, and the results were exactly the same, so it's really working, but without messing up the UI or impairing system apps like the camera.
Hey folks,
I've decided to put together a little wrap-up of the stuff I found regarding the sometimes rather poor 3D performance of the Note 4. This is only for experienced users who are familiar with things as rooting, backups, adb, in general: unbricking their phone if bad things happen. As usual, I don't take any responsibilty if you brick your phone or destroy it in any other way. Just make sure to activate USB debugging, and if anything goes wrong, either follow this guide, or simply reflash your ROM.
Just make sure you make a Nandroid or at least Titanium backup before you try this. Better safe than sorry...
It comes as no surprise that running a cpu at almost 3GHz takes its toll. Demanding games such as Real Racing 3 or XCOM:EW, or emulators such as PPSSPP cause the cpu to heat up rapidly, until it reaches ~80°C, before it gets mercilessly downclocked to cool down. At this point, you start noticing more or less pronounced performance drops. There isn't really much you can do, except using a custom kernel to downclock cpu & gpu, before your phone does.
But apart from that, there is another, even greater performance hog, which is also one of the main reasons for the overheating issue: the QHD resolution of our Note 4's screen. We're talking about a 3.69 megapixel resolution, that's almost twice as much as Full HD (2.07 MP), and exactly four times as much as HD (0.92 MP). Gorgeous and brilliant, beautiful to look at during everyday use, but pushing the Adreno gpu to its limits when it comes to gaming.
So, an ingenious guy called NOMone has created a nifty little tool called "NOMone Resolution Changer", already some time ago. It's available for free at Google Play. It's been widely discussed here on xda and on other forums, but I want to share my experience specifically on the Note 4.
Btw, it seems he only posted here two times, so he's most likely not active anymore, but you should head over and thank him anyway.
Now, if you're thinking "no way, why should I deliberately sacrifice my QHD resolution?", read on nonetheless. Because this tool is extremely easy to use, and if you only switch the resolution before playing a game, and revert afterwards (it's only one click), you won't have to sacrifice any visual quality. The settings stick after a reboot, so make sure to really restore defaults if you want to go back to QHD.
The trick is to use the appropriate resolution and dpi values, so your screen doesn't get mixed up.
The results are impressive, sometimes even staggering. Has anyone ever wondered why PPSSPP doesn't perform better on a Note 4 than it does on a Note 2? Here's the reason. PPSSPP gains so much performance , it's almost unbelievable.
I've also done some benchmark runs to measure the improvements (yeah, I know, benchmarks are bad, but still :angel: ). The improvement is clearly visible and, even more important, reproducable:
GFXBench GL Benchmark 3.1 (Manhattan):
1. 1440p: 449,4 frames, 7.2 fps
2. 1080p: 800,6 frames, 13 fps (+78%)
3. 720p: 1621 frames, 26 fps (+261%)
4. 480p: 2728 frames, 44 fps (+507%)
This is plain awesome. The Note 4 is listed even lower, with 434 frames, in the device list, while the 1080p Galaxy S5 reaches 775 frames.
AnTuTu (gpu score only):
1. 1440p: 16210
2. 1080p: 21253 (+31%)
3. 720p: 22524 (+40%)
4. 480p: 22523 (+40%)
Obviously, by comparing scores 3 and 4, the Note 4 hits the fps limit at HD resolution, so there's no more room for improvement in AnTuTu.
Seascape Benchmark (detail setting: Very High):
1440p: 26.9 fps
1080p: 46.6 fps (+73%)
720p: 53.4 fps (+99%, sometimes hits the frame limit of 59.0 fps)
480p: 59.0 fps (+119%, hits the frame limit constantly).
This is a beautiful OpenGL ES 2.0 test, so no cpu scores interfering with the result. Again the fps limit prevents a higher score, but nonetheless, this is pretty amazing.
Other benefits: if you're using a custom kernel, you can run gpu-intensive games at lower cpu speeds to keep the cpu temperature in check. In my case, XCOM:EW runs smoothly @ 30% (!!) cpu speed. This way, the cpu doesn't heat up to more than 60°C, which means it doesn't get downclocked while playing. If you like, you can also automate the process of setting the cpu speed with the aptly named app "Automate" . Which is fantastic, btw.
Now what about visual quality?
Seriously: it's hard to tell the difference. If you look very closely, you can see the display isn't as sharp in FHD as in QHD. But if you look that closely, you're in constant danger of triggering some random app with the tip of your nose. At normal viewing distance, especially while gaming, it's impossible to tell the difference.
So, are there any drawbacks?
Yes, there are: the UI gets messed up a bit (e.g. bigger status bar, some Samsung apps don't fit on screen anymore), and NOMone Resolution Changer doesn't seem to work with CM12.1. Well, at least for me, and other users reported so as well. I tested it some time ago, while I was on CM12.1, and even thought it was a fake app, which it isn't! Seems that the resolution is somehow hard coded into CM12, and you can only switch dpi. There's probably nothing you can do when you're running CM, except try your luck.
But if you are running a Touchwiz ROM, stock or custom, it should work as intended (Emotion Revolution ROM r10.1 in my case). And you can simply ignore the UI issues, as long as you only switch the resolution for gaming. It's not a real issue then, because the status bar is hidden anyway while the game is running.
If you want to keep your device running at FullHD permanently, it's a bit more complicated: first, you'll need Xposed, so you can use the App Settings module to set Android System and SystemUI to 480 dpi. This'll fix the UI (Not needed. Just reboot)
Some apps like phone, contacts, S-Note scale down to the lower dpi setting, whereas Samsung keyboard and the camera won't (camera works, see post #10 below).
So you'll have to install another keyboard like SwiftKey (if you don't have it already), find a working camera app (3rd party or hacked Note 4 camera), and clear your Google Play data (at least I had to, it wouldn't install any apps after the changes), and you're good to go. There might also be other issues I'm not aware of yet. But apart from the ones I described, everything's working fine so far.
Have fun!
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
mitko76 said:
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
Click to expand...
Click to collapse
You're right, you don't necessarily need this tool. All it does is simplify the process. And you should really be able to use adb commands to fix your phone when you mess it up. But NOMone's tool comes in very handy when you're away from your pc and need to switch resolutions quickly. In my case, it's when I want to use the camera: the UI is messed up at 1080p and I haven't found a way to fix it yet, except switch back to QHD. Or the other way round: if you want to play a demanding game on the train at lower resolution, but go back to QHD again.
I'm using 1080p resolution permanently now, because I get a smoother UI, a cooler phone, better battery life, and much better performance. I hope they don't give us 5" UHD screens next...
Could you please explain what is wrong with the camera on 1080p 480dpi? I am using these settings and have 0 problems with the camera. Just curious.. If possible please attach a screen shot. Cheers
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Xelasarg said:
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Click to expand...
Click to collapse
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
mitko76 said:
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
Click to expand...
Click to collapse
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Xelasarg said:
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Click to expand...
Click to collapse
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Cool
mitko76 said:
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Click to expand...
Click to collapse
Well, I went ahead and downloaded _alexndr's COI3 stock debloated rom base (Deodexed), extracted SamsungCamera3.apk, replaced the one in my /system/app dir, set permissions, rebooted, and everything's working fine now. :good:
No idea what the Emotroid guys did to the camera app.
I've attached the apk to this post in case anyone else is having this issue.
Man, I've been playing XCOM:EW at 720p, and my phone didn't get warmer than 59°C, even after 2+ hours. And the performance boost is just so incredible... Turns out I don't even mind the 720p resolution in 3D games, it didn't bother me at all.
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
domsch1988 said:
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
Click to expand...
Click to collapse
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
THANKS !
dooes this improve battery as well /
gonna try this
Boody hegan said:
THANKS !
dooes this improve battery as well
Click to expand...
Click to collapse
Yes, it does, at least a bit. The screen does still burn a lot of juice because it's so big and bright, but the cpu stays much cooler. Less heat=less power consumption.
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Xelasarg said:
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
Click to expand...
Click to collapse
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Boody hegan said:
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Click to expand...
Click to collapse
It should, unless SimplROM is CM12-based. NOMone Resolution Changer, as well as similar apps and the adb method, aren't limited to specific devices. In theory, they may all work on all Android phones. You'll have to try it out yourself, just make a backup before you do so!
domsch1988 said:
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Click to expand...
Click to collapse
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Xelasarg said:
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Click to expand...
Click to collapse
Nah, TW is no option... I choose CM because of the straight forward no bllsht Apps approach. Plus Nightly builds via OTA... In no possible way am i going back to TW
AnTuTu Benchmark @ 1080p, performance governor, stock cpu frequency (2.65 GHz): :highfive:
(OK, cpu was also very cool when benchmark started, 28°C).
Some of you might remember the last post i made about the floating windows mod... well that didn't work in MM, but now a_sh_ over at the xhalofloatingwindow thread made it work!
As with the last time you need to have xposed and i would advise to have the uninstaller zip ready just in case our z4 tab decides it has had it with the mods xD
1. Install the files under the post (i will post new files from the original thread when a_sh_ uploads a update and i can confirm it works on the z4)
2. Activate module in xposed and reboot
3. It may or may not freeze when starting apps after a reboot.... If it does like it did for me, one or 2 resets and reboots with the button near the sim/sd will make it boot(only took one reset for me)
4. In the XHFW app go to popup window and set popup dim to 0, it in my opinion makes it look more like true windows or linux instead of just looking like a normal popup and also makes the background app visible
5. Enable movable and resizable windows (go ahead and mess with the settings there as you wish)
6. Toggle multiwindow sidebar from your app drawer
7. In multiwindow sidebar app set tap launch mode to open as xhalofloatingwindow(center), i found this to work best for me but by all means try others if you want
8. Add apps to the sidebar
9. Have fun melting your snap810 with 4 games at once
As it always is with these huge hacks that shouldn't really work, probably not all apps will behave nice when forced to resize but i think it is at a usable level
Under the post is a pic of it running a few apps and the 2 apps needed to do this.
Another pic of it running 2 games at once (no lag) a chat a file explorer and 1080p yt (once more no lag) but it damn near melted a hole in the back of the tab xD temps were extreme but one would expect that as this was never designed to run more than one game at once. When only watching yt+ browsing or doing chat browsing and yt or only one game and other lightweight apps the temps remain normal so thats nice
New app version (uninstall old and install this) it is apparently a bit more polished than the last ver.
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