The Ultimate Apps2sd Thread!

/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.

/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

Click to expand...

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.

Rafiki
1) Depends on the kernel. No matter what, link app will need to run script, but depending on the kernel you may need to run some insmod commands to load necessary ext driver. One kernel may use ext2 for file management, and if no other ext drivers are loaded then you would need the module to load the appropriate driver.

2) If you never wiped the ext the apps will be there, but the linking files in data/app will have been wiped. The dev is attempting to find a way to make that work, but not as of now.

maybe someone here can help..trying to run Link2SD this is what happened so far:I am running OG D1 running LGB1.52

Not working...I made an ext2 partition on the sd card then followed these directions:
1) Download the ext2.ko file (zip attached)
2) Extract it to your SD card
3) Use Root Explorer to navigate where you extracted it to and copy the file
4) Navigate to /system/lib/modules/ and paste the ext2.ko file there.

then I rebooted and ran link2sd and got: Mount script error mount script cannot be created. mount:No such device

Did u try actually linking an app with your FAT32 setup? I never get anything displayed in the L2SD storage info screen (always n/a) but that doesn't mean it isn't setup correctly. I don't think this display is coded to recognize FAT partitions.

Sounds like perhaps the ext 2 driver may already be in use, perhaps by the new file management. Sometimes you need to try using same method but using ext3 or ext4 .ko and run insmod commands.
Also don't forget to reboot after insmod command.
Sometimes even that won't work.
So once the app actually is able to submit its script to the init folder and nothing had worked after that, I will edit the script myself, changing the ext number only and that ended up working.
But every ROM and kernel have different settings and modules, just because out mounted correctly on one ROM doesn't mean it will use same mount point on another even with the same kernel.
Combine experimentation and patience. And make a backup before diving into the unknown.
Gives you the freedom to screw around without worry.

@ID you are correct ....LINK2SD uses the 2nd partition but just doesn't show it through the app. Thank you. @danceswithbongs I don't think the corcor67 kernels support ext which is why I had issues trying to run it that way but all good now. Thanks

If I am lucky some of you are still subscribed to this thread and will get an email starting this post.
Please, anyone that has a decent depth of knowledge regarding mounting, binding, unmounting, remounting elsewhere while not destroying anything that was mounted incorrectly causing the ultimate demise of my phone. Also scripting, code and queries to find out what had been accidentally mounted and how to move it appropriately. Explanation follows:
I am in need of a little assistance.
And by a little I mean a lot.
I have been using link2sd for a long time and the ext partition would normally be mounted /dev/block/mmcblk0p2. Or vold/ 179:2.
I use the ext4 driver like Prime had recommended due to lower cpu load.
I don't know how I messed things up, but it may have been messing around with Swapper 2 and the linux swap partition. I think what ever I did screwed up all of my mount points.
I can no longer even mount the sdext in recovery to format and if I try to restore a pre mess up backup, it isn't allowing the sdext to mount so the nandroid doesn't fully restore.
I get the following error message in recovery:
E: can't mount /dev/block/mmcblk0p2 (file exists)
Error mounting SDEXT:!

So restoring the ext gets skipped. I tried.flashing new ROMs to see if that would overwrite whatever was the cause, but no luck. Flashed gb and froyo ROMs but still no luck.
Also I can't seem to find out what exactly exists on mmcblk0p2 or how to move those files to the correct location.
It won't show when running bb commands cat process mounts.
Though it shows the fs mounted to obb and asec and yaffs.
Using "Root System Tools" app, that handles a lot of root functions, terminal, file directory viewer..etc.
But now when using the directories manager to figure out what is mmcblk0p2 mounted to and what resides within. But even though all permissions fixed, when I try to access and see what is on /dev/block/mmcblk0p2 I get the following pop up:
Permission denied to open the file

I think there is an outside chance that java coding now resides there, but that its merely a guess based on what problems are now suddenly occurring for the first time ever.

My main concern is that something important indirectly was bound to mmcblk0p2. Something that if formatted before it is mounted correctly could brick the phone.

Since this mount mishap, notification sounds don't work.
Lockscreen never happens, so even on boot no lockscreen.
The home key now won't do anything, return to home, open app drawer or show recent apps when long pressed.
Nor does the search button.
They give haptic but that is it.
So frustrating and why I'm worried about what now resides incorrectly mounted and how any poorly thought up attempt could destroy the ability for the phone to function whatsoever.

I've tried flashing a bunch of different ROMs to see if they would fix it as they might have different set ups including froyo and a real old MIUI and PE.
Still same problem.

That's no way for an OG to live.

Thanks to all with offers of assistance, ideas and solutions.
I really need help on this one.

Don't let me down, please, as it is clear many previously posting in this thread possess great wealths of knowledge in this area.
This helper needs help.
Fingers crossed

Useful Searches

About DroidForums.net

DroidForums.net was founded in 2009 originally dedicated for the Motorola Droid, the first Verizon Android Phone. We have since expanded our community to cover all Android Phones, Android Tablets, and Android Wearables. We discuss various topics including Android Help, Android Device Reviews, Android Apps, Phone Accessories, Android Games and more. Our ultimate goal is to be the Internet's best and largest Android Forum.