XPost: comp.mobile.android, alt.comp.os.windows-10
From: marion@facts.com
On Tue, 4 Feb 2025 13:22:53 +0100, Carlos E.R. wrote :
>> BTW, my version of Ghost Commander is v1.62.3 and when I click on the Help
>> from inside of that app, it takes me to that URL so it's legitimate.
>>
>
> I wondered, because it is full of things about the war in Ukraine.
> Photos of the app are gone.
Hi Carlos,
Yes, I agree. It's funny looking. Both the URL & that political web page.
But you don't even need that page since the Sourceforge link has the APK.
>> What I do NOT understand is why I see *both* the 0000-0001 that Windows
>> formatted and a crytic AAAA-BBBB style identifier (which I can presume was
>> the original label name).
>
> No, that's probably the UUID.
Well, I have no idea what it is, but looking up the format of a UUID,
apparently the Universally Unique Identifier is a 128-bit number.
UUIDs are typically displayed as a 36-character string, divided into five
sections separated by hyphens, e.g., f43ca10b-68dc-4372-d567-0b02f2a3d48f
Maybe it's a shortened UUID, but it looks suspiciously like a default
volume name (aka volume label); but I didn't write down the original name.
The question would be how to list out the UUID on Android or Windows?
>> How can there be two volume labels to the same sdcard in Android?
>>
Googling, it seems sdcards don't have UUIDs anyway as they have the Card
Identification (CID) register (which we've discussed prior in this thread).
That CID register is a 128-bit code includes the card serial number,
manufacturer ID, and manufacturing date (plus a checksum).
CID Structure (128 bits total)
Manufacturer ID (MID): 8 bits - (e.g., SanDisk, Kingston)
OEM/Application ID (OID): 16 bits - OEM or application
Product Name (PNM): 5-character ASCII string for the product name
Product Revision (PRV): 8 bits for the product revision number
Product Serial Number (PSN): 32 bits - A unique serial number
Manufacturing Date (MDT): 12 bits - year & month of manufacture
CRC7 checksum: 7 bits - Used for error detection
Here is an example CID in hex that I found by searching for data.
03 53 44 53 55 30 34 47 10 0B 75 BC D0 23 8A
Here is what that manually translates into:
Manufacturer: SanDisk (MID: 0x03)
OEM/Application ID: SD (OID: 0x5344)
Product Name: SU04G (PNM: 0x5355303447)
Product Revision: 1.0 (PRV: 0x10)
Serial Number: 12345678 (PSN: 0x0B75BCD0)
Manufacturing Date: August 2023 (MDT: 0x238)
CRC7 Checksum: 10 in decimal (CRC: 0X67)
I think the number shown by Android is sufficiently different so as not to
likely be the CID, but more likely to be the original Volume Label instead.
The problem is two fold, of course, in UNDERSTANDING what is going on.
a. Why didn't Windows sufficiently wipe out the old volume name?
b. Why do some Android apps display one, or the other, or both names?
Luckily, the $EDITORS on Android don't seem to have a problem using the
Windows-assigned volume name (aka volume label); but it's an enigma.
The enigma to resolve is nobody (yet) seems to know how Windows works in
terms of changing the volume name (aka volume label), least of all me;
likewise, with Android that nobody (yet) knows why this is happening, least
of all me. I hate when I don't understand something. That irks me a lot.
But it's likely there isn't an expert on this newsgroup who knows why.
I'll ask on the forums why Android file managers display two volume names.
Thanks for your help (and for the help of others who valiantly tried).
--- SoupGate-DOS v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
