Groups | Search | Server Info | Login | Register


Groups > comp.mobile.android > #153880

Re: 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

Path csiph.com!weretis.net!feeder9.news.weretis.net!border-4.nntp.ord.giganews.com!border-1.nntp.ord.giganews.com!nntp.giganews.com!feeder.usenetexpress.com!tr1.iad1.usenetexpress.com!news-out.netnews.com!s1-2.netnews.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx38.iad.POSTED!not-for-mail
From croy <croy@spam.invalid.net>
Newsgroups comp.mobile.android
Subject Re: 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
Reply-To croy@pam.invalid.net
Message-ID <1d350ld42ig5vffbdo4uu1ev95t2s89l5p@4ax.com> (permalink)
References <10tpces$qa8$1@nnrp.usenet.blueworldhosting.com>
User-Agent ForteAgent/8.00.32.1272
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Lines 91
X-Complaints-To abuse@easynews.com
Organization Forte - www.forteinc.com
X-Complaints-Info Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date Mon, 11 May 2026 19:18:27 -0700
X-Received-Bytes 4703
X-Original-Bytes 4570
Xref csiph.com comp.mobile.android:153880

Show key headers only | View raw


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

Back to comp.mobile.android | Previous | NextPrevious in thread | Find similar


Thread

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 Maria Sophia <mariasophia@comprehension.com> - 2026-05-10 01:34 -0600
  Re: 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 Maria Sophia <mariasophia@comprehension.com> - 2026-05-11 12:41 -0600
    Re: 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 croy <croy@spam.invalid.net> - 2026-05-11 19:16 -0700
  Re: 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 croy <croy@spam.invalid.net> - 2026-05-11 19:18 -0700

csiph-web