My main problem is I have LOTS OF APPS. Because of this, I have to move them to the microSD card. The apps I usually move are the ones that eats up lots of space like games.
I've noticed another problem when I started moving the games unto my microSD card. Since the games has music files as well (like sound effects and in-game songs and whatnot) whenever I open a media player such as Ubermusic for example, I've noticed that those game music files also gets detected by Ubermusic. Because of this, whenever I choose "Shuffle All" and play all my music there would be times that I would hear Angry Birds squawking and them evil pigs getting smashed mixed in with my songs. (^_^") It has grown into a huge problem for me, since I can't move them back to the /data partition as there isn't any space left in there.
Currently, I use App2SD Pro to move those apps, and I hate it because even if you choose "Move All Apps" you still have to manually move them by pressing the button one by one and it has been so time-consuming. Because of this, I've been on a search for a proper solution.
Please correct me if I'm wrong.
Based on my personal research, I believe that we can partition the microSD card in such a way that it can have a /data partition of it's own, and that's what we call SD EXT right?
If that's true, does that mean that if I have this set up in my microSD card and my /data partition is full of apps, will the next app that I would install automatically gets installed to the SD EXT? Or do I need an app like Link2SD (based on my own research, I believe this app requires an SD EXT to work properly.) to manually transfer the apps that would not fit in the original /data partition?
And can someone please confirm-- since the app "Link2SD" says "link", does this mean that it just "links" or creates a "shortcut" in the microSD for the apps or does it really move the apps in the microSD?
And last but not the least, can someone point me out to the right direction where I can find an easy to follow guide (if there's any) to be able to create an SD EXT partition in my microSD card.
Oh, and by the way, I have a 16GB Samsung SDHC Class 2 microSD card if that would help.
Thanks in advance for all those that would help out! This community has never failed me, and I'm proud to be a part of it!
les02jen17 said:
Based on my personal research, I believe that we can partition the microSD card in such a way that it can have a /data partition of it's own, and that's what we call SD EXT right?
Click to expand...
Click to collapse
I may be new in posting, but as far as I know: SD-EXT is the whole sd card itself when your device does support internal second usb storage (also named sd card). That is the case for my Galaxy S2 where SD-EXT only refers to my EXTernal (i.e. removable) sd card; there's a fixed (internal) sd card too.
SD-EXT does not mean anything else for me.
Hope that'd be useful.
les02jen17 said:
And last but not the least, can someone point me out to the right direction where I can find an easy to follow guide (if there's any) to be able to create an SD EXT partition in my microSD card.
Oh, and by the way, I have a 16GB Samsung SDHC Class 2 microSD card if that would help.
Click to expand...
Click to collapse
I'm guessing you are on a custom ROM. You can partition your SD with CWM recovery. If your ROM supports apps2sd it will use the ext partition.
Class 2 is letter used for storage than performance, though.
Sent from my NookColor using xda premium
Related
I rooted my Aria using Unrevoked's one-click method, and flashed ATTN's FR008 ROM. I currently have only the factory 2GB sd card. I dl'd APPS2SD from the market and have moved the apps that are eligible to the SD card. There are still many apps that are still on the internal storage. My internal storage usually hovers around 100MB free; for right now anyway.
How low can the internal storage get before performance begins to degrade? Would it benefit me to dl ROM Manager? I am not too familiar with the pros/cons and/or procedures for partitioning the sd card.
Any help or advice is greatly appreciated! This is a great place for support and information and THANKS to all the dev's for all their hard work!!!
Perseids said:
I rooted my Aria using Unrevoked's one-click method, and flashed ATTN's FR008 ROM. I currently have only the factory 2GB sd card. I dl'd APPS2SD from the market and have moved the apps that are eligible to the SD card. There are still many apps that are still on the internal storage. My internal storage usually hovers around 100MB free; for right now anyway.
How low can the internal storage get before performance begins to degrade? Would it benefit me to dl ROM Manager? I am not too familiar with the pros/cons and/or procedures for partitioning the sd card.
Any help or advice is greatly appreciated! This is a great place for support and information and THANKS to all the dev's for all their hard work!!!
Click to expand...
Click to collapse
The internal storage you're seeing is strictly for apps and doesn't affect the operating system in any way. So no performance will ever be lost due to filling this up with as apps. To see "system"memory go menu> applications> running services. That's the one that affects performance.
Sent from my cm7 Aria using XDA App
What is the deal with EXT/2 and etc...?
I haven't figured out what the deal with the EXT partition is yet. I got a new 8GB card and was gonna put it in but was gonna wait til I understood all that first.
Should I Do a nandroid backup..
copy all contents of current SD card to pc...
Insert new card...
Format/Partition new card...
Copy previous backup of SD card to new card...
I'm just a little lost as to the advantage of the partition.
Any info. is greatly appreciated!
Noob question sorry, Is there a point where the memory in the device affects its performance? Like if too much of the internal memory is used will the phone run slower? Or what is the point of this apps to SD.
Using DT's A2SD method involving an ext2, 3, or 4 partition on the SD card moves every downloaded and installed app (minus system apps) onto the SD card. The A2SD provided with Froyo only allows apps that have been updated to work with A2SD would be able to move.
Moving all of your apps to the SD card is essentially the same as Cyanogen's setting to move all apps to the SD card. However, with the partition and DT's A2SD, it mounts the SD card's partition during the boot process which allows widgets and Facebook sync to be run off the SD card directly. (ie. Facebook sync will always stay synced no matter how many times you reboot, widgets will not have a "Problem Loading Widget" bar on your homescreen after you reboot)
With the normal A2SD, the apps on the SD card will load last after your phone has already booted up ("Preparing SD Card" in the notification bar).
Plus, you would be able to move your dalvik-cache (and app data --> experimental) to the SD card's partition also freeing up more internal memory.
Perseids said:
I haven't figured out what the deal with the EXT partition is yet. I got a new 8GB card and was gonna put it in but was gonna wait til I understood all that first.
Should I Do a nandroid backup..
copy all contents of current SD card to pc...
Insert new card...
Format/Partition new card...
Copy previous backup of SD card to new card...
I'm just a little lost as to the advantage of the partition.
Any info. is greatly appreciated!
Click to expand...
Click to collapse
The above steps are correct. If you want an ext partition you can do that through rom manager (will wipe sd card so back up to pc).
Unless you plan to run the DT a2sd you don't need an extension partition. Froyo a2sd moves the apps to the fat32 partition, the main partition of your sd card, not an ext partition.
I personally recommend using DT a2sd.
Sent from my cm7 Aria using XDA App
vicmora5 said:
Noob question sorry, Is there a point where the memory in the device affects its performance? Like if too much of the internal memory is used will the phone run slower? Or what is the point of this apps to SD.
Click to expand...
Click to collapse
you could fill your internal memory up to the point where there was no more room for apps to cache I suppose. But that's really it.
Sent from my cm7 Aria using XDA App
Success, but need more help
Okay, I got my sd card partioned (512MB EXT, 64MB swap). I dl'd and installed DT's A2SD and the best I can tell upon reboot A2SD moved apps to SD card. The only way I can tell is using DriveWatch.
I am using GOLauncher EX and now the flipping in the tray appears to be greatly affected by the app being on the SD card. Is there a way to move selected apps back to the phone?
No there isn't.
BTW you can check if your apps are on your SD card by typing
su
a2sd check
a2sd diskspace
In the terminal emulator
Perseids said:
Okay, I got my sd card partioned (512MB EXT, 64MB swap). I dl'd and installed DT's A2SD and the best I can tell upon reboot A2SD moved apps to SD card. The only way I can tell is using DriveWatch.
I am using GOLauncher EX and now the flipping in the tray appears to be greatly affected by the app being on the SD card. Is there a way to move selected apps back to the phone?
Click to expand...
Click to collapse
What you can do is delete go launcher then unzip the rom you flashed and put the go launcher apk into the /system/app folder and rezip it. boot into recovery, wipe cache and dalvic (don't wipe data), and then reflash your rom. DT a2sd doesn't move apps on the /system partition. This is what I do with launcherpro.
EDIT: you can try just pulling the go launcher apk via ADB and then removing it from the /data/app folder and then pushing the pulled app to the /system/app folder. This would be easier but I've had apps that FC after using this method. Some work, some don't.
Sent from my cm7 Aria using XDA App
Great advice!. Seems there is always more than one way to skin a cat. I will give one of those methods a try.
Clear your doubts guys!!!
Ok, so here's the deal, in a very longwinded way that should hopefully explain everything and answer ALL questions.
You have an SD card in your phone and, a bit like normal PC Hard Drives, you can "partition" them (split them into two or more sections of different filesystems). Normally, your SD card is just one big FAT32 partition, which is fine for storing your pics, messages, emails, etc.
Now, other then your Phone's SD card, your phone will have its own internal flash memory (or "NAND") storage. Tradditionally with Android, you could only install applications to this NAND storage, you cannot install them onto your SD card. So if you have an empty 32GB SD card, but only 5Mb of internal phone storage, you still wont be able to install many apps, if any at all.
This was done to protect the apps from things like piracy - it's not easy to access the location where apps are installed on your phone's internal storage (normally impossible without root), so you can't for example buy an app, copy it, refund it, then install it again.
Still, this is no good for those of us who like to install lots and lots of apps, legitimately, as we run out of internal storage very quickly.
So Google came up with a way to install apps to the SD card. A folder is created called something like .android_secure and this stores (I believe) encrypted versions of applications, but there's a few catches:
1) Apps aren't automatically stored here, you have to manually "move" them
2) Not all apps are capable of being moved, in fact most apps aren't, the developer needs to update their app and allow it. Some apps aren't and wont be updated and some developers may not want to allow it for whatever reason.
3) Not all app data is moved, most of it is but some data is left on your phone so many people still run out of internal storage quickly.
4) You can force ALL apps to be moved to this area by default, but it breaks incompatible ones - such as Widgets, which are unable to load due to the SD card not being "prepared".
So that's Froyo's version. Before Froyo existed, some very clever people came up with a thing called "Apps2SD". Remember I said that your SD card normally is one big FAT32 partition? Well, Apps2SD works by having your SD card patitioned into TWO filesystems. A normal FAT32 partition for your usual stuff and a secondary "EXT" partition. EXT is just a filesystem, like FAT32 or NTFS, but it's the filesystem used by Android internally. The SD card is normally FAT32 because it's a "universal" filesystem, that just about any machine will be able to read, whereas EXT filesystems are generally Linux only, but I digress.
EXT has several different versions. The most common one you'll see is ext3. The main difference between ext2 and ext3 is "journaling", which is just a fancy way of saying that should an operation (such as copying, writing or reading) be interrupted unexpectedly (say, by you turning your phone off), then no data should be lost or corrupted. You know how when you turn your phone on, it says "preparing SD card"? It takes a few minutes, but what it's actually doing is checking that the FAT32 partition hasn't been damaged, because FAT does NOT have journaling. If you used a computer back in the Windows 98 days, you may remember that lovely blue "Scandisk" screen that had to run every time you didn't shut your computer down correctly - that's the same thing. But then Windows 2000/XP came along with NTFS, which also has journaling, meaning you had less chance of loosing data. But I digress once more.
So you have your SD card partitioned into EXT and FAT32. Generally it doesn't matter if it's ext3 or ext4, but you don't get any real advantage with ext4 over ext3 in this instance. Apps2SD then runs a special script on your phone which "symbolically links" the folder from your phone's internal storage where your apps are normally stored, to the ext partition on your SD card. A symbolic link is a bit like a shortcut for folders, except it's transparent to the OS: In other words, Android doesn't know that when it's installing it's apps to the internal phone storage, it's actually being stored on the SD card. This effectively boosts your internal phone memory from the previous 5mb that you had in my example above, up to whatever size you made the ext partition on your SD card (often 512Mb or 1Gb, but it depends on how many apps you install).
Plus, because it's "journaled", it doesn't need to be "prepared", meaning it's ready to go as soon as the phone starts - so your widgets and apps work immediately (unlike "forced" Froyo Apps2SD, where widgets disappear).
The catch with Apps2SD is that whatever space the ext partition takes up is taken away from the SD card. So if you have a 4Gb card (with something like 3.5Gb of actual storage) and you make a 512Mb ext partition, your SD card will "shrink" to 3Gb. The space isn't actually lost, it's just being used by the ext partition. If you reformat your card, you'll get it back.
Finally, there's a difference between "Apps2SD" and "Apps2SD+". Remember I said that your apps are stored on a special folder inside your Phone's NAND storage? Well, that was a bit of a lie. It's actually stored in TWO places. There's a second area which is called the Davlik Cache. You don't really need to worry about what this is for (Hint: IT's to do with the Java runetime your phone uses to run apps), all you need to know is that apps use it to store data, which also eats up internal phone memory. Apps2SD+ moves davlik cache to the ext partition on your SD card as well, freeing up even more space. Some people believe that this may come at the cost of performance, as the internal NAND memory should be faster than your SD card (Which is why you also get people arguing over which "class" SD card is better for Apps2SD - the logic being that a faster SD card means less impact from this move), but the truth of the matter is that your applications will be running from your Phone's RAM anyway, so performance isn't really impacted at all. Since most apps are only a few hundred Kb's in size, or a couple of MB at the most, it's a non-issue.
Finally, any recent version of Apps2SD/Apps2SD+ should work with an SD card that is or isn't formatted with an ext partition. It'll check for this partition when your phone first boots and if it's not there, just use internal phone storage.
Having an ext partition WITHOUT Apps2SD+ shouldn't cause any issues, either, so you can format your SD card whenever you're ready.
So in summary:
Apps2SD "fakes" your phone's internal memory and puts it all on a hidden section of your SD card.
Apps2SD+ pushes even more content to the SD card, freeing up even more space on the phone itself.
"Froyo" Apps2SD has various limitations that "old" apps2SD does not, but is much easier to handle as it doesn't involve any kind of "partitioning".
Hi,
I wonder if someone can help me, I've got WP7.5 install as a NAND installation, with Android 4.0.4 as a SD installation. Both work brilliantly, although I do have some slight problems.
Android won't detect an SD card installed, so I can't use some apps, that require an SD card to be present.
Does anyone know if there is a fix for this, surely I'm not the only person in this position.
Cheers
I'm guessing it's because your SD has been formatted specially by WP, and Android can't read this. Your FAT32 partition is probably too small for anything to be stored in it.
The Fat32 partition is 1.6Gb.
Is it worth making that bigger, or creating another FAT32 partition?
Cheers
Hmm, I'd guess that you wouldn't have any more than 200-300MB free on your SD as read by SD Android then. I don't know how much an SD Android build takes up but the data.img is at least 1GB of that. As for increasing the partiton/creating a new one, I don't actually think that's possible without losing your data is it?
Hi,
Thanks for your help.
I'm not too fussed about losing anything...
Here is what I have just tried without any success.
I have a 8Gb card partitioned like this.
1.*Gb
Primary, FAT32, (Android SD install)
2Gb
Primary, FAT32, (My hope would be that Android would see this as the SD card)
4Gb Other (WP 7 partition)
No luck unfortunately, any ideas?
Cheers
Are you sure you're using an 'unlockable' WP7.x ROM? If so, try formatting the storage card to normal and flash a Android build, see if it utilises the memory card like normal, if it does, then I would say that you're doing something wrong when setting it up.
Just double check each step of a tutorial (example: this one) twice and hopefully you'll only have to flash one more time.
Why do you have 2 fat 32 partitions ?...just use one fat 32 partition..in regular sd android....data image is used as internal memory and fat 32 part as sd card
I believe your second partition is not being recognised...make only one fat 32 partition you don't need two
Sent from my HTC HD2 using Tapatalk 2
So I am running CM7 off of an sd card in my nook color.(Using http://forum.xda-developers.com/showthread.php?t=1904129 and I highly recommend). Win32discimager for some reason created a small partition just larger than the installer which remains on the card. I also have the android OS on the card that is taking up 1 gb partition. The rest of my 16gb micro sd card is labeled as the emmc for the tablet which is not what i intended. Now I cant load it up with my movies and videos like I had hoped.
Does anyone know:
Is there any way I can change these partitions on my card? (I have already tried EasuUS partition manager)
Where did the 1gb partition that android is on come from and why did the emmc get so large?
Is there any way to take the android image currently on my sd card and just putting onto the nook after I have already had it run from the sd card and then just formatting my sd card for storage?
There are probably newbie questions but I have tried to do my own research and havent found any certainties. Any help would be really appreciated.
posturize said:
So I am running CM7 off of an sd card in my nook color.(Using http://forum.xda-developers.com/showthread.php?t=1904129 and I highly recommend). Win32discimager for some reason created a small partition just larger than the installer which remains on the card. I also have the android OS on the card that is taking up 1 gb partition. The rest of my 16gb micro sd card is labeled as the emmc for the tablet which is not what i intended. Now I cant load it up with my movies and videos like I had hoped.
Does anyone know:
Is there any way I can change these partitions on my card? (I have already tried EasuUS partition manager)
Where did the 1gb partition that android is on come from and why did the emmc get so large?
Is there any way to take the android image currently on my sd card and just putting onto the nook after I have already had it run from the sd card and then just formatting my sd card for storage?
There are probably newbie questions but I have tried to do my own research and havent found any certainties. Any help would be really appreciated.
Click to expand...
Click to collapse
Ok, first you need to go to my tips thread linked in my signature and read in section B how the verygreen SD works. You will understand the partition structure a little better.
Now for your sdcard/emmc media storage problem, you have a setting wrong in CM7. Go to settings, CyanogenMod settings, Application and uncheck "Use internal storage". What that setting does is swap emmc and sdcard so that your real sdcard is called emmc and internal media storage is called sdcard. It is not default that way. Somehow it got checked.
Sent from my Nook HD+ using Tapatalk
I'm using a 400GB SD card. I saw a comment about creating 2 different partitions on it as I want to use part of it for app storage and the other part for file storage, The second partition would be exFAT so I can remove the card and transfer my books, music, etc. to it by attaching the SD card to my laptop as I understand that Windows would not be able to recognize the partition that would be formatted as internal storage. I did format the SD card using my laptop as two separate partitions. My Samsung Galaxy Tab A saw both partitions. I selected the 96GB partition as I wanted to use that for app storage and selected the option to use it as internal storage. Unfortunately when I did that, it appears that the system set the whole CD card up for internal storage. Does anyone have any insight on how to accomplish this - use part of the SD card for internal storage and part of it for storage that would be recognizable by Windows? Thank you very much.
I have not tried, so take the advice as a suggestion, perhaps android can be "fooled", which I doubt.
After creating a bulk partition in android, move the SD to Windows and resize that partition, and create a second partition on the remaining capacity and hide it.
Now move the SD back to android and see what happens.
If android will reformat the partitions again then I can't advise anything else.
However, if android accepts the memory, then the next step is to discover the partition in Windows and recheck the SD in android.
ze7zez said:
I have not tried, so take the advice as a suggestion, perhaps android can be "fooled", which I doubt.
After creating a bulk partition in android, move the SD to Windows and resize that partition, and create a second partition on the remaining capacity and hide it.
Now move the SD back to android and see what happens.
If android will reformat the partitions again then I can't advise anything else.
However, if android accepts the memory, then the next step is to discover the partition in Windows and recheck the SD in android.
Click to expand...
Click to collapse
Well, I was trying to work on that and now the Android Storage module (in Settings) keeps crashing when I open it. IDK what happened here. I've reformatted the SD card, I've removed the SD card, I've rebooted the table multiple times. I'm almost to the point of having to restore the tablet from scratch ... again.
Try this:
Link2SD - Apps on Google Play
Complete app management, move to SD, clear cache, remove bloatware and more
play.google.com
JR1979 said:
I'm using a 400GB SD card. I saw a comment about creating 2 different partitions on it as I want to use part of it for app storage and the other part for file storage, The second partition would be exFAT so I can remove the card and transfer my books, music, etc. to it by attaching the SD card to my laptop as I understand that Windows would not be able to recognize the partition that would be formatted as internal storage. I did format the SD card using my laptop as two separate partitions. My Samsung Galaxy Tab A saw both partitions. I selected the 96GB partition as I wanted to use that for app storage and selected the option to use it as internal storage. Unfortunately when I did that, it appears that the system set the whole CD card up for internal storage. Does anyone have any insight on how to accomplish this - use part of the SD card for internal storage and part of it for storage that would be recognizable by Windows? Thank you very much.
Click to expand...
Click to collapse
You're trying to convert a partition in sd card as internal storage and leave the rest as an external storage. Not possible as far as I know.
TheMystic said:
You're trying to convert a partition in sd card as internal storage and leave the rest as an external storage. Not possible as far as I know.
Click to expand...
Click to collapse
Thats a bummer but that is what I was feeling was going to be the outcome. I guess I'll just go with it as internal storage then and be rlefated to wireless transfer of my books, etc. To the tablet. Any thoughts on why my Storage module keeps crashing now? Something definitely went nuts somewhere along the way here. It was running fine.. until I start poking around with this. I'll probably just do a rebuild again tonight.. if I can find my steps notes.
I also don't think it's possible to do what you have in mind. It's also important to remember that Windows will only mount the first partition of an SD card. It won't see any other partitions without 3rd party software installed.
JR1979 said:
Thats a bummer but that is what I was feeling was going to be the outcome. I guess I'll just go with it as internal storage then and be rlefated to wireless transfer of my books, etc. To the tablet. Any thoughts on why my Storage module keeps crashing now? Something definitely went nuts somewhere along the way here. It was running fine.. until I start poking around with this. I'll probably just do a rebuild again tonight.. if I can find my steps notes.
Click to expand...
Click to collapse
The reason people want a micro SD card is to be able to move it around between devices, so it is not a good idea to convert it into 'internal storage' for two reasons:
1. You can no longer move the card around (not without reformatting it again).
2. This process would significantly slow down the system if the OS starts saving apps, data and files on the micro SD card because it sees this space as internal storage.
Because of how you partitioned the SD card and tried converting only a part of it as internal storage, my guess is the process caused corruption somewhere, and the system is crashing because of that. I'm afraid you'll have to do a factory reset and start from scratch. I hope your files are safe.
JR1979 said:
I'm using a 400GB SD card. I saw a comment about creating 2 different partitions on it as I want to use part of it for app storage and the other part for file storage, The second partition would be exFAT so I can remove the card and transfer my books, music, etc. to it by attaching the SD card to my laptop as I understand that Windows would not be able to recognize the partition that would be formatted as internal storage. I did format the SD card using my laptop as two separate partitions. My Samsung Galaxy Tab A saw both partitions. I selected the 96GB partition as I wanted to use that for app storage and selected the option to use it as internal storage. Unfortunately when I did that, it appears that the system set the whole CD card up for internal storage. Does anyone have any insight on how to accomplish this - use part of the SD card for internal storage and part of it for storage that would be recognizable by Windows? Thank you very much.
Click to expand...
Click to collapse
You should NEVER use an SD card for internal storage. They are MUCH to slow for that purpose. Today's SoC have RAM chips mounted directly on top and are several times faster than the fastest SD card bus. And low end tablets, which includes ALL Tab A devices, use a USB bus with limited bandwidth. So using faster SD cards is pointless as they will still only be as fast as the bus. SD cards are fine for storing video, audio, text and downloaded files, but NOT for running apps. Doing so will cause the device to be laggy at best, and cause crashes at worst.
blaacksheep said:
I also don't think it's possible to do what you have in mind. It's also important to remember that Windows will only mount the first partition of an SD card. It won't see any other partitions without 3rd party software installed.
Click to expand...
Click to collapse
The two partitions on the USB flash drive can be seen* in Windows without third-party software.
*I don't have an English Windows interface.
ze7zez said:
The two partitions on the USB flash drive can be seen* in Windows without third-party software.
*I don't have an English Windows interface.
Click to expand...
Click to collapse
I meant that it won't mount the second partition, although you can see it in Disk Manager.
blaacksheep said:
I meant that it won't mount the second partition, although you can see it in Disk Manager.
Click to expand...
Click to collapse
Windows 10 mounts both of these partitions, assigns them letters and you can use them (read and write).
ze7zez said:
Windows 10 mounts both of these partitions, assigns them letters and you can use them (read and write).
Click to expand...
Click to collapse
I stand corrected! Previous versions of Windows could not do that.
ze7zez said:
The two partitions on the USB flash drive can be seen* in Windows without third-party software.
*I don't have an English Windows interface.
Click to expand...
Click to collapse
Something strange in that attachment. Since when do Android SD cards have NTFS partitions? As far as I know, the internal storage partitions that Windows couldn't read were formated as Ext3 or Ext4 and the external as either FAT32 or exFAT.
lewmur said:
Something strange in that attachment. Since when do Android SD cards have NTFS partitions? As far as I know, the internal storage partitions that Windows couldn't read were formated as Ext3 or Ext4 and the external as either FAT32 or exFAT.
Click to expand...
Click to collapse
Don't suggest the volume label. Partition K: is FAT. The example shows that Windows can show two partitions on a USB stick.
ze7zez said:
Don't suggest the volume label. Partition K: is FAT. The example shows that Windows can show two partitions on a USB stick.
Click to expand...
Click to collapse
Of course it can. It can show several. But NOT the two partitions created on an Android SD card because one of then is formated in a file system Windows doesn't recognize and that is what the poster was talking about.
edit: Disk Manager will actually show the partition but it won't be assigned a drive letter because Windows can't mount it.