On the LG Optimus F6, How do you set up the SD card as the download destination/location?Support


  1. JonsExtremePorta

    JonsExtremePorta New Member

    I just got the LG Optimus F6. After downloading some apps I wanted to download FIFA which falls under the Games category. I wanted to know if there was any way I could set up downloads from google play to be downloaded into the SD card instead of the phone's internal memory.
    Please ELI5, because I tried but can'd find a way to do it
    Any help- thanks in advance
    Have a nice day

    Advertisement
    :
  2. MrGlowy

    MrGlowy Well-Known Member

    diack likes this.
  3. JonsExtremePorta

    JonsExtremePorta New Member

    In case i don't like the experience after rooting, can i revert back to factory settings?
    How complicated is the process for a novice android user? (i pretty much have the hang as far as how to use and tweak the phone, like closing apps or moving them to the SD card)

    And again, thanks for your time and patience, its greatly appreciated.
  4. MrGlowy

    MrGlowy Well-Known Member

  5. lucasmun09

    lucasmun09 Well-Known Member

    Well, does this swap the internal and the external? or is it just some kind of another app2sd application..... I want to know how to make my sd card primary storage.
  6. JVene

    JVene Well-Known Member


    We know, it's the primary goal.

    Not just for the F6, but for a wide range of devices.

    The goal, both yours and mine, is to mount the directory /data onto another device (SD Card), or at least all of the important directories under /data.

    /data is where EVERYTHING you download or install goes on a stock phone. Even what is called internal SD is simply a mount into /data/media on this phone.

    On the F6 that partition is about 1.2 GBytes. The internal storage is a device of 4 GBytes, divided into perhaps 30 partitions, some very small, many are likely 'virtual disks' or some such invention.

    The one we're all focused on is that 1.2Gbyte partition which mounts as the directory /data. We want to remap that directory onto the external SD card, but there are significant obstacles.

    For one, the stock SD cards are formatted in FAT32 (vfat, as Linux calls it). This filesystem doesn't handle all of the user and permission details well enough for Android to accept it as a replacement for /data or one of the important children like /data/apps or /data/data. For another, remapping a phone like the F6 can't be done prior to zygote starting - that's the dalvik virtual machine which everyone knows as Android.

    Before zygote starts, the OS is really just linux. If it were not locked, we could just edit the startup script in init.rc (or it's cousins) and thus mount whatever we like before zygote launches. The F6 bootloader is locked, so that's not an option. Our changes evaporate when the phone reboots.

    What we do have are pseudo init scripts, managed from something like universal init.d or smanager, which can be used to remap some things, but they can only run AFTER zygote is launched (they're not installed as part of Linux, they're installed as Android/Java applications).

    If we remapped /data at that point, we'd drive the phone nuts. By the time these scripts run, zygote is running, Android has already opened and used important configuration files in various directories under /data (typically /data/data), and yanking them out from under Android at that point causes problems.

    As you've observed the various approaches available for linking apk and application data directories can work, but it's not a real solution. Even swapping internal/external SD doesn't really do the whole thing. The storage page in Android tells you the space of the SD card is available, but there are still many important directories working in that precious 1.2 GByte partition, and it still fills up.

    I'm working on a hack. My son wants two games which are 600Mbyte and 900Mbyte downloads (some GTA 3 or some such thing). I can force fit the install, but like everyone else I want a real solution.

    The hack I'm working on would be able to perform the substitution of the important directories under /data. Remapping /data itself might be a bit much, I'm still experimenting, but I may know during the weekend of Jan 18/19th. If my solution works I'll open a thread for discussion on the subject here, but it won't be ready for anyone less than expert in the Android OS. I'm a developer, more focused on application development, but I know Linux/Unix and have sufficient familiarity with the Android implementation of Linux to fashion a solution for my son's F6, and thus present a theory for others here and other forums who might take the ball and fashion a solution for everyone else.

    No solution is without some compromise unless the bootloader lock can be defeated. My own solution begins with repartitioning the SD card, either entirely with one non FAT32 partition (ext2 for my experiments), or with a FAT32 of perhaps 4 GBytes and the rest as ext2 or ext4 (those are Linux filesystems). This means only other Linux or Unix machines would be able to read those SD cards.

    The hack I'm fashioning for my son's F6 doesn't compromise on the storage solution - that appears to be complete, such that not only does Android report 26Gbytes available (4 reserved for FAT), but so does the Linux df command.

    The compromise I've selected involves a slower, odd boot solution. The phone appears to boot twice upon power up or restart. It does NOT lead to boot loop lock, just two boot sessions. Once completed, storage is wide open.

    So far early efforts are very promising. I'm about 90% certain at this point it is possible to make a REAL remount of the important directories in /data ( /data/app and /data/data, for example), such that we can genuinely have the space of the SD card as the primary storage, not some phantom which appears in the storage page of Android's settings applet but isn't real. No further management required either. Once done, installs of applications, data, dex files, temporaries - everything - goes to the SD card. No need to "move to phone" or link, application by application, or - as is my case - force fit a 600 Mbyte install into a 1.2Gbyte partition that only has 350Mbytes available after uninstalling half the library.

    I hate it when it does that!
  7. lucasmun09

    lucasmun09 Well-Known Member

    From what I understand, what you want to do is achieved already... The data files go to the SD card but the apk installments still stay inside that puny 1.2gb storage. (more or less 400mb acutally). So what I figured that worked the best was to instal the app2sd swap mod from the link above, which swapped the sd card and internal memory. Voalla, now you have the internal storage as your sd card now. I downloaded a link2sd, which will "app2sd" the apk installments and not the data, which we don't have to worry about it. So by doing these things, I was to achieve downloading many apps I wanted and still had 250mb left over after moving the app installments to the sd card. currently 53 apps and games and from them, 7 games had <1gb data (which were stored into the sdcard by the app) and their massive apk's paritally moved to the sdcard that are <40mb.


  8. JVene

    JVene Well-Known Member

    I've detailed more about this in this other thread http://androidforums.com/lg-optimus-f6/819792-proposal-theory-external-sd-storage-solution-f6.html#post6399822.

    No, it's not actually real.

    I've researched every solution made available, and short of a custom ROM, there are no complete solutions exampled. Combinations of various tools do help considerably, but the truth about the storage of a device is only visible at the command line of linux, as in the output of the df command:

    Code (Text):
    1.  
    2. Filesystem                 Size         Used         Free    Blksize
    3. /dev                    402.14M       64.00K      402.08M       4096
    4. /system                   1.19G        1.06G      132.54M       4096
    5. /mnt/asec               402.14M        0.00K      402.14M       4096
    6. /mnt/obb                402.14M        0.00K      402.14M       4096
    7. /data                    29.04G        5.63G       23.41G      32768
    8. /sns                      7.91M        4.11M        3.80M       4096
    9. /mpt                     31.54M       12.50M       19.03M       4096
    10. /persist-lg               7.91M        4.14M        3.77M       4096
    11. /cache                  788.39M       14.38M      774.01M       4096
    12. /persist                  7.91M        4.10M        3.81M       4096
    13. /firmware                63.95M       41.80M       22.16M      16384
    14. /storage/external_SD     29.04G        5.63G       23.41G      32768
    15.  
    In all of the solutions available, none produce an output to match this one.

    In particular, note the /data partition in this report. It exactly matches the external storage device.

    df can also report by directory, with this form:

    df /data/app

    Which basically causes df to figure out what real device the path is served from and report that.

    /data on the stock device is a 1.27 Gbyte partition, so df /data would show the device with 1.27G as it's defined space, and some considerable amount less available after consumption.

    Likewise, df /data/media on stock devices would show the same storage space, because media is commonly just a directory under data.

    However, if a symbolic link were used to instead of a directory, /data/media might point to another device. If so, the result of df /data/media wouldn't match the result of df /data

    The important directories involved relative to the storage problem are:

    /data/app
    /data/data
    /data/dalvik-cache
    /data/media

    The app2external_sd swaps out /data/media - which is otherwise known via a mount as /storage/sdcard0.

    It doesn't swap out /data/app, /data/davik-cache or /data/data. Factually, these can't be swapped out while the Android VM is running because some applications freak out badly. Google apps are particularly insulted when their entry in /data/data is re-mapped.

    Move to phone, link2sd and other similar applications help to move material out of /data/app and /data/data, one application at a time. Some people can achieve satisfactory results with these tools, and they're the best combination of options available as apps.

    I arranged the same thing experimentally using the shell (via ADB). Linking, mounting and relocating manually, I was frusted by the fact the manufacturers leave this problem for us to deal with, and no real solution.

    Only a full substitution of /data is a complete solution - or, the effective equivalent of substituting all 4 of the important directories, at the minimum.

    Using the command line, either via a free terminal app or the adb shell, one can more deeply examine the results of:

    df /data/app
    df /data/dalvik-cache
    df /data/data
    df /data/media

    to understand what's really happening. The Android settings app which shows storage is easily confused by storage remapping, and reports space for apps which isn't actually there. Only df (or similar interrogation of Linux) can inform us of the real storage situation.

    So, no...these other applications have partial solutions, but I want a complete solution whereby primary storage of what we all recognize as the entirety of Android is on the SD card, so there's no app by app fiddling with it.

    An important realization comes from understanding downloads. If you download something from most sources, that's routed to a location in /data/media (or, the same via /storage/sdcard0).

    However, if you download from Google play store, it doesn't go there, it goes to /data/data/com.android.providers.downloads/cache/tmp

    Or something to that effect.

    Which means downloads from non-google sources might be routed to the external SD card while Google Play store downloads are not.

    Thus, all other downloads of large files would be fine, but a large download (or two or three together) from Google Play could overflow the space also occupied (still) by /data/app and /data/dalvik-cache.
  9. alexcool25565

    alexcool25565 Well-Known Member

    Edit: Wrong thread...
  10. philmiami

    philmiami Well-Known Member

    I ran this setup before on wife's F6.
    Showed 29GB Internal 1.7GB SD then went all whack on me
    re did it again with what was already on there, the .apk on the sd card
    now it just shows 29GB as Internal AND SD Card
    same card so internal memory redirects is locked out
    so it's cool with me.....
    I got no problems with it doing this
  11. ddrain5515

    ddrain5515 New Member

    Yo, i don't understand why everyone says you need to root in order to do something on an android. Like its an iPhone or something, HAA. But if you want to change the Primary Storage from Internal to External, just follow these steps.

    1. From any Home screen, tap the Apps icon.
    2. Tap Camera.
    3. Tap Settings.
    4. Swipe up on the menu and then tap Storage.
    5. Tap one of the following options:
      • SD card
      • Internal memory
    As Simple as cake. Also you can do this from your browser.


    1. From any Home screen, tap the Apps icon.
    2. Tap Browser.
    3. Tap the Menu key and then tap Settings.
    4. Tap Advanced.
    5. Tap Storage.
    6. Tap one of the following options:
      • SD card
      • Internal memory
    TADAAAAA!!!:smokingsomb::smokingsomb::smokingsomb::smokingsomb:
  12. sunnyd

    sunnyd Member

    That does not solve the major problem all of us are having at the moment. The browser and camera have nothing to do with the big issue. What they are saying is they want the hecka small internal storage switched to the external SD card as the primary. Just switching the browser and the camera only work for those 2 apps. Nothing else. So when installing apps from the play store it does not go to external SD card. What they are talking about is being able to install apps to external and have it act as the primary.

Loading...

Share This Page