Go Back   Android Forums > Android Phones > LG Optimus F6

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

Like Tree13Likes

test: Reply
 
LinkBack Thread Tools
Old January 24th, 2014, 08:25 PM   #1 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default Swap internal/External Insufficient Storage

Hi, i used the mod to swap the internal to external i did all the steps and everything but i still get the insufficient storage message wheni try to update a app on google play. I dont know if did something wrong?? Any help would be appreciated.

alexcool25565 is offline  
Reply With Quote
sponsored links
Old January 24th, 2014, 08:33 PM   #2 (permalink)
Member
 
Trevor Philips's Avatar
 
Join Date: Nov 2013
Location: Sandy Shores
Posts: 233
 
Device(s):
Carrier: Not Provided

Thanks: 51
Thanked 69 Times in 37 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
Hi, i used the mod to swap the internal to external i did all the steps and everything but i still get the insufficient storage message wheni try to update a app on google play. I dont know if did something wrong?? Any help would be appreciated.
I remember this problem, i think i solved it by deleting the .txt from the script, i don't remember exactly but i do believe that was the fix
Trevor Philips is online now  
Reply With Quote
Old January 24th, 2014, 09:02 PM   #3 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by Trevor Philips View Post
I remember this problem, i think i solved it by deleting the .txt from the script, i don't remember exactly but i do believe that was the fix
I did that and it still shows the error :/
alexcool25565 is offline  
Reply With Quote
Old January 24th, 2014, 09:11 PM   #4 (permalink)
Member
 
Trevor Philips's Avatar
 
Join Date: Nov 2013
Location: Sandy Shores
Posts: 233
 
Device(s):
Carrier: Not Provided

Thanks: 51
Thanked 69 Times in 37 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
I did that and it still shows the error :/
Mind telling me the exact steps you did?
Trevor Philips is online now  
Reply With Quote
Old January 24th, 2014, 09:44 PM   #5 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by Trevor Philips View Post
Mind telling me the exact steps you did?
1) Download Uni-init v1.0.apk

2) Install like a regular apk and open it

3) Click on Activate and allow with super user

4) Click on Verify to make sure init.d is enabled

5) Reboot your device

6) Download any Root Browser you like from the play store

7) Download 11extsd2internalsd and copy it to your sd card

8) Open Root Browser and copy 11extsd2internalsd and paste it /system/etc/init.d folder

9) Hold click 11extsd2internalsd and set permissions and make sure everything is checked as far as Read, Write, and Execute

10) Download Smanager from the google play store and open and allow with root access

11) Go to /system/etc/init.d and click on 11extsd2internalsd

12) Click at the top where it has Su and Boot and hit save and then exit

13) Reboot your device and your all done!


Did all of those but didnt realize until after that i had to change the .txt on it. i redid all the steps again when i did it.
alexcool25565 is offline  
Reply With Quote
Old January 24th, 2014, 09:52 PM   #6 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

See if you can report to us the storage report from Linux, using the df command.

If you can manage to use ADB (Google for a short download, something like install only ADB), get to a shell and type df /data.

If you have a terminal emulator app, you can use that. If you have to uninstall something expendable to get that, it would be informative to have the information from df /data.

The reason is that the application(s) which swap storage, as you're stating, target the /data/media directory, perhaps through /storage/scard0 or /scard. This directory is what the F6 "considers" internal storage. It's also the typical destination for temporaries when downloading.

Except for Google Play. They use /data/data/com.android.providers/downloads/tmp.

Tell us what df /data/data/com.android/providers/downloads tells you.

99% of the time, this directory is not re-mapped when internal/external devices are swapped, meaning that while other sources of downloading may route to the external card with that swap, Google Play downloads may not.

The storage app in Android "Settings" can lie to you. More accurately, it's not a thorough explanation of storage on the device.

If you have a means of directing Google to download to the SD card, like a symbolic link or a mount, then use that.
JVene is offline  
Reply With Quote
Old January 24th, 2014, 10:07 PM   #7 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by JVene View Post
See if you can report to us the storage report from Linux, using the df command.

If you can manage to use ADB (Google for a short download, something like install only ADB), get to a shell and type df /data.

If you have a terminal emulator app, you can use that. If you have to uninstall something expendable to get that, it would be informative to have the information from df /data.

The reason is that the application(s) which swap storage, as you're stating, target the /data/media directory, perhaps through /storage/scard0 or /scard. This directory is what the F6 "considers" internal storage. It's also the typical destination for temporaries when downloading.

Except for Google Play. They use /data/data/com.android.providers/downloads/tmp.

Tell us what df /data/data/com.android/providers/downloads tells you.

99% of the time, this directory is not re-mapped when internal/external devices are swapped, meaning that while other sources of downloading may route to the external card with that swap, Google Play downloads may not.

The storage app in Android "Settings" can lie to you. More accurately, it's not a thorough explanation of storage on the device.

If you have a means of directing Google to download to the SD card, like a symbolic link or a mount, then use that.

https://copy.com/41Dl9AoRI9iQ

this one didn't work said no such file or directory
df /data/data/com.android/providers/downloads
alexcool25565 is offline  
Reply With Quote
Old January 25th, 2014, 03:53 PM   #8 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
https://copy.com/41Dl9AoRI9iQ

this one didn't work said no such file or directory
df /data/data/com.android/providers/downloads


Right, sorry, the second time I typed it I wrote it incorrectly:

df /data/data/com.android.providers/downlaods
JVene is offline  
Reply With Quote
Old January 25th, 2014, 10:57 PM   #9 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by JVene View Post
Right, sorry, the second time I typed it I wrote it incorrectly:

df /data/data/com.android.providers/downlaods
It still says the same thing
alexcool25565 is offline  
Reply With Quote
Old January 26th, 2014, 01:20 AM   #10 (permalink)
Junior Member
 
DunderMifflin's Avatar
 
Join Date: Nov 2012
Location: Los Angeles CA
Gender: Male
Posts: 90
 
Device(s): Motion 4g, Samsung Galaxy SII Epic Touch 4G, LG Esteem,
Carrier: MetroPCS, Sprint

Thanks: 101
Thanked 4 Times in 4 Posts
Default

All the solutions I see involve factory resets
DunderMifflin is offline  
Reply With Quote
sponsored links
Old January 26th, 2014, 09:40 AM   #11 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
It still says the same thing
alexcool25565, I must apologize. Normally I'm not such a set of twisted fingers, but for some reason typing this has been a mess.

So...I copied this out of the adb shell after getting the command to actually work on the device, and I STILL had to do it 3 times to get it right.

Yikes, getting old sucks!

This will work!

Code:
df /data/data/com.android.providers.downloads

Filesystem                 Size         Used         Free    Blksize
/data/data/com.android.providers.downloads      1.27G      597.62M      703.86M       4096
This includes the result I see on the stock arrangement of my device (I have other configurations that show this instead)

Code:
Filesystem                 Size         Used         Free    Blksize
/data/data/com.android.providers.downloads        29.04G        6.50G       22.54G       4096
In the first one, the stock configuration is shown.

In the second one, an experimental configuration I'm discussing in a thread on a proposed theory to remap storage of the device.

Notice how the total free space change dramatically.

Now, to continue this investigation of your machine's configuration, try df on this:

Note: Double check my typing, we've already learned I'm not exactly precise sometimes

Code:
df /storage/sdcard0
df /data/media
df /sdcard
On the stock device, these 3 directories are routed to the same place. In the "swapped" arrangement you're using, I expect them to be routed to the external SD card instead.

If your /data/data/com.android.providers.downloads is not routed to the same device as /sdcard and /storage/sdcard0, then downloads from other sources might have room while downloads from Google Play would not.

You can temporarily solve the problem with a mount, or for a longer term solution, put the mount into an init.d script, or use a symbolic link.

Something like (and by that I mean this example is an illustration, you'd choose names and locations you prefer, and my typing may be inexact, I'm not testing this on my device as I type it)

Code:
mkdir /storage/external_SD/google_downloads

cp -rp /data/data/com.android.providers.downloads/cache /storage/external_SD/google_downloads

mount -o rw,bind /storage/external_SD/google_downloads /data/data/com.android.providers.downloads/cache
In that example I assume a directory called google_downloads is already created on the external card.

The mount is temporary in the sense that it won't stay around after a reboot.

You can make the mount stick by adding it (not the cp or the mkdir commands) to an init.d script.

You could also choose a symlink instead

Code:
mkdir /storage/external_SD/google_downloads

cp -rp /data/data/com.android.providers.downloads/cache /storage/external_SD/google_downloads

