Groups | Search | Server Info | Login | Register
Groups > comp.mobile.android > #146652
| From | Marion <marion@facts.com> |
|---|---|
| Newsgroups | comp.mobile.android, alt.comp.os.windows-10, alt.comp.os.windows-11 |
| Subject | Windows format doesn't completely change sdcard volume name for Android use |
| Date | 2025-02-04 20:28 +0000 |
| Organization | BWH Usenet Archive (https://usenet.blueworldhosting.com) |
| Message-ID | <vntt95$2dfo$1@nnrp.usenet.blueworldhosting.com> (permalink) |
Cross-posted to 3 groups.
The more I do to improve efficiency between Android and Windows, and specifically to make inevitable porting of each completely seamless, the more I learn how complex it gets when you are dealing with sdcards. <https://i.postimg.cc/bNGTzR6q/sdcard1.jpg> When you mindlessly double your portable memory, you end up with the new filespec being different than the old filespec due to the new volume name. <https://i.postimg.cc/7YngGTV4/swapportablememory.jpg> In order to make seamless the doubling of sdcard portable memory, I have, for years, Windows-formatted the new volume label to match the old name. <https://i.postimg.cc/1XDSvStx/formatlabel.jpg> That clever little trick wonderfully enables the filespec for the new sdcard portable memory to be the same as the old for Android apps. <https://i.postimg.cc/QN6nY1H5/sdcard09.jpg> Even Windows calls uses the new volume name, which is nicely consistent such that paths to map data on Windows are the *same* as on Android. <https://i.postimg.cc/zD9P15FX/sdcard11.jpg> OsmAnd~ Windows confirmation <https://i.postimg.cc/ZK4pNMTx/sdcard12.jpg> OsmAnd~ Android confirmation With the result that doubling portable storage is entirely seamless to all your Windows/Android apps whether they be editors or maps or file managers. <https://i.postimg.cc/dtVcLJTR/sdcard10.jpg>> However... with all magic... comes complexity (of understanding)... In another thread, an offshoot revealed that even if you change the volume name (aka volume label) of your portable storage sdcard, while Android apps can use either the old volume name or the new volume name (apparently), the question is why didn't Windows format *completely* change the Volume Name? *Clever helpful suggestion for portable memory using Windows & Android editors* <https://www.novabbs.com/computers/article-flat.php?id=57086&group=comp.mobile.android#57086> As a result, Android file managers sometimes display only the new name: <https://i.postimg.cc/C1rkysfz/roundsync.jpg> And some Android file managers only display the old volume name: https://i.postimg.cc/0yvf0ZGs/zarchiver.jpg> Yet, more often than not, Android file managers display both volume names! <https://i.postimg.cc/v8z1hhKn/ghostcommander.jpg> <https://i.postimg.cc/26yLxLXm/mixexplorer.jpg> <https://i.postimg.cc/PqGS9TnB/owlfiles.jpg> Why? Does anyone know what is going on to explain the recent observations above? -- The whole point of Usenet is to find people who know more than we do and then to pool our collective resources to solve problems as a team.
Back to comp.mobile.android | Previous | Next — Next in thread | Find similar
Windows format doesn't completely change sdcard volume name for Android use Marion <marion@facts.com> - 2025-02-04 20:28 +0000 Re: Windows format doesn't completely change sdcard volume name for Android use "R.Wieser" <address@is.invalid> - 2025-02-04 21:53 +0100 Re: Windows format doesn't completely change sdcard volume name for Android use "Carlos E.R." <robin_listas@es.invalid> - 2025-02-04 23:44 +0100
csiph-web