The Ultimate Apps2sd Thread!

[armin369]

What command are you running in terminal emulator?

"su
mkdir /data/sdext2
mount -o rw,nosuid,nodev,noatime,nodiratime /dev/block/vold/179:2 /data/sdext2"

^^^^ That's the command I run in TE

In Mini Tool it shows FAT32 as primary and then I created an EXT2 (500MB) and set it as primary also. Those were my only two partitions

So it gives the "invalid argument" response after you run the last line? I am guessing it is from the 05mountsd script that comes with CM7. The partition is likely already mounted as /sd-ext rather than as /data/sdext2 as is required for link2sd thus causing an error when you try to mount it as something else. If you delete the 05mountsd script and reboot then run link2sd it should detect your partition and make its own script to mount the ext partition on boot. It sounds like you have all of the proper modules (ext2, ext3, and ext4) so you should be able to make it work with the stock kernel. If link2sd won't make a script for you then you could try the link2sd script provided by Prime in the 3rd post of his kernel thread. I'm not sure if prime's link2sd script would work fine with the stock CM kernel but I am guessing it would (you could ask him in his kernel thread, he is generally very responsive and helpful).

Also if you can't get it working with the stock kernel and you don't want to use deprimed you might try his primed kernel as I think it is closer to the stock CM kernel than deprimed. There is also reprimed though, maybe that is the one similar to stock? I have lost track of all his different kernels. Maybe you should ask Prime which of his kernel is closest to stock as I know at one point he made one that was basically the stock CM kernel with working compcache. Good luck.

I couldn't get it to work. Looks like the only way to fix it is to install the link2sd preinstall that was created by Prime which is not combined with a kernel. Therefore, after flashing that zip, I am finally able to link my apps
Thanks a lot for your help

[GodfatherIP]

Godfather
You know much more overall so let me run this by you.
Even though he has the ext.ko modules, is it possible he needs to run insmod commands to load the driver still?
Or if the module exists, it means that it had already loaded the drivers upon first boot?
I know on some kernels that the link2SD couldn't script for, I was able to accomplish it after running the appropriate insmod command with one of the ext.ko 2 through 4, depending on the kernel.

I want to help get you running the app but at the same time, don't want to mess anything of yours up, or turn a five minute solution into a 5 hour nightmare.
Okay, make a backup first and if we don't hear back from Godfather regarding my thoughts in the next hour or two, reply on the thread that you are ready, backed up and have a terminal app. I think you wrote you did but I'll err on the side of caution.
When I get notified of the new post, I'll write out the commands to run and steps to take.


walkin the walk while tappin the talk
danceswithbongs

Maybe that was the problem as I believe Prime's script loads the ext4 module first and then mounts the partition. So maybe his modules weren't loaded but running Prime's script fixed it.

[GodfatherIP]

"su
mkdir /data/sdext2
mount -o rw,nosuid,nodev,noatime,nodiratime /dev/block/vold/179:2 /data/sdext2"

^^^^ That's the command I run in TE

In Mini Tool it shows FAT32 as primary and then I created an EXT2 (500MB) and set it as primary also. Those were my only two partitions

So it gives the "invalid argument" response after you run the last line? I am guessing it is from the 05mountsd script that comes with CM7. The partition is likely already mounted as /sd-ext rather than as /data/sdext2 as is required for link2sd thus causing an error when you try to mount it as something else. If you delete the 05mountsd script and reboot then run link2sd it should detect your partition and make its own script to mount the ext partition on boot. It sounds like you have all of the proper modules (ext2, ext3, and ext4) so you should be able to make it work with the stock kernel. If link2sd won't make a script for you then you could try the link2sd script provided by Prime in the 3rd post of his kernel thread. I'm not sure if prime's link2sd script would work fine with the stock CM kernel but I am guessing it would (you could ask him in his kernel thread, he is generally very responsive and helpful).

Also if you can't get it working with the stock kernel and you don't want to use deprimed you might try his primed kernel as I think it is closer to the stock CM kernel than deprimed. There is also reprimed though, maybe that is the one similar to stock? I have lost track of all his different kernels. Maybe you should ask Prime which of his kernel is closest to stock as I know at one point he made one that was basically the stock CM kernel with working compcache. Good luck.

I couldn't get it to work. Looks like the only way to fix it is to install the link2sd preinstall that was created by Prime which is not combined with a kernel. Therefore, after flashing that zip, I am finally able to link my apps
Thanks a lot for your help

Glad to hear you got it working!

[zachdroid]

Today Prime created a flashable zip which may help some of you. You should flash this pre-install of Link2SD, but I believe it works after install too. I don't believe you will need the 99Complete file from a previous post in this thread with this zip. I could be wrong, so someone jump in if I am. Prime tweeted the link, so I've reproduced his tweet below.

#cyanogenmod Link2SD Users: This is a link2sd pre-installation zip, it will remove /etc/init.d/05mountsd (mounts to /sd-ext) and replace it with a modified version that mounts (and scans if an issue is detected) the second (ext2/3/4) based SD Card partition using the ext4 driver.

You need to make certain /data/sdext2 exists before flashing the zip/using link2sd...this is a safety measure to prevent any possible mishaps with a previous /data/sdext2 setup.

Link2sd Pre-installation Flashable zip: http://bit.ly/gpGpKX

It looks as though the preinstall zip from Prime has moved my sd-ext cache of files to a data folder. If this is so when flashing a new rom I usually wipe system etc etc etc. Is this wipe pattern going to erradicatwe all of the apps I have there? Should I unlink all of the Apps prior to wipe and flash?

Sent from my Droid using DroidForums

[zachdroid]

^edit: they have been saved in /data/app

Sent from my Droid using DroidForums

[-iD]

Lol

/data/app is the standard internal storage location where apps are installed. What you're seing there are the apps u havent moved. The ones you've moved with L2SD will appear to be in /data/sdext2 but that's just a symlink; they're really on your 2nd partition. If u select "wipe sd-ext" while in recovery they'll be wiped otherwise they will still be there when u flash a ROM.

Sent from my Droid using Tapatalk

[zachdroid]

Lol

/data/app is the standard internal storage location where apps are installed. What you're seing there are the apps u havent moved. The ones you've moved with L2SD will appear to be in /data/sdext2 but that's just a symlink; they're really on your 2nd partition. If u select "wipe sd-ext" while in recovery they'll be wiped otherwise they will still be there when u flash a ROM.

Sent from my Droid using Tapatalk

Glad I could provide a laugh I have no files really on my data partition with the exception of system stuff and a dew that were buggy when moved. I did find the above referenced file but in the /data/app folder I must have been mistaken when I saw the names if all my apps there and nit in the normal sdext I usually find them in. Thanks for the help. I'm kind of experienced but still a noob at times. I appreciate the response.

Sent from my Droid using DroidForums

[rafiki1]

I'm currently using CM7 RC4 along with Deprimed kernel on my Droid and have two questions regarding apps2sdext

1) If I were to change kernels now, would I need to do all of this again or will the apps remain in the ext folder and I can use them as normal?

2) If I change roms do I have to do all this again, like if I try out liquid's rom or something?

Thanks
Sent from my Droid using Tapatalk

[rafiki1]

does anyone know? Please help

[zachdroid]

Provided kernel flashed supports ext3/4 you should be ok with flashing a different one.

Sent from my Droid using DroidForums