• 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

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


thought 3.6 already had it? that what blood told me on ctmod thread. I had same problem too...
install 3.6 and boot but tried to comment dalvik partition line so only apps moved and kept getting stuck on reboot. finally worked idk what I did different but it took 8 or 9 fresh installs of 3.6.

I used included koumamod.apk and kk2.5 tho was there Change since 3.6 release?
 
thought 3.6 already had it? that what blood told me on ctmod thread. I had same problem too...
install 3.6 and boot but tried to comment dalvik partition line so only apps moved and kept getting stuck on reboot. finally worked idk what I did different but it took 8 or 9 fresh installs of 3.6.

I used included koumamod.apk and kk2.5 tho was there Change since 3.6 release?

Yeah, the original CTmod 3.6 release had a corrupted koumamod.apk. The current one is fixed
 
Yeah, the original CTmod 3.6 release had a corrupted koumamod.apk. The current one is fixed

I just checked and my koumamod say on koumamod not capitalized. I downloaded yours separate but never used cuz blood said already included. multiple flashes and then it worked.

and is there any way to have app and dalvik share a partition? I'd have to wipe dalvik by hand or lose data apps though if it possible. or make flash zip that rm /data/dalvik-cache/*. that should work since it'd be on mmcblk0p2 and cwm mountable and able to follow path with out formatting whole partition
maybe
 
I just checked and my koumamod say on koumamod not capitalized. I downloaded yours separate but never used cuz blood said already included. multiple flashes and then it worked.

and is there any way to have app and dalvik share a partition? I'd have to wipe dalvik by hand or lose data apps though if it possible. or make flash zip that rm /data/dalvik-cache/*. that should work since it'd be on mmcblk0p2 and cwm mountable and able to follow path with out formatting whole partition
maybe

the only way to make them share a partition would be to go to /data mode.

you could make a cwm zip that can format mmcblk0p3 if you're using SSM.

