This is a self compiled Kernel from these sources. It's a fork of the kernel source git plus some performance tweaks and minus a bad patch, which turned out to drain the battery.
The initramfs (source) is a modified CF-Root v4.1 of the KG1.
I added some /proc and /sys tweaks in init.rc (github of the initramfs):
Code:
+ write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand
+ write /sys/block/mmcblk0/queue/scheduler noop
+ write /sys/block/mmcblk0/queue/read_ahead_kb 512
+ write /proc/sys/vm/highmem_is_dirtyable 1
+ write /proc/sys/vm/dirty_writeback_centisecs 1500
+ write /proc/sys/vm/laptop_mode 5
This probably works best with Villain ROM 2.0 [2.3.4] and the XXKG1 radio image.
History:
Version 1.1:
added touchscreen fix suggested by vincenzo91.
Version 1.2 :
now based on CF-Root 4.1 (was 4.0)
cherry-pick'ed some fixes from cfs-exp branch of ninphetamine github
removed "setprop dalvik.vm.execution-mode int:fast", which prevents JIT
changed touchscreen MOVHYSTI to 5 from 0 (15 original)
Version 1.3 :
removed bogus /sys, /proc settings
use /init from KG1/CF-ROOT
set readahead to 512kb
enabled fuse, so you can use "ntfs-3g" to mount a NTFS drive
There is also a variant with MOVHYSTI set to "0" (Backslash-1.3-HYST0). Let me know, if you have those touchscreen problems with either "0" (HYST0) or the "5" in the normal kernel.
So how does it look like? See the attached image (FastDormancy was not turned off, because it got better in 2.3.4)
Benchmark CF-Bench Pro v1.1
Interpretation left to the reader...
Code:
Stock CF-Root KG1: | Backslash-1.3:
Native: 11256 11478 11172 | 11566 11360 11414
Java: 3155 3235 3071 | 3411 3240 3327
Overall:6395 6532 6311 | 6673 6488 6561
read: 553 535 540 | 564 571 570
write: 138 180 176 | 181 181 173
saturn_de said:
This is a self compiled Kernel from this sources. It's a fork of the kernel source git plus some performance tweaks and minus a bad patch, which turned out to drain the battery.
The initramfs is a modified CF-Root v4.0 of the XXKG1.
I added some /proc and /sys tweaks in init.rc.
This probably works best with Villain ROM 2.0 [2.3.4] and the KG1 radio image.
So how does it look like?
Click to expand...
Click to collapse
So does this also fix the push exchange email battery drain or just some other drain (non-existent to me)?
saturn_de said:
This is a self compiled Kernel from this sources. It's a fork of the kernel source git plus some performance tweaks and minus a bad patch, which turned out to drain the battery.
The initramfs is a modified CF-Root v4.0 of the XXKG1.
I added some /proc and /sys tweaks in init.rc.
This probably works best with Villain ROM 2.0 [2.3.4] and the KG1 radio image.
So how does it look like?
Click to expand...
Click to collapse
This can fix the Android OS draining ?
szav said:
This can fix the Android OS draining ?
Click to expand...
Click to collapse
standby battery usage seems quite good, will try on cognition 1.11 and feedback..
Hy guys is it possibile have this kernel in a zip flashable version..
I haven' t my pc here but i need to try cause i want my phone for 24 hrs...a day...
Regards
cescof said:
Hy guys is it possibile have this kernel in a zip flashable version..
I haven' t my pc here but i need to try cause i want my phone for 24 hrs...a day...
Regards
Click to expand...
Click to collapse
Just flash in CWM. Open CWM and select Flash Kernel, then select this kernel. It will flash then reboot.
Testing it now. Lets hope it works
Btw, have you noticing it not obeying SetCPU?
In both CF-Root and a testkernel I tried then clock would go above the max I set. I had it set at 800 but it still went to 1ghz, 1.2ghz and 1.6ghz...
ante0 said:
Just flash in CWM. Open CWM and select Flash Kernel, then select this kernel. It will flash then reboot.
Testing it now. Lets hope it works
Btw, have you noticing it not obeying SetCPU?
In both CF-Root and a testkernel I tried then clock would go above the max I set. I had it set at 800 but it still went to 1ghz, 1.2ghz and 1.6ghz...
Click to expand...
Click to collapse
Just don't use SetCPU... it's useless. "Race to idle" is the key. Don't be smarter than the kernel and add more load with an app.
ante0 said:
Just flash in CWM. Open CWM and select Flash Kernel, then select this kernel. It will flash then reboot.
Testing it now. Lets hope it works
Btw, have you noticing it not obeying SetCPU?
In both CF-Root and a testkernel I tried then clock would go above the max I set. I had it set at 800 but it still went to 1ghz, 1.2ghz and 1.6ghz...
Click to expand...
Click to collapse
Really? Where did you check your real clock speed? In the Battery statistics in setCPU it tells me 0% for 1200 Mhz if i set it to 500-1000Mhz, using CF-Root for now.
@saturn_de: Isn't CF-Root 4.1 out? I have no idea whats changed but im one of those "the newer the better guys" even though i know thats not always true haha
EDIT: Ill stop using setCPU for today and see how it goes
ante0 said:
Just flash in CWM. Open CWM and select Flash Kernel, then select this kernel. It will flash then reboot.
Testing it now. Lets hope it works
Btw, have you noticing it not obeying SetCPU?
In both CF-Root and a testkernel I tried then clock would go above the max I set. I had it set at 800 but it still went to 1ghz, 1.2ghz and 1.6ghz...
Click to expand...
Click to collapse
it is not an overclocked kernel..and it obeys setcpu profiles..i am using them..
Removing setcpu as per saturn.. lets see..
dr3minem said:
@saturn_de: Isn't CF-Root 4.1 out? I have no idea whats changed but im one of those "the newer the better guys" even though i know thats not always true haha
Click to expand...
Click to collapse
I will have a look what changed in CF-Root 4.1 ...
So anyone here can confirm/deny the battery drain fix?
I cannot see any change yet. Just flashed KG1 and the kernel and the Android OS is still 20%.
We will see in a long-term.
Fingers crossed.
H377 said:
I cannot see any change yet. Just flashed KG1 and the kernel and the Android OS is still 20%.
We will see in a long-term.
Fingers crossed.
Click to expand...
Click to collapse
Email is still draining... Don't know about anything else as I haven't had any other processes / apps draining my power source aka battery.
Pume said:
Email is still draining... Don't know about anything else as I haven't had any other processes / apps draining my power source aka battery.
Click to expand...
Click to collapse
I have Gmail and Exchange all set up to PUSH but I don't have a problem with them. Only the Android OS's battery usage is high.
H377 said:
I have Gmail and Exchange all set up to PUSH but I don't have a problem with them. Only the Android OS's battery usage is high.
Click to expand...
Click to collapse
If your awake bar is not blue when the screen is off then you don't have anything to worry about. Android OS percentage does not mean a thing if the phone stays asleep when it should.
Pume said:
If your awake bar is not blue when the screen is off then you don't have anything to worry about. Android OS percentage does not mean a thing if the phone stays asleep when it should.
Click to expand...
Click to collapse
Thanks!
In fact after 12 or 14 hours I got 50% of the battery with normal usage. I don't know if it's normal or not but my HD2 and Desire also last almost the same.
I always had to charge them at night every day if I didn't want them to run of fuel during next business day.
Hi,
can you tell us what tweaks you applied ?
thx
from my side the kernel looks good so far good idle batterie atm
Flashed via CWM without problems. Will be using this kernel and post results tomorrow night.
I'm on Exynos 2.0.
After 1h2m almost always in idle with screen off (GMail&Exchange Push, 3G on) 1% has gone. The phone was charged to 100% and the battery stats were also wiped.
EDIT: GPS was/is also on
Related
Here is OTB-Reloaded for AOSP. This Kernel is overclockable and supports user adjustable under voltage control. You can choose what you want to do with this, if you want to use super undervolted settings for battery life you can. If you want to have a huge overclock you can. It is all depending on what your phone can handle and what you want to do. This kernel is based off of the facinate ed01 froyo source drop. It includes voodoo lagfix, voodoo color, bln, and many more tweaks.
OTB-Reloaded version 1.2
Built from ground up with new fascinate source
Overclock up to 1600 mhz - based off of onix kernel thanks to existz
13 frequency steps total
UV control via sysfs using Voltage Control app
Voodoo lagfix, color, and sound - thanks to Project-Voodoo thanks to supercurio
cwm3 installed with update zip
BLN - thanks to neldar
added simple i/o scheduler
added BFQ scheduler
added autogroup_sched patch v4
Kernel hz at 300, User hz at 150
TinyRCU - thanks to paulmck
Initramfs from JT1134 with busybox, and init.d support added
Update zip installs su binary and Superuser.apk
Modules tun and cifs included
rdnis support added
Backported ext4 patches - thanks to imnuts
Updated reserved memory settings and jhash3 table from speedmod kernel
Battery Hack - thanks to sirgatez
GizmoDroid fixes for data wipes
ssewk2x_real_fix.patch to make sure if you disable 100mhz step it stays disabled
Uses edify scripting
Other misc tweaks
Mini How-To
Do not use setcpu. Use voltage control from market. Test settings for at least a day before applying at boot. When testing just apply for now. It is best to not use more than 7 steps at a time. Users are encouraged to share their settings. If you would like a way to keep track of how much time cpu spends in state I recommend cpu spy from the market. The oc and uv are based off of the onix kernel for the i9000. You may be able to find helpful information there as well.
Frequency Mhz / Voltage
1600 mhz / 1500mV - overvolted **use extreme caution**
1500 mhz / 1500mV - overvolted **use extreme caution**
1400 mhz / 1375mV - overvolted **use caution**
1300 mhz / 1375mV - overvolted **use caution**
1200 mhz / 1300mV
1120 mhz / 1300mV
1000 mhz / 1275mV
900 mhz / 1275mV
800 mhz / 1200mV
600 mhz / 1175mV
400 mhz / 1050mV
200 mhz / 950mV
100 mhz / 950mV
Thanks
jt1134 of course...he is the man
supercurio for all of the wonderful work on project-voodoo
adrynalyne for his roms and odin packages
enderst for allowing me to build on his machine....that is awesome and so l33t to ssh to build on a remote machine
nedlar, taninm, rodderick, koush, thomasskull666, raspdeep, imnuts, khasmek, sirgatez, existz, nullghost ssewk2x, and GizmoDroid
Dank for the mirrors
All of the testers
Great people in IRC and anyone I might have missed.
*** If I missed giving you credit feel free to pm me and I will rectify as soon as possible. ***
Use this kernel at your own risk. I am not responsible for any damages to your phone. Be especially careful when overclocking and using voltages above 1375mV.
OTB-Reloaded AOSP ver 1.2 - latest version includes voodoo sound v8, cwm3 installed with update zip, default scheduler changed to deadline, fixes from ssewk2x
Q: OMG I lost Root
A: SU zip needs to be updated to work with the mount.wrapper we are using.
Flash OTB-Reloaded ver 1.1 or greater and your root su issues will be taken care of.
Click to expand...
Click to collapse
*** Mirrors ***
http://adbdev.com/danknub/SF_AOSP_OTB_OC_CWM3-1.0b_0412.zip old version
http://adbdev.com/danknub/SF_AOSP_OTB-Reloaded_v1.0_0420.zip old version
http://adbdev.com/danknub/SF_AOSP_OTB-Reloaded_v1.1_0420.zip old version
My Github
https://github.com/nemesis2all
im try it in miui rom
Sent from my Miui fascinate
Trying with SC 2.9... let's see if this fixes the notification wake problem...
kuronosan said:
Trying with SC 2.9... let's see if this fixes the notification wake problem...
Click to expand...
Click to collapse
i thought SC was considered a TW rom...therefore needing a TW kernal
will this kernel run on a TW rom?
kuronosan said:
Trying with SC 2.9... let's see if this fixes the notification wake problem...
Click to expand...
Click to collapse
This is NOT for sc 2.9 or any touchwiz based roms. You will have problems if it even boots.
Bah, forget it all. I'm just going back to the regular Voodoo EC10 until all of this gets sorted out.
Flashed and running very smooth, 2465 on Quadrant and a consistent 17 on linpack. Now for an all day battery test. Thanks, great work
Running Miui V5
nemesis2all said:
This is NOT for sc 2.9 or any touchwiz based roms. You will have problems if it even boots.
Click to expand...
Click to collapse
agreed! Flashed it last night and phone would freeze on boot screen
Sent from my Super Clean phone
ekowanz said:
im try it in miui rom
Sent from my Miui fascinate
Click to expand...
Click to collapse
works great...
Sent from my Miui fascinate
Well I had flashed it and had zero issues, but I'll take the word of a dev over my own any day.
Can anyone running this kernel confirm Bluetooth enables ok? Thanks in advance.
Sent from my MIUI Fascinate using XDA app
Confirmed Bluetooth is working with AOSP Rom and this kernal
Just wanted to let those wondering know that this kernel runs flawlessly on mesmerize (we have an AOSP rom that's soon to be released that I had a test copy of) thanks for taking the time to tweak this!
Runnin this kernel on fascinate - MIUI v1.3.5 - DL09 modem
Set CPU on conservative scaling
quadrant score: 2338
Linpack : 16.997
Everything works great so far! Thanks!!!!!! I'll check back in later to report any issues/success
Do you mean by this statement that bluetooth is fully functional including in call use???? That would be awesome and may allow me to more fully check the aosp rom out
skillz360 said:
Confirmed Bluetooth is working with AOSP Rom and this kernal
Click to expand...
Click to collapse
sent from my Super Clean 2.9.2 - Voodoo - Fascinate via Tapatalk Pro
My experience with Aosp (including this kernel and others) is that BT turns on successfully, but does not pair or recognize other devices.
chrisp304 said:
My experience with Aosp (including this kernel and others) is that BT turns on successfully, but does not pair or recognize other devices.
Click to expand...
Click to collapse
It turns on, pairs, but it doesn't work In call
I asked if Bluetooth was working because jt's current 0327-2 kernel doesn't have working Bluetooth. I was hoping to upload an update to jamezelles miui rom but I wanted an ec10 kernel with working Bluetooth first.
It's no biggie. There is another bug in the current miui release where the lockscreen shows the time only in 24h, so that's another reason to delay the update.
Thanks for the replies.. and for the kernel.
Sent from my MIUI Fascinate using XDA app
Original post update with new kernel.
nemesis2all said:
Original post update with new kernel.
Click to expand...
Click to collapse
Testing now...
Today a tried ogo2's beta3 ROM. In SetCPU I can't change the frequency. There are min 480-max 600 Mhz, if I change the value, nothing happens. That's wrong because it drains my battery.
Yeah, same problem here... such a pity because other than that its a great ROM!
Not really an 'issue' - the kernel isn't set up to allow overclocking, so why would it?
Not just overclocking. I can't go under 480 Mhz. That's a bigger problem for me.
cserepg said:
Not just overclocking. I can't go under 480 Mhz. That's a bigger problem for me.
Click to expand...
Click to collapse
I don't think the kernel allows you to change clock speeds from the MAX600 MIN480 HTC set as the default. Not an issue, but that feature will be added sometime (ogo2 said it would eventually I think)
OK, I thought that the default min clock speed is 245 Mhz.
Oh ok, didn't know it depended on the kernel, thanks.. This may be a totally noob question, but this is the Q&A section so, can I not just flash another kernel that does enable overclocking...?
Guys, cannot start neither beta3 nor beta4. When flash beta3 (through Clockworkmod 3), the system doesn't load, green 'HTC' letters tend to reboot. After beta4 installation the same screen, but static - without any reboots. I have S-ON. Wiping doesn't help.
Please, advise what to do.
Cheers!
cserepg said:
Today a tried ogo2's beta3 ROM. In SetCPU I can't change the frequency. There are min 480-max 600 Mhz, if I change the value, nothing happens. That's wrong because it drains my battery.
Click to expand...
Click to collapse
I eventually answered my own question.. You can just flash another kernel.. Look under the Overclocking tutorial in the Dev section...
It's ok now, I am using B-ROM. In this I've got too much reboot, battery drain, GPS issues, etc. Maybe beta 5-6-7 will get a chance...
cserepg said:
It's ok now, I am using B-ROM. In this I've got too much reboot, battery drain, GPS issues, etc. Maybe beta 5-6-7 will get a chance...
Click to expand...
Click to collapse
I'm using Blay0's ROM as well, haven't had any issues so far... are u doing a full wipe before you flash the ROM...?
If I installing a different ROM I always do a full wipe sure. I did not do full wipe, if I installing a newer version of a same ROM. Btw the most stable ROM is Blayo's, next Cyanogen, but there are no new sense...
Ok Guys !! kCernel is back !!
These are kernel for unlocked bootloader. They will be provided as ftf files which you need to flash using Flashtool by Androxyde.kCernel for STOCK GB (3.1.0.G.0.75) and STOCK based ROMS
This kernel works on ROMS like
X10S, FeraLAB, TEAM, ThGo, VmCmS, WolfBreak, etc
Testing Releases (without wifi) changelog and downloads
kCernel for FXP CM7 and ROMs based on FXP
This kernel works on ROMS like
FXP, M&M MIUI, M&M CM7, CosmicUI, etc
Features
----v 01 -----
Code:
> enabled CFQ, Anticipatory, Deadline, Noop IO Schedulers
> enabled Scary, SavagedZen, Smartass(v1&v2), Conservative, MinMax, interactivex, powersave, interactive CPU governors
> enabled user level voltage control (VDD sysfs interface)
use app like 'setxperia' or 'setvsel' to under/over volt device
> 128mhz - 1036mhz (more overclock in future version)
> Doomlord's Touch Based CWM recovery
> Doomlord's Boot Manager
> ZdZihu's xRecovery
Download Links
{ v 01 } Release Dt : 28 May 2012
DOWNLOAD PROBLEMS???
Please look in my signature for mirror links
A copy of files will ALWAYS be present on my ftp server, so use that if hotfile/devhost is not working for you
CREDITS
Huge thanks for the works and contributions of
Zdzihu, DoomLord, Bin4ry, Androxyde, Freexperia, Blagus, Defer, the_laser, th_jap
Major parts of ramdisk are taken from DoomKernel
DoomLords Touch Recovery is included
SOURCES
Sources for stock based kernel (fork from thgo)
Source for stock based kernel (fork from doomkernel)
Source for fxp based kernel (fork from freexperia)
reserved for later
reserved for later usage
kCernel STOCK R2 Test Releases
(note, wifi is broken on test2 )
TEST 1 > download
(from thgo sources, with linaro default cross compiler)
TEST 2 > download
(from doomkernel sources, with linaro default cc)
TEST 3 > download ftf || download wifi
(from stock gb sources, android toolchain)
TEST 4 > download ftf || download wifi
(from doom sources, with android toolchain cc)
NOTE:
Right now i just want to make sure which source tree and which cross compiler gives maximum battery.
Please test all test releases for a minimum period of 8-10 hours battery usage and post screenshots of the battery graph from about menu and if possible i would like to get CpuSpy screenshots too
Please mention which governor, cpu speed settings and io schedulers you are using
kCernel test log
Currently testing
[highlight]Flashed kCernel-SONY-r2-test1.tft[/highlight]
flashed kCernel-stock-r2-test2 with flashtool. On first boot entered xrecovery and
Cache wipe
Dalvik Cache wipe
Battery Stats wipe
Fixed Permissions
Rebooted enabled current widget app.
enabled logging to log chargeing times
.
[highlight]My standard ROM settings[/highlight]
[highlight]ROM[/highlight]
X10S v8.2 I have un-installed alot of stuff That i don't use
Battery.ZIP installed
CPU Master
Frequency range - 128MHz ~ 1190.4MHz
Scaling - smartassV2
I/O Scheduler - SIO (simple i/o)
Voltage - no under/over voltage changes made
ROM Toolbox
Auto memory manager - mild preset
SD Boost - 3072kb
[highlight]APP Killer[/highlight] - I do not use one, if I don't want it to run I use Titanium Backup to uninstall it.
no chance for locked BL?
after a couple hours of testing. here's my report, battery life is awesome, and it's stable and fast. so far no problems. here are a few screenshots. I'm running on the modified doom kernel, 1190-128, smartass v2, sio.
NoTnERb mate, i want to try! but i dont know what files should be download? locked BL user!
championswimmer said:
NOTE:
Right now i just want to make sure which source tree and which cross compiler gives maximum battery.
Please test all test releases for a minimum period of 8-10 hours battery usage and post screenshots of the battery graph from about menu and if possible i would like to get CpuSpy screenshots too
Please mention which governor, cpu speed settings and io schedulers you are using
Click to expand...
Click to collapse
Good to see you having a custom kernel but for battery testing i would recommend betterbatterystats to see the wakelocks and process using battery and also main thing is screen on time
botski said:
NoTnERb mate, i want to try! but i dont know what files should be download? locked BL user!
Click to expand...
Click to collapse
well, right now the kernels that champ posted are for unlocked boot loaders only. I know he's working on locked boot loaders so you'll have to wait
Is it possible for this kernel to be run on locked BL? I know I'm out by having a locked bootloader but I can't help it, my USB cable and USB port are broken and it's impossible to unlock my BL. It would be really appreciated if you could do so. Thanks.
Sent from my X10i using Tapatalk 2
sahibunlimited said:
Good to see you having a custom kernel but for battery testing i would recommend betterbatterystats to see the wakelocks and process using battery and also main thing is screen on time
Click to expand...
Click to collapse
here it is then
Hi,champ
glad to see kCernel is back
and really looking forward for kCernel for Debrand Engine v8
any way
every version of kCernel is awesome
sahibunlimited said:
Good to see you having a custom kernel but for battery testing i would recommend betterbatterystats to see the wakelocks and process using battery and also main thing is screen on time
Click to expand...
Click to collapse
i have it on my device but it'll be too harsh on testers to ask them to give analytical based on betterbatterystats
i just wanted a general user-perspective of battery life to decide which source tree i should use
Sent from my X10S using xda premium
championswimmer said:
i have it on my device but it'll be too harsh on testers to ask them to give analytical based on betterbatterystats
i just wanted a general user-perspective of battery life to decide which source tree i should use
Sent from my X10S using xda premium
Click to expand...
Click to collapse
Its best to just start that app once and without plugging in charger and after discharge dump a txt log from the app(menu>some option to save as a txt file on SD)
The wake locks are the main thing causing the drain because they wake up the CPU from deep sleep and don't let it go into deep sleep for long time causing drain
If their are some names of wake locks that you are not familiar with then use BBS app thread and you will get answer
Sent from my GT-I9100 using Tapatalk 2
btw champ, the thgo one was the one I tested before right? or is that a new one? also, any way we could get the wifi modules? thanks
wifi module for test1 is present in /module/ folder (copy using root explorer)
test2 has no wifi module. i forgot to compile it, now cleaned my source folder, no chance to compile again
test3 and test4 have separate wifi zips
@prodigy
that's what i am workin on right now
some bootloop issues are worrying me, other than that, it won't take much mroe time
test3 and test4 releases links up
championswimmer said:
@prodigy
that's what i am workin on right now
some bootloop issues are worrying me, other than that, it won't take much mroe time
Click to expand...
Click to collapse
Wow thankyou so much )
Sent from my X10i using Tapatalk 2
✰✰✰✰✰[KERNEL] DarkKnight v2.0 - THE END - (01/08)✰✰✰✰✰
DarkKnight KERNEL
Features:
Samsung ROM + MIUI + AOSP
JellyBean Support
Auto - Root
DM CWM Touch Recovery
Multiboot - Upto 6 ROM's
Kernel Updated to 3.0.36
XZ Kernel Compression
SLQB Memory Allocator
Boot Animation Support - [ /data/local & /system/media ]
CPU Freq Governors: lulzactive, ondemand, performance, powersave, smartassv2(default), userspace, pegasuq, conservative
I/O Schedulers: BFQ, CFQ, Deadline, SIO(default), No-op, V(R)
Undervolting already done
GPU Clock & Voltage Control
Charging Current Control
Touch Screen Sensitivity Fix
Increase TouchScreen Sensitivity
Fix fuel alert wakelocks
Frequency regulation based on screen on/off events
Add global min&max_suspend frequency variables
SpeedMod Color Profiles
Disable secondary cpu auto-hotplug when screen is off
Tegrak Second Core App Support
Smooth Scaling Interface
Improve CPU0 turnoff protection logic
Speedmod Sharpness Fix
Allow CPU-supported unaligned accesses
Brightness Curve MOD
Use ADB as root
Using OnDemand+Noop in Recovery for faster backup/restore
ARM Topology + Sched MC
Updated Mali Drivers
Joe's RCU
Kernel_HZ = 500HZ for smoothness
Toggle MDNIE Negative Effect with Home Button
Cleaner DMESG
Decreased LCD PowerOn delay
Lower Brightness for Low Light Conditions\
BootProgress Bar
Manual Method for Auto Brightness and Compass for AOSP Rom's - Refer steps below.
[*]Adjustable & Configurable Vibrator Interface
[*]Updated MMC Drivers with MMC_CAP_ERASE disabled
[*]BLN - Static
[*]Better Brightness & Gamma
[*]Updated Wifi Drivers
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changelog for v2.0:
Added JellyBean Support
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
Click to expand...
Click to collapse
2.0 CWM Zip
2.0 Odin Tar
Click to expand...
Click to collapse
How To Use Multiboot:
With v1.6 of DM Kernel for ICS, I introduce multiboot feature.
It is similar to the nandroid backup and restore function, but with a new menu and everything is done automatically
The menu is as follows:
Activate ROM
Backup ROM
Delete ROM
Inside each of this option we have 6 ROMs.
The steps to use Multiboot are as follows:
Install any ROM via the Install via Zip option. (Flash DM Kernel v1.9+)
Backup your ROM at any position as per your wish.
Install another ROM again via the Install via Zip option. (again flash DMv1.9+ and Up)
Backup that ROM at any position as per your wish.
Switch between ROM's using the Activate ROM option ( Backup your ROM each time before switching to another ROM)
Also I will try and automate more features.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
How To Switch Between Auto Brightness and Compass on AOSP ROM's:
Thanks to myfluxi, we now have support for Auto Brightness and Compass Mode on AOSP Rom's similar to xxfluxi kernel.
Steps to follow:
1) Download the Sensors.zip file from attachments.
2) Extract the files on sdcard.
3) If you want to have Auto-Brightness, then rename sensors.exynos4.so.os to sensors.exynos4.so
4) If you want to have Compass, then rename sensors.exynos4.so.prop to sensors.exynos4.so
5) Remember, you cannot have both
6) Copy that sensors.exynos4.so file to /system/lib/hw/ and reboot your phone.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Donations:
Hall of Fame
Juan Antonio Vermejo
Michael Foo
Brian Huijts
Yim Cheuk On
Marco Bouma
rkoby13
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you like my work, support it, please donate. I spend many hours behind developing and testing
and deep sleep lag here?
ionutz727 said:
and deep sleep lag here?
Click to expand...
Click to collapse
Works fine without any problems for me...With over 4000 downloads for the previous versions
Try and let me know
good kernel...
Going to try this! And hopefully using it on the next checkrom
ionutz727 said:
and deep sleep lag here?
Click to expand...
Click to collapse
Every kernel has deep sleep lag. Its just how it works I believe :-/.
Sent from my GT-I9100 using xda premium
awesome Kernel
how is the battery?
Cangir said:
how is the battery?
Click to expand...
Click to collapse
I'd like to know this too.
okay i have an issue here
im on RGUI MIUI (latest) i can't switch my keyboard language, and i can't switch to another keyboard.
i wiped cache and dlvk, i used cleaning script, i even reflashed the ROM.
i switched back to Siyah and everything went back normally.
i hope we can see a fix because i really love your work m8
OuT.Law said:
okay i have an issue here
im on RGUI MIUI (latest) i can't switch my keyboard language, and i can't switch to another keyboard.
i wiped cache and dlvk, i used cleaning script, i even reflashed the ROM.
i switched back to Siyah and everything went back normally.
i hope we can see a fix because i really love your work m8
Click to expand...
Click to collapse
a kernel surely cant bork your keyboard...
sakindia123 said:
a kernel surely cant bork your keyboard...
Click to expand...
Click to collapse
Exactly what i was thinking
Sent from my GT-I9100 using Tapatalk 2
So far so good.
I always liked your old Darkknight kernels on GB/CheckROM
Thanks keep up the good work.
so,now it work even on cm9/aokp rom's?
Finally this kernel for my AOKPs!
Well done mate
Still waiting for your building tuts
vivmar said:
so,now it work even on cm9/aokp rom's?
Click to expand...
Click to collapse
Yes
M90 said:
Finally this kernel for my AOKPs!
Well dona mate
Still waiting for your building tuts
Click to expand...
Click to collapse
TY
Sent from my GT-I9100 using Tapatalk 2
flashing on stock LPF
Like SIO @ def
After 4 hour No issues. Fast and stable with smartass V2 200 - 1000
is possible to ad in the custom recovery something to change Scaling and Scheduler without using 3rd party app?
wifi problems
Just flashed it on the Foxhound LPF and first thing I can report are the wifi issues.
It is not connecting to my wireless router WRT320N. It is connecting to an Asus 520WL.
Tried it several times, including re-entering the key, but wont connect to it. It doesnt reports any error, it just says Saved and nothing else happens.
Well, thats what happened, using siyah with miui I get no issues, but switching to DK my keyboard acts funny.
Thanks anyway m8
Sent from my GT-I9100 using XDA
spookyx said:
Just flashed it on the Foxhound LPF and first thing I can report are the wifi issues.
It is not connecting to my wireless router WRT320N. It is connecting to an Asus 520WL.
Tried it several times, including re-entering the key, but wont connect to it. It doesnt reports any error, it just says Saved and nothing else happens.
Click to expand...
Click to collapse
Yes a fix is coming...today night or max latest tomorrow
Sent from my GT-I9100 using Tapatalk 2
Alright guys, the time has come
As you already might have seen around here, I recently got this device and also started working on it.
Deep down in my heart I am more of a kernel dev than a ROM dev, which is why my first real contribution just had to be a kernel.
And not just any kernel, a wild one even: It's time to unleash the Werewolf in our tablet
As usual, my main goal is to get the best performance out of the device, especially for gaming.
I have been working with Tegra SoC's before, so I can probably make use of my previous experiences.
Now, enough with the chit-chat, time to look at the
Features
Patched CONFIG_KEYS vulnerability
CPU OC (up to 2.5GHz, default is stock 2.2GHz)
GPU OC (924MHz)
Custom I/O Schedulers (SIO, FIOPS, BFQ, CFQ, Deadline) with FIOPS as default
Ported ElementalX governor
[WIP] Added S2w and DT2W (experimental, not fully working --> use on your own risk!)
Added exFAT support
Added fsync toggle
KSM turned on by default with deferred timer
Added /dev/frandom support
Various TCP tweaks (enabled westwood as default TCP congestion control)
Requirements
MM bootloader and any MM ROM (should work on all ROMs running the MM kernel natively like CM13 or Bliss)
TWRP or any other custom recovery
fastboot environment
Installation
Download both the devicetree blob and the kernel zip
Boot into the bootloader and flash the DTB (fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb)
Boot into TWRP and install the zip
Reboot and feel the Werewolf's power
Bugs
S2W and DT2W not working when device is in deep sleep and touch may stop working when it was sleeping for too long
Direct download links
Werewolf_v001_anykernel-2016-01-25_1912.zip.zip
tegra124-tn8-p1761-1270-a04-e-battery.dtb
Feel free to look at this as a sneak-peek, I am far from done with getting the best out of this device
Please let me know what you think
XDA:DevDB Information
Werewolf Kernel, Kernel for the Nvidia Shield Tablet
Contributors
laufersteppenwolf
Source Code: https://github.com/laufersteppenwolf/android_kernel_nvidia_shieldtablet
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v001
Stable Release Date: 2016-01-25
Created 2016-01-25
Last Updated 2016-01-26
Testing, I'll let you know... Thnx!
Any reason why we can't just flash a zip version ? Just wont be at a computer anytime soon thats why
This is MM stock Nvidia K1 base
Is there a way to disable S2w and DT2W? I use the magnetic cover and don't need to double tap to wake.
KCKitsune said:
Is there a way to disable S2w and DT2W? I use the magnetic cover and don't need to double tap to wake.
Click to expand...
Click to collapse
Maybe you can use Kernel Adiutor to disable such options.
MrPhilo said:
Any reason why we can't just flash a zip version ? Just wont be at a computer anytime soon thats why
Click to expand...
Click to collapse
I had to raise the EDP limit as well as the freq table in the dtb in order to reach the oc freqs. You can try it without flashing the dtb, but I can't promise it'll work the way it should
KCKitsune said:
Is there a way to disable S2w and DT2W? I use the magnetic cover and don't need to double tap to wake.
Click to expand...
Click to collapse
Both features are disabled by default. If you want to try it out you'll have to enable it first
laufersteppenwolf said:
Both features are disabled by default. If you want to try it out you'll have to enable it first
Click to expand...
Click to collapse
Excellent. I'll give it a go and see how it works.
Is the battery a Lot weaker with this kernel and oc or is it the same?
Bit lost dev earlier the dtb flashed via fastboot no problems but i had to do a factory reset cause a was getting fcs but now its not working command write failed no such device or adress any ideas cheers
---------- Post added at 04:32 PM ---------- Previous post was at 04:31 PM ----------
skooter32 said:
Bit lost dev earlier the dtb flashed via fastboot no problems but i had to do a factory reset cause a was getting fcs but now its not working command write failed no such device or adress any ideas cheers
Click to expand...
Click to collapse
Edit using bliss rom mm
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
skooter32 said:
Bit lost dev earlier the dtb flashed via fastboot no problems but i had to do a factory reset cause a was getting fcs but now its not working command write failed no such device or adress any ideas cheers
---------- Post added at 04:32 PM ---------- Previous post was at 04:31 PM ----------
Edit using bliss rom mm
Click to expand...
Click to collapse
Edit done it now strange
I wish we had an dolphin version working on MM to try the werewolf
It works! But
So i installed it no problem cpu overclocks to 2.5GHz.
Kernel same page merging is fine .
Elemental x is great.
The the double tap to wake is buggy like it works once then stops working until i disable it then renable it.
My biggest problem is the same i have with EVERY SHIELD TABLET KERNEL YOU KERNEL DEVOLPERS CLAIM IS....... The gpu freq
You say its at 924 but the highest it goes in benchmarks and other apps is 540 and i cant overclock in kerner tuners like
Kernel auidtor
Device control
Kernel tuner
Etc....
All of them say no gpu tweaks.
I will like to point out i am running your kernel on the OG shield tablet not the new model but the old one running a version of android 6.0 that was converted from the new model shield to work on the og shield tablet stock rom so i thought ok lets try blisspop 6.0 and still nothing if you could be one of the first kernel modders to ACTUALLY get the the gpu to overclock and not give up or go quiet like the other kernel modders for this tablet then i swear the community for this tablet will make a satue of you because no one can seem to overclock this thing because they all give up but thanks anyways finally a 6.0 stock kernel that lets me overclock to 2.5ghz and secretly IVE ALAWYS wanted double tap to wake on this thing so if you could fix that as well id be super excited to donate
laufersteppenwolf said:
I had to raise the EDP limit as well as the freq table in the dtb in order to reach the oc freqs. You can try it without flashing the dtb, but I can't promise it'll work the way it should
Both features are disabled by default. If you want to try it out you'll have to enable it first
Click to expand...
Click to collapse
It's weird, because after testing I decided about no raising voltage in BitO-KX series (safety and eco criteria) and it seemed to be stable at max OC, but now I get RR at max freq with your kernel if I don't flash dtb, so I suspect Nvidia had readjusted something in MM kernel... Have you faced this?
Thnx for your great work.
Hi, first I'd like to say thank you for this kernel, I'm super stoked to try it. But I have some questions/fears to resolve first.
If I don't want to overclock do I still need to flash the dtb?
Is there a stock dtb that could be uploaded in case someone wants to revert to stock? Or would I be able to accomplish this simply by restoring a twrp backup?
Anyway, thanks again
Sent from my SHIELD Tablet K1 using Tapatalk
Working fast & smooth on Bliss v6.0. Thanks, laufersteppenwolf!
Nikownzyu said:
So i installed it no problem cpu overclocks to 2.5GHz.
Kernel same page merging is fine .
Elemental x is great.
The the double tap to wake is buggy like it works once then stops working until i disable it then renable it.
My biggest problem is the same i have with EVERY SHIELD TABLET KERNEL YOU KERNEL DEVOLPERS CLAIM IS....... The gpu freq
You say its at 924 but the highest it goes in benchmarks and other apps is 540 and i cant overclock in kerner tuners like
Kernel auidtor
Device control
Kernel tuner
Etc....
All of them say no gpu tweaks.
I will like to point out i am running your kernel on the OG shield tablet not the new model but the old one running a version of android 6.0 that was converted from the new model shield to work on the og shield tablet stock rom so i thought ok lets try blisspop 6.0 and still nothing if you could be one of the first kernel modders to ACTUALLY get the the gpu to overclock and not give up or go quiet like the other kernel modders for this tablet then i swear the community for this tablet will make a satue of you because no one can seem to overclock this thing because they all give up but thanks anyways finally a 6.0 stock kernel that lets me overclock to 2.5ghz and secretly IVE ALAWYS wanted double tap to wake on this thing so if you could fix that as well id be super excited to donate
Click to expand...
Click to collapse
First of all, how do you check the freq during the benchmarks?
I've been running antutu, and the GPU was properly using 924MHz (otherwise I wouldn't have said so)
Furthermore, you don't need to manually OC the GPU, it is OC'd by default simply because of the fact that no kernel tweaking app supported K1 GPUs up until now.
In the future the recommended app will be Device Control because that's what I am using myself. In the coming builds of DC, K1 GPU tweaks will be available there as I have added support for our GPU to Device Control: https://github.com/Evisceration/DeviceControl/commit/b2d4872869d1eda517c47588b83b6f3f895aaa01
DT2W and S2W are still on my list of course, and I'm sure the original shield will also be able to OC the GPU
BitOBSessiOn said:
It's weird, because after testing I decided about no raising voltage in BitO-KX series (safety and eco criteria) and it seemed to be stable at max OC, but now I get RR at max freq with your kernel if I don't flash dtb, so I suspect Nvidia had readjusted something in MM kernel... Have you faced this?
Thnx for your great work.
Click to expand...
Click to collapse
Hmm, no random reboots for me. I do have the dtb flashed, though. When do those reboots happen? During sleep, while playing,...?
Comparing the LP kernel to the MM kernel, quite a lot more stuff has moved into the dtb (like throttling, edp and power limits,...), which makes flashing the dtb even more important. Not sure, though, if they have also changed something regarding the actual voltage levels (except making it harder to add a proper UV interface).
Exile1975 said:
Hi, first I'd like to say thank you for this kernel, I'm super stoked to try it. But I have some questions/fears to resolve first.
If I don't want to overclock do I still need to flash the dtb?
Is there a stock dtb that could be uploaded in case someone wants to revert to stock? Or would I be able to accomplish this simply by restoring a twrp backup?
Anyway, thanks again
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Yes, flashing the dtb is always recommended.
No, TWRP does not make a backup of the dtb partition, I think I have a backup somewhere, though. I could upload it if needed
Ok so i check the freq in file manager system log you find more details about the benchmark like 3dmarks slingshot and whatnot so ok
I feel like an idiot could the reason be because i disnt flash the dtb? Because i forgot?
By the way i use AIDA64 and go to display the gpu goes from like 52 to 924 and i noticed while not using your kernel the maximum is like 824 witch is weird i could have SWORN on 5.0 stock kernel the maximum was 924 anyways it says it can go up to 924 but it stays at 524 i even run the device in max performance and run the benchmark and the app in MM's new multitask feature side by side and it stays at 524 while doing the most demading benchmark ever the 3dmark slingshot one also i benchmarked both using your kernel and not using your kernel and actually scored 80 points lower using yours (witch my highest is like 2480) but im sure this was because i didnt know kernel samepage merging was left on by default by the way is not good for benvhmarks obviously but good for games. But i will say the higher cpu overclock got me more fps in the CPU stress section of 3dmarks slingshot test (by the way all these tests are done on the 1440p one) basically what im getting at here is my device isnt overclocking but maybe thats because i didnt flash the dtb but i didnt think that mattered i will check back later after flashing it and seeing if my reaults are fortunate.
****EDIT**** so after flashing the dtb everything is still the same :/ what do you think im doing wrong is there any way i can send a system log or something i really want GPU overclocking
laufersteppenwolf said:
First of all, how do you check the freq during the benchmarks?
I've been running antutu, and the GPU was properly using 924MHz (otherwise I wouldn't have said so)
Furthermore, you don't need to manually OC the GPU, it is OC'd by default simply because of the fact that no kernel tweaking app supported K1 GPUs up until now.
In the future the recommended app will be Device Control because that's what I am using myself. In the coming builds of DC, K1 GPU tweaks will be available there as I have added support for our GPU to Device Control: https://github.com/Evisceration/DeviceControl/commit/b2d4872869d1eda517c47588b83b6f3f895aaa01
DT2W and S2W are still on my list of course, and I'm sure the original shield will also be able to OC the GPU
Hmm, no random reboots for me. I do have the dtb flashed, though. When do those reboots happen? During sleep, while playing,...?
Comparing the LP kernel to the MM kernel, quite a lot more stuff has moved into the dtb (like throttling, edp and power limits,...), which makes flashing the dtb even more important. Not sure, though, if they have also changed something regarding the actual voltage levels (except making it harder to add a proper UV interface).
Yes, flashing the dtb is always recommended.
No, TWRP does not make a backup of the dtb partition, I think I have a backup somewhere, though. I could upload it if needed
Click to expand...
Click to collapse
I didnt flashed the DTB and all is running fine and smooth without any reboots or something else. So my questions is Do I have to Flash it? @BitOBSessiOn said in his kernel thread that it is not necessary on the New mm bootloader. Thanks for your work!
Nikownzyu said:
Ok so i check the freq in file manager system log you find more details about the benchmark like 3dmarks slingshot and whatnot so ok
I feel like an idiot could the reason be because i disnt flash the dtb? Because i forgot?
By the way i use AIDA64 and go to display the gpu goes from like 52 to 924 and i noticed while not using your kernel the maximum is like 824 witch is weird i could have SWORN on 5.0 stock kernel the maximum was 924 anyways it says it can go up to 924 but it stays at 524 i even run the device in max performance and run the benchmark and the app in MM's new multitask feature side by side and it stays at 524 while doing the most demading benchmark ever the 3dmark slingshot one also i benchmarked both using your kernel and not using your kernel and actually scored 80 points lower using yours (witch my highest is like 2480) but im sure this was because i didnt know kernel samepage merging was left on by default by the way is not good for benvhmarks obviously but good for games. But i will say the higher cpu overclock got me more fps in the CPU stress section of 3dmarks slingshot test (by the way all these tests are done on the 1440p one) basically what im getting at here is my device isnt overclocking but maybe thats because i didnt flash the dtb but i didnt think that mattered i will check back later after flashing it and seeing if my reaults are fortunate.
****EDIT**** so after flashing the dtb everything is still the same :/ what do you think im doing wrong is there any way i can send a system log or something i really want GPU overclocking
Click to expand...
Click to collapse
Alright, so I just did exactly what you described: installed AIDA64 and it really does show 540MHz as max current freq with only AIDA open. Then I went on running sling shot and reading the freq via adb a couple of times during the bench and the freq was hopping between 756 and 924MHz just like it should:
Code:
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
924000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
756000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
924000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
756000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
756000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
924000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
924000000
[email protected]:/ # cat /sys/kernel/tegra_gpu/gpu_rate
756000000
Please check via adb as well while running the benchmark and let me know your findings
philipp21897 said:
I didnt flashed the DTB and all is running fine and smooth without any reboots or something else. So my questions is Do I have to Flash it? @BitOBSessiOn said in his kernel thread that it is not necessary on the New mm bootloader. Thanks for your work!
Click to expand...
Click to collapse
Yes you definitely should, especially when using OC freqs. The throttle tables are now stored within the device tree as well, which means the stock ones won't fit the current clock rates which could cause trouble once the devices tries to throttle down.
The DTB is needed regardless of the bootloader, they just have to match one another (LP bootloader and LP DTB vs MM bootloader and MM DTB)
Ok so tell me this if you have the time or backups have you tested the bench with and with out the kernel and i did what you did and whatta you know its overclocking BUT WHAT THE **** so why are we not seeing a performance increase? Is Aida the only reliable gpu checker lol are we being lied to by the system? If so? I wonder where does aida check its gpu freq i feel like going on an app system file ADVENTURE TO FIGURE THAT OUT i dont know maybe im expecting too much for gpu overclocking.
Might i have some suggestions for kernel additions? Like a simple line of code to automatically put in androids new mm multi window feature its buggy but can help ALOT for some stuff
Maybe research a zip called nitrox
Iteli plug so i dont have to use shields custom performance settings set the device at 2 cores to save power THEN go to device control and tick my freq
Most of of BitO's K features
I mention all these as your still the only 6.0 kernel for this tablet and yea i know you just released this kernel and i still love it but just some ideas you know
And GPU overclocking is still a priority