Now that we have to option to install apps to our sd card I have a couple questions.
1) Where are the apps stored? I tried finding them in root explorer on my sd card after i moved them but i could not.
2) When i get my 32gb card is there any special process i have to undergo now that I have moved apps to my sd card? As in should i move them all back to my phone before switching cards or if copy my entire card over to my new one will they be included?
I believe the apps are encrypted on the sd card.
install terminal, run terminal,
in terminal run "mount" (assuming this works even if not rooted)
see things like
/dev/block/dm-6 /mnt/asec/com.adobe.reader-1 ....
this implies the device mapper subsystem is in use. don't have any more info at this time.
within the /mnt/asec/*/ directory there is a file pkg.apk, though it doesn't seem like a traditional apk as not unzippable (or at least unzip -l pkg.apk seems to fail within terminal)
Related
My application has a backup/restore feature that writes a csv file to a directory named after the app, in the root of the sd card. I have a user trying to move from one tablet to another. The backup feature appears to properly be creating the backup file on her SD card. When she places the SD card in her new tablet, the backup file and the directory it's stored in do not appear to be on the SD card at all. Apparently she was successful in having other data from other apps move over.
I've walked her through everything I can think, including writing a test app to verify the issue. Without a doubt, the files exist on the old device, but don't exist when installed in the new device.
I'm unsure what the original device is, but the new device is a Dell Streak 7.
Anyone seen this before? I'm leaning towards corrupt SD card, but it seems it's my burden to prove as my app is the only app she's having issues with.
The root of /sdcard is not necesarrily the SDCARD you can remove and take out.
/sdcard is usually part of the build in memory which can be accessed and used by the user.
The SDCARD you can remove is usually found at /sdcard/external_sd on Android 2.2 devices and /sdcard/sd on Android 2.1 devices.
Yes the naming is a bit confusing .
Dark3n said:
The root of /sdcard is not necesarrily the SDCARD you can remove and take out.
/sdcard is usually part of the build in memory which can be accessed and used by the user.
The SDCARD you can remove is usually found at /sdcard/external_sd on Android 2.2 devices and /sdcard/sd on Android 2.1 devices.
Yes the naming is a bit confusing .
Click to expand...
Click to collapse
That would certainly explain some things, especially if a user is moving a SD card from one device to the next.
My app creates a folder under the path returned by the Environment.getExternalStorageDirectory() function, where it creates and reads a backup file.
My documentation asks users to connect their device to a computer, mount as USB, and copy the backup file into that directory. This user is simply moving the SD card between devices. I'm wondering if there is a better method than using the getExternalStorageDirectory that I can use, so that I can have a common location on all SD cards to facilitate users moving cards between devices.
wct097 said:
My documentation asks users to connect their device to a computer, mount as USB, and copy the backup file into that directory. This user is simply moving the SD card between devices. I'm wondering if there is a better method than using the getExternalStorageDirectory that I can use, so that I can have a common location on all SD cards to facilitate users moving cards between devices.
Click to expand...
Click to collapse
Well it depends on the device what happens if they mount as usb,
if they get the internal sdcard or the external sdcard or both.
On my galaxy i9000, both the internal(/sdcard/) and external (/sdcard/external_sd) are shown when pluging it into my computer and mounting it as usb.
Environment.getExternalStorageDirectory() will always return the path of the users storage enviroment which is in usually /sdcard . Thats fine so far.
The problem is there is no function to get the external storage (/sdcard/external_sd or /sdcard/sd).
The only option i know atm, would be to probe manually if such a directory exists. You can use Build.VERSION.SDK_INT to see which android the user has and check the right directory.
Build.VERSION.SDK_INT <= 7 would mean if he has plugged in an external sdcard it would be mounted under
Environment.getExternalStorageDirectory().getAbsolutePath() + "/sd/"
Build.VERSION.SDK_INT >=8 would be
Environment.getExternalStorageDirectory().getAbsolutePath() + "/external_sd/"
You could use that and maybe a "import backup" function to check for the file on an external sdcard?
I moved my micro SD card from one S4 (GT-I9505 with GE ROM) to another S4 (an actual GT-I9505G but rooted). Afterward, I'm having a weird permission issue.
I used Titanium to restore my applications from a backup on the card without problem. I set one of the restored applications to use the CD card for its storage which just reinstates its setting on the old phone. Now it complains that it can't create directories or files. The permissions on the directories on the SD card are rwxrwx--- and they are owned by root.sdcard_r I don't know why this app was able to write before but can;t write now.
How do apps/users get assigned to groups? I didn't see an \etc\groups file.
Follow the first post here
http://forum.xda-developers.com/showthread.php?t=2617921
I slowly look there no longer. I have rooted my S3 Neo initially quite normal and provided with CWM as it has been explained in various tutorials. Then I fixed the Android 4.4 write access issue with the "NextApp SDFix" from Android market. With the "ES File Explorer" and "Total Commander" I could normally rename files on the SD card, copy and move.
However, to me the practical effect is associated with all apps, which store data automatically on the SD card very mysterious, because instead of the SD card, they will continue stored internally namely in "/storage/Emulated/0". I tested this with "Dead Trigger 2", which is usually stores the game data in "Android/OBB". In Application Manager I have the opportunity the app to move itself to the correct SD card (.android_secure directory), but just the app itself and not the game data wich stay in the internal, emulated SD-Card.
For my previous smartphone, an Ace 2 NFC (I8160P) there was a fix for it to fit the "vold.fstab" to file: http://forum.xda-developers.com/showthread.php?p=28419837#post28419837
I could find only a tutorial changing the internal memory with the real SD-Card for the normal S3, which, however, is probably not compatible with the S3 Neo: http://android-hilfe.digidip.net/visit?url=http://forum.xda-developers.com/showthread.php?t=2036796 - Or should I try it so anyway?
At first the question: Why the Kitkat-Fix is at all useful, if it does not help in practice and the data continues to be stored internally? The only thing that has been directly accessed files to the correct SD card was the photo app but that's about it.
Update: I just see that it also provides an Android folder on the right SD card as well as in the emulated and actually reside in folders and the installed apps, including "Dead Trigger 2". However, the folder unlike emulated SD card are completely empty. What does that have to mean again?
I hope somebody can help me ans find a solution as I can't use my external SD-Card for most game datas or apps as planned or I will send back my S3 Neo tomorrow.
PLEASE!!! Can somebody help me???
do you use xposed? there are a couple of modules that allows you to use obb files from sdcard. Personally i use "xinternal". those ps apps never worked for me also.
Use Folder Mount
I use a xposed module called "HandleExternalStorage" and it works like a charm! Try it yourself!
Good luck
I got a otg-cable which has a USB port and a SD/micro SD card slot. It works fine (I can browse files when tapping on notification icon, card is empty/formatted), however, does anyone know where it's root folder is located? I can't find it with rootbrowser or root explorer.
Tried /mnt/ but there's nothing related, not even ext-sd, only the usual SDCard (internal storage), and i tried most other folders, just can't find it...
I want to backup my flashable (ROM) files from internal to my SD card without the need for a PC (which i currently don't have).
I'm using CM13.0 Snapshot on a G2-d802
anyone??
Just a thought: If the drive is indeed mounted and accessible, you could try the "df" command in Terminal Emulator to see a list of partitions and their mount points.
I have already found it. Apperantly i did not get through all folders in "/mnt". It's root-folder is located at "/mnt/media_rw/XXXX-XXXX/". I'm not sure how i messed that the first few times.
Thanks for your reply though, at least you took the time to actually make one
Ok, I have had many phones and this problem is a little bit weird for me.
I'm using Poweramp as my daily driver for music. I tried deleting some songs I stored on my SD and it said my files were write protected. I then used Root Browser just to see, that most of my music and photos I have on my SD card were not located in /sdcard but in /storage/57EF-B920, a directory I never created. When I put the SD card into my PC, I can see all my files normally and r/w without any issues.
I figured I could only alter files using the stock file browser and gallery app, but why? And why are my SD card stored media files showing up in /storage/57EF-B920 instead of their actual path? Is that a security feature?
My phone is 100% stock and not rooted.
Thanks for your help!
This is how it has always been on MM. The days of /sdcard, or /storage/extSDcard for your external SD card folder are long gone with LP/KK/JB I'm afraid.
The directory for external sd is unique to your SD card. Put in another SD card, and a new directory name will get generated for it, and it alone.
The ability for an app to write to SD card is down to the app's developer. It will need to have the updated methods that MM uses. Usually, if an app can write correctly, it will prompt you to browse to the root of your external sd card the first time it attempts to access it. Even then, some apps may need extra tweaking. Titanium Backup for example requires the storage type for the external SD card to be changed to Document Storage/Provider in its settings. I used to use Nandroid Manager on my rooted S4 on CM MM, and this could never update external SD card....I had to use Root Explorer to delete/rename my TWRP backups.
You can also double check specific apps for permission through Application Manager.
Go into the specific app in application manager, click on Permissions, and make sure Storage is turned on.
Even when turned on, some apps might still fail, as I've explained.
hawkerpaul said:
This is how it has always been on MM. The days of /sdcard, or /storage/extSDcard for your external SD card folder are long gone with LP/KK/JB I'm afraid.
The directory for external sd is unique to your SD card. Put in another SD card, and a new directory name will get generated for it, and it alone.
The ability for an app to write to SD card is down to the app's developer. It will need to have the updated methods that MM uses. Usually, if an app can write correctly, it will prompt you to browse to the root of your external sd card the first time it attempts to access it. Even then, some apps may need extra tweaking. Titanium Backup for example requires the storage type for the external SD card to be changed to Document Storage/Provider in its settings. I used to use Nandroid Manager on my rooted S4 on CM MM, and this could never update external SD card....I had to use Root Explorer to delete/rename my TWRP backups.
You can also double check specific apps for permission through Application Manager.
Go into the specific app in application manager, click on Permissions, and make sure Storage is turned on.
Even when turned on, some apps might still fail, as I've explained.
Click to expand...
Click to collapse
Sorry for the late reply, but thanks for the explanation! So it's because how MM works vs how Lollipop did and Poweramp not being uptodate with that? I'll try out the permission thing and even if I fail, it's good to know why it won't work. Thank for your help!