XPost: comp.mobile.android, alt.comp.os.windows-10   
   From: robin_listas@es.invalid   
      
   On 2025-02-03 11:40, Marion wrote:   
   > On Sun, 2 Feb 2025 15:44:38 +0100, Janis Papanagnou wrote :   
   >   
   >   
   >> You again stirred my curiosity - since I don't know about the Android   
   >> and its file-editors peculiarities... - How does Android recognize the   
   >> path with the (arbitrary) "A1B1-C1D1" and "A2B2-C2D2" path components   
   >> but not a generic (a fixed) one?   
   >   
   > Well, I wish I understood why *some* Android file managers show those   
   > cryptic identifiers, and yet other Android file managers show '0000-0001'.   
   >   
   > There must be someone out there who understands why, but it's not me (yet).   
   >   
   > Take a look at these screenshots I made for you to illustrate the question.   
   >   
   > 0. We're starting with an sdcard which was formatted to 0000-0001   
   >    Then we test only the 1st 4 file managers in my homescreen "file' folder   
   >       
   >   
   > 2. Notice the first file manager (OwlFiles) shows both the cryptic label   
   >    and the user-defined label (for reasons completely unknown to me).   
   >       
   >   
   > 3. The second file manager (Round Sync) is completely fooled by the label!   
   >       
   >   
   > 4. The third file manager (Mix Explorer) is almost completely fooled.   
   >       
   >   
   > 5. The fourth file manager (ZArchiver) isn't fooled in the least.   
   >       
   >   
   > I wish I understood those results.   
   > But I don't.   
   >   
   > Does anyone?   
   >   
   > Why do some file managers show 0000-0001, while others show both, and yet,   
   > still others only show the cryptic volume label & not the 0000-0001?   
   >   
   > I openly admit that I'm befuddled by those results.   
   > Does someone know more about this than I do?   
   >   
   > If so, please explain why we're seeing what we're seeing above.   
   > That would add value for sure.   
      
   I suspect some are using the UUID. But I don't understand how different   
   file managers can show different results, it should be the operating   
   system who names things in an unique way. Maybe there are two different   
   trees and they can choose.   
      
   Maybe the file manager is mounting the card? Why? It should be already   
   mounted by Android.   
      
   It is a non issue for me, as I can no longer use cards on my phones.   
   Maybe on the next tablets.   
      
      
   Huh, the filemanager I use is Ghost Commander. Sorry, I can't find the   
   official name. Setup/Aplications does not list it, Play Store does not   
   list it, but I have just run it. Unless it has been renamed to Total   
   Commander.   
      
   Google finds a site:   
      
   https://sites.google.com/site/ghostcommander1/About   
      
   but I don't know if this site is faked.   
      
   Weird.   
      
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)