I've put together a kernel package for our wonderful Prevail.
Version 2.5:
Short and sweet, I added swap support for anyone who cares about such things
Odin users: You will notice that the download file is now a .zip. this is because the tar file is inside and the config file is in there too. There are some instructions in the included readme.txt on how to install the config file, without it, the kernel will not attempt to mount the extended SDcard partitions at all.
CWM users: The installer script puts everything where it needs to be hands free. This is the best way to install IMO.
On to configuring:
For non-CTMod users: (CTMod will have it integrated in 3.5) Koumamod.apk 1.5
the above link lets you skip all this:
in /system there (should) be a file named koumamod. In there is this,
Code:
on koumamod
# Default Internal /data partition. Comment this line to disable mounting of the internal /data (not recommended)
mount ext4 /dev/stl13 /data rw noatime nosuid nodev barrier=0 data=writeback nobh nodiratime noauto_da_alloc
# Mount SD-EXT as /data partition (KoumaKernel 1.2 style) Uncomment this line to activate this mode
# mount ext4 /dev/block/mmcblk0p2 /data rw noatime nosuid nodev barrier=0 data=writeback nobh nodiratime noauto_da_alloc
# Required Directory and Permissions. Do not edit these
mkdir /data/dalvik-cache 0771 system system
chown system system /data/dalvik-cache
chmod 0771 /data/dalvik-cache
mkdir /data/app 0771 system system
# Mount SD-EXT as /data/app and SD-SWAP as /data/dalvik-cache (SSM Style) Uncomment both lines to activate this mode
# mount ext4 /dev/block/mmcblk0p2 /data/app rw noatime nosuid nodev barrier=0 data=writeback nobh nodiratime noauto_da_alloc
# mount ext4 /dev/block/mmcblk0p3 /data/dalvik-cache rw noatime nosuid nodev barrier=0 data=writeback nobh nodiratime noauto_da_alloc
# /data permissions. Do not edit
chown system system /data
chmod 0771 /data
trigger post-fs
This may be hard to read while in an editor on the phone itself. Just take your time with it
We are concerned with the lines that start with "mount ext4"
simply remove the # from in front of the line to for the mount option you want.
it's broken up into sections, 2 of them you should probably not mess with, they are labeled with Do Not Edit
Uncomment the sections you want to run, Comment the sections you don't.
The above is the default config, it just mounts the internal.
People running in all /data on the sd-ext can get away with commenting the first section, but your phone will not run or boot without your sdcard if you do that. but it seems to help gps for some people
Be careful to only have one mode uncommented at a time, there's no safety, you can end up with your SD-ext mounted in 2 places, making an endless loop within itself, this is bad (or it just wont mount the 2nd time, either way, don't do it)
Integrated Darktremor style App2SD! Hroark discovered a tweak that obsoletes A2SD apps and that change is now integrated with this kernel.
I've added an extra secret mod that can be unlocked by manually adding a third sd-card partition, I will post instructions at the end of this post. -Unhidden due to new cwm formatter
*NOTE* You absolutely MUST format your SD-ext partition if changing over from a traditional App to SD solution. This mounts the SD extended partition as /data. Other apps map SD-Ext to folders within /data, the structure will not match and will not work if you do not format.
If you do not have a partitioned SD card. THERE IS NO CHANGE. Don't worry about upgrading
Boot times -WILL- be slower. Especially with slower SD cards. I run a class 2 card because I'm a cheap bastard, it takes me an extra 30 seconds or so to boot. I expect faster cards will be faster. Smaller partitions should also be faster, I have a 4 gig SD-Ext partition.
Performance results with my 8 gig Class 2 card split 50/50? Some apps load slow, especially the first time. Things are pretty snappy after that.
Therefore, this is pretty good for general consumption.
There is no hotspot_event_monitoring.
Outside of that, this was originally a branch of Hroarkernel 1.2, with Hroark's smaller EXT4 drivers, and init.d support stolen from Shabbypenguin's init.rc
I would like to thank Hroark13 for the Kernel source and workshop, Hroarkernel, his EXT4 modules and his help in providing all the information I used in making my dhd.ko; and Shabbypenguin for confirming that I had the right init.rc lines to implement his init.d support method.
I would also like to thank trenchkato for getting overclocking to work and for sharing his code
Change Log:
Code:
2.5: Added swap support
2.4: Fixed GPS. Added Governors, Added IO schedulers, Upped Overclocking to 946, changed koumamod mounting
2.3: Fixed another bug where permissions and directories were not created properly. Added overclocking to 900MHz
2.2: Fixed bug where permissions and directories would not create correctly on clean SDcards. Removed RFS drivers. Fancied up the boot splash. first attempt at Signed zips
2.1: Updated Kernel string. Added a method for choosing mount style (SSM or 1.2/3 style)
2.0: Compiled from 2.6.35.14 source, tweaked mount locations. 1.5 turned official
1.4: Changed mount location for SD-EXT, to quiet some whiners :p
1.3: Skipped to avoid confusion with Build from Hroark
1.2: Tweaked Mount options for improved performance
1.1: Thanks to Hroark's hard work, pure App2SD integrated
1.0 cosmetic revision: swapped out boot splash for a work in progress version
1.0: Added bootanimation support, Cleaned up LS_COLORS (Thanks to Bloodawn for unknowingly showing me a spelling mistake I made that cause me grief with boot animations)
0.1GB: Redid 0.1 for Gingerbread Release, made dhd.ko smaller. Included new gingerbread ext modules made by Hrorak. Removed CIQ
0.2: Had to put CIQ service back in to resolve bootloops for some users
0.1: Initial Release
ClockWorkMod (CWM) Images:
Flash like any theme:
Copy KoumaKernel Zip file to your sdcard
Power off phone, or reboot into recovery if your phone supports it.
Power on your phone while holding the Volume Up and Camera buttons.
Navigate to "install zip from sdcard" -> "choose zip from sdcard" -> <Zip File for KoumaKernel>
Select the option: "Yes - Install <Zip File for KoumaKernel>"
Wait for the script to complete.
Reboot phone.
Super Secret Mod In order to activate the Super Secret Mod (moves /data/dalvik-cache to SD), you do the following (I will not answer questions regarding this, it is for the Advanced user and if you can't figure it out, you're not an advanced user, and seriously, if you can't work ADB and run a CWM zip, you probably shouldn't be modding your phone anyways. Just sayin):
1) Boot into Recovery
2) ADB shell into the phone
3) Run "sdparted -i"
4) Pick a size for a swap partition (CWM doesn't give you many size options, most are probably too small)
5) Pick a size for your EXT partition. Let the fat partiton have the rest.
6) When sdparted completes, manually convert the swap partition to ext4 by using the following: SD Ext Partition Formatter for CWM
* Suggestions *: Pick the same size for both your ext and your swap partitions, they seem to fill up at about the same rate. For me, I picked 1987, because it is exactly 1/4th of my SDcard so I have swap = 1987, ext = 1987 and vfat = 3974. Total = 7948 (8gig sdcard)
Last edited by Koumajutsu; May 24th, 2012 at 03:36 PM.
Reason: new Koumamod.apk
The Following 48 Users Say Thank You to Koumajutsu For This Useful Post:
what would removing hotspot_event_monitoring do for the phone?
free up about 6 MB of ram
hotspot_event_monitoring 89.kb removed
dhd.ko reduced from 2.6 mb to 264 kb
ext4.ko reduced from 3.4 mb to 346 kb
jbd2.ko reduced from 836 kb to 103 kb
since the hotspot_event_monitoring is a security feature, this may make tethering easier
Last edited by hroark13; October 17th, 2011 at 04:42 PM.
hotspot_event_monitoring 89.kb removed
dhd.ko reduced from 2.6 mb to 264 KB
ext4.ko reduced from 3.4 mb to 346 kb
jbd2.ko reduced from 836 kb to 103 kb
since the hotspot_event_monitoring is a security feature, this may make tethering easier
someone needs to couple this with carrier IQ remover.
That would be awesome.
Last edited by aladdin99; October 15th, 2011 at 05:30 PM.
I installed per the instructions for CWM zip installation, but after the script finished and the obligatory system rebooting the phone is now hanging up at the introduction Boost screen. It vibrated once and then quit..... Looks like I'll be hitting Odin pretty hard in the morning after I get off from work unless anybody has any ideas..... LOL
I installed per the instructions for CWM zip installation, but after the script finished and the obligatory system rebooting the phone is now hanging up at the introduction Boost screen. It vibrated once and then quit..... Looks like I'll be hitting Odin pretty hard in the morning after I get off from work unless anybody has any ideas..... LOL
Strange. can you try clearing your dalvik cache, or reflashing
The Following 3 Users Say Thank You to Koumajutsu For This Useful Post:
Strange. can you try clearing your dalvik cache, or reflashing
I had the same idea about clearing the Dalvik Cache just before I logged back in and saw this... It's kind of hard to work on my phone while watching over 3 other employees that are on heavy equipment. LOL.
I just cleared the cache and it's trying to boot up as I write this.
Well, I cleared the Dalvik cache and it looked promising. The phone entered the boot animation cycle, and then started bootlooping right when it should actually be booting up. Honestly, I think my phone just completely hates a change of any kind.... LOL!!!!!! It did the same thing when Shabby's RC1 first came out, and then hroarks ext4, and just about every other theme..... I'll push it through with Odin, after I Odin to get back up and running. LOL
Well, I cleared the Dalvik cache and it looked promising. The phone entered the boot animation cycle, and then started bootlooping right when it should actually be booting up. Honestly, I think my phone just completely hates a change of any kind.... LOL!!!!!! It did the same thing when Shabby's RC1 first came out, and then hroarks ext4, and just about every other theme..... I'll push it through with Odin, after I Odin to get back up and running. LOL
Sorry to hear you've had trouble. Before I released, I had an issue with the cwm version myself, Facebook started to force close. I had to go into applications and clear that app's cache then log back in again, and then it was fine.
I thought I squashed that bug, it may have just hit a system app for you
I guess you could try clearing your regular cache, but I'd hate to make you lose all your settings and any saved login info
Sorry to hear you've had trouble. Before I released, I had an issue with the cwm version myself, Facebook started to force close. I had to go into applications and clear that app's cache then log back in again, and then it was fine.
I thought I squashed that bug, it may have just hit a system app for you
I guess you could try clearing your regular cache, but I'd hate to make you lose all your settings and any saved login info
I did clear the system cache as well but it still kept boot looping. It's not that big of a deal though. I look forward to trying out the kernal when I'm back up and running in a few short hours.
Device(s): Samsung Galaxy Prevail
Google Nexus S 4G
Thanks: 3
Thanked 2 Times in 2 Posts
I tried flashing the CWM version but when the phone boots up, it'll do the single vibrate like it's supposed to and I'll here the signal sound but it won't leave the boot screen. I even did the usual wipe cache and dalvik cache after flashing like all the other goodies say to do hoping it would help but to no avail. Any suggestions on why this happened?
I tried flashing the CWM version but when the phone boots up, it'll do the single vibrate like it's supposed to and I'll here the signal sound but it won't leave the boot screen. I even did the usual wipe cache and dalvik cache after flashing like all the other goodies say to do hoping it would help but to no avail. Any suggestions on why this happened?
It could just be slow to go to the lock screen. I haven't ran many performance tests with the CWM version. I think I'll just take that version down for now. Though the people that have had success with it have been happy, I don't like a trend of people having problems.
I've been running the CWM version for about 3 days now and I've had no bootloop or error vibrations of any kind.
Great work!
Dont know that I can help any of you that are bootlooping. I was running hoarks kernal installed via the Odin package with the kernal and rooted system. After that I installed ShabbyRom (where I removed more apps to make it smaller and added Zeam launcher and some other stuff). Installed different themes, Honeycomb, Simple Blue, and one that I'm working on. And a few days ago I flashed this kernal via CWM with no issues.
I tried a bunch of things. including a stock ED13 image.
I can't get it to break.
It has to be something uncontrollable.
I've put it back up
If you run into problems, do a factory reset and try agian
I have the Dalvik cache moved to the SD card with Darktremors. I'm wondering if that caused some of the issues that my phone had last night with the cwm flash. ???? Just thinking.......
if your talking about the ciq remover it works fine with the kernal if you install it correctly
Thanks Bloodawn,
I spent almost an hour trying to reproduce Stlouizsin's issue, but I kept running into problems just trying to get CWM installed. Turns out I was skipping a step, I blame staying up too late
I was trying for hours to flash simple blue 4.1 but i kept boot looping.
did you flash simple blue 3.1 first as per the instructions?
CIQ removed themes seem to require a non-ciq removed theme to be flashed first for some strange reason
The Following User Says Thank You to Koumajutsu For This Useful Post:
What can we expect from future releases? Any plans?
I'm still learning quite a bit. There is a good group of people that have helped quite a bit with this, and at the moment I am trying to return the favor. One of the things I'd like to do is clean out a lot of references to things that don't exist in this phone(that is, if there is anything to clean out). I think it might improve boot times.
The Following 2 Users Say Thank You to Koumajutsu For This Useful Post:
I'm still learning quite a bit. There is a good group of people that have helped quite a bit with this, and at the moment I am trying to return the favor. One of the things I'd like to do is clean out a lot of references to things that don't exist in this phone(that is, if there is anything to clean out). I think it might improve boot times.
I haven't tried this yet, but keep up the great work. It's always nice to see a new face in development.
Just put up version 0.2
Seems that some things can require CIQ when the system initializes.
I put the init code back in for CIQ and it seems to clear up the cause of most of the bootloops.
i am running honeycomb theme with ciq removed, and just installed this kernel with no problems whatsoever. running smooth and a little snappier.
great job! thanks
isn't iqmsd the only file it calls for? cause I removed it from the phone with 3.0 of my remover
Yeah, but I ran into an issue when I installed my kernel that had iqmsd removed and then tried to install shabbymod. It got stuck at the boot animation and the boot log seemed to indicate that SprintAndroidExtension.apk was stuck trying to run CIQ
I put iqmsd back in and shabby loaded perfectly
it kinda boils down to, pre-ciq removal, run 0.2. After CIQ removal, install 0.1 for absolute obliteration of CIQ. But a factory reset seems to cause the things still looking for it at init to hang, so until they are all tracked down and squashed, doign a factory reset would mean goign to koumakernel 0.2, flashing a ciq enabled theme, flashing a CIQ removed theme, and then Koumakernel 0.1
Last edited by Koumajutsu; October 19th, 2011 at 11:30 AM.
The Following User Says Thank You to Koumajutsu For This Useful Post:
Kouma, I finally Odined .01 last night, and I must say GREAT JOB. The phone is running great and all is good until the next breakthrough development. LOL.!!!!!! Thank-you.
Just install kouma kernel 0.2, partitioned my 32gb sd card, the partition goes trhough fine, the format does too, but when I do to mount it I keep getting errors mounting the sd-ext? Any ideas why?
Just install kouma kernel 0.2, partitioned my 32gb sd card, the partition goes trhough fine, the format does too, but when I do to mount it I keep getting errors mounting the sd-ext? Any ideas why?
No clue really. maybe try a smaller partition size? I only have an 8 gig card, and I split it 4 and 4 and did not run into any issues.
Can you tell me the exact error that you're receiving?
The Following 2 Users Say Thank You to Koumajutsu For This Useful Post:
In clockwork I get and error trying to mount the sd-ext. When I I boot my phone it boots fine and everything, but my link2sd doesn't work anymore. I tried recreating mount scripts and none go through, and after trying to re-partition my card down to 128, with 0 swap space my ext4 partition comes up as other when I check it using Mini Partition tool and GParted on Linux.
In clockwork I get and error trying to mount the sd-ext. When I I boot my phone it boots fine and everything, but my link2sd doesn't work anymore. I tried recreating mount scripts and none go through, and after trying to re-partition my card down to 128, with 0 swap space my ext4 partition comes up as other when I check it using Mini Partition tool and GParted on Linux.
Hmmm, can you try it again with Hroarkernel installed. I don't think the issue is related to anything in the kernel
The Samsung Galaxy Prevail is an entry level device for Boost Mobile. Unlike some of it's Galaxy S cousins, you wont find some of the higher end "Galaxy S" features and it doesn't have the familiar TouchWhiz interface seen on so m... Read More
2Likes
[Kernel][GB] KoumaKernel 2.5
