Mpdecision on stock kernel - Nexus 4 Q&A, Help & Troubleshooting

Does this use more battery? I notice it keeps the first two cores at 1026 and 1512.
And the other two at 384 and 1512.
What benefits do you get for turning mp decision off?
I've tried a couple kernels but don't get the smoothness I get with stock on 4.2.2.
Sent from my Nexus 4 using xda app-developers app

Benefit is increased battery life. The sacrifice is less smoothness. I haven't used a kernel without mpdecision that is as smooth as one with it. I tried to convince myself that others were, but when I went back, the difference was very noticeable.

Related

[Q] [Opinions] Undervolt Settings.

First off, I would like to apologize in advance in case a thread like this exist and I can't find it.. :/ (Search is down, tried Googling) also, if anyone believes this to be in the wrong forum.
ANYWAYS! This is intended to be a preference/opinions thread centering around your OC/UC and Undervolt settings. Feel free to post your current set-up in Voltage Control (or any app of the like) and what Kernel you are running! I wanted to start this to get an idea of what everyone else is setting their UV and CPU clocks to, and possibly give a few of them a try on my own device. :]
Personally all of my clock speeds are at their defaults except for 1000Mhz @ 1200mV. (-75mV). I am also rocking Genocide v1.0 and getting a decent 30hrs of battery life with pretty moderate use.
Post away!
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
kennyglass123 said:
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
Click to expand...
Click to collapse
I believe that would be my point however.. curious as to what other people are running as far as cpu and voltage is concerned. Their success and failures. What people can get away with and remain stable. I, and others, could then try their setup (taking precautions of course; ie Nandroid backup.) And see what we get. Who knows, maybe I might adapt a set up that runs better on my device than my current one.
Sent from my SPH-D700 using XDA Premium App
Yes, every phone is different, but that is just more of a reason to collect data - perhaps a baseline can be established, which would be helpful in determining if a particular phone is messed up or just at the low end of the scale. Right now it is hard to determine if a particular phone's troubles are caused by low quality or by damaged hardware.
I keep all voltages at stock, and don't use any OC - my phone runs fine as is, and the battery life actually seemed worse with UV (and my screen felt hot with the screen UV).
Sent from my SPH-D700 using XDA App
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
xopher.hunter said:
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
Click to expand...
Click to collapse
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
I can only use Genocide kernel to get 1.3ghz at stock voltage with since all the other choices are uv'd. My last two Epics were able to handle uv'd 1.4ghz by 50mV but I'm not really complaining as I think this is a new phone they gave me and not a refurb. I currently have 100-400 uv'd by 100mV, 600-1000 uv'd by 75mV and 1300 at stock.
My phone can handle 1.4 Ghz but only with the stock voltages. If I try to touch it even by 25mV it locks up.
Who all has enabled the 100Mhz step? I noticed when I did my phone went into Deep Sleep a lot less by a noticeable amount. Staying at 100Mhz a lot.
Always interesting to hear about all this theory behind the reasons for undervolting OC and UC, then to hear about the issues (at times extreme) some have. I would also like to know who uses the 100 step and if it is noticeably better on battery life than the 200? Unfortunately I am missing out on it if I am. Still running Genocide here, but with 1.0 at -50mv 800 @ -50 and 600 @ -25. Very stable and still at 30+ battery life. Having 1.0 down 75 made me nervous. although I hear people dropping it down -100mv successfully.
Sent from my SPH-D700 using XDA Premium App
Good tip about "aggressive UnderVolting"...didn't know that actually drains your battery more. Might explain why 6 hours into my day, my battery is down to 30% already!!! I had it set at 1120Mhz UV to 1175mV (Stock = 1300)...
So now I'm going to try 1200Mhz only UV by 50...see what my battery life is after this!
Custodian said:
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Can you explain how this is so? Is this based on any actual research, experimentation, or online documentation, or is this just your own opinion?
Unless your undervolt causes the CPU to hang (I've seen mine start to warm up when it's hung, until a battery pull), I don't understand how providing less voltage to the cpu will cause it to drain the battery faster.
If you change the voltage settings please don't blame the rom developers when you phone bricks...
Sent from Bonsai 7.1.3.1
I'm running Twilight Zone v 1.1.1 RC1-Hajime Taisho, Vision kernel v 1.2
SetCpu-1.450 max
-1.450 min
Quadrant-2377
Linpack-20.577
Voltage Control-1.450
Uv -100
Quadrant-2346
Linpack-21.495
I ran SetCpu, benchmarks, ran VC, benchmarks..... This Epic runs super fast, with no FC's or any other problems at all. I'm currently using VC with the uv-100. As far as excessive battery use, I have Mugen 3200 mah battery. This battery lasts all day in heavy use with no problem.
Sent from my SPH-D700 using XDA Premium App

