With all the secrecy surrounding the SSM I doubt you'll get a straight answer. Though I will admit I'm not entirely sure why this is shrouded in secrecy. It makes it extremely difficult for those not as savy to try to figure it out or at least try to learn how to accomplish it. It just seems odd to me, but then again this is Kourma's kernel hehehe
My take on it is that it moves your dalvik cache to your SD card. This allows you to have more internal memory. Well something like that I suppose. The previous threads have people making separate partitions and then mapping those partitions. Now the Dalvik cache is supposed to use this new partition or some such.
Correct, it moves the dalvik cache to the sdcard, which in turn will give you a nice big boost in space.
The reason for the secrecy is because it's easy to goof up, either by typo, picking a size that isn't good for the individual situation, choosing to do the mod when it will slow the phone down to unacceptable levels (and then consequently blaming me/the kernel for it).
Then there is just not understanding a thing about ADB and asking crap like "How do I ADB?" or "I do not has computer, how can I has SSM?"
Hey Kouma, the 2.0 kernel is not creating the new partition, even worse, I do not even see the kernel icon in my apps list...
am I doing something wrong???
Correct, it moves the dalvik cache to the sdcard, which in turn will give you a nice big boost in space.
The reason for the secrecy is because it's easy to goof up, either by typo, picking a size that isn't good for the individual situation, choosing to do the mod when it will slow the phone down to unacceptable levels (and then consequently blaming me/the kernel for it).
Then there is just not understanding a thing about ADB and asking crap like "How do I ADB?" or "I do not has computer, how can I has SSM?"
Somehow when I was reading your response this image of an exploding android came to mind with the face of the user covered in ash like in the cartoons.
Here we go again... Thanks
init_parse_config_file("/init.rc");
/* pull the kernel commandline and ramdisk properties file in */
import_kernel_cmdline(0);
get_hardware_name(hardware, &revision);
snprintf(tmp, sizeof(tmp), "/init.%s.rc", hardware);
init_parse_config_file(tmp);
action_for_each_trigger("early-init", action_add_queue_tail);
queue_builtin_action(wait_for_coldboot_done_action, "wait_for_coldboot_done");
queue_builtin_action(property_init_action, "property_init");
queue_builtin_action(keychord_init_action, "keychord_init");
queue_builtin_action(console_init_action, "console_init");
queue_builtin_action(set_init_properties_action, "set_init_properties");
/* execute all the boot actions to get us started */
action_for_each_trigger("init", action_add_queue_tail);
action_for_each_trigger("early-fs", action_add_queue_tail);
action_for_each_trigger("fs", action_add_queue_tail);
action_for_each_trigger("post-fs", action_add_queue_tail);
queue_builtin_action(property_service_init_action, "property_service_init");
queue_builtin_action(signal_init_action, "signal_init");
queue_builtin_action(check_startup_action, "check_startup");
/* execute all the boot actions to get us started */
action_for_each_trigger("early-boot", action_add_queue_tail);
action_for_each_trigger("boot", action_add_queue_tail);
/* run all property triggers based on current state of the properties */
queue_builtin_action(queue_property_triggers_action, "queue_propety_triggers");