[KERNEL] | WildKernel v013 | Featurlicous | Tame Companion | January 29th
- Thread starter Emmanuel U
- Start date
-
- Tags
- development
I was going to ask if we can retrieve the file by restarting the device, and using something like root explorer to get it?
Edit: I used File Explorer to get it, but I'm thinking you have to do it before booting back into your device. I'm using Carbon and it still freezes up and reboots randomly.
Last edited:
I've noticed my phone charges noticeably slower with this kernel versus the stock Alpine kernel. Anything you can do? Awesome otherwise. Thanks!
kernel vs kernel
users of this kernel, please give me your opinion, which kernel is better this or the sultanxda v1.4.7?
users of this kernel, please give me your opinion, which kernel is better this or the sultanxda v1.4.7?
That depends.
If you use Sultan's kernel, you have to use his ROM. WildKernel works on several ROMS.
Two of the biggest features in Sultan's Kernel can be found in this kernel (CPUBoost, Screen Undervolt). This kernel is much more customizable than Sultan's kernel.
Stability seems to be a toss up. There are bugs in both kernels. I've had troubles with both kernels. Currently I use WildKernel because of Backlight Notification support and CPU governors (sometimes I have problems with ondemand). That and CarbonROM is much more to my liking than stock CM 11.
My advice: Try both and stick with the one that makes you happiest.
If you use Sultan's kernel, you have to use his ROM. WildKernel works on several ROMS.
Two of the biggest features in Sultan's Kernel can be found in this kernel (CPUBoost, Screen Undervolt). This kernel is much more customizable than Sultan's kernel.
Stability seems to be a toss up. There are bugs in both kernels. I've had troubles with both kernels. Currently I use WildKernel because of Backlight Notification support and CPU governors (sometimes I have problems with ondemand). That and CarbonROM is much more to my liking than stock CM 11.
My advice: Try both and stick with the one that makes you happiest.
Softbricked twice trying to install this kernel w/ LiquidSmooth Milestone.
The first time was on top of my in-use system (data and internal SD formatted as F2FS) using TWRP 2.8.1, the second time was with all partitions formatted back to EXT4, full wipe, and system reinstalled clean using TWRP 2.8.3.
Update: turns out the issue was my Internal Storage partition being F2FS the first round, which I "fixed" by reformatting to Ext4. This kernel didn't like that, but works fine now that I formatted Internal Storage as FAT.
The first time was on top of my in-use system (data and internal SD formatted as F2FS) using TWRP 2.8.1, the second time was with all partitions formatted back to EXT4, full wipe, and system reinstalled clean using TWRP 2.8.3.
Update: turns out the issue was my Internal Storage partition being F2FS the first round, which I "fixed" by reformatting to Ext4. This kernel didn't like that, but works fine now that I formatted Internal Storage as FAT.
Last edited:
Help please
Need your help with customizing. Im using your wild kernal with tame and would appreciate your input on optimizing my galaxy s2 as far as core and tweaks. Im only moderately tech savy and i dont know the optimal settings as far as mghz and such. Thank you for your help
Need your help with customizing. Im using your wild kernal with tame and would appreciate your input on optimizing my galaxy s2 as far as core and tweaks. Im only moderately tech savy and i dont know the optimal settings as far as mghz and such. Thank you for your help
He already has a recommend governor/scheduler section in the OP... Try those...
GS³: CyanideL + QuantumKernel Edition™
ギミチョコ！！
Need help i'm having the boot loop with KitKat kernels .I told about this issue to Sultan XDA ..and he replied as
Tell those kernel devs to fix their keypad driver:
[ 109.012786] Unable to handle kernel NULL pointer dereference at virtual address 0000001c
[ 109.012969] pgd = d5f14000
[ 109.013061] [0000001c] *pgd=5594e831, *pte=00000000, *ppte=00000000
[ 109.013458] Internal error: Oops: 17 [#1] PREEMPT SMP
[ 109.013580] Modules linked in: dhd vibrator frandom
[ 109.013977] CPU: 1 Not tainted (3.0.101-stock++ #1)
[ 109.014099] PC is at sec_keypad_enable_show+0x10/0x24.
[ 109.014282] LR is at dev_attr_show+0x1c/0x48...so find my problem here: http://xdaforums.com/galaxy-s2-tmobile/help/help-boot-4-3-roms-t2999362/post58093351#post58093351
I askes for a fix and he replied :
Your keypad hardware is slow to initialize at boot:
[ * *1.250640] [TKEY] get_touchkey_firmware F/W version: 0x0, Module version:0x0
[ * *1.250762] f/w read fail retry 6
[ * *1.250946] EXT_I2C No ACK
So some of the data structs in the keypad driver remain in a null state until keypad probe can complete. Some of that data is accessed before keypad probe on your specific device can finish (so it is dereferencing null data), thus crashing the kernel. It's being caused by the keypad-disabler feature, which my kernel does not have. Sorry, but I'm not really interested in fixing other people's kernels, so I can't help you with that..... Can u fix this for me plzz!!
Tell those kernel devs to fix their keypad driver:
[ 109.012786] Unable to handle kernel NULL pointer dereference at virtual address 0000001c
[ 109.012969] pgd = d5f14000
[ 109.013061] [0000001c] *pgd=5594e831, *pte=00000000, *ppte=00000000
[ 109.013458] Internal error: Oops: 17 [#1] PREEMPT SMP
[ 109.013580] Modules linked in: dhd vibrator frandom
[ 109.013977] CPU: 1 Not tainted (3.0.101-stock++ #1)
[ 109.014099] PC is at sec_keypad_enable_show+0x10/0x24.
[ 109.014282] LR is at dev_attr_show+0x1c/0x48...so find my problem here: http://xdaforums.com/galaxy-s2-tmobile/help/help-boot-4-3-roms-t2999362/post58093351#post58093351
I askes for a fix and he replied :
Your keypad hardware is slow to initialize at boot:
[ * *1.250640] [TKEY] get_touchkey_firmware F/W version: 0x0, Module version:0x0
[ * *1.250762] f/w read fail retry 6
[ * *1.250946] EXT_I2C No ACK
So some of the data structs in the keypad driver remain in a null state until keypad probe can complete. Some of that data is accessed before keypad probe on your specific device can finish (so it is dereferencing null data), thus crashing the kernel. It's being caused by the keypad-disabler feature, which my kernel does not have. Sorry, but I'm not really interested in fixing other people's kernels, so I can't help you with that..... Can u fix this for me plzz!!
Update
Stability update, enjoy. This will most likely be the final KitKat build.
Stability update, enjoy. This will most likely be the final KitKat build.
Similar threads
- Locked
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
56WildKernel
for T-Mobile Samsung Galaxy S II
Go check out Tame! It goes great with this and it handles OTA updates for this kernel.
This is a Linux based (3.0.101) Kernel which is maintained by me kept inline with the Cyangenmod Kernel so this is compatible with ALL the latest KitKat Roms (unless otherwise stated in the ROM).
Please report anything good and bad so that I know what to keep and what not to keep for the next release. This also helps me push out fixes faster when presented with lots of information (such as logs etc.).
Please see changelogs for an in-depth look at features. Also take a look at the screenshots for a sneak peek.
Feeling like a critic? Leave a review!
Link broken? Try one of the mirrors, Still a no go? Goto my signature and click the file backups link, then navigate to what you were looking for.
v013: AFH
TRU Mirrors: #1 / #2
All Releases: AFH | TRU Mirrors
[#WildKernel-Celox-CL]
[/HIDE]
Thanks:
TeamChopsticks & CyanogenMod
TeamSXL
Cl3Kener
Team Hydra
TeamDS
faux123
Sultanxda
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed
Info on Governors/Schedulers
You may find my source hosted @ Github
There is NO need to clear caches, kernel installer handles everything. Just flash and reboot.
My recommended Governor/Scheduler setups:
Did you read the announcement? (page header)
XDA:DevDB Information
WildKernel for the T-Mobile Galaxy S II (hercules), Kernel for the T-Mobile Samsung Galaxy S II
Contributors
Emmanuel U
Source Code: https://github.com/EmmanuelU/wild_kernel_samsung_msm8660/tree/android-msm-hercules-3.0
Kernel Special Features: Too many features to list, just install it.... now.
Version Information
Status: Stable
Current Stable Version: 013
Stable Release Date: 2015-01-29
Created 2014-05-28
Last Updated 2015-02-0117A lil progress
I finally had time to do some kernel work (been so busy last few weeks), and I managed to get CyanogenMod booting and stable with the 009 (I built CM from source alongside WildKernel). This is a good sign, however when I extract the same boot.img to flash on other latest roms I still get the same issue. Still workin on it :good:
15Update
v007 is out and this is one is has a numerous instability patches, that plagued previous versions...go check it out! Enjoy this one as future versions will include a lil extra present *cough* *cough* custom app for WildKernel *cough* *maybe* *cough*1411v003 and v004 Beta updated for Android 4.4.4
Small but much needed update for the kernels today. 003 and 004 beta now have support for Android 4.4.4, aswell as other previous 4.4 versions.
I recommend only using the v004 beta if you experience graphical issues with v003, otherwise I recommend v003 as it has better battery life (initial kernel base). I'll have it in this format until I can create/kang a kernel base that is stable for all while maintaining the original battery life that you can get with the current v003 (assuming you don't have a sh*tty battery
). Good day guys.
New posts
-
-
-
[ROM][14][KSU][OP7Pro] crDroid v10.4 [22.04.2024]
- Latest: Dylan Hameleers
-