rm -r /data/data/com.android.providers.downloads/cache

ln -s /storage/external_SD/google_downloads /data/data/com.android.providers.downloads/cache
Mounts are commands issued to the operating system to control the current running state of the system. They're used to mount devices (like CD Roms, SD cards, new hard drives) in Unix/Linux. They don't persist past reboots unless they're added to the startup configuration of the machine.

Links are part of the filesystem. They're "specialized" entries in the directory, and therefore are retained between reboots.

Some applications don't do well with links, but Google Play doesn't have a problem with them for it's download directory.

The mount and link command examples are "manual" adjustments similar to those found in the various solutions you're using, like app2external_sd or link2sd.

If you learn them you can adjust storage more completely on your own as you discover where things are stored.

I couldn't find documentation on the subject of Google Play's temp directory. What I did was to snap an image of the directory while downloading from Google to see where "new" files had just appeared.
JVene is offline  
Reply With Quote
Old January 26th, 2014, 07:59 PM   #12 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by JVene View Post
alexcool25565, I must apologize. Normally I'm not such a set of twisted fingers, but for some reason typing this has been a mess.

So...I copied this out of the adb shell after getting the command to actually work on the device, and I STILL had to do it 3 times to get it right.

Yikes, getting old sucks!

This will work!

Code:
df /data/data/com.android.providers.downloads

Filesystem                 Size         Used         Free    Blksize
/data/data/com.android.providers.downloads      1.27G      597.62M      703.86M       4096
This includes the result I see on the stock arrangement of my device (I have other configurations that show this instead)

Code:
Filesystem                 Size         Used         Free    Blksize
/data/data/com.android.providers.downloads        29.04G        6.50G       22.54G       4096
In the first one, the stock configuration is shown.

In the second one, an experimental configuration I'm discussing in a thread on a proposed theory to remap storage of the device.

Notice how the total free space change dramatically.

Now, to continue this investigation of your machine's configuration, try df on this:

Note: Double check my typing, we've already learned I'm not exactly precise sometimes

Code:
df /storage/sdcard0
df /data/media
df /sdcard
On the stock device, these 3 directories are routed to the same place. In the "swapped" arrangement you're using, I expect them to be routed to the external SD card instead.

If your /data/data/com.android.providers.downloads is not routed to the same device as /sdcard and /storage/sdcard0, then downloads from other sources might have room while downloads from Google Play would not.

You can temporarily solve the problem with a mount, or for a longer term solution, put the mount into an init.d script, or use a symbolic link.

Something like (and by that I mean this example is an illustration, you'd choose names and locations you prefer, and my typing may be inexact, I'm not testing this on my device as I type it)

Code:
mkdir /storage/external_SD/google_downloads

cp -rp /data/data/com.android.providers.downloads/cache /storage/external_SD/google_downloads

mount -o rw,bind /storage/external_SD/google_downloads /data/data/com.android.providers.downloads/cache
In that example I assume a directory called google_downloads is already created on the external card.

The mount is temporary in the sense that it won't stay around after a reboot.

You can make the mount stick by adding it (not the cp or the mkdir commands) to an init.d script.

You could also choose a symlink instead

Code:
mkdir /storage/external_SD/google_downloads

cp -rp /data/data/com.android.providers.downloads/cache /storage/external_SD/google_downloads

rm -r /data/data/com.android.providers.downloads/cache

ln -s /storage/external_SD/google_downloads /data/data/com.android.providers.downloads/cache
Mounts are commands issued to the operating system to control the current running state of the system. They're used to mount devices (like CD Roms, SD cards, new hard drives) in Unix/Linux. They don't persist past reboots unless they're added to the startup configuration of the machine.

Links are part of the filesystem. They're "specialized" entries in the directory, and therefore are retained between reboots.

Some applications don't do well with links, but Google Play doesn't have a problem with them for it's download directory.

The mount and link command examples are "manual" adjustments similar to those found in the various solutions you're using, like app2external_sd or link2sd.

If you learn them you can adjust storage more completely on your own as you discover where things are stored.

I couldn't find documentation on the subject of Google Play's temp directory. What I did was to snap an image of the directory while downloading from Google to see where "new" files had just appeared.

I got this https://copy.com/Q0wnWyXBgsyX

Now how would i set up the symbolic link for google play to download stuff in to the sd card?
alexcool25565 is offline  
Reply With Quote
Old January 26th, 2014, 11:54 PM   #13 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
I got this https://copy.com/Q0wnWyXBgsyX

Now how would i set up the symbolic link for google play to download stuff in to the sd card?
This report tells me that you have an 8 Gbyte card (or partition) mounted for access through both /sdcard and /storage/sdcard0. These are commonly routed to /data/media, and therefore the internal SD card, on stock devices. This informs me that you have the app2external_sd application, which I think you mentioned.

This means your directory /storage/external_SD is probably mounted to /data/media.

You can confirm this with the mount command (maybe post the result if you need another eye on it). Typing mount with no parameters shows the report. Also, df /storage/external_SD would report the same space as the /data/media shows here.

