Hot answers tagged

13

Marshmallow internal storage can be better used with a mixed-format SD card as I also explain in my blog here: http://blog.sam.liddicott.com/2016/02/android-6-semi-adopted-storage.html First, you need adb working. Have SD card inserted and formatted as portable. Eject your SD card from the Storage & USB menu Use "adb shell" to list your adoptable ...


11

If I am allowed to suggest out of the choices that you had provided, I will suggest Link2SD. With Link2SD you can try moving/linking a non-critical application to the SD card and check how well it works. Once moved or linked, try to reboot the phone (no other way than rebooting to avoid disappointments) and see whether that moved/linked non-critical app ...


8

Yes you have full 16GB for apps+data together in a single file system. You won't have to do any moving to SD card any more. Google merged both partitions. It's just one big file system now with sections for the former parts. It's completely transparent, so no worries for you. Formerly: /data and /sdcard were separate partitions Galaxy Nexus / Nexus 7 and ...


7

An app must explicitly support App2SD, or you cannot move it to the card. There are several reasons why an app might not support it: using widgets (both mentioned apps seem to fall into this category. AK Notepad: "Pin notes to your home screen"; Any.DO: "You can even add our widget to your homescreen") running a service As the sdcard would be unaccessible ...


6

OK, after some research it seems that all the apps moved to external SD-card are in the virtual file system /mnt/asec, which is, in turn, an abstraction layer over the encrypted files stored in the hidden .android_secure folder, on the ext. SD-card.


6

Check the app manifest using an app like Manifest Viewer and search for android:installLocation If it is declared as internalOnly then the app cannot be moved to external SD (unless root methods / apps are used) If this attribute is not declared, your application will be installed on the internal storage only and it cannot be moved to the external storage. ...


4

What you describe is a mix of multiple problems. First, your apps becoming "unavailable" is most likely due to Apps2SD being used, and you installed those on your SD card. See: How to undo Apps2SD Second thing is your card itself (hardware, the "thing you put inside your device"). If it goes broke that often, this rises some hardware related questions. ...


4

After Android Tools Update command adb shell pm setInstallLocation 2 has been changed to adb shell pm set-Install-Location 2 Updated Tutorial can be founded here.


4

As Manishearth wrote, this might indicate trouble with the card (and very likely does). The boot you describe might have been "too abrupt", not cleanly unmounting the card and thus corrupting its file system; in which case the "good ol' chkdsk" should help (btw, Android ships with fsck for the very same task, which you could execute via a terminal app or adb ...


4

Native app2sd method - which placed encrypted .asec files in .android_secure folder on external SD card - was available only up to Android 5. For details see Why root cannot access “.android_secure” directory on external SD card? Starting with Marshmallow, the native method of moving apps to external SD card works only if SD card is formatted as Adoptable ...


3

There are some factors that may affect this: An app must explicitly declare that it's preferable/possible to be installed on SD card. Beginning with API Level 8, you can allow your application to be installed on the external storage (for example, the device's SD card). This is an optional feature you can declare for your application with the android:...


3

App specific settings are usually stored in the internal storage folder accessible only to that app. While apps do have the ability to write to external storage and lose access to that data when you mount it, I doubt that is the case here. When you install and move an app to the SD Card, you are not moving the entire app. Some core content of the app still ...


3

Don't confuse the App-Cache with the Dalvik Cache: App Cleaner refers to the App-Cache (e.g. cached files from the internet, aka "webcache", or from other components of the app), while the Dalvik Cache's .dex files are placed on app installation (they are an optimized version of the app code). So basically you compare apples with oranges. As for your ...


3

