rj's custom kernel for Galaxy Player 5 international
aka rumirand
Hi there.
Finally got my YP-G70 back to life, so I'm working on get a better kernel and take advantage of this device. This kernel is based on stock G70XXKPF firmware, but some users report it works on other firmwares.
If you have a G70 US (capacitive home button), use Entropy512's kernel. If you have a 4.0, use Steves kernel.
Features
2.6.35.7 source for GingerBread.
Unsecure mode.
Swap support.
Overclock to 1.2Ghz and undervolt capabilities (use SetCPU or another software for UV).
Added lazy (default), interactive, interactiveX, smartassv2, ondemandX governors.
Added BFQ, V(R) and SIO (default) schedulers.
Init.d support.
Added statically linked busybox 1.19.3 (/sbin)*.
Modified adbd (pointing shell to /sbin/sh), so you can use adbd even if you don't have any partition working*.
ext4 support (ghetto lagfix).
ClockWorkMod (beta). Nandroid backup - restore works, mount/umount, format (formats to ext4).
You can boot in stock recovery placing /cache/.stock_recovery file (In terminal, just do 'touch /cache/.stock_recovery'), and reboot to recovery.
CIFS support.
jhash3.
SoD patch from netarchy/coolbho3k.
TinyRCU.
netarchy's conservative tuning patch.
Custom bootanimation support (/system/media/bootanimation.zip) from Entropy512's kernel.
Per-File fsync() disable - For info, look here.
Charginghacks from Entropy512.
*Useful for recovery/unbrick purposes. My device got bricked and got the partition table faulty. With this, you can rebuild your partition table using fdisk.
Changelog
Code:
r14
- Changed overclock patch (now Entropy512 based)
- BNEP enabled by kernel.
r13
- Add Charginghacks from Entropy512's kernel.
r12
- Overclock to 1.2 Ghz and UV capabilities.
r11
- Switch source code to YP-G70 US (this fixes the SoD patch issue).
- SoD patch reapplied.
- Custom bootanimation support thanks to Entropy512.
r10
- Battery drain fixed.
- Added latest patches/fixes from Entropy512's source code. Take a look at his Github.
r9
- Tentative fix for battery drain problem. Please provide some feedback.
r8
- Added V(R) scheduler.
- Added CIFS.ko.
- jhash3.
- TinyRCU.
- SoD patch.
- Conservative tuning patch.
r7
- Fixed backing up/restoring /dbdata.
- Added ability to backup/restore to internal storage and external sdcard.
r6
- Added ext4 support.
- Added CWM. Nandroid backup - restore works (/system, /data, /cache, kernel and recovery), mount/umount, format (formats to ext4).
r5
- Added ondemandX and interactiveX governors.
- Minor fixes on unsecure mode.
r4
- Added SIO scheduler (default).
- Added support for init.d scripts.
- Radio FM works now.
- Added statically linked busybox 1.19.3 (/sbin)*
- Modified adbd (pointing shell to /sbin/sh)*
r3
- Added cpufreq governors: interactive, smartassv2 and lazy (default).
- Added BFQ I/O scheduler -> to activate it, use some app like CPU Master.
r2
- 2.6.35.7 kernel from GB source.
- Unsecure mode.
- Swap support.
- Get config from /proc/config.gz
- Stock G70XXKPF ramdisk.
r1
- Initial upload -> doesn't work.
Download:
Kernel r14 (Odin) - Kernel r14 (CWM)
Kernel r13 (Odin) - Kernel r13 (CWM)
Kernel r12 (Odin) - Kernel r12 (CWM)
Kernel r11 (Odin) - Kernel r11 (CWM)
Kernel r10 (Odin) - Kernel r10 (CWM)
Kernel r9 - CWM beta
Kernel r8 - CWM beta
Kernel r7 - CWM beta
Kernel r6 - CWM beta
Kernel r5
Kernel r4
Kernel r3
Kernel r2 <- first working kernel.
Initial upload (r1) <- doesn't boot. So don't bother to flash it.
Installing:
Odin:
Download kernel from site.
Get your device in download mode (device turned off, press vol down key, plug the usb cable.
Open Odin3.
Select kernel file in PDA section.
Keep the rest Odin settings untouched (make sure re-partition, phone bootloader update and EFS clear aren't checked).
Start.
CWM:
Download kernel from site.
Place .zip file in /sdcard/external_sd/.
Reboot in recovery mode.
Choose install zip from sdcard.
Reboot.
Enable ghetto lagfix:
FIRST: MAKE SURE YOU HAVE AL LEAST 12MB OF FREE SPACE ON /SYSTEM PARTITION
Enter in recovery mode (CWM).
Do a full Nandroid backup.
Reboot your device.
Change .rfs.tar files in clockworkmod/backup/xx.xx.xx/ to .ext4.tar.
Edit nandroid.md5 to match .ext4.tar files.
Enter in recovery mode (CWM).
Do a full restore.
Reboot (you'll probably have some FCs, I got in GMaps and Market, just delete application's data/reinstall it).
If you want to go back to rfs, revert the steps.
Uninstalling:
Download stock XXKPF kernel here.
Flash it following the same instructions above.
Big thanks to Entropy512 for working in a CWM port for our devices and his kernel. This work is based on his job.
Source code available on my GitHub
Any suggestion/idea is welcome.
Do it at your own risk. I'm not responsible if any damage is done to your device.
Is this a Froyo or GB kernel? The kernel on my device has version 2.6.35.7 (GB 2.3.5). Apart from this, is there a way to backup the existing kernel before testing the development kernel. Thanks!
WT Ho said:
Is this a Froyo or GB kernel? The kernel on my device has version 2.6.35.7 (GB 2.3.5). Apart from this, is there a way to backup the existing kernel before testing the development kernel. Thanks!
Click to expand...
Click to collapse
Ok, first of all, I finally got my Galaxy Player working (thanks thanks for the dump you provided me)! So the next releases will be tested before uploading it.
For backup the kernel, the best to do is open the firmware .tar o .tar.md5 file and extract zImage file. Then, in linux, you can do:
Code:
tar cf zImage.tar <path-to-zImage>
You will get a .tar file containing only the kernel, flashable from odin3.
Don't bother testing the initial upload, it won't boot.
It looks to me like /dev/block/mmcblk0p11 and /dev/block/mmcblk0p12 contain the kernel and recovery kernel, therefore one could do the following to back up the partition:
Code:
dd if=/dev/block/mmcblk0p11 of=/sdcard/zImage-partition bs=4096
lardman said:
It looks to me like /dev/block/mmcblk0p11 and /dev/block/mmcblk0p12 contain the kernel and recovery kernel, therefore one could do the following to back up the partition:
Code:
dd if=/dev/block/mmcblk0p11 of=/sdcard/zImage-partition bs=4096
Click to expand...
Click to collapse
You're right. That's an alternative mode to backup kernel and recovery. You can even flash directly a kernel by dumping a zImage file (unpacked) to mmcblk0p11. I haven't done this myself, but it should work.
rumirand said:
You will get a .tar file containing only the kernel, flashable from odin3.
Don't bother testing the initial upload, it won't boot.
Click to expand...
Click to collapse
That's a good start already. We will wait for the next one.
Can you update the starting post with some information and make a note that the initial upload doesn't work.
Let us know what version of the kernel are you using.
Bump.
r2 is up and working.
Bump.
r3 is up and working. See changelog for details.
Do you have any plans to make an overclock kernel?
bdds13 said:
Do you have any plans to make an overclock kernel?
Click to expand...
Click to collapse
Yes. It's only changing some lines of the source code. Will test later today/tomorrow.
I'll upload it when it's done.
Thanks a lot!
Just flashed it. No major issues so far, will continue to use and see if I found anything unusual. Here are the versions reported on my device
Model number: YP-G70
Firmware version: 2.3.5
Kernel version 2.6.35.7-G70XXKPF-CL562492 [email protected] #rj's
Build number GINGERBREAD.ZSKP8
It should be noted that I am not flash the kernel on XXKPF firmware but ZSKP8 but it still works.
See also the screenshot attached.
rumirand said:
Yes. It's only changing some lines of the source code. Will test later today/tomorrow.
I'll upload it when it's done.
Click to expand...
Click to collapse
Tegrak Overclocking app can already overclock the stock kernel, will this introducing something not available in Tegrak? May be we can add a few more speed levels? Currently the stock kernel only has 1GHz, 800MHz, 400MHz, 200MHz and 100MHz.
WT Ho said:
Tegrak Overclocking app can already overclock the stock kernel, will this introducing something not available in Tegrak? May be we can add a few more speed levels? Currently the stock kernel only has 1GHz, 800MHz, 400MHz, 200MHz and 100MHz.
Click to expand...
Click to collapse
Only we would gain more speed levels. Tegrak does well the job in overclocking/undervolting and I think it's a clean solution (every user can choose if only wants overclocking/undervolting and how far wants to go).
I've overclocked my device to 1.5ghz, only slight overvolt needed at that frequency. Did undervolting too. Runs stable.
I'll see if I can port voodoo lagfix on this device.
Thanks for posting this..would love to try out..
I am already on 2.6.35 by flashing the kernel posted in this forum..official one since mine came with Android 2.1
Is yours without all the Samsung features such as icon shape, interface etc? Can that be removed to use raw Gingerbread?
chen2008 said:
Thanks for posting this..would love to try out..
I am already on 2.6.35 by flashing the kernel posted in this forum..official one since mine came with Android 2.1
Is yours without all the Samsung features such as icon shape, interface etc? Can that be removed to use raw Gingerbread?
Click to expand...
Click to collapse
This is only the kernel. The other things are in the rom. So, the icons, touchwiz UI aren't related to the kernel.
This kernel is great running smartassv2 and using Tegrak Overclocking app to over-clock to 1.3ghz and battery life is great and its very fast. thanks
Rueben_ said:
This kernel is great running smartassv2 and using Tegrak Overclocking app to over-clock to 1.3ghz and battery life is great and its very fast. thanks
Click to expand...
Click to collapse
How it does perform for you the lazy governor? For me seems to be more battery lifesaver than smartassv2 but in performance I don't know.
rumirand said:
How it does perform for you the lazy governor? For me seems to be more battery lifesaver that smartassv2 bit in performance I don't know.
Click to expand...
Click to collapse
I will run smartassv2 for a couple of hours then lazy and see if i notice a difference i will post again tonight. In uk its only 1:00pm lol
Edit: Used lazy now for about 2 hours and battery has gone done about 3% compared to smartassv2 6% doing more or less the same tasks thanks again.
i have 2 questions..
1. does it come with camera/compass/sound fix?
2. is this upgradeable rom or wipe rom?
thanks in advance.
Related
This is my kernel, it's based on stock SE and Sony's kernel sources, with some things from DoomKernel by DooMLoRD (so go and say thanks to him, and other developers too).
It has:
- Overclock up to 2Ghz
- CWM Recovery 5.0.2.7
- Prerooting
- CPU Governors:
brazilianwax
smoothass
smartassV2
SavagedZen
interactiveX
lagfree
minmax
Scary
smartass
interactive
conservative
userspace
powersave
ondemand
perfomance
v2 added:
- Xperia Mini support
- Tun/tap interface enabled (VPN, ipv6)
- Swap support enabled
- Two way call recording support added
- I/O schedulers:
noop
anticipatory
deadline
cfq
bfq
vr
sio
v2.1 changed:
- disabled NFS and CIFS (battery drain fix from DoomKernel), let's see if it can really increase battery life.
v2.2 changed:
- moved to from 4.0.2.A.0.58 to 62 source, though I didn't see any changes
- added 0% battery workaround patch by Bazoocaze. I don't even know what it does but it seems to be something useful since everyone includes this in their kernels
- New cpufreq driver from DoomKernel. You can experience some problems with overclocking now (my phone becomes unstable at 1.8GHz now, instead of 2.0), but phone eats much less battery in sleep. I've also changed 1018Hz to 1024Hz and 249Hz to 245Hz because those new numbers looked wierd
v2.3 changed:
- moved back to 4.0.2.A.0.58 source (just to make sure that everything will work).
- updated version number in ramdisks to 62.
- removed 0% battery workaround patch (it's useless on our devices).
- reverted old cpufreq driver with small fix. It should be stable now and phone seems to eat less battery than in 2.1. (thanks himasura for lots of testing)
- salvaged some ram.
- enabled NTFS support.
- enabled usb-storage driver, so you don't need to manually load usb-storage.ko now.
- Version number now shows version of kernel (#23=2.3).
v2.4 changed:
- Now phone lights up blue led to show when you can enter recovery (thx to DooMLoRD).
- Minor changes in ramdisks.
- Enabled hid drivers for microsoft and a4tech.
v2.5 changed:
- Re-added CIFS
- Enabled ext4 support
- Added zram and cleancache drivers
- Added lulzactive governor
- Root fs now mounts as rw after boot.
v2.6 changed:
- removed lulzactive governor as it wasn't working properly (thx to kamarush and others for pointing that)
v2.7 changed:
- moved to sony 4.0.2.A.0.74 kernel sources (updated touchscreen driver)
- Increased GPU dedicated memory to 4MB
- Updated su binary in autoroot.
v2.8 changed:
- added new cpufreq driver at last (with CPU frequency fixup by DooMLoRD), battery drain is lower now. I left version 2.7 too for those who want higher overclock or have some problems with 2.8.
v2.9 changed:
- fixed governors to match new frequency table. Test please.
v3.0 changed:
- updated zram driver.
- staging:lowmemkiller add Fugeswap.
- ICS and GB versions.
v3.1 changed:
- [ICS] Updated recovery to DooMLoRD's ICS version and as a result fixed usb mounting issues in recovery. The recovery will say that it's for arc, but don't worry, it woks fine on our phones.
- [GB] No release, everything works fine there
v3.2 changed:
- [ICS] Upadated recovery again, fixed booting issues. It's recovery by kamarush now , so thanks a lot to him.
- [GB] No release.
Everything else is similar to stock kernel for now.
Requirements:
For 2.3.4 version: 4.0.2.A.0.42/58/61/62/74 rom.
For 4.0.4 version: 4.1.B.0.431 rom.
Unlocked bootloader.
Installing:
If you're using windows, here's the simpliest way to install kernels:
Install drivers.
Download and extract these files to some folder.
Place boot.img to the same folder.
Execute flash.cmd.
Turn off your phone, hold volume up button and connect it to pc.
When everything is ready close cmd window and turn on the phone.
If something is wrong try "advanced/wipe dalvik cache" in recovery.
Useful scripts:
Here are some useful scripts which work with this kernel. Just download, extract and copy them into "/etc/init.d" folder:
This kernel doesn't have zram enabled by default. Use this to enable 64mb zram swap:
https://yadi.sk/d/-0kzYZOs3KETHm
Our phones have a lot of free space in "/cache" partition, so you can use script by inteks to create a 64mb swap there. It is much faster than using SD card:
https://yadi.sk/d/Nhkogctl3KETJW
The same with "/system". Here's a bit modified version of previous script, the only change is that it uses another partition:
https://yadi.sk/d/C7gVW-oH3KETK8
Important information:
If you used KRsH Kernel or X kernel before you need to restore /system/lib/modules/ with stock files. Or just simply flash this: View attachment signed-mango_stock_modules.zip (2.3.4) or this View attachment ics_wifi_modules-signed.zip (4.0.4) via recovery.
If you're using 4.0.4 version and have used other custom kernels before I also recommend you deleting "/system/autorooted" file, so that busybox could be reinstalled properly.
Entering recovery:
While booting, wait until blue led lights up and press volume down button to enter recovery.
Building kernel:
If you're a developer, feel free to download kernel sources from GutHub and change whatever you like:
Install some Linux distribution (Tested on Linux Mint Debian and Ubuntu 10.04).
Download everything using git or by clicking "Download as tar.gz" on github.
Place files in some folder (path mustn't contain spaces).
Make your changes.
Execute build-all.sh to build kernel for all devices or use build-[model].sh for one device.
Download:
Android 4.0.4 version
Rage Kernel v3.2 [Mini Pro]
Rage Kernel v3.2 [Mini]
Rage Kernel v3.2 [Live With Walkman]
Rage Kernel v3.2 [Active]
Android 2.3.4 version
Rage Kernel v3.0 [Mini Pro]
Rage Kernel v3.0 [Mini] (fixed)
Rage Kernel v3.0 [Live With Walkman]
Rage Kernel v3.0 [Active]
Rage Kernel v2.7 [Mini Pro]
Rage Kernel v2.7 [Mini]
Rage Kernel v2.7 [Live With Walkman]
Rage Kernel v2.7 [Active]
DuMOHsmol said:
Since I'm new to these forums, I can't post in development section, hope someone will move this thread.
This is my kernel, it's based on stock SE 4.0.2.A.0.58 kernel sources, with some things from DoomKernel and KRsH Kernel.
I'm new to kernel development, so there could be some bugs.
It has:
- Overclock up to 2Ghz
- CWM Recovery 5.0.2.7
- Prerooting
- CPU Governors:
brazilianwax
smoothass
smartassV2
SavagedZen
interactiveX
lagfree
minmax
Scary
smartass
interactive
Everything else is similar to stock kernel for now.
Note that there is working usb-otg support from stock kernel (it seems to be broken in KRsH kernel, that's mainly why I've made my own).
Requirements:
4.0.2.A.0.58 rom
Unlocked bootloader
Fastboot
Put kernel to fastboot folder and use fastboot flash boot boot.img to flash it.
If you used KRsH Kernel before, you also need to restore /system/lib/modules/ with stock files.
While booting, press continuously the volume down button to enter recovery.
If you're a developer, feel free to download kernel sources (narod.ru/disk/34772141001/ragekrenel.tar.gz.html) and change whatever you like. Just unpack and execute buildse.sh to compile kernel and create boot.img (tested on Linux Mint Debian).
Click to expand...
Click to collapse
really thank you for your great work ,but would you develop a kernel that can fit mini st 15i based on 0.58 or 0.61 please? thank you
but we still haven't got .58 or .61 on ST15i
metalrawk said:
but we still haven't got .58 or .61 on ST15i
Click to expand...
Click to collapse
0.42 also sounds good!!!!
Bump. Can anyone move this to correct thread? Speaking of Xperia Mini support, I may add it on these weekends.
DuMOHsmol said:
If you used KRsH Kernel before, you also need to restore /system/lib/modules/ with stock files.
Click to expand...
Click to collapse
can you share it please? i have no backup
Just flash the stock rom again.. well that's what I did. I used Android Commander to back everything up first so I didn't have to install everything seperately then just installed everything through windows 7 in one hit.
The ROM seems to be working ok. Have only been using it for a few hours
Dear DuMOHsmol,i think you need to post more,so you can post on development thread
xpawx.o0o said:
Just flash the stock rom again.. well that's what I did. I used Android Commander to back everything up first so I didn't have to install everything seperately then just installed everything through windows 7 in one hit.
The ROM seems to be working ok. Have only been using it for a few hours
Click to expand...
Click to collapse
I have some modifications in the system and no backup programm will restore this with 1 click.
Just help me and upload the modules
Sent from my SK17i using Tapatalk
Here are stock modules, flash via recovery:
Many thanks DuMOHsmol! Could you add support for voice call recording 2-way-call-recording.googlecode.com/svn/ and BFQ scheduler?
New version. Added io schedulers, voice recording, xperia mini support, swap support, tun/tap interface.
can't wait.
thank u.
Sent from my S51SE using xda premium
Thank You for your hard work.
Any Battery Issue
Can someone pls test & post reply About bettery.
Stuck at sony ericsson logo. (Boot Loop)
I had flashed KRsH kernel with HYBROM v4 Rom was working good until
I flashed this kernel & was trying enter CWM to update mango signed files
but unfortunately I could not enter.
So reverting back to KRsH with HYBROM v4.
IMRAND said:
Stuck at sony ericsson logo. (Boot Loop)
I had flashed KRsH kernel with HYBROM v4 Rom was working good until
I flashed this kernel & was trying enter CWM to update mango signed files
but unfortunately I could not enter.
So reverting back to KRsH with HYBROM v4.
Click to expand...
Click to collapse
You have mini or mini pro?
I have xperia mini pro sk17.
Iam Doing any steps wrong pls confirm.
---------- Post added at 01:18 PM ---------- Previous post was at 01:08 PM ----------
Also pls confirm what is the major difference between your & KRsH Kernel
should continue with the same KRsH or should I try to flash this one.
This can't be moved to the Development forum yet.
The OP needs at least 10 posts, or he won't be able to post anything in the thread.
Once the OP gets 10 posts, please ask a mod to move it to the Development forum
IMRAND said:
I have xperia mini pro sk17.
Iam Doing any steps wrong pls confirm.
---------- Post added at 01:18 PM ---------- Previous post was at 01:08 PM ----------
Also pls confirm what is the major difference between your & KRsH Kernel
should continue with the same KRsH or should I try to flash this one.
Click to expand...
Click to collapse
That's strange, it works fine on my SK17i. Maybe the problem is in custom rom?
Does stock kernel work?
Speaking of KRsH kernel, it seems to be DoomKernel ported to our phones (although I'm not sure about this), while mine is based on stock kernel with just some tweaks from DoomKernel.
There is working usb-otg support in Rage Kernel, and also voice call recording support. Also someone claim that KRsH kernel drains battery too fast, though I didn't have any problems with it.
BTW Kamarush absolutely dosnt approve this kernel.
From private:
-"And i don't give a word on Rage kernel... Because he didn't got permission to use OUR modules, and kernel sources...."
This is Rage Kernel v2.9 for Xperia Mini / Mini Pro / Active / Live recompiled to run on FXP CM7.2.0 ROM from Freexperia Project here.
The boot image consists of kernel compiled from DuMOHsmol's Rage Kernel v2.9 source, FXP wi-fi driver and FXP ramdisk. It is tested running in FXP122 CM7.
The kernel is compiled using FXP default config, modified to enabled added features in Rage Kernel, so overall the features is similar to Rage Kernel v2.9 (see post #2 below)
Credits:
Many thanks to DuMOHsmol for Rage kernel source and DoomLord for providing the base/stock source.
Thanks for Freexperia Team for making such a great rom.
Thanks for wucinac, HUdasp, gandhar, Snoopo, & jakobxxl for initial testing and feedbacks.
This kernel will not be updated everyweek like FXP rom releases. It would only be updated if there's update in Rage Kernel or there's update in FXP ramdisk/ROM that requires changes in this kernel too.
I mainly compiled this kernel because it gives good battery life, so I haven't tested all features that Rage Kernel offer. Therefore I can't really confirm that those added features will work fine in CM7. What does work is the basic functionalities (like calls, wifi, bluetooth, camera, etc) and added cpu governors, overclocking options, and added i/o schedulers. What I haven't test: zram and swap.
And because I personally considered this kernel as some kind of a workaround for the battery drain issue in fxp kernel (see post #3 below), then if FXP team has fixed it, this kernel might be no longer needed.
As of version 2.6, changes from original Rage Kernel source are below:
4 files in Rage source replaced with files from FXP source :
- arch/arm/mach-msm/board-semc_mogami.c
- arch/arm/mach-msm/sdio_ctl.c
- drivers/mfd/marimba-codec.c
- drivers/misc/lm356x.c
Files sdio_ctl.c and marimba-codec.c is replaced to avoid compiling errors when using fxp defconfig. The file board-semc_mogami.c is replaced to fix touchscreen problem when using original file. File lm36x.c is replaced to fix force close problem in Torch app.
Another change is patch from here applied to fix the touchscreen issue.
Changes in version 2.7 are included as a patch files in the download post below.
Changes in version 2.8 & 2.9 are related only to cpufreq driver & cpu governors, so the patch from 2.7 can still be used, but the cpufreq part of the diff must be removed.
Version 2.7 / 2.8 / 2.9:
Please see all download links for Mini/Mini Pro/Active/LiveWithWalkman in this #75 post.
Flashing disclaimer applies! Use this kernel at your own risk.
How to use:
1. For the first time CM7 users: Flash the Freexperia CM7 kernel & Rom first, and make sure everything works fine, and then continue to step 2. For those that already have CM7 running, just begin at step 2.
2. Flash this kernel using fastboot.
3. Reboot to CWM and wipe cache
4. Reboot again.
Notes :
- This kernel is not supported in anyway by FXP team or original Rage maintainer DuMOHsmol. Anyone having problem, please don't ask them for support. Just ask in this thread & I'll try to figure it out.
- Battery life is not solely affected by the kernel. It can also be affected by apps/mods/tweaks used or applied in the rom. If battery drain is high, then please check what cause the wakelocks using apps like BetterBatteryStats here
- There are instances that using Google Maps or Latitude (or maybe other gps-related apps) would cause GpsLocationProvider keeping the phone awake, like the case in this post #82 and post #34. This situation can be diagnosed using that BetterBatteryStats app mentioned above. The workaround is to disable gps and reboot the phone.
- Of course, other than advantages, there are also disadvantages using this kernel in FXP cm7. Advantages including: a bit better battery life, more cpu governors, more i/o schedulers, etc. Disadvantages: I perceive sdcard i/o is somewhat slower, sometimes there's lag in video recorder, there might be broken features in future FXP releases, not supported by FXP team, and there might be other problems that haven't been encountered yet. If anyone experiencing more disadvantages than advantages using this kernel, then please consider using FXP kernel instead.
Features (quoted directly from DuMOHsmol's Rage Kernel original post here ) :
DuMOHsmol said:
This is my kernel, it's based on stock SE 4.0.2.A.0.74 kernel sources, with some things from DoomKernel by DooMLoRD (so go and say thanks to him, and other developers too).
It has:
- Overclock up to 2Ghz
- CWM Recovery 5.0.2.7
- Prerooting
- CPU Governors:
brazilianwax
smoothass
smartassV2
SavagedZen
interactiveX
lagfree
minmax
Scary
smartass
interactive
conservative
userspace
powersave
ondemand
perfomance
v2 added:
- Xperia Mini support
- Tun/tap interface enabled (VPN, ipv6)
- Swap support enabled
- Two way call recording support added
- I/O schedulers:
noop
anticipatory
deadline
cfq
bfq
vr
sio
v2.1 changed:
- disabled NFS and CIFS (battery drain fix from DoomKernel), let's see if it can really increase battery life.
v2.2 changed:
- moved to from 4.0.2.A.0.58 to 62 source, though I didn't see any changes
- added 0% battery workaround patch by Bazoocaze. I don't even know what it does but it seems to be something useful since everyone includes this in their kernels
- New cpufreq driver from DoomKernel. You can experience some problems with overclocking now (my phone becomes unstable at 1.8GHz now, instead of 2.0), but phone eats much less battery in sleep. I've also changed 1018Hz to 1024Hz and 249Hz to 245Hz because those new numbers looked wierd
v2.3 changed:
- moved back to 4.0.2.A.0.58 source (just to make sure that everything will work).
- updated version number in ramdisks to 62.
- removed 0% battery workaround patch (it's useless on our devices).
- reverted old cpufreq driver with small fix. It should be stable now and phone seems to eat less battery than in 2.1. (thanks himasura for lots of testing)
- salvaged some ram.
- enabled NTFS support.
- enabled usb-storage driver, so you don't need to manually load usb-storage.ko now.
- Version number now shows version of kernel (#23=2.3).
v2.4 changed:
- Now phone lights up blue led to show when you can enter recovery (thx to DooMLoRD).
- Minor changes in ramdisks.
- Enabled hid drivers for microsoft and a4tech.
v2.5 changed:
- Re-added CIFS
- Enabled ext4 support
- Added zram and cleancache drivers
- Added lulzactive governor
- Root fs now mounts as rw after boot.
v2.6 changed:
- removed lulzactive governor as it wasn't working properly (thx to kamarush and others for pointing that)
v2.7 changed:
- moved to sony 4.0.2.A.0.74 kernel sources (updated touchscreen driver)
- Increased GPU dedicated memory to 4MB
- Updated su binary in autoroot.
v2.8 changed:
- added new cpufreq driver at last (with CPU frequency fixup by DooMLoRD), battery drain is lower now. I left version 2.7 too for those who want higher overclock or have some problems with 2.8.
Everything else is similar to stock kernel for now.
Click to expand...
Click to collapse
A bit background:
I use FXP CM7 rom for my mini pro since release 049 and like it very much. One thing that made me keep switching back to stock rom was the high battery drain, because in my daily activities electric plug is not always readily available, so battery life is critical for me.
In fxp 052 I got a bit desperate and trying to use custom kernel based on stock from bbooff here, with fxp rom. The battery life is excellent, just like stock rom, but I encountered 2 problems: touchscreen sometimes become unresponsive and wifi was not working (even if I replaced wifi modules with stock).
Finally, I decide to learn how to compile android kernel, and I found that it is quite similar with compiling linux kernel, which I've frequently done to my computer and laptop.
So, I compiled kernels from 3 sources and compare the battery life in my mini pro. They are from DoomLord's official SE source, DuMOHsmol's Rage kernel source, and krizky82's X Kernel source. I also recompiled kernel from FXP kernel source using stock semc_mango_defconfig, to see if battery life is better. The conclusion is that best battery life is achieved using stock and Rage Kernel, and I've been using FXP with rage kernel since release 102 and haven't considered going back to stock rom again.
I posted in Rage Kernel thread to thank DuMOHsmol, and since then there's 3 xda members that ask me to share this kernel, so I make this thread.
I hope this could help those who want to use FXP CM7 and need a battery life that's close to what stock rom offer.
Note:
As of release 114/115, FXP kernel also has better power management and quite a good battery life. The power consumption difference between this rage kernel and fxp kernel is not as much as it used to be before. In case of broken features or any problem caused by using this kernel in FXP cm7 rom, then please consider using FXP kernel instead.
hi ,after flash your kernel ,my device have a boot-loop,please check it ,thank you
zhanglz0904 said:
hi ,after flash your kernel ,my device have a boot-loop,please check it ,thank you
Click to expand...
Click to collapse
Okay, I'll check it. I might zip the wrong file. What is your device? I assume it is mini / st15? Because kernel for mini pro works fine in my mango. I'll check and if needed I will re-compile it.
Edit:
I think the problem was I incidentally used wrong ramdisk for mini kernel.
I have made a new kernel for mini, but it needs testing first. So, if anyone's willing to test it, please send me a PM. Thank you...
Edit:
Fixed. Link for mini updated.
Thank you!!
Im using cyanogen fxp 111
Only need flash the kernel?
Or need make a full wipe?
edwarddd said:
Thank you!!
Im using cyanogen fxp 111
Only need flash the kernel?
Or need make a full wipe?
Click to expand...
Click to collapse
You are using mini pro, right? I'm still fixing kernel for mini.
You don't need to do a full wipe, just wipe the cache partition.
Yes im using the mini pro
Thanks!
thanks a lot.even i was switching back to stock because of the battery drain ..will try this on my mini pro today
i am using fxp111 on my st15i,thank you for your great work .
zhanglz0904 said:
i am using fxp111 on my st15i,thank you for your great work .
Click to expand...
Click to collapse
Mini kernel is fixed. Link is updated. Please test it and let me know if you encounter any more problem. Thank you for your feedback...
greenAlgae said:
Mini kernel is fixed. Link is updated. Please test it and let me know if you encounter any more problem. Thank you for your feedback...
Click to expand...
Click to collapse
hi ,greenAlgae ,i am sorry to tell that i encountered the same problems with using your fixed kernel ,it may not the ramdisk,but the drivers,i think .
by the way ,some of us using the rage kernel have encountered the same problem,they aslo "complained" the boot-loop ,so i think the problem is kernel itself not the the ramdisk ,i am very happy if you will fix it ,thank you much .respected your work
zhanglz0904 said:
hi ,greenAlgae ,i am sorry to tell that i encountered the same problems with using your fixed kernel ,it may not the ramdisk,but the drivers,i think .
Click to expand...
Click to collapse
what is the problem?
im install fixed kernel and everithing working.
no bootlop or error during boot.
zhanglz0904 said:
hi ,greenAlgae ,i am sorry to tell that i encountered the same problems with using your fixed kernel ,it may not the ramdisk,but the drivers,i think .
by the way ,some of us using the rage kernel have encountered the same problem,they aslo "complained" the boot-loop ,so i think the problem is kernel itself not the the ramdisk ,i am very happy if you will fix it ,thank you much .respected your work
Click to expand...
Click to collapse
Is there any error when you flash it using fastboot? Did you get to boot logo only or you get to cyanogen boot animation when the phone bootloop?
wucinac said:
what is the problem?
im install fixed kernel and everithing working.
no bootlop or error during boot.
Click to expand...
Click to collapse
Thank you wucinac. It seems there's some kind of inconsistencies here. Hopefully it can be worked out, else i would have to pull out the kernel for mini altogether.
Sent from my SK17i using XDA
For st15i i have to use fastboot query with flag:
Code:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
P.S. Rage flash'ed without any problems. Kudos to developer, many thanks for merging battery save and direct call record!
oh great! Let's test!
gqcJYb3UN8xSIWNUy2xX said:
For st15i i have to use fastboot query with flag:
Code:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
P.S. Rage flash'ed without any problems. Kudos to developer, many thanks for merging battery save and direct call record!
Click to expand...
Click to collapse
So, it does work for mini after all, right?
All credits goes to original devs. It was DuMOHsmol who added the features, so your kudos goes to him
Snoopo said:
oh great! Let's test!
Click to expand...
Click to collapse
Yes sir, please test it and kindly let me know how it goes . Any feedbacks - even negative ones - will be much appreciated
Sent from my SK17i using XDA
So long time ago i using stock rom, and rage kernel are the best, i think that are the best kernel
For stock neves restart the phone on overclock , i dont back to stock rom never thanks!!
Sorry for my bad inglish
edwarddd said:
So long time ago i using stock rom, and rage kernel are the best, i think that are the best kernel
For stock neves restart the phone on overclock , i dont back to stock rom never thanks!!
Sorry for my bad inglish
Click to expand...
Click to collapse
Well, overclocking is the feature that I very rarely use. Because I use this kernel for better battery life, and overclocking might just negated that
But I'm glad that it works for you
Sent from my SK17i using XDA
greenAlgae said:
A bit background:
I use FXP CM7 rom for my mini pro since release 049 and like it very much. One thing that made me keep switching back to stock rom was the high battery drain, because in my daily activities electric plug is not always readily available, so battery life is critical for me.
In fxp 052 I got a bit desperate and trying to use custom kernel based on stock from bbooff here, with fxp rom. The battery life is excellent, just like stock rom, but I encountered 2 problems: touchscreen sometimes become unresponsive and wifi was not working (even if I replaced wifi modules with stock).
Finally, I decide to learn how to compile android kernel, and I found that it is quite similar with compiling linux kernel, which I've frequently done to my computer and laptop.
So, I compiled kernels from 3 sources and compare the battery life in my mini pro. They are from DoomLord's official SE source, DuMOHsmol's Rage kernel source, and krizky82's X Kernel source. I also recompiled kernel from FXP kernel source using stock semc_mango_defconfig, to see if battery life is better. The conclusion is that best battery life is achieved using stock and Rage Kernel, and I've been using FXP with rage kernel since release 102 and haven't considered going back to stock rom again.
I posted in Rage Kernel thread to thank DuMOHsmol, and since then there's 3 xda members that ask me to share this kernel, so I make this thread.
I hope this could help those who want to use FXP CM7 and need a battery life that's close to what stock rom offer.
Click to expand...
Click to collapse
I have installed your kernel on my sk17i .. with FXP 111, but overclocking is set to 1024?
First of all,
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM/kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Ok then, now that u've read the disclaimer we can continue with me and this kernel.
Frankly i'm no dev, just know a little bit of linux thus i know howto compile kernel, and i like tinkering with kernel to include what i like.
by that i'm learning as i go, so go easy on me please
About the kernel name, MESA stands for Man-Eating Seals of Antiquity, codename for kernel 2.6.32.
https://en.wikipedia.org/wiki/List_of_Linux_kernel_names
Click to expand...
Click to collapse
Roughly features of this kernel include:
- base on Sony's official 4.1.B.0.587 kernel source, so i build this from ground up. patched to upstream 2.6.32.60. ics kernel should work with stock/custom rom based on stock ics 4.1.B.0.431 or 4.1.B.0.587, and jb kernel should work with source based jb rom eg cm10, aokp and pa. personally i've tested this with expeacer's exmiuiv4, lasan's miui, stock ics, fxp's cm10 and aokp jb.
- updated to upstream linux 2.6.32.61.
- hybrid kernel, support stock/stock based, cm9/cm9 based, cm10/cm10 based rom.
- patched with Con Kolivas's patchset that includes bfs task scheduler v0.404, so this is a bfs kernel. stock kernel and all of custom kernel here so far uses cfs cpu scheduler. read about bfs cpu scheduler here.
- oc upto 1.8ghz and using 100mhz steps. default boot only use 1ghz.
- uv sysfs interface to modify voltage. i also decrease voltage abit. for anyone who wish to use stock voltage, heres stock voltage table
- cpu governors includes default stock ondemand, interactive, powersave, perfomance and userspace, i've added ondemandx, intellidemand, smartassV2, smoothass, interactivex, brazilianwax, scary, lulzactive, lagfree, smartass, minmax and savagedzen. default booting governor is interactive, its been updated/backported from kernel 3.x. read about cpu governors here.
- disk io scheduler includes deadline, sio, cfq, noop, anticipatory, zen, bfq and vr. default booting disk io scheduler is sio. read about io schedulers here.
- dual recovery, cwm and twrp. access cwm by pressing volume down button and twrp by pressing power button. also can swap those keycode by adding "swap.recovery.keycode=true" to build.prop. phone will vibrate slightly before entering both recovery as indicator. also included autoroot which wont give problem with miui rom, init.d startup script and unsecure ramdisk for adb root access. v4.7 got twrp 2.4.3.0 and cwm 6.0.3.9.
- swap and zram support.
- ext2/3/4 support.
- usb otg support.
- ntfs read/write with fuse module built in.
- samba support with cifs module built in.
- wifi modules integrated into kernel, then added into ramdisk. it will be insmod directly from ramdisk and existing wifi modules in rom wont be touched.
for full itsy bitsy changes read the changelog.txt in download folder.
and to comply and abide with gpl, source diff also included in the download folder.
Click to expand...
Click to collapse
Howto install:
1- be sure u already unlocked bootloader.
2- download correct kernel for your rom and phone and make sure md5 checksum matches. jellybean rom should use the kernel with "jb" in filename. or just use the new hybrid which support cm9/cm9 based, cm10/cm10 based rom and cm10.1/cm10.1 based rom.
3- if kernel downloaded in *.7z format u need to unpack it using winrar or 7zip.
4- flash the kernel via fastboot.
Click to expand...
Click to collapse
Troubleshoot:
- ini.d script not working? read this
- stuck at booting after flashing kernel? wait a little bit longer. kernel needs to run some script when booting.
- still stuck at booting? wipe cache and dalvik cache via recovery.
Click to expand...
Click to collapse
Reporting bugs:
1- if u got freeze problem, paste logcat to pastebin and give me the link.
2- if u got sudden reboot, after the sudden reboot, paste content of /proc/last_kmesg to pastebin and give me the link.
3- also tell me which phone u use, with which rom and which kernel.
what is that logcat and dmesg thingy u kept talking about? google for it.
how to get it? use this
Click to expand...
Click to collapse
Credits also goes to:
- google for this awesome platform, android.
- sony for releasing the kernel source.
- fxp team for some of their patch i use, and for the awesome cm10.
- kamarush for helping with problem i've had with wifi modules earlier, and also for the ramdisk i've taken from his minicmlite v3 kernel.
- doomlord for some of his patch i use.
- krizky82 for some of his patch i use.
- adridu59 for some of his patch i use.
- <insert your name here if u feel that i've failed to mention your name>
Click to expand...
Click to collapse
nice, good work.
can you please post the sources?
far fetched request,
can you make this for cm9?
Good work, i wonder if someone could develop a BFS Kernel for Mini pro. i used to use BFS with my Optimus One.
Nice one mate....!! i think it is more battery efficient( uses less battery)
gandhar said:
nice, good work.
can you please post the sources?
far fetched request,
can you make this for cm9?
Click to expand...
Click to collapse
because i had ****ty connection speed i wont be able to setup github and the like.
but diff patch are in download folder. use that to patch sony's official 4.1.B.0.431 and u'll get exact source as on my pc
Good job Mate
Sent from my SK17i using XDA
an0nym0us_ said:
because i had ****ty connection speed i wont be able to setup github and the like.
but diff patch are in download folder. use that to patch sony's official 4.1.B.0.431 and u'll get exact source as on my pc
Click to expand...
Click to collapse
yeah, thanks..
just wondering
what if you compile with fxp ramdisk, what happens then?
gandhar said:
yeah, thanks..
just wondering
what if you compile with fxp ramdisk, what happens then?
Click to expand...
Click to collapse
i've never tested, but probably wont boot. fxp's cm9 need its own kernel config too, not just difference in the ramdisk.
coolbuy said:
Good work, i wonder if someone could develop a BFS Kernel for Mini pro. i used to use BFS with my Optimus One.
Click to expand...
Click to collapse
whats BFS buddy???
an0nym0us_ said:
i've never tested, but probably wont boot. fxp's cm9 need its own kernel config too, not just difference in the ramdisk.
Click to expand...
Click to collapse
i'll try that out someday and let you know if it works out.
good day
whalesplaho said:
whats BFS buddy???
Click to expand...
Click to collapse
http://ck.kolivas.org/patches/bfs/sched-BFS.txt
http://ck.kolivas.org/patches/bfs/bfs-faq.txt
an0nym0us_ said:
http://ck.kolivas.org/patches/bfs/sched-BFS.txt
http://ck.kolivas.org/patches/bfs/bfs-faq.txt
Click to expand...
Click to collapse
thanks buddy....
I installed your kernel with hybrom v2 wt19i at the monent working perfect good work
Sent from my WT19i using XDA
Bluetooth not working with stock rom.
Wifi works perfect with the MESA Modules
fabiode34 said:
Bluetooth not working with stock rom.
Wifi works perfect with the MESA Modules
Click to expand...
Click to collapse
Umm can anyone else confirm this?
Forgot to test bt myself on stock rom earlier. Currently on exmiui and bt works for send/receive file to/from my laptop.
Congratulations men, waiting for xmp
Sent from my SK17a using xda premium
an0nym0us_ said:
Umm can anyone else confirm this?
Forgot to test bt myself on stock rom earlier. Currently on exmiui and bt works for send/receive file to/from my laptop.
Click to expand...
Click to collapse
Here it says "Activating..."
But nothing else... Can you send me the bluetooth modules from your current rom?
fabiode34 said:
Here it says "Activating..."
But nothing else... Can you send me the bluetooth modules from your current rom?
Click to expand...
Click to collapse
Did u reboot and try again after reboot?
If that didn't work too i'll test myself later by restoring my stock rom cwm backup.
Yes i already tried rebooting.
Still says "Activating..."
bluetooth works fine for me and wlan i forgot to install wifi modules (downloading now) i think it will works fine
Really nice work and thank you
Btw it's oc 1.6
Edit: my Rom MIUI v4 2.6.15
Before you do anything: I will not be held responsible for anything bad that happens to your phone.
Hello World! I want to share with you my first kernel for our N1. It's based on the great job of Evervolv team, texasice and the rest of developers that contribute with this great ROM running Jellybean 4.2.
Please, consider that this is a personal experiment with kernel builds, so don't expect a dedicated personal support but I accept all your comments.
This kernel should work in Evervolv and CM10.1 ROMs.
What will you installing exactly in v0.7?
Based in Evervolv's Jellybean repo (android_kernel_htc_qsd8k)
Applied UKSM patches.
Built with Linaro v4.7 toolchain
Added some extra CPU governors. Full list available:
- lionheart smartassV2 interactive conservative userspace powersave ondemand performance
Added SIO scheduler
Applied patch for events waiting to get input_event lock: https://code.google.com/p/android/issues/detail?id=42265#c162 (hope to fix some GUI lags)
Zen scheduler set to default (new in 0.7)
Other few changes (new in 0.7)
Downloads
msku-kernel-xtra-for-Evervolv-0.7.zip
Code pushed to my [new] github account: https://github.com/figue/android_kernel_htc_qsd8k
Full changelog, references and some tests look here
Instructions
Push it to sdcard
Flash into recovery
Wipe only cache+dalvik
To revert your kernel to stock, flash your ROM again.
reserved
jolinnard said:
Instructions
Push it to sdcard
Flash into recovery
Wipe only cache+dalvik
To revert your kernel to stock, flash Evervolv's ROM again.
To test SIO scheduler, use SetCPU or another similar. To do it manually, execute in adb shell or terminal emulator (type "su" first):
Code:
for p in /sys/devices/virtual/mtd/mtd*/mtdblock*/queue/scheduler ; do echo sio > $p ; done
Right now I'm having great results with lionheart governor. Try it...
Click to expand...
Click to collapse
Could you please tell us the benefits of using your kernel versus stock kernel? For example, sounds, wifi, speed, etc....
Reasons are simple: you have more governors and schedulers to choice, UKSM patches are an experiment that maybe free more memory (something to read about it), but I'm not sure that it's working in Android. Only can say that it works great on my device. And with my kernel you can test the proposed patch for the "famous" entropy bug (well, at least the only real that it's proposed by Android developers, not placebo).
But try it yourself and test it!
Sent from my Nexus One using xda premium
w0w! c00l! Thanks, I'll give a try...
Works smooth on Evervolv Nightly 05/01 with Lionheart governor... Will try other governor n will update if got any issues. Thanks for the kernel, thought kernel update for N1 is dead. Hope more to come. Thanks again!
Suddenly reboot.. Huhu... Here the logcat... Thanks
http://pastebin.com/raw.php?i=6MRYZQfn
clustered said:
Suddenly reboot.. Huhu... Here the logcat... Thanks
http://pastebin.com/raw.php?i=6MRYZQfn
Click to expand...
Click to collapse
Thanks, don't know what's happening, I was running 2 days without any issues. I'm removing kernels meanwhile.
When I was on previous nightly 05/01, it was running fine.. Update to latest nightly 11/01 it start to reboot again n again. I flashed back the latest nightly, now fine. Maybe you could take a look from the latest nightly... Thanks...
Sent from my Nexus One using xda app-developers app
I restart all kernel changes. I've uploaded a first version to test. If somebody wants to try:
v0.5
It's a boot.img, flash from bootloader (fastboot flash boot boot-0.5.2.img) or recovery (flash_image boot /sdcard/0/boot-0.5.2.img).
jolinnard said:
I restart all kernel changes. I've uploaded a first version to test. If somebody wants to try:
v0.5
It's a boot.img, flash from bootloader (fastboot flash boot boot-0.5.2.img) or recovery (flash_image boot /sdcard/0/boot-0.5.2.img).
Click to expand...
Click to collapse
No reboot for me with this version... With the previous version I had reboot using smartassv2, now using lionheart it works just fine!
Will give a try later on when in front of PC.. Got zip version? Can try now.. Thanks
Sent from my Nexus One using xda app-developers app
v0.5 seem to be working well. I'm using the Evervolv 11th daily build and it seems zippier than the default kernel. What's new in v0.5?
yulius said:
v0.5 seem to be working well. I'm using the Evervolv 11th daily build and it seems zippier than the default kernel. What's new in v0.5?
Click to expand...
Click to collapse
v0.5 it's a rebased version. Only applied SIO scheduled and lionheart (both set to default)
jolinnard said:
v0.5 it's a rebased version. Only applied SIO scheduled and lionheart (both set to default)
Click to expand...
Click to collapse
Just pushed 0.6. Check the OP.
This version includes all previous patches (so UKSM enabled again) and it shouldn't crash.
The OP has a bad link for the download but the changelog link is good and has the zip. So far the kernel is looking good.
yulius said:
The OP has a bad link for the download but the changelog link is good and has the zip. So far the kernel is looking good.
Click to expand...
Click to collapse
Fixed!
I get this error in the logs. I don't know if it's relevant or not.
E/PowerHAL( 476): Error opening /sys/kernel/mm/ksm/sleep_millisecs: No such file or directory
The uksm directory exists. This doesn't seem to be affecting anything on the phone for me.
yulius said:
I get this error in the logs. I don't know if it's relevant or not.
E/PowerHAL( 476): Error opening /sys/kernel/mm/ksm/sleep_millisecs: No such file or directory
The uksm directory exists. This doesn't seem to be affecting anything on the phone for me.
Click to expand...
Click to collapse
Yeah, I noticed the same too. Probably it's because I set strategy to UKSM in kernel config and PowerHAL it's set to search into KSM directory. I need to investigate a bit more.
Almost 2 days on this latest kernel... works fine, smooth without any problem at all... running lionheart governor... thanks anyway...
Features:
Sony sources 12.0.A.1.257
Linaro 4.6.2
Neon Optimizations
Overclock up to 1.89GHz (disabled)
Dynamic Fsync
RAM optimization
WiFi optimization
CIFS, NTFS as external modules
kernel level Sound Control (how to)
CPU Voltage Control interface (VDD) (how to)
NLS_UTF8
ro.secure=0
/rootfs and /system mounted as rw
Init.d support
CWM 6.0.3.2
Governors:
- Interactive
- Ondemand
- Performance
- Powersave
- Conservative
- Userspace
I/O shedulers:
- SIO
- Deadline
- noop
...
Credits:
@varun.chitre15 for CWM 6.0.3.5
@DoomLord for ramdisk
@sj8023ld for CWM 6.0.3.2
How To Flash:
fastboot flash boot your_kernel.elf or flash .zip via CWM recovery
Enter CWM (button Volume Up) and make Wipe Cache Partition and Wipe Dalvik Cache
Reboot
Downloads:
CWM 6.0.3.2: sp_kernel_cwm.zip
CWM 6.0.3.5: sp_kernel_cwm.zip
Sources:
Github
Changelog:
[06.08.2013] v4
- synchronized numbers of versions between 4pda forum and xda forum
- Add a simple GPU governor for Adreno xxx GPU series
- Optimized simple GPU governor for Adreno xxx GPU series
- Intellidemand governer
- Some perf optimization
- version with CWM 6.0.3.5
[29.07.2013] v2.2
- deadline optimized
- ZSMALLOC
- ZRAM (module)
- ZRAM optimized for Android
- KSM
- ARM THUMBEE
[18.07.2013] v2.1
- fiops i/o shed
- row i/o shed
[09.07.2013] v2
Some minor changes:
- without overclock
- disabled dynamic file sync as it causes display flickering when locking
[08.07.2013] v1
- first version
alivanov79 said:
Changelog:
[08.07.2013]
- first version
Click to expand...
Click to collapse
Excellent giving this a try and let you know the feedback soon.
cool! going to flash it now
can i flash it on lock bootloader????
saberamani said:
can i flash it on lock bootloader????
Click to expand...
Click to collapse
+1
saberamani said:
can i flash it on lock bootloader????
Click to expand...
Click to collapse
NO.
To flash any custom kernel you must unlock bootloader first.
Updated the kernel:
[09.07.2013] v2
Some minor changes:
- without overclock
- disabled dynamic file sync as it causes display flickering when locking
nice, noticed screen flickering too when locking, after 2 days i didnt find any bugs or problems
can you add fiops scheduler and extra governors like intellidemand and Wheatley ?
tr0llica said:
nice, noticed screen flickering too when locking, after 2 days i didnt find any bugs or problems
can you add fiops scheduler and extra governors like intellidemand and Wheatley ?
Click to expand...
Click to collapse
Will do
Whats the difference between this kernel and the one from doomlord?
Redeque said:
Whats the difference between this kernel and the one from doomlord?
Click to expand...
Click to collapse
See commits on github and description in OP
Hi i flashed ur Kernel over Doom's One. One Question. Can i need to flash the Module.zip separately ? For a better wifi Connection ?
Edit:
That Module.zip not seems to be a flashable one... Whats the use of it. ? Pls explain. I am asking because i am not find any description about it in OP... I really need that after flashing SP kernel ?
Thanks in advance
Rajeev said:
Hi i flashed ur Kernel over Doom's One. One Question. Can i need to flash the Module.zip separately ? For a better wifi Connection ?
Edit:
That Module.zip not seems to be a flashable one... Whats the use of it. ? Pls explain. I am asking because i am not find any description about it in OP... I really need that after flashing SP kernel ?
Thanks in advance
Click to expand...
Click to collapse
Yes, it's not flashable .zip. You don't need to install them. The kernel works with stock ones OK. There are only two modules that can be needed: cifs.ko and ntfs.ko.
The free ram never low than 200M. The minimum RAM is too big. Can you redistribute RAM? For example the minimum RAM to 50M. I want to play the Vegas but SP always kill the game process because RAM not enough. Sorry for my poor English.
某龙兄 said:
The free ram never low than 200M. The minimum RAM is too big. Can you redistribute RAM? For example the minimum RAM to 50M. I want to play the Vegas but SP always kill the game process because RAM not enough. Sorry for my poor English.
Click to expand...
Click to collapse
Yes. That is a problem.
On the other hand, is there any way to install only a voltage module instead the whole kernel? I've got no unlockable bootloader i fear.
lanluckez said:
Yes. That is a problem.
On the other hand, is there any way to install only a voltage module instead the whole kernel? I've got no unlockable bootloader i fear.
Click to expand...
Click to collapse
I think there is no way...
Hi, cwm don't flash updatepacks. It's show flash but nothing. I must copy all with aroma filemanager . Thanks
Gesendet von meinem Xperia SP
joke19 said:
Hi, cwm don't flash updatepacks. It's show flash but nothing. I must copy all with aroma filemanager . Thanks
Gesendet von meinem Xperia SP
Click to expand...
Click to collapse
In order to check I deodexed my rom via CWM and install Xperia Honami Home & Widgets via CWM. Have installed them from external sd card and everything is OK.
Maybe updater-script in your flashable .zip is wrong?
Been using this kernel now for a 6 days and everything is fine but the music skips! i've tried several players and this happens!