You explained it fine.
It's possible to move any files to the SD card, but please don't. Use Copy instead then, if the copy was successful, delete the original. (If a Move goes bad in the middle, you can lose both the original and the copy. If a copy goes bad, all you lose is the copy and you can copy it again.)
As I said, though - files. Not apps. Pictures, videos, music, tones (ringtones, notification tones, alarm tones), documents, any files. "Moving" apps to the SD card doesn't, it moves pieces of the app and leaves a link to each piece in internal storage (because that's where Android looks for them), so it saves you almost nothing. And, since Android apps have to keep their current state at all times (because if the app is running in the background and Android needs the RAM it's taking, Android just kills it. When you bring that killed app to the foreground again, Android loads it into RAM and tells it to start where it left off. To you it appears that the app was always running, waiting for you to get back to it.) The problem is that while eMMC (internal) storage is designed to take constant writing, SD storage isn't. It's designed for "write once, read many", because it's rated in number of writes. So if you move a fast action game to the SD card, it's going to be writing to the card almost constantly - and the card will fail a lot sooner than it should.
So keep things you move to the card to those things that you may read 5 times a day (my list of medications is like that - I almost never change the list, but it gets put up on the screen every time I go to a doctor - and at 77, that's often. A video you're going to watch many times, pictures you're going to look at many times, things like that are fine. Just no apps. (And some apps won't run from the SD card, so the developer has turned off the "Move to SD card" function, so you can'tmove it to the card.)
06-14-2019 05:56 PM
