hi harsh, nice to see you here again. following you in the P990 forum for a long time. so anything from you must be great that i shouldn't miss.
although i have read through your posts, dont really get it..so my noob question:
this kernel should bring me more power or more juice ?
Sent from my Nexus 4 using xda app-developers app
0.873920] acpuclk-8064 acpuclk-8064: ACPU PVS: 1
------ or -------
[ 0.873920] acpuclk-8064 acpuclk-8064: ACPU PVS: FAST
When I put dmesg | grep PVS in terminal emulator I get " operation not permitted"
EDIT: I GOT IT... "FASTER"
Sent from my Nexus 4 using Tapatalk 2
Many of us P990 fellows have upgraded to Nexus 4 even after saying NO MORE LG .
From my PC I had to type a ADB shell and then hit enter first then I put the rest of the command in
Sent from my Nexus 4 using Tapatalk 2
root@android:/ #
dmesg | grep PVS
1 |root@android:/ #
I did that and got to it saying:
Code:root@android:/ #
Which is where I typed the dmesg command in.
What I got was:
Code:dmesg | grep PVS 1 |root@android:/ #
So what I got was just a number rather than the word. I'm using _motley's kernel. The OP says it should be the word if it's not his kernel...
I did that and got to it saying:
Code:root@android:/ #
Which is where I typed the dmesg command in.
What I got was:
Code:dmesg | grep PVS 1 |root@android:/ #
So what I got was just a number rather than the word. I'm using _motley's kernel. The OP says it should be the word if it's not his kernel...
I got FAST before I flashed the kernel and now I'm on 3. Going to test out battery life for a couple days and report back.
Side note... ex P999 user who swore off LG but here I am.
Sent from my Nexus 4
Sorry for my bad English. I do not understand .... Which is better? or drains less battery kernel??? 1 or faster
I have faster
Sent from my Nexus 4 using xda premium
If you have faster it means the device can technically undervolt a little lower than the other devices based on binning. Now depending on which kernel you use most of them had fast and faster share the same table so people were not taking advantage of having a faster PVS. For example:
Slow: 800MHz@775mV
Nominal: 800MHz @750mV
Fast/Faster: 800MHz@725mV
This is an example of having 3 profiles, now if you use this kernel "with" faster binned support or any new kernel that adopts having more than 3 then you will have:
Slow: 800MHz@775mV
Nominal: 800MHz @750mV
Fast:800MHz@725mV
Faster: 800MHz@700mV
*This is just an example*
Now just for clarification purposes and not having people go crazy and getting replacements, just because you got a Nominal or Slow doesn't mean the device can't UV.. because Google did not sit there and try to undervolt each and every device to see their capability. If the binning of these are anything like binning intel CPUs they will have good UVers and bad UVers and on the other side have good OCers and bad OCers, each one will have pros and cons but it wont be drastically like oh I the max I can clock is 1.5GHz and nothing else because these CPUs should be able to clock higher without changing much... granted that the device doesn't heat up and "throttle" or if that is the case.
The advantages of undervolting is you can have better battery life and/or if you undervolt slightly with overclocking you can probably clock higher will a little less heat involved. UV requires a little bit of stability testing so you don't softbrick or bootloop your phone. You can't just use it for 10min and be like oh my UV is sooo stable. You may have to test it for the entire day and use programs that put load on the phone itself. Using facebook or twitter will not put much stress on the 4 cores yet alone 1 or 2. Some of the kernels we are fortunate to have already come with pre-undervolted tables so you're already set (for those who are scared to UV). Any more than that will require some testing since most of the kernel devs here only set those they think majority of people can handle. (A kernel may put 1.5GHz @1050mV, but you think your device can do 1.5GHz@975mV) They will have a safety margins and if you've noticed some other kernels when released with -50 more mV may cause instability for most (not all). For those wanting to do UV + OC it gets trickier because you have to deal with unstability (from lack of power) with OC (additional heat), the phone itself is fast so I don't see the need for it except for benchmark/e-peen purposes and killing your battery faster .
So yeah before you guys go on an undervolting rampage make sure you have a backup kernel in your SD and also don't apply to boot unless you're 158% sure your settings are stable. Some people tend to go for easy mode nowadays and think they can ramp up their undervolting settings to -175~200mV and show it off. Remember it is hard to brick these phone unless you're just that _______ to begin with. :silly: :good:
Well, our cpu are made at some quality standards. We have 4 different quality of cpu for apq8064 from Qualcomm. so depending on which one is on your phone it selects frequency table from slow, nominal, fast and faster.
Google kernel source have same frequency table for fast and faster. So those with faster are not getting their extra advantage :crying:
And faster binned CPU has lot to do with UV, when you look as frequency table of faster, it is already preconfigured to have lower voltages than fast, and lot lower than slow binned.You can identify you CPU chip by below command in terminal.
adb shell dmesg | grep PVS
It will give you some output as given example below
Code:adb shell dmesg | grep PVS [ 0.873920] acpuclk-8064 acpuclk-8064: ACPU PVS: FAST
Phones with faster binned should have better battery than slower binned phone out of box without any other configuration.
And for UV its already hardcoded and can be adjusted by System Tuner app further. And OC I am not willing to add. Maybe will adjust frequency(underclock) later on but hardcoded and tested.
#!/system/bin/sh
# First we set colors
echo "255 255 255" > /sys/devices/platform/kcal_ctrl.0/kcal
# Now Gamma, need to change values at place 6 and 7 only
# value at 6 is amp0 and at 7 is amp1
# kgamma_r is for red, g for green and b for blue
# values amp0 and amp1 are located below $$$$
# ---------------------$$$$$-----------
echo "208 114 21 118 0 [B][COLOR="Red"]20 00[/COLOR][/B] 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_r
echo "210 114 21 118 0 [B][COLOR="red"]19 00[/COLOR][/B] 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_g
echo "212 114 21 118 0 [B][COLOR="red"]19 00[/COLOR][/B] 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_b
# undercover's LG Preset values :D, thank you.
#!/system/bin/sh
# First we set colors
echo "255 255 255" > /sys/devices/platform/kcal_ctrl.0/kcal
# Now Gamma, need to change values at place 6 and 7 only
# value at 6 is amp0 and at 7 is amp1
# kgamma_r is for red, g for green and b for blue
# values amp0 and amp1 are located below $$$$
# --------------------$$$$$-----------
echo "208 64 68 118 1 [COLOR="red"][B]04 02[/B][/COLOR] 48 32 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_r
echo "210 64 68 118 1 [B][COLOR="red"]00 00[/COLOR][/B] 48 32 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_g
echo "212 32 35 116 0 [B][COLOR="red"]26 16[/COLOR][/B] 80 51 3" > /sys/devices/platform/mipi_lgit.1537/kgamma_b
# Harshkernel default settings