• Tutorial: Samsung Cache-Protection Guide to prevent Aurora's cache of downloaded split APKs from the Google Play repo from being wiped out too soon

    From Maria Sophia@mariasophia@comprehension.com to comp.mobile.android on Sun May 10 01:34:50 2026
    From Newsgroup: comp.mobile.android

    Tutorial: Samsung Cache-Protection Guide to prevent Aurora's cache of downloaded split APKs from the Google Play repo from being wiped out too
    soon

    Tested only on unrooted, somewhat degoogled, Android 13 Samsung Galaxy
    A32-5G

    Samsung Device Care deletes APKs that the Aurora Store temporarily
    saves in its protected folders after installing an app because
    Samsung cleanup routines mistake them for abandoned junk files.

    Specifically, Samsung's com.samsung.android.lool service aggressively
    wipes temp files in app-private storage if it thinks the app is idle,
    even if the files were created seconds ago.

    These steps are designed to stop that behavior.

    1. Stop the system from suspending Aurora so it can hold onto its files.
    Android Settings > Apps > Aurora > Battery > Unrestricted

    2. Disable auto optimization (if they exist)
    Android Settings > Battery and device care > Additional care
    Auto optimize daily = off
    Close apps to free up memory = off
    Restart when needed = (doesn't matter)

    3. Stop the RAM manager from killing the process in the background.
    a. Launch Aurora
    b. Press the bottom-bar Android ||| Recents hamburger icon
    c. Swipe sideways to locate the Aurora card
    d. Tap on the Aurora icon at the top of that Aurora card
    e. Select "Lock this app" out of the popup choices
    (Note the lock icon in the bottom right corner in the recents card.)

    4. Open the Samsung hidden never-sleeping-apps menu to add Aurora manually.
    adb shell am start -n com.samsung.android.lool/com.samsung.android.sm.battery.ui.usage.CheckableAppListActivity
    --ei activity_type 2

    5. Press the (+) button to add Aurora (if Aurora is an available option).

    6. Set Aurora to Active status so the system doesn't target its folders.
    adb shell am set-standby-bucket com.aurora.store 10

    7. Add Aurora to the "Do Not Clean" list.
    adb shell dumpsys deviceidle whitelist +com.aurora.store
    This prevents the system from wiping the app's cache and data while
    the phone is in "Doze" mode or during idle maintenance.

    8. Stop the system from automatically undoing these settings later.
    adb shell settings put global adaptive_battery_management_enabled 0

    Testing the fix

    A. Confirm Aurora is on the do-not-clean list
    adb shell dumpsys deviceidle whitelist | grep com.aurora.store
    A line starting with "user" confirms the system-level bypass is active.

    B. Confirm Aurora is marked as Active
    adb shell am get-standby-bucket com.aurora.store
    A return of 5 or 10 means the kernel is treating Aurora as a priority.

    C. The main test
    i. Open Aurora Store settings > Installation.
    ii. Ensure "Delete APK post-install" is switched off.
    iii. Install any app.
    iv. Once installed, tap the "Downloads" icon (top right) in Aurora.
    v. Long-press the app just installed and select "Save App Bundle".
    vi. Export the file to a folder in internal storage.

    If Aurora successfully saves the file, the cache was protected. If
    the app reports "file not found" or fails, the Samsung cleanup
    wiped the cache before the APK could be exported.

    D. Why manual verification fails
    adb shell run-as com.aurora.store ls -l files/Download
    Result: "run-as: package not debuggable"
    Samsung security prevents direct terminal access to an app's private
    folders. The "Save App Bundle" test is the only reliable verification.

    Note if Aurora Services are used instead of Shizuku for silent installs,
    then repeat the steps for Aurora Services in addition to Aurora.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.mobile.android on Mon May 11 12:41:39 2026
    From Newsgroup: comp.mobile.android

    Maria Sophia wrote:
    Specifically, Samsung's com.samsung.android.lool service aggressively
    wipes temp files in app-private storage if it thinks the app is idle,
    even if the files were created seconds ago.

    It's worse than I had thought.
    <https://dontkillmyapp.com/samsung>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From croy@croy@spam.invalid.net to comp.mobile.android on Mon May 11 19:16:20 2026
    From Newsgroup: comp.mobile.android

    On Mon, 11 May 2026 12:41:39 -0600, Maria Sophia <mariasophia@comprehension.com> wrote:

    Maria Sophia wrote:
    Specifically, Samsung's com.samsung.android.lool service aggressively
    wipes temp files in app-private storage if it thinks the app is idle,
    even if the files were created seconds ago.

    It's worse than I had thought.
    <https://dontkillmyapp.com/samsung>

    Interesting, but nothing much newer than Android 14. I'm on 16, and I
    think there are new problems there.

    Between Android, and the front ends that the phone makers put on and just
    have to update every time some programmer has a new feature they want to install, things are bound to fall thru the ice every now and then.
    --
    croy
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From croy@croy@spam.invalid.net to comp.mobile.android on Mon May 11 19:18:27 2026
    From Newsgroup: comp.mobile.android

    On Sun, 10 May 2026 01:34:50 -0600, Maria Sophia <mariasophia@comprehension.com> wrote:

    Tutorial: Samsung Cache-Protection Guide to prevent Aurora's cache of >downloaded split APKs from the Google Play repo from being wiped out too
    soon

    Tested only on unrooted, somewhat degoogled, Android 13 Samsung Galaxy
    A32-5G

    Samsung Device Care deletes APKs that the Aurora Store temporarily
    saves in its protected folders after installing an app because
    Samsung cleanup routines mistake them for abandoned junk files.

    Specifically, Samsung's com.samsung.android.lool service aggressively
    wipes temp files in app-private storage if it thinks the app is idle,
    even if the files were created seconds ago.

    These steps are designed to stop that behavior.

    1. Stop the system from suspending Aurora so it can hold onto its files.
    Android Settings > Apps > Aurora > Battery > Unrestricted

    2. Disable auto optimization (if they exist)
    Android Settings > Battery and device care > Additional care
    Auto optimize daily = off
    Close apps to free up memory = off
    Restart when needed = (doesn't matter)

    3. Stop the RAM manager from killing the process in the background.
    a. Launch Aurora
    b. Press the bottom-bar Android ||| Recents hamburger icon
    c. Swipe sideways to locate the Aurora card
    d. Tap on the Aurora icon at the top of that Aurora card
    e. Select "Lock this app" out of the popup choices
    (Note the lock icon in the bottom right corner in the recents card.)

    4. Open the Samsung hidden never-sleeping-apps menu to add Aurora manually.
    adb shell am start -n
    com.samsung.android.lool/com.samsung.android.sm.battery.ui.usage.CheckableAppListActivity
    --ei activity_type 2

    5. Press the (+) button to add Aurora (if Aurora is an available option).

    6. Set Aurora to Active status so the system doesn't target its folders.
    adb shell am set-standby-bucket com.aurora.store 10

    7. Add Aurora to the "Do Not Clean" list.
    adb shell dumpsys deviceidle whitelist +com.aurora.store
    This prevents the system from wiping the app's cache and data while
    the phone is in "Doze" mode or during idle maintenance.

    8. Stop the system from automatically undoing these settings later.
    adb shell settings put global adaptive_battery_management_enabled 0

    Testing the fix

    A. Confirm Aurora is on the do-not-clean list
    adb shell dumpsys deviceidle whitelist | grep com.aurora.store
    A line starting with "user" confirms the system-level bypass is active.

    B. Confirm Aurora is marked as Active
    adb shell am get-standby-bucket com.aurora.store
    A return of 5 or 10 means the kernel is treating Aurora as a priority.

    C. The main test
    i. Open Aurora Store settings > Installation.
    ii. Ensure "Delete APK post-install" is switched off.
    iii. Install any app.
    iv. Once installed, tap the "Downloads" icon (top right) in Aurora.
    v. Long-press the app just installed and select "Save App Bundle".
    vi. Export the file to a folder in internal storage.

    If Aurora successfully saves the file, the cache was protected. If
    the app reports "file not found" or fails, the Samsung cleanup
    wiped the cache before the APK could be exported.

    D. Why manual verification fails
    adb shell run-as com.aurora.store ls -l files/Download
    Result: "run-as: package not debuggable"
    Samsung security prevents direct terminal access to an app's private
    folders. The "Save App Bundle" test is the only reliable verification.

    Note if Aurora Services are used instead of Shizuku for silent installs, >then repeat the steps for Aurora Services in addition to Aurora.

    If I tried to do all those things, I would probably brick this phone in no time!
    --
    croy
    --- Synchronet 3.22a-Linux NewsLink 1.2