Repository navigation
App Management, Filters, Background Checks & Backup
This document explains how to skip individual faulty updates, permanently exclude specific apps from updates, configure automatic background checks, and back up or restore your entire configuration.
- 🟢 Part 1: Explained Simply for Everyone (Plain Language)
- 💻 Part 2: Technical Documentation for Experts & Power Users
-
❓ Part 3: Comprehensive Frequently Asked Questions (FAQ) & Common Issues
- 3.1 When should I use "Skip this version"?
- 3.2 When should I use "Ignore app permanently"?
- 3.3 Why should I be careful with pre-installed System Apps?
- 3.4 Do background update checks drain the battery?
- 3.5 Does the exported backup file include my installed APK files?
- 3.6 Can I open and edit the backup file in a text editor?
- 3.7 Common Issue: Why am I not receiving background notifications about new updates?
- 3.8 Common Issue: "Error importing backup file" after manual editing
- 3.9 Common Issue: Why does an app reappear even though I tapped "Skip this version"?
- 🔗 Part 4: Official Links & Further Resources
Sometimes you do not want to install a specific update. When you tap on an app card in the Updates tab, ApkUp gives you two smart options:
| Feature | What happens? | When will you be notified again? |
|---|---|---|
| ⏭️ Skip this version | Only this specific update (e.g., version 2.4.1) is hidden. |
As soon as the developer releases the next newer version (e.g., 2.4.2 or 2.5.0), ApkUp automatically shows the app again! |
| 🙈 Ignore app permanently | The entire app is excluded from all future update checks. | Never — until you manually remove the app from the ignored list. |
You always stay in full control and can undo either choice with a single tap:
-
Via Setup / Settings: Open Setup ➔ Filters & System. There you will find two clear management lists:
- "Manage ignored apps"
- "Manage skipped versions"
- Via the "Apps" Tab: Tap the "Ignored" filter chip at the top of the list. You will immediately see all hidden apps and can re-enable them right there.
- Instant Search & Flexible Sorting: Both Updates and Apps feature live search alongside matching sort menus (Name A–Z / Z–A, Source, plus Newest Release Date in Updates and Recently Updated in Apps) with automatic scroll-to-top on changes.
-
Watch Uninstalled Apps: Tap the
+button in the Apps top bar to follow an app that is not installed yet (by package ID and optional GitHub/GitLab/Codeberg URL). Tracked entries appear under the Watched filter chip and surface discovered releases in Updates with aWatched · Newbadge and a direct Install button.
-
Save APK without Installing: Inside any update's details sheet, tap Save APK to download standalone
.apkinstallers or bundled.apkssplit archives directly into your publicDownload/ApkUp/folder (or a custom folder configured in Setup ➔ Saved APK folder via SAF). Every saved package passes cryptographic integrity and signature checks before export; if a configured SAF folder is unavailable, ApkUp falls back toDownload/ApkUp/and notifies you via snackbar. - Overall Batch Progress & ETA: When updating or saving batches, the hero banner, queue sheet, and download notification show combined percentage, current speed, and estimated time remaining.
- Under Setup ➔ Advanced Settings ➔ Diagnostic & Update Log, you can save (
.txt) or share a sanitized diagnostic report of recent update events. -
Opt-In Process Logcat: Including ApkUp's own process
logcatoutput is disabled by default (opt-in checkbox) for maximum privacy, and all known credential/token formats (Bearer,Authorization: token,ghp_/github_pat_,glpat-,PRIVATE-TOKEN,Basic, and AuroraAuth=/aas_et/) are automatically redacted before export. Temporary share files incacheDir/diagnostic_logs/are automatically cleaned up.
Every smartphone comes with dozens of pre-installed system apps from the manufacturer (Samsung, Xiaomi, Google Pixel).
- By default, ApkUp hides these system apps so your update list stays clean and focused.
- If you also want to update system components (such as Android System WebView or manufacturer utilities), you can enable Setup ➔ Filters & System ➔ Include System Apps.
You do not have to open ApkUp manually every day to check for new versions:
- Under Setup ➔ Background Checks, you can choose how often ApkUp should automatically check for updates in the background:
- Every 6 hours
- Every 12 hours
- Once a day (24 hours – Recommended)
- Every 2 days (48 hours)
- Once a week (7 days)
- Whenever new updates are found, ApkUp sends a clean notification to your phone.
-
Background Update Time Window (v1.44.0+): Open Setup ➔ Background Update Time Window to either pause checks & auto-updates during quiet hours (e.g.
22:00 – 07:00) or allow them only within a chosen window. If a scheduled run falls outside the window, ApkUp automatically schedules a one-time catch-up run at the next window start. -
Pre-Release Channels & Rollback Backups (v1.44.0+): Open Setup ➔ Include Pre-Releases to enable individual channels (Beta, RC, Alpha, Nightly) globally or override them per app. With Automatic Rollback Backups enabled, ApkUp saves the previous APK in private storage (
2 GBLRU limit) before updating so you can roll back from Update History. - Import from App Watcher (v1.44.0+): Open Setup ➔ Import & Export ➔ Import from App Watcher to import uninstalled apps (with their last-seen version) straight into your Watchlist.
When you get a new smartphone or reinstall the app, you do not have to reconfigure your settings, ignored apps, or linked GitHub projects from scratch:
-
📤 Create a Backup (Export):
- Open ApkUp ➔ Setup ➔ Backup & Restore.
- Tap "Export Configuration".
- Choose a location (such as your Downloads folder or Google Drive) and save the file (e.g.,
apkup-backup.json).
-
📥 Restore a Backup (Import):
- Open ApkUp on your new device ➔ Setup ➔ Backup & Restore.
- Tap "Import Configuration".
- Select your saved
apkup-backup.jsonfile. All your sources, custom source priority order, pinned app assignments, filters, ignored apps, and GitHub/GitLab/Codeberg links are restored immediately!
ApkUp strictly separates package-wide exclusions from version-specific exclusions at the architectural level:
-
Package-Wide Exclusion (Ignore App):
Applied before any network queries are dispatched. Ignored package names (
applicationId) are excluded from batch requests sent to external APIs. This reduces network payload size, preserves rate-limit quotas (such as the GitHub API quota), and enhances privacy. -
Version-Specific Pinning (Skip Version):
Stores the combination of package name, skipped version string, and internal Android build number (
versionCode). As long as update sources report the sameversionCode, the entry is filtered out. As soon as any source delivers a strictly higherversionCode, the pin expires automatically and the newer release is surfaced normally.
For periodic update checks, ApkUp never keeps a persistent background service running; instead, it delegates scheduling to the native Android WorkManager (JobScheduler):
-
Network Constraint (
NetworkType.CONNECTED): The job is triggered by the OS only when an active data connection is available. - Doze Mode & App Standby: Android batches execution together with other system maintenance windows so the radio/modem does not have to wake up separately.
- Dynamic Rescheduling: Changing the check interval in settings seamlessly updates the existing periodic job.
So that the app can immediately display the most recently discovered updates upon launch without waiting for a network scan, ApkUp saves a local Update Snapshot in private app storage after every successful check:
- The snapshot contains all discovered updates along with their alternative sources and version metadata.
- When ApkUp starts (or when you switch between tabs), this cached snapshot is loaded instantaneously and preserved (
!hadCache) without triggering an unwanted online re-scan, while reconciling against the live state of the AndroidPackageManager. You can pull down (Pull-to-Refresh) on the Updates tab at any time to trigger a fresh online scan.
For exporting and importing settings, ApkUp uses the official Android Storage Access Framework (SAF). As a result, ApkUp requires zero broad filesystem permissions (READ_EXTERNAL_STORAGE or MANAGE_EXTERNAL_STORAGE) — the app is granted read or write access strictly to the single .json file selected by the user.
The exported JSON file stores:
- Enabled update sources, F-Droid repositories, watched apps, and filter settings (Alpha/Beta filters, system apps, architecture filters)
- List of permanently ignored package names and skipped individual versions
- Manually linked GitHub, GitLab, and Codeberg/Forgejo repositories (validated on import for
https://, allowed hosts, and regex length limits) - Theme, display, and background check preferences (Note: Personal access tokens stay encrypted on-device in Google Tink
AES-256-GCMstorage and are never exported in plaintext backups; importing a backup also resetsuseRootInstallertofalsewith a security notice so Root must be explicitly re-enabled on the device).
This feature is ideal when you know that one specific update of an app has a bug (for example, if other users report that version 4.1.0 crashes). You simply skip 4.1.0 and ApkUp will automatically notify you again as soon as the fixed version 4.1.1 is released.
This is particularly useful when you intentionally want to keep an app on a specific older version (for example, a customized app, a modded build, or an app whose new UI design you dislike).
Many manufacturers (such as Samsung, Xiaomi, or Oppo) tailor their built-in system apps (e.g., Phone, Camera, Gallery, Launcher) specifically to a particular device model and Android OS version.
- Installing a system app from APKMirror that was extracted from a different device model or OS version can cause that system app to crash.
- That is why ApkUp hides system apps by default. Only enable this option if you know exactly which system component you want to update.
No. ApkUp does not keep a persistent background process running for update checks; instead, it hands scheduling over to the Android operating system (WorkManager). Android runs the brief check (usually taking only 3–5 seconds) right when your phone is already awake and connected to Wi-Fi or mobile data.
No, the .json file backs up exclusively your ApkUp settings, filters, ignored apps, and repository links. That is why the backup file is only a few kilobytes in size and can be shared or saved to the cloud in an instant.
Yes! Because it is a cleanly formatted standard JSON file, you can open it on your PC or phone with any text editor, add multiple GitHub repositories at once, and then import the file back into ApkUp.
If automatic background checks are enabled but you still do not receive notifications, it is almost always caused by one of these two device settings:
-
Notification permission denied on Android 13+:
- Open Android Settings ➔ Apps ➔ ApkUp ➔ Notifications and make sure the main toggle "All ApkUp notifications" is turned on.
-
Strict OEM battery optimization:
- Brands like Samsung, Xiaomi, OnePlus, or Huawei often suppress background jobs for apps that have not been opened for several days.
- Solution: Go to Android Settings ➔ Apps ➔ ApkUp ➔ Battery and select "Unrestricted".
If you manually edited an exported .json backup file in a text editor and ApkUp reports an error during import, there is usually a small syntax typo in the JSON structure:
-
Most common cause: A trailing comma (
,) after the very last entry in a list, or missing quotation marks ("). - Solution: Validate your edited file on a free syntax checker such as jsonlint.com, or export a fresh file from ApkUp to use as a template.
The "Skip this version" feature remembers the exact internal build number (versionCode) of the skipped update.
- If the developer publishes a hotfix a few hours later (e.g., keeping the same version name
2.1.0but incrementing the internal build number from2100to2101), ApkUp rightly detects it as a new build and offers it to you. - If you do not want to see any updates for an app at all, choose "Ignore app permanently" instead.
Here you can find further information and official resources on Android background tasks and the JSON backup format:
- 🔋 Don't Kill My App! (OEM guides against background termination): dontkillmyapp.com (Step-by-step instructions for Samsung, Xiaomi, Pixel, OnePlus & more so background checks run reliably)
- ⚙️ Android Developers – WorkManager Documentation: developer.android.com/topic/libraries/architecture/workmanager (Technical documentation on battery-efficient background scheduling on Android)
- 📋 JSONLint – Online JSON Validator: jsonlint.com (Handy tool if you edit your
apkup-backup.jsonmanually on a PC and want to check for syntax errors)