I did extensive experiments with my Nook Color to come up with a pretty swanky setup with very, very good battery life, very good performance and great stability. Many people responded favorably to this discussion, so I figured I'd try the same with the HD+. The HD+, with CM10.x, simply does not have the tweakability that the NC did, but it has some tweakability.
My goals are still the same:
10+ hours of battery watching movies (no wifi)
15+ hours of battery reading books (screen on, no wifi)
smooth, fast, predictable performance
zero crashes, random reboots, etc.
To begin with, start with the CM10.1.3 stable version: http://get.cm/get/jenkins/42537/cm-10.1.3-ovation.zip
Do the normal steps to install CM, DON'T BE TEMPTED TO USE CM10.2.x! It is slower, less stable, and far worse on battery life
Then configure the following:
Settings -> Performance -> Processor: governor - HOTPLUG, min CPU 396MHz, max CPU 1500, set on boot checked
Settings -> Performance -> I/O scheduler: NOOP, set on boot checked
Settings -> Performance -> Memory management: zRam disabled, Allow purging of assets checked
Settings -> Performance -> 16bit transparency checked
Settings -> Performance -> Surface improvement: disable dithering
Now, for watching movies, use "BS Player", which has far better battery performance than MX Player
Using these settings and Moon+ Reader I am able to get >12 hours of active screen on reading time, and using BS Player about 8-10 hours of watching movies.
Performance is smooth and quick, zero random reboots.
Having an occasional crash of Chrome, but I don't think it's the tablet or OS's fault.
Enjoy!
Why noop over deadline?
Sent from my Nook HD+ using xda app-developers app
I agree about 10.2. The change log is mainly telephony improvements and opengl 3 that the 4470 does not support. Trim is problematic for most HD+ as well.
I might try this. ....
But yeah, why noop?
I'd love to try this on the Nook HD. Are the performance settings missing in the stable 10.1 CM release for the 7" Nook HD? Or am I missing enabling a setting? I don't see settings>performance...
Solar257 said:
I'd love to try this on the Nook HD. Are the performance settings missing in the stable 10.1 CM release for the 7" Nook HD? Or am I missing enabling a setting? I don't see settings>performance...
Click to expand...
Click to collapse
You have to go to settings, about tablet and tap the build number several times. That activates developer options and I think performance too.
Sent from my Nook HD+ running CM10.1 on emmc.
I have been using the suggested tweaks, but already had 16Bit on and use 402m heap size. Not seeing a noted difference yet, but turning dithering off actually results in lag in some games: Zen Pinball is an example. Turning dithering back on corrects the issue.
The device still is second tier for overall smoothness compared to the Excite 7.7 and TF300. Those devices though are not dealing with over twice the pixel count to manage and push. CPU of the 4470 is actually better overall than the Tegra 3, but twice the pixels is a huge difference.
interesting that BS player bests MX for battery consumption...I shall try it!...unfortunately its
not playing audio on some .avi files as MX does. But I'll use it when I can to save on battery
This 10.1.3 rom is it the CM RC2?
:fingers-crossed:I would not describe the Nook HD+ as "smooth and predictable", since the combo of display, gpu (not cpu) and low ram are fixed overhead we probably can not compensate completely for with tweaks (the price we pay for the pretty display). Some of the settings you kindly posted seem to create their own issues, if you play games or use a lot of apps.
After a few days of testing myself with 10.1:
Settings -> Performance -> Processor: governor - Interactive, min CPU 396MHz, max CPU 1500, set on boot checked
Settings -> Performance -> I/O scheduler: Deadline, set on boot checked
Settings -> Performance -> Memory management: zRam disabled, Allow purging of assets checked
Settings -> Performance -> 16bit transparency checked
Settings -> Performance -> Surface improvement: Leave dithering on middle setting
1. Hotplug seems more suited for quadcores unless you are mainly doing light browsing, video and light gaming.
2. Noop seems to cause additional I/O lag after opening and closing a few apps over time- especially games.
3. zRam disabled is good and ditto for purging assets!
4. 16bit transparency helps!
5. Turning dithering off can/will create lag and stutter in games- especially 3D.
6. It seems the two biggest performance killers as far as settings are activating zRam and turning dithering off.
Added:
Again, as far as 10.2, I still 100% agree that 10.1 performs better. If people respectfully look at the change logs, 10.2 does nothing for performance since the updates were telephony and opengl 3.0 that the 4470 does not leverage. Trim for most HD+ tablets can be a slow or quick kiss of death. The net result with trim disabled is a rom with no apparent performance advantages. That said, if people are happy with 10.2 on the HD+, cool stuff!
What some might be seeing when going to 10.2 is the starting from scratch and cache cleaning is more the actual improvement than 10.2 itself. If this is the case, the improvement could be short term, but there are a few features that make 10.2 worthwhile for some folks.
Hotplug seems to be better for battery life vs. interactive. I don't do any gaming or 3D graphics stuff, really just web browsing, reading books and watching movies. I favor stability and battery life in these cases. I suppose there are better settings for gaming especially if you don't mind sacrificing battery life.
I leave tomorrow on one of my frequent trips from TX to Europe, and again I will run my HD+ to the limits of battery life watching movies and reading books on the plane. Anyone have comments about whether the Deadline scheduler is better for battery life (or any different) vs. Noop?
Related
Hey there,
I went through a lot of trouble to get my HTC Magic (32B) working really well,
just wanna share this for people who have issues with the phone's performance as well.
I've tried many things, including a swap partition (on a fast SD-Card) as well as compcache.
Turns out, disabling both did the trick. It FINALLY went from unusable to fast and enjoyable!
My current rom:
Cyanogenmod 6.1.0 RC1
Settings->Cyanogenmod-->Performance:
Compcache DISABLED
JIT Enabled (I noticed an increase in CPU Power with the linpack benchmark,
but it still seems underpowered at 3.3 mflops)
Dithering Disabled
Keep Home App in Cache Enabled
Keep MMS-App in Cache Enabled
VM Heap 16m
Also I am using SetCPU to overclock to 576mhz at the moment(feels like the battery is draining faster).
Another thing I did was to reduce number of Homescreens in ADWLauncher down to 3, since thats 'nuff for me.
Hope this helps someone out there, as I was about to shatter my phone into a million pieces :O
On a sidenote: How many mflops do you get with your Magic?
I have the same findings There was a point when swap, overclock, apps2SD, and compcache all would make a major speed-up on your phone, but the CM6.1RC and the nightlies that shortly preceded it have given me the best performance in my magic's history with all of it turned off.
My phone is configured very similar to yours. I went up to vm24 to smooth out how heavier applications run. I left JIT on despite the theoretical drawbacks because I notice no performance hit and it makes a difference on fractal rendering apps (I'm indifferent to benchmarks).
The CM forums seem to be in a bit of turmoil atm because people are slowing down their phones by applying mods that genuinely sped it up in the past.
But for the first time I can be widget-heavy, always go straight back to home, use window animations, never have choppy music (even when using navigation), use alternate keyboards with no performance hit, and even run a good few live wallpapers. All with unprecedented battery life? Not sure what CM did but he/they sure did it right.
One thing - overclocking your CPU will better your benchtest results but I think you'll surprise yourself by leaving it stock, and even (gasp!) underclocking it. CPU clockrate is one of many possible bottlenecks and considering the 1.5 and 1.6 official roms were capped at 384 (or 352 I can't remember), I doubt it is the culprit of possible slowdowns. I run at 384 almost all of the time and have noticed no side effect except for extreme battery life and added stability (615 gives me reboots). The only differences I've seen overclocking make are in fractal rendering apps and benchtests but Pandas vs. Ninjas and Raging Thunder rock at 384.
glad to see I'm not alone with this
I can still see the phone running out of ram when alot is going on, but its ok.
I'll try your suggestion and underclock the phone.
Another small tweak I just found:
under mobile network settings there is an option "only use 2G", which is checked by default. turning this off improved my connection speed (obviously).
but again this comes at the cost of battery-life.
I'm running nightly 8/6/2011. I have three home screens at 5 columns, 8 rows.
Only widgets are Google Voice, Plume, and Playerpro.
My home screens lag when I scroll between them and I don't understand why. I'm thinking it could be my overclock settings. I had mine at on demand, with min at 600, and max at 1200.
Then I tried using nook tweaks and set the 4th step at 1200, 5th at 1300. Didn't really change anything about the home screen though (everything else runs blazingly fast, however. ).
Do I need to change voltages along with the cpu? What do you use that makes it run smooth? Some youtube vids really impress me.
Edit: I've also tried using performance, but it didn't feel like it changed anything. :/
you may want to try... in cm settings, lock home in memory and don't enable surface dithering, this may help.
have you try launcher pro? its vary super smooth and no lag.
here are my settings and stats. im using launcher pro and all is smooth and vary stable, with good battery life.
me: cm7 / n155 / conservative / 16 bit nenamark1 22.9 neocore 29.9 quadrant 2642
300 @ .8125v
600 @ 1.0v
800 @ 1.1625v
1100 @ 1.2375v
1200 @ 1.2875v
Thank you for the reply! I disabled dithering, and applied the same voltage/cpu steps, and it seems a lot better now!
I am used to adw-ex, but I see that launcher pro is a little more popular these days. I will try it out. Thanks again.
Voltage settings shouldn't affect your performace, they should be stable or unstable and cause things to not work.
The conservative governor is certainly not going to help your cause, ondemand is probably your best bet. You do not want to use performance, as it will set your cpu to max out non-stop.
Before I start credit belongs to eL_777 for posting this in the asus prime thread.
I read that enabling the "Force GPU Rendering " in the developer options would increase the speed of apps. I so I gave it a try and it has definitely increased the overall smoothness for me. I also what to add that it may cause some apps to force close but the only issue I noticed so far is launcher pro not displaying properly. I just switched to adw ex so that is no longer an issue. I opera, browser and tapatalk seem to be faster. It also seems to have an impact on the YouTube app. Hopefully this info helps some people out.
I didn't come across this yet in the xoom forum so I thought it I would share. Sorry if it is common knowledge.
Original post:
eL_777 said:
Hey guys I noticed earlier that my Netflix app was ALOT smoother than it used to be before the ICS update but several others disagreed with me so I was confused. Then I remembered that I enabled this setting in the developer options menu in the android settings, "Force GPU Rendering". Make sure you enable that, close Netflix and start it back up and it should be a million times smoother after you do that. Hope this helps.
Click to expand...
Click to collapse
runhopskipjump said:
Before I start credit belongs to eL_777 for posting this in the asus prime thread.
I read that enabling the "Force GPU Rendering " in the developer options would increase the speed of apps. I so I gave it a try and it has definitely increased the overall smoothness for me. I also what to add that it may cause some apps to force close but the only issue I noticed so far is launcher pro not displaying properly. I just switched to adw ex so that is no longer an issue. I opera, browser and tapatalk seem to be faster. It also seems to have an impact on the YouTube app. Hopefully this info helps some people out.
I didn't come across this yet in the xoom forum so I thought it I would share. Sorry if it is common knowledge.
Original post:
Click to expand...
Click to collapse
I had tried it and thought that there was an improvement in smoothness, but it seems that as you say, it can break some applications. But thanks for the reminder.
Enabling this preference in developer options offloads task of rendering window components like buttons, text and complex 2d graphics calculations to GPU. This often results in much faster UI rendering including animations.
On one side you will definitely achieve better frame rate (and hence smooth experience) throughout system, but you may end up using more battery. On certain devices, GPU consumes more power the CPU, hence you may observe 5-15% lower battery life with option enabled.
offloading UI rendering to GPU has obvious benefits so that CPU can work on other important tasks like database IO, data manipulation, layout calculations and responding to other user inputs.
I would recommend having this option enabled on devices with weaker CPUs e.g. You should seldom need to enable this on dual-core 1.4ghz ARM CPU.
Odp: Enabling "Force GPU Rendering " for more speed in some apps
taranfx said:
Enabling this preference in developer options offloads task of rendering window components like buttons, text and complex 2d graphics calculations to GPU. This often results in much faster UI rendering including animations.
On one side you will definitely achieve better frame rate (and hence smooth experience) throughout system, but you may end up using more battery. On certain devices, GPU consumes more power the CPU, hence you may observe 5-15% lower battery life with option enabled.
offloading UI rendering to GPU has obvious benefits so that CPU can work on other important tasks like database IO, data manipulation, layout calculations and responding to other user inputs.
I would recommend having this option enabled on devices with weaker CPUs e.g. You should seldom need to enable this on dual-core 1.4ghz ARM CPU.
Click to expand...
Click to collapse
I finally gave up GPU rendering as it crash the tab many times. Ie google maps hang the tab after 10-15 min time of usage to such extend that it bootlooped over and over till battery is dead. Also browsing web cause same crashes. If you face many random crashes-you know what to do.
Wysyłane z mojego XOOM 2 ME za pomocą Tapatalk 2
So for the newbies (I have been modding Androids for a years now):
What's the set-up you have found to work best? Are there any issues with it?
Here's mine:
Cyanogen 10 (ROM)
KTManta with kttweaker app(kernel)
interactive CPU: 2100/200 GPU:720/100 (Governor)
FIOPs(scheduler)
Notes:I also gave a five volt boost to the CPU steps (but I would do this last thing and only if you need it). Advice from Omnislyfer: I would like to tell you is about the overheat of you device. Our exynos processor it's great, but it has got some problems with temp at higher frequencies. You have overclocked a lot your device, and I think it's an insane thing to do. The main goal of voltage settings are to undervolt the device at stock frequencies, in order to reduce the overheating effects. You have done exactly the opposite: you have OC your device and also you have rises the voltages. So thrust me: from Ktweaker app, load default settings (so max CPU free will be 1700, and 533 for gpu), then subtract at least -50mv to all CPU voltages and -25 gpu voltages. You will not see particular performance loss (our n10 rly doesn't need Overclock) and hoverheat problems will disappear. Thanks Omni, I currently am testing this. Edit: Tested and this is great advice for this kernel. There is still heat issues for cpu intensive apps, but they are slower to manifest. Straight GPU functions (MX player -HW+) do not seem to need the undervolting and may be able to be ramped up. I did not test with any intensive games as it is hard to seperate the processors.
Video player (this is important for Nexus 10's):
MX Player with the custom codec properly installed (it occasionally (1/100 hours) drops the app when streaming video (twitch), but re-opens easily.
Comments to the community: I agree that people should try out everything. However, I recently had to re-root an old phone and run back through a lot of threads to find a stable set-up. This was to even see if I had rooted correctly. On the Nexus 10, the base Cyanogen 10 kernel kind of blows and my device was all sorts of buggy. The purpose of this is to help new modders and share some knowledge about stable set-ups with each other.
I've ran the gambit of custom ROMs through various versions of Android swearing by one over another but in the end I returned to rooted stock, Franco kernel, XPosed framework with Gravity box. Stability is my driving force and that just seems the most stable without loosing features such as the immersion UI.
Must have apps:
SuperSU
Viper4android
LMT
Nova launcher
Neutron
MX Player
For me other apps fall off in importance but those are the ones I'm taking to a deserted Island.
Sent from my Nexus 10 using XDA Premium HD app
And this is my config:
-Purity ROM - - > clean, stable and fast;
-Trinity Kernel - - > extreamly fast, but it leaks some feature (there is No Undervolt);
-ART runtime! - - > you have no idea of the advantages. Everything is faster and great battery life improvements.
About the apps :
-SuperSu;
-Nova launcher;
-Trinity Kernel Toolbox;
-MusicFX
Hi,
First I think you should give a look at this thread: http://forum.xda-developers.com/showthread.php?t=2725128. Many people are sharing their configurations there, it may help you .
For me, I'm using CM11, no additional tweaks for kernel or anything else, just CM11 was good enough for me. I can play Dead Trigger 2 without frame drops, listen to FLAC audio in Poweramp without issues and watch heavy videos on MX Player.
Also boot time is ≈20 seconds, so I found this to be my favorite setup .
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
I would like to open the gaming discussion with all the informatin in one place. At the end I will sumarize it and adjust first post.
Android version
Nougat vs. Oreo - what is your experience. Is S7 gaming peformance really so much better in Oreo comapred to Nougat?
ROM
Which ROM do you find the best for gaming performance?
Game mode
Is game performance really better when game mode is on?
Game launcher/Game tools
Disable or enable for better performance?
Game tunner
Samsung Game tunner app, especially the HW pefrormance settings - It is important to turn it on or is it a point less?
Governor and I/O
Which governor and I/O do you find the best?
Additional tips for gaming performance
Place for your comments, scripts, settings, etc.
Thank you for your opinions.
I'm only playing PUBG mobile which is a poorly optimized game for the exynos imo but i'll give you my experiences anyway.
I feel gaming on Oreo is noticeably smoother than Nougat, i encounter less stuttering, frame drops, etc... since i updated to Oreo.
ROM
Latest Devbase v5.8
Game mode
I dont touch performance settings since i set hw performance in game tuner to +3 already
Game Launcher/Game Tools
The game launcher only groups everygame on your device to a folder and it has nothing to do with performance. So enabling or disabling it base on ur personal preferences
Game Tuner
It actually makes a noticeable difference in performance in graphics intensive games if you set it to +3 or +4, but on casual, less demanding games just set it to -2 or turn it off completely
Gov,io
Just leave them at their stock settings which is interactive and cfq and you will be fine
Additional tips
Personaly i lower my resolution in both game tuner and in display setting to achieve a more consistent frame rate