Transfer to new microsd produced files with leading "._" on them.

[migs_inc]

I have a Galaxy S10+ on Verizon and purchased a new 512GB microsd to replace the 256GG microsd I had been using. Both microsd's are from Samsung. I was advised by Verizon to simply use the card adapter to copy the complete disk to my Macbook Pro and then copy those files to the new microsd with the card adapter. Did that. However when I load the new microsd into the phone, the jpg (photo) files all have a prefix of "._" added to each file.

Interestingly, when I load the new microsd into my Macbook, the files do not show the "._" prefix. I do not have enough free internal storage on the phone to copy into that area and to the new card. How can I finalize this transfer?

 

[SpookDroid]

Sounds like a Mac 'issue' most likely. The method is pretty much what you would usually do, but not well versed enough on how Macs handle file copies or file extensions, only done that in a Windows computer. Is the data too much? If not, you can just copy everything onto the phone, then swap cards, and move things to the card again.

 

[bbgpsuser]

I would expect you to see 2 files, one with the "._" prefix and one without. The one with the "._" prefix is the resource fork that the Mac created for the file. You should be able to delete the "._" prefix files on your phone and just use the ones without the prefix. Of course make sure that you have a backup before you delete anything.

 

[Gayle Lynn]

You have "show invisible files"

Windows would show .DS_ on files you touch. Used for thumbnails and indexing

 

[Rukbat]

Try putting the 512GB card into the Mac (using the adapter), and the 256GB card into the phone. Delete everything from the 512GB card. Connect the phone to the Mac, then drag all the folders from the 256GB card to the 512GB card. If that doesn't do it, you'll have to find someone with a Windows (yes - Windows doesn't play games with *nix filesytem files) PC and do that on the Windows machine.

. is *nix for "hidden". ._ is the resource fork - but the picture for the jpg files might have ended up in the resource fork, not the .jpg file. (Which is why Windows is better for this - it has no resource fork, it "hides" files by setting flags in the directory entry for the file - which doesn't get copied over. Sometimes it's better to have an OS that doesn't understand how the other OS [and both Mac and Android run on *nix] works, so it just copies the files.)

 

[Gayle Lynn]

Depending what the source of a photo is, and maybe any file, I see "-iOS" appended to files automatically - which I strongly detest.