Safe Undervolting

Hi, I've lowered all the figures by 100mv, but I notice no difference in my battery life. Is it safe to lower the figures more?
Sent from my Nexus 7 using xda premium
Define what you mean by "safe".
Higher core voltages are used at higher clock rates in order to preserve logic margin in the face of more power supply noise and tighter timing. So, undervolting by definition means you are giving up margin.
Whether your SoC happens to have a worst-case timing path which is "fast" or "slow" relative to other devices cannot be deduced by anyone here on XDA or even at Nvidia. About the best you can hope for is some "feel good reports" about what others do with undervolting and completely undisciplined "testing". But even that provides no information about your individual chip.
good luck
Thanks for your reply. By "safe" I mean without damaging my device. And yes, it would be interesting to hear some undervolting stories. I'd quite like to extend my battery life. Cheers!
Sent from my Nexus 7 using xda premium
I've been using my nexus 7 runing a AOKP pub build by mrRobinson and franco's r47 kernel. i've undervolted the entire board by 100mv it is runing pretty solid without any noticible lag or instability. Yet every chip is diferent and can or cannot this margin you'll have to test for your self. Just leave the option 'set on boot' unticked untill your sure that your device is capable of using those kind of voltages. And don't use very large steps. Just like overclocking in fact! Try it - it runs - get a little bit lower. If it crashes you shoukd be able to reboot the nexus and the settings you've changed reseted
Sent from my Nexus 7 using Tapatalk 2
antmasi said:
I've been using my nexus 7 runing a AOKP pub build by mrRobinson and franco's r47 kernel. i've undervolted the entire board by 100mv it is runing pretty solid without any noticible lag or instability. Yet every chip is diferent and can or cannot this margin you'll have to test for your self. Just leave the option 'set on boot' unticked untill your sure that your device is capable of using those kind of voltages. And don't use very large steps. Just like overclocking in fact! Try it - it runs - get a little bit lower. If it crashes you shoukd be able to reboot the nexus and the settings you've changed reseted
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks! Have you noticed any improvement in battery life?
Sent from my Nexus 7 using xda premium
Been testing for 2 days now! Battery seems a little bit better yet maybe placebo! But i feel it does not get has hot as runing stock voltages! It was the main reason i did the undervolt!
Sent from my Nexus 7 using Tapatalk 2
antmasi said:
Been testing for 2 days now! Battery seems a little bit better yet maybe placebo! But i feel it does not get has hot as runing stock voltages! It was the main reason i did the undervolt!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Placebo
Sent from my Nexus 7 using XDA Premium HD app
For what i've read that's the truth but if the frequencies set for the soc are getting less power shoudn't it draw less power from battery? 100mv its almost 10% of the stock voltages!
Sent from my Nexus 7 using Tapatalk 2
antmasi said:
For what i've read that's the truth but if the frequencies set for the soc are getting less power shoudn't it draw less power from battery? 100mv its almost 10% of the stock voltages!
Click to expand...
Click to collapse
For the SoC, whether it's leakage (V^2/R) or dynamic power dissipation (f*C*V^2), yes, you might expect let's say (0.9^2) = 81% battery use at the same operating frequencies.
OTOH, if 75% of the power drain normally is used by the LCD backlight (for instance in a "reading web pages" use case), then reducing the supply voltage will get you only 1/4 of that 20% savings - about a 5% improvement - because the power is being dissipated elsewhere. (Display, DRAM, 3G radio, WiFi radio, etc)
I agree with what you've pointed! In fact i've just taken out the undervolt because Inhad a reboot under heavy multitasking (torrent download, xbmc opened, chrome also downloading a smal file) i'm not certain that it was caused by the uv but it's possible. The Nexus started to lag and then froze completly! From time to tima i've the need of heavy multitask and it wasn't up to the task!
Sent from my Nexus 7 using Tapatalk 2

Annoying issue with core scaling...

