Related
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)
I've recently updated my firmware to Kitkat 4.4.2 and I am unable to save to my extsdcard using Mybackup Pro 4.0.5. Every time I've tried to backup to the extsdcard, I get "The path that you entered is not valid, your change was not saved".
okizen said:
I've recently updated my firmware to Kitkat 4.4.2 and I am unable to save to my extsdcard using Mybackup Pro 4.0.5. Every time I've tried to backup to the extsdcard, I get "The path that you entered is not valid, your change was not saved".
Click to expand...
Click to collapse
I have the same problem. I can't my backup to extsdcard using my GO Backup and Titanium Backup. I used folder mount but still no success.
Afaik kitkat does not allow 3rd party apps to write on the external sdcard
Gesendet von meinem GT-I9505 mit Tapatalk
benni2903 said:
Afaik kitkat does not allow 3rd party apps to write on the external sdcard
Gesendet von meinem GT-I9505 mit Tapatalk
Click to expand...
Click to collapse
I actually installed FolderMount from the store and it noted the issue and corrected on reboot, now TB and other apps work fine with SD card.
nrps1 said:
I actually installed FolderMount from the store and it noted the issue and corrected on reboot, now TB and other apps work fine with SD card.
Click to expand...
Click to collapse
In the last few days Samsung has been pushing out Android 4.4.2 to flagship devices like the Galaxy
Note III and Galaxy S4. Unfortunately, Google implemented an SD card write restriction in the latest
Android version which can be quite annoying for users with an SD card in their phone.
The new “feature” basically restricts apps from writing to external SD cards. This can be quite
annoying, because many users want to store apps on a secondary SD card instead of the main storage
unit.
Luckily, how to fixing this problem can be easily done if you have root access. Here’s how you can do it
(Please be aware that you’re performing these changes on your own risk!):
Make sure that you have root access
1. Perform a NANDROID backup to be completely safe
2. Use a root-enabled file manager and navigate to /system/etc/permissions
3. Edit platform.xml and find “WRITE_EXTERNAL_STORAGE“
4. Add an additional group definition for this permission: <group gid=”media_rw” />
5. Save the changes and restart your device
6. You are now able to write on your external SD card again
I hope that I was able to help you.
The newest version of My Backup Pro 4.0.9 supports now 4.4.2 but I still can't setup the backup directory for external SD card? Tryed
/sdcard/sd
/mnt/sdcard-ext
/sdcard/external_sd
/sdcard/
mnt/extSdCard
and still nothing, My Backup Pro still doing backup into internal memory. What is the point of having app on ur phone. I'm not rooted and don't want to do it.
Luk45z said:
The newest version of My Backup Pro 4.0.9 supports now 4.4.2 but I still can't setup the backup directory for external SD card? Tryed
/sdcard/sd
/mnt/sdcard-ext
/sdcard/external_sd
/sdcard/
mnt/extSdCard
and still nothing, My Backup Pro still doing backup into internal memory. What is the point of having app on ur phone. I'm not rooted and don't want to do it.
Click to expand...
Click to collapse
+1.
Even though I'm rooted, I agree 100% with you.
Try to move the app to your sd card. There should then be an app folder on the sd card and the app should be able to write there.
Sent from my GT-I9505
Thank for this tip, but didn't work for me... Stupid Google :/ still doing backup to internal memory.
DarkCase said:
In the last few days Samsung has been pushing out Android 4.4.2 to flagship devices like the Galaxy
Note III and Galaxy S4. Unfortunately, Google implemented an SD card write restriction in the latest
Android version which can be quite annoying for users with an SD card in their phone.
The new “feature” basically restricts apps from writing to external SD cards. This can be quite
annoying, because many users want to store apps on a secondary SD card instead of the main storage
unit.
Luckily, how to fixing this problem can be easily done if you have root access. Here’s how you can do it
(Please be aware that you’re performing these changes on your own risk!):
Make sure that you have root access
1. Perform a NANDROID backup to be completely safe
2. Use a root-enabled file manager and navigate to /system/etc/permissions
3. Edit platform.xml and find “WRITE_EXTERNAL_STORAGE“
4. Add an additional group definition for this permission: <group gid=”media_rw” />
5. Save the changes and restart your device
6. You are now able to write on your external SD card again
I hope that I was able to help you.
Click to expand...
Click to collapse
Hi DarkCase
I've got Root Explorer 3.16 but I can't seem to edit the platform.xml file.
okizen said:
Hi DarkCase
I've got Root Explorer 3.16 but I can't seem to edit the platform.xml file.
Click to expand...
Click to collapse
Did you press this first?
Thanks....
DarkCase said:
In the last few days Samsung has been pushing out Android 4.4.2 to flagship devices like the Galaxy
Note III and Galaxy S4. Unfortunately, Google implemented an SD card write restriction in the latest
Android version which can be quite annoying for users with an SD card in their phone.
The new “feature” basically restricts apps from writing to external SD cards. This can be quite
annoying, because many users want to store apps on a secondary SD card instead of the main storage
unit.
Luckily, how to fixing this problem can be easily done if you have root access. Here’s how you can do it
(Please be aware that you’re performing these changes on your own risk!):
Make sure that you have root access
1. Perform a NANDROID backup to be completely safe
2. Use a root-enabled file manager and navigate to /system/etc/permissions
3. Edit platform.xml and find “WRITE_EXTERNAL_STORAGE“
4. Add an additional group definition for this permission: <group gid=”media_rw” />
5. Save the changes and restart your device
6. You are now able to write on your external SD card again
I hope that I was able to help you.
Click to expand...
Click to collapse
Thanks , it worked for me
I'm having the same problem too. I've e-mailed the developers of MyBackup Pro to see if they've got any ideas.
It says MyBackup Pro 4.0.9 fixes KitKat issues, it doesn't fix this one!
I will if I have to but I don't want to or see why I should have to, effectively break (root) my Galaxy S4 just to backup to SD card when it worked fine with Jellybean 4.3. I don't need Root access otherwise
--------------------------------------------------------------------------------------------------------------------------------------------------
None of this is mentioned in Google's KitKat Release Notes or on-screen when the Samsung Update Notification appeared. So far KitKat has broken for me:
1. SMS Backup+ prior to KitKat could restore SMS messages back to the phone, it can still back them up but not restore
2. LG G Pad's QPair It still works but used to be blue when connected, white when not connected. Now that everything is white mad, it's grey when not connected and white when connected. No where near as clear.
3. MyBackup Pro can no longer backup to SD card
Being able to backup to SD card is obviously crucial!
I've seen zero benefits from going from Jellybean 4.3 to Kitkat.
DarkCase said:
In the last few days Samsung has been pushing out Android 4.4.2 to flagship devices like the Galaxy
Note III and Galaxy S4. Unfortunately, Google implemented an SD card write restriction in the latest
Android version which can be quite annoying for users with an SD card in their phone.
The new “feature” basically restricts apps from writing to external SD cards. This can be quite
annoying, because many users want to store apps on a secondary SD card instead of the main storage
unit.
Luckily, how to fixing this problem can be easily done if you have root access. Here’s how you can do it
(Please be aware that you’re performing these changes on your own risk!):
Make sure that you have root access
1. Perform a NANDROID backup to be completely safe
2. Use a root-enabled file manager and navigate to /system/etc/permissions
3. Edit platform.xml and find “WRITE_EXTERNAL_STORAGE“
4. Add an additional group definition for this permission: <group gid=”media_rw” />
5. Save the changes and restart your device
6. You are now able to write on your external SD card again
I hope that I was able to help you.
Click to expand...
Click to collapse
++++++++1111111
okizen said:
Hi DarkCase
I've got Root Explorer 3.16 but I can't seem to edit the platform.xml file.
Click to expand...
Click to collapse
I have already written this (media_rw) in xml file, but still go backup is unable to write to external sd card. With esfexplorer I can make folder or files on external sd card, so permission is rw?
any idea
What is google thinking. Why would I save to internal memory and not be able to have a backup everywhere I go in multiple locations?
As for the fix you shouldnt have to root your device just to have it write to a card. this makes no sense
DarkCase said:
In the last few days Samsung has been pushing out Android 4.4.2 to flagship devices like the Galaxy
Note III and Galaxy S4. Unfortunately, Google implemented an SD card write restriction in the latest
Android version which can be quite annoying for users with an SD card in their phone.
The new “feature” basically restricts apps from writing to external SD cards. This can be quite
annoying, because many users want to store apps on a secondary SD card instead of the main storage
unit.
Luckily, how to fixing this problem can be easily done if you have root access. Here’s how you can do it
(Please be aware that you’re performing these changes on your own risk!):
Make sure that you have root access
1. Perform a NANDROID backup to be completely safe
2. Use a root-enabled file manager and navigate to /system/etc/permissions
3. Edit platform.xml and find “WRITE_EXTERNAL_STORAGE“
4. Add an additional group definition for this permission: <group gid=”media_rw” />
5. Save the changes and restart your device
6. You are now able to write on your external SD card again
I hope that I was able to help you.
Click to expand...
Click to collapse
Hi,
I did what you have suggested except the first step (i.e. NANDROID backup). Upon restart I got all messages like (Google stoped fuctioning, Bluetooth sharing stopped functioning, etc)....
I put the original copy of the file back in place (so essentially, I put the original platform.xml back.....still the problem would not go....
My Note 2 (N7100) is useless now.... can any fellow help?
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
Hi, my problem is with the phone of my girlfriend. Now have external 64GB SD, because internal storage is full. I used Android SDK and all the instructions for set default storage for install APP the new SD Card, you know, with the command adb shell pm set-install-location 2. And no error, i try get-install-location and report 2. But googe play only try to install in the internal storage.
I think the problem is with the system of the emulated storaged or something, but i tried many APP, many solutions, and i cant fix this, i search in google and others locations, have 30 tabs in firefox open with information, but i cant found the solution for this
Samsung Galaxy NOTE 4 (910F)
Android 5.1.1 (Of samsung of course)
Rooted
The vold.stab is:
dev_mount sdcard /storage/sdcard1 auto /devices/msm_sdcc.2/mmc_host
PLEASE, help me! thanks
I tried dismounting and mounting the SD, touching the vold.stab file, but do not get any results.
Can anybody help me?
Go back to stock, upgrade to 6.0.1. Then see if this helps-
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
The article is for S7, but see if you can have that working in the N4 - just have a backup of everything (int SD, ext SD, full backup in recovery).
ph03n!x said:
Go back to stock, upgrade to 6.0.1. Then see if this helps-
The article is for S7, but see if you can have that working in the N4 - just have a backup of everything (int SD, ext SD, full backup in recovery).
Click to expand...
Click to collapse
Thanks, for the moment 6.0.1 is not released in Orange (confirmation date has passed and still not have it, I assume that is in the offing). When have 6.0.1 i try you solution, thanks.
ph03n!x said:
Go back to stock, upgrade to 6.0.1. Then see if this helps-
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
The article is for S7, but see if you can have that working in the N4 - just have a backup of everything (int SD, ext SD, full backup in recovery).
Click to expand...
Click to collapse
I tried this in my phone. While the command itself worked after a bit of a tweak, the storage situation was pathetic - the phone showed the External SD as a part of the overall storage, but did not save files to it. Instead, it started saving files to the actual internal SD Card, resulting in space running out pretty soon. The External SD card was just there, and there was no way to migrate the files from the internal storage to the adoptable storage.
I just got a new Note 4 (this is the 3rd one I'm using since the first release in 2014) and I also want to adopt external memory card as my internal space bcos the 16Gg duos version is just too small and app to SD comes with a lot of hassles. After a lot of search for different solutions (which I tried out by the way but didn't work) I came across this thread for another phone entirely but it resolved my issue: https://forum.xda-developers.com/galaxy-tab-s/general/patch-adoptable-storage-enabler-t3460478.
The only downside is that I can't pop out my card (128Gg Samsung) and plug into my PC but I can still explore it directly from the phone itself.
I've been using the phone for 3 days and it runs smoothly, I hope that solves your problem too.
So there are two parts to the adoptable storage. The first part is the partitioned SD card and mounting the partition. Simple to be done via root essentials or the command line.
The other part is the actual menu entry on an app in application manager for moving it to the second partition. IIRC samsung does not have this support built in. So you need to flash something to replace that manager bit. In my experience with an on5 (like less than 1GB free on internal storage out of the box), adoptable wasn't really worth it, too much stuff still on internal storage. As not every app will allow you to move it to that second partition. It requires both system support and app support.
What I did there was to use the app apps2sd. Same idea, second partition on SD card. But it doesn't show up in settings -> storage. You manage where the apps go via that app. I use the link feature which places a symbolic link in the internal storage and moves all the actual files to that sd card partition.
Will Rickards said:
So there are two parts to the adoptable storage. The first part is the partitioned SD card and mounting the partition. Simple to be done via root essentials or the command line.
The other part is the actual menu entry on an app in application manager for moving it to the second partition. IIRC samsung does not have this support built in. So you need to flash something to replace that manager bit. In my experience with an on5 (like less than 1GB free on internal storage out of the box), adoptable wasn't really worth it, too much stuff still on internal storage. As not every app will allow you to move it to that second partition. It requires both system support and app support.
What I did there was to use the app apps2sd. Same idea, second partition on SD card. But it doesn't show up in settings -> storage. You manage where the apps go via that app. I use the link feature which places a symbolic link in the internal storage and moves all the actual files to that sd card partition.
Click to expand...
Click to collapse
I've been using apps2sd fot about a year and it comes with it headache too, sometimes the apps wouldn't find the external data (usually games with a lot of data) and it'll start downloading it again into the internal memory, so I usually find myself having to force stop the app, delink and relink the data on the memory card to fix the bind. I also didn't bother to partition my SD card since I can explore it on the PC with my phone connected. What this solution ( https://forum.xda-developers.com/galaxy-tab-s/general/patch-adoptable-storage-enabler-t3460478 ) does is to flash back the option to use the SD card as internal memory that Samsung removed from the phones and it works seamlessly on all Samsung phones with rooted stock OS.
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!