or you could make a zip that could mount mmcblk0p2 as /data and then delete /data/dalvik-cache/*

depends on what you want to do for your specific setup. If you're looking to change your setup, figure out how you want your setup to be first, then figure out where dalvik-cache will be physically, and that will determine how you need to go about making the zip
 
the only way to make them share a partition would be to go to /data mode.

you could make a cwm zip that can format mmcblk0p3 if you're using SSM.

or you could make a zip that could mount mmcblk0p2 as /data and then delete /data/dalvik-cache/*

depends on what you want to do for your specific setup. If you're looking to change your setup, figure out how you want your setup to be first, then figure out where dalvik-cache will be physically, and that will determine how you need to go about making the zip


ya I can do all that just wondered if just those 2 folders could be on one partition singled out from rest of data on fone. I moved apps only and got swap on 3rd partition. apps hella room left but data with dalvik 30mb free. I'll just use full ssm I guess but I figured there's be a way to dual mount them to one partition or whatever that would be called
 
Ok, I got everything working the way I wanted. Kk2.5, halfass1. So now I'm playing with swap. I'd like to use my third sd partition and the phones /data partition as well, since I've got my sd-ext as /data. I'm not real versed in android, but I'm learning. I see stl13 still mounted as /data, as well as the sd-ext. What I don't see is my sd's swap mounted anywhere.

I know /dev/stl13 is the phones old /data partition, I don't know what the mount point is for the sd cards swap is. Can someone point me in the right direction to mount both these as swap? And also stop mounting stl13 as /data. I tryed using koumamod.apk, but when I had it not mount my data (or whatever that check box says), it wouldnt boot up. I'm about to try the new koumamod.apk that was just posted. See if that works. Thanks.

Excellent... The new koumamod.apk worked great, my stl13 is no longer mounted as /data. And everything is working fine. I just need to get my swap all sorted out. Any suggestions?
 
Ok, I got everything working the way I wanted. Kk2.5, halfass1. So now I'm playing with swap. I'd like to use my third sd partition and the phones /data partition as well, since I've got my sd-ext as /data. I'm not real versed in android, but I'm learning. I see stl13 still mounted as /data, as well as the sd-ext. What I don't see is my sd's swap mounted anywhere.

I know /dev/stl13 is the phones old /data partition, I don't know what the mount point is for the sd cards swap is. Can someone point me in the right direction to mount both these as swap? And also stop mounting stl13 as /data. I tryed using koumamod.apk, but when I had it not mount my data (or whatever that check box says), it wouldnt boot up. I'm about to try the new koumamod.apk that was just posted. See if that works. Thanks.

Excellent... The new koumamod.apk worked great, my stl13 is no longer mounted as /data. And everything is working fine. I just need to get my swap all sorted out. Any suggestions?

OK, now if you want to use stl13 as swap you're goign to have to jump through a couple hoops. Don't worry, they're big hoops, and they're close to the ground :)

you can try this:
in ADB type: mkswap /dev/stl13
in the swap menu, pick /dev/stl13 as a swap
when I was experimenting on CTmod 3.5, this seemed to cause my phone to randomly shut off. it might work in 3.6 though, I haven't tried it.

here is what I did after a my experiments:
I remounted /system as rw,
made a folder in /system called swap,
mounted /dev/stl13 as /system/swap
made a file the complete size of stl13 ("dd if=/dev/zero of=/system/swap/swapfile")
made that file into swap ("mkswap /system/swap/swapfile")
made an init.d script to mount stl13 as /system/swap at startup,
picked /system/swap/swapfile in koumamod.
profited :)
 
OK, now if you want to use stl13 as swap you're goign to have to jump through a couple hoops. Don't worry, they're big hoops, and they're close to the ground :)

you can try this:
in ADB type: mkswap /dev/stl13
in the swap menu, pick /dev/stl13 as a swap
when I was experimenting on CTmod 3.5, this seemed to cause my phone to randomly shut off. it might work in 3.6 though, I haven't tried it.

here is what I did after a my experiments:
I remounted /system as rw,
made a folder in /system called swap,
mounted /dev/stl13 as /system/swap
made a file the complete size of stl13 ("dd if=/dev/zero of=/system/swap/swapfile")
made that file into swap ("mkswap /system/swap/swapfile")
made an init.d script to mount stl13 as /system/swap at startup,
picked /system/swap/swapfile in koumamod.
profited :)


Excellent, I'll give it a shot when I get off work. Any ideas y my screen will flash on and off when it's sitting asleep? I got it to stop the first time it started doing it after I installed phandroid, by turning off all the phandroid notifacations. It started doing it again this morn.
 
Excellent, I'll give it a shot when I get off work. Any ideas y my screen will flash on and off when it's sitting asleep? I got it to stop the first time it started doing it after I installed phandroid, by turning off all the phandroid notifacations. It started doing it again this morn.

dunno, I've never seen that before. then again, my phone lives in a holster, so if it's doing that, I don't see it.
Maybe some other app is creating notifications?
 
dunno, I've never seen that before. then again, my phone lives in a holster, so if it's doing that, I don't see it.
Maybe some other app is creating notifications?


It isn't a notifacation thing. Thats just what solved it last time I saw it. Not sure really what it is.
 
Any ideas y my screen will flash on and off when it's sitting asleep? I got it to stop the first time it started doing it after I installed phandroid, by turning off all the phandroid notifacations. It started doing it again this morn.

IIRC, some apps that do stuff while the phone is in standby will wake up the phone, to get the CPU to run at regular operating speed. That keeps it from lagging the crap out of the phone. Its been a while since I read it and i don't remember what it was precisely, but I'd bet its some app that syncing something on the net.
 
I have ctmod 3.6 with kk 2.5 . I created the partition via cwm, but my phone still says it only has200 MB of internal memory. I previously had ctmod 3.5 with kk2.4, the partion worked fine, but I had lag issues with rom itself, so I flashed back to fa19 gingerbread. When blood dawn released 3.6, I did a new install,& that is when the problem started. So my question is, do I need to do the upgrade even though its included in ctmod?
 
I have ctmod 3.6 with kk 2.5 . I created the partition via cwm, but my phone still says it only has200 MB of internal memory. I previously had ctmod 3.5 with kk2.4, the partion worked fine, but I had lag issues with rom itself, so I flashed back to fa19 gingerbread. When blood dawn released 3.6, I did a new install,& that is when the problem started. So my question is, do I need to do the upgrade even though its included in ctmod?

Its in ssm mode which doesn't show up under internal storage, change it to data mode and select disable internal data and reboot.
 
For some reason disabling /dev/stl13 and mkswap'ing it may make ur phone lock on boot 75% of the time...

Had to reformat it back to ext3, and remount it as data again. Not happy about that :(

How do I make it ext4 again?
 
For some reason disabling /dev/stl13 and mkswap'ing it may make ur phone lock on boot 75% of the time...

Had to reformat it back to ext3, and remount it as data again. Not happy about that :(

How do I make it ext4 again?

mkfs.ext2 /dev/stl13

e2fsck -p /dev/stl13

tune2fs -c0 -i0 -j /dev/stl13

tune2fs -O extents,uninit_bg,dir_index /dev/stl13

e2fsck -fpDC0 /dev/stl13
 
After reading through the thread I'm thoroughly confused. If there is a dummied down version of how to go about this? I'm using CTMod 3.6.

What I understood is "Mount SD-EXT as /data partition" is to use the second partition on my SD card as extra storage for my phone.

First partition to be vfat and second to be ext4.

The other option "Mount SD-EXT as /data/app and SD-SWAP as /data/dalvik-cache" is to use the second partition on the card as extra storage and the third partition on the card as swap-space for the phone.

First partition to be vfat, second to be ext4 and third to be ext4 also. Or should the third be linux-swap?

I'm using gparted to partition and my third partition is actually sdb6 for some reason. Is that going to throw off my phone? Should I try something else to partition the card or should I just update /dev/block/mmcblk0p3 to read /dev/block/mmcblk0p6?

Thanks in advance.
 
[<vfat><ext4><ext4>] for ssm

OR
[<vfat><ext4><ext4><swap>] (if i understand correctly) for ssm with a swap partition
 
That's what I'm now running, uber-thanks to Kouma. Never run faster.
44188308-1b04-9fbf.jpg
 
[<vfat><ext4><ext4>] for ssm

OR
[<vfat><ext4><ext4><swap>] (if i understand correctly) for ssm with a swap partition

That's what I understand some people are doing. Though you can't get sdparted to do [<vfat><ext4><ext4><swap>] without modifying it.

Right now, I run Data mode and have my card:
[<vfat><ext4><swap>]
I got a 2016 in AntuTu rocking with my Class 2 card like that
but that class 2 scored 5.4MB/s write and 17.1MB/s Read
 
Right now, I run Data mode and have my card:
[<vfat><ext4><swap>]
I got a 2016 in AntuTu rocking with my Class 2 card like that
but that class 2 scored 5.4MB/s write and 17.1MB/s Read
And which option should I uncomment for that to take effect?

I'm currently in possession of a 8gb class 4 card. I'm going to partition it like that. I'm going to leave SSM alone for right now. Play with it later.

Thanks for your help guys!
 
feature suggestion...

I got data app on mmcblk0p3 and dalvik on mmcblk0p2. I do this by clicking save on the koumamod.apk(1.3) on SSM and then manually editing file before rebooting. apk copies same script over.

idk if anyone else doing modified SSM like me but I like it cuz it formats dalvik when I format sd-ext in cwm and factory rest well save my apps over ROM flash. think you could either have it ls (or what ever command that is) the current mounts and if app mounted on mmcblk0p3 then mv modified-koumamod to /system/koumamod
or
have it recognize if both partitions already used in SSM and not over write if off our on/data
 
not a big deal I just save to give .apk root permissions every time I upgrade to new version then edit before reboot but I thought that might be a cool 2nd SSM option since they perform the same.you'd just have to flash zip that formats both ext everytime you switch modes
 
I used to run on a Galaxy Prevail and recently upgraded to the Transform Ultra. I have been running your kernel for the Prevail for over 6 months and I love it. This may seem like a lot to ask, but what would it take to rework your kernel to run strictly WiFi and Bluetooth and not connect to the Boost network?? I would rather not pay for another line on the phone, but I would like to make use of the device. I own my own business repairing PC's and I would like to have the Prevail as a sort of storage device and mini tablet. If there is any way that this could be done I would be more than happy to assist you with testing on this or any other project you have regarding the Prevail.
 
Turn off mobile data in settings and/or use juice defender in extreme mode. It will disable the cdma radio essentially making it a tiny little tablet (JD even has tablet mode)
 
Back
Top Bottom