I know many will probably just ignore this bug, but I can't because just knowing it's there is pestering. Anyway the GPU is not functioning properly ever since 4.2.2 . Its frequency isn't dynamic.
I would like if some volunteers with faux clock or another GPU reading app could confirm if they have the same issue on 4.2.2 .
Sent from my Nexus 4 using xda app-developers app
Default governor for GPU is ondemand, it's behaving properly.
meangreenie said:
Default governor for GPU is ondemand, it's behaving properly.
Click to expand...
Click to collapse
On demand doesn't entail a static frequency. Previously it would drop to 128 or 200 but now it sticks to 400... That is definitely not normal behavior for this governor. I only had faux clock open and I doubt that app would be GPU intensive.
And this is a problem for me because the the back is noticeably warmer than before despite me having a max of 1ghz and eco mode.
Sent from my Nexus 4 using xda app-developers app
Ah ok sorry, thought you meant it wasn't scaling through the frequencies on light loads.
Dunno may be it's using some kind of low power state instead, I'm using faux stock enhanced kernel and mine is cool at the back with just normal use, also getting great battery life.
Mine only gets hot with heavy gaming or by just browsing with 3g on.
meangreenie said:
Ah ok sorry, thought you meant it wasn't scaling through the frequencies on light loads.
Dunno may be it's using some kind of low power state instead, I'm using faux stock enhanced kernel and mine is cool at the back with just normal use, also getting great battery life.
Mine only gets hot with heavy gaming or by just browsing with 3g on.
Click to expand...
Click to collapse
My issue is that it sticks to 400 which is high state. The only time it changes is when I set it to 487, it'll switch between 487-->400 constantly. Something is triggering a load but these tests are on fresh installs. It's generating heat which isn't good for batteries, especially non removable.
All these issues with my nexus are seriously making me reconsider my purchase -_-
Sent from my Nexus 4 using xda app-developers app

(Q) More power = more battery?

I used to get about 2 hrs 25 minutes SOT with:
3g, 50% brightness, 1.2ghz, 2 cores, - 175 uv, interactive (hispeed at 702mhz)
Now I've got 2 hrs (30% battery left) with th following:
3g, 50 brightness, 4 cores, 1.5ghz, - 175uv, Wheatley governor.
Why am I getting better battery using more power?
I'm also getting amazing performance.
Thanks!
Sent from my PAC powered Matr1x fueled monster NEXUS 4
It MAY be this:
First test with 2 cores maybe used the full 1.2Ghz for a long time.
Second test with 4 cores maybe just used 1Ghz(just an example).
And the second test there is another govenour set...
Correct me if i'm wrong.
Sent from my Nexus 4 using xda app-developers app
failly said:
It MAY be this:
First test with 2 cores maybe used the full 1.2Ghz for a long time.
Second test with 4 cores maybe just used 1Ghz(just an example).
And the second test there is another govenour set...
Correct me if i'm wrong.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I checked the frequency usage in trickster, on 2 cores 702 was uses the most, 1.2ghz was barely used.
On 4 cores, 1.5 is used quite a lot.
Also, Wheatley is a performance governor, with decent battery, I think interactive is the same . But Wheatley gives better performance.
Sent from my PAC powered AKFAUX fueled monster NEXUS 4
okmijnlp said:
I checked the frequency usage in trickster, on 2 cores 702 was uses the most, 1.2ghz was barely used.
On 4 cores, 1.5 is used quite a lot.
Also, Wheatley is a performance governor, with decent battery, I think interactive is the same . But Wheatley gives better performance.
Sent from my PAC powered AKFAUX fueled monster NEXUS 4
Click to expand...
Click to collapse
Thanks for clearing it up!
Hmm well I wouldn't know any other explanation!
Sent from my Nexus 4 using xda app-developers app
Race to idle.
Same reason why LTE can use less power than 3g/2g in certain situations. Same goes for underclocking. (Yes, underclocking can actually decrease the battery life)
Basically, you draw more power but finish the task more quickly. Therefore you have higher peak power usage, but it will go back down more quickly resulting in lower overall power consumption.
For example: you need 10 seconds for a task while draining 100mA/h on the first setup.
On the second one, it only takes 5 seconds to finish, but uses 150mA/h.
Overall, the first way had lower peak currents but drained more power overall than the second.

Is it possible to disable 2 cores on default kernel or any custom kernel