Ok, to direct Google play you should create a directory on the external card, which in your case is visible through /sdcard or /storage/sdcard0 (they're the same directory ultimately).

mkdir /sdcard/google_downloads

or something to that effect...your preference, as long as it's under /sdcard

to make sure permissions are wide open,

chmod 777 /sdcard/google_download_cache

The directory you want to re-direct (and this time I'm double checking this ) is /data/data/com.android.providers.downloads/cache

There are a few directories under /data/data/com.android.providers.downloads, and the cache directory is the one you need to route.

Just so any existing content remains available (though it's not critically important)....copy it.

cp -rp /data/data/com.android.providers.downloads/cache/* /sdcard/google_download_cache

Adjust the tail of that command to your directory name preference..it's the directory you made earlier.

You've asked about creating a link, and I did that myself in earlier experiments...Google worked fine with this. There are valid reasons to consider a mount...it's an alternate way of doing this.

But first, the symbolic link method:

Now that the content of the cache has been copied, we must remove the cache content on the source (this MAY free up a little space, but we also need the directory gone to create the link there).

Take a careful moment when typing the rm command below, it recursively removes all files from the given directory and all it's subdirectories...get it right.

perhaps a preparatory:

ls -l /data/data/com.android.providers.downloads

helps make sure we're both pointing to the right place...yes, I left of "cache" above compared to below.

rm -r /data/data/com.android.providers.downloads/cache

That rm removes the content of the cache recursively.

Now, finally, create the link - the first directory parameter (/sdcard/google_download_cache) is the name I use as an example, substitute what you chose to creat

ln -s /sdcard/google_download_cache /data/data/com.android.providers.downloads/cache

The link that is create is the last parameter...the link is cache under /data/data/com.android.providers.downloads

now, ls -l /data/data/com.android.providers.downloads

You'll see a few directories listed, and the one entry named cache will be identified as a link to /sdcard/google_download_cache.

Just so we're clear about all of this, there are a few minor consequences.

If the external SD card is removed, this link will point to nowhere. Google Play would suddenly be unable to download anything.

If the directory this link points to is removed, the same thing results.

If you decide to move things around, you can simply rm the link (that is, rm /data/data/com.android.providers.downloads/cache) - then remake the link to some other location.

You could just mkdir to recreate the original cache directory as it was to undo this.

If you remove app2external_SD, this link will again point to no where.

On a stock device (where app2external_sd has NOT routed /sdcard to the external card), the destination for the same example directory I had you create above would then be

/storage/external_SD/google_download_cache

I point this out in case you uninstall app2exernal_sd and want Google to continue working - you'd have to refashion the link to fix that.


Ok, that's about it for the link approach, now about the mount approach. Mounting is typically reserved for more upper level directories and devices, but it can be applied anywhere and has a similar resulting effect as a symbolic link with an important difference.

Some applications explicitly look for and occasionally have problems with symbolic links. If you copy a directory with symbolic links inside it, what is copied is not the CONTENT, but the LINK (basically just a notation that it is LINK). That is usually the correct choice, but not always. If, for example, you expect to back things up, the link approach produces a LINK in the backup archive, but the CONTENT is not backed up, unless you explicitly tell the backup software to descend through symbolic links to get the data instead.

In general use, if an application refers to directory or a file that is a symbolic link, opens it and uses it - doing exactly what you'd expect...it ends up getting the information from where the link directs it. Not ALL applications do that, and backup software is among them. The copy command (cp) is another.

Mounts, however, don't cause this behavior. When you backup from locations with mounts, there is no link - the backup gets CONTENT, just like any normal directory.

The problem with mounts is that they don't stick around after a reboot. They only stay around while the machine is running. Links are written to a directory, and therefore DO stick around between reboots. Mounts are commands to the operating system...nothing is written to a directory, so they have to be written into startup scripts if you need them to be mounted at every boot (this is a typical configuration choice).

For the Google Play directory this has no serious consequence, but now that you know how to create symbolic links you need to be aware of their side effect, and the alternative.

The mount command's use is like this:

mount -o rw,bind /sdcard/google_download_cache /data/data/com.android.providers.downloads/cache

This is a bind mount...the assumption being that your binding the source directory, /sdcard/google_download_cache to the destination directory /data/data/com.android.providers.downloads/cache

Both directories must exist for this to work. To use a mount instead of a link, you begin with the same steps I listed above for the link, but stop at the link (and don't perform the link).

Then, one time only, after you have removed (with rm -r ) the old /data/data/com.android.providers/cache content, you must create the empty directory named cache to receive the mount.

mkdir /data/data/com.android.providers.downloads/cache

The empty directory will stay between reboots, but the mount command only lasts until a reboot.

To use a mount you must install something like Smanager or Universal Init.d and follow their instructions to place the mount command in a shell script that will execute at every boot.

That's simply how mounts are used which must be persistent. They have significant advantages over links, but require initialization scripts.

I point this out because I know the problem you're solving. I had it too....you will eventually run out of space, again and again. You'll probably want to route other locations to targets on the external card, and now you have some information on how to do that. I've been at this for decades. I know how this is.

There's an axiom I learned back in the mid 80's when 60 Mbytes (yes Mbytes not Gbytes) was considered large for a PC. The axiom is...data will tend to occupy all available space.

That has actually gotten worse over time, so you'll need to understand what you can do about it short of a full scale solution.

I've just completed work on a full scale solution which I have working on my LG F6. For me there is not an internal/external debate anymore. The entire /data directory is routed to a 28 Gbyte partition. I have room from hundreds of applications and download space. I'm preparing a means of installing the solution for F6 devices by minimally experienced owners. Unfortunately it wasn't as simple as mounting external space over /data...that is basically the goal, but the obstacles in the way required that I recompiled a small binary file that is part of the Android operating system. /data is too "top level" to be mounted over once Android is running. It has to be done before Android takes over, but after Linux is up.

I have a short thread on the F3 forum pointing to a technical discussion on the subject on the F6, which documents the theory and discusses my experiments leading to a complete solution to the storage problem.

Well, as complete as the size of an external storage device.

That is my caution to you. Some applications just don't like being messed with, and Google is one of them. This cache directory never caused it a problem, but anything above the cache directory caused Google to repeatedly complain, virtually disabling the phone until I disabled Google.

One can only discover through experiment under these conditions (virtually zero documentation regarding our targets).
JVene is offline  
Reply With Quote
Old January 27th, 2014, 04:41 PM   #14 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by JVene View Post
This report tells me that you have an 8 Gbyte card (or partition) mounted for access through both /sdcard and /storage/sdcard0. These are commonly routed to /data/media, and therefore the internal SD card, on stock devices. This informs me that you have the app2external_sd application, which I think you mentioned.

This means your directory /storage/external_SD is probably mounted to /data/media.

You can confirm this with the mount command (maybe post the result if you need another eye on it). Typing mount with no parameters shows the report. Also, df /storage/external_SD would report the same space as the /data/media shows here.

Ok, to direct Google play you should create a directory on the external card, which in your case is visible through /sdcard or /storage/sdcard0 (they're the same directory ultimately).

mkdir /sdcard/google_downloads

or something to that effect...your preference, as long as it's under /sdcard

to make sure permissions are wide open,

chmod 777 /sdcard/google_download_cache

The directory you want to re-direct (and this time I'm double checking this ) is /data/data/com.android.providers.downloads/cache

There are a few directories under /data/data/com.android.providers.downloads, and the cache directory is the one you need to route.

Just so any existing content remains available (though it's not critically important)....copy it.

cp -rp /data/data/com.android.providers.downloads/cache/* /sdcard/google_download_cache

Adjust the tail of that command to your directory name preference..it's the directory you made earlier.

You've asked about creating a link, and I did that myself in earlier experiments...Google worked fine with this. There are valid reasons to consider a mount...it's an alternate way of doing this.

But first, the symbolic link method:

Now that the content of the cache has been copied, we must remove the cache content on the source (this MAY free up a little space, but we also need the directory gone to create the link there).

Take a careful moment when typing the rm command below, it recursively removes all files from the given directory and all it's subdirectories...get it right.

perhaps a preparatory:

ls -l /data/data/com.android.providers.downloads

helps make sure we're both pointing to the right place...yes, I left of "cache" above compared to below.

rm -r /data/data/com.android.providers.downloads/cache

That rm removes the content of the cache recursively.

Now, finally, create the link - the first directory parameter (/sdcard/google_download_cache) is the name I use as an example, substitute what you chose to creat

ln -s /sdcard/google_download_cache /data/data/com.android.providers.downloads/cache

The link that is create is the last parameter...the link is cache under /data/data/com.android.providers.downloads

now, ls -l /data/data/com.android.providers.downloads

You'll see a few directories listed, and the one entry named cache will be identified as a link to /sdcard/google_download_cache.

Just so we're clear about all of this, there are a few minor consequences.

If the external SD card is removed, this link will point to nowhere. Google Play would suddenly be unable to download anything.

If the directory this link points to is removed, the same thing results.

If you decide to move things around, you can simply rm the link (that is, rm /data/data/com.android.providers.downloads/cache) - then remake the link to some other location.

You could just mkdir to recreate the original cache directory as it was to undo this.

If you remove app2external_SD, this link will again point to no where.

On a stock device (where app2external_sd has NOT routed /sdcard to the external card), the destination for the same example directory I had you create above would then be

/storage/external_SD/google_download_cache

I point this out in case you uninstall app2exernal_sd and want Google to continue working - you'd have to refashion the link to fix that.


Ok, that's about it for the link approach, now about the mount approach. Mounting is typically reserved for more upper level directories and devices, but it can be applied anywhere and has a similar resulting effect as a symbolic link with an important difference.

Some applications explicitly look for and occasionally have problems with symbolic links. If you copy a directory with symbolic links inside it, what is copied is not the CONTENT, but the LINK (basically just a notation that it is LINK). That is usually the correct choice, but not always. If, for example, you expect to back things up, the link approach produces a LINK in the backup archive, but the CONTENT is not backed up, unless you explicitly tell the backup software to descend through symbolic links to get the data instead.

In general use, if an application refers to directory or a file that is a symbolic link, opens it and uses it - doing exactly what you'd expect...it ends up getting the information from where the link directs it. Not ALL applications do that, and backup software is among them. The copy command (cp) is another.

Mounts, however, don't cause this behavior. When you backup from locations with mounts, there is no link - the backup gets CONTENT, just like any normal directory.

The problem with mounts is that they don't stick around after a reboot. They only stay around while the machine is running. Links are written to a directory, and therefore DO stick around between reboots. Mounts are commands to the operating system...nothing is written to a directory, so they have to be written into startup scripts if you need them to be mounted at every boot (this is a typical configuration choice).

For the Google Play directory this has no serious consequence, but now that you know how to create symbolic links you need to be aware of their side effect, and the alternative.

The mount command's use is like this:

mount -o rw,bind /sdcard/google_download_cache /data/data/com.android.providers.downloads/cache

This is a bind mount...the assumption being that your binding the source directory, /sdcard/google_download_cache to the destination directory /data/data/com.android.providers.downloads/cache

Both directories must exist for this to work. To use a mount instead of a link, you begin with the same steps I listed above for the link, but stop at the link (and don't perform the link).

Then, one time only, after you have removed (with rm -r ) the old /data/data/com.android.providers/cache content, you must create the empty directory named cache to receive the mount.

mkdir /data/data/com.android.providers.downloads/cache

The empty directory will stay between reboots, but the mount command only lasts until a reboot.

To use a mount you must install something like Smanager or Universal Init.d and follow their instructions to place the mount command in a shell script that will execute at every boot.

That's simply how mounts are used which must be persistent. They have significant advantages over links, but require initialization scripts.

I point this out because I know the problem you're solving. I had it too....you will eventually run out of space, again and again. You'll probably want to route other locations to targets on the external card, and now you have some information on how to do that. I've been at this for decades. I know how this is.

There's an axiom I learned back in the mid 80's when 60 Mbytes (yes Mbytes not Gbytes) was considered large for a PC. The axiom is...data will tend to occupy all available space.

That has actually gotten worse over time, so you'll need to understand what you can do about it short of a full scale solution.

I've just completed work on a full scale solution which I have working on my LG F6. For me there is not an internal/external debate anymore. The entire /data directory is routed to a 28 Gbyte partition. I have room from hundreds of applications and download space. I'm preparing a means of installing the solution for F6 devices by minimally experienced owners. Unfortunately it wasn't as simple as mounting external space over /data...that is basically the goal, but the obstacles in the way required that I recompiled a small binary file that is part of the Android operating system. /data is too "top level" to be mounted over once Android is running. It has to be done before Android takes over, but after Linux is up.

I have a short thread on the F3 forum pointing to a technical discussion on the subject on the F6, which documents the theory and discusses my experiments leading to a complete solution to the storage problem.

Well, as complete as the size of an external storage device.

That is my caution to you. Some applications just don't like being messed with, and Google is one of them. This cache directory never caused it a problem, but anything above the cache directory caused Google to repeatedly complain, virtually disabling the phone until I disabled Google.

One can only discover through experiment under these conditions (virtually zero documentation regarding our targets).
wow that was alot lol.. anyway im new with this phone and i really dont wanna mess it up can you like guide me through redirecting google play to the sd card. Thanks so much
alexcool25565 is offline  
Reply With Quote
Old January 27th, 2014, 05:10 PM   #15 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

Ok, this is actually a repeat of half that post, slightly distilled.

It is for the symbolic link.

For anyone else reading this, it is assumed for this situation that app2external_sd is installed, meaning that /storage/external_SD and /storage/sdcard0 (and thus /sdcard) are SWAPPED.

If this is being done on a phone that does NOT have app2external_sd installed, then those owners should substitute "/storage/external_SD/ for every appearance of "/sdcard/" in these instructions.


You have to be able to use the ADB utility. To do that you have to be sure that debugging is enabled under "developer options" in the "settings" app. This option is grayed out if the cable is connected.

You should also visit "PC Connection" in settings, select the "media" option (the second option).

You also must have rooted the phone.

Then, open a command prompt, change to the directory where you installed ADB, and type:

adb shell

That gives you a prompt with a $ at the end. Then:

su

The prompt then ends with #, indicating you are now the root user, AKA super user.

If you can't get this far, we have to go over how to use ADB, ensure your USB drivers from LG are installed, that debugging is turned on.


Next, these two

mkdir /sdcard/google_downloads
chmod 777 /sdcard/google_download_cache

Then:

cp -rp /data/data/com.android.providers.downloads/cache/* /sdcard/google_download_cache

Then:

cd /data/data/com.android.providers.downloads

and:

rm -r cache

ln -s /sdcard/google_download_cache cache

I adjusted these instructions slightly, specifically the "cd /data/data/......" to make it a little easier to type the commands and be sure you're in the right position for the two that follow.

That creates the symbolic link with Google Play will use as the download destination.
JVene is offline  
Last edited by JVene; January 27th, 2014 at 05:16 PM.
Reply With Quote
Old January 27th, 2014, 05:31 PM   #16 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by JVene View Post
Ok, this is actually a repeat of half that post, slightly distilled.

It is for the symbolic link.

For anyone else reading this, it is assumed for this situation that app2external_sd is installed, meaning that /storage/external_SD and /storage/sdcard0 (and thus /sdcard) are SWAPPED.

If this is being done on a phone that does NOT have app2external_sd installed, then those owners should substitute "/storage/external_SD/ for every appearance of "/sdcard/" in these instructions.


You have to be able to use the ADB utility. To do that you have to be sure that debugging is enabled under "developer options" in the "settings" app. This option is grayed out if the cable is connected.

You should also visit "PC Connection" in settings, select the "media" option (the second option).

You also must have rooted the phone.

Then, open a command prompt, change to the directory where you installed ADB, and type:

adb shell

That gives you a prompt with a $ at the end. Then:

su

The prompt then ends with #, indicating you are now the root user, AKA super user.

If you can't get this far, we have to go over how to use ADB, ensure your USB drivers from LG are installed, that debugging is turned on.


Next, these two

mkdir /sdcard/google_downloads
chmod 777 /sdcard/google_download_cache

Then:

cp -rp /data/data/com.android.providers.downloads/cache/* /sdcard/google_download_cache

Then:

cd /data/data/com.android.providers.downloads

and:

rm -r cache

ln -s /sdcard/google_download_cache cache

I adjusted these instructions slightly, specifically the "cd /data/data/......" to make it a little easier to type the commands and be sure you're in the right position for the two that follow.

That creates the symbolic link with Google Play will use as the download destination.
not sure if you typed this one correctly.
chmod 777 /sdcard/google_download_cache
alexcool25565 is offline  
Reply With Quote
Old January 27th, 2014, 06:02 PM   #17 (permalink)
Senior Member
 
Muilisx's Avatar
 
Join Date: Jan 2011
Location: Long Island, NY
Gender: Male
Posts: 1,071
 
Device(s): Galaxy S3
Carrier: MetroPCS

Thanks: 61
Thanked 175 Times in 145 Posts
Send a message via AIM to Muilisx
Default

Not trying to disrespect anyone or their phones but you knew it was only up to 1.2GB of internal space when you bought it, so after the OS, and bloatware, you're probably around 800-900MB of space available to the user which will go VERY VERY FAST. Rooting, and moving everything to the SD card will only help for so long. The F6 seems like a great phone all around from the phone itself to the camera, but internal space is very low, and is very important when it comes to buying a phone so when I saw the space available, I said, no thanks.
__________________
•NY•
Muilisx is online now  
Reply With Quote
Old January 27th, 2014, 06:32 PM   #18 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
not sure if you typed this one correctly.
chmod 777 /sdcard/google_download_cache

Actually, this is the one I didn't type correctly

mkdir /sdcard/google_downloads


It SHOULD be

mkdir /sdcard/google_download_cache


to match the remaining instructions.

The name could be anything you want, but google_download_cache will do.
JVene is offline  
Reply With Quote
Old January 27th, 2014, 06:56 PM   #19 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

Quote:
Originally Posted by NY11725 View Post
Not trying to disrespect anyone or their phones but you knew it was only up to 1.2GB of internal space when you bought it, so after the OS, and bloatware, you're probably around 800-900MB of space available to the user which will go VERY VERY FAST. Rooting, and moving everything to the SD card will only help for so long. The F6 seems like a great phone all around from the phone itself to the camera, but internal space is very low, and is very important when it comes to buying a phone so when I saw the space available, I said, no thanks.

...and I hope you take this response without offense in kind, but I've seen this general post on several "storage" related threads, though I don't recall the identity on those posts.

I'm a software engineer of decades experience. I know this technology extremely well. While your point is reasonable, it's not the entire story.

Virtually every Android device has this problem. It doesn't matter if primary storage is 1.2Gbytes, 3Gbytes, 5Gbytes or 7. Eventually, if the user installs applications of sufficient size, they all fill up.

This problem IS exacerbated on the F6 and similar devices, but every Android device exhibits the problem.

Android has no good solution on the settings page. It should. It is nearly trivial to correct from the AOSP source (which I have for 7 versions of this OS). They've never addressed the issue. That's Google's failure, or the open source developer community, for not providing a solution to this problem.

I have an F6, which has the same storage problem of the F3 and other phones. Yet, on my F6, I have 28 Gbytes of space for applications, temporaries, data, cache...everything.

I applied the same theoretical solution to the Kindle Fire first generation, but put the additional storage on a network drive. The Fire only has a 8 GByte internal SD, but even the other units, including the Samsung Galaxy tablets, don't have a solution to the storage problem once their internal storage is filled. The extenal SD cards are still unused as PRIMARY storage extension.

I've solved that problem for myself. I'm preparing a beta solution for others. Anyone able to use a custom ROM may avail themselves of a solution on their own. The F6 wouldn't have this problem if custom ROM's addressed it. LG could address it, but ultimately it's Google's fault for implementing a standard which perpetuates this problem.

Consumers should expect that adding an SD card expands storage. They shouldn't have to consider what that storage is limited to. It would be like purchasing a larger SD card for a camera only to learn that the manufacturer didn't mean it could store images, only some temporary files - or that it could store pictures, and LOTS of them, but only at limited resolutions.

Now, you may note that this somewhat supports your point.

My point is that the target of the complaint isn't specifically this model phone, but ultimately is the fault of Google.

After I did the reverse engineering, looked through the AOSP source for the operating system, and realized what is really happening, it took me about 30 minutes to experimentally prepare a solution that worked. It subsequently took about 10 days to polish all the details about that solution and begin packaging it into something end users MIGHT be able to install themselves, given certain caveats (rooting among them), but really...Google could have made this a first class end user solution as simple as a selection on the settings page.

That would have solved this problem for all devices, all models (except the Kindle Fire first gen; it has no external SD slot - which hampered it's acceptance, and they responded to the market).
JVene is offline  
Reply With Quote
Old January 27th, 2014, 07:17 PM   #20 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by JVene View Post
Actually, this is the one I didn't type correctly

mkdir /sdcard/google_downloads


It SHOULD be

mkdir /sdcard/google_download_cache


to match the remaining instructions.

The name could be anything you want, but google_download_cache will do.
It worked, then came to this one
cp -rp /data/data/com.android.providers.downloads/cache/* /sdcard/google_download_cache

no such file or directory
alexcool25565 is offline  
Reply With Quote
sponsored links
Old January 27th, 2014, 11:01 PM   #21 (permalink)
Senior Member
 
Muilisx's Avatar
 
Join Date: Jan 2011
Location: Long Island, NY
Gender: Male
Posts: 1,071
 
Device(s): Galaxy S3
Carrier: MetroPCS

Thanks: 61
Thanked 175 Times in 145 Posts
Send a message via AIM to Muilisx
Default

Quote:
Originally Posted by JVene View Post
...and I hope you take this response without offense in kind, but I've seen this general post on several "storage" related threads, though I don't recall the identity on those posts.

I'm a software engineer of decades experience. I know this technology extremely well. While your point is reasonable, it's not the entire story.

Virtually every Android device has this problem. It doesn't matter if primary storage is 1.2Gbytes, 3Gbytes, 5Gbytes or 7. Eventually, if the user installs applications of sufficient size, they all fill up.

This problem IS exacerbated on the F6 and similar devices, but every Android device exhibits the problem.

Android has no good solution on the settings page. It should. It is nearly trivial to correct from the AOSP source (which I have for 7 versions of this OS). They've never addressed the issue. That's Google's failure, or the open source developer community, for not providing a solution to this problem.

I have an F6, which has the same storage problem of the F3 and other phones. Yet, on my F6, I have 28 Gbytes of space for applications, temporaries, data, cache...everything.

I applied the same theoretical solution to the Kindle Fire first generation, but put the additional storage on a network drive. The Fire only has a 8 GByte internal SD, but even the other units, including the Samsung Galaxy tablets, don't have a solution to the storage problem once their internal storage is filled. The extenal SD cards are still unused as PRIMARY storage extension.

I've solved that problem for myself. I'm preparing a beta solution for others. Anyone able to use a custom ROM may avail themselves of a solution on their own. The F6 wouldn't have this problem if custom ROM's addressed it. LG could address it, but ultimately it's Google's fault for implementing a standard which perpetuates this problem.

Consumers should expect that adding an SD card expands storage. They shouldn't have to consider what that storage is limited to. It would be like purchasing a larger SD card for a camera only to learn that the manufacturer didn't mean it could store images, only some temporary files - or that it could store pictures, and LOTS of them, but only at limited resolutions.

Now, you may note that this somewhat supports your point.

My point is that the target of the complaint isn't specifically this model phone, but ultimately is the fault of Google.

After I did the reverse engineering, looked through the AOSP source for the operating system, and realized what is really happening, it took me about 30 minutes to experimentally prepare a solution that worked. It subsequently took about 10 days to polish all the details about that solution and begin packaging it into something end users MIGHT be able to install themselves, given certain caveats (rooting among them), but really...Google could have made this a first class end user solution as simple as a selection on the settings page.

That would have solved this problem for all devices, all models (except the Kindle Fire first gen; it has no external SD slot - which hampered it's acceptance, and they responded to the market).
Nicely said
JVene likes this.
Muilisx is online now  
Reply With Quote
Old January 28th, 2014, 07:36 AM   #22 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
It worked, then came to this one
cp -rp /data/data/com.android.providers.downloads/cache/* /sdcard/google_download_cache

no such file or directory
That would probably mean that Google had cleared the cache and nothing was there.

That assumes the destination directory is correct.

Back out just a little and think on this:

You're creating a directory called google_download_cache inside /sdcard.

That means all the commands that direct attention to that directory should be spelled the same (in case either of us typed it incorrectly).

The source directory is (or was) /data/data/com.android.providers.downloads/cache

That's a directory, in the stock phone, called cache under /data/data/com.android.providers.downloads

If cache is empty, then I'd expect the cp command to say something to that effect, and that would be harmless.

You can triple check that it's working as expected with a simple test.

Start by being connected through the adb shell

then:

cd /sdcard/google_download_cache
ls -l

look at what's listed (could be empty).

Now, stay connected to the shell and use Google Play to download something large enough to take a few minutes.

When it gets going, repeat the

ls -l

command.

I expect a tmp directory will be there. If so, cd to it

cd tmp

no slashes

in either case, tmp or not, do:

ls -l

You should see a file ending in .apk, usually something like download.apk (they may number them if there's more than one, and they may download updates without telling you)

If you repeated ls -l every few seconds, the file size should grow as the download proceeds.

That proves it's working as intended.
JVene is offline  
Last edited by JVene; January 28th, 2014 at 07:39 AM.
Reply With Quote
Old January 28th, 2014, 01:40 PM   #23 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by JVene View Post
That would probably mean that Google had cleared the cache and nothing was there.

That assumes the destination directory is correct.

Back out just a little and think on this:

You're creating a directory called google_download_cache inside /sdcard.

That means all the commands that direct attention to that directory should be spelled the same (in case either of us typed it incorrectly).

The source directory is (or was) /data/data/com.android.providers.downloads/cache

That's a directory, in the stock phone, called cache under /data/data/com.android.providers.downloads

If cache is empty, then I'd expect the cp command to say something to that effect, and that would be harmless.

You can triple check that it's working as expected with a simple test.

Start by being connected through the adb shell

then:

cd /sdcard/google_download_cache
ls -l

look at what's listed (could be empty).

Now, stay connected to the shell and use Google Play to download something large enough to take a few minutes.

When it gets going, repeat the

ls -l

command.

I expect a tmp directory will be there. If so, cd to it

cd tmp

no slashes

in either case, tmp or not, do:

ls -l

You should see a file ending in .apk, usually something like download.apk (they may number them if there's more than one, and they may download updates without telling you)

If you repeated ls -l every few seconds, the file size should grow as the download proceeds.

That proves it's working as intended.
Ok thanks and now when i entered this ln -s /sdcard/google_download_cache cache
Says sh: syntax error: 'in' unexpected not sure what that means.
alexcool25565 is offline  
Reply With Quote
Old January 28th, 2014, 02:59 PM   #24 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
Ok thanks and now when i entered this ln -s /sdcard/google_download_cache cache
Says sh: syntax error: 'in' unexpected not sure what that means.
ln is the link command.

In the form you quoted the command must be typed while the current directory is /data/data/com.android.providers.downloads

Are you sure you typed ln, not in...ln stands for link, so that's l as in link, n as in nancy.
JVene is offline  
Reply With Quote
Old January 28th, 2014, 04:49 PM   #25 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by JVene View Post
ln is the link command.

In the form you quoted the command must be typed while the current directory is /data/data/com.android.providers.downloads

Are you sure you typed ln, not in...ln stands for link, so that's l as in link, n as in nancy.
opps lol i put a i instead of a l .

so i did it and when entered it it said Cache link failed file exists then the /data/data/com.android.providers.downlods link came up with the # at the end.
alexcool25565 is offline  
Reply With Quote
Old January 28th, 2014, 08:00 PM   #26 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
opps lol i put a i instead of a l .

so i did it and when entered it it said Cache link failed file exists then the /data/data/com.android.providers.downlods link came up with the # at the end.
That means the cache directory may not have been removed.

try:

cd /data/data/com.android.providers.downloads
ls -l

Look to see if cache exists. The error tells me it does.

It may already be a link for some reason (you've tried several things). If it is, you can read where it's link to - report that back if you see it.

If cache is a directory, then:

rm -r cache

Then try the link command
JVene is offline  
Reply With Quote
Old January 29th, 2014, 01:34 PM   #27 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by JVene View Post
That means the cache directory may not have been removed.

try:

cd /data/data/com.android.providers.downloads
ls -l

Look to see if cache exists. The error tells me it does.

It may already be a link for some reason (you've tried several things). If it is, you can read where it's link to - report that back if you see it.

If cache is a directory, then:

rm -r cache

Then try the link command
Alright, i did that now says opendir permission denied for both commands ls -l
and rm -r cache
alexcool25565 is offline  
Reply With Quote
Old January 30th, 2014, 05:33 PM   #28 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
Alright, i did that now says opendir permission denied for both commands ls -l
and rm -r cache

alexcool, I'm sorry this is giving you so much trouble, but it appears that you're proceeding on a step by step basis without real comprehension of the commands you're following. I empathize, these things are technically deep.

To do what you want, you'll really need to consider reading a little on using the Linux shell, sometimes referred to as the bash shell (Android uses a simplified version of it).

Now, to your specific problem at this point:

About the only reason I can think this would give you such a response is if you're not operating as the super user, AKA root user.

If the prompt you're getting from the phone ends with a $, you're a "regular" user.

You have to enter "su" to switch to the super user.

The prompt will then end with a #.

When you're configuring a device that has been rooted, and require the level of security access only available to the super user, you must be sure the # is at the end of the prompt, or the commands will be denied on a security basis.

This is one of the primary reasons for rooting a phone.

To this point I've proceeded under the assumption that you're over 25 years of age. There are two reasons I can think of that someone would be inquiring here for instructions of this level:

1 - An Android device owner entirely unfamiliar with the technology, but so frustrated with the phone that they're willing to push through and spend time trying to fix it, because they've invested significant money into the device and can't use it others.

2 - An Android device owner younger than 21, curious about the phone, interested in pushing it's limits and correcting its flaws, and otherwise unfamiliar with the technology.

I need to learn which applies to you?

You're going through quite a lot of obstacles to complete what is, to someone of 30+ year's experience as I have, a quick task.

I empathize with everyone...literally hundreds of millions of people...for which this technology is a complete mystery.
JVene is offline  
Reply With Quote
Old January 31st, 2014, 02:27 PM   #29 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by JVene View Post
alexcool, I'm sorry this is giving you so much trouble, but it appears that you're proceeding on a step by step basis without real comprehension of the commands you're following. I empathize, these things are technically deep.

To do what you want, you'll really need to consider reading a little on using the Linux shell, sometimes referred to as the bash shell (Android uses a simplified version of it).

Now, to your specific problem at this point:

About the only reason I can think this would give you such a response is if you're not operating as the super user, AKA root user.

If the prompt you're getting from the phone ends with a $, you're a "regular" user.

You have to enter "su" to switch to the super user.

The prompt will then end with a #.

When you're configuring a device that has been rooted, and require the level of security access only available to the super user, you must be sure the # is at the end of the prompt, or the commands will be denied on a security basis.

This is one of the primary reasons for rooting a phone.

To this point I've proceeded under the assumption that you're over 25 years of age. There are two reasons I can think of that someone would be inquiring here for instructions of this level:

1 - An Android device owner entirely unfamiliar with the technology, but so frustrated with the phone that they're willing to push through and spend time trying to fix it, because they've invested significant money into the device and can't use it others.

2 - An Android device owner younger than 21, curious about the phone, interested in pushing it's limits and correcting its flaws, and otherwise unfamiliar with the technology.

I need to learn which applies to you?

You're going through quite a lot of obstacles to complete what is, to someone of 30+ year's experience as I have, a quick task.

I empathize with everyone...literally hundreds of millions of people...for which this technology is a complete mystery.
Ok, i think i would be the 2nd one.
I redid everything being superuser with the # at the end. I think i did it correct this time no errors came up. not sure if it worked or not yet. Also how would i partition my sd card so i can move other apps on internal to the sdcard. Thanks
alexcool25565 is offline  
Reply With Quote
Old January 31st, 2014, 05:46 PM   #30 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

JVene, a little bit earlier when i cleared the cache using link2sd i started to get this pop up message "unfortunately the process android.process.media has stopped." i cant open the gallery and it pops up quite alot. any thing i can do to fix it? Thanks.
alexcool25565 is offline  
Reply With Quote
sponsored links
Old February 3rd, 2014, 12:05 PM   #31 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

Partitioning the SD card can be done with a free app called AParted. I've not used it, so I can't attest to how it works, but that's it's intention. I assume you're planning to use 'link2sd' with it's requirement to partition the card.

You can prove the link is working with a simple test. Get into the shell "adb shell", switch to su (root/super user), then:

cd /data/data
df ./
cd com.android.providers.downloads
df ./
cd cache
df ./

The first two 'df' commands should report the space on the INTERNAL sd card.

The last one should report the space of the EXTERNAL sd card.

That's because, if all worked well, the directory 'cache' inside com.android.providers.downloads (itself under /data/data) is routed by the symbolic link.

Now, as to the clear cache issue...I'm not exactly sure.

I'll have to wait until my son returns with his F6 to discover where the gallery and 'android.process.media' store their information. Something they expect to see is now gone.

As you proceed, you'll want to be sure to backup anything you deem of value precisely because this kind of thing can happen.

I have to take some care and concern here. Being among the "under 21" category as I asked earlier explains why you'd have the persistence in solving these issues. Most in the 'over 25' category would loose patience and pay someone else to fix their phone.

The problem is that you're proceeding with powerful commands without genuine comprehension. When I was 17 I had a Fiat Spyder, rusted to it's ears. I was by no means a mechanic, but I was audacious about tinkering and the car needed the head serviced (two valves, it turns out, were burned and damaged, though the car still ran).

It was winter, so I was working in a garage. I didn't realize one is supposed to disconnect the battery before doing this kind of work. I demonstrated why, to myself. As I reached for the last bolt on the head I hopped up on the car, one knee on the driver side fender, the other by the radiator, the engine below me. I got the bolt off, lifted the head and...spark! The head brushed against some positive lead coming from the battery and ignited the fuel vapor. A flash of flame washed over my face and thorax, then a raging fire engulfed the engine underneath me. It took me at least 2 seconds, INSIDE that fire, to figure out where to drop the head so I could find an extinguisher, which of course I didn't have. I ended up emptying 3 cans of Sprite, shaken vigorously, to put out the fire. For some reason that worked, just as the fire department arrived (someone heard and apparently looked to see me fighting to save the house from burning down).

Now, fortunately, the days of destroying computer equipment in a blaze of sparks and fire is behind us (there was a time). Yet, with respect to the relative safety of the experiment, you are in the 21st century analogy of doing something like that.

Hence, expect Google applications to complain, repeatedly, if something isn't exactly where they expect it to be.
JVene is offline  
Reply With Quote
Old February 3rd, 2014, 07:53 PM   #32 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

I i got it stuck in boot loop mode by changing the font and i didnt install a recovery and now i dont know what to do. i dont know how to get it out. fast help would be appreciated. thanks

update:i got it to the factory hard reset i did that and it still does boot loop.
alexcool25565 is offline  
Last edited by alexcool25565; February 3rd, 2014 at 08:01 PM.
Reply With Quote
Old February 3rd, 2014, 08:04 PM   #33 (permalink)
Member
 
Trevor Philips's Avatar
 
Join Date: Nov 2013
Location: Sandy Shores
Posts: 233
 
Device(s):
Carrier: Not Provided

Thanks: 51
Thanked 69 Times in 37 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
I i got it stuck in boot loop mode by changing the font and i didnt install a recovery and now i dont know what to do. i dont know how to get it out. fast help would be appreciated. thanks

update:i got it to the factory hard reset i did that and it still does boot loop.
from my knowledge, there is no way of escaping a boot loop but using the unbrick guide
Trevor Philips is online now  
Reply With Quote
Old February 3rd, 2014, 08:07 PM   #34 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by Trevor Philips View Post
from my knowledge, there is no way of escaping a boot loop but using the unbrick guide
how would i do that?
alexcool25565 is offline  
Reply With Quote
Old February 3rd, 2014, 08:22 PM   #35 (permalink)
Member
 
Trevor Philips's Avatar
 
Join Date: Nov 2013
Location: Sandy Shores
Posts: 233
 
Device(s):
Carrier: Not Provided

Thanks: 51
Thanked 69 Times in 37 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
how would i do that?
It requires a big download, Heres the file http://goo.gl/5uHRw1 (700mb+) , then follow the unbricking guide here Unbrick KDZ for MetroPCS (Updated 11/13/2013) , comeback to me for any more help
Trevor Philips is online now  
Reply With Quote
Old February 3rd, 2014, 08:26 PM   #36 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by Trevor Philips View Post
It requires a big download, Heres the file http://goo.gl/5uHRw1 (700mb+) , then follow the unbricking guide here Unbrick KDZ for MetroPCS (Updated 11/13/2013) , comeback to me for any more help
Thanks, but the link inst loading..
alexcool25565 is offline  
Reply With Quote
Old February 3rd, 2014, 08:29 PM   #37 (permalink)
Member
 
Trevor Philips's Avatar
 
Join Date: Nov 2013
Location: Sandy Shores
Posts: 233
 
Device(s):
Carrier: Not Provided

Thanks: 51
Thanked 69 Times in 37 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
Thanks, but the link inst loading..
try this Unbrick
Trevor Philips is online now  
Reply With Quote
Old February 4th, 2014, 04:55 AM   #38 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by Trevor Philips View Post
try this Unbrick
still not loading..
alexcool25565 is offline  
Reply With Quote
Old February 4th, 2014, 12:08 PM   #39 (permalink)
Junior Member
 
Join Date: Jan 2014
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 76 Times in 31 Posts
Default

Quote:
Originally Posted by alexcool25565 View Post
still not loading..

Hello, tech support :

The suspense is just KILLING my friend here:

I'm sending a PM to alexcool25565 with a temporary solution.
JVene is offline  
Reply With Quote
The Following User Says Thank You to JVene For This Useful Post:
Trevor Philips (February 4th, 2014)
Old February 4th, 2014, 01:34 PM   #40 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2013
Posts: 79
 
Device(s): Lg optimus f6
Carrier: MetroPcs

Thanks: 7
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by JVene View Post
Hello, tech support :

The suspense is just KILLING my friend here:

I'm sending a PM to alexcool25565 with a temporary solution.
lmao!! thanks very much i will do this as soon as i get home.
alexcool25565 is offline  
Reply With Quote
sponsored links
Old March 2nd, 2014, 03:59 PM   #41 (permalink)
New Member
 
Join Date: Jun 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Smile

Quote:
Originally Posted by JVene View Post
This report tells me that you have an 8 Gbyte card (or partition) mounted for access through both /sdcard and /storage/sdcard0. These are commonly routed to /data/media, and therefore the internal SD card, on stock devices. This informs me that you have the app2external_sd application, which I think you mentioned.

This means your directory /storage/external_SD is probably mounted to /data/media.

You can confirm this with the mount command (maybe post the result if you need another eye on it). Typing mount with no parameters shows the report. Also, df /storage/external_SD would report the same space as the /data/media shows here.

Ok, to direct Google play you should create a directory on the external card, which in your case is visible through /sdcard or /storage/sdcard0 (they're the same directory ultimately).

mkdir /sdcard/google_downloads

or something to that effect...your preference, as long as it's under /sdcard

to make sure permissions are wide open,

chmod 777 /sdcard/google_download_cache

The directory you want to re-direct (and this time I'm double checking this ) is /data/data/com.android.providers.downloads/cache

There are a few directories under /data/data/com.android.providers.downloads, and the cache directory is the one you need to route.

Just so any existing content remains available (though it's not critically important)....copy it.

cp -rp /data/data/com.android.providers.downloads/cache/* /sdcard/google_download_cache

Adjust the tail of that command to your directory name preference..it's the directory you made earlier.

You've asked about creating a link, and I did that myself in earlier experiments...Google worked fine with this. There are valid reasons to consider a mount...it's an alternate way of doing this.

But first, the symbolic link method:

Now that the content of the cache has been copied, we must remove the cache content on the source (this MAY free up a little space, but we also need the directory gone to create the link there).

Take a careful moment when typing the rm command below, it recursively removes all files from the given directory and all it's subdirectories...get it right.

perhaps a preparatory:

ls -l /data/data/com.android.providers.downloads

helps make sure we're both pointing to the right place...yes, I left of "cache" above compared to below.

rm -r /data/data/com.android.providers.downloads/cache

That rm removes the content of the cache recursively.

Now, finally, create the link - the first directory parameter (/sdcard/google_download_cache) is the name I use as an example, substitute what you chose to creat

ln -s /sdcard/google_download_cache /data/data/com.android.providers.downloads/cache

The link that is create is the last parameter...the link is cache under /data/data/com.android.providers.downloads

now, ls -l /data/data/com.android.providers.downloads

You'll see a few directories listed, and the one entry named cache will be identified as a link to /sdcard/google_download_cache.

Just so we're clear about all of this, there are a few minor consequences.

If the external SD card is removed, this link will point to nowhere. Google Play would suddenly be unable to download anything.

If the directory this link points to is removed, the same thing results.

If you decide to move things around, you can simply rm the link (that is, rm /data/data/com.android.providers.downloads/cache) - then remake the link to some other location.

You could just mkdir to recreate the original cache directory as it was to undo this.

If you remove app2external_SD, this link will again point to no where.

On a stock device (where app2external_sd has NOT routed /sdcard to the external card), the destination for the same example directory I had you create above would then be

/storage/external_SD/google_download_cache

I point this out in case you uninstall app2exernal_sd and want Google to continue working - you'd have to refashion the link to fix that.


Ok, that's about it for the link approach, now about the mount approach. Mounting is typically reserved for more upper level directories and devices, but it can be applied anywhere and has a similar resulting effect as a symbolic link with an important difference.

Some applications explicitly look for and occasionally have problems with symbolic links. If you copy a directory with symbolic links inside it, what is copied is not the CONTENT, but the LINK (basically just a notation that it is LINK). That is usually the correct choice, but not always. If, for example, you expect to back things up, the link approach produces a LINK in the backup archive, but the CONTENT is not backed up, unless you explicitly tell the backup software to descend through symbolic links to get the data instead.

In general use, if an application refers to directory or a file that is a symbolic link, opens it and uses it - doing exactly what you'd expect...it ends up getting the information from where the link directs it. Not ALL applications do that, and backup software is among them. The copy command (cp) is another.

Mounts, however, don't cause this behavior. When you backup from locations with mounts, there is no link - the backup gets CONTENT, just like any normal directory.

The problem with mounts is that they don't stick around after a reboot. They only stay around while the machine is running. Links are written to a directory, and therefore DO stick around between reboots. Mounts are commands to the operating system...nothing is written to a directory, so they have to be written into startup scripts if you need them to be mounted at every boot (this is a typical configuration choice).

For the Google Play directory this has no serious consequence, but now that you know how to create symbolic links you need to be aware of their side effect, and the alternative.

The mount command's use is like this:

mount -o rw,bind /sdcard/google_download_cache /data/data/com.android.providers.downloads/cache

This is a bind mount...the assumption being that your binding the source directory, /sdcard/google_download_cache to the destination directory /data/data/com.android.providers.downloads/cache

Both directories must exist for this to work. To use a mount instead of a link, you begin with the same steps I listed above for the link, but stop at the link (and don't perform the link).

Then, one time only, after you have removed (with rm -r ) the old /data/data/com.android.providers/cache content, you must create the empty directory named cache to receive the mount.

mkdir /data/data/com.android.providers.downloads/cache

The empty directory will stay between reboots, but the mount command only lasts until a reboot.

To use a mount you must install something like Smanager or Universal Init.d and follow their instructions to place the mount command in a shell script that will execute at every boot.

That's simply how mounts are used which must be persistent. They have significant advantages over links, but require initialization scripts.

I point this out because I know the problem you're solving. I had it too....you will eventually run out of space, again and again. You'll probably want to route other locations to targets on the external card, and now you have some information on how to do that. I've been at this for decades. I know how this is.

There's an axiom I learned back in the mid 80's when 60 Mbytes (yes Mbytes not Gbytes) was considered large for a PC. The axiom is...data will tend to occupy all available space.

That has actually gotten worse over time, so you'll need to understand what you can do about it short of a full scale solution.

I've just completed work on a full scale solution which I have working on my LG F6. For me there is not an internal/external debate anymore. The entire /data directory is routed to a 28 Gbyte partition. I have room from hundreds of applications and download space. I'm preparing a means of installing the solution for F6 devices by minimally experienced owners. Unfortunately it wasn't as simple as mounting external space over /data...that is basically the goal, but the obstacles in the way required that I recompiled a small binary file that is part of the Android operating system. /data is too "top level" to be mounted over once Android is running. It has to be done before Android takes over, but after Linux is up.

I have a short thread on the F3 forum pointing to a technical discussion on the subject on the F6, which documents the theory and discusses my experiments leading to a complete solution to the storage problem.

Well, as complete as the size of an external storage device.

That is my caution to you. Some applications just don't like being messed with, and Google is one of them. This cache directory never caused it a problem, but anything above the cache directory caused Google to repeatedly complain, virtually disabling the phone until I disabled Google.

One can only discover through experiment under these conditions (virtually zero documentation regarding our targets).
thanks for explaining the mystery ( how the whole things works) , was really helpful for me to understand !
but I think it is bit technical and needs lions's heart to try these steps ( if one doesnt know what he/she is trying to do, few wrong delete command can get you some trouble )
Trevor Philips likes this.
andriodamit is offline  
Reply With Quote
Old March 3rd, 2014, 10:24 PM   #42 (permalink)
ayi
Junior Member
 
Join Date: Dec 2013
Posts: 51
 
Device(s): LG G2 (Verizon) - LG F6 (MetroPCS)
Carrier: T-Mobile 25$ - Family Plan

Thanks: 2
Thanked 0 Times in 0 Posts
Default

can't get mounts2sd to work but Link2apps workfine.

It won't mount my external mount (ext3) like link does
ayi is offline  
Reply With Quote
Old March 11th, 2014, 03:01 PM   #43 (permalink)
New Member
 
Join Date: Mar 2014
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

can i delete smanager after everything is done
gogeta1322 is offline  
Reply With Quote
Old March 11th, 2014, 03:49 PM   #44 (permalink)
Member
 
Trevor Philips's Avatar
 
Join Date: Nov 2013
Location: Sandy Shores
Posts: 233
 
Device(s):
Carrier: Not Provided

Thanks: 51
Thanked 69 Times in 37 Posts
Default

Quote:
Originally Posted by gogeta1322 View Post
can i delete smanager after everything is done
no, it does all the work for booting up
Trevor Philips is online now  
Reply With Quote
Old March 12th, 2014, 09:33 PM   #45 (permalink)
New Member
 
Join Date: Mar 2014
Posts: 9
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by alexcool25565 View Post
1) Download Uni-init v1.0.apk

2) Install like a regular apk and open it

3) Click on Activate and allow with super user

4) Click on Verify to make sure init.d is enabled

5) Reboot your device

6) Download any Root Browser you like from the play store

7) Download 11extsd2internalsd and copy it to your sd card

8) Open Root Browser and copy 11extsd2internalsd and paste it /system/etc/init.d folder

9) Hold click 11extsd2internalsd and set permissions and make sure everything is checked as far as Read, Write, and Execute

10) Download Smanager from the google play store and open and allow with root access

11) Go to /system/etc/init.d and click on 11extsd2internalsd

12) Click at the top where it has Su and Boot and hit save and then exit

13) Reboot your device and your all done!


Did all of those but didnt realize until after that i had to change the .txt on it. i redid all the steps again when i did it.
I did steps 1- 13 nothing happened after rebooted it.
Still the internal memory is 1.2 in my lg f6 with a 32 gb external s-d card.
What should i do?
Mac09 is offline  
Reply With Quote
Old March 12th, 2014, 11:31 PM   #46 (permalink)
Member
 
Join Date: Feb 2011
Location: jax
Gender: Male
Posts: 197
 
Device(s): LG Optimus F6 - Rooted/Mem mod - Freedom Kernal 1.6ghz
Carrier: MetroPcs

Thanks: 26
Thanked 16 Times in 13 Posts
Default

I posted a possible solution in, ugh... I'll edit in a min add link.
Flablitz is offline  
Reply With Quote
Old March 12th, 2014, 11:37 PM   #47 (permalink)
Member
 
hubsabubs's Avatar
 
Join Date: Jan 2012
Location: Dallas, GA
Gender: Male
Posts: 233
 
Device(s): Huawei Ascend II, LG Optimus M, Coolpad Quattro, LG Optimus F6
Carrier: MetroPCS

Thanks: 20
Thanked 55 Times in 44 Posts
Default

Quote:
Originally Posted by Mac09 View Post
I did steps 1- 13 nothing happened after rebooted it.
Still the internal memory is 1.2 in my lg f6 with a 32 gb external s-d card.
What should i do?
Did you uninstall SManager after you were all done, because you aren't supposed to. It has to stay on the internal phone storage to initiate the script at boot, or else you will be left with your stock storage setup, because there's nothing telling it to remount.

I followed each step accordingly and had no issues, worked beautifully on first attempt.
Mac09 likes this.
hubsabubs is online now  
Reply With Quote
The Following User Says Thank You to hubsabubs For This Useful Post:
Mac09 (March 13th, 2014)
Old March 13th, 2014, 11:36 AM   #48 (permalink)
New Member
 
Join Date: Mar 2014
Posts: 9
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 1 Time in 1 Post
Default

I repeated all the steps an still i can't get it. My lg f6 is rooted I stared in step 7 to 13 but it did not work. Them I stared from 1 to 13 and still it did not worked. Would give me another solution o can you give me more details. on how to do it. I do not have experience about these issues. Should I install smanager again after reboot? I will really appreciate. Thanks
Mac09 is offline  
Reply With Quote
Old March 13th, 2014, 02:22 PM   #49 (permalink)
Member
 
hubsabubs's Avatar
 
Join Date: Jan 2012
Location: Dallas, GA
Gender: Male
Posts: 233
 
Device(s): Huawei Ascend II, LG Optimus M, Coolpad Quattro, LG Optimus F6
Carrier: MetroPCS

Thanks: 20
Thanked 55 Times in 44 Posts
Default

If you uninstalled the Smanager after doing all the steps, then you need to redownload it and install it again.

One thing I know I didn't do during this process was download the file with any sort of file association. I didn't add a .txt to the 11extsd2internalsd or anything when I saved it to my desktop. I just download the file as is and saved it as is. It's still sitting in my documents unassociated, with no file extension. In the description it just says "File". Maybe adding a file extension to it messes up the encoding on the file?

And again I repeat,

YOU CAN NOT DELETE OR UNINSTALL SMANAGER AFTER YOU DO THIS MOD!!!

It has to remain installed on the internal memory of the phone the entire time you use this mod, or else there will be nothing telling the script to remount the storage after boot!!!! Leaving you with your standard storage. As long as you use this mod you will have to keep the SManager app installed. Do not Link2SD it, do not Move to SD Card it. Leave it on the internal storage. It has to be able to be read as quickly as possible at boot, the system boots internal storage first, then scans the media on your sd card and mounts it after its all done. So you want the system finding SManager (It is set to launch on boot) as soon as it can so it can swap the mounts before the phone scans the external SD Card. It will pop up in your notification bar for a moment, then disappear and you will never see it again.

I went into my launcher and removed the SManager Icon from my app list, so in essence since I turn my screen off on boot and let it do its thing, I never see it! Unless looking at my app list in the settings menu.
hubsabubs is online now  
Last edited by hubsabubs; March 13th, 2014 at 03:18 PM.
Reply With Quote
Old March 15th, 2014, 07:33 PM   #50 (permalink)
New Member
 
Join Date: Mar 2014
Posts: 9
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by hubsabubs View Post
If you uninstalled the Smanager after doing all the steps, then you need to redownload it and install it again.

One thing I know I didn't do during this process was download the file with any sort of file association. I didn't add a .txt to the 11extsd2internalsd or anything when I saved it to my desktop. I just download the file as is and saved it as is. It's still sitting in my documents unassociated, with no file extension. In the description it just says "File". Maybe adding a file extension to it messes up the encoding on the file?

And again I repeat,

YOU CAN NOT DELETE OR UNINSTALL SMANAGER AFTER YOU DO THIS MOD!!!

It has to remain installed on the internal memory of the phone the entire time you use this mod, or else there will be nothing telling the script to remount the storage after boot!!!! Leaving you with your standard storage. As long as you use this mod you will have to keep the SManager app installed. Do not Link2SD it, do not Move to SD Card it. Leave it on the internal storage. It has to be able to be read as quickly as possible at boot, the system boots internal storage first, then scans the media on your sd card and mounts it after its all done. So you want the system finding SManager (It is set to launch on boot) as soon as it can so it can swap the mounts before the phone scans the external SD Card. It will pop up in your notification bar for a moment, then disappear and you will never see it again.

I went into my launcher and removed the SManager Icon from my app list, so in essence since I turn my screen off on boot and let it do its thing, I never see it! Unless looking at my app list in the settings menu.
Thanks for replay.
I did it again following every step but if a just turn off the phone, the smanager app take action and the external s d card of 32 gb become the internal memory but i f I reboot it application does not work it goes back to the normal internal memory which is 1.2 gb. What can I do to prevent this. Do you have any specific website that allows me to download the 11extesd2internalsd with out the ext extension.?
Mac09 is offline  
Reply With Quote
Reply

LG Optimus F6
Current Rating:
Rate this Phone:




Go Back   Android Forums > Android Phones > LG Optimus F6
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 10:42 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.