As Matthew already stated, there's no unique answer possible to your question -- all depends on your usage patterns. Generally spoken, I'd say moving app data should be preferred: If you move the Dalvik Cache, it would affect all your apps -- while moving the app data only affects apps which store some data (and by "some" I mean "data size exceeds their ...


3

According to our tag wiki, the Duos comes with Android 4.x -- which natively supports to move apps to SD: Settings→Apps→Manage Apps, sroll to the app you want to move, tapp the "Move to SDCard" button. If the button is grayed out, the app does not support being moved to SDCard. See Unable to move few Apps to SD Card for details on that. ...


3

There are a quite a few options. Open Terminal Emulator and check with the 'df' command, how much space is left on your partitions. Is /data or /system full? Goto system/apps/all > 'Sort by size to' find out which apps eat up the most space. Check if you have big size apps installed where you could change data location within the app to sdcard. Thinking of ...


3

Eureka! Here is how I've done it: SD card partition and format Unsure about which partitions I would have been able to relocate, I decided to recreate my sd card with the exact same layout of my Samsung Galaxy S III internal memory. USERDATA is the last partition and there is a good reason for it: my sd card size is greater then the internal memory and ...


3

OK, I think I found out the best setup. Format your SD card as internal memory. Go to Settings > Storage > Internal and open each app. Some apps have a "change" button. Press it to move the app into the SD card. Finally go to Settings > Storage > Internal and on the right corner press Migrate data. At this point, you did all you could.


3

Apps installed on the SD-Card are stored in the ".android_secure" directory. You cant see the APK files directly in that folder because the it is encrypted to prevent direct access to the APK file of paid apps.


2

I've been Googling this problem for a few days now. It appears to be based in some startup bug wherein the launcher app scans for existing applications before the SD card (internal or external) is mounted. First off, use FileManager or equivalent to look at your SD card's contents. If you see some grey icons with the app names or "com.[appname]" , then ...


2

Of course you can. Although it seems like there's no problem to migrate dalvik-cache to a normal SD card filesystem (the most common, vfat), it still is highly recommended that you format your SD card to ext4 (or the same as your /data) to ensure everything works fine. So let's go. A full backup of all your apps is recommended before proceeding though if ...


2

Depends on how the copy is performed. The SD card contains a couple of hidden files/directories (especially with App2SD being used, there's the .android_secure folder to be considered). Usually, when on a Linux workstation, a complete copy from sdcard#1 to sdcard#2 should do the job (cp -dpR <source> <target>). Same should apply to Mac OS. As I ...


2

Background Android has specific rules regarding the installation of applications and their physical location. It works like and hierarchical structure: If the app has a specified location by the developer, this takes priority. If it is not specified in the app, then the default install location is used. Android has 3 identifiers for app storage location: ...


2

Many questions in one, but all connected -- so I'll give it a try: You can device those apps in two categories, basically: those which work "similar" to the native app2sd, and those which don't. There are several rules an app must obey to be "allowed" for installation on SD card. Apps installed on SD card can e.g. not automatically start at boot time (as ...


2

There is no common desktop in Android. The desktop or the better term, the Home screen and its content changes based on the Launcher currently set as default. Desktop is also no directory in Android unlike traditional Linux distributions where you can simply browse them using command-line or a file manager. Anyhow, most of the Launchers including the stock ...


2

Disk Usage provides a way to find files and directories which consume a lot of space on phone and SD card


2

As you no longer have the original device, you've lost one option: Backing up those apps using Titanium Backup ★ root, sending those backups to the new device, and restoring them with the very same Titanium Backup. If you didn't back up your apps before turning the device in, it's like asking: "I just burned those papers. Can I still get a copy of them?" At ...


2

Starting with about ICS (Android 4.0), not all devices do support App2SD anymore (for reference, see also: How to move application to SD card in samsung galaxy s duos; the Galaxy S Duos and LG Optimus 4X are two of those devices -- looks like your Galaxy S3 Mini is another candidate, if the "Move to..." option is not there at all). This is, however, not the ...


2

You pretty much answered yourself: you move your apps to your SD card, then you unmount your SD card. No SD card -> the apps in it are not there anymore -> Android considers they have been deleted.


2

You need root access for it, so if you are not rooted, you can manually move the apps to the SD card (if that has been allowed by the app developer) in the Settings->Apps->(App to be moved to SD)->Move to SD Card. Or you can use a specialized linking app, such as App 2 SD, Link2SD or similar (if you have root).


Only top voted, non community-wiki answers of a minimum length are eligible