Skip to main content
Android Enthusiasts

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

16
  • 2
    @t0mm13b ah, that's not ideal. I knew that change was there alright, but I was under the (obviously wrong) impression that Samsung would patch this to work on their own device with official ROM as they still 'support' EXT-SD cards. On a rooted device SOME have had success with folder mount, but others have bricked their device. Try XDA and see what's there, it is being worked on but I've not see a definitive answer. Commented Feb 26, 2014 at 11:57
  • 1
    In short, the real workaround, is to change one line in the manifest within the kitkat source and recompile the rom and flash it. Google are clear on moving away from SDCards, flash memory capacity are increasing, and cheap to embed on device board, and furthermore, using cloud services for storage. Its a major inconvenience, perhaps someone with Xposed framework might circumvent it.... pita.. Commented Feb 26, 2014 at 12:36
  • 1
    @DanHulme complaining to author of app is not the solution. Its a drastic change by Google... Commented Feb 26, 2014 at 12:43
  • 1
    The permission's existed since API 16, and there's been a big warning in the official training for as long as I can remember. Commented Feb 26, 2014 at 12:58
  • 1
    It's still a dumbass move. Why should we be forced to store all our downloads on internal memory? The whole point (more or less) of having an SD slot is so we can dump a bunch of media onto a card and swap one collection for another. I suppose Google wants us all to use "cloud memory" which is worthless when off the network. Commented Feb 26, 2014 at 15:39