Currently running 4.4.2. stock with ART enabled. This combo suits me well in terms of fluidity and everything works great. Now I would like to have an option on disabling 2 cores to extend battery life. is there an app to do so on stock kernel and is it even possible to do it on some custom kernel? If there's no option to do it on stock id like recommendation for custom kernel that works on stock rom and would enable me to do this via some app.
And id like that ART can stay enabled.
Buy a dual core phone
Sent from my Nexus 4 using Tapatalk
Ivan609 said:
Currently running 4.4.2. stock with ART enabled. This combo suits me well in terms of fluidity and everything works great. Now I would like to have an option on disabling 2 cores to extend battery life. is there an app to do so on stock kernel and is it even possible to do it on some custom kernel? If there's no option to do it on stock id like recommendation for custom kernel that works on stock rom and would enable me to do this via some app.
And id like that ART can stay enabled.
Click to expand...
Click to collapse
try a custom kernel like ak or hellscore
after that disable 2 cores using trickster mod/kernel specific app
Yes, Darkrai is right. Test a custom Kernel like AK, Matr1x, Hells core, Franco or Faux.
You can easily flash the zip via recovery. After that, you should download a Kernel App like Trickster Mod or Kernel Tweaker from the Play Store to customize the whole kernel, gpu, cpu, govenors, schedulers (2wake) etc. And also the cores of the cpu. But you need not to stop 2 cores, you only have to underclock the cpu, so you have all 4 cores but they, for example stop at 1ghz, which save battery at all
I don't really think it helps your battery life (a lot).
More cores at a lower frequency are more power efficient than less cores that have to work at a higher frequency to get the same job done.
And hotplug is there for a good reason, if cores can sleep they will.
Or does anyone have personal experience where it really helped a lot?
I don't understand why people complain about battery life. They say 1 day is not enough, well it is considering their usage.
You can easily pull of 2-3 days without playing games. The problem is that everyone spends like 2-5 hours looking at their phones every day!
On topic: If you want to have performance and fluidity with 2 cores, you will save 0% battery because cores will work on higher frequencies. Just try not to using your phone 24/7
Ivan609 said:
Currently running 4.4.2. stock with ART enabled. This combo suits me well in terms of fluidity and everything works great. Now I would like to have an option on disabling 2 cores to extend battery life. is there an app to do so on stock kernel and is it even possible to do it on some custom kernel? If there's no option to do it on stock id like recommendation for custom kernel that works on stock rom and would enable me to do this via some app.
And id like that ART can stay enabled.
Click to expand...
Click to collapse
Short answer: No.
Long answer: No. But you can undervolt them (All 4 of them at the same time).
Ivan609 said:
Currently running 4.4.2. stock with ART enabled. This combo suits me well in terms of fluidity and everything works great. Now I would like to have an option on disabling 2 cores to extend battery life. is there an app to do so on stock kernel and is it even possible to do it on some custom kernel? If there's no option to do it on stock id like recommendation for custom kernel that works on stock rom and would enable me to do this via some app.
And id like that ART can stay enabled.
Click to expand...
Click to collapse
Try Franco kernel ... it by default supports dual core mode ... moreover u can play with hotplug values according to need
You can using a custom kernel, lots include the ability to but the best implementation is faux's eco mode which is found in Faux's kernel and Ak kernel.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I have tried semaphore kernel with 2 cores only online.
No big difference with other custom kernels where I was using all 4 normally. And the worse about 2 cores is the lag at many applications.
Unleashed by my Nexus 4
RASTAVIPER said:
I have tried semaphore kernel with 2 cores only online.
No big difference with other custom kernels where I was using all 4 normally. And the worse about 2 cores is the lag at many applications.
Unleashed by my Nexus 4
Click to expand...
Click to collapse
Great, its the kind of discussion i hoped to start. My logic was that n4 might have enough cpu power for surfing and casual usage with 2 cores only. So if i disable another 2 i might extend battery life.
Its great some of you tried and show me that my logic was flawed
Now undervolting. I suppose that i cant fiddle with stock kernel and undervolt cpu? Any recomendations for custom kernel. id like it to be as similar as stock, with undervolting feature enabled.
And are there any real gains in undervolting?
Ivan609 said:
Great, its the kind of discussion i hoped to start. My logic was that n4 might have enough cpu power for surfing and casual usage with 2 cores only. So if i disable another 2 i might extend battery life.
Its great some of you tried and show me that my logic was flawed
Now undervolting. I suppose that i cant fiddle with stock kernel and undervolt cpu? Any recomendations for custom kernel. id like it to be as similar as stock, with undervolting feature enabled.
And are there any real gains in undervolting?
Click to expand...
Click to collapse
Many custom kernels support uv like Franco, hell God etc.
Uving is offering a little cooler cpu, which means more time till thermal throttling to start.
Let's say it helps system in general, but not something to notice in big way.
Unleashed by my Nexus 4
Undervolting brings much more than turning off cores. As a side effect your phone won't heat as quickly under heavy load.
What will save you a lot of power while having the phone awake is screen brightness. So you should look for a clever auto brightness solution or, like me, use a mod that let's you adjust brightness by swiping the status bar. I keep my screen dimmed to the low at all times and only make it brighter temporarily if I am outside and the sunlight blinds.
Sent from my Nexus 4 using xda app-developers app

Categories

Resources