• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Kernel][GB] KoumaKernel 2.5

I installed KK2.4 with CTMod 3.5. I have a 8gb sd card, it's set up the same way kouma has his under super secret mod (swap = 1987, ext = 1987 and vfat = 3974. Total = 7948 (8gig sdcard)) and have it on default in CTMod Settings (I was told that this meant it was SSM). Was thinking of updating to KK2.5. Will it work?

Was thinking that if super secret mod uses the partition that was meant for swap that enabling swap would not be possible... but I really don't know much about this stuff.

go ahead and pick ssm in ctmod settings just to have the display match the real

updating to 2.5 won't make any changes if you use the upgrader zip
 
Kuma, love the kernels. I've been on 1.2 forever now, becuase I like the sd-ext mounted as /data. I see that you've made it easily configurable as to where the mount point is in 2.5. I've been trying to upgarde to no avail. I've done the factory resets, cleared the davlik cache, even formated my sd-ext several times. I've done this on both the CWM version and the ODIN version. I'm still getting stuck on the Kouma Kernel 2.5 splash screen no matter what.

Can I get a little help here? BTW I'm pretty pissed someone took my MaNiMaL_X nick... Disapear for a few years and people start identity theiving...
 
Kuma, love the kernels. I've been on 1.2 forever now, becuase I like the sd-ext mounted as /data. I see that you've made it easily configurable as to where the mount point is in 2.5. I've been trying to upgarde to no avail. I've done the factory resets, cleared the davlik cache, even formated my sd-ext several times. I've done this on both the CWM version and the ODIN version. I'm still getting stuck on the Kouma Kernel 2.5 splash screen no matter what.

Can I get a little help here? BTW I'm pretty pissed someone took my MaNiMaL_X nick... Disapear for a few years and people start identity theiving...

What mod are you on?
 
Stock / my own

KK runs on a different filesystem than stock, you will have to switch to a new rom. CTmod is the top-o-the-line model, Halfassrom is basic stock made to run KK

Kouma, the new feature of 2.5, is it still running off the external apps? and if we try to use it on SSM, will it piss things off? Not messing with it ATM, but asking for posterity
 
KK runs on a different filesystem than stock, you will have to switch to a new rom. CTmod is the top-o-the-line model, Halfassrom is basic stock made to run KK

Kouma, the new feature of 2.5, is it still running off the external apps? and if we try to use it on SSM, will it piss things off? Not messing with it ATM, but asking for posterity

2.5 just adds functionality without changing anything existing.
It just knows what swap is and how to use it if you specifically tell it how you want to use it and when.
Other than that, it's pretty open to interpretation on how/if you want to implement swap
 
1.2 runs great on stock. Is there a change I missed?

Here's what you missed

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
 
Ya I don't see anything about file systems. So I'm assuming I shouldn't have a problem like previously commented. Any suggestions?

I've tried out different mods, and I don't like the missing functionality like bluetooth n such. So I modified the stock the way I want it. And I'd like to keep it. But I want the swap functions of kk2.5.
 
ya i don't see anything about file systems. So i'm assuming i shouldn't have a problem like previously commented. Any suggestions?

I've tried out different mods, and i don't like the missing functionality like bluetooth n such. So i modified the stock the way i want it. And i'd like to keep it. But i want the swap functions of kk2.5.

STOCK uses RFS file system. If you want a stock feel use HALF ASS ROM. It uses EXT 4 file system... Kouma kernel ONLY supports ext4...
Read 2.2 change log...
 
Ya I don't see anything about file systems. So I'm assuming I shouldn't have a problem like previously commented. Any suggestions?

I've tried out different mods, and I don't like the missing functionality like bluetooth n such. So I modified the stock the way I want it. And I'd like to keep it. But I want the swap functions of kk2.5.


HoneyBread has all the stock functions working
 
Ya I don't see anything about file systems. So I'm assuming I shouldn't have a problem like previously commented. Any suggestions?

I've tried out different mods, and I don't like the missing functionality like bluetooth n such. So I modified the stock the way I want it. And I'd like to keep it. But I want the swap functions of kk2.5.

You can use bluetooth on CTMod 2.5, just go to the market and install play music. Also The CM9 ROM has working bluetooth.
 
can someone tell me if I'm a genius or an idiot? haven't tried yet and script was made for cache download size and I modified (poorly)

please don't try this anybody just trying to find out if this is logical and if so useful
 
