• Re: Is it true there isn't a single one combined TRASH on Android?

    From Arno Welzel@usenet@arnowelzel.de to comp.mobile.android on Tue Oct 20 12:34:25 2026
    From Newsgroup: comp.mobile.android

    Wendelin Uez, 2026-10-12 14:32:

    Because, there is no concept of a "filesystem" for apps.

    Miracle of miracles, then I must have a special version of Android because mine is full of files.

    I talk about how apps access these files.

    <https://developer.android.com/guide/topics/providers/document-provider>

    Of course Android uses a real filesystem, but it has no central recycle bin like Windows. In Android, each app must provide its own one, but most apps do not need to manage one. Apps dealing with files like Samsungs's file manager often provide one.

    Even the file manager does not use a "filesystem", but only storage
    providers. And if every "file" is only a storage object with an UUID
    what should a "trash can" then store? Or do you expect very SAF storage provider to bring its own "trash can" interface and a documented way,
    how apps can access it?

    In Windows, deleting a file simply means to move its system record into recycle bin, and Windows can restore the file by moving back this record. In Android, a deleted file might immediately be overwritten by other data if the deleting app does not manage recycling.

    Even in Windows the recycle bin is *not* used, when you access a remote
    file systems on a NAS - even when which is available as "drive".

    Seen from an app in Android, every file is just a storage object and not
    some file on some "local drive".
    --
    Arno Welzel
    https://arnowelzel.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.mobile.android on Wed Oct 21 00:42:24 2026
    From Newsgroup: comp.mobile.android

    Arno Welzel wrote:
    Even in Windows the recycle bin is *not* used, when you access a remote
    file systems on a NAS - even when which is available as "drive".

    I always wondered about using Windows to delete a file on Android when
    mounted with MTP over Wi-Fi (or USB).

    How does *that* work with respect to trash.
    (Whose trash?)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.mobile.android,alt.comp.os.windows-10 on Wed Oct 21 12:25:28 2026
    From Newsgroup: comp.mobile.android

    Maria Sophia wrote:
    Even in Windows the recycle bin is *not* used, when you access a remote
    file systems on a NAS - even when which is available as "drive".

    I always wondered about using Windows to delete a file on Android when mounted with MTP over Wi-Fi (or USB).

    How does *that* work with respect to trash.
    (Whose trash?)

    Looking it up, when we delete an Android file from Windows File Explorer
    over MTP, Windows is the initiator. It sends DeleteObject to the device.

    The Android device's MTP responder does the actual filesystem work.

    Windows' Recycle Bin is not involved because its NTFS-driver machinery is
    not involved, so there's nothing to rename into the Windows recycle bin.

    And, depending on the Android version, most likely it's not there either.
    It's likely gone.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.mobile.android on Fri Oct 23 17:42:13 2026
    From Newsgroup: comp.mobile.android

    Andy Burns wrote:
    Frank Slootweg wrote:
    For example on Samsung phones, these days the 'Messages' app is the
    Google - not Samsung - version. And when you delete a SMS ('text')
    message from this app, it says 'This action cannot be undone.', so it
    does *not* use the My Files app -> Trash.

    That's interesting. On Googol Messages on my Pixel phone, I can hit
    the trash can after selecting one or more messages, and I get the
    delete confirmation prompt warning that the delete can't be undone.
    But if I hit the 3 dots without selecting particular messages and
    select Trash, I get a confirmation message that the whole chat will
    be moved deleted after 30 days if I select Move to Trash.

    Same here ... delete a single message and it warns that it'll be gone
    with no way back, but delete an entire conversation and you can get it back.

    But I'd never expect that deleted SMS would share a common bin with
    deleted files, why would they?

    I'm cleaning up my phone so that I can install WhatsApp (as my 128GB sd card was
    given to my wife (long story) so I'm out of space on the 64GB internal storage).

    Cleaning out trash can be done, apparently, from adb.
    But it wasn't enough, in my case, so I had to delete actual files too.

    adb shell df -h /data
    Filesystem Size Used Avail Use% Mounted on
    /dev/block/dm-47 50G 49G 413M 100% /data/user/0

    adb shell rm -rf /storage/emulated/0/.Trash-1000
    adb reboot

    adb shell df -h /data
    Filesystem Size Used Avail Use% Mounted on
    /dev/block/dm-47 50G 49G 449M 100% /data/user/0

    adb shell rm -rf /storage/emulated/0/Trash

    adb shell df -h /data
    Filesystem Size Used Avail Use% Mounted on
    /dev/block/dm-47 50G 49G 449M 100% /data/user/0

    adb shell rm -rf /storage/emulated/0/Android/data/com.android.providers.media/cache/*

    adb shell df -h /data
    Filesystem Size Used Avail Use% Mounted on
    /dev/block/dm-47 50G 49G 449M 100% /data/user/0

    adb shell "find /storage/emulated/0 -type f -size +10M -exec ls -l {} \; 2>/dev/null | sort -k5 -rn"

    adb shell rm -rf /storage/emulated/0/.fvTrash
    adb shell df -h /data
    Filesystem Size Used Avail Use% Mounted on
    /dev/block/dm-47 50G 49G 804M 99% /data/user/0

    adb shell rm /storage/emulated/0/Android/data/net.osmand.plus/files/Us_california_los-angeles_northamerica.obf
    adb shell rm /storage/emulated/0/Android/data/net.osmand.plus/files/Us_california_san-francisco_northamerica.obf
    adb shell rm /storage/emulated/0/Android/data/net.osmand.plus/files/Us_california_san-diego_northamerica.obf
    adb shell rm /storage/emulated/0/Android/data/net.osmand.plus/files/Us_california_los-angeles-north_northamerica.obf
    adb shell rm /storage/emulated/0/Android/data/net.osmand.plus/files/Us_california_sacramento_northamerica.obf
    adb shell rm /storage/emulated/0/Android/data/net.osmand.plus/files/Us_california_fresno_northamerica.obf
    adb shell rm /storage/emulated/0/Android/data/net.osmand.plus/files/Us_california_lancaster_northamerica.obf
    adb shell rm /storage/emulated/0/Android/data/net.osmand.plus/files/Us_california_stockton_northamerica.obf
    adb shell rm /storage/emulated/0/Android/data/net.osmand.plus/files/Us_california_redding_northamerica.obf
    adb shell rm /storage/emulated/0/Android/data/net.osmand.plus/files/Us_california_chico_northamerica.obf
    adb shell rm /storage/emulated/0/Android/data/net.osmand.plus/files/Us_california_bakersfield_northamerica.obf
    adb shell rm /storage/emulated/0/Android/data/net.osmand.plus/files/World_basemap_mini.obf

    adb shell df -h /data
    Filesystem Size Used Avail Use% Mounted on
    /dev/block/dm-47 50G 47G 3.3G 94% /data/user/0


    adb install -r current.apk
    Performing Streamed Install
    Success

    adb shell df -h /data
    Filesystem Size Used Avail Use% Mounted on
    /dev/block/dm-47 50G 46G 3.3G 94% /data/user/0


























    --- Synchronet 3.22a-Linux NewsLink 1.2