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
Related
This is a repackaging of DooMLoRD's kernel for the Ray - this is only for the stock Rom at this time, and will not work on MIUI or CM.
It's based on DooMLoRD's Github sources, original thread with more information about the Kernel is here: http://forum.xda-developers.com/showthread.php?t=1172885 - all thanks should go to him, I've edited very little, simply changed some of the config to suit the Ray and tested it.
Brief summary:
* Overclockable to 2GHz (set at 1GHz to start - made sure of it this time!)
* Enabled most of the schedulers so you can choose your favourite (brazillianwax, smoothass, SavagedZen, interactiveX, lagfree, minmax, Scary, smartass, interactive, conservative, ondemand, userspace, powersave, smartassV2, performance).
[UPDATE]
Had a look at the issues with the 'Flash' on the camera not working - this is now fixed.
Also, after being requested by a couple of people I've recompiled it for MIUI - you'll have to flash the second version for it to boot. (Please choose the correct one, flashing the wrong one will let you access CWM-recovery, but the system won't boot.) MIUI isn't working at this time.
Updated Kernel can be found here for Stock Roms:
http://dl.dropbox.com/u/17615284/DoomKernel-2011-12-28-1201.img
[Edit] Kernel for MIUI booted, but became unresponsive after it's been on a while. Taken the link down until I can find a day or two where I'm not using my phone so I can flash MIUI myself and look into it.
Thank you very much for this good present !
I just would ask if it is compatible with bheremans' MIUI rom, and if it's not if someone can port it, or explain to me how it can be done.
hartej said:
Brief summary:
* Overclockable to 2GHz (set at 1GHz to start - made sure of it this time!)
* Enabled most of the schedulers so you can choose your favourite (brazillianwax, smoothass, SavagedZen, interactiveX, lagfree, minmax, Scary, smartass, interactive, conservative, ondemand, userspace, powersave, smartassV2, performance). Think I may have missed a few - shall go back and check when I get a chance.
* Can't remember if I managed to get it working with the latest Ramdisk or not. At one point I was using it with a previous Ramdisk but not sure if I eventually got it working... (Currently the CMW Recovery is version 5.0.2.7?) I'll have to check on this, if it's using an old RamDisk then some of the features may not be available.
Initial release - I've been using it for a day now and it seems quite stable.
http://dl.dropbox.com/u/17615284/RayDoomKernel-2011-12-18.img
Click to expand...
Click to collapse
Can you integrate in the kernel the dual mode call recording ability, please?
aragog53 said:
Thank you very much for this good present !
I just would ask if it is compatible with bheremans' MIUI rom, and if it's not if someone can port it, or explain to me how it can be done.
Click to expand...
Click to collapse
No idea, I think that MIUI, CM7 and Stock Roms require different Kernels (or some serious customisation) so i'd be guessing: No. But it's just a guess.
Tistitus said:
Can you integrate in the kernel the dual mode call recording ability, please?
Click to expand...
Click to collapse
DooMLoRD added this to his Kernel, but I don't have any requirement to record my calls so can't confirm if it's working or not. Feel free to test it out - you may find yourself in luck!
Bah! Uploading failed the first time, but it's fixed now.
If you downloaded the file before I posted this, and only have a 1.2MB file then please DONT FLASH IT. It shouldn't mess anything up permanantly but your device won't boot.
I've uploaded the file again (to the same location), please re-download and flash this one (it should be just over 6MB)
Please make it compatible for miui?;D.......
Sent from my ST18i using Tapatalk
Hi hartej glad to see you back on the forum
A have quick question, how can be repaired this problem: http://code.google.com/p/android/issues/detail?id=3708 DooMLord may be able to help you repair it? Or will show some tips
Sorry for double post...i had found a way to port to MIUI...take a look here hartej..)
bheremans said:
Rom by iriijo
To port kernel : nothing special, just compile it with :
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_2G is not set
and
CONFIG_PAGE_OFFSET=0xC0000000
Click to expand...
Click to collapse
Sent from my ST18i using Tapatalk
Hi Hartej, sorry but even with your second upload. The kernel doesn't boot. It stays at black screen (not even the SE logo)
@hartej: some notes ...
thinking its a good choise using DooMLoRD's kernel as your base, congratulations for your wise decision
some minutes befor i fastboot'ed (temporarly) your image (i.e. fastboot boot <image>)
# kernel cpufreq defaults is ondemand 245760/1862400Hz - no max 1GHz as you'r thinking?
some LITTLE change-requests from me - please
# /proc/config.gz support - a great help for every self-builder
# init.d support - importent i'm thinking, i modifyed init.semc.rc in initrd.img in your boot image for myself (serves only as a example)
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
user root
oneshot
# a git respository of your kernel for self builder
ok, thats all for NOW, thank you for your good work.
greetings
Doesn't boot
I've downloaded your present(RayDoomKernel-2011-12-18.img / 6.23MB) and flash it on my Ray with fastboot tool. But it doesn't boot, just shows me black screen.(Not even show me SE logo ) Anyway I appreciate your great effort.
is it for stock 4.0.2.0.A.42 firmware
Oh I tried.Doesn't boot with the 4.0.2.A.042 FW.
@hartej
glad to see u back on this
some devices cant handle 1.6Ghz+
thats why i keep 2 kernels
2.0Ghz
and
1.6Ghz
for other things u can check my kernel-ramdisk
SWDJPA said:
I've downloaded your present(RayDoomKernel-2011-12-18.img / 6.23MB) and flash it on my Ray with fastboot tool. But it doesn't boot, just shows me black screen.(Not even show me SE logo ) Anyway I appreciate your great effort.
Click to expand...
Click to collapse
masray said:
Oh I tried.Doesn't boot with the 4.0.2.A.042 FW.
Click to expand...
Click to collapse
Lol, I'll upload the right one eventually! Just tried downloading and flashing this myself, only to discover that I'd mistakenly uploaded the latest version instead of the working one. Still playing with getting the ARC ramdisk working with the Ray, possibly because of the speed issue DooMLoRD quotes above which is the reason for the black screen - the Kernel itself is identical, it's just a difference in the RamDisks.
I've uploaded the working one now - sorry for any confusion!
http://dl.dropbox.com/u/17615284/DoomKernel-2011-12-18-1547.img
hartej said:
Lol, ... I've uploaded the working one now - sorry for any confusion!
http://dl.dropbox.com/u/17615284/DoomKernel-2011-12-18-1547.img
Click to expand...
Click to collapse
i'll testet it shortly, now it boot in ondemand 245760/1024000Hz und init.d support works too - super
one questions leaves ...
i want to compile myself. where to get your changes for the ray (.config mainly ???), when i use DooMLoRD's cloned git sources ???
thanks and have i nice day ...
hartej said:
Lol, I'll upload the right one eventually! Just tried downloading and flashing this myself, only to discover that I'd mistakenly uploaded the latest version instead of the working one. Still playing with getting the ARC ramdisk working with the Ray, possibly because of the speed issue DooMLoRD quotes above which is the reason for the black screen - the Kernel itself is identical, it's just a difference in the RamDisks.
I've uploaded the working one now - sorry for any confusion!
http://dl.dropbox.com/u/17615284/DoomKernel-2011-12-18-1547.img
Click to expand...
Click to collapse
Please for MIUI ??
Works Great
Two thumbs up!
It is quite stable even at 2ghz.
But I would stay at 1.5 with smartass v2 considering battery life.
Thank you
-Ray User from Korea.
doesn't work with FXP050 on my Ray ... It does boot into the system but it doesn't show any submenus or option menus ... they are there, i can select by where i remember them to be but it is not graphicly shown
This Kernel is for STOCK Rom !!!! not for cyanogen mod.
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?
v2 Released. Scroll down for info!
Hello,
After lots of help from sirkay and FXP, I've built my own kernel that I thought I'd share with you.
This kernel wouldn't exist without the hard work of FXP. This is built from his source code. All real credit for this belongs with him (and DoomLord too, also an FXP Team member)
That said, this is my take and keeps the rather awesome release that is CM7.2 alive!
To be clear: This is a kernel for Cyanogen Mod 7.2 - Gingerbread! If you want a good ICS Kernel look at Sirkay's Thread.
So, what's different?
Uses a very recent GCC to compile, GCC version 4.6.3 which I optimised the build for Cortex-a8 and NEON.
Is compiled for performance not size (Optimize for size unticked)
Heap Randomisation is disabled.
Enabled SWAP - So you can use swap if you want to...
Default Scheduler changed to deadline, same as the Sony official kernel (still has bfq if you want to use it)
Default governor changed to ondemand.
CONFIG_OABI_COMPAT turned off. (This might break apps, haven't found any yet though)
Disabled CPUFreq Debugging.
Disabled FRAME_POINTERS, enabled STACK_UNWIND. Reason here: http://lists.openmoko.org/nabble.html#nabble-td6126708
There is no boot logo when this kernel boots. Each time I added one, the kernel refused to boot. I'll look at that. Just have patience, your phone is booting still...
(Here's where I make lots of stupid claims about how smooth, how buttery, how much battery life this kernel saves. Except I'm not a screaming idiot, so I'm not going to do that!)
I'm interested in any feedback you have, but I did this mostly for me.
And please remember the real person to thank, FXP. It's his source code I've used to build this. Also again thanks to Sirkay for his help and pointers.
Download it from here.
- muppet
Nice Kernel what's battery performance ??
aditya080908 said:
Nice Kernel what's battery performance ??
Click to expand...
Click to collapse
About the same as every other kernel.
OTG support? ?!
Sent from my ST18i
so good, This is what I looking for
@muppetmania attach here you png file. i can try to convert it to .rle for you
Could GB MIUI have the privilege?
Could we have a CM7 based MIUI 2.3.7 kernel?
I think GB MIUI works just fine and don't want to upgrade to ICS or JB.
But a better kernel for GB MIUI is always appreciated.
Thanks in advance,pls let us know if you'd be willing to.
Anoopnk said:
OTG support? ?!
Click to expand...
Click to collapse
If you'd like me to respond to questions, please post an actual articulate question in the first place. Cheers.
Yes, I'm aware I'm a ****, it's been pointed out to me already
sirkay said:
@muppetmania attach here you png file. i can try to convert it to .rle for you
Click to expand...
Click to collapse
Thanks sirkay, but the problem isn't that I can't make a rle file, it's that the rle file when added to the ramdisk stops the kernel booting. It seems to a bug in the SEMC loader, I found a post about it somewhere. Does the boot.img need to be padded out to a certain size to work?
Sometimes my logo.rle would work, but then I'd make changes, recompile, and the kernel would hang on boot. Annoying, so I've removed it for the moment.
rivtre said:
Could we have a CM7 based MIUI 2.3.7 kernel?
I think GB MIUI works just fine and don't want to upgrade to ICS or JB.
But a better kernel for GB MIUI is always appreciated.
Thanks in advance,pls let us know if you'd be willing to.
Click to expand...
Click to collapse
Hi rivtre,
I'd love to help, but my Ray is the only phone I have and is running CM7.2. While I could make a kernel for MIUI I'd have no (easy) way to test it. It wouldn't be fair to anyone if I started releasing untested things. So I'm sorry, it's not that I don't want to help, but no. Anyway, read the next bit to see why that's probably not a bad thing!
To All:
My kernel seems to be terrible when it comes to HD video recording. Can anyone else test this? I get heaps of dropped frames using my kernel when recording HD video vs a FXP Stock kernel. I need to look more at this, but for the moment I'd recommend not using this kernel!
v2 Released!
Version 2 of muppet kernel released.
What's new?
Compiled with GCC 4.7.1
Reverted to BFQ Scheduler by default
Reverted to Interactive CPU Scaling by default
Added logo.rle so you know it's booting!
Removed Debugging Symbols (CONFIG_KALLSYMS)
Reverted the scheduler and CPU scaling as they seemed to be the cause of the video recording lag.
Enjoy!
Download
does the kernel also work with this rom http://forum.xda-developers.com/showthread.php?t=1424121?
can I flqsh the kernel with flashtool?
is overclocking possible?
borg17a said:
does the kernel also work with this rom http://forum.xda-developers.com/showthread.php?t=1424121?
can I flqsh the kernel with flashtool?
is overclocking possible?
Click to expand...
Click to collapse
Not sure if it works with the stock ROM or not - try it and report back.
Yes, like all kernel images, you can flash it with Flashtool.
You can OC up to 1.6Ghz.
I tried it, but It doesn't work. Booting failed
muppetmania said:
Not sure if it works with the stock ROM or not - try it and report back.
Yes, like all kernel images, you can flash it with Flashtool.
You can OC up to 1.6Ghz.
Click to expand...
Click to collapse
borg17a said:
I tried it, but It doesn't work. Booting failed
Click to expand...
Click to collapse
Oh well sorry. It's only for CM7.2
muppetmania said:
Version 2 of muppet kernel released.
What's new?
Compiled with GCC 4.7.1
Reverted to BFQ Scheduler by default
Reverted to Interactive CPU Scaling by default
Added logo.rle so you know it's booting!
Removed Debugging Symbols (CONFIG_KALLSYMS)
Reverted the scheduler and CPU scaling as they seemed to be the cause of the video recording lag.
Enjoy!
Download
Click to expand...
Click to collapse
Just flashed your kernel, going to give a test run! thanks!!
Edit:
Well it doesn't seem to me that the camera recording works at all ... pictures = fine - but when trying to record video - the image freezes - and the camera app crashes.
I have to reboot to get back into the camera app...
Also, can't play any video I previously recorded...
Anything I'm missing?
I've flashed your kernel and did a cache + dalvik wipe...
Cheers!
Apocalyps2 said:
Just flashed your kernel, going to give a test run! thanks!!
Edit:
Well it doesn't seem to me that the camera recording works at all ... pictures = fine - but when trying to record video - the image freezes - and the camera app crashes.
I have to reboot to get back into the camera app...
Also, can't play any video I previously recorded...
Anything I'm missing?
I've flashed your kernel and did a cache + dalvik wipe...
Cheers!
Click to expand...
Click to collapse
Oh, well that's not the sort of feedback I wanted!
I haven't done much video recording the last couple of weeks (I've been away from work)
Let me do some testing and see what I can find...
Thanks for reporting
If you want a logcat I'll make one and get it to you , cheers
Sent from my ST18i using xda app-developers app
GPS
i just install your kernel on my phone...but why my GPS cannot running well
a1nx said:
i just install your kernel on my phone...but why my GPS cannot running well
Click to expand...
Click to collapse
why your bug reporting so terrible
a1nx said:
i just install your kernel on my phone...but why my GPS cannot running well
Click to expand...
Click to collapse
Update baseband to 75 or 77 ...reflash kernel !!!
Have fun !!
Sent from my ST18i
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...
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.
*/
Now this is nAa 3.x based kernel. Major props to him for making it happen. I thought we all would be forever stuck with ancient 2.6 kernel
The original from nAa is already good enough, but because i know howto compile kernel and feels uneasy using kernel compiled by others, here u go, somewhat extended kernel from the original one.
Click to expand...
Click to collapse
FEATURES:
Pretty much the same as nAa's, difference is:
1- compiled using Sourcery G++ Lite 2011.03-42 crosscompiler which is gcc 4.5.2 for kernel 3.4.x and with linaro 4.7-2013.06-1 which is gcc 4.7.4 for kernel 3.0.x
2- my own cpu frequency table with oc upto 1.8ghz with 100mhz steps. slightly preundervolted too.
3- not sure if its just me or the rom i'm using, interactive governor in nAa's seems abit buggy, it stayed at lowest frequency after waking from deep sleep thus making phone lags and unuseable. so i've patched it and make it default governor for kernel 3.4, and ondemand as default for kernel 3.0
4- enabled conservative and powersave cpu governor.
5- lowmemorykiller driver patched from various source
6- some networking stuff eg disabled all packet scheduling algorithm except sfb, and using veno as default tcp congestion avoidance algorithm.
7- using slub memory allocator instead of default slab.
8- enabled and use tiny preempt rcu instead or tiny rcu.
9- enabled sched autogroup.
10- wifi compat-driver is from "old" nAa's 3.4.0 which i think backported from kernel 3.8 or 3.9. current naa 03 kernel, he downgraded to compat-wireless from linux 3.2 due to some people said got connection error. that didn't happen to me so i haven't downgraded it. the 3.0 kernel uses compat-wireless 3.0.9-1.
11- currently patched to upstream linux 3.4.50 for kernel 3.4 and to 3.0.85 for kernel 3.0
12- removed smartassv2 and smartassh3 cpu governor. seems buggy and doesn't work well with kernel 3.4 and 3.0
13- added fiops disk io scheduler and made it default for kernel 3.4, sio as default for kernel 3.0
14- only for cm10. nAa's 03 got all individual ramdisk for stock, cm9, cm10 and cm10.1 ramdisk so it should boot with all those roms but i've only added cm10 ramdisk. if kernel detected that booting rom is not cm10 or cm10 based it'll force boot into recovery.
15- modules will be insmod directly from within ramdisk. existing modules in rom wont be touched.
16- miui based on cm10 compatibility by adding its required services in ramdisk.
17- stweaks support for kernel 3.0
18- probably many small things i forgot...
for more geeky bits by bits changes, read changelog.txt
Click to expand...
Click to collapse
BUGS?
it inherit the same bugs from nAa's kernel, probably more due to what i changed. but do not, i repeat, do not report bugs in any rom thread if u chose to use this kernel instead of default provided kernel in rom zip. by doing so u just made life harder for those rom maker/compiler. i'll *****slap anyone who does so.
but if u still want to report bugs, report to me and provide logs. without logs i'll just ignore it.
Click to expand...
Click to collapse
SOURCE:
download patch file from sourcepatch folder from download link. apply the patch onto vanilla 3.4 kernel for kernel 3.4.x and onto vanilla 3.0.8 kernel for kernel 3.0.x
Click to expand...
Click to collapse
CREDITS/THANKS TO:
1- nAa who originally port codeaurora kernel 3.x
2- everyone whom contribute to nAa kernel 3.x
3- codeaurora
4- linus torvalds and whole kernel dev team
5- google and whole android dev team
6- sony for this phone.
7- <insert your name here if u feel that i've failed to mention your name, whoever u are>
Click to expand...
Click to collapse
DOWNLOAD​
Click to expand...
Click to collapse
reserved for rainy days
Is USB OTG enabled here ??
Sent from my Live With Walkman using xda premium
Nice, I'll try it with BadBeanX soon
Sent by The Dark Side of The Force. Said Yoda.
enabled in defconfig, but not sure if it works or not because i didn't have otg cable to test.
cm10.1
great work !
but can you please support ramdisk cm10.1
Thanks ...
Hmmm...the title is a bit wrong my friends...it should be 20130609 not 20130509
anyway i will be watching this thread regularly cause i'm using your kernel right now...
adrpat said:
great work !
but can you please support ramdisk cm10.1
Thanks ...
Click to expand...
Click to collapse
probably not. it'll be unstable, especially for automatic light sensors.
http://forum.xda-developers.com/showpost.php?p=42234545&postcount=2731
Can't get it to boot with Polish Blood 4.2.2 AOSP
Sent from my Live With Walkman using xda premium
This is for jelly bean 4.1...
Sent from my Xperia Mini using Tapatalk 2
an0nym0us_ said:
probably not. it'll be unstable, especially for automatic light sensors.
http://forum.xda-developers.com/showpost.php?p=42234545&postcount=2731
Click to expand...
Click to collapse
Pardon me but what about slow SD Card speed while copying from PC?
I experienced that before on nAa kernel
Sorry for my broken english
Black_jackss said:
Pardon me but what about slow SD Card speed while copying from PC?
I experienced that before on nAa kernel
Sorry for my broken english
Click to expand...
Click to collapse
If I'm not mistaken, mike said he already solved it in his cm10.1 but i cannot seems to find any related commit in his github, or any other github that forked naa's. If anyone could point me to exact fix for it then I'm more than happy to include the fix.
edit: probably this one?
https://github.com/LegacyXperia/msm7x30-3.4.x-nAa/commit/3deef4ae03ba5eafc20f559644c0be6d6d3253b0
zerorated24 said:
This is for jelly bean 4.1...
Sent from my Xperia Mini using Tapatalk 2
Click to expand...
Click to collapse
Exactly. I already wrote clearly in thread title, in first post and in changelog. Thats why i changed boot init script to force boot into recovery if booting into unsupported rom. Spare them hassle of watching lags and systemui crash.
Should've made the script to trashed and corrupted partition tho, teach them unforgettable lesson to read properly :sly:
edit: nvm - delete
electrified said:
what do i have to delete if i'm stuck in Wifi turning on... ?
Click to expand...
Click to collapse
Nothing. Wifi should always be fully working. Modules are called directly from ramdisk, not involving any files from rom. But if its not working, logcat and dmesg would be awesome.
an0nym0us_ said:
Nothing. Wifi should always be fully working. Modules are called directly from ramdisk, not involving any files from rom. But if its not working, logcat and dmesg would be awesome.
Click to expand...
Click to collapse
now working after a few reboots
Sorry but this was a reply on the post above me.
Sent from my Xperia Mini using Tapatalk 2
Works very well, also USB OTG is supported (finally). Thanks, and keep up the good work!
csoresz2 said:
Works very well, also USB OTG is supported (finally). Thanks, and keep up the good work!
Click to expand...
Click to collapse
u tested usb otg?
wow kernel size decreased alot compared previous version. seems you removed adblock right