I#!/system/bin/sh
#
# bind mount /data/watever to /system/watever if system
# partition is too small. or maybe mkdir /system2 and bind mount /system to./system2
#

SYSTEMSIZE=$(df -k /system | tail -n1 | tr -s ' ' | cut -d ' ' -f2)
SYSTEMONLY=$(getprop dalvik.vm.dexopt-system-only)
if [ "$SYSTEMONLY" = "1" ]
then
NEEDED=XXXXX
else
NEEDED=XXXXXX
fi

if [ $SYSTEMSIZE -lt $NEEDED ]
then
mount -o bind /data/watever /system/watever (or /system /system2)
fi


exit 0
 
thinking either bind mount part of /data to /system if I'm using SSM.
Or
move /data to mmcblk0p2 and mount /stl13 to /system/app and odex it since I got space from using whole system partition. then it not wasted on /data to ext and mmcblk0p3 is swap
 
thinking either bind mount part of /data to /system if I'm using SSM.
Or
move /data to mmcblk0p2 and mount /stl13 to /system/app and odex it since I got space from using whole system partition. then it not wasted on /data to ext and mmcblk0p3 is swap


on second thought bind mounting would be better. don't wanna mess up mount and have app folder missing.

maybe mount /system/yay to st13
and bind mount /system/app and /system/yay
then it just looks at space in other partition as additional storage instead of permanent mount and only apps in bind mount would be missing if problem

is this true and/or logical? I know I could get script together but I'm not gonna try unless some one tells me I'm not just blowin smoke out my &55
 
I put up an updated copy of koumamod.apk for configuring Koumamod.

and swap usage...... I need to make a manual for that i think, it has some neat features that are probably not intuitive
 
Heads up kouma, theres an issue in CTmod 3.6. On an update install with manually wiped dalvik, changing from the default SSM to data will lock up the phone at the KK boot screen. I sat for a good twenty minutes with no change, so i'm certain its locked up.
 
Heads up kouma, theres an issue in CTmod 3.6. On an update install with manually wiped dalvik, changing from the default SSM to data will lock up the phone at the KK boot screen. I sat for a good twenty minutes with no change, so i'm certain its locked up.

try it again. it worked fine for me.
also, don't wipe your dalvik, the entire phone gets formatted when you install ctmod, doing that is excessive and redundant. Save yourself a little time
 
try it again. it worked fine for me.
also, don't wipe your dalvik, the entire phone gets formatted when you install ctmod, doing that is excessive and redundant. Save yourself a little time

just tried it again, using separate KK 2.5 install. The koumamod setting was showing data, but the extra storage was not available. rebooted to no effect. Tried reselecting data and rebooting, locked up on KK boot screen again. I'm gonna flash 2.4 and see if it works.

Edit: same thing on 2.4, both installing on top of what i had, and fresh installing CTmod then installing 2.4 immediately after. Flashing back to my nandroid backup for now.

Theres someone else on CTmod thread with same problem, and of course its the same setup as my guide, so theres dozens of newbs gonna do the same thing we did :eek:
 
just tried it again, using separate KK 2.5 install. The koumamod setting was showing data, but the extra storage was not available. rebooted to no effect. Tried reselecting data and rebooting, locked up on KK boot screen again. I'm gonna flash 2.4 and see if it works.

Edit: same thing on 2.4, both installing on top of what i had, and fresh installing CTmod then installing 2.4 immediately after. Flashing back to my nandroid backup for now.

Theres someone else on CTmod thread with same problem, and of course its the same setup as my guide, so theres dozens of newbs gonna do the same thing we did :eek:
ok, try this, install ctmod3.6
boot
install the koumamod.apk in the OP of this thread (if it refuses to install, try replacing the one in the ctmod.zip with this one)
and then try setting to data mode again
 
ok, try this, install ctmod3.6
boot
install the koumamod.apk in the OP of this thread (if it refuses to install, try replacing the one in the ctmod.zip with this one)
and then try setting to data mode again

Sorry, my dad is selling some lawnmowers, and some really big dude showed up at my front door wanting to buy some of them. I try to stay out of dads business, so i had to call him up, but the phone number is in my prevail, which is currently half modded and unusable, so I had to call mom, and get her to call him, and then he was busy and couldn't call me.... ugh. anyways back to work

Koumamod.apk would not install with package installer, so I had to switch it out in the zip. It seems to be working correctly now. Booted up on data, and the available storage is correct. Thanks a ton kouma
 
Back
Top Bottom