I've had this tablet since the big sale in the winter, using it mostly for gaming (FIFA 16 mobile with those graphics tho) and reading PDFs. Never got around to rooting and ROMing because of school. I've experienced the usual minor frustrations: heat/throttling (sometimes a big deal while playing FIFA), screen redraw lags, etc.
So what modifications should I do to bring out the best performance, for gaming and for just general usage? :good:
iarejohnsmith said:
I've had this tablet since the big sale in the winter, using it mostly for gaming (FIFA 16 mobile with those graphics tho) and reading PDFs. Never got around to rooting and ROMing because of school. I've experienced the usual minor frustrations: heat/throttling (sometimes a big deal while playing FIFA), screen redraw lags, etc.
So what modifications should I do to bring out the best performance, for gaming and for just general usage? :good:
Click to expand...
Click to collapse
I used the skipsoft program to unlock my bootloader, remove the encryption, install Super SU root, and install TWRP recovery. Then I downloaded and installed the latest Pure Nexus (CMTE) and fire and ice kernel. I haven't tried any other ROMs. I also bought mine during the winter sale. Stock Nexus 9 is unbearable. Rooted and ROMed these things fly! Been on my tablet for almost 2 hours during internet. Haven't had any lag or any noticeable rise in temperature.
Using AICP with NaHCO₃ kernel. AICP is based off of cm but adds a lot of features like slim/omni-recents, adaway, and more customizations. With NaHCO₃ you can disable zram and enable ksm, which makes 2 GB of ram barely noticable(it got a better antutu ram score than the s6). It also has a lot of governors, I/O schedulers, and TCP congestion algorithms. (you can change all of this with kernel auditor)
manibengood said:
I used the skipsoft program to unlock my bootloader, remove the encryption, install Super SU root, and install TWRP recovery. Then I downloaded and installed the latest Pure Nexus (CMTE) and fire and ice kernel. I haven't tried any other ROMs. I also bought mine during the winter sale. Stock Nexus 9 is unbearable. Rooted and ROMed these things fly! Been on my tablet for almost 2 hours during internet. Haven't had any lag or any noticeable rise in temperature.
Click to expand...
Click to collapse
Hmm... I usually prefer to avoid all-in-one programs and do things manually to get familiar with all the steps, although this program does seem like it would save me a lot of time haha. Speaking of encryption, I've read most people don't see much difference after removing, do you agree?
iarejohnsmith said:
Hmm... I usually prefer to avoid all-in-one programs and do things manually to get familiar with all the steps, although this program does seem like it would save me a lot of time haha. Speaking of encryption, I've read most people don't see much difference after removing, do you agree?
Click to expand...
Click to collapse
Didn't notice too much of a difference. Mainly because I did everything at once. Went from stock to completely ROMed. I do have to say that the difference between the two is like night and day. The skipsoft program also allows you to manually install steps. I used to do things completely manually, but can't anymore. Newborn in the house make it hard to concentrate on steps.
I'm on latest stock and fire-ice kernel! ?
latest DU Official and Fire-Ice
whowatchlist said:
Using AICP with NaHCO₃ kernel. AICP is based off of cm but adds a lot of features like slim/omni-recents, adaway, and more customizations. With NaHCO₃ you can disable zram and enable ksm, which makes 2 GB of ram barely noticable(it got a better antutu ram score than the s6). It also has a lot of governors, I/O schedulers, and TCP congestion algorithms. (you can change all of this with kernel auditor)
Click to expand...
Click to collapse
I use AICP on my phone and its great, but ran like sludge on my OG nexus 7 (relatively speaking for that thing, CM and stock were faster). How does it run on the 9?
fyarf said:
I use AICP on my phone and its great, but ran like sludge on my OG nexus 7 (relatively speaking for that thing, CM and stock were faster). How does it run on the 9?
Click to expand...
Click to collapse
So I actually ended up using AICP (tried Dirty Unicorns first but couldn't get it to boot because of an encryption issue that has since been fixed in the ROM) and it runs fine. As you guys have mentioned, significantly smoother than stock. It's the difference between unusable and usable for leisurely browsing. Haven't really bothered with the customization options yet, and the weather clock that I wanted to use doesn't work, but all in all not sludgy at all. :good:
Related
Hey, I have my Galaxy note 2 on stock rom, 4.1.2. Odexed
I was wondering which is the best kernel that supports swaping external memory on internal
I really need your help, i dont know which kernel I should choose, I was going to try redpill kernel but people are saying that it has battery draining problems
Please help me, I baby my note 2 and I would rather die than seeing my note 2 having issues, and thats why I dont flash custom roms
Or, if there is a way to swap external mem on internal with some kind of app or OTHER WAY THAN A KERNEL
Thanks
You can use search button for that script. And you have to use kernel with init.d support.
perseus has best battery life with good performance, high costumisation by stweaks. agni best performance set by trickster mod problem is i can't set over the gpu... neak is good but i think it,s not so smooth. that was a shot review of some kernel. my choice at the time is agni
Sent from my GT-N7100 using xda premium
Perseus really does have the best battery drain.
But it lags in games.
Redpill has the best audio engine. Scoobydoo
Some members like. Neak more. Wolfson
Adam is currently going into the right way... You could. Try adam... Seems to. Ne. Very good.
Every custom kernel supports init.d.
Just flash the mod exsd2internalsd..... And you're good to go
Sent from my GT-N7100 using xda premium
Stock is the best kernel, if you care about performance. Period.
But you'll realize that after using a fluid ROM like ARHD, with stock ROM performance of all kernels felt same to me. Still if I had to choose one I'd go for N.E.A.K, as it is pretty straightforward with nifty features, just if it had the exFAT support!
Sent from my GT-N7100 using Tapatalk 2
jujuburi said:
Stock is the best kernel, if you care about performance. Period.
But you'll realize that after using a fluid ROM like ARHD, with stock ROM performance of all kernels felt same to me. Still if I had to choose one I'd go for N.E.A.K, as it is pretty straightforward with nifty features, just if it had the exFAT support!
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I don't know on what basis you're making this claim, but anyways it's been the exact opposite for me - Redpill, Perseus, Devil all have great fluidity (had to mess about with the settings of Perseus a bit to eliminate the initial lag - but with no other) - and I haven't tried OC/UV much. Not to mention the headphone/speaker amp and saturation prevention options, screen calibration etc. which you miss out on stock.
tuxonhtc said:
I don't know on what basis you're making this claim, but anyways it's been the exact opposite for me - Redpill, Perseus, Devil all have great fluidity (had to mess about with the settings of Perseus a bit to eliminate the initial lag - but with no other) - and I haven't tried OC/UV much. Not to mention the headphone/speaker amp and saturation prevention options, screen calibration etc. which you miss out on stock.
Click to expand...
Click to collapse
The basis was my own testing with Perseus, Red Pill and even Adam, for a pretty long time. Not a single one was as fast and fluid as stock, even with the modified settings of stock kernel found here,
http://forum.xda-developers.com/showpost.php?p=41902544&postcount=4602
Oh, and as I said, if you are on stock ROM you won't notice anything, that's why I used Perseus as long as I was on stock ROM, but since I moved to ARHD, there was no other option other than stock.
Yes, I agree there are some advantages of custom kernels, like saturation prevention as you said, but no way I was giving up very noticeable performance degradation for some extra features without which I am not bothered at all. And since I installed Viper there are some amplifications, so that point is unchecked from custom kernels advantage list.
PS: If you have no problem could you send me your settings of whatever kernel you are using? I wanna try once more and see. Please don't bother if that kernel doesn't support exFAT.
jujuburi said:
The basis was my own testing with Perseus, Red Pill and even Adam, for a pretty long time. Not a single one was as fast and fluid as stock, even with the modified settings of stock kernel found here,
http://forum.xda-developers.com/showpost.php?p=41902544&postcount=4602
Oh, and as I said, if you are on stock ROM you won't notice anything, that's why I used Perseus as long as I was on stock ROM, but since I moved to ARHD, there was no other option other than stock.
Yes, I agree there are some advantages of custom kernels, like saturation prevention as you said, but no way I was giving up very noticeable performance degradation for some extra features without which I am not bothered at all. And since I installed Viper there are some amplifications, so that point is unchecked from custom kernels advantage list.
PS: If you have no problem could you send me your settings of whatever kernel you are using? I wanna try once more and see. Please don't bother if that kernel doesn't support exFAT.
Click to expand...
Click to collapse
I never ever stayed stock except for the while I had to send it to service. Otherwise I used redpill (exFAT supported) and I've noticed no difference at all from when I had stock unrooted. What's your issue - are you experiencing lag with custom kernels? Or what?
Fair point regarding Viper (love it and use it always myself), but FLL tuning and DAC resampling options make it sound better at that. IMO.
I stay on Perseus, mainly because of its color calibration and all the Stweaks customization features. Now if I use stock kernel, I feel my screen is completly unrealistic, almost fluorescent lol
As for performances, the Note 2 is just powerful enough not to see any difference between kernels. People using ARHD will always tell you that stock kernel is the best for the following reason: Mike1986 says stock is the best and won't give support if you're using another kernel. Period.
I'm using ARHD, but can't stand the fake colors and the lack of customization provided by stock kernel (no GPU overclock for example, no CPU overclock, nothing you can do if your "whites" are pink or blue, etc)
i900frenchaddict said:
As for performances, the Note 2 is just powerful enough not to see any difference between kernels. People using ARHD will always tell you that stock kernel is the best for the following reason: Mike1986 says stock is the best and won't give support if you're using another kernel. Period.
I'm using ARHD, but can't stand the fake colors and the lack of customization provided by stock kernel (no GPU overclock for example, no CPU overclock, nothing you can do if your "whites" are pink or blue, etc)
Click to expand...
Click to collapse
What the hell does this suppose to mean? Mike says.....blah blah....I don't care what Mike says! And what support are you talking about? I was on Perseus while I was using A.R.H.D, one can flash any kernel on ARHD, what to support there?
It's my view, and I am quite sure of all the ARHD users too, the stock kernel gives much more fluid and lag free performance than any other kernel available. Everybody likes customization, but as I said not with the price of performance compromise.
And you can OC GPU/CPU with Tegrak on Stock kernel. Get your facts straight before typing some gibberish.
Perfect example of why "best ROM/kernel" threads are not allowed.
Thread closed.
Towle
XDA Moderator
There are any disadvantages to go back to ice cream sandwich 4.0 version? Now I have custom 4.4.2 and it is laggy no matter what.
P7500
Sent from my Nexus 5 using xda premium
Lior84 said:
There are any disadvantages to go back to ice cream sandwich 4.0 version? Now I have custom 4.4.2 and it is laggy no matter what.
P7500
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
Perhaps you could try one of the lollipop versions. They (both aosp and Omni) are really stable. If you however need 3G I would suggest the aosp rom.
There's no harm in trying them out. If you still feel that they lag to much you can always go back to stock.
I've been running the aosp rom on my wifi tab for some time now and it performs pretty great actually.
Pretty great you mean responsive? Because I use omni 4.4.2 and it's laggy no matter what I do.
Sent from my Nexus 5 using xda premium
Lior84 said:
Pretty great you mean responsive? Because I use omni 4.4.2 and it's laggy no matter what I do.
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
Yes, responsive. I did overclock it to 1400mhz but it's running stable. Only youtube is sometimes not the best when running 720p videos.
Not responsive :/
Is it smooth when using chrome, scrolling and doing other activities?
Tell me the best settings to get it fast with Lollipop.
P.S: i suggest the cm10.2 ROM with tabletUI if you want smooth scrolling and graphics.
Mast3rC22 said:
Is it smooth when using chrome, scrolling and doing other activities?
Tell me the best settings to get it fast with Lollipop.
P.S: i suggest the cm10.2 ROM with tabletUI if you want smooth scrolling and graphics.
Click to expand...
Click to collapse
I can only speak from my experience with the aosp rom but scrolling in Chrome is smooth, I'm also using Nova Launcher and it is overclocked to 1400 mhz. Please don't expect miracles from this old device that samsung gave up on one ago. It runs 5.1.1 as smooth as it can. Also don't expect any hard core gaming and youtube will sometimes have issues. If all these things are deal-breakers then stay with whatever you have now. I wrote this from my own experience with my own tab. My father has the same one else only that one is bone stock. Touch wiz and everything with only a handful of apps installed. And yes it runs smooth and has less "issues" but it's running 4.0.4... I hope my explanation helps you make an informed decision.
Lior84 said:
There are any disadvantages to go back to ice cream sandwich 4.0 version? Now I have custom 4.4.2 and it is laggy no matter what.
P7500
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
I was considering the same. I was on 4.4 omni, seemed laggy. Flashed stock ICS, which did seem snappy but still bloated. I thought I'd give AOSP 5.1 a go. Haven't over clocked anything and its definitely smoother than 4.4 omni. Very compact ROM, I installed gapps and that only set google play. Currently tested WiFi and GPS and they're working. Chrome is smooth and running flash smoothly. Auto detected resolution on YouTube.com is smooth. Haven't tried YouTube app as yet. I normally use tubemate anyway. This tab will always have trouble playing 1080p vid. Max I go now is 720. Tried and its working fine using mxplayer. 5.1 is still in social testing but the bugs are slowly being fixed. I was on ICS for a long time as it performed well. Having experienced the same with 4.4 and now upgrading to this rom , I'm happy with how smooth and responsive it is. Ticks the boxes.
My main concern is lags. I run omni 4.4 on with nova and the response is disappointing.
Most of the time, my son use it to watch movies, YouTube and some games but nothing really hard. When I take it to do some stuff on it, the lags just giving me crazy. I know that the main problem is lack of RAM but hey, with 4.0.4 it works OK.
Sent from my Nexus 5 using xda premium
Going back does mean stability. The way I look at it though is you can only put so much into a mini, but it will always be a mini, not a Ferrari. Lollipop seems to work OK but its stretching the capability of this tab. For me with minor tweaks its going OK. A goto software always on all my droids is Greenify. It kills all the apps lingering in the background and stops them from opening again unless I open them. Try it out, you need all the ram you can get outta these older tabs. With the paid version it also kills system apps like google play services which is a big ram hog. I guess the only way you'll make your mind up is give ICS a go for a few days then try LP and see what you think.
A lollipop ROM might be smoother, if there would be the "Performance" menu in the settings app (like CM12).
If anyone has got any cyanogenmod ROM, i suggest these settings:
CPU governor:
• Intellidemand/ondemand: The CPU will increase the frequency when needed. It's default in many kernels. I really suggest that, because the device will be very stable (and smooth) and the battery life will be quite good :good: ;
• Performance: The CPU frequency will be set to max setting;
• Powersave: The CPU frequency will be set to minimum setting.
CPU min frequency: 150mhz (max. 200mhz)
CPU max frequency: overclock to 1400Mhz (do not overclock to 1.5 or 1.6ghz, the cpu will freeze and might be damaged)
I/O scheduler: deadline
zRam: 18%
Resources clean: on
KSM: on
PS: Enable "Set on boot" to each menu.
Sorry for the worst english ever.
I like decatf's 5.1 AOSP rom. He put a lot of work into creating a wrapper for hwcomposer which does a better job translating some of the newer rendering apis to work with the ancient ics binary Nvidia video driver blobs. That's why videos and animations are much smoother on his rom than the alternatives and why you don't get that weird "lightning bolt" rendering effect that's been around since pershoot's cyanogen jelly bean roms. He also implemented an audio driver wrapper as well in the same vein. And if you use his TWRP version, you can format /cache and /data to use f2fs, which definitely helps with disk I/O. He even ported over Multirom so you can dual-boot, but alas, it doesn't boot Ice Cream Sandwich roms at the moment.
It's the best modern rom thus far for the original Tab 10.1. Other than proper modern and native Nvidia drivers updated for Lollipop, the only thing really holding back the original 10.1 at this point is the Tegra 2's lack of NEON support. But there's nothing decatf can do about that.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Help
Should i root and install pure nexus rom on my nexus 9?
Will i get a performance upgrade in normal day to day use?
Yes, difference is huge, like day and night.
Nexus 9 on stock is unusable slow for me.
Example:
Play Music, Youtube and so on open like 5 times as fast as before
Web Browsing is not stuttering/lagging all the time
General Performance difference is really noticeable
I'm running PureNexus Rom + FireIce Kernel
I tried it, but I did not really notice any difference, but I only tried it for a few hours. I noticed that apps opened quicker with CyanogenMod (that could be attributed that to running minimal Google Apps by using OpenGapps Pico) but that could just be in my mind.
What rom did you try and what kernel?
I'm not a cyanogenmod fan, feel like their rom is always a bit slower than others.
DirtyUnicorn is pretty fast as well.
Personally the only ROM I have been happy with on my nexus 9 has been pure nexus. I've changed out kernels a bit but settled with fire ice kernel. Maxed out CPU and GPU over clock and haven't complained about performance for both games and apps. I ran stock for a few weeks and this is a lot better. (Pure nexus) I don't do benchmarks and what not but the overall feel with fsync off is what I originally expected it to be out of the box. Its a nexus. Give it a try if you hate it go back to stock. That's the joy of the nexus. I also use pure nexus on my nexus 6 and love it the same.
creambyemute said:
What rom did you try and what kernel?
I'm not a cyanogenmod fan, feel like their rom is always a bit slower than others.
DirtyUnicorn is pretty fast as well.
Click to expand...
Click to collapse
I tried Pure Nexus ROM and perhaps one or two others (aside from CM). I tried EX & FireIce kernels.
Regarding the performance or user experience, I have no proof. Just opinion.
Honestly, it is so easy to just try the ROMs & kernels, I wonder why these threads ever pop up. Just try them and see which one you prefer.
http://www.xda-developers.com/andro...every-car-through-updated-app-on-smartphones/
Looks like it may run on LP ROMs. Didn't tried yet.
That looks really interesting. Might be the reason I've been waiting for to upgrade to 5.1
Sent from my SM-G920F using Tapatalk
pa.ko said:
http://www.xda-developers.com/andro...every-car-through-updated-app-on-smartphones/
Looks like it may run on LP ROMs. Didn't tried yet.
Click to expand...
Click to collapse
Not installing on my LP unit running @dsa8310 October ROM. Starts the installation and after a few seconds - App not installed. At first I thought it's location-based but installed OK on my Samsung phone (Marshmallow)
m00n61 said:
Not installing on my LP unit running @dsa8310 October ROM. Starts the installation and after a few seconds - App not installed. At first I thought it's location-based but installed OK on my Samsung phone (Marshmallow)
Click to expand...
Click to collapse
i think you installed the arm64 version. You need the arm version. Mine is working. Make sure you installed the google app and google play music app before installing. Normally android auto is installing this in its installation, but than it goes in a loop (in mine case). So install them first.
For the rest android auto is slow, because it's using google maps, which is slow in the android 5.1 version. Spotify is working fine btw.
I'm working for a MAnufacture which produces HU for cars. Right now there is a native Android System for cars in discussion.
Source:
http://www.computerworld.com/articl...auto-making-your-car-a-big-mobile-device.html
I installed this on my Joying RK3188 running the latest Malaysk 5.1.1 ROM. Unfortunately, the ROM itself is so slow, Android Auto is almost unusuable. It does work, mind you, but the ROM seems to be the problem. Anyone know any bare-bones 5.1.1 ROMs that run quick? Thanks.
dcdttu said:
I installed this on my Joying RK3188 running the latest Malaysk 5.1.1 ROM. Unfortunately, the ROM itself is so slow, Android Auto is almost unusuable. It does work, mind you, but the ROM seems to be the problem. Anyone know any bare-bones 5.1.1 ROMs that run quick? Thanks.
Click to expand...
Click to collapse
try DSA room, its best 5.1 rom I used
dcdttu said:
I installed this on my Joying RK3188 running the latest Malaysk 5.1.1 ROM. Unfortunately, the ROM itself is so slow, Android Auto is almost unusuable. It does work, mind you, but the ROM seems to be the problem. Anyone know any bare-bones 5.1.1 ROMs that run quick? Thanks.
Click to expand...
Click to collapse
It's not exactly the ROM. It's the combination Google Maps + Google Now + Android Auto. I tried it on a clean ROM with only root and pretty much everything removed and it's unusable.
I also noticed that a 5.1 ROM will run OK as long as you only have either Google Maps or Google Now. When you have both it's barely working.
m00n61 said:
It's not exactly the ROM. It's the combination Google Maps + Google Now + Android Auto. I tried it on a clean ROM with only root and pretty much everything removed and it's unusable.
I also noticed that a 5.1 ROM will run OK as long as you only have either Google Maps or Google Now. When you have both it's barely working.
Click to expand...
Click to collapse
Don't know if it is only RAM related. These units have very poor CPU profile - throttling. stepup clock control settings which use highest clock only rarely so most of the time CPU is running slow so many processes suffer especially when multiple apps are running in background.
I'm not using 5.1 ROM (as I see still issues and people complaining) so I cannot test if and what apps mix causes issues.
You may try some kernel tools for testing different governors, CPU throttling (yes I would try also thermal throttling if you want to be on the safe side as rumours are Chinese used above mentioned downclocked setup in order to save CPU from overheating as there is no heat sink).
It would be interesting to open new thread for this. Much improvements may be achieved only by tuning kernel. And that needs some experimenting and practising.
Also, regarding 5.1 it is well known that it is 'heavy' and one of the main points of 6 (MM) was to reduce resource usage. So instead jumping to LP and having resource issues, I'll wait to see if there will be progress on MM which may resolve much of the problems around.
pa.ko said:
Don't know if it is only RAM related. These units have very poor CPU profile - throttling. stepup clock control settings which use highest clock only rarely so most of the time CPU is running slow so many processes suffer especially when multiple apps are running in background.
I'm not using 5.1 ROM (as I see still issues and people complaining) so I cannot test if and what apps mix causes issues.
You may try some kernel tools for testing different governors, CPU throttling (yes I would try also thermal throttling if you want to be on the safe side as rumours are Chinese used above mentioned downclocked setup in order to save CPU from overheating as there is no heat sink).
It would be interesting to open new thread for this. Much improvements may be achieved only by tuning kernel. And that needs some experimenting and practising.
Also, regarding 5.1 it is well known that it is 'heavy' and one of the main points of 6 (MM) was to reduce resource usage. So instead jumping to LP and having resource issues, I'll wait to see if there will be progress on MM which may resolve much of the problems around.
Click to expand...
Click to collapse
I agree. From monitoring resource usage under 5.1 I have to say that while RAM usage will rarely go over 700 MB CPU is aggressively downclocked. However, I need to first add a heatsink and then play with governors.
However, not sure how much would that really help with Android Auto, it's so damn slow it takes like 20 seconds just to start
m00n61 said:
I agree. From monitoring resource usage under 5.1 I have to say that while RAM usage will rarely go over 700 MB CPU is aggressively downclocked. However, I need to first add a heatsink and then play with governors.
However, not sure how much would that really help with Android Auto, it's so damn slow it takes like 20 seconds just to start
Click to expand...
Click to collapse
Heatsink issue is to be investigated also. For instance many phones do not have heatsinks and still endure very heavy usage. So it may be not necessary. For instance, thermal throttling may be sufficient.
Thus, both governor and thermal control should be investigated. I believe it is possible with little effort to tune these units to work very nicely without much hw poking.
SW in these units is just so bad and poor it is almost unbelievable! Beside designers didn't have basic knowledge on architecture, they even 'tuned' many things in just opposite of what is needed. They could have better situation if only leaves everything by default in AOSP
UPDATED FOR MARCH SECURITY PATCH! 08/03/2017
Hey folks!
Today I decided to share my actual setup for everyone to try and report back.
Mind that is still WIP, absolutely far from perfect and it's based on my personal preference, since it's built around the way I use the phone. But it can be easily adopted for many people here since it's pretty flexible.
The main goal of this setup is to provide consistency, both in battery and performance. Also, I mind security a bit, this is why I update the phone often; Because of that I want to flash the least possibile .zip files in recovery after updating to the latest security image (I'm lazy and I like things done nice once, and I never do them twice when it's not needed)
With this setup you should go between 10%/h to 15%/h SOT, consistently. I've seen some of my friends dropping to 9%/h, but no guarantees
Also, added bonus: It DOESN'T trips SafetyNet, so you can use Pay and your beloved Pokemon go!
Also note that english isn't my native language, but I try my best to write as readable that I can. Sorry about that.
This require an unlocked bootloader, but not necessary a rooted phone.
The Setup:
1) First things first: Clean your phone from junk around (I suggest a pretty hard wipe) and since this require to be on the stock system (which IMO works best) flash latest N build.
2) Convert your data and cache to F2FS. It's pretty good, and even if in your opinion it doesn't boost performance THAT much, take in mind that it requires no trimming (which EXT4 does need). Mind not converting /system, this is UNSUPPORTED on stock system. It needs a custom rom.
3) Flash "Flash Kernel" from here. You can literally use any kernel you prefer, but I found this rich enough to use it. Mind it does support F2FS, if you converted to it in step 2.
4) Flash Magisk. This way you have root out-of-the-box and safetynet isn't tripped (for you Pay users!) Also, it plays nice with the mods in the next steps. Don't forget to activate "magisk hide" in the app!
5) Flash this magisk mod (increases media volume steps to 30, in call volume steps to 15)
6) Reboot your phone and set it up.
7) Install Magisk App, WakeBlock, and your kernel manager for the kernel you chose. In this setup, I use EX Kernel Manager.
8) Now, from your favourite root file manager go to /cache and create this directory structure: magisk_mount/system/framework/oat/arm64/ then place in the last folder (arm64) this file. It's from this mod, called WakeBlock. (It basically acts like amplify, but doesn't need xposed NOR root)
9) Reboot the phone.
The setup it's done, you can now tweak it as you prefer or just follow the below steps.
The Kernel tweaking:
1) Open up EX Kernel App and go to CPU, set both governors to Interactive and tick stick on reboot
2) Go to governor options and choose your governor. I use AmanuensisOne v1.0, which gives me around 6-7h sot. Load it, stick it on reboot and back to CPU.
3) Go to CPU Boost options, and disable everything (set everything to 0/disabled) and tick stick on reboot. Then back to CPU.
4) Enable core_control and disable msm_thermal, stick them on reboot.
5) Go to Memory and Disable UKSM stick on reboot.
6) Go to Miscellaneous set I/O Scheduler to FIOPS, stick on reboot, Readahead to 1024 with stick on reboot, disable fsync, also set it to reboot.
Done!
Blocking those nasty wakelocks and save the battery! (aka R.I.P. NlpCollectorWakelock):
It's reccomanded to use the phone for a while before doing this. Wakeblock collects informations on wakelocks only when they fire the first time, so a bit of use it's needed.
1) Open wakeblock app and check if it says "service bound". If it doesn't you may have missed something on the "The setup" part, check point #8.
2) Go to wakelocks and block this wakelocks (the time is expressed in ms in the app - Don't enter spaces, of course.) if you don't have a wakelock, skip it:
- NlpWakeLock -- 600 000ms
- GCoreFlp -- 600 000ms
- RILJ -- 800 000ms
- UrlDispSvcFastWL -- 600 000ms
- CMWakeLock -- 600 000ms
- *net_scheduler* -- 3 600 000ms
- Wakeful StateMachine: GeofencerStateMachine -- 600 000ms
- LocationManagerService -- 600 000ms
- SyncLoopWakeLock -- 600 000ms
- NetworkStats -- 800 000ms
- Icing -- 3 600 000 ms
- ULR_BarometerReading_WakeLock -- 600 000ms
- NfcService:mRoutingWakeLock -- 3 600 000ms
- NlpCollectorWakeLock -- 600 000ms
Take in mind that this wakelocks are blocked without impacting ANY functionality of the phone. You may want to increase the time if don't use geolocation at your own risk
More tweaks (improve smoothness and perceived UI speed):
This is a highly WIP part, setting anything different might break your system or get your phone into bootloop (happend twice to me). I highly suggest to have a backup if you want to fiddle more with these settings. You are advised. If you find something useful, please share.
1) Download HEBF and L Speed. These two apps have many tweaks to improve UX and saves a little bit more juice.
2) Open up L Speed and set it this way:
- Main tweaks: Activate Kernel sleepers optimization, Improve scrolling, Liquid smooth UI
- Battery: Activate Battery improvement
- LNET Optimizer: Activate all the tweaks and set NET Buffers to small (or big, but it wastes more battery)
- Seeder: Set to Enlarger mode
- Settings: apply on boot delay set to 60 sec.
3) Open up HEBF and set it this way:
- Set user type to "Chuck Norris" and proceed.
- Battery: Activate Google play services drain fix (Master) and usage report
4) Go into Settings > Developer options and scale all animations to 0.5x
Done, if you done all of this correctly you should see a dramatic improvement on battery life and performance.
I still reccomend to use Naptime, or better, Greenify to save some extra juice.
Have a good day, and enjoy your phone!
Please comment with your battery stats or suggestions if you wish to improve this topic.
Today's battery performance pic
Well, pretty good for me!
CappyT said:
Today's battery performance pic
Well, pretty good for me!
Click to expand...
Click to collapse
What's your average SOT?
Inviato dal mio Pixel XL utilizzando Tapatalk
giovanto98 said:
What's your average SOT?
Inviato dal mio Pixel XL utilizzando Tapatalk
Click to expand...
Click to collapse
Normally i go for 6-7h pretty consistently, i touched 8h, but it was a day were i kept my screen on pretty much all the time with really quick screen offs.
The average sot may vary, but with my friends we've tested around 6h
As you can see from the screen i've installed accubattery few hours ago, but is already almost accurate in battery reading.
I can provide more accurate averages in a week or two
CappyT said:
Normally i go for 6-7h pretty consistently, i touched 8h, but it was a day were i kept my screen on pretty much all the time with really quick screen offs.
The average sot may vary, but with my friends we've tested around 6h
As you can see from the screen i've installed accubattery few hours ago, but is already almost accurate in battery reading.
I can provide more accurate averages in a week or two
Click to expand...
Click to collapse
Why don't you use a custom rom? Any reason in particular?
DEVILOPS 007 said:
Why don't you use a custom rom? Any reason in particular?
Click to expand...
Click to collapse
Using a custom rom has for sure some advantages, but:
- It may (and possibly will) be unstable or certain features bugged out
- Doesn't provide much more than stock rom already does (and if it does, are just secondary things like looks and customization that you can live without)
- No wakeblock for it, which saves a TON of battery (i might compile it, but hell, takes a lot of time)
- You can switch Android versions easily (and mostly without wiping /data)
- Much more support (even the official one)
- The feel and look of a clean android version
- I often don't like crap integrated with other roms based on stock
- Odexed it's faster and saves a little little juice (i don't do app modding, so...)
That's pretty much why.
Take in mind that this is my thought, and doesn't universally qualify as truth.
CappyT said:
Using a custom rom has for sure some advantages, but:
- It may (and possibly will) be unstable or certain features bugged out
- Doesn't provide much more than stock rom already does (and if it does, are just secondary things like looks and customization that you can live without)
- No wakeblock for it, which saves a TON of battery (i might compile it, but hell, takes a lot of time)
- You can switch Android versions easily (and mostly without wiping /data)
- Much more support (even the official one)
- The feel and look of a clean android version
- I often don't like crap integrated with other roms based on stock
- Odexed it's faster and saves a little little juice (i don't do app modding, so...)
That's pretty much why.
Take in mind that this is my thought, and doesn't universally qualify as truth.
Click to expand...
Click to collapse
Okay thanks, I appreciate your opinion. I mainly prefer custom roms not for customisability and features but roms (mainly Chad's uber) is faster and snappier than any rom out there and is on Clang 4.0 unlike any other roms I think. Also custom roms typically have less bloat and all and has more support for themes and stuff. Can you use substratum and what wakelocks do you block? If you do ever look at getting wakeblock on custom roms could you please look into Chad's uber. I contacted him but he hasn't responded. I'd be happy to help and do it myself but I don't know how to unfortunately.
---------- Post added at 07:03 PM ---------- Previous post was at 06:58 PM ----------
CappyT said:
Using a custom rom has for sure some advantages, but:
- It may (and possibly will) be unstable or certain features bugged out
- Doesn't provide much more than stock rom already does (and if it does, are just secondary things like looks and customization that you can live without)
- No wakeblock for it, which saves a TON of battery (i might compile it, but hell, takes a lot of time)
- You can switch Android versions easily (and mostly without wiping /data)
- Much more support (even the official one)
- The feel and look of a clean android version
- I often don't like crap integrated with other roms based on stock
- Odexed it's faster and saves a little little juice (i don't do app modding, so...)
That's pretty much why.
Take in mind that this is my thought, and doesn't universally qualify as truth.
Click to expand...
Click to collapse
I was also wondering, are there any great custom roms that currently work with wakeblock? So odexed custom roms
CappyT said:
Normally i go for 6-7h pretty consistently, i touched 8h, but it was a day were i kept my screen on pretty much all the time with really quick screen offs.
The average sot may vary, but with my friends we've tested around 6h
As you can see from the screen i've installed accubattery few hours ago, but is already almost accurate in battery reading.
I can provide more accurate averages in a week or two
Click to expand...
Click to collapse
What % of battery health accubattery shows you?
Inviato dal mio Pixel XL utilizzando Tapatalk
DEVILOPS 007 said:
Okay thanks, I appreciate your opinion. I mainly prefer custom roms not for customisability and features but roms (mainly Chad's uber) is faster and snappier than any rom out there and is on Clang 4.0 unlike any other roms I think. Also custom roms typically have less bloat and all and has more support for themes and stuff. Can you use substratum and what wakelocks do you block? If you do ever look at getting wakeblock on custom roms could you please look into Chad's uber. I contacted him but he hasn't responded. I'd be happy to help and do it myself but I don't know how to unfortunately.
Click to expand...
Click to collapse
Yeah, I understand custom rom may be compiled with different toolchains to be faster, but the speed gain is between negligible and placebo, to me. The stock with these settings is buttery smooth and fast. Also, to have a faster look, go to developer settings and set all the animations to 0.5x. I know it doesn't affect performance, but the percieved smoothness is increased.
I tried many custom roms. It's mostly a fight than a good experience for me, so I gave up on it (I used to have cyanogemod on all my phones, for years and I was a big fan of it)
For WakeBlock, I don't plan to compile it for other roms, I'm just currently working on a LineageOS version, but that's it. It's up to your rom dev to integrate it.
BTW Yes, I can use substratum themes, but only in legacy mode. Keep in mind that this will OFC trigger SafetyNet. (like all substratum themes)
giovanto98 said:
What % of battery health accubattery shows you?
Inviato dal mio Pixel XL utilizzando Tapatalk
Click to expand...
Click to collapse
96%, right now.
Solid guide, similar to what i'm already doing but i use Uber as my ROM. Flash kernel is great, although for some reason i universally have a problem on my 6P where my android system usage is as high if not higher than my screen usage? Has anyone else had this issue regardless of their ROM etc? Tried multiples of combos, including stock/dark rom/Stock+ w/ different kernels. Any help would be appreciated!! Good guide none the less!
mrgenie1 said:
Solid guide, similar to what i'm already doing but i use Uber as my ROM. Flash kernel is great, although for some reason i universally have a problem on my 6P where my android system usage is as high if not higher than my screen usage? Has anyone else had this issue regardless of their ROM etc? Tried multiples of combos, including stock/dark rom/Stock+ w/ different kernels. Any help would be appreciated!! Good guide none the less!
Click to expand...
Click to collapse
Lot of users had this problem, check out the tread "nougat battery life" here on xda.
Inviato dal mio Pixel XL utilizzando Tapatalk
mrgenie1 said:
Solid guide, similar to what i'm already doing but i use Uber as my ROM. Flash kernel is great, although for some reason i universally have a problem on my 6P where my android system usage is as high if not higher than my screen usage? Has anyone else had this issue regardless of their ROM etc? Tried multiples of combos, including stock/dark rom/Stock+ w/ different kernels. Any help would be appreciated!! Good guide none the less!
Click to expand...
Click to collapse
I had a similar problem and I found out that it was my WiFi signal too low.
I used "Battery Historian" to see that.
iI's a gui that helps you find what is draining your battery giving you a graph and very detailed stats.
You can also see the wakelocks that wake your device and how much you doze in screen off.
It's located in bathist.ef.lc and it needs a bugreport from your device(to get it you need to run "bugreport > /sdcard/bugreport.txt or you can use the dedicated function into "Developer options")
SimoIanni said:
I had a similar problem and I found out that it was my WiFi signal too low.
I used "Battery Historian" to see that.
iI's a gui that helps you find what is draining your battery giving you a graph and very detailed stats.
You can also see the wakelocks that wake your device and how much you doze in screen off.
It's located in bathist.ef.lc and it needs a bugreport from your device(to get it you need to run "bugreport > /sdcard/bugreport.txt or you can use the dedicated function into "Developer options")
Click to expand...
Click to collapse
okay thanks, ill look into it! my WiFi router is right outside my room, but i still get 3 bars so maybe that's the issue.. the wifi chip's dying or something similar.
mrgenie1 said:
Solid guide, similar to what i'm already doing but i use Uber as my ROM. Flash kernel is great, although for some reason i universally have a problem on my 6P where my android system usage is as high if not higher than my screen usage? Has anyone else had this issue regardless of their ROM etc? Tried multiples of combos, including stock/dark rom/Stock+ w/ different kernels. Any help would be appreciated!! Good guide none the less!
Click to expand...
Click to collapse
It could be even ART JIT, since in 7.x apps aren't optimized at installation time, but at runtime. It may take a week to have everything ok.
Anyway thanks, the only difference I made here is the fact that I'm using wakeblock, a mod that I co-developed in the absence of xposed (and amplify)
Saves a ton of battery, so if you are wakelocking, check it out
Do you use adaptive brightness, set it manually, or what do you do?
HTC_Phone said:
Do you use adaptive brightness, set it manually, or what do you do?
Click to expand...
Click to collapse
Adaptive/automatic, the bar is set just a little before the middle
Some updates on the average battery life
CappyT said:
Some updates on the average battery life
Click to expand...
Click to collapse
Would you recommend using ForceDoze in place of Greenify/L Speed/NapTime?
I know ForceDoze works better with 6.0 since with stock Doze, it only works when the device is at a still position for at least 30 mins and ForceDoze has the ability to alleviate that, letting the device set into Doze mode regardless how much the device moves around, but with 7.0/7.1+, its like an improved Doze v2. So...
explorer-10 said:
Would you recommend using ForceDoze in place of Greenify/L Speed/NapTime?
Click to expand...
Click to collapse
I personally use greenify and l speed for some additional tweaks.
Take in mind that you can use whatever you feel it's right, depending on your needs (greenify for example is selective, while the others aren't)
Anyway all of these will provide only a little bit of reduction of screen off drain, so the difference (for me, at least) it's pretty negligible.
The real deal in screen off performance is limiting the wakelocks, this way you can doze a lot more.