symbi0sis kernel v1.3.1 + GuesteOC v2.2.1 (TrymHansen)
- If you like my work, you could vote positively for this thread or buy me a beer.
Info: Better Battery Stats is working! Use the latest XDA-version.
If you want to test you device's stability: Try TrymHansen's Myrt Torture Tester! - this tool is awesome : http://forum.xda-developers.com/showthread.php?t=1645938 -- read the instructions first!
Donators from XDA:
flat__line
Actarus-73
Thank you !! :good:
Donators from Handy-Faq:
amoebe1 (on XDA: franky_z)
Thank you too !! :good:
Also many donations have been made already for my Hybrid ROM which includes this kernel, thanks again!
Basic description:
a symbiosis of temasek's CM7 kernel and guestekrnL (stock) - Thanks, appreciation and credits to temasek, as his kernel has been used as base for this kernel! :good:
this is a Cyanogenmod 7 kernel! not for Stock
focus on stability, smoothness and great power consumption
Linux 2.6.32.59
allows Ramhack from 0-96 MByte (this means 0-96 MB additional real RAM, lowering GPU Ram), can be set easily with GuesteOC app, reboots aren't affected by ramhack.
comes with TrymHansen's famous GuesteOC app - following kernel-features can currently be controlled with it:
stepless or stepful over- and underclocking from 216 MHz - 1450 MHz
complete deactivation of second cpu core (and reactivation of course)
maximum screen-off frequency
second cpu core activation speeds/times and auto-calculation of those
change of IO schedulers and read-ahead buffer
swappiness
3-way virtual RAM enhancement: you can choose between Swap, ZRam, CompCache and enable/disable them on the fly
disable fsync (can be used for higher benchmarks) - attention, disabling is bad for your data in case of sudden power loss and also it can both decrease or increase power consumption
touch-light brightness (101 intensity steps choosable)
special feature: changing auto-backlight intensity (8 intensity steps choosable)
on-the-fly changing of virtual RAM size (16 - 256 MByte)
slider for vibration intensity (from very low to strong)
changing Ramhack-Size directly from within GuesteOC with a slider - 0-96 MB; modifying boot image and reboot happens automatically on applying
app for Undervolting included (MyrtUV by TrymHansen)
Default CPU speed is 1000 MHz - but you can OC using the included app of course
...
The toolchain affects: stability, smoothness, performance & power consumption.
Changelog latest version:
v1.3.1
additional UHOC (ulta high OC) version is available too with default clock of 1,1 GHz and max clock 1,536 GHz - the frequency/voltage table looks like this:
<=216 MHz - 770 mV \ <=389 MHz - 770 mV \ <=503 MHz - 800 mV \ <=760 MHz - 875 mV \ <=912 MHz - 925 mV \ <=1150 MHz - 1025 mV \ <=1312 MHz - 1125 mV \ <=1408 MHz - 1225 mV \ <=1536 MHz - 1325 mV
Click to expand...
Click to collapse
(9 steps because symbi0sis offers one faked additional freq/volt step unlike other kernels)
only use UHOC version if you really need overclocking > 1,45 GHz! otherwise use default version with OC up to 1,45 GHz
new symbi0sis toolchain v2 with full arm hard-float ABI support instead of softfp, updated components and tweaks
Which version of the kernel should I take?
only take a version with "-UHOC" at the end of the filename if you really need highest overclocking
symbi0sis toolchain is always changing and work in progress. its purpose is to beat guestekrnL toolchain in kernel smoothness, performance and battery. There is no guarantee yet that it succeeds, therefore YOUR feedback is needed. guestekrnL toolchain on the other hand is the chain which has proven to be stable, smooth and energy efficient for more than 4 months. So: basically it's recommended to always try the kernel builds built with latest symbi0sis chain and to compare with the guestekrnL chain builds. If you notice strange behavior or high power drain, you can always fall back to the good old guestekrnL chain
rktdi said:
hmm which version to choose? gueste or symbiosis tool chain? what is the difference?
Click to expand...
Click to collapse
As mentioned the compilation toolchains are used for compiling the kernel under linux (= making binary kernel image out of kernel source files) and affect battery, stability, smoothness (scrolling) and performance of the kernel. I might open a new thread for offering the chains separately soon.
Currently I like symbi0sis chain v2 the most. It's hard to say which one is smoother though. [Edit OCT 14 2012: guestekrnL chain still seems to be most liked by majority of the users concerning scrolling smoothness, but there are many positive feedbacks on power consumption of symbi0sis-chain v2 edition] Gueste Chain is from May 31 2012 (initially created for guestekrnL) while symbi0sis v2 is from October 10 2012. Gueste is the "good old stable&smooth one" and symbi0sis is the one aiming to beat (be better than) gueste --- war of the chains :laugh:
Some differences:
- symbi0sis chain v2 uses gcc compiler v4.5.4 (2012) while gueste uses gcc v4.5.3 (2011)
- symbi0sis chain v2 uses some newer libs and components than gueste chain
- symbi0sis chain v2 is a full hard-float chain while gueste chain is softfp (probably performance improvement)
- some differences in build flags
- minor other differences
So just try whatever edition you like, they are both not bad at all.
fixed LED button notification bug one more time, hopefully finally this time
enhanced kernel building script which automatically builds all 4 versions of the kernel (2 toolchains + UHOC/nonUHOC) - advantage for me basically because it saves time :laugh:
tun.ko no longer as module but directly compiled in kernel again
switched back to ZRam without snappy compression due to some lagginess reasons
drastically improved smoothness (same or better than 1.1.2 of the kernel)
various changes in kernel configuration, inspired by 1.1.2 of the kernel
added full arm hard-float ABI support for performance
SIO IO-scheduler is now default again - there have been some changes in the default values, so the currently recommended settings will be set in GuesteOC automatically after kernel flash. Try them.
changed auto-brightness steps: the lowest step now is 99% identical to CM7 kernel original default auto-brightness
new build flags for kernel modules
some tweaks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog previous versions:
v1.3
additional UHOC (ulta high OC) version is available too with default clock of 1,1 GHz and max clock 1,536 GHz - the frequency/voltage table looks like this:
<=216 MHz - 770 mV \ <=389 MHz - 770 mV \ <=503 MHz - 800 mV \ <=760 MHz - 875 mV \ <=912 MHz - 925 mV \ <=1150 MHz - 1025 mV \ <=1312 MHz - 1125 mV \ <=1408 MHz - 1225 mV \ <=1536 MHz - 1325 mV
Click to expand...
Click to collapse
(9 steps because symbi0sis offers one faked additional freq/volt step unlike other kernels)
updated GuesteOC app by TrymHansen (thank you!!!) for controlling new kernel feature, supporting new kernel modules structure & mounting and fixing some bugs
compiled with newly created symbi0sis toolchain (different from the one used for testbuild), providing improved performance and smoothness [the chain affects battery, performance, stability and smoothness]
tweakable kernel logging (logging disabled by default)
completely fixed LED button notification bugs, led button brightness now will always be restored correctly on ScreenOn to the value set in GuesteOC
screen-state-based kernel behavior: giving for example the possibility of kernel logging only when screen is on
kernel modules can now be loaded with "modprobe <module-name>" and don't need to be loaded with "insmod <full_module_path/module-name.ko>" - advantage: modprobe doesn't need full module path and also loads dependent modules if there are dependencies
added tun.ko module
compiled snappy compression/decompression as modules, will be loaded along with ZRam and unloaded if ZRam is disabled
stability improvements
removed Compcache (ZRam is better)
many changes in kernel configuration
battery-related changes
some other, minor things
I introduced a completely new kernel OnTheFly feature:
Code:
kernel_logging
(OTF name)
It accepts values 0, 1 or 2
0 = no logging [GuesteOC-default, set on boot after kernel flash]
1 = logging only when screen is on
2 = logging all the time [kernel-internal default, used until overwritten by GuesteOC]
This can be controlled/set via GuesteOC (see screenshot).
[Kernel logging is what you see when you open the app "aLogcat"]
less or no logging is believed to save some battery juice
v1.2.1.1
additional UHOC (ulta high OC) version is available again with default clock of 1,1 GHz and max clock 1,536 GHz - the frequency/voltage table looks like this:
<=216 MHz - 770 mV \ <=389 MHz - 770 mV \ <=503 MHz - 800 mV \ <=760 MHz - 875 mV \ <=912 MHz - 925 mV \ <=1150 MHz - 1025 mV \ <=1312 MHz - 1125 mV \ <=1408 MHz - 1225 mV \ <=1536 MHz - 1325 mV
Click to expand...
Click to collapse
(9 steps because symbi0sis offers one faked additional freq/volt step unlike other kernels)
building modules with -Os flag instead of -O2
using SLUB memory allocator instead of SLAB allocator for better performance
using VR scheduler as default instead of SIO (in my opinion it stays most lag-free after days of uptime)
disabled CPU alignment again (for battery)
now using Google SNAPPY compression for ZRam instead of LZO - should provide better performance. However CompCache uses LZO and in my opinion phone feels smoother when using CompCache. Just try both and compare, set the desired compressed RAM method in GuesteOC.
fixing "incompatibility" of symbi0sis with OC tools other than GuesteOC - now all tools recognize 216 MHz as lowest CPU freq instead of 389 -- possible problem: you maybe can't set min CPU freq to 389 MHz anymore in some OC tools, you would have to use 5xx instead.
fixing some smaller issues, like a touch LED bug
some changes in kernel configuration for provision of higher smoothness & battery (?)
some stability changes
Improved smoothness
v1.2
enabled CPU alignment - allowing the processor to perform unaligned accesses for many types of memory accesses
disabled uaccess with memcpy
small changes in battery driver
same toolchain as before, Flix123 toolchain unfortunately didn't work with this kernel
fixed cpufreq stats build error
building kernel modules with O2 optimization level instead of O3
reverted pwrgood_latency to default value
merged/included FORCE_FAST_CHARGE - credits to chad0989
chad0989 said:
This patch allows one to force AC or USB charging for any charger. It also provides additional security when connecting to public charging stations because with either force AC or force USB mode on, USB transfers are disabled, protecting your data.
Fast charge can be toggled by issuing:
echo 1 > /sys/kernel/fast_charge/force_charge_mode
Slow charge:
echo 2 > /sys/kernel/fast_charge/force_charge_mode
and off:
echo 0 > /sys/kernel/fast_charge/force_charge_mode
Plug your phone into the charger AFTER toggling the desired mode.
In addition I have created a toggle fast charge widget that may be used to toggle fast/slow charge on and off right from your home screen:
https://play.google.com/store/apps/details?id=com.incredicontrol.fastchargewidget
Click to expand...
Click to collapse
disabled some kernel logging
auto-removal of ETaNA kernel remains on installation of symbi0sis kernel
added a small tweak file by carburano basically for better balanced RAM management
ZRam with 200MB will now be enabled automatically on kernel installation
some other less important changes
v1.1.2
Various internal changes for providing better power consumption (really seems to be improved)
additionally: an ultra-high-OC version (UHOC) for power users and nerds.
UHOC version coming in two flavors, low voltage and high voltage
low voltage version uses following steps [cpu freq \ voltage]:
216-770 \ 503-800 \ 655-850 \ 912-900 \ 1150-1000 \ 1312-1100 \ 1408-1200\1536-1300
Click to expand...
Click to collapse
high voltage version will use following steps [cpu freq \ voltage]:
216-770 \ 503-850 \ 800-900 \ 1050-950 \ 1200-1050 \ 1322-1150 \ 1438-1250 \ 1556-1350
Click to expand...
Click to collapse
high voltage version will be built tonight
this means OC up to 1,536 GHz - will NOT work on every phone - if you get bootloops after too high OC, re-flash the kernel
UHOC version for power users and capable phones, higher power consumption possible but on normal frequencies not necessarily
if you use UHOC-lowVolt version, you could run it @1150MHz as default, because this uses the same voltage as 1000MHz. It doesn't mean it will consume the same energy (is a bit more complicated) but at least not much more and you still get more power.
Again: UHOC version will NOT work on every phone
default version with OC up to 1450 MHz is still recommended
v1.1.1
Amazing new features by TrymHansen for GuesteOC:
on-the-fly changing of virtual RAM size (16 - 256 MByte)
slider for vibration intensity (from very low to strong)
changing Ramhack-Size directly from within GuesteOC with a slider - 0-96 MB; modifying boot image and reboot happens automatically on applying - THX again to TrymHansen, you are the best!
reverted some changes in defconfig for hopefully providing a bit better battery again compared to v1.0
enabling optimized crypto routines in defconfig
changed the OTF name "gpu_ram_size" to "ramhack_size", now showing size of Ramhack in MB and not size of GPU Ram
increased max possible vibration intensity just a bit
shortened kernel name - still don't forget that this is a fork of Temasek's kernel, who has done a great job
played around with creating new toolchains, still fell back to the old one I made for my stock kernel which still provides good smoothness and battery
disabled kernel-side haptic feedback on change of vibration strength - GuesteOC tool does this anyway
added 3 small binaries to kernel setup zip for providing GuesteOC app the possibility to change ramhack size
kernel setup now (from 1.1.1 upwards) does not change ramhack size, so if you used ramhack before it will be remembered even if you flash a new symbi0sis kernel. This also means if you used a kernel without ramhack before, it won't be enabled by default after flashing a new symbi0sis kernel. Just enable it with the desired size in GuesteOC
credits during development of this version to TrymHansen
v1.1
improved smoothness
3-way virtual RAM enhancement
Ramhack possible from now on, 48 MB hack default
reduced internal logging
defconfig changes
optimized AES and SHA1 routines
current size of GPU RAM (= 128 - Ramhack value) is OTF readable in /proc/gueste/gpu_ram_size --> so 128 MB - gpu_ram_size = size of ramhack -> default: 128 - 80 = 48 MB Ramhack
OTF changeable vibrator (haptic feedback) intensity in both /proc/gueste/strong_haptic_feedback (0 or 1 , 0 sets vib to 3000 and 1 sets it to 3600) and /proc/gueste/vibe_intensity (values 1500-3600)
updated deadline & SIO IO schedulers
credits during changes of this release to morphic, wkpark, vadonka, faux123 and vork - If I forgot someone he/she is most likely mentioned in the git commits or source code merges
v1.0
Initial release
symbi0sis of temasek's CM7 kernel and guestekrnL 1.8.1 (Stock)
credits during changes of this release to temasek
proven good power consumption (as of many feedbacks)
Ramhack:
Ramhack size in MB (set it in GuesteOC):
MisjudgedTwat said:
0 -- Everything is working
32 -- Everything is working [in rare cases problems with video rec]
48 -- Everything is working [in some cases problems with video rec]
64 -- 1080p video recording/playback doesn't work
80 -- 1080p video recording/playback and some very heavy 3D games doesn't work (Chainfire3D texture resolution adjust help)
96 -- 1080/720p video recording/playback, and many 3D games doesn't work (Chainfire3D texture resolution adjust help)
Click to expand...
Click to collapse
Questions:
Is this kernel compatible with MIUI? Yes it should be, there have been multiple positive feedbacks. But backup first!
What does virtual memory/RAM mean? Virtual memory means that the real available RAM (the more the bigger Ramhack is) can either be compressed to simulate additional RAM (= ZRAM or ComCache) or it can be enhanced using a Swap file which will be stored on the SD card. Swap is slower than compressed RAM, and compressed RAM is faster but needs more battery!
I OC'd / UV'd too high and get bootloops - what now? If you OC'd too high and get bootloops, re-flash only the kernel, it will remove OC / UV ! No need to re-flash whole ROM.
Download: http://www.mediafire.com/?2m7r8ya1gksn3
Installation: Just flash. Preferably use a clean system without many left-overs from other kernel so you don't get a wrong impression of symbi0sis kernel.
Stefan Gündhör said:
Hi! Nice to hear that you are willing to try symbi0sis :good:
Well since some version symbi0sis kernel deletes the init scripts and some additional stuff flashed along with Etana kernel (if you used older versions of etana kernel before and didn't do a full wipe since then there might be some files not being deleted by symbi0sis setup script).
Easiest way would be if symbi0sis cleaned the whole init.d folder, but I always criticized this about kernel DEVs doing this because in this cause all custom init.d scripts added by creators of custom ROMs would be lost too.
However there are some things symbi0sis can't/doesn't clean: If I remember correctly, Etana kernel also tweaks /system/build.prop file with performance/networking/whatever tweaks. These entries will be left over even if you change your kernel.
You could of course replace this file with the original file of the ROM you use.
Additionally in past Etana kernel sometimes also replaced some system files with tweaked or different ones. You can't really undo that.
But basically this is no problem, the tweaks will work with symbi0sis kernel as well. I just mentioned it because user experience / power consumption / stability of "clean cm7 + symbi0sis" versus "cm7 with etana previously + symbi0sis" might be different.
But just go ahead, try symbi0sis and if you think you need a full wipe you can still do that later on
Click to expand...
Click to collapse
Complete Source: https://www.mediafire.com/folder/2m7r8ya1gksn3//symbi0sis Kernel
Screenshots: (the Antutu shots are from different versions; first shot shows ramhack 48 (=420 MB real RAM) + ZRam (=210 MB additional virtual RAM); Info: GuesteOC app by TrymHansen comes in many languages!)
better than the best...
The best among all...guys this kernel has performance with battery saving...truly it justified it's name symbiosis...performance gueste and battery temask....awesome work was waiting for something like this....hats off to you
galaxyfitankit said:
The best among all...guys this kernel has promenade with battery saving...truly it justified it's name symbiosis...performance gueste and battery temask....awesome work was waiting for something like this....hats off to you
Click to expand...
Click to collapse
Thx I hope battery of 1.1 is as good as 1.0 ! Otherwise I will have to undo some changes.
Excellent work Stefan. I'll update GuesteOC within two-three days to support the vibration-steps. (And possibly the ram-hack size.)
TrymHansen said:
Excellent work Stefan. I'll update GuesteOC within two-three days to support the vibration-steps. (And possibly the ram-hack size.)
Click to expand...
Click to collapse
Great I planned to PM you but you were faster
I reused nearly every feature of GuesteOC app
Thank u that's great - the ram-hack size (or in fact the gpu ram size) can only be read OTF, so u could display it in GuesteOC but not change - for changing I thought I make simple CMW ZIPs conatining only a small script for setting the desired Ramhack value (the boot.img /boot params have to be altered, don't know any other way yet).
The vibro-steps will be awesome as slider! 1500 - 3600 is currently allowed, but maybe I should increase a bit more? But I think 3600 should be enough.
Also the checkbox for strong vib can stay! It will set vib to 3600 or 3000 (when checked / unchecked) - and when the steps are set to 3600 (current max), then the strong-vib boolean will be updated too and set to 1 and as soon as <3600 it will be set to 0 kernel internally.
So long story short the checkbox and slider can co-exist, just make sure to update both when one is changed
Stefan Gündhör said:
Great I planned to PM you but you were faster
I reused nearly everything of GuesteOC app
That's great - the ram-hack size (or in fact the gpu ram size) can only be read OTF, so u could display it in GuesteOC but not change - for changing I thought I make simple CMW ZIPs conatining only a small script for setting the desired Ramhack value (the boot.img /boot params have to be altered, don't know any other way yet).
Click to expand...
Click to collapse
Hmmm, ok. I'll have a look at your zips and see if it's possible to do the same thing from Android. (I'm thinking dd to a location in the boot-partition at the moment, maybe not possible.)
The vibro-steps will be awesome as slider! 1500 - 3600 is currently allowed, but maybe I should increase a bit more? But I think 3600 should be enough.
Click to expand...
Click to collapse
Probably fine. I've done this before for Vadonka's kernel, which goes from 1500 to 3700.
Also the checkbox for strong vib can stay! It will set vib to 3600 or 3000 (when checked / unchecked) - and when the steps are set to 3600 (current max), then the strong-vib boolean will be updated too and set to 1 and as soon as <3600 it will be set to 0 kernel internally.
So long story short the checkbox and slider can co-exist, just make sure to update both when one is changed
Click to expand...
Click to collapse
Ok. Not sure I agree (I think it's poor design to have two controls for one value), but I can live with it
TrymHansen said:
Hmmm, ok. I'll have a look at your zips and see if it's possible to do the same thing from Android. (I'm thinking dd to a location in the boot-partition at the moment, maybe not possible.)
Probably fine. I've done this before for Vadonka's kernel, which goes from 1500 to 3700.
Ok. Not sure I agree (I think it's poor design to have two controls for one value), but I can live with it
Click to expand...
Click to collapse
Yeah we / you 'd need to unpack and re-pack boot.img from within android I believe!
and do sth like
#!/sbin/sh
echo \#!/sbin/sh > /tmp/createnewboot.sh
echo /tmp/mkbootimg --kernel /tmp/zImage --ramdisk /tmp/boot.img-ramdisk.gz --cmdline \"[email protected] [email protected] loglevel=0 muic_state=1 lpj=9994240 CRC=3010002a8e458d7 vmalloc=256M brdrev=1.0 video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:35e00:2800:800,linux:34700:1000:800,mbr:400:200:800,system:600:2bc00:800,cache:2c200:8000:800,misc:34200:400:800,userdata:38700:c0000:800 androidboot.hardware=p990\" --base $(cat /tmp/boot.img-base) --output /tmp/newboot.img >> /tmp/createnewboot.sh
chmod 777 /tmp/createnewboot.sh
/tmp/createnewboot.sh
return $?
Click to expand...
Click to collapse
but with exchanged values for ramhack like
mem=$((383+$hack))[email protected] nvmem=$((128-$hack))[email protected]$((384+$hack))M loglevel=0 muic_state=1 lpj=9994240 CRC=3010002a8e458d7 vmalloc=256M brdrev=1.0 video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:35e00:2800:800,linux:34700:1000:800,mbr:400:200:800,system:600:2bc00:800,cache:2c200:8000:800,misc:34200:400:800,userdata:38700:c0000:800 androidboot.hardware=p990
Click to expand...
Click to collapse
Ok. Not sure I agree (I think it's poor design to have two controls for one value), but I can live with it
Click to expand...
Click to collapse
Yeah I only left the boolean thing because GuesteOC currently supports it! But if you make a slider, you could perform a check if kernel supports a slider for vibration and then just don't display the checkbox anymore!
Should I increase maximum Vibration to 3700 or sth. too with next version? Stupid thing is this version has 3600 already :/ so slider of new GuesteOC wouldn't work on this correctly
Stefan Gündhör said:
Yeah we / you 'd need to unpack and re-pack boot.img from within android I believe!
Click to expand...
Click to collapse
Well, that shouldbe possible, but I'd have to bundle to binaries with the app, making it quite a bit larger. (Or possible only enable the feature if the binaries are already present - and create a cwm-zip to install them.) I'd have to do tons of testing though, can't risk bricking someone's device.
Yeah I only left the boolean thing because GuesteOC currently supports it! But if you make a slider, you could perform a check if kernel supports a slider for vibration and then just don't display the checkbox anymore!
Click to expand...
Click to collapse
That was the plan, since it still has to work on the stock kernel.
Should I increase maximum Vibration to 3700 or sth. too with next version? Stupid thing is this version has 3600 already :/ so slider of new GuesteOC wouldn't work on this correctly
Click to expand...
Click to collapse
Hehe, I haven't made the new GuesteOC yet, so do whatever you please. It'll be a few days, so make any changes you wish until then. (I can read back the value after setting it to detect if it goes to 3700 or 3600.)
downloading, trying tonight
So i will try to combine with miui
Edit: V1.1 is freezing miui. Maybe my phone cant handle preloaded OC? Can i get version with 1000 Mhz?
Sent from LG 2X using Tapatalk 2 Elite
Simply Spectacular!
Thank you...
etana's kernel has a new competitor in the daily kernel usage panorama
whoah, an update... gonna flash 1.1 now... been using 1.0 since stefan posted in temasek's thread, i'm on temasek's #132
So far, working perfect for me.
Together with CM7.2 Misjudgedtwat's build 37. RH 48 mb as default. OC to 1200.
Sent from my Optimus 2X using xda app-developers app
galaxyfitankit said:
The best among all...guys this kernel has performance with battery saving...truly it justified it's name symbiosis...performance gueste and battery temask....awesome work was waiting for something like this....hats off to you
Click to expand...
Click to collapse
Guy, did you have in test a pre-release of this? How can you say that 30 minutes after its publishing? It is supposed to have at least 5 charges to analyse battery drain.
Sent from my LG-P990 using xda app-developers app
wals46 said:
Guy, did you have in test a pre-release of this? How can you say that 30 minutes after its publishing? It is supposed to have at least 5 charges to analyse battery drain.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
He's talking about the 1.0 release of the kernel, which has only been posted in some CM7 threads 3 days ago
I didn't open the thread for 1.0 already, as I wanted to add some more features first (v1.1)
thx for the feedback so far @ all
Rayman96 said:
So i will try to combine with miui
Edit: V1.1 is freezing miui. Maybe my phone cant handle preloaded OC? Can i get version with 1000 Mhz?
Sent from LG 2X using Tapatalk 2 Elite
Click to expand...
Click to collapse
Default cpu speed already is 1000 MHz so I'm afraid it's not compatible with MIUI! :/ Some more feedbacks on MIUI would be nice though.
Edit: Maybe I have to enhance kernel installer for MIUI compatibility! First priority is CM7 but I will look into it.
Hi
i installed version 1.1 and there is a thing which is not clear about the OC frequencies.
In GuesteOC the min freq is 216MHz in Myrt Torture tester on Undervolt the min freq is 389MHz.
Could it be something wrong with my installation? I installed is over Etana, so there could be some leftover.
4lph4 said:
Hi
i installed version 1.1 and there is a thing which is not clear about the OC frequencies.
In GuesteOC the min freq is 216MHz in Myrt Torture tester on Undervolt the min freq is 389MHz.
Could it be something wrong with my installation? I installed is over Etana, so there could be some leftover.
Click to expand...
Click to collapse
What you noticed there is a special tweak I made for and use in my kernels, allowing to "fake" an additional OC voltage step which in fact helps lowering power consumption. complicated to explain but it is good for your battery and real lowest CPU freq is still 216 MHz! the voltage you set for 389 will also be used for the freqs 216-389 !
However besides that we need to review power consumption of v1.1 - in v1.0 it is nearly perfect, but maybe it got worse. If so, I will revert some changes and release v1.1.1
Stefan Gündhör said:
He's talking about the 1.0 release of the kernel, which has only been posted in some CM7 threads 3 days ago
I didn't open the thread for 1.0 already, as I wanted to add some more features first (v1.1)
thx for the feedback so far @ all
Click to expand...
Click to collapse
Disappointed, sorry Stefan.
Sent from my LG-P990 using xda app-developers app
Related
[STOCK KERNEL][NOV20] guestekrnL v2.2.1 | stable, smooth [VIBRO- &RAMHACK] [AROMA]
guestekrnL kernel v2.2.1 + GuesteOC v2.3 (TrymHansen) -- with Aroma
- If you like my work, you could press thx, vote positively for this thread or buy me a beer.
If you want to test you device's stability: Try TrymHansen's Myrt Torture Tester! - this tool is awesome : http://forum.xda-developers.com/showthread.php?t=1645938 -- read the instructions first!
Donators from XDA:
Daniele S.
flat__line
Thank you !! :good:
Basic kernel description:
this is a Gingerbread LG O2X Stock kernel! not for use with Cyanogenmod
focus on stability, smoothness and great power consumption
Linux 2.6.32.9
allows Ramhack from 0-96 MByte (this means 0-96 MB additional real RAM, lowering GPU Ram), can be set easily with GuesteOC app, reboots aren't affected by ramhack.
comes with TrymHansen's famous GuesteOC app - following kernel-features can currently be controlled with it:
stepless or stepful over- and underclocking from 216 MHz - 1450 MHz
complete deactivation of second cpu core (and reactivation of course)
setting of maximum screen-off frequency
second cpu core activation speeds/times and auto-calculation of those
change of IO schedulers and read-ahead buffer
swappiness
2-way virtual RAM enhancement: you can choose between Swap & ZRam and enable/disable them on the fly
disable fsync (can be used for higher benchmarks) - attention, disabling is bad for your data in case of sudden power loss and also it can both decrease or increase power consumption
touch-light brightness (101 intensity steps choosable)
special feature: changing auto-backlight intensity (8 intensity steps choosable)
on-the-fly changing of virtual RAM size (16 - 256 MByte)
slider for vibration intensity (from very low to strong)
changing Ramhack-Size directly from within GuesteOC with a slider - 0-96 MB; modifying boot image and reboot happens automatically on applying
app for Undervolting included (MyrtUV by TrymHansen)
Default CPU speed is 1000 MHz - but you can OC using the included app of course
OnTheFly-changing of kernel logging policy:
Code:
kernel_logging
(OTF name)
It accepts values 0, 1 or 2
0 = no logging [GuesteOC-default, set on boot after kernel flash]
1 = logging only when screen is on
2 = logging all the time [kernel-internal default, used until overwritten by GuesteOC]
This can be controlled/set via GuesteOC app.
[Kernel logging is what you see when you open the app "aLogcat"]
less or no logging is believed to save some battery juice
merged/included FORCE_FAST_CHARGE - credits to chad0989
...
For this kernel + the GuesteOC app to work properly you need init.d scripts to be working on your ROM. You should be able to enable them using the latest AROMA installer of guestekrnL >= v2.1, if they are not working on your ROM.The toolchain affects: stability, smoothness, performance & power consumption.If you can't enable ZRam, upgrade to Rebuild 2 release of guestekrnL v2.0 or to a newer releaseIf something else doesn't work: Recommended is Busybox 1.19.4 -- install it with JRummy installer, not a different installer!@ROM-CHEFs (important!):
If you want to directly include guestekrnL v2.x in your Stock ROMs, you will have to set the command line parameters of your ROMs boot.img (via Android kitchen -> modify boot image -> modify command line params) to the following (otherwise Ramhack can't be enabled by the users):
Code:
[email protected] [email protected] loglevel=0 muic_state=1 lpj=9994240 CRC=3000001a323ed07 vmalloc=256M brdrev=1.0 video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:35e00:2800:800,linux:34700:1000:800,mbr:400:200:800,system:600:2bc00:800,cache:2c200:8000:800,misc:34200:400:800,userdata:38700:c0000:800
(This will enable the default 32 MB RamHack right after the installation of your ROM with latest guestekrnL included.)
Also in v2.0 the setup script and many setup files of guestekrnL have changed - make sure to merge all the important parts into your ROM setup. Also do not include boot-up scripts which modify LED brightness or virtual RAM and similar stuff or disable kernel logging because that's the job of GuesteOC app.
Changelog latest version:
v2.2.1
smoothness-related changes for higher smoothness
tun.ko now built-in in kernel again
spica toolchain edition now is default preselected on in AROMA installer
v2.2
smoothness-related changes for higher smoothness
better RAM management
tun.ko now as kernel module instead of built-in in kernel
dropped symbi0sis-toolchain edition, instead added spica1234 toolchain edition (like the name says this toolchain has been built by spica1234, credits for this chain go to him)
new unique feature: introducing dual-vibrator support:
in GuesteOC you can set the kernel's vibration intensity (like you already know)
new: intensity 1500 - 2700 uses "weak" vibrator output device for vibration (the one used in original stock kernel)
intensity levels >2700 - 3700 use the "strong" vibrator output device
some prefer the weak device because it seems to be more "accurate", others prefer the stronger one
now it's completely up to you which one to use, without having to change the kernel version! Enjoy
Changelog version 2.1:
v2.1
also read the v2.0 Changelogs!
smoothness-related changes for higher smoothness
added FlixEdition-Power by and for flix123 with the following differences to official version: https://github.com/StefanGuendhoer/guestekrnL_for_stock_v1.6.2_upwards/compare/master...FlixEdition - the differences are minimal because I merged some good changes into the official version of the kernel. Nevertheless thanks to flix123 for his endless efforts to make this kernel smoother :good::victory: Currently the FlixEdition-Power is only different from guestekrnL-Flix123-Chain in it's default GuesteOC settings (heavy use of second core, different scheduler, stock led brightness,...) and in the default ramhack size. Still flix123 has earned his own edition named after him, as he is the creator of the very smooth flix-toolchain I use for 2 of my builds as well and the one responsible for some more smoothness improvements in the kernel in general.
Still I recommend to use the normal/official build as of the default heavy use of second core of FlixEdition-Power (higher battery drain during use) and because fsync is disabled by default - not everyone likes that.
AROMA Installer is now able to enable init.d, apply smoothness tweaks and convert filesystem to ext4 if a user selects this option - however this option can only be experimental as it replaces the boot image, which should but might not work fine on every stock ROM. Backup first!
Changelog version 2.0 part 3/3:
v2.0 Rebuild 2
this kernel version is still the same as v2.0, so also read the other v2.0 Changelogs!
fixed ZRam not working for everyone - see the changes here: https://github.com/StefanGuendhoer/...mmit/55eac20be15cffe001c5d2ce9452f3887e7fff74
This rebuild has been made for all those who had problems enabling ZRam
Who already got ZRam working and already has latest GuesteOC v2.3, does NOT need to upgrade to this release!
Changelog version 2.0 part 2/3:
v2.0 Rebuild 1
this kernel version is basically the same as v2.0 so please read the changelog of v2.0 additionally!
introducing 2 new editions (built with a toolchain by flix123) for provision of maximum smoothness + an extra AROMA version with ALL kernel editions inside:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
all other editions are the same as before, only GuesteOC has been updated and they have been recompiled (couldn't avoid)!
AROMA installer package has been built automatically by my new enhanced kernel building script
AROMA installer package allows you to choose between 6 different kernel editions, and allows you to set max. CPU frequency, RamHack size, desired IO Scheduler and ZRam enabled/disabled right during the installation of the guestekrnL kernel
new GuesteOC v2.3 directly included with undervolting AND overvolting (new) - TrymHansen is the creator of guesteOC, thank you very much for this awesome new version, Trym! :good:
complete sources of guestekrnL v2.0 will be published soon - this means the Ramhack for stock, vibration strength for Stock, tweakable kernel logging and other features introduced by me for guestekrnL will be available for other developers too - please don't forget who introduced them first.
Advice:
Please try the new edition(s) compiled with flix123 toolchain (by flix123, thanks to flix for provision!) - you can test & install them along with your preferred settings with the cool new AROMA installer package!
Changelog version 2.0 part 1/3:
v2.0
introducing ramhack + changeable ramhack size (!) (details some lines below) - never seen on any LG O2X stock kernel before
introducing completely adjustable vibration intensity (!) (details some lines below) - never seen on any LG O2X stock kernel before
additional UHOC (ulta high OC) version is available too with default clock of 1,1 GHz and max clock 1,536 GHz - the frequency/voltage table looks like this:
<=216 MHz - 770 mV \ <=389 MHz - 770 mV \ <=503 MHz - 800 mV \ <=760 MHz - 875 mV \ <=912 MHz - 925 mV \ <=1150 MHz - 1025 mV \ <=1312 MHz - 1125 mV \ <=1408 MHz - 1225 mV \ <=1536 MHz - 1325 mV
Click to expand...
Click to collapse
(9 steps because symbi0sis offers one faked additional freq/volt step unlike other kernels)
only use UHOC version if you really need overclocking > 1,45 GHz! otherwise use default version (HOC) with OC up to 1,45 GHz
new symbi0sis toolchain v2 with full arm hard-float ABI support instead of softfp, updated components and tweaks
4 kernel versions:
Which version of the kernel should I take?
only take a version with "-UHOC" at the end of the filename if you really need highest overclocking
symbi0sis toolchain is always changing and work in progress. its purpose is to beat guestekrnL toolchain in kernel smoothness, performance and battery.
rktdi said:
hmm which version to choose? guestekrnL tool chain or symbiosis tool chain? what is the difference?
Click to expand...
Click to collapse
As mentioned the compilation toolchains are used for compiling the kernel under linux (= making binary kernel image out of kernel source files) and affect battery, stability, smoothness (scrolling) and performance of the kernel.
guestekrnL chain is from May 31 2012 (initially created for guestekrnL) while symbi0sis v2 is from October 10 2012. guestekrnL chain is the "good old stable&smooth one" and symbi0sis is the one aiming to beat (be better than) gueste --- war of the chains :laugh:
Some differences:
- symbi0sis chain v2 uses gcc compiler v4.5.4 (2012) while guestekrnL uses gcc v4.5.3 (2011)
- symbi0sis chain v2 uses some newer libs and components than guestekrnL chain
- symbi0sis chain v2 is a full hard-float chain while guestekrnL chain is softfp (probably performance improvement)
- some differences in build flags
- minor other differences
Feedback on the performance of both chains by different users:
- symbi0sis chain v2 seems to provide a bit better power consumption than guestekrnL chain
- symbi0sis chain v2 seems to provide the best overall performance
- guestekrnL chain seems to provide the smoothest slow-scrolling (so the fewest lags when scrolling very slowly)
- guestekrnL chain seems to be a bit more stable than symbi0sis chain (so if you use symbi0sis and have freezes or something you might want to try guestekrnL chain edition)
So just try whatever edition you like, they are both not bad at all.
enhanced kernel building script which automatically builds all 4 versions of the kernel (2 toolchains + UHOC/nonUHOC) - advantage for me basically because it saves time :laugh:
switched back to ZRam without snappy compression due to some lagginess reasons
drastically improved smoothness
various changes in kernel configuration, inspired by 1.1.2 of my CM7 symbi0sis kernel
added full arm hard-float ABI support for performance
there have been some changes in the kernel & GuesteOC default values, so the currently recommended settings will be set in GuesteOC automatically after kernel flash. Try them.
changed auto-brightness steps: the lowest step now is 99% identical to CM7 kernel original default auto-brightness
new build flags for kernel modules
updated GuesteOC app by TrymHansen (thank you!!!) for controlling new kernel feature, supporting new kernel modules structure & mounting and fixing some bugs
tweakable kernel logging (logging disabled by default)
screen-state-based kernel behavior: giving for example the possibility of kernel logging only when screen is on
kernel modules can now be loaded with "modprobe <module-name>" and don't need to be loaded with "insmod <full_module_path/module-name.ko>" - advantage: modprobe doesn't need full module path and also loads dependent modules if there are dependencies
stability improvements
removed Compcache (ZRam is better)
I introduced a completely new kernel OnTheFly feature: (never seen on any LG O2X stock kernel before)
Code:
kernel_logging
(OTF name)
It accepts values 0, 1 or 2
0 = no logging [GuesteOC-default, set on boot after kernel flash]
1 = logging only when screen is on
2 = logging all the time [kernel-internal default, used until overwritten by GuesteOC]
This can be controlled/set via GuesteOC (see screenshot).
[Kernel logging is what you see when you open the app "aLogcat"]
less or no logging is believed to save some battery juice
Amazing new features by TrymHansen for GuesteOC:
on-the-fly changing of virtual RAM size (16 - 256 MByte)
slider for vibration intensity (from very low to strong)
changing Ramhack-Size directly from within GuesteOC with a slider - 0-96 MB; modifying boot image and reboot happens automatically on applying - THX again to TrymHansen, you are the best!
optimized AES and SHA1 routines
current size of Ramhack is OTF readable in /proc/gueste/ramhack_size -> default: 32 MB Ramhack [changebale in GuesteOC]
OTF changeable vibrator (haptic feedback) intensity in /proc/gueste/vibe_intensity (values 1500-3700) [changebale in GuesteOC as well]
enabling optimized crypto routines in defconfig
added 3 small binaries to kernel setup zip for providing GuesteOC app the possibility to change ramhack size
many changes in kernel configuration
battery-related changes
some other, minor things
some tweaks
credits during changes of this release to TrymHansen, morphic, wkpark, vadonka, faux123 and benee - If I forgot someone he/she is most likely mentioned in the git commits or source code merges or the changelogs and commits of my symbi0sis kernel
Ramhack:
Ramhack size in MB (set it in GuesteOC):
MisjudgedTwat said:
0 -- Everything is working
32 -- Everything is working [in rare cases problems with video rec]
48 -- Everything is working [in some cases problems with video rec]
64 -- 1080p video recording/playback doesn't work
80 -- 1080p video recording/playback and some very heavy 3D games doesn't work (Chainfire3D texture resolution adjust help)
96 -- 1080/720p video recording/playback, and many 3D games doesn't work (Chainfire3D texture resolution adjust help)
Click to expand...
Click to collapse
Questions:
What does virtual memory/RAM mean? Virtual memory means that the real available RAM (the more the bigger Ramhack is) can either be compressed to simulate additional RAM (= ZRAM) or it can be enhanced using a Swap file which will be stored on the SD card. Swap is slower than compressed RAM, and compressed RAM is faster but needs more battery!
I OC'd / UV'd too high and get bootloops - what now? If you OC'd too high and get bootloops, re-flash only the kernel, it will remove OC / UV ! No need to re-flash whole ROM.
Download all versions: http://www.mediafire.com/?9lvnkfthj9dbo
Installation: Just flash. Preferably use a clean system without many left-overs from other kernel so you don't get a wrong impression of symbi0sis kernel.
Stefan Gündhör said:
Hi! Nice to hear that you are willing to try guestekrnL :good:
Well since some version guestekrnL deletes some init scripts and some additional stuff flashed along with other kernels like HorsePower, but there might be some files (left-overs) not being deleted by guestekrnL setup script.
Easiest way would be if guestekrnL cleaned the whole init.d folder, but I always criticized this about kernel DEVs doing this because in this cause all custom init.d scripts added by creators of custom ROMs would be lost too.
However there are some things guestekrnL can't/doesn't clean: Tweaks by other kernels in /system/build.prop file per example. These entries will be left over even if you change your kernel.
You could of course replace this file with the original file of the ROM you use.
Additionally in past some kernels also replaced some system files with tweaked or different ones. You can't really undo that.
But basically this is no problem, the tweaks will work with guestekrnL as well. I just mentioned it because user experience / power consumption / stability of "clean ROM + guestekrnL" versus "ROM with different kernel previously + guestekrnL" might be different.
But just go ahead, try guestekrnL and if you think you need a full wipe you can still do that later on
Click to expand...
Click to collapse
Complete sources in the main download folder: http://www.mediafire.com/?9lvnkfthj9dbo
Screenshots: will follow soon
Changelogs & description guestekrnL v1.x:
guestekrnL v1 - for Stock & Stock-based ROMs
Download all Versions: http://www.mediafire.com/?9lvnkfthj9dbo
Latest version (v1.8.1-HighOC): http://www.mediafire.com/?pfby2anqqdifz
Latest FlixEditions by Flix123 (based on guestekrnL 1.8.1 if > v1.3): http://www.mediafire.com/?kguh32agjhmgp
You find the latest GuesteOC tool (for overclocking and tweaking) by TrymHansen always here: LINK
Click to expand...
Click to collapse
You need init.d to be already working on your ROM in order to use GuesteOC! - If u don't have init.d yet, u can enable using a spica PerformancePack
Click to expand...
Click to collapse
Easily build your own (modified) version of guestekrnL: http://forum.xda-developers.com/showthread.php?t=1678049
Click to expand...
Click to collapse
Changelog:
June 09, 2012 -- added best battery edition of guestekrnL v1.8.1: LINK
Changelog:
June 03, 2012 -- guestekrnL v1.8.1-HighOC: LINK
Changelog:
May 30, 2012 -- first community build of guestekrnL is out -- guestekrnL-FlixEdition-v1.1: LINK
Changelog:
May 28, 2012 -- rebuild of guestekrnL SR99R100.1PI.1337 using a different VM -- rebuilt version is smoother than the build from yesterday (May27)!
Changelog:
May 27, 2012 -- guestekrnL SR99R100.1PI.1337: LINK
Changelog:
May 13, 2012 -- guestekrnL v1.7_SE-Final: LINK
Changelog:
May 01, 2012 -- guestekrnL v1.7.0: LINK
Changelog:
April 26, 2012 -- guestekrnL v1.6.2: LINK
Changelog:
April 17, 2012 -- guestekrnL v1.6.1: LINK
Changelog:
April 13, 2012 -- Bugfix01 for guestekrnL v1.6:
Small Bugfix: Trym has discovered a very small bug, causing one of the saved OTF frequencies not to be remembered correctly after reboot. You can solve it by flashing the Bugfix01 or the kernel with Bugfix01 included.
(This is no kernel bug! Just a bug in an /etc/init.d/ script responsible for "remembering" the OTF values)
Click to expand...
Click to collapse
Changelog:
April 12, 2012 -- guestekrnL v1.6 + Bugfix01 (April 13): LINK
Changelog:
March 26, 2012 -- guestekrnL v1.5: LINK
Changelog:
March 20, 2012 -- guestekrnL v1.4.1: LINK
Changelog:
March 07, 2012 -- guestekrnL v1.3.1:
extremely small kernel and modules sizes (even without -Os compilation flag)
both ZRam (+369 MB Ram) and Swap (+383 MB Ram) enabler/disabler available for download - freedom of choice (ZRam enabler will disable Swap and vice-versa) ; Zram should be more performant than Swap, but eventually also drain the battery faster ; both ZRam and Swap are disabled by default
BFQ scheduler updated
many entries added to global kernel configuration file "include/linux/guestekrnl.h" (only important for users interested in compiling guestekrnL from source)
bug fixes, performance tweaks
compilation flags changed (-O2 instead of -Ofast)
some kernel logging removed
xz-compressed kernel image, xz-(de)compression (boot-time) support added
reverted some changes in lowmemorykiller
many voltage and clock/speed adjustments
new version of ZRam enabler, the old one won't work!
stable, not too highly undervolted kernel -- you can UV yourself using UV tools though (only overclockable edition)
Changelog:
March 03, 2012 -- guestekrnL v1.2.1:
Overclocking bug fixed - once CPU is OC'd it will stay OC'd now
changes in cpu speed steps: new steps are 216, 324, 503, 800, 1015, 1100, 1216, 1408 (same steps as etana kernel currently uses)
kernel default cpu speed now 1.0 GHz like stock kernel
screen off max cpu speed now 503 MHz
changes again in second core handling
stability fixes
strong vibration editions (thx to spica1234) -- please note that strong vibration might cause problems if haptic feedback is enabled in LG stock keyboard:
markop90 said:
I guess the vibrator is too strong and LG "tap" sensors are activated moving the cursor randomly
Click to expand...
Click to collapse
Changelog:
March 02, 2012 -- Additional version without OC/UV possibility @1.0 GHz Stock-max.Speed -- for stock kernel lovers
Changelog:
March 01, 2012 -- guestekrnL v1.2 FINAL:
never-seen smoothnes @ 912 MHz (= underclocked)
non-working ramzswap kernel module removed
ZRAM integrated as kernel module (use is optional; use of ZRAM "increases" RAM amount (= +369MB), but might drain battery faster)
activation/deactivation pack for ZRAM
old swap file will be deleted on kernel or zram pack install
lower swappiness if no ZRAM is used
ipv6 enabled again
revert second core activation & treshold back to stock kernel settings for better battery
there will be an additional version with stronger vibration soon (thanks and credits to spica!)
currently two downloadable & flashable kernel ZIPs:
guestekrnL_v1.2_FINAL_withAndrevOC_normalVibration.zip -> Andrev OC Adjuster and Myrt Undervolt GUI will be installed directly with the kernel
guestekrnL_v1.2_FINAL_Bulk_normalVibration.zip -> Only the kernel will be installed
-- pending: version with stronger vibration
Changelog:
February 18, 2012 -- FINAL version of v1.1:
new cpu speed steps & voltages
again more smoooothness (scrolling, responsiveness)
max. ScreenOff CPU frequency lowered to 316 MHz and some other changes (hopefully saving some juice)
3 versions of kernel with different cpu speed steps:
Low overclock version with cpu speed steps 216-316-503-655-816-912-1015-1100 (MHz) -- recommended version!!
Medium overclock version with cpu speed steps 216-316-503-655-816-912-1015-1216 (MHz)
High overclock version with cpu speed steps 216-316-503-655-816-912-1015-1312 (MHz)
the first 7 cpu speed steps are the same in all 3 versions, because I decided these steps are the best choice -- there is only one OC step because there can only be 8 CPU steps (handled by OC tools)
try 1,1Ghz max version, it is smooth enough for nearly everyone I hope, even at 1,0 GHz!!
default max cpu clock (screen on) is 1015 MHz
Features/Description
WIPE DALVIK CACHE BEFORE INSTALL
- EXT2/3/4 built in
- based on official LG v20Q kernel sources
- OC/UV support, overclocking up to 1408MHz
- Andrev OC compatibility
- not highly undervolted by default, you can do this yourself using tools
- however, still some voltage tweaks
- CPU clock locked at max. 503 Mhz while screen is off (taken from swiftextreme kernel if I remeber correctly) - no need to set this in oc tools
- default CPU clock at 1.0 GHz, you can higher/lower it yourself using OC tools
- very smooooooth
- Voodoo Sound
- SLQB
- CIFS, TUN
- SWAP & ZRAM support
- many Tweaks either by me or "inspired" and taken from the source codes of ironkrnL and SwiftExtreme kernel
- compiled with Linaro GCC & Toolchain
- more things which you can find in the latest changelogs
Credits:
- setiron
- fajarep
- cpasjuste
- pastime1971
- spica1234
- supercurio
- dr4go
- LG for v20Q sources
Big THX to spica1234 for supporting me via PM during development!!!!
Latest sources @ Github (1.0 sources @mediafire): https://github.com/StefanGuendhoer/LG-P990-O2X----guestekrnL-for-stock for kernels < 1.6.2 and https://github.com/StefanGuendhoer/guestekrnL_for_stock_v1.6.2_upwards for kernels > 1.6.2 OR at http://androtransfer.com/?developer=gueste&folder=sources
Source for kernel 1.7-SE is within the download folder of the kernel and @androtransfer and @mediafire!
I'll not use this moment, because I use CM7 + vadonka's kernel. But I followed the topic and kernel development, for future testing based on a stock rom. Thanks Stefan.
totally agree with your initial paragraph, personally I envy the knowledge that shows every day spica, but for the ignorant like me, is much more useful to mention kernel set, and while this is a personal opinion, maybe instead so many parameters to configure, it would be more useful, use presets as a function of the tastes of each user, power, response, saving battery etc etc, well, maybe not the right place here, well, in principle, its kernel is installed normally, it may seem silly but I assure you it is not, say my phone is very special in terms of internal modificaiones already the slightest forces blocked at the moment I tried connecting wifi perfect, seamless gPS, fM radio without problems and later proves the bt. As for the rom, I'm wearing the carburano and is perfectly smooth, no lags etc., for the moment .... we know that android is the opposite of wines worsen over time. Best regards, and I hope this is not really your last job for our phone, I say sincerely.
Stefan,
Thank you very much for this kernel, installed without thinking and testing it now. Couple of observation I made, and opinion I have about the testing stuff.
1. I have no experience in android and stand in minus on technical aspects. You opinion about letting users do the testing of kernels is kind of valid BUT since IMHO, what spica doing is the right thing here. Since this is a development section. So technically developers release their work here so that others developers can test it and contribute 'technically' to improve their work. Honestly speaking dumbass users like me have absolutely no place here .
Everyone who uses the work of a developer have to , should and must understand that what he is doing is testing a possible experimental work and it can lead to unpredictable results. Then analyze what happens, look for possible workaround or solution and give it back to the developer and others, to improve his work.
Dumb users like me have no place here because I don't understand what happens if I use a particular switch or parameter. So there is absolutely no point doing something that I have no clue and then come whining and spoil the developers thread with statements like "helppppppp or my phone is deadddd " or similar things, without even bothering to give details like - for example - what kernel they use, what BB / ROM combination they have, What other application they installed that possibly can create this problem.
Having said that, there are a lot of good developers who patiently help people like this because of the goodness of their heart - you are on of such person. Yet, this being a developer's section should not be treated by noobs as a personal helpdesk to get instant technical support for FREE. If that happens, it affect the development very badly because it wastes everyone's time - especially of the developers.
Phew..! Since my rant is over, I will get back to you 'if' I understand what happens after installing your kernel and eagerly waiting for your latest gift to us .
Congrets for new kernel, nice to see you back
No offence, I don't like even to write this, first time in my life I'm writing this.
OP:
It's not only the instability of current kernels, it's also the "overkill" especially spica does with his latest RC12 kernel - I prefer to keep things simple, users are users and not developers, and so I don't really like this "outsourcing" of sensitive kernel settings to users. There are various good CM7 kernels and they don't need this stuff either. Also spica compiles his kernels with the O3 optimisation flag instead of the usual O2 flag. O3 means even higher code optimisation, but so high that it can easily result in broken kernels or weird issues and bugs. Almost nobody uses O3 flag for kernel compilation. So I tried to create a stable, performant and hopefully not too much battery-consuming kernel myself. The sources of ironkrnL and Swiftextreme kernel (both CM7 kernels) have been very inspiring and helpful.
==>" it's also the "overkill" especially spica does with his latest RC12 kernel - I prefer to keep things simple, users are users and not developers "
What I do is something you can't, that's why want to keep it simple What I do is something *new* which needs more skills, knowledge of HW and programming Yes users are user not Devs, That's why I've set simple 'Powersave" and 'Nitros' profile for them who have no more knowledge. And we've an APP now to control these values
==>" and so I don't really like this "outsourcing" of sensitive kernel settings to users"
SENSITIVE? None of my max values are above your or any other Kernel's max values. I've given an opportunity to lower the values not increase the value. And my default values are lower than your or anyother kernel So in terms of SENSITIVE, atleast RC12 values are not sensitive, And I've written kernel modules to not accept any SENSITIVE values,You don't like thiis "outsourcing" values. What you like applying various pre-available *patches* which berely are made for android? Or you dislike someone's coding knowledge?
==> " There are various good CM7 kernels and they don't need this stuff either"
Nobody needs nothing as per your psychology. And as per your psychology CM Devs should have abandoned development after they had released first stable version. As per your psychology they should have stopped adding new features and releasing nighties and RCs? What can we say in other words? "End Of Development?" Nothing is needed until it's valued. Do you know what SR and RC means? PPL who wants stability can stick with SR series. CM7 kernel don't need this stuff cause they've more important other things to concentrate on
==>"Also spica compiles his kernels with the O3 optimisation flag instead of the usual O2 flag. O3 means even higher code optimisation, but so high that it can easily result in broken kernels or weird issues and bugs. Almost nobody uses O3 flag for kernel compilation"
Where you learn this? Yes nobody uses O3 but Ofast which is 2 steps more optimized flags. Swiftextreme uses Ofast and many devs use Ofast. So as per your theory does these kernels are resulted broken kernels with bugs and issues?
Then I think you should e-mail GCC to remove this O3 flag
==>"So I tried to create a stable, performant and hopefully not too much battery-consuming kernel myself"
Your kernel obviously should be stable cause You've done nothing creative. What do you think is resposible for stability? You used LG base source, merged Oc and Voodoo codes and other codes available. So definately it should be stable. But is that stability is credit of yours or LG and other Devs? There is a way much difference in compiling kernel and developing kernel. Anybody can merge changes with basic linux knowledge and issue few commands and kernel is ready. Developer in real mean is someone who creates something out of nothing, who has knowledge of stuff and how stuff work, someone with knowledge of programming to write codes, read and to be understood codes and knowledge to rectify wrong code and correcting them. There is a way much difference in Kernel Compiler and Kernel Developer.
This is no personal, I dont want to hurt anyone but to clear somethings Dont mind
There are some users who prefer simple and stability rather than something with many new features but not so stable.
ryaneu said:
There are some users who prefer simple and stability rather than something with many new features but not so stable.
Click to expand...
Click to collapse
Yes you're absolutely right but whats the theory and logic of writing that paragraph in OP thread?
Does it make sense?
Sent from my LG-P990 using Tapatalk
the difference between the v20l and the v20q kernel is almost nothing.
better off pick any v20l based OC kernels what is tested by the users already
some people believe that the new v20q kernel is have a new features and better stability. i was compared the v20l and the v20q kernel, an other thread im posting the difference and a patch file too. i can say the lg developers did not force themselves.
Moderator Message
Can we stay on topic?? Thanks
Yes that would be bad to close this thread...... for some words that should never have been written....
+1 for spica, critizing a developer for doing something new is not right IMO. if u want stable then stick to stock.
BTW loving the flaming going on ;-)
coldfear00 said:
+1 for spica, critizing a developer for doing something new is not right IMO. if u want stable then stick to stock.
BTW loving the flaming going on ;-)
Click to expand...
Click to collapse
I do not think anyone has criticized spica, quite the contrary, two different views and equally positive in the absence of our device as usual and once again the LG more interested, however, the thread is to talk Kernel, not if I like something or other but ultimately developers to present their work and the rest to try them. and our opinions to help improve the whole story. Greetings to all.
Lo_RaT_PeNaT said:
I do not think anyone has criticized spica, quite the contrary, two different views and equally positive in the absence of our device as usual and once again the LG more interested, however, the thread is to talk Kernel, not if I like something or other but ultimately developers to present their work and the rest to try them. and our opinions to help improve the whole story. Greetings to all.
Click to expand...
Click to collapse
if u wanna talk about kernels and not personal views about who likes what, then stefan should not have said this line " It's not only the instability of current kernels, it's also the "overkill" especially spica does with his latest RC12 kernel - I prefer to keep things simple, users are users and not developers "
Yes that's what I'm pointing, on the first page(OP) of this thread, he should write describtion about his kernel like what other dev does, not about what I or anyone is doing
Never mind
Sent from my LG-P990 using Tapatalk
I insist, I think the thread is to discuss the kernel, after each has their opinions, but to make it clear, how about this?
[QUOTE = Stefan Gündhör; 22370651]
Big THX to spica1234 for support supporting me via PM DURING development!!
[/ QUOTE]
You think stefan is being selfish and evil?, I think not, just believe that for most users, and say it clear, most, including myself meeting, we are unable to understand many things, is a opinion, written words can lead to misinterpretations and in this case, I think stefan at no time intended to offend or criticize the work of spica, but good sprucing think they will not be no doubt. In any case I think this should stay and finished, sure everything is clarified and two, two developers, along with others are keeping alive our mobile and certainly is welcome. Greetings to all
hi, wow, good luck with the kernel i made my non overclock kernel in our local forum based on v20q for stock based rom like gr6...
make sure you got a lot of free time, doing kernel and rom at the same time takes time a looooot.....
fajarep said:
hi, wow, good luck with the kernel i made my non overclock kernel in our local forum based on v20q for stock based rom like gr6...
make sure you got a lot of free time, doing kernel and rom at the same time takes time a looooot.....
Click to expand...
Click to collapse
fajarep should again return to cheer you too .... not it
getting back to the topic did some1 actually tested this kernel?
Lo_RaT_PeNaT said:
I insist, I think the thread is to discuss the kernel, after each has their opinions, but to make it clear, how about this?
[QUOTE = Stefan Gündhör; 22370651]
Big THX to spica1234 for support supporting me via PM DURING development!!
[/ QUOTE]
You think stefan is being selfish and evil?, I think not, just believe that for most users, and say it clear, most, including myself meeting, we are unable to understand many things, is a opinion, written words can lead to misinterpretations and in this case, I think stefan at no time intended to offend or criticize the work of spica, but good sprucing think they will not be no doubt. In any case I think this should stay and finished, sure everything is clarified and two, two developers, along with others are keeping alive our mobile and certainly is welcome. Greetings to all
Click to expand...
Click to collapse
y r u so hooked up on proving stefan innocent, how do u know he didnt mean to critize spica, and y dosent stefan clear the foul air himself on this thread.
im +1 for spica because if my english aint so bad this line he said looks like criticism to me " It's not only the instability of current kernels, it's also the "overkill" especially spica does with his latest RC12 kernel - I prefer to keep things simple, users are users and not developers "
for my issue resolved, but absolutely sure that the intention of stefan is not apparently be interpreted, also without a doubt, and now please, to the point, the kernel, and I must say that I tried the BT's car and has not been disconnected at any time, not blackscreen not freezes at least for now the battery issue, I can not say for now. Greetings to all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thanks to http://yasserrizky.com/ for your banner
objective : good battery life
Not for AOSP / AOKP ROM
Download Here
(thanks to geistteufel for your ftp server, space and bandwith!)
Do not forget to donate to this forum XDA :
http://forum.xda-developers.com/donations.php
Stable Version change-log:
Incremental update from last version
GalaxSih Kernel Jelly Bean v1.3
Big thanks to beta tester:
ksr007
tupac19861013
hieupham
Sad56
BR377
poppy9009
walda
jothi2lingam
saintsinner25
hshah
wl3gan
Milchbeck
eric-filth
"D"
drdoulittle
erto90
pidz
6pudu5
brunodu91
RuralGalaxy
androb0t
demmo81
agam1308
Tenacius D
[email protected]
Click to expand...
Click to collapse
change log:
Upgrade from 3.0.36 to linux kernel 3.0.37
Fixed ROM power savings feature, This is now fixed and powersavings mode will throttle to 1000MHz. - credit to andreilux
Revert "wakelock: use single threaded workqueueus"
Mdnie: custom settings: Includes hardcore sharpnes fixes, and black gamma curve adjustment for black crush (andreilux)
Remove Miscellaneous tweaks from RAMDISK
Sync with XXDLJ4 boot.img (thanks andip for boot.img file)
Back to arm-eabi-4.4.3 compiler from Linaro compiler
LZO as kernel compression
Compile Logger as module
Printk.c: disable linux printk logging thanks to AndiP
Disable Sound Debug
Revert "pegasusq: add tweak from galaxsih ICS v3.9 pegasusq tweak ( now its setting totally like stock kernel)
Revert "reduce busfreq volt to -25mV"
Revert "cpufreq: pegasusq: instead of jumping around the frequencies leaving some unused we now jump from one to another by 100Mhz increments
Revert "kernel optimizations - by VOKU"
Revert "wakelock: use single threaded workqueueus"
GalaxSih Kernel Jelly Bean v1.2
Thanks to Beta contributor:
SETdown
spencer1208
Sad56
samaxen
netchow
delgamarco
hshah
kwankl
tupac19861013
brunodu91
ksr007
mariosraptor
AndiP
Milchbeck
Chillz88
borjaag
RuralGalaxy
androb0t
poppy9009
Razertje
jothi2lingam
ph3nom
Jmldsilva
slimldj
benc88
currydude
wtfshouldidonow
fastcx
Click to expand...
Click to collapse
Update linux kernel from 3.0.31 to 3.0.36
Kernel optimizations - by VOKU
Resync to XXDLJ2 ramfs thx to andip for your stock boot.img
Revert : power: reduce regulator initializations to regulator minimal (this commit is not for i9300 - thanks to andreilux for your notice)
Revert: sensorhub: Fix firmware mislabeling and version checking (this commit is not for i9300 - thanks to andreilux for your notice)
Wakelock: use single threaded workqueueus
Switch do_fsync() to fget_light()
Staging: android: lowmemorykiller.c - Fix compiler warning about the type of the module parameter.
pegasusq (based on ondemand): cpuidle detection by Andrea Arcangeli
Android Logger as a module - thanks to andip for your idea.
Possibly car dock error have been fix..need your report to prove it., thanks to gokhanmoral
MTP fix for OSX user
Big Thanks to 1.1 Beta contributor:
AbuYahya
JYJY
[email protected]
ph3nom
ongchonghian
Sad56
x10i DauL
fastcx
jothi2lingam
raaghav2
tupac19861013
androb0t
samaxen
RuralGalaxy
fastcx
SETdown
poppy9009
Click to expand...
Click to collapse
GalaxSih Kernel Jelly Bean v1.1
Change log:
power: reduce regulator initializations to regulator minimal -AndreiLux
sensorhub: Fix firmware mislabeling and version checking
Payloaded firmware version doesn't correspond labeling. This causes the kernel
to reflash the firmware on every single boot thinking it has a newer firmware
than listed on the device. - AndreiLux
max77686+max77693 revert: disable debugging - this will fix USB charge error.
android: lowmemorykiller: Change default debug_level to 1
cpufreq: pegasusq: instead of jumping around the frequencies leaving some unused we now jump from one to another by 100Mhz increments - franciscofranco
net: wireless: bcmdhd: sync with newer sources - gokhanmoral
merges with GT-I9300_SEA_JB_OpenSource.zip -gokhanmoral
re-enable touchbooster
mdnie: black crush fix. (Thanks to AndreiLux)
cpuidle: Change state properties - AndreiLux
fix front camera crash - (revert front camera block-space to default stock)
change cfq to deadline io scheduller as default io scheduller
thanks to Sad56 for your idea.
about Deadline:
The scheduler helps organise reads and writes in the I/O queue to maximise performance. The default scheduler in the Linux kernel is CFQ (Completely Fair Queuing), which is designed with the rotational latencies of spinning platter drives in mind. So while it works well for standard hard drives, it doesn't work so well when it comes to SSDs.Fortunately, the kernel comes with some other schedulers to play with, and here the deadline and NOOP schedulers are ideal
Wifi: Reenable IPv6, disable multicast in suspend (entropy512)
Why do they keep on reenabling that stupid "let dirty networks tank the battery" feature?I have yet to see an example of something that disablingmulticast in suspend breaks. Signed-off-by: entropy512
reapply bcmdhd: change packet filter settings to block multicast
bcmdhd: update wireless driver to 1.28.11.9 from Korean S3 (gokhanmoral)
mmc: Increase timeout - this tweak for some crappy cards (andreilux)
Revert:"disable GENTLE_FAIR_SLEEPERS"
reduce busfreq volt to -25mV
set sched_mc_power_savings to 1
Big thanks to : V1.0 beta tester:
Milchbeck
skivnit
JYJY
ph3nom
poppy9009
6pudu5
jothi2lingam
kandem
ksr007
brunodu91
Sad56
samaxen
RuralGalaxy
Click to expand...
Click to collapse
JB-V1.0
Jelly Bean v1.0 Change Log:
Compile with linaro 4.7 2012.9
Triangle Away support.
ADB active while in recovery mode
Bigger RAM limit
USB faster charge (only effect with usb 3 port)
CFQ as default I/O Scheduler
Pegasusq as default I/O Scheduler
mms-ts: Disable touch booster
mali: reduce utilization sampling timeout
Add ARM cpu topology definition
pegasusq: add tweak from galaxsih ICS v3.9 pegasusq tweak
enable arch_power
disable GENTLE_FAIR_SLEEPERS
Proportional Rate Reduction for TCP.
Disable Various Debugging
Custom Voltage / U/V Interface control support (tested with voltage control & setcpu)
Undervolt GPU to -25mv for all frequency
Update wifi driver to 1.28.11.9
cpupower: update the cpu_power according to cpu load (thanks to andreilux to make it work)
for more detail change log goto:
https://github.com/harunjo/galaxsih-kernel-JB-S3
ICS Kernel Version
6.0
beta tester:
deadsoullp
JYJY
jothi2lingam
apeiron6
N78006
samaxen
delgamarco
dladz
mobilevirus
CRBoy47
hieupham
RuralGalaxy
walda
Jekle_Ace
ongchonghian
mariosraptor
sunwee
ph3nom
telenger
thank for your help guys!
Click to expand...
Click to collapse
-Fix arm topology patch
-Fix broken sound with MHL adapter, edit: confirm its fixed with v6.0
-Disable touchbooster mali (disable again, i think (mali: reduce utilization sampling timeout) is enough for smoothness)
-Kernel patch from 3.0.42 to 3.0.43
-Bigger RAM - Changed memory mapped regions’ allocation sizes (by AndreiLux).
-Patch MTP driver to samsung source update 2
revert:
-Modify unicast filter and ignore IPv4 multicast except for mDNS
-mmc: increase read and write timeouts for bad SDHC cards
-modem_if: make modem driver silent
-revert HRTICK to 0
-kernel compression revert back to gzip
-pegasusq tweak back to 3.9 tweak
5.0
beta tester:
JYJY
Milchbeck
jothi2lingam
hieupham
CRBoy47
MuertoKo
marioh
ph3nom
samaxen
6pudu5
apeiron6
poppy9009
N78006
Simow.b
ksr007
Chillz88
mariosraptor
Click to expand...
Click to collapse
thanks for your help guys!
-Modify unicast filter and ignore IPv4 multicast except for mDNS
credit: AndreiLux
-ARM: 7011/1: Add ARM cpu topology definition
The affinity between ARM processors is defined in the MPIDR register.
We can identify which processors are in the same cluster,
and which ones have performance interdependency. We can define the
cpu topology of ARM platform, that is then used by sched_mc and sched_smt.
Signed-off-by: Vincent Guittot
Reviewed-by: Amit Kucheria
Signed-off-by: Russell King
-Alternate wakelock stats labeled as "Discrete" instead of "Exclusive"
credit: Tungstwenty
gokhanmoral:
-modem_if: make modem driver silent
-mmc: increase read and write timeouts for bad SDHC cards
-pegasusq (based on ondemand): cpuidle detection
Signed-off-by: Andrea Arcangeli
ported by: gokhanmoral
-Linaro Compiler update to 2012.18
-disabling printks - hardcore
-sdcard sdhci: Remove Samsung's broken hack
Signed-off-by: Andrew Dodd
-sound Fix debug level
Signed-off-by: Andrew Dodd
-max77686: Fix debug statements
4.0
Thanks to v4.0 Beta Tester:
-ksr007
-ph3nom
-mariosraptor
-hieupham
-MuertoKo
-Jekle_Ace
-apeiron6
-Milchbeck
-Chillz88
-kenzolo
-pidz
-sunwee
-jothi2lingam
-samaxen
-poppy9009
-walda
-amaliapika
-spencer1208
[email protected]
-alerems
Click to expand...
Click to collapse
- Update kernel from 4.0.41 to 4.0.42
- Re-Enable Touchbooster
- Increase USB charging mAh to 800 so you can charge faster via usb3
- voltage control fix, compatible with most of undervolt application - tested with voltage control and setcpu
AndreiLux:
-Disabled the Kies daemon, I see no point in it and it uses up memory uselessly. Obviously Kies won't work any-more, if you want you can start the service yourselves manually.
-silence the touchscreen debug
-Decreased Mali utilization timeout to 100ms down from 1s which improves reaction time on instant GPU loads (Lock screen is best example).
-gokhanmoral:
-Fix media scanning problem with new clockworkmod
-add efs-backup script
-s3cfb: brightness curve mod
dorimanx:
- Shut Modem logs after new modem update.
- arm: smp: Wrap backtrace IPI with irq_enter/exit
This appears to be something that should also be wrapped. Also,
the backtraces experienced may be a cause and not a symptom -
instead of an RCU stall causing backtraces, backtraces
may be causing an RCU stall - which causes more backtraces
and then the system gets mental.
Signed-off-by: Andrew Dodd
-lib/checksum.c: optimize do_csum a bit
Reduce the number of variables modified by the loop in do_csum() by 1,
which seems like a good idea. On Nios II (a RISC CPU with 3-operand
instruction set) it reduces the loop from 7 to 6 instructions, including
the conditional branch.
Signed-off-by: Ian Abbott
Signed-off-by: David S. Miller
-init/main.c: execute lockdep_init as early as possible
This patch removes the lockdep warning[1] on ARM platform.
The warning is caused by printk inside smp_setup_processor_id.
It is safe to do this because lockdep_init doesn't depend on
smp_setup_processor_id, so make printk can be called as early
as possible without lockdep complainment.
Signed-off-by: Ming Lei
Galaxsih ICS kernel Source Code
Galaxsih Jelly Bean Kernel Source
Interesting UV test thread from:
http://forum.xda-developers.com/showthread.php?p=22126846#post22126846
bedalus said:
Miscellaneous
[Q] You claim you cannot increase battery life using UV beyond 2%. Justify yourself!
[A] When the processor is in use (i.e. not asleep or idle) UV does save a tiny amount of power. I tested with the most extreme UV my phone could handle. With a high performance governor, e.g. smartassv2, extreme UV would reduce CPU drain by 13%, or about 7 mA. With a governor that keeps the CPU frequency low, CPU drain would be reduced by about 18%, or 4.6 mA (weighted - see the spreadsheet starting cell H88).
Remember, these savings are limited to the processor, and only when it is active. For most users, this will mean the screen is on. For comparison, the screen on minimum brightness displaying black uses 9mA. On max brightness, displaying white, it uses 690mA. Let us assume some median value, ~350 mA.
A saving of 4.6 mA out of at least 350 mA (screen) plus 20 mA (CPU)
= 1.2%
A saving of 7 mA out of at least 350 mA (screen) plus 50 mA (CPU)
= 1.8%
So, regardless of your choice of governor, even with extreme undervolting, you are not going to be able to increase your battery life by more than 2%.
Click to expand...
Click to collapse
How to Under volting this kernel?
thanks to eric-filth for helping me wrote this guide
GPU undervolting patterns
light: 875 900 950 1000 (this is galaxsih kernel default GPU UnderVolt)
medium: 850 875 925 975
heavy: 825 850 900 925
note: this kernel already have GPU UV light setting (-25mV) by default*
example init.d script for medium (-50mv) GPU UV:
in terminal (or using root explorer) create a file, put the file inside of /system/etc/init.d/*
the file name must have 11xxx file name format to be working
file name example:
111Cpu, 111Gpu, 111Int
Steps:
1.
# touch /system/etc/init.d/11Gpu
# touch /system/etc/init.d/111Cpu
# touch /system/etc/init.d/111Int
2. open the file using root exlorer and edit the empty 11gpuUV file like below
GPU UNDERVOLT:
inside of 111Gpu file for example (-25mV):
Code:
#!/system/bin/sh
echo "850000 875000 925000 975000" > /sys/class/misc/gpu_voltage_control/gpu_control
CPU UNDERVOLT: ( this even more simple if you are using cpu undervolt app (setcpu, system tuner, etc)
inside of 111Cpu file for example (-25mV):
Code:
#!/system/bin/sh
echo "1275 1213 1175 1125 1075 1025 975 950 938 925 925 900 875" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
INTERNAL BUS UNDERVOLT:
inside of 111Int file for example (-25mV):
Code:
#!/system/bin/sh
echo "1025 1025 925 925 875 875 875" > /sys/devices/system/cpu/cpu0/cpufreq/int_mV_table
3. change the file permission
# chmod 744 /system/etc/init.d/111Gpu
#chmod 744 /system/etc/init.d/111Cpu
# chmod 744 /system/etc/init.d/111Int
4. change the init.d folder permission
# chmod -R 755 /system/etc/init.d
4. reboot
5.
recheck below file to confirm the UV value have been commit;
GPU:
/sys/class/misc/gpu_voltage_control/gpu_control
CPU:
/sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
BUS:
/sys/devices/system/cpu/cpu0/cpufreq/int_mV_table
- for troubleshoot init.d process you can read *post init process at /data/user.log after reboot
if you got problem and your devices cannot boot properly, you can delete those file in your init.d folder and start again afterward
how to do that?:
1. power off your phone:
2. connect your phone using usb cable to phone
3. start adb shell
cmd> adb shell
4. su -
5. # rm -rf /system/etc/init.d/*
please be carefull with your uV setting
Enable logcat
cmd> adb shell
#su
#mount -o remount,rw /system
#echo ANDROIDLOGGER >> /system/etc/tweaks.conf
#mount -o remount,ro /system
Reboot your phone and you should have it enabled.[/I]
Welcome m8.
this is an optimized stock kernel for better battery life or did i misunderstand..
Good work. Shall give this a go when I have time cheers.
Sent from my GT-I9300 using Tapatalk 2
zodiaxe66 said:
Welcome m8.
this is an optimized stock kernel for better battery life or did i misunderstand..
Click to expand...
Click to collapse
basicly like that, i build that from samsung i9300 source..apply the tweak to the source and then compile the kernel
Any feedback guys?
Sent from my GT-I9300 using xda app-developers app
benc88 said:
Any feedback guys?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
+1 ... i really need feedback here
I'm in the car otherwise I would try now and give feedback
Skickat från min GT-I9300 via Tapatalk 2
Is faux doing sgs iii kernels?
Sent from my GT-I9300 using Tapatalk 2
I want AOSP "battery" kernel!
Skickat från min GT-I9300 via Tapatalk 2
Running it with Foxhound 1.1 for a couple of hours, seems bugfree for now, pretty smooth (although I think speedmod is a little better on this point). Will see for battery life, no warning to this point.
Thanks for this kernel !
Thanks for this, I'm a fan of kernels that don't attempt to include everything and the kitchen sink.
Suggestions:
Replace the adbd with a patched one by Chainfire to make it run as root. You can get it from https://github.com/simone201/neak-gs3-kernel/tree/master/ramdisk-samsung/sbin or https://github.com/gokhanmoral/ramfs-sgs3/tree/master/sbin
Enable Triangle Away support: https://github.com/gokhanmoral/siyahkernel-sgs3/commit/7afacc67b40d1b441415ce403d99cfbfa6cfc152
Possibly add an option to enable the logcat. Maybe build it as a module and allow a way for it to be loaded early in the ramdisk? I like to use it to diagnose any bad smali edits I may have made and because my live logcat bootscreen doesn't display anything anymore
Thanks it seems very fast and very little battery drain..
Enviado desde mi GT-I9300 usando Tapatalk 2
so how is this compared to phenomenal kernel ?
baste07 said:
Is faux doing sgs iii kernels?
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
No.
box4m said:
I want AOSP "battery" kernel!
Skickat från min GT-I9300 via Tapatalk 2
Click to expand...
Click to collapse
+1
qwerty12 said:
Thanks for this, I'm a fan of kernels that don't attempt to include everything and the kitchen sink.
Suggestions:
Replace the adbd with a patched one by Chainfire to make it run as root. You can get it from https://github.com/simone201/neak-gs3-kernel/tree/master/ramdisk-samsung/sbin or https://github.com/gokhanmoral/ramfs-sgs3/tree/master/sbin
Enable Triangle Away support: https://github.com/gokhanmoral/siyahkernel-sgs3/commit/7afacc67b40d1b441415ce403d99cfbfa6cfc152
Possibly add an option to enable the logcat. Maybe build it as a module and allow a way for it to be loaded early in the ramdisk? I like to use it to diagnose any bad smali edits I may have made and because my live logcat bootscreen doesn't display anything anymore
Click to expand...
Click to collapse
Version 2.1 uploaded
-minor fix
-Triangle away support credit: gokhanmoral & qwerty12 for suggestion
-add adb insecure (thx qwerty12 for suggestion)
-modified post init script
logcat still disable by default,
but you can enable it later
I'm interested to try this, is it similar to the Phenomenal kernel?
Khy50 said:
I'm interested to try this, is it similar to the Phenomenal kernel?
Click to expand...
Click to collapse
Yes, it's with undevolting like phenomenal, but with olty one version. I'm trying this and I'm very happy but it's too early to talk about battery, but it's seems very good
Enviado desde mi GT-I9300 usando Tapatalk 2
any report of battery performance so far?
with v2.1
i got more than 14 hours with not much usage..and my phone battery still have 63%....
My Dhollmen kernel.
Galaxy Tab 2 : Marshmallow - AOSP compatible.
Sources in Git-Hub
Credits for Kernel Team, Google, Samsung, Cyanogenmod and anyone else who has worked on it.
Cpu boot at 1216 MHz.
Gpu boot at 384 MHz.
Undervolt.
Boot with 'pegasusq' as cpufreq governor.
Boot with 'sioplus' as block scheduler.
Boot with 'slub' as allocator.
CPU overclock selectable up to 1520 MHz.
GPU overclock selectable up to 512 MHz.
PowerVR SGX 540 kernel modules blob build [email protected]
Activated ZRAM with LZ4 compression
Tweaked Init process.
Android F2 File system (F2FS) support.
Windows NTFS support.
Windows CIFS support.
Unix/Linux NFS support.
Windows exFAT support.
ISO 9660 support.
Manages /etc/init.d/ and /etc/sysctl.conf.
Init's improvements built in kernel.
I think it does not need further sysctl.conf tweaks.
GENERAL NOTES:
Booting pegasusq because it is very soft with frequency scaling and looks as good compromise between performance and battery saving.
Naturally, each user should choose the one that best suits your needs.
This kernel not use and remove, if any when it installs, /system/lib/hw/power.*.so, as they are redundants here and interfere with CPU's
management frequency, increasing eat CPU cycles.
User can insert boot actions by scripts in /etc/init.d. Here, it is important to establish the order of execution starting with numbers script names,
to run always the latter that has the largest number.
Has been included an interface to the OC of the GPU, using "cat /sys/devices/system/cpu/cpu0/cpufreq/gpu_frequency"' command to view current frequency.
Kernel will stop secundary processor when its performance is not necessary for the functioning of the tablet.
Maybe I can tune a little more, but for now the second processor still remain stopped with low power requirement, even the first reaches 600 MHz.
I have further reduced the working voltage used by the Core, GPU, and CPU frequencies up to 1216 MHz.
I have completely replaced the memcopy & memmove functions code for memory data movement. The new code can be up to 10 times faster.
I have lately added several optimizations to improve performance and reduce overhead.
Download Latest releases
MARSHMALLOW VERSION CHANGELOG:
2016.05.16
Possibility of loading several roms.
Removed zram and swap.
Rebuild init.
Several changes designed to increase performance.
Several changes designed to reduce battery consumption.
2016.03.20
Adding dynamic tiler allocation.
2016.03.19
In line with Cyanogenmod at date.
Added the majority of previous improvements.
CHANGES OC OPTIONS BY HAND:
Code:
# GPUFREQ --> X = 1 (384 MHz) || 0 (307 MHz) || 2 (512 MHz)
echo 'X' > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
# CPUFREQ --> X = 1216000 || 1008000 || 1360000 || 1420000 || 1460000
echo 'X' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# SCHEDULER --> X = row || cfq || sioplus
echo 'X' > /sys/block/mmcblk0/queue/scheduler
# GOVERNOR --> X = pegasusq || interactive || ondemand || lulzactive
echo 'X' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
WARRANTY: You agree that this product is provided "as is" without any warranty, either expressed or implied, on its operation.
DISCLAIMER: You assumes at your SOLE RESPONSIBILITY and RISK all results produced by the "software" and/or instructions in this thread.
XDA:DevDB Information
KERNEL Dhollmen - AOSP - Espresso Tab2 , Kernel for the Samsung Galaxy Tab 2
Contributors
tuxafgmur
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 20160516
Stable Release Date: 2016-05-16
Created 2014-06-11
Last Updated 2016-05-16
.
This post refers only to previous 2016.03.19 versions
Cpu boot at 1216 MHz.
Gpu boot at 384 MHz.
Undervolt.
Boot with 'pegasusq' as cpufreq governor.
Boot with 'sio' as block scheduler.
Boot with 'slqb' as allocator.
CPU overclock selectable up to 1460 MHz.
GPU overclock selectable up to 512 MHz.
PowerVR SGX 540 kernel modules blob build [email protected]
Last ducati-m3.bin firmware supported.
Without debug code.
SElinux Support.
SNAPPY and LZ4 compression libs for SWAP soported.
Activated ZRAM with LZ4 compression
Tweaked Init process.
Android F2 File system (F2FS) support.
Union File system (AUFS) support.
Windows NTFS support.
Windows CIFS support.
Unix/Linux NFS support.
Windows exFAT support.
ISO 9660 support.
UDF DirectCD and CDRW/DVD support.
Apple HSFS and HSFS+ R/W support.
DIrectories /mnt/mntpoint1, /mnt/mntpoint2 and /mnt/mntpoint3 suitables for your needs.
Battery images replaced.
Manages /etc/init.d/ and /etc/sysctl.conf.
Init's improvements built in kernel.
I think it does not need further sysctl.conf tweaks.
GENERAL NOTES:
Booting pegasusq because it is very soft with frequency scaling and looks as good compromise between performance and battery saving.
Naturally, each user should choose the one that best suits your needs.
This kernel not use and remove, if any when it installs, /system/lib/hw/power.*.so, as they are redundants here and interfere with CPU's
management frequency, increasing eat CPU cycles.
User can insert boot actions by scripts in /etc/init.d. Here, it is important to establish the order of execution starting with numbers script names,
to run always the latter that has the largest number.
With this kernel, the user not need a separate script to run at the end of the boot.
Has been included an interface to the OC of the GPU, using "cat /sys/devices/system/cpu/cpu0/cpufreq/gpu_frequency"' command to view current frequency.
Kernel will stop secundary processor when its performance is not necessary for the functioning of the tablet.
Maybe I can tune a little more, but for now the second processor still remain stopped with low power requirement, even the first reaches 600 MHz.
I have further reduced the working voltage used by the Core, GPU, and CPU frequencies up to 1216 MHz.
I have completely replaced the memcopy & memmove functions code for memory data movement. The new code can be up to 10 times faster.
I have lately added several optimizations to improve performance and reduce overhead.
DhollmenL : Lollipop versions
DhollmenK : Kit-Kat versions
If your Rom have problems after installing kernel, you must install the blobs file.
Download Latest releases
LOLLIPOP VERSION CHANGELOG:
2015.06.28
Included 'lulzactive' governor.
Included Cgroups as requested by Lollipop
A lot of little optimizations.
2015.02.15
Reverted MAG2GA patches
2015.02.13
First LP version
KIT-KAT VERSION CHANGELOG:
2015.06.24
Restored 'lulzactive' governor.
A lot of little optimizations.
2015.01.17
Updated F2Fs driver.
Last Boeffla codec.
Restored Gpu 512MHz overclock.
Google 4.8 toolchain compilation.
Many code optimizations.
2014.10.19
Solves encrypted /data partition mount.
New Fstrim management.
Mokee rom support.
Linaro 4.8.3 compilation.
Several code optimizations.
2014.09.18
Several code optimizations.
2014.08.17
Linaro 4.9 compilation.
Secure futex uptream patches.
Rework F2Fs files system.
Updates exFat file system.
Sio tweak.
VFS, sync, writeback and readahead changes.
Introducing Boeffla codec.
Changes init script for F2Fs support.
A few more improvements.
2014.06.13
Removed blobs from 10th installation file.
New independent blobs file.
2014.06.10
More reduced voltage to 1216 MHz.
More reduced voltage 1460 MHz as proposed by @Shepguessed.
Included blob files.
Included camera's 4.4.3 @Tsjoklat fix.
Multiple optimizations.
2014.04.12
Restored SELinux permissive behavior.
MHL to Hdmi video support.
Adding AUFS support.
Multiple optimizations.
2014.03.20
Strongliy reworked Kit-Kat's roms battery drain issue.
Reworked frequencies governor.
Adding F2Fs support. You still need Rom and Recovery support for this.
Unified my prev JB and KK releases.
Code slightly reduced.
CHANGES OC OPTIONS BY HAND:
Code:
# GPUFREQ --> X = 1 (384 MHz) || 0 (307 MHz) || 2 (512 MHz)
echo 'X' > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
# CPUFREQ --> X = 1216000 || 1008000 || 1360000 || 1420000 || 1460000
echo 'X' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# SCHEDULER --> X = row || cfq || sio
echo 'X' > /sys/block/mmcblk0/queue/scheduler
# GOVERNOR --> X = pegasusq || interactive || ondemand || lulzactive
echo 'X' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Latest for JB-4.3 Roms --> View attachment 2351488
Latest for CM-10.1 Rom --> View attachment 2133681
WARRANTY: You agree that this product is provided "as is" without any warranty, either expressed or implied, on its operation.
DISCLAIMER: You assumes at your SOLE RESPONSIBILITY and RISK all results produced by the "software" and/or instructions in this thread.
Re: [KERNEL] DhollmenCM for P51xx Cyanogenmod 10.1
Thanks man for this... Work freaking awsome love it
Im running blackbean 8
Sent from my GT-P5113 using Tapatalk 2
Big thanks for this, downloading and uploading
Can anyone confirm if this is compatible with BAKED Blackbean 8.0? Running P5100 here.
panda00 said:
Can anyone confirm if this is compatible with BAKED Blackbean 8.0? Running P5100 here.
Click to expand...
Click to collapse
I think so, but you must test by yourself.
No problem if you backup your system first. :angel:
Tab runs great with this kernel (CM 10.1 latest nightly). Thank you op, we need a kernel like this.
Snappy.
tested cm 10.1 M2 your kernel. antutu say to me 7918 point thanks.
Re: [KERNEL 3.0.31] DhollmenCM for P51xx Cyanogenmod 10.1
Thanks!
Verstuurd van mijn GT-P5100 met Tapatalk
I only have one word for you: PERFECTO!!!
thank you!
Hai tuxafgmur, mind to review my github commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1 and https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk ?
ketut.kumajaya said:
Hai tuxafgmur, mind to review my github commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1 and https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk ?
Click to expand...
Click to collapse
I created muy github acount and master repo yesterday morning, and i still can't upload my sources.
I'm very busy now, but I have interest in reviewing yours and yor great work.
Thank you very much four your kind information.
Regards.
tuxafgmur said:
These frequencies, it does not really represent a true overclock, because the CPU is designed to work normally at 1008 and 1200 MHz.
Samsung stays at the bottom of the table and we opted for the top.
Exactly the same applies to the GPU.
Click to expand...
Click to collapse
Can you make for us another version that is true overclock, that means we can select higher frequencies such as 1350, 1400 for CPU and 512 for GPU
Thanks for your great kernel. My device is flying with it. :good:
muoino said:
Can you make for us another version that is true overclock, that means we can select higher frequencies such as 1350, 1400 for CPU and 512 for GPU
Thanks for your great kernel. My device is flying with it. :good:
Click to expand...
Click to collapse
Yes, I can.
First post, please
I don't test this kernel version. If you install this, send me feedback, please.
DhollmenCM-Kernel_20130310.zip with latest CM10.1 seems a bit laggy? CPU is running at 1200, but don't know about GPU clock, was it lowered from previus kernell?
same here. With 1350 MHz. New HOT OC kernel same.
About laggy:
I don't think GPU.
I think in freq governor. I try to reduce battery comsuption.
1) Can you test with antutu and compare with first post image ?
2) Can you do: "echo lulzactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor" and test with it?
Thanks in advance
Antutu gets stuck at initializing screen and then my tab reboots
If I change the governor to lulzactive, it's still laggy.
kbal said:
DhollmenCM-Kernel_20130310.zip with latest CM10.1 seems a bit laggy? CPU is running at 1200, but don't know about GPU clock, was it lowered from previus kernell?
Click to expand...
Click to collapse
Same problem old kernel more smooth, stable and no lag.
---------- Post added at 03:46 PM ---------- Previous post was at 03:39 PM ----------
antutu not working on new kernel freezes my tablet i go back your old kernel now.
aquarist said:
Same problem old kernel more smooth, stable and no lag.
---------- Post added at 03:46 PM ---------- Previous post was at 03:39 PM ----------
antutu not working on new kernel freezes my tablet i go back your old kernel now.
Click to expand...
Click to collapse
Version removed.
Working to resolve the issue.
My Dhollmen kernel.
Galaxy Tab 2 : Marshmallow - AOSP compatible.
Sources in Git-Hub
Credits for Kernel Team, Google, Samsung, Cyanogenmod and anyone else who has worked on it.
Cpu boot at 1216 MHz.
Gpu boot at 384 MHz.
Undervolt.
Boot with 'pegasusq' as cpufreq governor.
Boot with 'sioplus' as block scheduler.
Boot with 'slub' as allocator.
CPU overclock selectable up to 1520 MHz.
GPU overclock selectable up to 512 MHz.
PowerVR SGX 540 kernel modules blob build [email protected]
Activated ZRAM with LZ4 compression
Tweaked Init process.
Android F2 File system (F2FS) support.
Windows NTFS support.
Windows CIFS support.
Unix/Linux NFS support.
Windows exFAT support.
ISO 9660 support.
Manages /etc/init.d/ and /etc/sysctl.conf.
Init's improvements built in kernel.
I think it does not need further sysctl.conf tweaks.
GENERAL NOTES:
Booting pegasusq because it is very soft with frequency scaling and looks as good compromise between performance and battery saving.
Naturally, each user should choose the one that best suits your needs.
This kernel not use and remove, if any when it installs, /system/lib/hw/power.*.so, as they are redundants here and interfere with CPU's
management frequency, increasing eat CPU cycles.
User can insert boot actions by scripts in /etc/init.d. Here, it is important to establish the order of execution starting with numbers script names,
to run always the latter that has the largest number.
Has been included an interface to the OC of the GPU, using "cat /sys/devices/system/cpu/cpu0/cpufreq/gpu_frequency"' command to view current frequency.
Kernel will stop secundary processor when its performance is not necessary for the functioning of the tablet.
Maybe I can tune a little more, but for now the second processor still remain stopped with low power requirement, even the first reaches 600 MHz.
I have further reduced the working voltage used by the Core, GPU, and CPU frequencies up to 1216 MHz.
I have completely replaced the memcopy & memmove functions code for memory data movement. The new code can be up to 10 times faster.
I have lately added several optimizations to improve performance and reduce overhead.
Download Latest releases
MARSHMALLOW VERSION CHANGELOG:
2016.05.16
Possibility of loading several roms.
Removed zram and swap.
Rebuild init.
Several changes designed to increase performance.
Several changes designed to reduce battery consumption.
2016.03.20
Adding dynamic tiler allocation.
2016.03.19
In line with Cyanogenmod at date.
Added the majority of previous improvements.
CHANGES OC OPTIONS BY HAND:
Code:
# GPUFREQ --> X = 1 (384 MHz) || 0 (307 MHz) || 2 (512 MHz)
echo 'X' > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
# CPUFREQ --> X = 1216000 || 1008000 || 1360000 || 1420000 || 1460000
echo 'X' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# SCHEDULER --> X = row || cfq || sioplus
echo 'X' > /sys/block/mmcblk0/queue/scheduler
# GOVERNOR --> X = pegasusq || interactive || ondemand || lulzactive
echo 'X' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
WARRANTY: You agree that this product is provided "as is" without any warranty, either expressed or implied, on its operation.
DISCLAIMER: You assumes at your SOLE RESPONSIBILITY and RISK all results produced by the "software" and/or instructions in this thread.
XDA:DevDB Information
KERNEL Dhollmen - AOSP - Espresso Tab2, Kernel for the Samsung Galaxy Tab 2
Contributors
tuxafgmur
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 2016.05.16
Stable Release Date: 2016-05-16
Created 2014-07-14
Last Updated 2016-05-16
.
This post refers only to previous 2016.03.19 versions
Cpu boot at 1200 MHz.
Gpu boot at 384 MHz.
Undervolt.
Boot with 'pegasusq' as cpufreq governor.
Boot with 'sio' as block scheduler.
Boot with 'slqb' as allocator.
CPU overclock selectable up to 1480 MHz.
GPU overclock selectable up to 512 MHz.
PowerVR SGX 540 kernel modules blob build [email protected]
Last ducati-m3.bin firmware supported.
Without debug code.
SElinux Support.
SNAPPY and LZ4 compression libs for SWAP soported.
Activated ZRAM with LZ4 compression
Tweaked Init process.
Android F2 File system (F2FS) support.
Union file system (AUFS) support.
Windows NTFS support
Windows CIFS support.
Unix/Linux NFS support.
Windows exFAT support.
ISO 9660 support.
UDF DirectCD and CDRW/DVD support.
Apple HSFS and HSFS+ R/W support.
DIrectories /mnt/mntpoint1, /mnt/mntpoint2 and /mnt/mntpoint3 suitables for your needs.
Battery images replaced.
Manages /etc/init.d/ and /etc/sysctl.conf.
Init's improvements built in kernel.
I think it does not need further sysctl.conf tweaks.
GENERAL NOTES:
Booting pegasusq because it is very soft with frequency scaling and looks as good compromise between performance and battery saving.
Naturally, each user should choose the one that best suits your needs.
This kernel not use and remove, if any when it installs, /system/lib/hw/power.*.so, as they are redundants here and interfere with CPU's
management frequency, increasing eat CPU cycles.
User can insert boot actions by scripts in /etc/init.d. Here, it is important to establish the order of execution starting with numbers script names,
to run always the latter that has the largest number.
With this kernel, the user not need a separate script to run at the end of the boot.
Has been included an interface to the OC of the GPU, using "cat /sys/devices/system/cpu/cpu0/cpufreq/gpu_frequency"' command to view current frequency.
Kernel will stop secundary processor when its performance is not necessary for the functioning of the tablet.
Maybe I can tune a little more, but for now the second processor still remain stopped with low power requirement, even the first reaches 600 MHz.
I have further reduced the working voltage used by the Core, GPU, and CPU frequencies up to 1200 MHz.
I have completely replaced the memcopy & memmove functions code for memory data movement. The new code can be up to 10 times faster.
I have lately added several optimizations to improve performance and reduce overhead.
DhollmenL : Lollipop versions
DhollmenK : Kit-Kat versions
If your Rom have problems after installing kernel, you must install the blobs file.
Download Latest releases
LOLLIPOP VERSION CHANGELOG:
2015.06.30
Included 'lulzactive' governor.
Included Cgroups as requested by Lollipop
A lot of little optimizations.
2015.02.15
Reverted MAG2GA patches
2015.02.13
First LP version
KIT-KAT VERSION CHANGELOG:
2015.06.24
Restored 'lulzactive' governor.
A lot of little optimizations.
2015.01.17
Updated F2Fs driver.
Last Boeffla codec.
Restored Gpu 512MHz overclock.
Google 4.8 toolchain compilation.
Many code optimizations.
2014.10.19
Solves encrypted /data partition mount.
New Fstrim management.
Mokee rom support.
Linaro 4.8.3 compilation.
Several code optimizations.
2014.09.18
Several code optimizations.
2014.08.19
Camera blob.
2014.08.17
Linaro 4.9 compilation.
Secure futex uptream patches.
Rework F2Fs files system.
Updates exFat file system.
Sio tweak.
VFS, sync, writeback and readahead changes.
Introducing Boeffla codec.
Changes init script for F2Fs support.
A few more improvements.
2014.07.14
More reduced voltages
Included camera's patch (If needed).
Multiple optimizations.
2014.04.12
Restored SELinux permissive behavior.
Adding AUFS support.
Multiple optimizations.
2014.04.01
Reworked frequencies governor.
Adding F2Fs support. You still need Rom and Recovery support for this.
Unified my prev JB and KK releases.
Code slightly reduced.
CHANGES OC OPTIONS BY HAND:
Code:
# GPUFREQ --> X = 1 (384 MHz) || 0 (307 MHz) || 2 (512 MHz)
echo 'X' > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
# CPUFREQ --> X = 1216000 || 1008000 || 1360000 || 1420000 || 1460000
echo 'X' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# SCHEDULER --> X = row || cfq || sio
echo 'X' > /sys/block/mmcblk0/queue/scheduler
# GOVERNOR --> X = pegasusq || interactive || ondemand || lulzactive
echo 'X' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Latest for JB-4.3 Roms --> View attachment 2351512
Latest for CM-10.1 Rom --> View attachment 2133759
NOTE: I not own a 7-inch model, so I can't try it personally. Above is reference of my P51XX version.
WARRANTY: You agree that this product is provided "as is" without any warranty, either expressed or implied, on its operation.
DISCLAIMER: You assumes at your SOLE RESPONSIBILITY and RISK all results produced by the "software" and/or instructions in this thread.
Good to see new options will give it a try maybe tomorrow
Re: [ KERNEL ] DhollmenCM for P31xx Cyanogenmod 10.1
It would be good for gpu to max To Reduce stress on cpu and cpu lock at 1420,
Stablest frequency of our tab 2 p31XX.
Sent from my GT-P3100 using Tapatalk HD
Re: [ KERNEL ] DhollmenCM for P31xx Cyanogenmod 10.1
zeuscluts said:
It would be good for gpu to max To Reduce stress on cpu and cpu lock at 1420,
Stablest frequency of our tab 2 p31XX.
Sent from my GT-P3100 using Tapatalk HD
Click to expand...
Click to collapse
For redusing cpu load ....we have to do some.....xxxxxx work.... (means many work.....)
This kernel has ultimate stability. ......good....
But my interest is some where roming.....
I want 2.....
Am not happy untill and unless my Gtab2 is 2....
Confusing dont read. .....
★If You Feel Am Helping Raise My Thanks Meter To Infinity By Hitting Thanks Button★
Re: [ KERNEL ] DhollmenCM for P31xx Cyanogenmod 10.1
Has someone tried in Stock?
Enviado desde mi GT-P3110 usando Tapatalk 2
Re: [ KERNEL ] DhollmenCM for P31xx Cyanogenmod 10.1
moliverac8 said:
Has someone tried in Stock?
Enviado desde mi GT-P3110 usando Tapatalk 2
Click to expand...
Click to collapse
Dear, its clearly mention for DhollmenCM for P31xx Cyanogenmod 10.1
Sent from my GT-P3100 using Tapatalk HD
Re: [ KERNEL ] DhollmenCM for P31xx Cyanogenmod 10.1
zeuscluts said:
Dear, its clearly mention for DhollmenCM for P31xx Cyanogenmod 10.1
Sent from my GT-P3100 using Tapatalk HD
Click to expand...
Click to collapse
I know but sometimes works anyway.
Enviado desde mi GT-P3110 usando Tapatalk 2
moliverac8 said:
I know but sometimes works anyway.
Enviado desde mi GT-P3110 usando Tapatalk 2
Click to expand...
Click to collapse
I don't test ... for now.
Hello, may i know how to OC the GPU?
I jus changed the number from 1 to 2. But when i reopen the file it still shows 1.
Re: [KERNEL - New Unified Version] DhollmenCM for P31xx Cyanogenmod 10.1
adishakthi said:
For redusing cpu load ....we have to do some.....xxxxxx work.... (means many work.....)
This kernel has ultimate stability. ......good....
But my interest is some where roming.....
I want 2.....
Am not happy untill and unless my Gtab2 is 2....
Confusing dont read. .....
★If You Feel Am Helping Raise My Thanks Meter To Infinity By Hitting Thanks Button★
Click to expand...
Click to collapse
Useless crap not needed in every thread
Sent on my GT-P3100 using xda premium.
hwwr said:
Hello, may i know how to OC the GPU?
I jus changed the number from 1 to 2. But when i reopen the file it still shows 1.
Click to expand...
Click to collapse
I've test now.
It seems unification breaks this option, that I've nver test.
I'll modify my code for next version.
Thanks.
tuxafgmur said:
I've test now.
It seems unification breaks this option, that I've nver test.
I'll modify my code for next version.
Thanks.
Click to expand...
Click to collapse
Cant wait to see the OC of the GPU to the max.
Currently only ur kernel has that high support.
hwwr said:
Cant wait to see the OC of the GPU to the max.
Currently only ur kernel has that high support.
Click to expand...
Click to collapse
I've uploaded new revision :good:
hwwr said:
Cant wait to see the OC of the GPU to the max.
Currently only ur kernel has that high support.
Click to expand...
Click to collapse
All imoseyon, cmenard, and blackhawk derivative has it
ketut.kumajaya said:
All imoseyon, cmenard, and blackhawk derivative has it
Click to expand...
Click to collapse
Hi Ketut. Nice to read you here in my thread
tuxafgmur said:
Hi Ketut. Nice to read you here in my thread
Click to expand...
Click to collapse
A good thing you dare come to my cage
ketut.kumajaya said:
A good thing you dare come to my cage
Click to expand...
Click to collapse
R: [KERNEL - New Unified Revision] DhollmenCM for P31xx Cyanogenmod 10.1
This kernel works really great at 1480 on my P3110.
Fast and stable!!
Thank you for your work!!
New revision 1 available for download :good:
These kernels should work on every stock ICS LG rom or custom rom based on LG ICS rom.
Civato kernels build with V30B LG source & compiled on google 4.4.3 toolchain.
Thanks to :
WKPARK patchesRamHack and first OC patch
Also want to thank pengus77 , ezterry, godmachine81 , Thor2002ro, Faux123,chad0989 , Pidozz
NOTE:
I'm not a DEV and not pretending to be one, I'm a android enthusiast.
I would like to thank all XDA members that are helpful.
I build and mod stuff for my personal needs and then I share them.
Do I want something in return? NO.
You don't like it, no problem, there are enough good DEV's with there kernel to help you along.
So on request I started a separate thread for this kernel , it started with my rom and the need for a good custom kernel.
Click to expand...
Click to collapse
I don't provide any guarantee or a lawer if your phone explode and you get accused and charged for a terrorist act.
To be clear , the kernel got the POSSIBILITY to OC and tweak , if you don't do anything it runs at stock settings.
Meaning = MAX speed 1000MHz , Noop scheduler , interactive governor= LG default settings.
CivZ_SkyWalker_RF2.5rm
Sithlord in 3 different versions.
Ramhack or no ramhack
usb FastCharge
Compiled with Optimized flags-O3/-O2
-OC up to 1.5GHz , UV/OV , default boot up speed is 1.0GHz
-Minimum UV 650mV , Maximum OV 1400mV
Best CPU control app when you want to UV is free for XDA members SETCPU , download 2.24 or buy it, SUPPORT the devs! (it allows you to type in voltage changes and not only slide), Remember only steps of 10mV are real values , if you apply a step of 25mV it will actually be 20mV. So use setcpu to type in voltage steps of 10mV , 20mV , 30mV, ...............
-GPU 3D & 2D ( scales from 300 - 425MHz)
(stock is 300)
-Terminal kernel control commands
(Led light , FSYNC control , ZRam , Modules, SWAP increase)
-USB FastCharge (disabled at default)
-Available RamHack :No ramhack /24mb / 32mb
- Extra zRam 96Mb(disabled by default)
-Governors:
Powersaver
PERFORMANCE
USERSPACE
ONDEMAND
INTERACTIVE in dynamic mode (default)
CONSERVATIVE
LulzActive
(LulzActive tegrak tweak app included)
LionHeart
-Shedulers
NOOP(default)
DEADLINE
CFQ
SIO
ROW
BFQ-v5
Zen
VR
-Led control thanks to pengus77 (Max at default)
-Dynamic FSYNC @ Faux123 & Pengus77 (Disabled at default)
-Extra Modules loadable/unloadable on the fly
-Voltages / Frequencies:
NO 5mV steps as they are not supported by the LG regulator (Thanks Pengus77 for the heads-up)
750mV(216MHz) ; 780mV(312MHz) ; 800mV(456MHz) ; 850mV(608MHz) ; 900mV(760MHz); 920mV(816MHz) ; 950mV(912MHz) ; 1000mV(1000MHz boot up speed) ; 1050mV(1100MHz) 1100mV( 1200MHz); 1150mV(1300MHz); 1200mV(1408MHz) ; 1300mV(1504MHz)
Kernel control options to use with Terminal: (Settings are applied immediately and stick even after reboot now)
For a list of the commands on your phone (in case you forgot)
Type in terminal
su(enter)civz(enter)
Dynamic FSYNC control: (disabled by default)
Terminal command:
su (enter) df_on (enter) = This will enable Dynamic FSYNC (setting are applied immediately and sticks after reboot)
su (enter) df_off (enter) = This will disable Dynamic FSYNC (setting are applied immediately and sticks after reboot)
Led Brightness control: (Maximum brightness by default)
Terminal command:
su (enter) ledmin (enter) = This will set led at minimum brightness (setting are applied immediately and sticks after reboot)
su (enter) ledmed (enter) = This will set led at medium brightness (setting are applied immediately and sticks after reboot)
su (enter) ledmax (enter) = This will set led at maximum brightness (setting are applied immediately and sticks after reboot)
Load/unload Extra Modules : (Modules are unloaded by default)
(Cifs; hfs; hfs+; md4; nls_utf8; sha256; sha512)
Terminal command:
su (enter) m_load (enter) = This will load the extra modules (setting are applied immediately and sticks after reboot)
su (enter) m_unload (enter) = This will unload the extra modules (setting are applied immediately and sticks after reboot)
Enable/Disable EXTRA ZRam96MB: (Disabled by default)
Terminal command:
su (enter) zram_on (enter) = This will enable ZRam96MB (Reboot is needed to apply changes and sticks after reboot)
su (enter) zram_off (enter) = This will disable ZRam96MB (Reboot is needed to apply changes and sticks after reboot)
Enable/Disable LG 131MB SWAP or 260MB SWAP: (131MB is LG default)
Terminal command:
su (enter) lg_swap_of (enter) = This will disable LG swap (Reboot is needed to apply changes and sticks after reboot)
su (enter) lg_swap130_on (enter) = This will enable LG 130MB swap (Reboot is needed to apply changes and sticks after reboot)
su(enter)lg_swap260_on(enter) = This will enable LG 260MB swap (Reboot is needed to apply changes and sticks after reboot)
Note on LG swap: The 131Mb is default of LG
LG got this enabled in the stock LG rom and it uses the dev/block/mmcblk0p4 (unused partition) for it so not the same as ZRam that uses /dev/block/zram0 file. The LG Swap partition is enabled by default , I just add this command so if a user don't want to use the LG swap it can be done now with a single command.
Change system swappines value: (Android default is 60)
(setting are applied immediately and sticks after reboot)
Terminal command:
su(enter)swappines_0(enter) = set swappines at 0 = system waits very long to swap , Kills tasks very quick
su(enter)swappines_20(enter) = set swappines at 20 = Performance setting for gaming
su(enter)swappines_40(enter) = set swappines at 40 = Performance setting and some multitasking
su(enter)swappines_60(enter) = set swappines at 60 = Androids default , balanced setting
su(enter)swappines_80(enter) = set swappines at 80 = Aimed for multitasking/Balanced
su(enter)swappines_100(enter) = set swappines at 100 = Aimed for extreme multitasking , NOT GAMING
Update GPS lto
(this is done automatically with a init.d script , so in case it failed, here a way to do this manually)
Terminal command:
su (enter) gps_update (enter) = This will update gps lto file , if the file is not older then 5 days it won' t update.
Change system Fatsdormancy setting:
(setting are applied immediately and sticks after reboot)
Terminal command:
su(enter)fastdormancy_on(enter)=enable Fastdormancy = android default
su(enter)fastdormancy_off(enter)=disable Fastdormancy
Note about fastcharge option in kernel:
It is OFF at default, user needs to enable it.
Use at own risk, it is meant to use on car/plain chargers, don't know the effect in the long term.
And I don't know the effect when ussed on a PC usb connection.
The "FastCharge" app from playstore is installed in data, use it to toggle ON/OFF.
Or use the following terminal commands:
To enable it = echo 1 > /sys/kernel/fast_charge/force_fast_charge
To disable it= echo 0 > /sys/kernel/fast_charge/force_fast_charge
If you use fastcharge on a pc, usb will not be mounted and no data can be received or send.
Based on the work of chad0989 , Pidozz and Pengus77.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
LG-SU660-VERSIONS
CivZ_SkyWalker_RF2.5rm-SU660
CivZ_SkyWalker_RF2.5rm_24RH-SU660
CivZ_SkyWalker_RF2.5rm_32RH-SU660
Side note on USB BSOD (screen off and pluging in usb resulting in BSOD)
I noticed that with enabled Dynamic FSYNC or a to high OC it can still occur.
So in that case please turn on screen before plugging in USB.
Click to expand...
Click to collapse
Changelog:
[New in RF1.3-Cleaned out the kernel source
-Powersaver governor activated
-Optimized deadline scheduler
-Nvidia USB plugin BSOD fix
New in RF1.4:
-Added BFQ-v5r1 scheduler
@ iBluemind
(More info see Q&A)
-More versions.
New in RF1.5:
-Fix for governor switching
(coming from hotplug to a other governor made one core stuck in sleep state , resulting in bad performance and instability).
-3 New governors: "Aggressive" , "Gallimaufry", "Sakuractive".
-Most governors optimized.
(reverted BFQ to V5 version, performance is smoother I think)
-New "Zen" scheduler and most schedulers optimized
-Reduced android logger time.
-Increased readahead (1024kb instead of the default 128kb)
-Included mmc_cap hard brick fix. (Don't know if it is needed on this phone but can't hurt, a lot of samsung phones died this way when wiping data in recovery)
-Controle led brightness
ledmin ; ledmed; ledmax
NEW RF1.5_FC edition
Added USB Fast Charge in this edition.
8-Feb-2013:
RF1.6:
-Only compiled on -03 CF flags and with FastCharge option.
-GPU 3D clock up to 400MHz
(Before it was 350 where stock is 300)
-Patch for EXt4 error.
-CPU Freq lock off
-Reverted deadline scheduler
-Ramdisk got back the old settings for better battery life when not OC'd.
-216 and 312 MHz default voltage dropped with 25mV.
-Ramp-up speed on interactive back to 80 , you can change this in setcpu.
10-Feb-2013
RF1.7:
-Max CPU OC is now 1.5GHz
-New Lower default Voltage table:
750mV(216MHz) ; 775mV(312MHz) ; 800mV(456MHz) ; 850mV(608MHz) ; 900mV(760MHz); 925mV(816MHz) ; 950mV(912MHz) ; 975mV(1000MHz) ; 1050mV(1100MHz) 1125mV( 1200MHz) ; 1150mV( 1248MHz) ;1200mV(1300MHz) 1250mV(1352MHz) ; 1275mV(1404MHz) ; 1300mV( 1456MHz) ; 1325mV(1500MHz)
-Voltage settings changed in tegra2_dvfs.c so the 1.5GHz is stable.
-GPU 2D clock OC'd up to 400MHz
(stock is 300)
-Secondary clock epp & mpe OC'd to 350MHz
(stock is 300)
-ARCH power enabled
12-Feb-2013:
RF1.8 released
Update for stability reason that some users experienced.
Thanks to all the testers and there feedback.
-2D & 3D clock decreased back to 350MHz OC
(this is the RF1.4 setting as this is the best for all users)
Performance gain is not enough to justified to OC to 400MHz.
The 400MHz version will not be released public as it is not good for most users, please don't ask for it.
-Secondary mpe clock back to stock for the stability reason.
-RATE_LIMIT of 3D back to stock for the stability reason.
13-Feb-2013:
RF1.9
-Bug fix for Reboot /shutdown freeze when OC'd.
-Voltage table updated.
-Lower voltage for 1500 and 1456 MHz
Minimum UV voltage is now 675mV
-3D GPU 400MHz OC.
16-Feb-2013:
RX2.0
New Voltage table for higher stability.
New CPU max speed 1.544GHz.
New GPU 2D clock of 400MHz.
New terminal kernel commands.
Compiled with new flags (-O2 with some parts of -O3 flags to reduce code size).
Updated voltage table to gain stability when OC'd.
Dynamic FSYNC @ Faux123 integrated (Disabled at default)
Kernell-HZ increased to 256HZ (stock is 100) for better performance and smoothness.
User HZ increased to 200HZ (stock is 100) for smoothness
Support for NTFS
Support for NFS 3/4
HFS & HFS+ as modules
CIFS as module
md4 as module
sha512 as module
utf8 as module.
16-Feb-2013:
RX2.0_b released
Fix for the terminal commands error.
21-Feb-2013:
RX2.1 Released
Reverted User and Kenrel HZ to stock for stability.
Reverted back to -O3 custom flags
New terminal commands for ZRam and Extra modules
USB OTG (on the go) enabled (testing)
22-Feb-2013:
RX2.2 released:
Changed some custom flags for decrease of code size.
Reverted OTG setting (not working and causing problems)
Shed_Features back to stock setting (causing USB pluggin BSOD)
New Terminal command 'civz"
I hope this is a 100% rock solid stable version and I'm truly sorry for the many releases the last few days.
I wish to bring a stable kernel so some features are reverted as wow factor is not what I look for.01-Mar-2013:
CivZ_SithLord_再见 released
Main goal 100% stable kernel with good battery life, that is why the following changes are applied:
Forced governor linked patch (Make sure both cpu's run at the same governor, even with "setcpu & antutu") thanks Ezterry.
Max OC 1500MHz with lower voltage table (see in kernel info) , this to reduce battery consumption.
Removed a bunch of governors as they caused problems in some situations (so it seemed), see kernel ifo for what is included.
LulzActive Governor (with app) , tweaked by me to be less aggressive.
02-Mar-2013:
CivZ_SithLord_再见_r2 released
Reverted voltage table to RX2.2 release as some users had problems on max OC with lower rail voltages.
I can UV with -50mV on all frequencies but that is all up to the quality of your tegra2 cpu.07-Mar-2013:
CivZ_SkyWalker_RF1.0 released
New name because the OC code totaly changed compared to SithLord.
Totally new OC code with new frequencies and very low default voltages.(Thanks to my friend ezterry)
Max = Min frequency really fixed (now it won't be stuck at 750MHz when setting max frequency below 760MHz and not just showing the value but actually applying it so now you can set screen-off max at example: 312MHz in a profile with a cpu app).
Dynamic MODE enable on the interactive governor.
Min Max cpu frequency code changed and editable in defconfig before compiling kernel(Thanks to my friend ezterry)
Compiling optimizations flags changed (again thanks to my friend ezterry)
LulzActive governor balanced settings with max screen-off frequency of 608MHz
I would like to thank all the beta testers and I hope the result is up to your expectations!
08-Mar-2013:
CivZ_SkyWalker_RF1.1 released
More aggressive lulzactive governor settings on user request
New terminal command for LG 131MB swap
New terminal command for manual updating GPS lto file
Also a SU660 version available
96ZRam disabled by default from now on (not needed in my opinion, swap already got 131Mb on unused partition, but it is still available as a option)
10-Mar-2013:
CivZ_SkyWalker_RF1.2 released
New Max OC speed of 1544MHz
2D GPU back to 400MHz OC
OC code updated
New Terminal command to increase LG SWAP to 260MB
Updated FSYNC with latest Pengus77 release
Enabled ARCH-Power
SU660 24RH version available
"civz" terminal command updated with latest commands
13-Mar-2013:
CivZ_SkyWalker_RF2.0 released
Reverted MAX OC to 1504MHz (this way I could drop rail voltages so it will stay cooler, settings of RF1.0)
New Voltage table (no 5mV steps as pengus77 mentioned the regulator doesn't except 5mV steps)
Real min voltage is now 650mV (again thanks for pengus77 pointing me this out that board power and regulator had to be modded)Best CPU control app when you want to UV is free for XDA members SETCPU , download 2.24 or buy it, SUPPORT the devs! (it allows you to type in voltage changes and not only slide), Remember only steps of 10mV are real values , if you apply a step of 25mV it will actually be 20mV. So use setcpu to type in voltage steps of 10mV , 20mV , 30mV, ..
New Governor , LionHeart , tweaked by me to be very battery friendly.
GPU 2 D & 3D scales from 300 - 450MAX . What does this mean: When you play a stressfull game it will go up to Max 450MHz if it can depending on = It scales with voltage and process ID , lower voltage/ lower stress/ lower CPU speed = lower GPU speed. I hope this is the best solution for all users and best for battery/performance.
FastCharge updated to pengus77 edition.
Kernel Panic Timeout increased to 10 so a automatic reboot can be prevented when running out of memory on multitasking.
SU660 gets all versions.
FOR RF2.0 I would like to thank Pengus77 for his contribution on the voltage control and the updates of FSYNC and FastCharge.
I would also like to thank my good friend ezterry and godmachine81 for the OC code and GPU code.
Next I thank all my beta testers for the info and stressing there phone.
14-Mar-2013:
CivZ_SkyWalker_RF2.0-b released
New terminal commands to control the swappines
LG terminal command name change !!!
civz command updated
The rest of the kernel is 100% the same!
23-Mar-2013:
CivZ_SkyWalker_RF2.2-b released
New secondary , GPU frequency table.
3D Clock scales max to 425MHz.
2D clock scales up to 400MHz max (only when needed in heavy load)
USB connection delay patch
Fastdormancy terminal command
29-Mar-2013:
CivZ_SkyWalker_RF2.3rm released
gspca_main.ko module moved to optional modules
Stripped of all debugging = Lighter and optimized code
Fixed some code errors while compiling
06-Jul-2013:
CivZ_SkyWalker_RF2.5rm released
SetCPU 3.1.0 and higher reverted voltage fixed so on older versions of setCPU this kernel won't report correctly.
Note on LG SWAP increase:
Remember that on stock LG rom the default LG swap is 131MB. If you change kernel that doesn't got this terminal option and you changed the swap size or disabled it , no problem the swap commands are installed in system/bin so if you didn't delete them you can always use it. This does not count for other terminal command that come with the kernel.
Side note on USB BSOD
It is very random and still not 100% solved.
I noticed that with enabled Dynamic FSYNC or a to high OC it can still occur.
Just turn on your screen before connecting to pc and safe yourself a battery pull.
Click to expand...
Click to collapse
Side note:
Kernels comes as a boot.img = ramdisk with zImage.
Reason is that I made some changes in ramdisk. , init.d support.......
The meaning of this kernel is if you don't OC you get supurb battery life and 100% stability. If you start changing default governors and schedulers it will and can have a effect on battery life and OC to much with to much UV it will get unstable.
I recommend 1.2-1.3GHz for 24/7 use and not more. Governors can have a great effect on battery life. The flexibility in the kernel is there for the user to pick his/her favorite setting.
Source see second post!
More info about Sithlord and the effect of RamHack and Zram
Thank you! you are the best developer.
antutu with CivZ_SkyWalker_RF1.0 released - 7561
antutu with CivZ_SkyWalker_RF2.0 released - 7026
nothing has changed, all standard
Why is that?
SuRMaJ said:
Thank you! you are the best developer.
antutu with CivZ_SkyWalker_RF1.0 released - 7561
antutu with CivZ_SkyWalker_RF2.0 released - 7026
nothing has changed, all standard
Why is that?
Click to expand...
Click to collapse
Did some benchmarks.
All with 50mV UV and lulzactive /row
1000 MHz = 7002 points
1200MHz = 7480 points
1504 MHz = 8701 points
That is like 99% the same as RF1.0
Don't only look at benchmarks , look at user experience.
RF2.0 is a lot more balanced then 1.0
could you please tell me how to build a su660 kernel form p990 sources? thanks
New RF2.0-B
xzmu said:
could you please tell me how to build a su660 kernel form p990 sources? thanks
Click to expand...
Click to collapse
Linux , Time , source.
I think there are enough great guides here on XDA on how to...
---------------------------------------------------------------------------------------------------------------------------------------
14-Mar-2013:
CivZ_SkyWalker_RF2.0-b released
New terminal commands to control the swappines
LG terminal command name change !!!
civz command updated
The rest of the kernel is 100% the same!
How does it work: (so you got some inside info , please also take a look into the zips bin files for the people that want to learn a little more , this way you get a better understanding of what it does when you type in the commands)
A sysctl.conf is installed in system/etc
When you type in the command , the sysctl.conf is edited to hold the value for after a reboot
the vm swappines is changed when you typed in the command so it is applied immediately and it sticks after reboot.
If you should delete the sysctl.conf in system/etc for some reason the swappines will return to android default of 60.
Click to expand...
Click to collapse
PLEASE TAKE A LOOK AT THE NEW TERMINAL COMMANDS AS SOME CHANGED BY NAME!
Kernel control options to use with Terminal: (Settings are applied immediately and stick even after reboot now)
Enable/Disable LG 131MB SWAP or 260MB SWAP: (131MB is LG default)
Terminal command:
su (enter) lg_swap_of (enter) = This will disable LG swap (Reboot is needed to apply changes and sticks after reboot)
su (enter) lg_swap130_on (enter) = This will enable LG 131MB swap (Reboot is needed to apply changes and sticks after reboot)
su(enter)lg_swap260_on(enter) = This will enable LG 260MB swap (Reboot is needed to apply changes and sticks after reboot)
Note on LG swap: The 131Mb is default of LG
LG got this enabled in the stock LG rom and it uses the dev/block/mmcblk0p4 (unused partition) for it so not the same as ZRam that uses /dev/block/zram0 file. The LG Swap partition is enabled by default , I just add this command so if a user don't want to use the LG swap it can be done now with a single command.
Change system swappines value: (Android default is 60) (setting are applied immediately and sticks after reboot)
Terminal command:
su(enter)swappines_0(enter) = set swappines at 0 = system waits very long to swap , Kills tasks very quick
su(enter)swappines_20(enter) = set swappines at 20 = Performance setting for gaming
su(enter)swappines_40(enter) = set swappines at 40 = Performance setting and some multitasking
su(enter)swappines_60(enter) = set swappines at 60 = Androids default , balanced setting
su(enter)swappines_80(enter) = set swappines at 80 = Aimed for multitasking/Balanced
su(enter)swappines_100(enter) = set swappines at 100 = Aimed for extreme multitasking , NOT GAMING
Click to expand...
Click to collapse
SU660-VERSIONS
CivZ_SkyWalker_RF2.0-SU660-b
CivZ_SkyWalker_RF2.0_24RH-SU660-b
CivZ_SkyWalker_RF2.0_32RH-SU660-b
Side note on USB BSOD (screen off and pluging in usb resulting in BSOD)
I noticed that with enabled Dynamic FSYNC or a to high OC it can still occur.
So in that case please turn on screen before plugging in USB.
Enjoy!
My phone is unhappy with 1400 & 1500 OC
don't feel the need anyway! heheh
Thanks for your work hard. I like your kernel. But my phone is used old bootloader. Could you build this kernel for Old bootloder?
Re: [KERNEL]CivZ SkyWalker_RF2.0-b (MAX OC 1.504GHz) for ICS / New bootloader
nguyenletuquynh said:
Thanks for your work hard. I like your kernel. But my phone is used old bootloader. Could you build this kernel for Old bootloder?
Click to expand...
Click to collapse
Mr.Civato only build kernel for ICS based ROM which uses NEW BL, So I guess the answer would be "NO"
Sent from my LG-P990 using xda app-developers app
Can't wait to get my hands on this update, really a big thank you to Sir Civato for including SU660,
Is there a possibility to have a none overclocked kernel for GPU sir?
P.S. Im still on 1.2 and it gave me no problems and this is the first time my device performed at its best on the battery and performance perspective. Can't wait to update 1.2 to 2.0b with FLEX_ICER!
I LOVE YOU Civato!!
really glad you're breathing life to this lonely ghost town.
My Set-up:
Flex_ICER 4.6
SkyWalker 2.0b
default freq
lionheart -50UV
+ row
gaming/surfing and overall performance is superb!
I can't really give relevant feedback regarding Battery Life since I'm a heavy DATA user.
Screen Off:
216-312mhz
both -60uv
powersave gov.
it sleeps but not die
This is sick! Great job! I hope next release you'll add smartassv2.
it will work on this ROM right?
http://forum.xda-developers.com/showthread.php?t=2173094
Thanks in advance
WasifSal said:
it will work on this ROM right?
http://forum.xda-developers.com/showthread.php?t=2173094
Thanks in advance
Click to expand...
Click to collapse
yes, ofc! as long as it's stock ICS based ROM that uses New BL
genemini said:
yes, ofc! as long as it's stock ICS based ROM that uses New BL
Click to expand...
Click to collapse
I want to use other roms.
:fingers-crossed::fingers-crossed: :angel:
RF2.2 released for SU660
23-Mar-2013:
CivZ_SkyWalker_RF2.2-b released = SEE OP
New secondary , GPU frequency table.
3D Clock scales max to 425MHz.
2D clock scales up to 400MHz max (only when needed in heavy load)
USB connection delay patch
Fastdormancy terminal command
awesome
awesome! gonna try the latest one out on Flex_ICER! Thank you Sir Civato :highfive:
Battery life is nearly doubled , on stock settings. WOW I cant think of what sir civato did to the latest release, pretty awesome x99:victory:
2.3 released
29-Mar-2013:
CivZ_SkyWalker_RF2.3rm released
gspca_main.ko module moved to optional modules
Stripped of all debugging = Lighter and optimized code
Fixed some code errors while compiling
LG-SU660-VERSIONS
CivZ_SkyWalker_RF2.3rm-SU660
CivZ_SkyWalker_RF2.3rm_24RH-SU660
CivZ_SkyWalker_RF2.3rm_32RH-SU660
Code:
Older kernel versions:
LG-SU660-VERSIONS
[URL="http://d-h.st/cOR"]CivZ_SkyWalker_RF2.2-SU660-b[/URL]
[URL="http://d-h.st/l9W"]CivZ_SkyWalker_RF2.2_24RH[/URL][URL="http://d-h.st/l9W"]-SU660-b[/URL]
[URL="http://d-h.st/85i"]CivZ_SkyWalker_RF2.2_32RH[/URL][URL="http://d-h.st/85i"]-SU660-b[/URL]
civato said:
29-Mar-2013:
CivZ_SkyWalker_RF2.3rm released
Click to expand...
Click to collapse
Trying this one out now sir on stock P990! Thank you sir Civato :highfive:
Love and respect :good: