- Status
Many of us P990 fellows have upgraded to Nexus 4 even after saying NO MORE LG
.As it is UV kernel more battery is the thing you get. For me Nexus 4 is already very fast device.
And what I was talking about in previous post is different is each processor chips when manufactured even if they are all same Qualcomm S4 APQ8064, its same like we had in P990, some phones can OC higher but some can't. But good part in here is, manufacturer have an idea of which phone can OC/UV higher than other and its not as blind try and error as in tegra2 we suffered from.
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
[
If you are on kernel of any other devs you will have it in strings SLOW, NOMINAL, FAST and FASTER
and if you have already flashed my kernel you will have it in numbers from 0 to 3 which indicate SLOW to FASTER.
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
EDIT: I GOT IT... "FASTER"
Sent from my Nexus 4 using Tapatalk 2
Last edited:
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
Haha you're right. Sold my p990 in summer and i was like: "LG? Never again!"
But the difference between the Nexus 4 and other LG phones is that
the Nexus 4 is a Nexus and the others aren't
Last edited:
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...
assuming you are rooted with superSU type su in to the emulator and hit enter first to grant permission
Reboot and try again, I got the same problem, somebody in another thread showed the solution
Sent from my Nexus 4 using xda premium
Yes, 1 is nominal. 0 is slow, 2 is fast, and 3 is faster.
I got FAST
EDIT: People who are having issues, it can be due to the fact that root access is messed up in the last cm nightly.
Last edited:
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
Side note... ex P999 user who swore off LG but here I am.
Sent from my Nexus 4
Would be great of someone report about it. UV control(thanks faux and motley) will be added in next build.
Sent from my Nexus 4
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:
Last edited:
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:
Thanks for the clarification. Now I have it clear ....
very nice work, harsh... and good explanations.
i'm pretty sure the binning of the CPUs has the same effects on Qualcomm-CPUs than it has with Intel-CPUs. Bought a pretested Intel Core i7 back then, just to make sure to get the best OC/UV-performer.
Unfortunately my Qualcomm-CPU is only "1", nominal.
If I apply your flash, would my voltages still be still lowered?
Thanx and best regards,
Hallu
i'm pretty sure the binning of the CPUs has the same effects on Qualcomm-CPUs than it has with Intel-CPUs. Bought a pretested Intel Core i7 back then, just to make sure to get the best OC/UV-performer.
Unfortunately my Qualcomm-CPU is only "1", nominal.
If I apply your flash, would my voltages still be still lowered?
Thanx and best regards,
Hallu
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
190Hello guys n gals,
This is Kernel for Nexus 4 should work on all ROMs if having unmodified RAMDISK. For sources visit my github
It is CWM flashable zip file. So can be easily flashed.
Those having kernels with modified RAMDISK and other things, do flash RESET kernel(provided by other great devs in their kernel thread) before flashing this kernel.
harshkernel was made by me from google sources, and some extra tweaks for Personal USE.
I do not have time to support like other devs, I am just sharing what I have made for myself as my daily driver.
Features:
- Added support for people who have CPU with FASTER binning.
- So now cpu supports Slow, Nominal, Fast and Faster.
- UV accordingly to have best stability. min UV is 100 so also not so less either
- Updated OnDemand and Interactive governor
- Raw ioscheduler
- Gamma control faux, also enabled init.d
- HSIC wakelock fixed
If you like it hit THANKS button.
Download file is in AnyKernel format from koush, should work on all ROMs with unmodified RAMDISK
harshkrnl build June-10 Linux 3.4.48 Link: DOWNLOAD
No update to boot.img from now on, cant upload stuff as fast as before. Slow internet
Boot Image Feb-20 (build with new 4.2.2 ramdisk): http://d-h.st/7vB
Google's 4.2.2 Stock kernel with UV, Gamma and faux's Sound. Nothing more nothing less.
Download Link: http://d-h.st/8z8
boot images will not be updated, as having very few downloads... maybe those who use it are senior members and can pack by their own if required.
sourcecode129And for Gamma Controlling using init.d script or using terminal.
Examples to learn about it.
LG Preset Undercover
Code:#!/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.
My kernel defaults, Google Preset
Code:#!/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
Values marked in RED color are only values you need to change while using this script.
and all these echo commands you can use it in terminal too, or you can run script from terminal.
I am providing scripts here, so you can directly download it to your mobile phone. Remove txt extention, and put it in /system/etc/init.d folder, and set permissions.
XDA:DevDB Information
[KERNEL][UV][Linux 3.4.48] Harsh Kernel build June-10, a Kernel for the Google Nexus 4
Contributors
Harsh
Kernel Special Features: Kernel for JB 4.2.2
Version Information
Status: Stable
Created 2013-08-22
Last Updated 2013-08-2265Changelog:
Build June-10
Linux 3.4.48
Build May-15
Linux 3.4.45
Faux's Sound 2.1
Don't break whats not broken
Build Mar-21
Linux 3.4.37
Build Mar-12
Linux 3.4.35
Faux's Sound Control
Build Mar-01
Linux 3.4.34
Disable few wifi debug
Build Feb-24
Linux 3.4.33
Upgrade to Graphics Driver from caf
More HSIC Patches from caf
Build Feb-20
Linux 3.4.32
Updated RAW to latest caf source
Build Feb-16
Linux 3.4.31
Sync with Google 4.2.2 sources
New video drivers from google
1st India Edition
Build Feb-05
Linux 3.4.29
Compiled from new setup of my Laptop
Build Feb-03
More changes to UV
Added latest fixes by Google
Build Feb-01: Safe UV
Safe UV by Skkip (UV accordingly so that stability is priority)
Build Jan-29: Gamma
Added Gamma control possibility using script or terminal
Step forward in CLEANER device (no kernel controlling apps)
Build Jan-28
Linux 3.4.28
Nothing much
Uploaded 2 builds (Normal and Lower UVed)
Build Jan-24 -fixed
Linux 3.4.27
Added westwood+ and set as default
Removed some of logging and debugs
And UV is now -100 mV across the board as per many requests.
Fixed TouchControl from my previous mess-up.
Build Jan-22
TouchControl Supported now.
Gamma control added, and also tweaked inside kernel
Removed some IO schedulers
Removed some unnecessary debugging
Build Jan-20
Updated to Linux 3.4.26
Camera driver tweak testing (not proven improvement but does not harm either)
Enabled CIFS suddenly I had need for this one
Build Jan-18
Interactive Governor is now fixed
OnDemand is set as default (use trickster app to select Interactive governor).
Build Jan-16
More changes to RAW io scheduler from caf
Update to Linux 3.4.25
And smoothness of Jan-15 continues
Build Jan-15
More tuning outside kernel code(compiler) for better smoothness.
Secret (its not kernel thing, so no GPL code)
Build Jan-11
RAW iosched patches from caf
Update interactive gov from google (plz dont use it yet)
Build with gcc46 again to test. (previous build was gcc47)
More caf patches
Build Jan-07
Showp-1984's suggested touchscreen fix
Everything same as below. Its just for touchscreen fix
Build Jan-05 L2
Updates to L2 table
Try2 on 3g data fix (no reverts on hsic wakelock fix, its still there)
Been testing this build since yesterday on 3g with sweep2wake enabled consumed my 1/3 of monthly data and had no problems. 23h 7m all on 3g - s2w enabled, with 1h 50m screen on. Battery currently at 23%
Build datatest
Lots of changes look for my github IPA branch for it.
Build Jan-03
Disabled sweep2wake by default (can be enabled by various apps)
Add support for krait cores retention (low power mode cpu core voltage handling changes)
Added Internet Protocol Accelerator (testing phase, data is working do not worry)
Build 0201
Added ROW iosched and set as default
Removed some governors (ondemand is default and preferred)
Qualcomm Secure Execution Environment Communicator fixes which were missed out before.
Build 3012
better 3g battery proven from last version
Better cpufrequency management
Changes in Omdemand for above :good:
last version for year 2012
Happy New Year.... Once again :laugh:
Build 2912
test for HSDPA battery consumption
Probably last version for year 2012 (going Paris tomorrow)
Happy New Year....
Build 2812
Fixed msm_hsic_host wakelock
Edit: 2nd Attempt to fix hsic wakelocks
Build 2712
Completely Cleaned all remaining Qualcomm InKernel mpdecision traces
Should be perfectly stable now.
Build 2512
Merry xmas
Reverted back to original mpdecision (thanks showp-1984 and Imperticus)
Added Sweep2Wake (thanks again showp-1984 genius :highfive
Warning: Sweep2Wake only active for bottom part of screen (navigation bar area)
Build 2212
Updated Latest OnDemand governor from codeaurora
Codeaurora mpdicision InKernel Solution (possible to set max frequency below project butter)
InKernel mpdicision is new approach from Codeaurora sources and not similar to show-p1984(s2w salute
)
Build 2212
Merged kernel.org Linux 3.4.x upto latest current Linux 3.4.24
Updated prima wifi drivers "prima: release 3.2.1.13"
Build 1912
CPU Binning Names added back. No more numbers
Color can be set using Franco's Display Control or Trickster Kernel MOD
Build 1812
Build Using more msm CPU oriented flags
Enable Voltage control (using System Tuner app from market)
Thanks Faux and motley for that. :good:
Build 1612
Added UV for all 4 frequency table slow, nominal, fast and faster
UV added accordingly to maintain stability for all.
As I have NOMINAL CPU, its tested on that only
Build 1512
Add support for FASTER PVS bin
Support selecting different PVS tables
Lower VDD_DIG voltage vote for L2
Color calibrated to my own liking (reduced yellow screen effect)
If you like it hit THANKS button.44Crossing fingers for the new build
New build uploaded
Build Feb-24 Changelog in post 2....
And download link in Post1.... sorry friends no upload of boot.img as my internet upload speed is about 20kbps, very slow.
If you like my kernel or download it, hit thanks
New posts
-
General Redmagic 9 Pro | 9 Pro Plus (NX769J) 9.0.13 Global EDL ROM- Latest: Oswald Boelcke
-
-
