Related
Hi all:
this time I see Google insist that any new smartphone should be ships with the latest Android version.
What Google is looking for in KitKat ?
For me I will not update to KitKat !
Because of the following:
"The WRITE_EXTERNAL_STORAGE permission must only grant write access to the primary external storage on a device. Apps must not be allowed to write to secondary external storage devices, except in their package-specific directories as allowed by synthesized permissions."
That means your microSD card is secondary storage and apps will not be allowed to use it, Google has screwed up the KitKat API as they think there is a big security problem with external SD cards !!!!!
Oh... your SD Card is completely useless, applications will no longer be able to create, modify or remove files and folders on your external SD card. As a for-instance, you can no longer use a file manager to copy files from your computer to the SD card over a network.
in short Google want you to use their cloud services instead of your SD card, I feel like we are going back in time, and Samsung is involved in this game.
I agree, this is definitely a bad change. Luckily though, I've never stored apps on my external SD so this is not a problem for me.
You can simply download apps like App2SD and move them to the sd. Obviously you have to have root access...
Has any one else lost the ability to write to their socketed sdcard since the 4.4.2?
thesavo said:
Has any one else lost the ability to write to their socketed sdcard since the 4.4.2?
Click to expand...
Click to collapse
Thats a "feature" of kitkat. Can't be changed unless you have root.
Seriously?
Yes, see here for fix(if your rooted):
https://play.google.com/store/apps/details?id=nextapp.sdfix
thesavo said:
Seriously?
Click to expand...
Click to collapse
It's a security issue. Before KK, the SD card was wide open to any other process to be able to request read/write to any directory and file, regardless of whether or not they created that file or directory.
Now, under KK, a program can create a file or folder in a "protected" area and only that program has the ability to modify the contents in that folder. It cannot modify other folders or files that it didn't create.
Time to move the podcasts. So my older shows that I worked hard to keep to keep the ext sdcard1 as a target, will have to be copied to sdcard0.too bad.thanks @iBolski
No wonder BeyondPod kept 'accidently' putting shows on SDcard0 for the last year. Even though I "pinned" it to SDcard1 in the advanced settings.
Even with the application that patches the /etc/permissions/platform.xml, I have found certain apps still do not work correctly. Dolphin Browser, for example, cannot switch to /storage/sdcard1. It keeps saying it can't find it and I need to ensure I don't have "USB Mode" enabled, which I don't even have as an option when connected to a PC.
I also have init.d installed on my machine and I had startup scripts that mounted various directories from my external to the internal SD card to "fool" the device so that apps that wouldn't save to the external but the internal would save across a mount. Well, that no longer works. For example, Amazon MP3 will not save downloaded music anywhere except to the internal sd card. I had my startup scripts mount an amazonmp3 directory on my external SD card to the internal amazonmp3 directory on the internal memory card. When I proceeded to download music, it didn't show up in the external directory. However, I noticed that the internal sd card's memory did decrease. I then unmounted the directory and saw that the Amazon MP3 app was ignoring the mount under KitKat and directory saved the files into the /storage/sdcard0/amazonmp3 directory, even though it was mounted to the directory on the external SD card. It did work under JB and ICS, but apparently, with KitKat, some apps will still write directly to the native directory on the internal SD card, ignoring the fact that I've mounted a different directory to it.
The stock Moto camera will write to the external SD card if you go and change the setting for it. However, the Google Camera does not give you any option to store your pictures anywhere except on the internal SD card memory. :crying:
Remember, apps can write to the external card, if you don't apply the "patch", but only to what is considered a protected are (the /storage/sdcard1/Android directory structure) and then, they can only write to a directory that the app created. They can read other directories, but they cannot modify them.
iBolski said:
It's a security issue. Before KK, the SD card was wide open to any other process to be able to request read/write to any directory and file, regardless of whether or not they created that file or directory.
Now, under KK, a program can create a file or folder in a "protected" area and only that program has the ability to modify the contents in that folder. It cannot modify other folders or files that it didn't create.
Click to expand...
Click to collapse
That's official explanation (bull****) as you described above with non stock camera. Basically KK made external storage almost useless. I found this nice description quite long time ago.
https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn
Zeljko1234 said:
That's official explanation (bull****) as you described above with non stock camera. Basically KK made external storage almost useless. I found this nice description quite long time ago.
https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn
Click to expand...
Click to collapse
I know at this point, Root Explorer still works with it, after setting the correct permissions into the /etc/permissions/platform.xml file. That works for a lot of apps. The only one that I know that is currently broken is Dolphin browser. I cannot navigate to the /storage/sdcard1/ area anymore. It keeps telling me it can't find the file or directrory and that I should make sure the SD card is ready and USB Mass Storage (haven't seen this option since my Droid X2) is not on.
So definitely, Dolphin Browser is doing something differently that even the patch isn't working for it.
Problem is that without root user cannot edit platform.xml and even after that some applications refuse to write to sd card. Another example is OfficeSuite 7 Pro which I bought and now cannot edit file if it's needed. Workaround is to save to internal then overwrite to sd card.
Basically stock Android becoming more and more limited, harder and harder to get root... That's so bad that I wouldn't update to official kk in the case that my phone has locked bootloader.
Read this article http://www.xda-developers.com/andro...use-even-more-issues-for-root-app-developers/
I've been all day trying to get a Micro SD installed on my T-Mobile Samsung Galaxy Go5 so I can move apps onto it. After bricking an old SD 32 GB card and buying a new 64 GB card I started searching for help here. I found information that said the card has to be formatted as 'Internal Storage.' This post described the process (the process that worked toward the bottom).
I'd been trying to figure out how to install the Android SDK on my Windows PC without downloading Android Studio in order to get the adb shell mentioned in that post set up. I found this post and this post on the stackoverflow forum, but just wasn't able to figure it all out. But it looks like I need the Java SE Development Kit 10 installed.
I was able to set up USB debugging on the phone though.
Can anyone help me out here and describe just what must be done to achieve all this?
Thanks for any feedback on this
Not really able to help but i read many people advise against using SD card as internal storage. Most regular SD cards r not fast enough or durable enough to last more than a few months. Just sharing
sautom said:
Not really able to help but i read many people advise against using SD card as internal storage. Most regular SD cards r not fast enough or durable enough to last more than a few months. Just sharing
Click to expand...
Click to collapse
I think you're right about that. I've installed programs on USB sticks that can be quite sluggish. Then again I've had a number of system maintenance utilities on flash drives for years that aren't and still perform fine. Then they don't get used for hours on a day to day basis.
I moved a number of apps on my old Galaxy Ace to a micro sd card though, most used was the Poweramp music player that's always performed well.
And I've got the card now, so I may as well try to get it set as internal and just see how it performs over time. Thanks for you feedback sautom.
TakuSkan said:
I've been all day trying to get a Micro SD installed on my T-Mobile Samsung Galaxy Go5 so I can move apps onto it. After bricking an old SD 32 GB card and buying a new 64 GB card I started searching for help here. I found information that said the card has to be formatted as 'Internal Storage.' This post described the process (the process that worked toward the bottom).
I'd been trying to figure out how to install the Android SDK on my Windows PC without downloading Android Studio in order to get the adb shell mentioned in that post set up. I found this post and this post on the stackoverflow forum, but just wasn't able to figure it all out. But it looks like I need the Java SE Development Kit 10 installed.
I was able to set up USB debugging on the phone though.
Can anyone help me out here and describe just what must be done to achieve all this?
Thanks for any feedback on this
Click to expand...
Click to collapse
If you have lollipop or newer Android version, you should be able to use the "Adoptable storage" option.
Also, if performance is important to you, then you won't like this option, using sdcard as internal is slower, the only "gain" in using this is the system has more storage to use. There is no gain on performance, you actually lose there.
I don't recommend using sdcard as internal storage though. There are way too many issues that come along with using this kind of modification. A lot of times, the sdcard gets corrupted, then the real issues start when you try to fix it, usually, the device won't function properly, the data on the sdcard gets lost/corrupted, just to name a couple of the many possible issues. It isn't exactly "easy" to fix this when it happens, depending on what goes wrong, sometimes it can't be fixed.
Sent from my LGL84VL using Tapatalk
Droidriven said:
If you have lollipop or newer Android version, you should be able to use the "Adoptable storage" option.
Click to expand...
Click to collapse
I've read quite a bit on this and "adoptable storage" now, and agree that trying to use an expansion SD card as internal memory to run apps is a bad idea Droidriven. I still have a little over 1 GB left on the tiny built in 8GB internal SD Card memory, and have most of what I want installed.
I'm pretty green when it comes to Android, coming from many years with Windows and a tad with Linux. I see that with v6.0.1 Marshmallow, the OS began setting up a system directory tree on the 64 GB SD card when I installed it, and I'm able to set data folders there for apps like the camera. That'll be good for storing large camera videos and other media files.
One thing I haven't figured out yet though is whether or not there's any setting on a non-rooted phone like this Go5 that will allow me to transfer files directly into the 'Android' folder on the internal 8 GB card from Windows. I'm able to connect the two via USB or FTP and write files from Windows to folders on the 8 GB card like 'Download'. But I can't copy any files from Windows over to any of the writable apps folders in the 'Android' folder. I've resorted to copying them 1st to 'Download' from Windows, and then using a file manager in Android to copy files over to the 'Android' folder. I'm not used to such rigid file/folder permissions.
Does this sound like an issue that will require rooting? It'd make life a lot easier if that weren't the case. I'd think if I can write files to that 'Android' folder from within Android, I ought to be able to do the same remotely somehow.
Thoughts?
TakuSkan said:
I've read quite a bit on this and "adoptable storage" now, and agree that trying to use an expansion SD card as internal memory to run apps is a bad idea Droidriven. I still have a little over 1 GB left on the tiny built in 8GB internal SD Card memory, and have most of what I want installed.
I'm pretty green when it comes to Android, coming from many years with Windows and a tad with Linux. I see that with v6.0.1 Marshmallow, the OS began setting up a system directory tree on the 64 GB SD card when I installed it, and I'm able to set data folders there for apps like the camera. That'll be good for storing large camera videos and other media files.
One thing I haven't figured out yet though is whether or not there's any setting on a non-rooted phone like this Go5 that will allow me to transfer files directly into the 'Android' folder on the internal 8 GB card from Windows. I'm able to connect the two via USB or FTP and write files from Windows to folders on the 8 GB card like 'Download'. But I can't copy any files from Windows over to any of the writable apps folders in the 'Android' folder. I've resorted to copying them 1st to 'Download' from Windows, and then using a file manager in Android to copy files over to the 'Android' folder. I'm not used to such rigid file/folder permissions.
Does this sound like an issue that will require rooting? It'd make life a lot easier if that weren't the case. I'd think if I can write files to that 'Android' folder from within Android, I ought to be able to do the same remotely somehow.
Thoughts?
Click to expand...
Click to collapse
I always just use the ES File Explorer app, it lets me move whatever I want to/from Android folder.
Sent from my LGL84VL using Tapatalk
Droidriven said:
I always just use the ES File Explorer app, it lets me move whatever I want to/from Android folder.
Click to expand...
Click to collapse
Yes, from within Android. I'm using the free open source Amaze file manager that I can do that with. But I can't connect the Android phone to a Windows PC and be able to copy files from Windows to the Android folder on the phone. Just to Download, and maybe DCIM and the root of the internal 8 GB SD memory.
Can ES File Explorer access shared folders on a Windows PC? Amaze sets up an FTP server, but I don't see where it can access files on a Windows system.
EDIT: Seems it can: How to Access Shared Windows Folders on Android, iPad, and iPhone
TakuSkan said:
Yes, from within Android. I'm using the free open source Amaze file manager that I can do that with. But I can't connect the Android phone to a Windows PC and be able to copy files from Windows to the Android folder on the phone. Just to Download, and maybe DICM and the root of the internal 8 GB SD memory.
Click to expand...
Click to collapse
You should be able to do this with just Windows. Are you sure that you have your USB options set correctly? It should be set to MTP(file transfer).
When you connect the device to PC, you should see a USB icon in the status bar on the device, pull down notification panel, it should have a notification that takes you to your USB options.
Or, when you connect the device, you might get a pop-up menu on your device that has settings for USB options.
It varies from one device to another and one android version to another.
Do you have USB debugging enabled in developer options?
Also, if you do some reading about everything that the ES File Explorer app can do, you'll see that it can be used to transfer files to/from PC via more than a few options, including wirelessly/remotely.
It has several things it can do and different ways to connect when connecting/connected to other devices, including smart TV and others. It can also be used as a server or even be used to create a hotspot.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You should be able to do this with just Windows. Are you sure that you have your USB options set correctly? It should be set to MTP(file transfer).
Click to expand...
Click to collapse
Yes Droidriven. I have set USB debugging and USB is set as MTP. I just discovered that Amaze does connect to Windows like ES File Explorer by running it's cloud search function. So far Amaze has done everything I've been told to use ESFE for. But Amaze is very light. I just used Amaze to copy a file over from a shared Windows folder to that Android folder on the phone.
I have Total Commander on the Windows system, but when I use it to navigate to an apps subfolder of Android on the phone, it can't see any of the files or folders that I can access with Amaze from within the phone.
So I'm half way there Just need to figure out how to get Windows to see and write files on this Go5 now.
TakuSkan said:
Yes Droidriven. I have set USB debugging and USB is set as MTP. I just discovered that Amaze does connect to Windows like ES File Explorer by running it's cloud search function. So far Amaze has done everything I've been told to use ESFE for. But Amaze is very light. I just used Amaze to copy a file over from a shared Windows folder to that Android folder on the phone.
I have Total Commander on the Windows system, but when I use it to navigate to an apps subfolder of Android on the phone, it can't see any of the files or folders that I can access with Amaze from within the phone.
So I'm half way there Just need to figure out how to get Windows to see and write files on this Go5 now.
Click to expand...
Click to collapse
I don't know where you're having issues, all I have ever done is just connect my device to Windows via USB then use the native Windows Explorer file manager to transfer to/from internal/external to PC/device. I've never had to do anything special or use any extra software on the device or PC to achieve this, plus, I've done this on different Windows systems.
Sent from my LGL84VL using Tapatalk
Droidriven said:
I don't know where you're having issues, all I have ever done is just connect my device to Windows via USB then use the native Windows Explorer file manager to transfer to/from internal/external to PC/device. I've never had to do anything special or use any extra software on the device or PC to achieve this, plus, I've done this on different Windows systems.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I think it may be because this was a T-Mobile phone and that they may have disabled some functions like "adoptable storage" which doesn't seem to be present, as well as maybe setting permissions to prevent access to certain system folders.
I've even found that I have to change the extensions of some files like ini files to txt before I can drag and drop from Windows Explorer via a USB connection to just a few folders on Android.
It is a bit nutz. Rooting would probably solve the problem. But I'm not ready to go there yet. There may be an answer for getting the Windows > Android file viewing and writing yet. But at least for the moment I can copy both ways with the Amaze File Manager.
Okay, I'm back to considering formatting this 64 GB SD Card as internal storage. I would really like to record video to it, and with the internal memory limited to 1 GB that's left of the total of 8 GB from the factory, that's just not going to make it.
I got the Android SDK and 'adb shell' working on my PC, and started researching how to run commands that would target just the SD Card, and not the existing memory. The command 'sm list-disks' returns: disk:179,32
Is that the phone's internal memory, the SD Card's memory, or perhaps all memory on the phone? When I run the command 'sm list-volumes' I get:
private mounted null
public:179,33 mounted 38C4-18FE
emulated mounted null
I know 38C4-18FE is listed on the phone as being my added SD Card. So I'm hesitant to run the command I see people using to format their SD Cards: 'sm partition disk:179,33' I've wiped the wrong drives by mistake before using Windows diskpart when I didn't specify the right drive/volume. Can anyone clear that up for me?
I'm still hesitant to do this as it seems the phone will automatically begin to use the entire contents of the SD Card as space to run its OS. Might there be commands that would specifically alot the space on the card for writing data, and not for apps that would write and rewrite data there? Something I could create a folder in and point video recording apps to?
Android 6.0.1 Marshmallow
TakuSkan said:
Okay, I'm back to considering formatting this 64 GB SD Card as internal storage. I would really like to record video to it, and with the internal memory limited to 1 GB that's left of the total of 8 GB from the factory, that's just not going to make it.
I got the Android SDK and 'adb shell' working on my PC, and started researching how to run commands that would target just the SD Card, and not the existing memory. The command 'sm list-disks' returns: disk:179,32
Is that the phone's internal memory, the SD Card's memory, or perhaps all memory on the phone? When I run the command 'sm list-volumes' I get:
private mounted null
public:179,33 mounted 38C4-18FE
emulated mounted null
I know 38C4-18FE is listed on the phone as being my added SD Card. So I'm hesitant to run the command I see people using to format their SD Cards: 'sm partition disk:179,33' I've wiped the wrong drives by mistake before using Windows diskpart when I didn't specify the right drive/volume. Can anyone clear that up for me?
I'm still hesitant to do this as it seems the phone will automatically begin to use the entire contents of the SD Card as space to run its OS. Might there be commands that would specifically alot the space on the card for writing data, and not for apps that would write and rewrite data there? Something I could create a folder in and point video recording apps to?
Android 6.0.1 Marshmallow
Click to expand...
Click to collapse
It's possible to partition the external sdcard so that it has separate partitions with one of those partitions devoted to internal storage and the other for whatever you want. I'm not versed in specific tools and methods to do it, there are many.
Sent from my LGL84VL using Tapatalk
Droidriven said:
It's possible to partition the external sdcard so that it has separate partitions with one of those partitions devoted to internal storage and the other for whatever you want. I'm not versed in specific tools and methods to do it, there are many.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I'm happy with dedicating the entire memory in my sd card to adoptable storage space. I just want to know if adb is returning the right designation of my added sd card memory, and not the default internal memory.
Does the command 'sm list-disks' run from an adb shell that returns this for me: disk:179,32 mean that 179,32 is the designation that represents the sd memory card I added? Or if I try to use adb to partition 179,32 as adoptive memory, will I be formatting the default internal memory? What would be an adb command to return the designation of the small 8 GB default internal memory of my phone?
TakuSkan said:
I'm happy with dedicating the entire memory in my sd card to adoptable storage space. I just want to know if adb is returning the right designation of my added sd card memory, and not the default internal memory.
Does the command 'sm list-disks' run from an adb shell that returns this for me: disk:179,32 mean that 179,32 is the designation that represents the sd memory card I added? Or if I try to use adb to partition 179,32 as adoptive memory, will I be formatting the default internal memory? What would be an adb command to return the designation of the small 8 GB default internal memory of my phone?
Click to expand...
Click to collapse
Have you tried running the command without the external sdcard inserted? That will tell you the designation of your internal because internal is all it will see, then insert the external sdcard, then you can run the command to see what the designation for the external is. Once you setup Adoptable Storage, there will be no difference in designation, the OS will see your internal and your external as one complete storage space, it sees external as if it were internal and identifies/labels it as such for all intents and purposes.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you tried running the xommand without the external sdcard inserted? That will tell you the designation of your internal because internal is all it will see, then insert the external sdcard, then you can run the command to see what the designation for the external is. Once you setup Adoptable Storage, there will be no difference in designation, the OS will see your internal and your external as one complete storage space, it sees external as if it were internal and identifies/labels it as such for all intents and purposes.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
That is exactly the information I've been after Droidriven. That sounds like the perfect way to differentiate default internal memory from an SD addon. I read where after formatting/partitioning the sd card, installed apps will stay on the internal memory unless you opt for an ill advised process of moving them to the new space where they probably won't perform well.
How will the OS see the added sd memory after formatted as adoptable storage? My concern is that since this a cheap flash memory sd card, I don't want the OS to start writing and rewriting to this sluggish, slow flash memory card and just wear the thing down. Is there any way to specify the added memory as being data storage only? I only want the extra memory for writing video from the phone to a space large enough to hold multiple files
TakuSkan said:
I read where after formatting/partitioning the sd cardm installed apps will stay on the internal memory unless you opt for an ill advised process of moving them to the new space where they probably won't perform well.
Click to expand...
Click to collapse
That's right.
TakuSkan said:
How will the OS see the added sd memory after formatted as adoptable storage?
Click to expand...
Click to collapse
As far as I know, it will see all one space with no way to "store here instead of there" that I know of. The OS uses the entire space as it sees fit.
TakuSkan said:
My concern is that since this a cheap flash memory sd card, I don't want the OS to start writing and rewriting to this sluggish, slow flash memory card and just wear the thing down.
Click to expand...
Click to collapse
That is exactly what it will do, this is the common cause of sdcard formatted as internal getting burned out, they aren't meant to do all that writing/rewriting/overwriting/deleting constantly. Frequent activity kills it in the end, hence, my original post warning against the downsides to using external as internal. Once external is incorporated into internal, if the external gets corrupted, the OS won't boot or operate, potentially making a terrible mess to get the device recovered but not the external sdcard, it's toast at that point, along with everything that was stored on it, in some cases, the device can't be recovered either, due to lack of software support or publicly available downloadable firmware.
TakuSkan said:
Is there any way to specify the added memory as being data storage only? I only want the extra memory for writing video from the phone to a space large enough to hold multiple files
Click to expand...
Click to collapse
It might be possible somehow, but it probably requires root and some other apps that use root to make the needed modifications to direct data where you want it stored. I'm not sure it's possible though because, as I said previously, the OS sees internal and external as one complete partition, with no way to "see" a difference between them because they no longer have differing disk designations.
In my honest opinion(based on my exposure and experience with various devices that have used this as an option and the issues they have had along the way), using external as internal is too risky and shouldn't be used. Oddly, Adoptable Storage works better on devices that have better hardware and plenty of internal storage than it does on lower end devices with limited hardware and limited storage, the lower, limited devices are typically the ones that end up having issues. I know, this seems counter-intuitive since the better devices don't need the extra internal storage and the lower devices do need the extra internal storage, but we both know that flash memory is very unreliable for continuous write/delete/rewrite and is doomed to fail.
Could you possibly consider some kind of OTG storage, wireless USB drive or some kind of "cloud" storage or FTP setup?
You should be able to direct your downloads, your pics and your recordings to the folder of your choice when downloaded/created instead of having to move them after. I'm not certain you need to do this just to be able to use your external to store data.
Sent from my LGL84VL using Tapatalk
Hi,
Samsung S8+ exynos, running latest samsung stock image, rooted with magisk 17.3.
SD card set up as regular external storage, *not* adopted storage.
Whenever I try to have something write to SD card I get "Can't write to (volume id of filesystem on card)". I believe its this "security" feature biting me that was introduced some time back in kitkat.
So far I had been using netapp sdfix (https://play.google.com/store/apps/details?id=nextapp.sdfix) to sort this out, but it seems that doesn't work anymore in android 8.
Any ideas? I'm not afraid to ssh into my phone and do stuff at the lowest level.
Cheers
[L]
There are apps that move your apps and the data to external storage. Thats all I know. And you can also set up your camera to save all pictures n videos in external storage by going into settings. Hope that helps. I know it's not the best solution but it helps save up your storage 100%
I know all that, that's not the issue here.
The issue is (for one example) that I can't set the music folder for the humble bundle app to the music folder I'm using on the SD Card (which works just fine in any music app).
I can't use id3fixer to repair mp3 files because it cannot write to the files.
I can't use ghost commander or amaze to create a folder on SD card - it works with the built in "file manager" in android though.
[Lemmy said:
;78046099]Hi,
Samsung S8+ exynos, running latest samsung stock image, rooted with magisk 17.3.
SD card set up as regular external storage, *not* adopted storage.
Whenever I try to have something write to SD card I get "Can't write to (volume id of filesystem on card)". I believe its this "security" feature biting me that was introduced some time back in kitkat.
So far I had been using netapp sdfix (https://play.google.com/store/apps/details?id=nextapp.sdfix) to sort this out, but it seems that doesn't work anymore in android 8.
Any ideas? I'm not afraid to ssh into my phone and do stuff at the lowest level.
Cheers
[L]
Click to expand...
Click to collapse
Check magisk repo there's an app in there to change the setting to read/write permissions for SD cards
but with that module active, wouldn't that mean that for example media scan would find every mp3 file twice?
[Lemmy said:
;78046939]but with that module active, wouldn't that mean that for example media scan would find every mp3 file twice?
Click to expand...
Click to collapse
I don't know you would have to try and find out. As far as I am away it basically gives you read/write access to your SD card it doesn't control what is written to it.
Another thing that you could try is in twrp in the mount menu is to mount SD card.
...and then *reboot* into the installed system, right? I'm pretty sure mounting the card RW in twrip is not going to help...
Then use the magisk module to change the sd card permission to r/w
I don't use ghost commander but it does have access to read/write to SD card(according to google description)
spawnlives said:
Then use the magisk module to change the sd card permission to r/w
I don't use ghost commander but it does have access to read/write to SD card(according to google description)
Click to expand...
Click to collapse
It doesn't, at least not on android 8...
spawnlives said:
Then use the magisk module to change the sd card permission to r/w
I don't use ghost commander but it does have access to read/write to SD card(according to google description)
Click to expand...
Click to collapse
Tried the module, it does mount the card writeable, but the media scanner does not touch anything outside /storage, so id3fixer does not know about the media files, and can't fix the tags.
Why does it seem to require higher magic to be able to just copy and use mp3 files from my computer....
[Lemmy said:
;78049321]Tried the module, it does mount the card writeable, but the media scanner does not touch anything outside /storage, so id3fixer does not know about the media files, and can't fix the tags.
Why does it seem to require higher magic to be able to just copy and use mp3 files from my computer....
Click to expand...
Click to collapse
Have just tried ghost commander file explorer
Basically in normal use it is not in root mode. You have to enable it in settings under advance - show advance home items. This will bring up root mode and mount menus in the home page menu. Have changed sdcard from r/w to r/o back to r/w with no issues. So I would check you settings to see if it is enabled.
Dear all,
the following problem might be unusual and the opposite of what other people want, but as the title says:
Is it possible to prevent Android 11 (and custom ROMs based on it) from writing to the external SD card? That is, I don't want apps or the O/S itself to store any data there. You now probably are asking yourself whether I have gone totally crazy, putting an external SD card into the phone and not wanting it to be used, so I'll give a bit of background:
I have a Samsung S9 plus Duos (G965F/DS) and have installed a custom recovery (TWRP 3.5.2) and a custom ROM (ArrowOS 11) onto it. Then I have installed SSHelper 13.2 and have put an external SD card into the phone.
I am taking backups very seriously. I don't want to root my phone, but nevertheless want bit-for-bit backups of all partitions or data, respectively. I don't have much data on the phone, but the data and the O/S configuration I *do* have must be regularly backed up no matter what. The backup must *not* be in the cloud. That led me to the following idea for the backup process:
- Boot into TWRP
- Let TWRP make the backup, using the partitions of the internal storage as source, and using the external SD card as destination
- Reboot to system
- Fire up SSHelper
- Copy the backup from the external SD card to a PC, e.g. via WinSCP.
That process works like a charm; I have done it several times.
[ Side note: The SSHelper / WinSCP combo is ingenious. It enables me to transfer data (e.g. backups) between my PC and my phone without involving the cloud and without having to pull out the external SD card all the time. Doing the latter every other day would probably damage the phone or the external SD card quite fast. ]
Now I have only one small problem left: Android itself of course recognizes the external SD card as well and installs a folder structure on it (e.g. Downloads, Movies, Pictures etc.). Although I actually haven't seen files (other than placeholders) in there yet, I have no clue if and under which circumstances apps or the O/S might put important data in these external SD card folders. I have to prevent the latter, because it would render my backup method (backup internal storage completely to external SD card) useless.
Hence the question: Is there a method to tell the O/S and all apps that they may read the external SD card, but under no circumstances must place data there?
Thank you very much in advance for any ideas!
P.S. I have seen many threads where users had problems with the external SD card, e.g. not being able to make apps use it or not being able to see its contents. But I somehow have the opposite problem: Of course, I need to see the external SD card's contents (which is no problem), but I want to prevent normal apps and the O/S from writing something there.
No you can't prevent android from creating default folders on it, but I'm pretty sure you can exclude them from backup.
Thank you very much!
However, excluding these folders from backup wouldn't be wise if Android or an app would have put data in them ...
D9yHyi8Fe3mo1YgM said:
Thank you very much!
However, excluding these folders from backup wouldn't be wise if Android or an app would have put data in them ...
Click to expand...
Click to collapse
Then don't exclude the whole Android folder, just some folders inside. Like /obb folder or system apps data inside /data
Or just exclude "LOST" or other cache folders.
D9yHyi8Fe3mo1YgM said:
Dear all
Is it possible to prevent Android 11 (and custom ROMs based on it) from writing to an SD card? That is, I don't want apps or the O/S itself to store any data there.
Click to expand...
Click to collapse
Assuming you are speaking of an External SD-card ( Note: As with Android internal storage memory by default is named SD-card ).
As long as you don't use an external SD-card ( completely or partially ) as Adoptable Storage by default neither apps nor OS itself write to it ( store data on it ).
@jwoegerbauer Thank you very much! This what I have experienced, too. I have seen the folders, but no data in them. I am still wondering why it creates those folders at all if it doesn't put data in them.
I eventually have missed it, but I think I have gone through every option of ArrowOS, but didn't find a menu item where I could activate (or inactivate) the external SD card as adoptable storage. Therefore I suspected it would do that automatically, depending on circumstances.
Another mystery (for me) is that (AFAIK) data would go into subfolders of the "Android" folder on the external SD card. But the Android folder is nearly empty, while the rest of the folder structure (Documents, Pictures etc.) is at the root level of the external SD card (i.e. at the same level as the "Android" folder).
P.S. Yes, I was speaking of the external SD card. I'll check if it's still possible to edit my posts and make that clear.
Thank you very much again!
XDHx86 said:
Then don't exclude the whole Android folder, just some folders inside. Like /obb folder or system apps data inside /data
Or just exclude "LOST" or other cache folders.
Click to expand...
Click to collapse
Thank you very much again!
I should have made myself more clear: My plan is to have all data only in internal storage and to back up internal storage to the external SD card.
When there is normal data (besides these backups) on the external SD card, three problems arise:
1) The normal data on the external SD card takes up space. If I can't control which data Android and the apps put there, the remaining space may not be sufficient for the backups one day.
Every portion of normal data which is on the external SD card counts twice in that sense. First, it increases the backup size by its own size; secondly, it reduces the space which remains for the backups by its own size.
2) I know that I wrote that I will transfer the backups to a PC wirelessly. However, I still want the phone to run normally even after I have removed the external SD card. If Android or the apps put normal data on the external SD card, this is not possible any more.
3) Excluding certain data on the external SD card from backup is problematic and would void the main advantage of my backup strategy:
I really don't need to think about what to exclude or include. I just back up all internal partitions, completely and bit by bit, to the external SD card. If I lose the phone, I can buy another one, flash TWRP onto it, restore those backups, and have the original O/S, apps and all data, and even dm-verify will be no issue.
I have no clue about Android and I am not able (or would be too lazy anyway) to decide which data to include or exclude to achieve the same. So I really would like to avoid that triage.
I believe that some time ago I had found an ugly trick to keep Android and the apps from creating and using those folders. I'll have to check whether I have taken notes about it ...
Thank you very much again!
@D9yHyi8Fe3mo1YgM
To clarify things:
You have to distinguish between portable storage and adoptable storage. Adoptable storage really extends device's internal storage, whereas portable storage does not.
If apps are granted WRITE_EXTERNAL_STORAGE / READ_EXTERNAL_STORAGE permission then they can access the external SD-card, too.
jwoegerbauer said:
You have to distinguish between portable storage and adoptable storage. Adoptable storage really extends device's internal storage, whereas portable storage does not.
Click to expand...
Click to collapse
Thank you very much again! I suspected so, but didn't find the setting in the UI of ArrowOS yet. I am nearly sure that I just missed it, and will research again (just out of curiosity, because extending the internal storage to the external SD card is exactly the opposite of what I want).
jwoegerbauer said:
If apps are granted WRITE_EXTERNAL_STORAGE / READ_EXTERNAL_STORAGE permission then they can access the external SD-card, too.
Click to expand...
Click to collapse
I see. Thank you very much for the explanation. I'll go through the app permissions and check that. Then only the O/S itself could put data there.
[ Side note: In the meanwhile, I have corrected my posts according to your hint regarding the term "SD card". ]
I don't know if this topic has aged or not, have you found any solution?
I don't want Android system to write files like Android-Podcast-Alarms-Music-Notification into my sd card, I want my sd card to be clear and clean
this order system which android uses is very useless and annoying, when will they remove that??!!