Related
Hi!
I noticed that in my Tab Pro 8.4 right after turning it on, when I'm not doing anything and just staring at the monitor it let only one core on clocked at 300MHz (using dashclock CPU information extension). So far so good.
The problem is that after some time, in the same context (doing nothing staring at the homescreen) it let two or four cores on clocked at 1497, so I have to reboot in order to save battery.
Any ideas why this is happenening? Does that happen to you?
P.S.: Battery saving settings turned on
It's mpdecision bug - needs root to fix
This issue should be affecting all stock ROM users of TAB Pro 8.4.
I noticed it a while ago and recently had some free time. The issue was narrowed down to Samsung's buggy mpdecision binary in /system/bin and you need root access to fix it. There are two ways to do it (you'll need terminal and file manager with root access rights):
1. Open terminal, type "su" and then "stop mpdecision". Open Root Explorer, navigate to /system/bin and rename "mpdecision" file to something like "00mpdecision". Reboot. All cores will be running at 300 mhz when idle and tablet will feel noticeably smoother and faster. I did not see any serious impact on battery while running this way for 2 weeks already.
2. Download attached mpdecision file from CM11 modrianwifi ROM, unrar it and transfer it to your tablet. Open terminal, type "su" and then "stop mpdecision". Open Root Explorer, navigate to /system/bin and rename "mpdecision" file to something like "00mpdecision". Copy new mpdecision file into /system/bin, change ownership to root:root and access rights to rwxr-xr-x.
Reboot. The issue will be resolved for good and unused cores will be shutdown properly. Tablet will feel the same way it was before file replacement.
Hope it helped.
favero_ said:
Hi!
I noticed that in my Tab Pro 8.4 right after turning it on, when I'm not doing anything and just staring at the monitor it let only one core on clocked at 300MHz (using dashclock CPU information extension). So far so good.
The problem is that after some time, in the same context (doing nothing staring at the homescreen) it let two or four cores on clocked at 1497, so I have to reboot in order to save battery.
Any ideas why this is happenening? Does that happen to you?
P.S.: Battery saving settings turned on
Click to expand...
Click to collapse
Hm I'm not seeing this issue on my tablet running the NK1 firmware, though I think I do remember it happening on the AND3 Firmware (saw it under Android Tuner) , I wonder if it was fixed under NK1, I'm curious too - do you know a easy way to reproduce it?
Here is a screenshot of CPU-Z, my tablet has been running for at least 1 day without a reboot, and had some 3D games run on it etc, CPU cores always seem to fallback to offline and 300mhz under my test
On a side note:
I don't run the Samsung Touch Wiz Launcher I am using "TSF Shell" as my Launcher, and have disabled some Samsung apps like "My Magazine" and a few Knox things that run in the background. also I don't use too many widgets since I found out they can hog CPU esp on poorly written apps. ,
mpdecision
I saw this issue on NA1, ND3, NG1 and NK1 firmware. Initially I thought it was fixed in NK1, but it came back in 3 days after last reboot. I'm running heavily de-bloated rooted stock f/w (Knox is at 0x0).
As for reproduction - I was suspecting Flipboard, but the issue came back after its uninstall as well. Seems to be uptime-related. 1 day uptime is not enough for NK1 - please check after 2 more days.
I'm running TouchWiz, but used "MyAndroidTools" to disable several services and startups for few remaining stock widgets and apps. Now I'm totally happy with my Tab Pro - best tablet I've ever had.
otyg said:
Hm I'm not seeing this issue on my tablet running the NK1 firmware, though I think I do remember it happening on the AND3 Firmware (saw it under Android Tuner) , I wonder if it was fixed under NK1, I'm curious too - do you know a easy way to reproduce it?
Here is a screenshot of CPU-Z, my tablet has been running for at least 1 day without a reboot, and had some 3D games run on it etc, CPU cores always seem to fallback to offline and 300mhz under my test
On a side note:
I don't run the Samsung Touch Wiz Launcher I am using "TSF Shell" as my Launcher, and have disabled some Samsung apps like "My Magazine" and a few Knox things that run in the background. also I don't use too many widgets since I found out they can hog CPU esp on poorly written apps. ,
Click to expand...
Click to collapse
NetFluke said:
This issue should be affecting all stock ROM users of TAB Pro 8.4.
Click to expand...
Click to collapse
Thank you! I've replaced my /system/bin/mpdecision file with yours and so far the tablet is working properly.
I'll know in a few days if it sticks. But, I definitely had this problem with the governor with T320XAR1ANK1. FYI, for what ever it's worth, I've noticed this governor is slightly slower to ramp up. I don't really care, as the tablet is still super responsive, but some may also notice that Antutu and CF-Bench scores are slightly lower with this governor.
Yeah I can confirm its still present in K1, I tried to limit it down to a few things that could be causing it but have been unsuccessful sine it occurs at random it seems
but my thinking its either something to do with
1. video decoding (I watched a few videos) .
2. charging the tablet (I noticed on my ampere cable it was drawing 0~70 - 120 mA idle )- but this could be because cpu was already drawing more power then needed, usually it's 0 ~ with an occasional 30 mA when plugged in with screen off.
3. possibly game / 3d
...anyways I switched the mpdecision file and it seems to work fine now, except for a slower rampup speed like the others said - not really a big deal i'm sure this will help battery life too.
favero_ said:
Hi!
I noticed that in my Tab Pro 8.4 right after turning it on, when I'm not doing anything and just staring at the monitor it let only one core on clocked at 300MHz (using dashclock CPU information extension). So far so good.
The problem is that after some time, in the same context (doing nothing staring at the homescreen) it let two or four cores on clocked at 1497, so I have to reboot in order to save battery.
Any ideas why this is happenening? Does that happen to you?
P.S.: Battery saving settings turned on
Click to expand...
Click to collapse
WOW! Finally someone on this forum other than me noticed this issue
I think I posted about this issue in September or so, and nobody else here said they noticed anything. Then I stopped checking this forum regularly... I'm glad to see others have now noticed this problem and have even figured out the root cause too!
I just got cm 13 and i wonder IF i change res to 1920x1080 will their be negative stuff and will my phone get better performance IF i change res
From my experience, it will affect performance in positive way, but battery life will be pretty much same. Try it out
dmxpeter said:
From my experience, it will affect performance in positive way, but battery life will be pretty much same. Try it out
Click to expand...
Click to collapse
Will contacts and playstore breake IF so how could i reactivate apps
Battery life will not improve because the pixels are just getting bigger for it to become 1080p this does NOT actually disabled them or anything. IT does the same as your PC.
gusselibus said:
Will contacts and playstore breake IF so how could i reactivate apps
Click to expand...
Click to collapse
No, everything should work fine. The problem could be with stock rom, but on CM you should be good to go.
wold i get super big Icons
just try it, open terminal and type
su wm size 1920x1080 //this will change your resolution, you can experiment with different resolutions
su wm density 560 //density - if you go too high, everything will be bigger; if you go lower, everything will be smaller; I would recommend 500
reboot your device
if something goes wrong, you can always reset your resolution and density
su wm size reset //it will reset your screen size to default value - 2k (1440x2560)
su wm density reset //this will reset density to default value - (560 on CM13 I think)
Don't be afraid, try everything out, experiment.
Ok - you may be familiar with my mod here -
http://forum.xda-developers.com/hon...ipt-disable-enable-swap-honor-5x-kiw-t3308321
If not - try it - but in any case, from that thread, get SH Script Runner, Stericson's Busybox Installer
What this mod is about -
Makes your phone act like it's 720p instead of 1080p
It's still 1080p
But it moves the work from the GPU to the screen's hardware scaler
There's no such thing as a free lunch so this won't give you more battery duration
This may screw up your favorite keyboard, like SwiftKey - use the Google keyboard
This may screw up your icon sizes in your launcher (so look for launcher options to change that if you care)
This is going to make your fonts smaller in many places
This mod is not guaranteed to work the way you want
You MUST make a nandroid backup before proceeding if you know what's good for you
Run this the same way as you would my swap scripts
What this mod contains -
dpi-switch.zip that you unzip at the top of your /sdcard
If you followed the swap script instructions, you already knew that
720p.sh does exactly what the name implies - it's the mod
1080p.sh does what the name implies - it restores your phone to the default state
You must be root to run - see the instructions - turn on the SU button in SH Script Runner
Your phone will reboot when done
I may or may not change that
What could possibly go wrong -
If you use this with other DPI or screen mods, the sky could fall, your friends will leave and your dog will disown you - plus your phone will be borked
You didn't ignore me, you made a nandroid backup so nothing really bad can happen if you did
The screen may start out as tiny - play with it some, it will sort itself out - maybe even hold power to kill it and start it again
I can reproduce that but not every time
You can get the right sized screen and be fine, just play with it if it hits you
Try turning to landscape and back, that seems to clear it up too
That only happens right after the mod is applied
Important things to know about this mod -
No puppies were harmed during its creation
I am not responsible if your phone dies, catches fire, blows up, tries to take over the world, or starts running like a bat out of hell and makes you very happy
OK, I'm a little bit responsible for that last bit but only a little
Monjori OpenGL Shader benchmark test - 49 fps stock, 62 fps modded
PERFECTLY SAFE TO GO BACK AND FORTH FROM 720 TO 1080 AT ANY TIME
Enjoy - if it's pretty necessary, I'll come back with pictures - but seriously - see the swap thread linked about - this just copies the same approach, and just gives you some new commands.
Cheers!
PS - Yes - you can too do this yourself or use some other apps. No - nothing is as easy as doing it this way if you're not an expert in these things - that's why I made this for you.
Download is right here -
View attachment dpi-switch.zip
Here are the codes:
720p -
Code:
#!/system/bin/sh
# Sets 720p windows defaults on 1080p 5.5" Huawei, such as honor 5x
# Must run as root
# WILL reboot when finished!
# March 19, 2016
# EarlyMon
wm size 720x1280
wm density 320
setprop sys.powerctl reboot
1080p -
Code:
#!/system/bin/sh
# Restores 1080p windows defaults on Huawei, such as honor 5x
# Must run as root
# WILL reboot when finished!
# March 19, 2016
# EarlyMon
wm size reset
wm density reset
setprop sys.powerctl reboot
Is it the same as running
adb shell wm size 720x1280
adb shell wm density 320
adb reboot
Through adb or are there changes in value ?
Edit: I looked into the files and saw a change in density, 267 instead of 320...would it work with 320 ?
Zakaria.R said:
Is it the same as running
adb shell wm size 720x1280
adb shell wm density 320
adb reboot
Through adb or are there changes in value ?
Edit: I looked into the files and saw a change in density, 267 instead of 320...would it work with 320 ?
Click to expand...
Click to collapse
Yep, basically the same thing. There are namespace and zygote differences from Huawei so things in a terminal emulator aren't always the same as when run through adb, so we need root here.
267 comes from Pythagoras -
sqrt( 720^2 + 1280^2 ) / 5.5 = 267
320 is the class value understood by services and both work equally well.
I've updated the script to the use the 320 class value for density and went ahead and changed shutdown to reboot - I've seen occasional weirdness with just a reboot, but the first post instructions say if it's weird, try a shutdown anyway.
I'm not sure the changes make a difference but you're right - most folks familiar with this will expect the class value there, so I've changed the script.
And as I mentioned at the end of the post - no magic, nothing you can't do yourself if you know how, just a lot easier this way for non-experts.
Cheers!
PS - added the script codes to the second post, no secrets to this.
EarlyMon said:
Yep, basically the same thing. There are namespace and zygote differences from Huawei so things in a terminal emulator aren't always the same as when run through adb, so we need root here.
267 comes from Pythagoras -
sqrt( 720^2 + 1280^2 ) / 5.5 = 267
320 is the class value understood by services and both work equally well.
I've updated the script to the use the 320 class value for density and went ahead and changed shutdown to reboot - I've seen occasional weirdness with just a reboot, but the first post instructions say if it's weird, try a shutdown anyway.
I'm not sure the changes make a difference but you're right - most folks familiar with this will expect the class value there, so I've changed the script.
And as I mentioned at the end of the post - no magic, nothing you can't do yourself if you know how, just a lot easier this way for non-experts.
Cheers!
PS - added the script codes to the second post, no secrets to this.
Click to expand...
Click to collapse
Appreciate the explanation good job my friend keep up
Performance Impact for 2D games
I notice my phone is bit laggy when I play 2D game with 720p mode. I doubt scaler is overloaded.
So I compare both score with GFX benchmark.
Here are texturing results. 720p score was about 1270, native was about 1400.
720p mode impact some 2D performance by use hardware scaler always.
Same benchmark shows improvement in other areas - there's no simple answer and this is a mod to use when it benefits games that get along with it. As you've found, not all do.
EarlyMon said:
Same benchmark shows improvement in other areas - there's no simple answer and this is a mod to use when it benefits games that get along with it. As you've found, not all do.
Click to expand...
Click to collapse
Strong agree.
I decided my phone to leave default. 'cause for me, more suitable than 720p. But someone is not.
Not simple.
Here are all results for comparison. for someone.
On my KIW-L21 the Screen did not scale, unfortunately.
Meaning the Screen with a resolution of 720p was stuck in the upper left corner of the screen(Like a window, the rest of the screen was black),
while the touch input was rooted from the whole screen, which made it a little bit challenging to operate the device
Any idea how one could tackle that problem?
Nekly said:
On my KIW-L21 the Screen did not scale, unfortunately.
Meaning the Screen with a resolution of 720p was stuck in the upper left corner of the screen(Like a window, the rest of the screen was black),
while the touch input was rooted from the whole screen, which made it a little bit challenging to operate the device
Any idea how one could tackle that problem?
Click to expand...
Click to collapse
1. Enable auto-rotate. Then rotate your phone at lock screen.(See #1)
2. Try edit script "wm density 267" instead of 320. Use SH script runner on root mode. (See #3~)
3. Try adb command via PC (see #3) if you feel too difficult to operate with touch screen.
I counter same problem. I resolve this with 3. 'cause I can't unlock my phone
ssrnsrsr said:
1. Enable auto-rotate. Then rotate your phone at lock screen.(See #1)
2. Try edit script "wm density 267" instead of 320. Use SH script runner on root mode. (See #3~)
3. Try adb command via PC (see #3) if you feel too difficult to operate with touch screen.
I counter same problem. I resolve this with 3. 'cause I can't unlock my phone
Click to expand...
Click to collapse
1. Autorotate is on. Does not do anything.
2. Edited the script to uses 267 density. Did not work either.
3. ADB kinda works with density 320. I could test, wether to use this mod or not. But in my Use Case I got no benefit whatsoever. Also not beeing able to change this on the go is another deal breaker to me.
Thanks for the support.
I have the same results as Nekly. After digging deeper, the problem lies within the EMUI 3.1 launcher. After you change the resolution/density, the icons look all jacked. I opened some games, and the games look just fine. There is definitely a noticeable FPS boost.
There's no such thing as a free lunch so this won't give you more battery duration
Click to expand...
Click to collapse
After careful thought, I tend to disagree with this statement. While the screen is off, hes right, there is no free lunch there. While I have not tested it, in theory it *should* result in more battery duration while you are using the phone. My theory is that if you were to change the resolution to 720x1280 thats 921600 total pixels rendered on the screen. Instead of the normal 1080x1920 which is 2073600 total pixels rendered. Thats a net difference of 1161000 less pixels that the GPU has to render. So less work for the GPU. The MHZ will still be the same so no change there. If there was no FPS boost in the game, then the GPU would still be doing the same amount of work. But there is an FPS boost.
This is an awesome tweak, I wish I could get the launcher to display the icons correctly. Again great work @EarlyMon!
TouchOdeath said:
I have the same results as Nekly. After digging deeper, the problem lies within the EMUI 3.1 launcher. After you change the resolution/density, the icons look all jacked. I opened some games, and the games look just fine. There is definitely a noticeable FPS boost.
After careful thought, I tend to disagree with this statement. While the screen is off, hes right, there is no free lunch there. While I have not tested it, in theory it *should* result in more battery duration while you are using the phone. My theory is that if you were to change the resolution to 720x1280 thats 921600 total pixels rendered on the screen. Instead of the normal 1080x1920 which is 2073600 total pixels rendered. Thats a net difference of 1161000 less pixels that the GPU has to render. So less work for the GPU. The MHZ will still be the same so no change there. If there was no FPS boost in the game, then the GPU would still be doing the same amount of work. But there is an FPS boost.
This is an awesome tweak, I wish I could get the launcher to display the icons correctly. Again great work @EarlyMon!
Click to expand...
Click to collapse
0.5 × 2 = 1
If you render half as many pixels per frame but increase the number of frames per second by what could be a factor of two, then the system theoretically ends up rendering the same number of pixels per second.
(pixels/frame × frames/second = pixels/second)
GPUs and displays work on fields - even the LCD control matrix doesn't have to refresh in terms of pixels - so the math is actually quite a bit more complex for making predictions.
If you get better battery performance, great!
But I won't promise that because TANSTAAFL.
Nice!! Very deep insight, love the formula!!
Loving these small but useful script contributions, Mon. Thanks for the hard work. Will definately try this when I get home. Question - is the effect on the icons on the native launcher only? I removed that from /system and installed Nova as my only and default launcher, so just wondering if it's Huawei's fault or just a secondary effect from the resolution change.
I have the same results as Nekly. After digging deeper, the problem lies within the EMUI 3.1 launcher. After you change the resolution/density, the icons look all jacked.
Click to expand...
Click to collapse
What I said in the above quote is wrong. Nekly does a great job in describing the problem:
On my KIW-L21 the Screen did not scale, unfortunately.
Meaning the Screen with a resolution of 720p was stuck in the upper left corner of the screen(Like a window, the rest of the screen was black),
while the touch input was rooted from the whole screen, which made it a little bit challenging to operate the device
Any idea how one could tackle that problem?
Click to expand...
Click to collapse
I'm experiencing the exact same problem on my L24 as @Nekly and I now have a ghetto solution.
There is an app called Resolution Changer. It has widgets you can place on your desktop. I have two widgets, a 720p and a 1080p. When the device is rebooted, the resolution will screw up, all you have to do is click on the 1080p, and it will restore fullscreen. Then click on 720p widget, and your screen will be fullscreen 720p. I'll post a better solution when I find one.
+1 to @EarlyMon for coming up with this geniusry. This tweak is clutch.
Can anybody get me a flashable zip that resets the resolution back to 1080p? I used the Resolution Changer app and somehow I screwed up my display. Any help would be appreciated!
EDIT: found this -->https://forum.xda-developers.com/android/general/guide-fixing-resolution-using-nomone-t2921856, this guy saved my day, but it would be more convenient when having a flashable zip file instead of having to connect to a computer and reset res via adb. Cheers!:good:
I want to lower the device resolution to 1920x1080 to give the phone a bit more snappiness, maybe even more battery life.
I found a thread that has done it ----> This thread
However using the commands
wm size 1080x1920
wm density 441
does not work running android M
I am running the AOSP - CAF rom
Has anyone done succeeded at doing this on android M?
I've had no issue using the wm command on any versions of XenonHD on my d855. I have always used Nomone resolution changer to check the current resolution. But the terminal commands work for me whether the apps installed or not.
If I remember rightly some ROMs have issues with changing density "wm density" to a lower value, but that can be rectefied by changing (or adding) "ro.sf.lcd_density=" in the build prop. I have my wm density set to 320 and my buildprop to "560"
I think you may need to report this issue in your ROMs forum thread to get more accurate advice though. Like I said, I've never had any problems on XenonHD with ACC1.6 kernel.
Link420able said:
I want to lower the device resolution to 1920x1080 to give the phone a bit more snappiness, maybe even more battery life.
I found a thread that has done it ----> This thread
However using the commands
wm size 1080x1920
wm density 441
does not work running android M
I am running the AOSP - CAF rom
Has anyone done succeeded at doing this on android M?
Click to expand...
Click to collapse
its useless to downgrade your resolution to 1080p.there will be 0% improvement on battery and a minor 10-20% boost in gpu performance.it will make your g3 look ugly so better not do that.if u want better battery life go fo some 3rd party batteries like zerolemon and others
I found a tip for my sm-p600 to degrease battery drain.
You just have to degrease resolution and dpi.
On an adb console on your PC :
tape this:
Code:
wm size 2048x1280
(you will have a fc launcher, no pain)
then tape
Code:
wm density 250
your res is now 2048x1280 and your tab is now battery friendly about 50%
it stay after reboot.
if you want to go back to native screen, you have to set res to 2560x1600 and dpi 320
try ! it work
Don't do this on terminal emulator because on change res, you have continuous fc launcher and you can't change dpi.
:good:
This shows how silly xHD resolution is for phones with less than 6 inches. And how amazing battery life could be on current top phones if they still had FullHD displays.
Sm-p600 is an amazing tab with a very high rsolution but have a poor battery life.
If you degrease the res a little, you still have a good display but your battery will stay longer.
Its my choose, so i share.
Please explain how I do this.?
I downloaded android - skd and Android studio and I have USB debugging enabled but that's all I know. Thanks in advance.
Great idea ...
Dear @murigny64 , it's a good idea to lower the resolutions ... but , didn't you face any problems with system apps ( as they are designed for some especial resolutions ... ) ? also , how was your performance with games and demanding apps ? ... did it effect your benchmark results ? ... Great Thanks in Advance
With Best Wishes
Hitman1376
hitman1376 said:
Dear @murigny64 , it's a good idea to lower the resolutions ... but , didn't you face any problems with system apps ( as they are designed for some especial resolutions ... ) ? also , how was your performance with games and demanding apps ? ... did it effect your benchmark results ? ... Great Thanks in Advance
With Best Wishes
Hitman1376
Click to expand...
Click to collapse
No prob with system apps if you respect resolution vs density.
Only one thing : bootanimation is shifted when you boot device.
I've doing this especially for games like crash royale.
Before the tweak, i can play about 30minutes only. But now, i can play more than 1 hour. It's very amazing.
You can try, it's easy.
Antutu is 53550 with stock 5.1.1 .
+ Good idea to reduce the resolution :good:, more juice for the processor, radio, Gpu, screen on time, etc.
+ I used NOMone resolution changer w\ root (revert back to default in 9s if things go wrong).
+ Layerpaint & cpu-z detects the display as 8".
- Got 51th 48296 on antutu 6.2.7 (lollypop stock serbia rooted, P601 w\ deathly adiutor) Right bellow note 5, Probably because TW lollypop & old processor. Was "13th" 54954 on kitkat (P601 w\ gltools).
- samsung gallery got 1/4 view cut on the right side of the screen (folder view) , i use quickpic.
Didn't see any significant increase in terms of battery life, only slightly.
can anyone else confirm it works?
I'd be interested in an explanation of how reducing the resolution would have any effect on battery usage. The backlight is still on, all the pixels are still used, so what's using less battery?
theophile2 said:
I'd be interested in an explanation of how reducing the resolution would have any effect on battery usage. The backlight is still on, all the pixels are still used, so what's using less battery?
Click to expand...
Click to collapse
Less render pressure for the SoC I assume. Backlight is still the #1 hog though.
---------- Post added at 07:41 PM ---------- Previous post was at 07:36 PM ----------
To OP: Although this could be overkill, I think you could make the new resolution an integer-multiple downsize to the original (e.g. 2x - 1280x800), so that one image pixel could correspond to an integer-amount of physical pixels (e.g. 2^2=4) on the screen. Could ease rendering pressure even more, but naturally at the cost of clarity.
murigny64 said:
I found a tip for my sm-p600 to degrease battery drain.
You just have to degrease resolution and dpi.
On an adb console on your PC :
tape this:
Code:
wm size 2048x1280
(you will have a fc launcher, no pain)
then tape
Code:
wm density 250
your res is now 2048x1280 and your tab is now battery friendly about 50%
it stay after reboot.
if you want to go back to native screen, you have to set res to 2560x1600 and dpi 320
try ! it work
Don't do this on terminal emulator because on change res, you have continuous fc launcher and you can't change dpi.
:good:
Click to expand...
Click to collapse
Hi, adb says this is WM is not recognized as a command. Do you know what am I doing wrong?
>>> nevermind. just an incomplete command
adb shell WM size 2048x1280
Is it possible to do a step by step for non developers? (or a quick video)
What software are you running?
Wow, if working that sounds awesome! Do you think it works also on the P605 (LTE version)?