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
Related
All of the sudden, all the files on my SD card went missing! I was transferring music and video files to the device over USB (as a storage card, per the custom ROM USB/PC feature) and after it was done, it showed my card as blank.
I took the card out of the phone (XV6900) and put it into my SD adapter and into my computer. The 4GB card shows that 1.8GB are in use when I go to properties, however, there are no files at all in the root of the drive! Like they are invisible! (Yes, I have Windows set to show all hidden and system files, so that is not the problem)
How do I get my files to reappear? It looks like they are not actually deleted! i don't get why this happened all of the sudden
you can try an undelete program and check the sdcard while in the reader
undelete programs can handle sdreaders just like they can hd's
Rudegar said:
you can try an undelete program and check the sdcard while in the reader
undelete programs can handle sdreaders just like they can hd's
Click to expand...
Click to collapse
Did that already...it found a ton of stuff that used to be on there, but not the current files.
had the same thing happen to me once in awhile
where the sdcard just get corrupt which is why I keep
an raw copy of it on my computer in case I need to copy it back
Rudegar said:
had the same thing happen to me once in awhile
where the sdcard just get corrupt which is why I keep
an raw copy of it on my computer in case I need to copy it back
Click to expand...
Click to collapse
I'm using the same 4GB card as my old phones. this never happened on my Titan or TouchPro, each of which I have for a year or so. I have had a Vogue for 1 week and it has happened twice! does the XV6900 wipe the card periodically or when performing certain actions? even on a ROM update/flash it should touch the SD card when running from the RUU package in windows
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 have recently got a Shield Tablet and I have attempted to add a 128GB to the internal storage but every time I go through the adoption process to bring it into internal, it formats it and results in it being corrupted? The sdcard is brand new.
Tablet is on Marshmallow.
HeroXx said:
I have recently got a Shield Tablet and I have attempted to add a 128GB to the internal storage but every time I go through the adoption process to bring it into internal, it formats it and results in it being corrupted? The sdcard is brand new.
Tablet is on Marshmallow.
Click to expand...
Click to collapse
I am having the same issue with the Shield tablet and a 128g sd card. I can use as portable, but trying to adopt as internal storage always returns the "damaged" partition after formatting and starting the moving process. I have tried formatting as ext4 in a PC first as recommended by others to no avail. If anyone is able to get this working please post your fix.
Found the below "Notes" on Nvidia's site. Looks like you'll have to format NTFS on your PC. Some PCs will not allow you that option out of the box, but you can easily change Windows' built-in formatter's options to allow it to format NTFS. The settings are somewhat hidden. To enable it, open up Device Manager and find your micro-SD card, go to the Properties -> Policies tab and then choose "Optimize for performance". Once you've done this, you'll see the NTFS option in the format dialog. Just make sure you "Eject" the card properly, as it seems it's more easily corrupted if not ejected properly.
NOTES:
The ability to move data to SD card is variable for select*apps*and games. Onlyapps*that developers have opted in as moveable to external storage can be moved.
The SHIELD tablet K1 only supports writing to FAT32 and NTFS formatted cards.
64*GB*(or higher) microSD cards – Android does not support the exFAT file system out-of-the-box. Because the standard FAT32 file system does NOT support partitions greater than 32*GB*by default, 64*GB*cards come pre-formatted as exFAT. If you want to use a 64*GB*microSD with the SHIELD tablet K1, it has to be converted to a file system format that is supported by stock Android, which in this case is NTFS. This can be done using a PC.
Android KitKat significantly changes the way applications are allowed to use SD cards. If you use SD Card to store data, please read here for further details."
Hey, I have a similar problem but wanted some opinions.
Received my new K1 and updated to MM and everything is cool. Installed PNY 64GB (10 class) and chose the integrated storage option. The K1 sees the storage and I'm able to move apps to it. My problem is that new apps cannot download due to no storage. The message "whatever app cannot be downloaded. Install a SD CARD......something, something" (sorry, I'm at work).
Will formatting my sd card to FAT32 or NTFS fix this or is there something else wrong? I haven't seen any messages or errors regarding corruption and the sd card is working.
Thanks for any helpful suggestions!
When my 64Gb card was formatted exFat as it came stock, i had the same issue. I'm on LP. I had an almost empty card inserted, other than some mp3 files, and kept getting the message that my storage was full and that i need to delete some apps. I've since formatted it NTFS but i have not checked to see if items are being sent to the external SD. Don't have my tablet with me right now to check, but i wanted to reply to you that you were not alone in seeing the out of room message.
Sent from my LG-E980 using XDA Free mobile app
I had my PNY 64GB formatted with exFAT and it worked ok. I've switched to adopted storage and that worked too. But I saw other glitches with internal storage, such as MTP not seeing all files/folders even after reboot. I think "adopted storage" is buggy in general currently. It's also quite slow. Not impressed.
I prefer the Move to SD of Lollipop and Kitkat.
Do we already have a fix/workaround for this? I have a K1 (with the latest OTA 1.2) and 64GV Samsung Evo, formatting the sd card as adoptive storage still says corrupted. I already tried formatting it as Fat32/NTFS but to no avail.
I also couldn't get adopted storage to work.
The best fix for me is not using adopted storage
Instead I use an app called FolderMount which simply creates a symbolic link (is this the correcton term?) on the device's internal storage for whatever folder/file you like. It integrates moving data and managing it as well making the process as easy as it gets though you can of course do the same thing manually as it's using linux operations to do these things.
After you make the symbolic link when apps look for the data in the usual place on internal storage they "see" it but the data is actually whereever the symbolic link points to ie. on your external SD card.
Not found any real workaround for this it makes the tablet a bit of a dud
Sent from my SHIELD Tablet K1 using XDA-Developers mobile app
diji1 said:
I also couldn't get adopted storage to work.
The best fix for me is not using adopted storage
Instead I use an app called FolderMount which simply creates a symbolic link (is this the correcton term?) on the device's internal storage for whatever folder/file you like. It integrates moving data and managing it as well making the process as easy as it gets though you can of course do the same thing manually as it's using linux operations to do these things.
After you make the symbolic link when apps look for the data in the usual place on internal storage they "see" it but the data is actually whereever the symbolic link points to ie. on your external SD card.
Click to expand...
Click to collapse
I've read about the FolderMount app before but I thought that it works only for lollipop. I'll give this a try. Thanks!
NinjaCoool said:
I've read about the FolderMount app before but I thought that it works only for lollipop. I'll give this a try. Thanks!
Click to expand...
Click to collapse
Caveats: I actually haven't tried it on Marshmallow since I went back to LP however I cannot see any reason that FolderMount will not work as it's using underlying Linux operations to do all the work. But YMMV.
I like this approach since you can move any folder from internal storage to microSD which makes it very flexible. For example you could move:
/Download
/Images/DCIM
/Android/obb
/Android/data
/where you store recorded videos/
and never worry about internal storage again (until you run out of microSD of course lel)
Or whatever you wanted.
diji1 said:
Caveats: I actually haven't tried it on Marshmallow since I went back to LP however I cannot see any reason that FolderMount will not work as it's using underlying Linux operations to do all the work. But YMMV.
Click to expand...
Click to collapse
FolderMount from the Play Store is not working on MM due to security changes.
There is a beta version that fixes it for some devices. Best to read the official thread here: http://forum.xda-developers.com/showthread.php?t=2192122
Sent from my SGH-I337M using XDA Free mobile app
There's a problem with cards 64GB and up. I managed to format as internal storage a 32GB one, had no succes with 64 and 128 ones
I couldn't get portable storage to work on the stock MM RoW LTE rom. It works perfectly fine on all the custom roms I've tried (Bliss, Temasek, RR, etc) but none of those have LTE so for me it's either or if I want to use a MM rom. Otherwise, I'd have to use a LP rom for both to work...
I've hit this issue using the RR rom with my 128gb SD. But then if I keep the card in portable mode, I have those permission issues with my emulators. Has anyone got any suggestions or recommendations?
I've so far tried xInternalSD, SDFix and FolderMount with no success and I don't want to do that solution where I have to adjust the permission xml of all my apps. Its micromanagement I don't want.
I just have to use fat32 to get my 128gb card to work.
gqukyo said:
I just have to use fat32 to get my 128gb card to work.
Click to expand...
Click to collapse
To work as adopted storage or portable storage? Because mine is working in portable mode, just has write to SD permissions issues for any apps not updated to deal with MM's new OTT security requirements on External SD's (which is most apps to be honest).
Adopted storage, I only tried it once but didn't like it so using portable.
gqukyo said:
Adopted storage, I only tried it once but didn't like it so using portable.
Click to expand...
Click to collapse
Being Fat32 initially shouldn't have made a difference, because the card is reformatted to ext4 when its made into adopted storage and the tablet just seems incapable of reading an ext4 encrypted SD Card, so it comes up as corrupted.
What brand and model is your 128gb micro sd? And was it the stock rom you did it on? I'm using a Sandisk Ultra myself, and this definately does not work.
It's been awhile so I don't recall all the things I've tried nor the roms. All I know is I got it to it to work once. Think I have a SanDisk something. Just wasn't worth it in the end to me. If you're trying to get it to work, doesn't hurt to try. Stranger things have worked to fix issues in android.
In the past on my Android phones, primarily LG, I have had SD cards installed and they became the default storage location for download, DCIM, images saved from any program, etc. Now I have the G5 and it seems to be quite different. I have an SD card installed and it seems there is no way to make it the default location as it has been in the past. I understand that adoptive storage can be made to work to use the SD card for more 'internal' RAM but I have had two issues with this, 1. I can't see the phone with ADB when connected to my PC and 2. I can't seem to find adoptive storage instructions that work. I am not new to LG or Android phone but this one has me a bit confused. Can adoptive storage be used on the T-Mobile G5 and/or can the SD card be made the default location for the G5 to store things, like DCIM, downloads, etc like all the LG phones in the past?
Thanks,
T.E
I was able to get adoptable storage going, discovered there's a typo in Paul O'Brien's article, once I fixed that I was set to jet. This is an edit from Paul's article here:
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
1. BACK UP THE DATA YOU HAVE ON YOUR MICROSD CARD. Your card will be formatted by this process, so make sure you have saved any pictures, videos etc. from your card to your PC before you start.
2. Decide how you want to split your card. You can either commit 100% of the card to internal storage, or split between internal storage and conventional SD. This option is useful if you like to unplug your card and put it in your PC. I would probably recommend committing the whole card.
3. Umount the sdcard before connecting it in debug mode to your pc.
4. Open your command window / terminal on your computer and type the 'adb shell' command (with your phone connected of course). You will need to enable USB debugging in developer settings (which in turn is displayed by tapping the build number of the device 5 times) in order to see the option.
5. Type 'sm list-disks' to list the disks available for adoption. It'll look something like below - take note of the disk ID (disk:179:160 in this example).
6. Partition the disk. For this we use the 'sm partition DISK TYPE RATIO' command. For example, to partition the disk above as fully adopted storage (aka private) I'd use the command 'sm partition disk:179,160 private'. If I wanted a 50/50 split between adopted and regular, I'd use the command 'sm partition disk:179,160 mixed 50'. Easy right?
7. This took almost no time at all for me.
8. Go to the sdcard in storage and move data to it. This will then merge the space on the card and the internal storage.
HTH.
Ok, first problem first. I have the SDK installed, debug mode on and phone connected. I can see the file system on the phone but ADB DEVICES returns nothing. Until I can get that resolve I can't even do the rest.
Can anyone tell me how to get the T-Mobile LG G5 to be recognized by ADB?
Resolved and I believe I have the adoptable storage working now.
If this is done with a somewhat slow SD card will it have a negative impact on the entire system?
btothec said:
If this is done with a somewhat slow SD card will it have a negative impact on the entire system?
Click to expand...
Click to collapse
Maybe. Please correct me if I'm wrong but adoptable storage tries to only put stuff on the sdcard that will live comfortably there. Nothing system related will go there, so worse case an app takes longer to launch.
scottricketts said:
Maybe. Please correct me if I'm wrong but adoptable storage tries to only put stuff on the sdcard that will live comfortably there. Nothing system related will go there, so worse case an app takes longer to launch.
Click to expand...
Click to collapse
I am using a 64gb Class 10 and have not noticed any significant change in performance.
scottricketts said:
I was able to get adoptable storage going, discovered there's a typo in Paul O'Brien's article, once I fixed that I was set to jet. This is an edit from Paul's article here:
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
1. BACK UP THE DATA YOU HAVE ON YOUR MICROSD CARD. Your card will be formatted by this process, so make sure you have saved any pictures, videos etc. from your card to your PC before you start.
2. Decide how you want to split your card. You can either commit 100% of the card to internal storage, or split between internal storage and conventional SD. This option is useful if you like to unplug your card and put it in your PC. I would probably recommend committing the whole card.
3. Umount the sdcard before connecting it in debug mode to your pc.
4. Open your command window / terminal on your computer and type the 'adb shell' command (with your phone connected of course). You will need to enable USB debugging in developer settings (which in turn is displayed by tapping the build number of the device 5 times) in order to see the option.
5. Type 'sm list-disks' to list the disks available for adoption. It'll look something like below - take note of the disk ID (disk:179:160 in this example).
6. Partition the disk. For this we use the 'sm partition DISK TYPE RATIO' command. For example, to partition the disk above as fully adopted storage (aka private) I'd use the command 'sm partition disk:179,160 private'. If I wanted a 50/50 split between adopted and regular, I'd use the command 'sm partition disk:179,160 mixed 50'. Easy right?
7. This took almost no time at all for me.
8. Go to the sdcard in storage and move data to it. This will then merge the space on the card and the internal storage.
HTH.
Click to expand...
Click to collapse
Can this be undone? What happens if you remove the sdcard? Is it still readable in a PC, so the files could be recovered if the phone died?
Click on the sdcard then select make portable storage. No clue what happens if you take it out other than some programs won't work.
kchannel9 said:
Can this be undone? What happens if you remove the sdcard? Is it still readable in a PC, so the files could be recovered if the phone died?
Click to expand...
Click to collapse
If it gets encrypted you won't be able to read it in a PC.
Sent from my LG-H830 using XDA-Developers mobile app
Can someone that had done it please post pics of how is it supposed to look like once you do the process, the reason I asked is bc under storage I can see the storage as one but in many google apps I only the the the 32gb of storage and no 211gb like on the storage settings. Thanks in advance
TheEditor said:
Ok, first problem first. I have the SDK installed, debug mode on and phone connected. I can see the file system on the phone but ADB DEVICES returns nothing. Until I can get that resolve I can't even do the rest.
Click to expand...
Click to collapse
How did you do it im having the same issue?!?!?!?!
TheEditor said:
Resolved and I believe I have the adoptable storage working now.
Click to expand...
Click to collapse
how did you fix the adb shell problem?!?!?!
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
i get this when i type in adb shell
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Dawid>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
C:\Users\Dawid>
what do i do? how do I fix this?
you guys have adoptable storage working? do you guys like it? Yay Or Nay? i have it working fully no problems just i havent formatted my sd card yet. wondering if its worth doing.
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??!!