• Re: Android 6 internal vs SD storage

    From micky@3:633/10 to All on Saturday, August 15, 2026 10:23:59
    In comp.mobile.android, on Sat, 15 Aug 2026 09:34:36 +0100, Nuno Silva <nunojsilva@invalid.invalid> wrote:

    On 2026-08-15, micky wrote:

    In comp.mobile.android, on Fri, 14 Aug 2026 20:33:21 -0500, VanguardLH
    <V@nguard.LH> wrote:

    Mike Easter <MikeE@ster.invalid> wrote:

    I do not use cell phones conventionally; I don't carry a phone, I don't >>>> normally even turn a phone on. I just now subscribed to this group to >>>> ask a question, but I haven't read any recent msg threads here.

    I have an old cellphone w/ Android 6 and no cell plan which I use for >>>> various purposes via wifi, camera, & music. I have a newer tablet phone >>>> which does have a plan which I use occasionally via wifi.

    I am fairly ignorant of navigating my old cellphone's features, which is >>>> why I'm here now.

    Whenever I start the phone, I'm informed about how low the 8G internal >>>> storage is. I only recently changed the settings to use the 32G SD card >>>> by default instead of internal.

    My problem is that I can't find a way to 'get rid of' any data in
    internal storage that is causing my low storage condition.

    The online advice I've found hasn't been helpful to me.

    My guess is you are asking about the Adoptive Storage feature. Once you >>>adopt the SD card to augment your phone's internal storage, everything

    Are SD cards always adopted like this, or acn they be used without
    encryption and locking?

    Storage cards can definitely be used without encryption, and, at least
    on Android 4.2, can also be used to store installed apps without >filesystem-wide encryption (if there is some encryption, it's localized
    to the relevant files).

    on the SD card is erased, and it gets encrypted to lock that SD card to >>>that phone. If you ever want to use the SD card elsewhere, you will
    have to un-adopt the SD card which formats it. Adoption is destructive >>>when you want to enable it, and when you want to release it.

    Yeah, I jumped to conclusions even to ask the question.

    I posted prematurely, because Vanguard's post seemed like an magically well-timed answer to my problem.

    This morning, I looked at the 30 jpegs and one video that I had copied,
    the 4%, and all that I tried opened fine. So I guess the card was never adopted or encrypted at all. (Good, since I didn't think I did that.)
    The video seemed out of order no matter what sort order I imagined, but
    it had been copied too and it played.

    Then I started where it left off to copy the rest. It got through 38%
    of the files and then just stopped again, no messsage. Had to use Task
    Manager and another box to close the file manager.

    Properties has all along said the SD card has no errors, but when I try
    to repair it anyhow, it says it can't.

    Now, I can display the top level directory items, but when using an after-market file manager, PowerDEsk, I try to open any of the
    directories one level down, the file manager repositions at "PC" or some
    high place unrelated to the SD card. When I use the MS file manager,
    this doesn't happen unless I try to open DCIM, which is where the photos
    are, but it happens that way when I try to open DCIM. (Inside that is
    Camera, and that has the photos. It used to open but now doesn't even
    though I never tried to write to it. I only read, and it copied 38+4%
    of the files.)

    I will look into ddrescue that you mention, but I'm not optimistic.

    It sounds like a) either I should do a complete formatting, not a quick
    one, or b) I should throw the card away and start over.

    (I read the rest of your post too. Thanks for the good info.)


    When I have time, I reed every post in the android group, and the
    windows and firefox groups.

    But I never have eough time anymore to do that and I just red this
    thread because it was next, and by golly, it relates to a question I was
    working on.

    I have other copies of the pictures but I still wanted to copy the ones
    on the SD card from my BROKEN phone (in case by some miracle they
    weren't the same as the ones from the same dates that I already have). I
    couldn't open the few I tried to oprn and when I tried to copy all 9
    gigs in win10, it did 4% and stopped with no message. I was going to
    work on it some more later. But now I know why.

    Are you certain that the card itself is OK hardware-wise and has no
    errors in the filesystem? If not, you may be better off copying with >something like ddrescue. (No idea what's available for Windows NT.)

    For the record and assuming I didn't have 3 other copies, is there a way
    to unencrypt the files so I can still see my photos?

    If it's time-consuming or impossible, I'll just reformat the 64GB SD
    card to exFAT, right? Is quick-format good enough?

    My two cents would be: don't do that unless you're entirely sure it
    can't be recoveded.

    All of this, and especially if the files are irrecoverable, lowers the
    value of an SD card, not completely but somewhat, of course, for those
    in the previous thread who say it's of no value. I had thought
    otherwise, that it would be like the harddrive in a computer, easily
    available after the computer failed***.

    Hard drives can be encrypted too. Although I think that's mainly used
    with user-supplied passphrases, I'd not be surprised if the DRM in TPM
    and "Secure computing" allowed for a similar thing.

    I should also mention that, though the phone created a data subdirectory
    for every app, all 220, and some of them had multiple subdirectories, it
    took me a long time to check but none except for the photo/video
    directory had more than 2 files, both under 100 bytes. So only the
    photos were saved there and only after I set some setting to save to the
    SD card, for fear internal storage would fill up.

    Of course the external storage is no worse than the internal storage
    here, because it will be hard and probably impossible to get anything
    out of internal storage now that the phone is broken. It's not like a
    computer , is it, where you can open it up and take out the storage, or
    is it?

    ***Why *do* they encrypt the SD card and lock it to the phone? If they
    didn't, it would be more useful after the phone failed.

    So that data cannot be extracted without permission? And perhaps to
    enforce non-rooted Android limitations too... (so this one would
    definitely be DRM too).

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Mike Easter@3:633/10 to All on Saturday, August 15, 2026 09:54:34
    Nuno Silva wrote:
    ... wait, are we talking*non-volatile* data*storage* or RAM?

    Sorry; I was smearing it all together, 'confusingly'.

    The phone in question has 1G (0.94) ram, 8G (6.52 used) internal storage
    + 32G (1.2 used) SD card.

    Booted, now the phone has 250 meg ram free and 1.5G internal storage available, and almost all of the SD card's.

    --
    Mike Easter

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Carlos E. R.@3:633/10 to All on Saturday, August 15, 2026 19:25:44
    On 2026-08-15 16:23, micky wrote:
    In comp.mobile.android, on Sat, 15 Aug 2026 09:34:36 +0100, Nuno Silva <nunojsilva@invalid.invalid> wrote:


    Properties has all along said the SD card has no errors, but when I try
    to repair it anyhow, it says it can't.

    Now, I can display the top level directory items, but when using an after-market file manager, PowerDEsk, I try to open any of the
    directories one level down, the file manager repositions at "PC" or some
    high place unrelated to the SD card. When I use the MS file manager,
    this doesn't happen unless I try to open DCIM, which is where the photos
    are, but it happens that way when I try to open DCIM. (Inside that is
    Camera, and that has the photos. It used to open but now doesn't even
    though I never tried to write to it. I only read, and it copied 38+4%
    of the files.)

    I will look into ddrescue that you mention, but I'm not optimistic.

    ddrescue does no repair. It simply copies a disk or partition to another place, even if it finds errors when reading it.

    For instance, the other day I tried to recover deleted photos on a card. First I cloned the card with 'dd', then I recovered the photos with PhotoRec (Linux), working on the image, instead of the card.

    From my notes:

    SystemRescueCd http://www.system-rescue-cd.org/

    PhotoRec recovers files from deleted memory cards (from cameras). 12 April 2009
    http://www.cgsecurity.org/wiki/PhotoRec
    f3 http://oss.digirati.com.br/f3/ recovers/analyses USB sticks.



    --
    Cheers,
    Carlos E.R.
    ES??, EU??.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From s|b@3:633/10 to All on Saturday, August 15, 2026 19:48:16
    On Fri, 14 Aug 2026 15:23:57 -0700, Mike Easter wrote:

    My problem is that I can't find a way to 'get rid of' any data in
    internal storage that is causing my low storage condition.

    Can you see 'Storage' somewhere in the menu? It's possible your OS is
    using most of it. I've seen this before on older smartphones.

    What phone are we talking about?

    --
    s|b

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Mike Easter@3:633/10 to All on Saturday, August 15, 2026 11:48:03
    s|b wrote:
    Mike Easter wrote:

    My problem is that I can't find a way to 'get rid of' any data in
    internal storage that is causing my low storage condition.

    Can you see 'Storage' somewhere in the menu? It's possible your OS is
    using most of it. I've seen this before on older smartphones.

    Yes I can see storage; but as I examine the various dir/s, I'm not
    finding anything that is 'mine'.

    What phone are we talking about?

    BLU Grand Energy; I read that it was released in '17.

    https://www.bluproducts.com/devices/grand-energy/index.html

    Tech is near/at the bottom of the page full of pretty pictures :-)

    Technology
    Android v6.0 Marshmallow
    GSM Quad Band
    3G: HSPA +21Mbps
    3G 850/1700/1900/2100
    3G 850/900/1900/2100

    Display
    5.0" HD 720x1280 ~294ppi
    Curved Glass

    Camera
    5MP Main w/Flash
    5MP Front w/Flash
    HD 1080p@30fps

    Processor
    MediaTek 6580
    1.3GHz Quad Core
    With Mali-400 GPU

    Memory
    Internal 8GB | 1GB RAM
    MicroSD up to 32GB

    Battery
    4000mAh

    Connectivity
    Bluetooth 4.0
    Wi-Fi, Hotspot
    Micro USB v2.0


    --
    Mike Easter

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Nuno Silva@3:633/10 to All on Sunday, August 16, 2026 01:14:50
    On 2026-08-15, Carlos E. R. wrote:

    On 2026-08-15 16:23, micky wrote:
    In comp.mobile.android, on Sat, 15 Aug 2026 09:34:36 +0100, Nuno Silva
    <nunojsilva@invalid.invalid> wrote:


    Properties has all along said the SD card has no errors, but when I try
    to repair it anyhow, it says it can't.

    Now, I can display the top level directory items, but when using an
    after-market file manager, PowerDEsk, I try to open any of the
    directories one level down, the file manager repositions at "PC" or some
    high place unrelated to the SD card. When I use the MS file manager,
    this doesn't happen unless I try to open DCIM, which is where the photos
    are, but it happens that way when I try to open DCIM. (Inside that is
    Camera, and that has the photos. It used to open but now doesn't even
    though I never tried to write to it. I only read, and it copied 38+4%
    of the files.)

    I will look into ddrescue that you mention, but I'm not optimistic.

    ddrescue does no repair. It simply copies a disk or partition to
    another place, even if it finds errors when reading it.

    Yes, but it is tailored for media with errors or reading difficulties,
    and will let you know if there *are* errors.

    For instance, the other day I tried to recover deleted photos on a
    card. First I cloned the card with 'dd', then I recovered the photos
    with PhotoRec (Linux), working on the image, instead of the card.

    Yeah, just for undeletion in a healthy medium, ddrescue isn't necessary, although one might feel tempted just to get its progress display.


    From my notes:

    SystemRescueCd http://www.system-rescue-cd.org/

    PhotoRec recovers files from deleted memory cards (from cameras). 12 April 2009
    http://www.cgsecurity.org/wiki/PhotoRec
    f3 http://oss.digirati.com.br/f3/ recovers/analyses USB sticks.

    --
    Nuno Silva

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Carlos E. R.@3:633/10 to All on Sunday, August 16, 2026 11:06:24
    On 2026-08-16 02:14, Nuno Silva wrote:
    On 2026-08-15, Carlos E. R. wrote:

    On 2026-08-15 16:23, micky wrote:
    In comp.mobile.android, on Sat, 15 Aug 2026 09:34:36 +0100, Nuno Silva
    <nunojsilva@invalid.invalid> wrote:


    Properties has all along said the SD card has no errors, but when I try
    to repair it anyhow, it says it can't.

    Now, I can display the top level directory items, but when using an
    after-market file manager, PowerDEsk, I try to open any of the
    directories one level down, the file manager repositions at "PC" or some >>> high place unrelated to the SD card. When I use the MS file manager,
    this doesn't happen unless I try to open DCIM, which is where the photos >>> are, but it happens that way when I try to open DCIM. (Inside that is
    Camera, and that has the photos. It used to open but now doesn't even
    though I never tried to write to it. I only read, and it copied 38+4%
    of the files.)

    I will look into ddrescue that you mention, but I'm not optimistic.

    ddrescue does no repair. It simply copies a disk or partition to
    another place, even if it finds errors when reading it.

    Yes, but it is tailored for media with errors or reading difficulties,
    and will let you know if there *are* errors.

    Ok, yes.

    ...

    --
    Cheers,
    Carlos E.R.
    ES??, EU??.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From micky@3:633/10 to All on Sunday, August 16, 2026 11:52:56


    This post is relevant to win10 and 11 .


    In comp.mobile.android, on Sun, 16 Aug 2026 01:14:50 +0100, Nuno Silva <nunojsilva@invalid.invalid> wrote:

    On 2026-08-15, Carlos E. R. wrote:

    On 2026-08-15 16:23, micky wrote:
    In comp.mobile.android, on Sat, 15 Aug 2026 09:34:36 +0100, Nuno Silva
    <nunojsilva@invalid.invalid> wrote:


    Properties has all along said the SD card has no errors, but when I try
    to repair it anyhow, it says it can't.

    Now, I can display the top level directory items, but when using an
    after-market file manager, PowerDEsk, I try to open any of the
    directories one level down, the file manager repositions at "PC" or some >>> high place unrelated to the SD card. When I use the MS file manager,
    this doesn't happen unless I try to open DCIM, which is where the photos >>> are, but it happens that way when I try to open DCIM. (Inside that is
    Camera, and that has the photos. It used to open but now doesn't even
    though I never tried to write to it. I only read, and it copied 38+4%
    of the files.)

    I will look into ddrescue that you mention, but I'm not optimistic.

    ddrescue does no repair. It simply copies a disk or partition to
    another place, even if it finds errors when reading it.

    Yes, but it is tailored for media with errors or reading difficulties,
    and will let you know if there *are* errors.

    For instance, the other day I tried to recover deleted photos on a
    card. First I cloned the card with 'dd', then I recovered the photos
    with PhotoRec (Linux), working on the image, instead of the card.

    Yeah, just for undeletion in a healthy medium, ddrescue isn't necessary, >although one might feel tempted just to get its progress display.


    From my notes:

    SystemRescueCd http://www.system-rescue-cd.org/

    PhotoRec recovers files from deleted memory cards (from cameras). 12 April 2009
    http://www.cgsecurity.org/wiki/PhotoRec
    f3 http://oss.digirati.com.br/f3/ recovers/analyses USB sticks.

    Just for a follow-up. Use of windows 10 (because that box has a
    full-size SD card reader in the front and the win11 only has a tiny slot
    in the side hard to get to since my breakfast table is covered with
    junk), use of win10 to copy the files was erratic, to put it mildly.

    Would win11 work better for this troublesome copying?

    I usually use PowerDesk but the only free copy is quite old now. I
    thought when I right clicked and did Properties, it would use the same Properties program that MS File Explorer used, but the MS version has
    too more tabs!!!! Hardware and one other. Maybe something about
    PowerDesk means it can't implement those two tabs, can't relay the
    information?

    Anyhow, as I said, with Powerdesk I would go to the SD card, go to DCIM,
    go to Camera, and then open all the photos and videos, and then it would reposition at This PC. So I tried the MS file explorer.

    Same thing, but after 5 times, the sixth time it didn't. One time
    stopped at the same 4% but continued a couple minutes later (a previous
    and a later time I waited for an hour and it just stayed at 4%.

    One time it made it to 50%. I would just copy what's left, but more
    likely to freeze the window or reposition at This PC if I try to list
    them. More failures, reboot windows, more failures.

    One time only it said Cannot copy filename, and offered to skip it, but
    like a fool I clicked on Retry. And it just froze, never offered to
    skip it again.

    All when I think I have 3 other copies of all these pictures.

    So I decide to format, and it refuses to do a non-quick format. I do a
    quick format and then it is wiling to do a non-quick format, which it
    does at the appropriate slow pace.


    But I think I'd be a fool to rely on this SD card, right? I know
    formating is supposed to find all the bad spots, and list their
    locations so they are not used, but would you guys use this SD card for anything important?

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Sunday, August 16, 2026 13:13:58
    On Sun, 8/16/2026 11:52 AM, micky wrote:

    But I think I'd be a fool to rely on this SD card, right? I know
    formating is supposed to find all the bad spots, and list their
    locations so they are not used, but would you guys use this SD card for anything important?

    You have to know how a device works under the hood, to be
    using trash-bunny techniques on it. Is it direct mapped, and
    you can burn spots into it, or, is it "wear leveled static&dynamic".

    https://www.reddit.com/r/raspberry_pi/comments/ex7dvo/quick_reminder_that_sd_cards_with_wearleveling/

    A lot of trash-bunny techniques, result in writes to a device.
    It it is already on its way out, and in a spiral-of-death,
    the activities might actually be accelerating the end of
    the device.

    As for the article, we've been baited before by all this talk
    of wear leveling, and the game continues. It's hard to say
    whether any quality TLC flash devices exist, as that's what
    these pieces of shit will be made of. I looked at my computer
    store listing, and you can't buy an 8GB MLC based one any more,
    they're going to all be TLC or QLC. And they won't
    actually tell you what kind of flash is in an SD.
    "Buying new is not necessarily buying better"
    Some of the older SD cards, are going to last longer.
    Just because of the flash type.

    This makes a good hobby though, and is slightly ahead of
    stamp collecting. And as that Reddit thread shows, it has the
    same amount of drama, for sure (the "talking with engineering" schtick
    the tech support carried out). Companies and their tech support,
    it's highly likely they don't even make the product themselves,
    and it arrives in big burlap bags and they put their brand
    sticker on it.

    Summary: If you device isn't healthy... don't use it.

    Paul


    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From micky@3:633/10 to All on Sunday, August 16, 2026 21:26:39
    In comp.mobile.android, on Sun, 16 Aug 2026 13:13:58 -0400, Paul <nospam@needed.invalid> wrote:

    On Sun, 8/16/2026 11:52 AM, micky wrote:

    But I think I'd be a fool to rely on this SD card, right? I know
    formating is supposed to find all the bad spots, and list their
    locations so they are not used, but would you guys use this SD card for
    anything important?

    You have to know how a device works under the hood, to be
    using trash-bunny techniques on it. Is it direct mapped, and
    you can burn spots into it, or, is it "wear leveled static&dynamic".

    https://www.reddit.com/r/raspberry_pi/comments/ex7dvo/quick_reminder_that_sd_cards_with_wearleveling/

    A lot of trash-bunny techniques, result in writes to a device.
    It it is already on its way out, and in a spiral-of-death,
    the activities might actually be accelerating the end of
    the device.

    As for the article, we've been baited before by all this talk
    of wear leveling, and the game continues. It's hard to say
    whether any quality TLC flash devices exist, as that's what
    these pieces of shit will be made of. I looked at my computer
    store listing, and you can't buy an 8GB MLC based one any more,
    they're going to all be TLC or QLC. And they won't
    actually tell you what kind of flash is in an SD.
    "Buying new is not necessarily buying better"
    Some of the older SD cards, are going to last longer.
    Just because of the flash type.

    This makes a good hobby though, and is slightly ahead of
    stamp collecting. And as that Reddit thread shows, it has the
    same amount of drama, for sure (the "talking with engineering" schtick
    the tech support carried out). Companies and their tech support,
    it's highly likely they don't even make the product themselves,
    and it arrives in big burlap bags and they put their brand
    sticker on it.

    Summary: If you device isn't healthy... don't use it.

    I didn't understand most of what you wrote, but I bought a new SD card.
    4x as big, too.

    Months ago you gave a suggestion in the android group, to turn off
    gestures so that my phone woldn't light up when putting it in my pocket.
    I'm positive I had done that but I checked and it wasn't set that way,
    so I set it and was waiting for results to tell you if it worked or not.
    At firs it seemed to say yes, but later results were a little mixed. And
    of course now the phone is dead, so it will never be known for sure.

    Even though I figured Xiaomi fixed the problem in the 7 years since the
    last phone, it was still a factor in my being ready to buy a different
    brand.

    The last phone's screen turned on when I didn't want it to, and turned
    off when it was plugged into the car charger, even when I was looking at
    a map and wanted it on all the time. It did not turn off when I was
    folling the map's directions, but that was not enough. I installed a
    couple apps that said it would keep the screen on, one that went by app
    (and I set it for all the map apps) but it didnt' work either. :-)
    Hard to write for so many different implementations.

    If the new phone fixes one of these, it will be an improvement. If both
    of them, it will be miraculous.


    Paul

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Sunday, August 16, 2026 23:19:09
    On Sun, 8/16/2026 9:26 PM, micky wrote:
    In comp.mobile.android, on Sun, 16 Aug 2026 13:13:58 -0400, Paul <nospam@needed.invalid> wrote:

    On Sun, 8/16/2026 11:52 AM, micky wrote:

    But I think I'd be a fool to rely on this SD card, right? I know
    formating is supposed to find all the bad spots, and list their
    locations so they are not used, but would you guys use this SD card for
    anything important?

    https://www.reddit.com/r/raspberry_pi/comments/ex7dvo/quick_reminder_that_sd_cards_with_wearleveling/>>
    Summary: If you device isn't healthy... don't use it.

    I didn't understand most of what you wrote, but I bought a new SD card.
    4x as big, too.

    The Reddit thread, mentions an SD Association utility for
    working on an SD. The people in the thread claim, it
    "changes the device capacity", which means a block of flash
    is getting disabled, or there is some mechanism other
    than $BADCLUS, for marking off bits of the device.

    But if one section of device fails, what condition are
    the other sections in ? Should we take a chance on that ?

    It is the same chance we take, when moving a partition
    on a hard drive, to the "unworn" part of the disk. Is
    that a good idea ? There, you rely on your field
    statistics. Drives can hold on for a good long time,
    and if you are babying the device, you can actually
    note the thing going downhill. (For example, I could
    see 300 reallocations after a major data change on the disk.)
    You can stop using the device, if you know when it is
    going to cut out. I actually followed a hard drive
    downhill, until its functional status changed. If
    the reallocated max is 5500 sectors, the device stops
    working at exactly half that number. You're not
    allowed to do any more writes to the disk, once
    it gets to half of that number. You don't actually
    have 5500 to burn up. And I ruined a device on purpose,
    to get that information.

    If you're using a storage device, and the behavior
    is known, maybe you can "use them up" like that, and
    transfer off just before they crash for good.

    If on the other hand, there isn't enough data to tell
    you how the thing is working, then replacing it promptly
    is also an option.

    If you buy one with Wear Leveling, it should last a lot
    longer. The SD is unlikely to have a TRIM command, so
    this means the internal TRIMming is done by some other
    (not as good) technique. That's also a feature of SSDs.
    If your OS does not send TRIM commands, that's OK,
    as the device has a fall back it uses internally.

    600 590 580 585 590 Average about ~585 or so, of write cycles
    blk blk blk blk blk Maybe weekly TRIM helps with this

    600 550 575 565 590 Maybe the average is a bit lower...
    blk blk blk blk blk when the internal mechanism is used

    600 is a location that is "worn out" (600 write cycles).

    The other locations are less worn. If we discarded the second
    device there, the 550 location, we have 50 writes remaining for that
    block (that's if the device would even talk to us, the assumption is
    that it has stopped working).

    TRIM uses knowledge of where actual files are stored, to "tell"
    the storage device, which locations do not require flash backing and
    can go back into the "free pool" of blocks.

    When the internal mechanism is used, and no TRIM commands
    tell the drive the situation, the drive can still manage some
    amount of leveling, just not as good as with TRIM.

    Without any wear leveling at all, if you keep writing the
    MBR sector over and over and over again, the MBR fails first,
    and gobs of potential write capability are thrown away when
    the device is tossed in the garbage. That's how my
    dead USB sticks treated me. A spot burned into them apparently,
    and the devices, unrecoverable. A $3 stick, does not wear level.

    Paul





    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Steve Hayes@3:633/10 to All on Monday, August 17, 2026 08:32:57
    On Fri, 14 Aug 2026 22:37:01 -0400, micky <NONONOmisc07@fmguy.com>
    wrote:

    In comp.mobile.android, on Fri, 14 Aug 2026 20:33:21 -0500, VanguardLH ><V@nguard.LH> wrote:

    Mike Easter <MikeE@ster.invalid> wrote:

    I do not use cell phones conventionally; I don't carry a phone, I don't >>> normally even turn a phone on. I just now subscribed to this group to
    ask a question, but I haven't read any recent msg threads here.

    I have an old cellphone w/ Android 6 and no cell plan which I use for
    various purposes via wifi, camera, & music. I have a newer tablet phone >>> which does have a plan which I use occasionally via wifi.

    I am fairly ignorant of navigating my old cellphone's features, which is >>> why I'm here now.

    Whenever I start the phone, I'm informed about how low the 8G internal
    storage is. I only recently changed the settings to use the 32G SD card >>> by default instead of internal.

    My problem is that I can't find a way to 'get rid of' any data in
    internal storage that is causing my low storage condition.

    The online advice I've found hasn't been helpful to me.

    My guess is you are asking about the Adoptive Storage feature. Once you >>adopt the SD card to augment your phone's internal storage, everything

    Are SD cards always adopted like this, or acn they be used without
    encryption and locking?

    I've never "adopted" a card like this, and always used them for data
    storage, which I can copy to computers etc.

    My first Android phone had 1Gb of main storage, and soon ran out of
    space for photos, sound recordings etc.



    --
    Steve Hayes from Tshwane, South Africa
    Web: http://www.khanya.org.za/stevesig.htm
    Blog: http://methodius.blogspot.com
    E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From s|b@3:633/10 to All on Wednesday, August 19, 2026 19:49:10
    On Sat, 15 Aug 2026 11:48:03 -0700, Mike Easter wrote:

    s|b wrote:

    Can you see 'Storage' somewhere in the menu? It's possible your OS is
    using most of it. I've seen this before on older smartphones.

    Yes I can see storage; but as I examine the various dir/s, I'm not
    finding anything that is 'mine'.

    Is it possible the storage, OS and apps, is just "full". I've seen this
    on older phones. Maybe the OS doesn't change much, but apps get larger
    and larger. Only solution, in those cases, was to buy a new one.

    What phone are we talking about?

    BLU Grand Energy; I read that it was released in '17.

    https://www.bluproducts.com/devices/grand-energy/index.html

    Tech is near/at the bottom of the page full of pretty pictures :-)

    Ah, I can see it on gsmarena.com: <https://www.gsmarena.com/blu_grand_energy-8556.php>

    9 years. That's not too bad.

    --
    s|b

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)