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:
Related
{
"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%....
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
Discontinued. Thank skate4life
{
"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"
}
ARM.
The Next Reliable Managed Architecture.
- ARM or Android Reliant Management, Aims to bring full battery saving to our devices and add features not introduced. This would of course reduce battery hunger and at the same time, sustain the performance of our phones. ARM IS A PURE CM Build Except its Kernel.
THIS IS A KANGed Kernel and a PURE CM Built ROM with Minor Addons. I am not responsible or credited for the kernel source codes whatsoever. I only modify the kernel to my needs and add more features not available in Official CM kernel which will be beneficial to all of us. THE IS ROM NOT BUILT FROM MY SOURCE. Comes from the pure Jenkins of CM.
[/QUOTE]
- Undervolted Clock values for more battery life
- 4.2 User Interface
- Enhanced Audio with Beats™ and MusicFX
- Enhanced Experience with customizations
- Various Tweaks In Kernel
- Optional OC to 1.1GHz
- Each Clock Speed fully utililises its Voltage
- Powersave Tweaks on various modules
- Tweaks in ROM
- Lower Battery Consumption
- Solved CM10 Vibration issue with the Overclock
Click to expand...
Click to collapse
COMPATIBLE WITH
- PACman + By Duarte777
- AOKP + By chenleicpp
- Official CyanogenMod
- ParanoidAndroid + By Duarte777
- ShenduOS 4.0.4
- ShenduOS 4.1.2
- SlimBean + By LoLaTion
- Dark Mod
- More just say
- MIUI Yet to be tested
Source Code (KERNEL) - Github
Last Commits: 27 Nov 2012
The ROM Source Codes are not needed due to the fact that it is Deep fried(Chinese-Style Of Cooking) by me.
Screenies
======================
+ ROM Changelog+
Base : CyanogenMod 10
Maintainer : RomWiz
-Nightly 1- 16-11-2012
= Based On CM10.0.0
= Ported Some parts from CNS
= Added Beats™ Audio (Thanks To Awesome)
= Integrated GAPPS
- Nightly 2 -
= Added TweakZV6 (Thanks to [email protected],OP)
= Initialise Build.prop Tweaks
= Removed Apps that disappeared, or missing from App Drawer
= Further Cleaning for Smaller size
= Removed NFC Capable Libs
= Removed Samsung-Related Libs
= Fixed Launcher FC
= Fix Settings FC
= Cleaned apps
= Adrenaline™ Boost (Thanks to imbawind)
= Removed GAPPS
= Enlightened ROM for size
- Release Candidate 1 - 20-11-2012 -
= Ported 4.2 System Apps
= Added further Build.prop tweaks
= Cleaned ROM Again
= Changes to Boot Animation and Sound
= Rebased to Latest CyanogenMod Nightlies
= Added Fixed Photosphere
- Release Candidate 2 -NA-
= RomWiz to take over ROM Segment
Click to expand...
Click to collapse
Bugs
--------
- KERNEL - Softkey light will go permanently off and will come back after locking and unlocking.
- Battery Drain - The latest version has reduced hunger by 3-8% against Stock CM kernels
{KERNEL} Changelog With Features Indicated
Base : CyanogenMod Stock Kernel Source
*R1* 31-10-2012
- Compiled from source
- Synced with latest sources
*R2* 1-11-2012
- Synced With Sources
- Added Governors : InteractiveX, OndemandX
- Enabled Governors from Source : Powersave, Interactive, userspace, Conservative
- Added A few sysctl Tweaks
*R3 Alpha* 10-11-2012
- Push all commits to My Git
- Added deadline Scheduler
- Removed Interactive and InteractiveX: Due to latency issues
- Enabled Sysctl Syscall Support
- Very Minor Fixes
- Set Default Governor : (OndemandX)
*R3* 11-11-12
- Used Ondemand as default governor due to new battery life improvements
- Synced Sources with CM
- Set Swappiness to 0
*REASON: As Official CM10 kernel does not even support swapfile, i set this to zero, so as to improve performance a little
- Undervolt WLAN
- Tweaked Ondemand to further reduce power hunger but sustain the performance at the same time
- Re-Added Interactive and InteractiveX and fixed latency Issues
*R3+* 12-11-2012
- Tweaked InteractiveX to reduce latency
- Tweaked Overall voltages for MPUs
*R4* =MILESTONE 1= 20-11-2012
- Shifted Source Code to a new Github for tidyness
- Integrate OPP values into Kernel 3.0.8
- Reduce BL voltages
- Added 1.1GHz Overclock
*R4+* 20-11-2012
- Bump Up all Clock Values to rightfully fit the Clock voltages
- Reduce Some Clock Value Voltages to rightfully balance battery power and speed
- Changes to the Clock Policy for better Clock Rules
*R5* -Never Belittle this small update!- =21-11-2012=
- Further reduce the voltages per clock rate
*v1* + 23-11-2012 + (Formally known as v5.00A1)
- Balance the clock rates and voltage
- Add another 800MHz OPP
** =MILESTONE 2= What to expect soon
¶ INCLUDES ALL ITS ALPHAS AND BETAS ¶
- Tweak voltage to prevent SoD
- Add 2 New OPP rates for Underclocking and fix voltage correctly
+ 150MHz
+ 200MHz
- Remove Powersave Bias from InteractiveX which causes the extreme lags
- Add OC for 1.2GHz
- Modify Ifdef for any errors regarding Underclocking
- Added All OPPs 100MHz by 100MHz jumps
- Enable a 1.3GHz OC as 1.2GHz is not considered Overclock under TI specifications of OMAP 3630
- Overclock GPU to 210MHz from 200MHz
+NOT DONE+
- Reduce Softkey LED from 5mA to 1mA
Click to expand...
Click to collapse
-Credits-
+ Texas Intruments, Providing me a Wiki to refer on modding kernel.
+ CyanogenMod, Especially arcee, for providing AND fixing the source codes actively
> Codename Sammy, For some libs, and apks ,Thread
< Awesome, For his Creation Of Awesome Beats™
+ YOU, Readers, for providing me a place to allow you to give me suggestions
+ Boype, For Refering to your Source codes to counter check with TI's wiki.
+ Redy, For giving me the correct Manual link for TI
→ xonar_ , for commenting on whatever commit or new feature which will result in a problem & Solutions and tutorials on new implementations
+ Google, For allowing me to identify whatever errors i face.
π N00BY0815 for more suggestions and solutions
× Gabwerkz, for fixes,methods of uses and files for modifactions
♥ XDA Community, Giving comments on whatevers best for implementations
Approved By B.Jay.
For the Kernel.
+DO NOT MIRROR+
For The Kernel, READ THE FIRST POST THOROUGHLY BEFORE FLASHING ON YOUR CURRENT ROM
EVERYTHING IS GOING ACCORDING TO DATE OF RELEASE.
Kernel
RR Kernel R2 - DEV HOST
RR Kernel R3 - Download
Milestone 1 - Download
- Date Achieved : 19-11-2012 -
ARM Project R4+ (Named as R4) - Download
ARM Project R5 - Download
v1 (Formerly Known As v5.00A1) - Download
ROM
Nightly 1 - Dropbox
Nightly 2 Final - Dropbox
RC 1 - Download +Dropbox+ | MIRROR
FAQs
+ Q: Whats the difference?
A: Read the disclaimer.
+ Q: Will I get worse performance than the Official CyanogenMod Kernel?
A: It depends on what commits are added. My Kernel only fixes bugs i can fix and which are unsolved and Of course, I will add more features not available in CyanogenMod Official
Done!
Tutorials
Here are some useful commands for the ROM.
When you do not have enough memory, utilize Adrenaline™ Boost.
Type:
imbawind said:
su
boost
Click to expand...
Click to collapse
Enjoy more RAM!
Testimonies
Please Comment on all aspects.
UniversalSS said:
My testimony/comments(NON-BIAS):
I'm using this with RevolutionRemix 1.4.1Final and it is pretty good with occasional hangs here and there.Runs smoothly and is able to play games intensively.A bit more battery drain as well though.With more governors,I wont say that this kernel is useless but I definately think that the developer can do more.Conclusion:An alright kernel with a bit more features.But dev can do better
Click to expand...
Click to collapse
norby55 said:
I've put this on my P970. It works pretty well, some parts of the UI work better than before. I am using CM10 and it's a bit of a improvement.
It would be interesting to see the implementation of more governors (like SmartAss). A bit of tweaking and this Kernel is set to be a really good one!
Click to expand...
Click to collapse
Keep it up!
Donations Hall Of Fame
> Every Person Who has Thanked This Thread
If you tested it, could you give me/us a specific resumen about what it does, I mean, what will I gain if I install it?, which bugs you meant?
Mexickano said:
If you tested it, could you give me/us a specific resumen about what it does, I mean, what will I gain if I install it?, which bugs you meant?
Click to expand...
Click to collapse
By Gaining New features such as governors. Do take note that i will add more soon
Bugs by battery drain. not really a bug but more of a issue
Sent from RevolutionRemix v1.4.1 FINAL with Tapatalk
My testimony/comments(NON-BIAS):
I'm using this with RevolutionRemix 1.4.1Final and it is pretty good with occasional hangs here and there.Runs smoothly and is able to play games intensively.A bit more battery drain as well though.With more governors,I wont say that this kernel is useless but I definately think that the developer can do more.Conclusion:An alright kernel with a bit more features.But dev can do better
Mexickano said:
What ROM? I think in this thread we are talking about a kernel, not about a ROM, if you want argue with him, pm him, and keep this topic clean of dramas please.
Click to expand...
Click to collapse
So, Was the kernel ok to you?
Sent from my LG-P970 using Tapatalk 2
In the next build, i will implement the 'hotplug' governor. Other users as of :http://forum.xda-developers.com/showthread.php?t=1843973 has a possible battery improvement by using this governor.
Sent from my LG-KU5900 using Tapatalk 2
I'm waiting for the R3 release, really wanna try, especially with the battery life...
You have gave Dev Section another color bro...thanks...
kirigaze said:
I'm waiting for the R3 release, really wanna try, especially with the battery life...
You have gave Dev Section another color bro...thanks...
Click to expand...
Click to collapse
I dont really fix stuff You should thank XDA for giving me a place. And, i apply cherry picks for battery life. So yeah.. there is a R3 alpha in my devhost. So please feel free to try. Theres only minor battery life extension. The next R3 should be able to reduce battery intake obviously.
Sent from my LG-KU5900 using Tapatalk 2
New pushes and commits started.
Reducing WLAN voltage to further reduce battery hunger
Set swappiness to 0
More coming...
Sent from my LG-P970 using Tapatalk 2
nicholaschw said:
New pushes and commits started.
Reducing WLAN voltage to further reduce battery hunger
Set swappiness to 0
More coming...
Sent from my LG-P970 using Tapatalk 2
Click to expand...
Click to collapse
you have first and second post for that. don't up your topic by yourself :| .
// whatever , you don't deserve a new post , so i edited .
skate4life said:
you have first and second post for that. don't up your topic by yourself :| .
Click to expand...
Click to collapse
I did not
Sent from my LG-P970 using Tapatalk 2
"*R3*
- Used Hotplug as default governor due to user beliefs throughout XDA
- Synced Sources with CM
- Set Swappiness to 0
- Undervolt WLAN"
Click to expand...
Click to collapse
Im really curious how did you manage to make "hotplug" working, as it's only working on multi-core devices? If i am missing anything, just correct me
And if u can explain me what did u change to make 'sio' compiling without problems, cause i had some problems with it.
@EDIT
static int
sio_queue_empty(struct request_queue *q)
{
struct sio_data *sd = q->elevator->elevator_data;
/* Check if fifo lists are empty */
return list_empty(&sd->fifo_list[SYNC]) &&
list_empty(&sd->fifo_list[ASYNC]);
}
Click to expand...
Click to collapse
I see that you changed something here, but can you explain why?
Hbohd said:
Im really curious how did you manage to make "hotplug" working, as it's only working on multi-core devices? If i am missing anything, just correct me
And if u can explain me what did u change to make 'sio' compiling without problems, cause i had some problems with it.
Click to expand...
Click to collapse
Yeah, it seems he missed the Professors Class, and didn't read the CPU-Governors material
Hotplug Governor:
The “hotplug” governor scales CPU frequency based on load, similar to “ondemand”. It scales up to the highest frequency when “up_threshold” is crossed and scales down one frequency at a time when “down_threshold” is crossed. Unlike those governors, target frequencies are determined by directly accessing the CPUfreq frequency table, instead of taking some percentage of maximum available frequency.
The key difference in the “hotplug” governor is that it will disable auxillary CPUs when the system is very idle, and enable them again once the system becomes busy. This is achieved by averaging load over multiple sampling periods; if CPUs were online or offlined based on a single sampling period then thrashing will occur.
Sysfs entries exist for “hotplug_in_sampling_periods” and for “hotplug_out_sampling_periods” which determine how many consecutive periods get averaged to determine if auxillery CPUs should be onlined or offlined. Defaults are 5 periods and 20 periods respectively. Otherwise the standard sysfs entries you might find for “ondemand” and “conservative” governors are there.
Obviously, this governor is only available on multi-core devices.
Click to expand...
Click to collapse
So u guys mean when i compile i will get: Werror:xxxxxx cpu_in
Cpu_out
Back to research...
Sent from my LG-P970 using Tapatalk 2
Hi. This kernel work with stock kernel 3.0.8 rom v28C ( using for lg optimus black p970 ) ? Thanks !
Sent from my LG-P970 using xda app-developers app
anhungai said:
Hi. This kernel work with stock kernel 3.0.8 rom v28C ( using for lg optimus black p970 ) ? Thanks !
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
Nope. It does not. This is for CyanogenMod 10 Only. And Compatible with Shendu v2.0
====EDIT=====
PARom
- CM10 LG UI
- RR Kernel
- ACID Audio
- Improved battery life over CM10
Stay Tuned
Sent from my LG-P970 using Tapatalk 2
nicholaschw said:
Nope. It does not. This is for CyanogenMod 10 Only. And Compatible with Shendu v2.0
====EDIT=====
PARom
- CM10 LG UI
- RR Kernel
- ACID Audio
- Improved battery life over CM10
Stay Tuned
Sent from my LG-P970 using Tapatalk 2
Click to expand...
Click to collapse
Can custom kernel 3.0.8 for p970 ( using stock kernel 3.0.8, rom v28C) ? Where i can ? Please !
Sent from my LG-P970 using xda app-developers app
anhungai said:
Can custom kernel 3.0.8 for p970 ( using stock kernel 3.0.8, rom v28C) ? Where i can ? Please !
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
"Father, forgive them because they don't know what they are doing." (J.Christ)
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.
Here it is, as requested by mrg666.
Contary to MiRaGe, which the kernel naruKa is derived, this is more tweaker's kernel, I will add more features over time.
This kernel is shipped with default stock kernel settings.
Ondemand, cfq, stock clocks, stock voltages, etc.
I'm not responsible to what and what will happen to your mako.
If anyone know how to set GPU max clock from kernel, instead of from init.d script, please let me know
Download
Source
Features/Changelog:
R19
Simple gpu governor
faux's snakecharmer (always on if you use fauxclock because this was compiled as built in feature, not kernel module)
dynfsync
ziddey's otg + faux tuneables (do flash the package ziddey provides)
Fastcharge
Synced with latest mirage
intelli_plug!
Removed msm_hsic_host commits temporary since it creates dmesg spam
R18
Synced with latest MiRaGe
R17
Synced with latest MiRaGe
4.4.3
GPU Voltage control
R16
Additional commits to S2W/DT2W, see GitHub for commits containing lge_touch_core
Fixes to MSM_DCVS, see github for moar details
Faux123 low clocks and ultimate overclock is back!
R15
Some msm_hsic_host patches
Fixed multiple 487.5MHz GPU clock showing up
R14
BFQ for real
Wheatly governor
R13
BFQ, SIO, FIOPS I/O scheduler
Bedalus's preservative
R12Ribaasu
Bricked's msm_mpdecision and msm_thermal
Intellidemand
Intelliactive
Complete rebase to MiRaGe
No CPU under/overclocking for now because inability to boot
Compiled with Ubuntu 14.04 LTS, GCC 4.8, -O2
R11
Further GPU overclocking to 533MHz, defaults is still 400MHz
R10
Fixed the messed up voltage table and possible fix for freezing while on 27 and 54 MHz
R9
Fixed possible multiple cpu clocks showing up
Disable Bricked's msm_mpdecision because of compiler errors until a solution is found
Reenabled and synced AutoSMP
Synced with latest MiRaGe
Ultra low clocks @ 27 MHz thanks to [email protected]
R8
Synced with latest MiRaGe
Removed autosmp
Bricked's msm_mpdecision
Bricked's msm_thermal
Bricked's S2W
Bricked's DT2W
R7
Synced with latest MiRaGe
R6
Fixed duplicate 386 MHz showing up
Faux123's GPU Overclock to 487.5 MHz
Faux123's ultimate CPU Overclock to 1.944 MHz
R5 GitHub edition
Thanks to @xenyz
Lowered Voltage control minimums
F2FS Support
Added Samsung's exFAT drivers
R4
Finally proper kexec-hardboot
FauxVoltage
Faux123's low clock @ 162MHz
R3/First release
Anykernel based
synced with Mirage's source at the time of complication.
reenabled disabled governor and iosched (for 'as close to stock' reason)
PA Halfbreed
kexec (not working for now)
fauxsound
fauxgamma
bedalus's bus speed hack
Compiled on Fedora 20 x86_64, Linaro GCC 2014.03 - Cortex-A15 @Christopher83, -j4 -o3
XDA:DevDB Information
naruKa kernel, Kernel for the Google Nexus 4
Contributors
passlogin
Kernel Special Features:
Version Information
Status: Testing
Created 2014-04-05
Last Updated 2014-08-13
Reserved
SysFs tunables
intelli_plug
#Disable msm_mpdecison and enable intelli_plug
echo 0 > /sys/kernel/msm_mpdecision/conf/enabled
echo 1 > /sys/module/intelli_plug/parameters/intelli_plug_active
#Selects intelli_plug profile
#4 cores:Balanced = 0, Performance = 1, Conversative = 2
#2 cores: Eco Performance = 3, Eco Conversative = 4
echo 4 > /sys/module/intelli_plug/parameters/nr_run_profile_sel
#Screen-off frequency
#'echo 4294967295' to disable
echo 270000 > /sys/module/intelli_plug/parameters/screen_off_max
Exactly what I've been looking for! Thank you for your work, will test and get back
...sent from space
Thanks will try it.
Sent from my Nexus 4 using xda app-developers app
You must give your sources please
barome said:
You must give your sources please
Click to expand...
Click to collapse
I will, if I can.
My speed is under 32kbps and if I find public hotspot which has great upload speed, I will do it ASAP.
What about implementing Semaphore DT2W?
My priority right now is bricked msm_mpdecision & thermal so no no right now.
For dt2w, franco has s2s and dt2w right?
EDIT: Sorry for derping but I will consider bricked's s2w and dt2w since he has it in his repo.
Still if you want to request semaphore's, explain it's benefit over bricked and I will consider it.
I've used various kernels with d2tw and semaphore's has the least battery drain, is the most accurate, doesn't unlock in pocket and doen't has the screen edges error.
passlogin said:
My priority right now is bricked msm_mpdecision & thermal so no no right now.
For dt2w, franco has s2s and dt2w right?
EDIT: Sorry for derping but I will consider bricked's s2w and dt2w since he has it in his repo.
Still if you want to request semaphore's, explain it's benefit over bricked and I will consider it.
Click to expand...
Click to collapse
The best implementation of dt2w with least problems of screen freeze issues....
Guess that answer's why you should consider it
But great work
vampire36 said:
The best implementation of dt2w with least problems of screen freeze issues....
Guess that answer's why you should consider it
But great work
Click to expand...
Click to collapse
That's leaves me with the s2w.
dt2w and s2s isn't in the top on my priority list.
I will work with dt2w and s2w after bricked msm_ then
If you folks didn't notice, R4 is out. Do check the changelog.
I've made a github account, though it's still empty, check the op for link.
Can we have a link to download section on the first post? I think a lot of us, tapatalkers, would appreciate it... Thank you in advance!
Sent from my Nexus 4 using Tapatalk
Jagdish84 said:
Can we have a link to download section on the first post? I think a lot of us, tapatalkers, would appreciate it... Thank you in advance!
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Is linking to DevDB download place is enough?
passlogin said:
Is linking to DevDB download place is enough?
Click to expand...
Click to collapse
It is to me!
Cheers for the quick response.
Source is up everybody, have a look!
Blue colors look brown on Beanstalk rom.
Sent from my Nexus 4 using xda app-developers app
Nice, thanks!
Can you lower min voltage from 800 mV to something like 675 and add f2fs please?
https://github.com/faux123/mako/commit/693873aa7e6001fe07cdc6263fdeabba08f709df
Sent from my Nexus 4 using Tapatalk
junxracr said:
Blue colors look brown on Beanstalk rom.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well it's your rom issue, check if your rom is cm based or modify the gamma table.
xenyz said:
Nice, thanks!
Can you lower min voltage from 800 mV to something like 675 and add f2fs please?
https://github.com/faux123/mako/commit/693873aa7e6001fe07cdc6263fdeabba08f709df
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I thought that commit has gone into the kernel, thanks for remembering!