Hello!
I own the Samsung Galaxy Tab S2 (with stock Android 5.02) and programs such as uTorrent cannot save on the external SD card. Do I have to give extra write permissions to the apps? The apps can read only I think.
The tab is not rooted so far.
Did you try Stickmount ??
Look for sd card fix on play. You need to be rooted.
SD Fix KitKat writable USB worked for me.
Sent from my SM-T810 using XDA-Developers mobile app
Code:
fetito666 said:
Hello!
I own the Samsung Galaxy Tab S2 (with stock Android 5.02) and programs such as uTorrent cannot save on the external SD card. Do I have to give extra write permissions to the apps? The apps can read only I think.
The tab is not rooted so far.
Click to expand...
Click to collapse
Apps like Root Explorer and others that support Lollipops write access will prompt you to select the drive it will have permission to. If the app doesn't then, its outdated and wont access it. It has to do with the write permission that Google removed.
jetbruceli said:
Code:
Apps like Root Explorer and others that support Lollipops write access will prompt you to select the drive it will have permission to. If the app doesn't then, its outdated and wont access it. It has to do with the write permission that Google removed.
Click to expand...
Click to collapse
It's dysfunctional in lollipop. Only really works in MM.
WRITE permissions can be obtained globally as said by applying the sd fix.
ashyx said:
It's dysfunctional in lollipop. Only really works in MM.
WRITE permissions can be obtained globally as said by applying the sd fix.
Click to expand...
Click to collapse
As the op states, he is not rooted. So only apps that can ask for permission to use the SD card will.
jetbruceli said:
As the op states, he is not rooted. So only apps that can ask for permission to use the SD card will.
Click to expand...
Click to collapse
He stated 'Yet' and it becomes obvious that root is required when downloading the Sd card fix and I already stated it requires root in my previous post.
If he wants global freedom to write to the sd card then that's the road to take.
ashyx said:
He stated 'Yet' and it becomes obvious that root is required when downloading the Sd card fix and I already stated it requires root in my previous post.
If he wants global freedom to write to the sd card then that's the road to take.
Click to expand...
Click to collapse
Well that is a no brainer. Having root allows for all things to work but sacrifice security. I personally do not root anymore. My main apps, Root Explorer-MX Player-PLay Movies work with the MicroSD after a the permission was given.
Hopefully when MM comes we can have the option to adopt the extra storage and move on from this night mare
jetbruceli said:
Hopefully when MM comes we can have the option to adopt the extra storage and move on from this night mare
Click to expand...
Click to collapse
Adopted storage brings it's own issues. I for one don't use it as its implementation affects access to the sd card through custom recovery and other platforms.
However write access permissions are now much improved and any app can obtain these permissions if the user allows.
As regards security when rooting, it doesn't have to be a risk. It's up to the user to be aware of what rooting is and how to use it.
Root can still be Selinux aware. It's up to the user to ensure what they do with their device is safe.
I for one feel my device is more secure with root as *I* have control over my device not what the manufacturer decides.
I will take measures to protect myself if required.
Even some of the apps I use to protect myself need root.
The benefit of root to me personally far outweighs any perceived security issue.
^^^ agree 100%
Sent from my SM-T810 using XDA-Developers mobile app
Related
[Edit] disregard, unrooted users. Apparently, my XOOM just wasn't cooperating with the older version of the app. Sorry for the false alarm.
Just a heads up for those of you who use root explorer. The app has been updated to allow for files to be associated with a specific app from within Root Explorer. What the change log failed to mention was that writing to the SD card in /mnt/external1 (aka, your removable SD card) is now functioning in the app.
Huzzah!
Ive always been able to write to my external sd card with root explorer... or am I missing something?
I wasn't able to until this morning's update. I see that they've also formatted the app for tablets (sort of) with the settings button in the upper right corner.
Ihaven't had a problem writing to my sdcard with Root Explore prior to today either.
I've always been able to write to my external SD card with Root Explorer (as well as every other file manager I've installed. However, I applaud the update as welcome news for those who could not.
Yes, let everyone know...just another good reason to root your Xoom.
This makes me curious. I've been rooted since the beginning, yet it just now works for me. I'm wondering if this fixes r/w access for non rooted devices.
Sent from my Xoom using XDA App
I have been able to write to my external SD since the first day of rooting. Root Explorer is the tool I have used since the beginning.
Sistema1927 said:
I have been able to write to my external SD since the first day of rooting. Root Explorer is the tool I have used since the beginning.
Click to expand...
Click to collapse
same here, but Root Development is always a good thing.
But it wasnt true that in 3.2 sdcard was just "reading" or something like that?
Sorry for my english.
Ifiuse said:
But it wasnt true that in 3.2 sdcard was just "reading" or something like that?
Sorry for my english.
Click to expand...
Click to collapse
People were complaining about that, but if rooted, you could change r/o to r/w in Root Explorer.
arrtoodeetoo said:
This makes me curious. I've been rooted since the beginning, yet it just now works for me. I'm wondering if this fixes r/w access for non rooted devices.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
Nope. Just tried.
Sent from my Xoom using Tapatalk
hi
should be getting mine today
how is everybody coping with the low storage issue?
i have been reading up on directory bind and also rickywyatt method
i dont plan on unlocking the bootloader but i do plan on rooting
What low storage issue are you talking about?
While most of them are installed on the SD, I have a lot of installed applications (about a hundred) and I still have more than 3Gb available (internal storage).
An SDcard can be used for your pictures/videos/games, up 32Gb (at least).
If you want to root your phone and don't want to unlock your bootloader, then don't upgrade it.
However, depending on the installed firmware, it may be impossible to root without unlocking the bootloader.
Motorola has fixed the root exploit in the last update.
ciberbeb said:
What low storage issue are you talking about?
While most of them are installed on the SD, I have a lot of installed applications (about a hundred) and I still have more than 3Gb available (internal storage).
An SDcard can be used for your pictures/videos/games, up 32Gb (at least).
If you want to root your phone and don't want to unlock your bootloader, then don't upgrade it.
However, depending on the installed firmware, it may be impossible to root without unlocking the bootloader.
Motorola has fixed the root exploit in the last update.
Click to expand...
Click to collapse
oh, that was something i wanna ask, so if i download Need for Speed MW the 2 gb will install on the SD?
I can't see that it goes to the sd card everything I have downloaded has gone onto the internal memory
App2sd doesn't work so I think the only two methods we can use are directory bind or the internal swap memory trick
Sent from my XT890 using xda app-developers app
emu123 said:
I can't see that it goes to the sd card everything I have downloaded has gone onto the internal memory
App2sd doesn't work so I think the only two methods we can use are directory bind or the internal swap memory trick
Sent from my XT890 using xda app-developers app
Click to expand...
Click to collapse
Did u tried using this app? i dont have a good connection so i cant try it by myself with games https://play.google.com/store/apps/...t=W251bGwsMSwxLDEsImNvbS5zbGYuTGlzdGdsQXBwIl0.
Deshabilitado said:
oh, that was something i wanna ask, so if i download Need for Speed MW the 2 gb will install on the SD?
Click to expand...
Click to collapse
It depends on the application. Some apps put thier "big" files on the sdcard, some won't.
As emu123 said, you can use an app like Apps2sd to move them from the internal to the external storage.
Even if I install a lot of games, I never ran out of storage. That was the case with my old HTC Desire HD.
Big games can use up to 400Mb, I still have more than 3Gb, which means I can install, at least, 7 big games (but some of them will put files on the SDcard if present). It won't ever happen.
EDIT: I think Apps2sd doesn't work with Android 4.x. Not sure, but I think that the system manages where to install apps when internal storage is full.
I already suggested the ability to move apps to the SD card on the motorola forums, Razr I discussions:
I even got an answer!
I'm a new user so I can't post links search it
Agustinb14 said:
I already suggested the ability to move apps to the SD card on the motorola forums, Razr I discussions:
I even got an answer!
I'm a new user so I can't post links search it
Click to expand...
Click to collapse
I'm not sure the "gosh that's a good idea, we'll pass it on" really counts as an answer - almost as if no-one had ever thought of it before!
Does anyone know how to disable vibro on screen unlocking?
Hi, I set up a thread (in my signature) specifically for for those of us new to Motorola - I just got my first Moto phone 2 days ago too. You may find the thread helpful - I will update it with any info. that people need.
How do you mean low storage? Internally? 8GB (practically 5GB) is low to you? Compared with what? Most phones in the upper tier of mid-range have 8GB and many top-range phones start with 8GB...it seems perfectly normal to me. Either way, do you have an SD card? I've a 32GB for my music and it's now full...some phones load the SDs so slowly...but NOT thins phone, all of my music is found in seconds. :fingers-crossed:
So, I just installed the 4.4.2 OTA and I immediately noticed one big problem: I wasn't able to modify content on my SD card. I wasn't able to delete folders, or create folders, or create files. Reading content was no problem, and the camera app was able to save pictures to the card, but going through a file manager wouldn't work.
I started to do some research and I found this post from the developer of my chosen file manager, FX:
https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn
Then, while getting ready to post this, I found another related thread:
http://forum.xda-developers.com/showthread.php?t=2641936
I thought this was a big enough deal to warrant a new thread here. Bottom line is you may want to hold off on this update, or at least go in with your eyes open because for a lot of people, like me, this is a BIG problem. It's damned near a dealbreaker for using my S4 as a matter of fact. Note that it does seem you're able to use the My Files app, but that's almost useless to me: FX has SMB support and I'm constantly pulling files off my server. I even have FolderSync set up to run every night, but I don't expect that'll work either (I'm about to try now).
Whether Samsung spits out a fix quickly, or whether I can root and fix this, it's a pretty significant problem. Be aware folks!
Then I will update after a stable de-knoxed ROM is available.
Sent from my SPH-L720 using Tapatalk
Thanks.for this. I think I will still update as I plan on staying unrooted and will use "my files".
Sent from my SPH-L720 using Tapatalk
anees02 said:
Then I will update after a stable de-knoxed ROM is available.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I'm all for avoiding Knox, but in this case it appears to not be Knox-related after all... looks like it was a permission change that Google mandated for devices with external storage and Samsung followed the specification to the letter. I think Tod Liebeck explained it better than I can though. I can only hope Samsung gets it together and quickly releases a patch... I've read in another thread that they may have done this before and quickly put out a fix... if so, shame on them for making the same mistake twice, but so long as a fix is forthcoming, so be it. I'm not so sure there will be one though, that's my concern.
It's early to call that is the bug since nobody mentioned this issue.
And all are busy how to update.
I will wait 48 hours until all things be more clear.
Could you try another SD card and tell us if the issue is happening to the new sd card?
Sent from my SPH-L720 using Tapatalk
anees02 said:
It's early to call that is the bug since nobody mentioned this issue.
And all are busy how to update.
I will wait 48 hours until all things be more clear.
Could you try another SD card and tell us if the issue is happening to the new sd card?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thing is, it was something that was apparently talked about before the update on other devices with 4.4.2. It's not a bug per se, Samsung did what Google told them to do, and Google told them to do it, I'd bet, to push people towards cloud storage since they don't want external storage used anymore anyway. None of that matters though because the fact is it's hurting some users (though I'd agree that not all will be impacted- it all depends on how you use your device).
A different card wouldn't matter, it's not related to that at all. It's a permission change that Google mandated with 4.4 (or 4.3, I've seen some conflicting info) that only impacts devices with external storage, and Samsung chose to follow Google's specification exactly in this case, to the detriment of (some) users.
FYI, *IF* you're rooted, here's a solution that fixes this. Worked for me and easy to do:
http://forum.xda-developers.com/showthread.php?t=2524277
Just remember to keep a copy so you can quickly undo it to take an OTA since I assume it'll stop an OTA.
Soooo lemme get this straight... Lets say I update to KitKat (NAE)and root it, and I have apps on my computer (like Flappy Bird APK for instance), I now cannot copy the Flappy Bird APK onto my SD Card then place it (using a root explorer) in system/app and use it?! If so this is a huge deal-breaker... Or am I misunderstanding this and there's more to it?
thankfully you can still create on the SD card from a computer when plugged. but i can confirm you cannot create anything on the SD card from ES file explorer, you can still create on the internal storage just fine tho
Joe0113 said:
Soooo lemme get this straight... Lets say I update to KitKat (NAE)and root it, and I have apps on my computer (like Flappy Bird APK for instance), I now cannot copy the Flappy Bird APK onto my SD Card then place it (using a root explorer) in system/app and use it?! If so this is a huge deal-breaker... Or am I misunderstanding this and there's more to it?
Click to expand...
Click to collapse
You can still copy from your computer if you use a USB cable... if you instead have a shared drive on your PC and connect to it via SMB from a file explorer, you won't be able to copy a file to the SD card.
In addition, using a third-party file explorer you won't be able to create, rename, delete or edit files or directories on the SD card, nor will you be able to copy files from internal storage to your SD card. This is strictly a limitation placed on non-system apps (meaning any you yourself install).
If you're rooted though, a quick edit to a single system file will deal with this, but nobody should *have* to do that.
fzammetti said:
You can still copy from your computer if you use a USB cable... if you instead have a shared drive on your PC and connect to it via SMB from a file explorer, you won't be able to copy a file to the SD card.
In addition, using a third-party file explorer you won't be able to create, rename, delete or edit files or directories on the SD card, nor will you be able to copy files from internal storage to your SD card. This is strictly a limitation placed on non-system apps (meaning any you yourself install).
If you're rooted though, a quick edit to a single system file will deal with this, but nobody should *have* to do that.
Click to expand...
Click to collapse
That's ridiculous... what the hell Android/Samsung?!
Wow! Not trying to rub it in or anything but thank goodness I switched to the Nexus 5. What a nightmare. I hope Samsung fixes it soon for you guys
Sent from my Nexus 5 using Tapatalk
Thanks for this, lets go here for any further discussion...http://forum.xda-developers.com/showthread.php?t=2646762
When Did We Get the Ability Again to Move Apps to the SD Card?
I noticed this in the Note 4 and was surprised and excited. I probably was not mindful about the KitKat operating system before stumbling onto this.
I thought this feature was only possible when rooting and using ROM's like CyanogenMod. I thought the ability to move apps to the SD was discontinued after Gingerbread because of Security & Privacy concerns.
arjun90 said:
When Did We Get the Ability Again to Move Apps to the SD Card?
I noticed this in the Note 4 and was surprised and excited. I probably was not mindful about the KitKat operating system before stumbling onto this.
I thought this feature was only possible when rooting and using ROM's like CyanogenMod. I thought the ability to move apps to the SD was discontinued after Gingerbread because of Security & Privacy concerns.
Click to expand...
Click to collapse
When I bought my Note 4 I could not use third party apps like Root Explorer to move files to SD. The only thing that worked was the "My Files" app that came bundled with the phone. That was all fixed once I rooted and flashed a custom rom like Dynamic Kat or FireKat. I think there is a build.prop fix and/or an xposed module fix (e.g. Wanam) if you don't want to flash a custom rom, but yes that still requires root as far as I know (but I could be wrong ).
My Note 4 was never rooted, and I have the ability to move apps to an SD card using Clean Master.
sefrcoko said:
When I bought my Note 4 I could not use third party apps like Root Explorer to move files to SD. The only thing that worked was the "My Files" app that came bundled with the phone. That was all fixed once I rooted and flashed a custom rom like Dynamic Kat or FireKat. I think there is a build.prop fix and/or an xposed module fix (e.g. Wanam) if you don't want to flash a custom rom, but yes that still requires root as far as I know (but I could be wrong ).
Click to expand...
Click to collapse
What possible reason (as in good reason), would google have for making it impossible for users to write to their own sd cards?
I just got this S5 (AT&T) and it updated when I turned it on before I realized that the SD card is mounted ro, AND that you can't root 4.4.4.
I've searched for workarounds and barring rolling back to 4.4.2 I haven't found any.
So, why did google do this?
And, is there really no way around it?
What good is an SD card that I can't even create, modify, or delete files from? Did they not realize that this is why we have external storage?
doesn't towelroot root 4.4.4? I'm a bit hungover this morning, but pretty sure you're rootable as long as you don't do an over the air (OTA) update to 5.0 from AT&T.
I'm on 5.0 rooted room and using at&t .
nicetucu said:
doesn't towelroot root 4.4.4? I'm a bit hungover this morning, but pretty sure you're rootable as long as you don't do an over the air (OTA) update to 5.0 from AT&T.
I'm on 5.0 rooted room and using at&t .
Click to expand...
Click to collapse
towelroot told me that it doesn't support this phone.
If 5.x is available for my phone, won't that cure the sdcard ro mess? I was reading on Android Police that 5 was supposed to fix things.
4.4.4 is rootable, 5.0 owa is not. Don't do anything before you read up on the process to root 4.4.4 first and then how to update to 5.0 while keeping root. As for the sdcard, it works fine, read and write, on all versions. You have a different issue.
From all I've read after searching, 4.4.4 is not rootable, and below 5.something the sd card is not writeable by any app that either google or the carrier did not install or include with the firmware. Are those points incorrect?
Thanks
Tref said:
From all I've read after searching, 4.4.4 is not rootable, and below 5.something the sd card is not writeable by any app that either google or the carrier did not install or include with the firmware. Are those points incorrect?
Thanks
Click to expand...
Click to collapse
Downgrade to nce. Read the entire OP
http://forum.xda-developers.com/showthread.php?t=3076803
Tref said:
From all I've read after searching, 4.4.4 is not rootable, and below 5.something the sd card is not writeable by any app that either google or the carrier did not install or include with the firmware. Are those points incorrect?
Thanks
Click to expand...
Click to collapse
Search Play Store for NextApp SDFix to make your SD card writable. Worked great for me.
From your pc, did your sd card are format in fat32? Did you see in esexplorer /storage/extSdCard?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
cmerlyn said:
Search Play Store for NextApp SDFix to make your SD card writable. Worked great for me.
Click to expand...
Click to collapse
Does it require root?
jo0147 said:
From your pc, did your sd card are format in fat32? Did you see in esexplorer /storage/extSdCard?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Click to expand...
Click to collapse
I've had this card in several phones, it's not new. This is a known issue with kitkat
All: I don't want to take a chance on a set of instructions that includes multiple mentions of others bricking their devices while trying to follow them. All I was hoping to do was first and foremost rant a bit about google, and second to learn whether or not google let common sense rule and restored full write access to "our" external cards in a later update. They shouldn't have messed with external r/w access in the first place. If they really want to make our phones more secure when installing apps they should do a better job of policing their appstore and the code they host on it, imo.
Tref said:
Does it require root?
Yes, root is required for the app.
Click to expand...
Click to collapse
Tref said:
Does it require root?
I've had this card in several phones, it's not new. This is a known issue with kitkat
All: I don't want to take a chance on a set of instructions that includes multiple mentions of others bricking their devices while trying to follow them. All I was hoping to do was first and foremost rant a bit about google, and second to learn whether or not google let common sense rule and restored full write access to "our" external cards in a later update. They shouldn't have messed with external r/w access in the first place. If they really want to make our phones more secure when installing apps they should do a better job of policing their appstore and the code they host on it, imo.
Click to expand...
Click to collapse
1) @muniz_ri's instructions will never result in a brick if followed correctly
2) there is no way to get sd card access on kitkat without root.
3) lollipop does support 3rd party apps writing to sd cards. However, the apps need to be updated to use the new API. (Most apps worth installing are updated by now)
Sent from my SAMSUNG-SM-G900A using Tapatalk
Tanks for the info about 5.0
I thing tail use the same policy about external storage. I not able to copie file from my linux to my usb, except for an other usb with tail partition.
Might it be that by disabling our ability to write to the external SD card, and limiting the abitlity of apps to do the same, that google is pushing people toward google drive? Could/would they be that avaricious?
It shouldn't come as a surprise as most all companies are driving toward paid storage.
But it is particularly galling when we are denied the use of storage that is vital to what we do on these things, and that we paid for ourselves.
Tref said:
Might it be that by disabling our ability to write to the external SD card, and limiting the abitlity of apps to do the same, that google is pushing people toward google drive? Could/would they be that avaricious?
It shouldn't come as a surprise as most all companies are driving toward paid storage.
But it is particularly galling when we are denied the use of storage that is vital to what we do on these things, and that we paid for ourselves.
Click to expand...
Click to collapse
Nope.. Android M is going have full sd card support including encryption.
Sent from my SAMSUNG-SM-G900A using Tapatalk