Notifications were too intrusive: install-success and export sat on
IMPORTANT_HIGH channels and produced heads-up alerts for every app,
while genuine download failures were buried in the IMPORTANCE_MIN
downloads channel where they were easily missed.
Restructure the channels around user intent:
- Download progress -> MIN, silent, no badge
- Installed apps -> LOW, silent (was HIGH)
- Updates available -> DEFAULT, silent
- App export -> LOW, silent (was HIGH)
- Errors & alerts -> HIGH (new, the only heads-up channel)
Failed downloads, installer-status errors and the unarchive auth prompt
now route to the high-importance alerts channel so they aren't lost,
while successful installs/exports stay quiet.
Android ignores importance edits on an already-created channel, so the
install/export channels get new IDs and the retired IDs (including the
folded-in account channel) are deleted on next launch.
Fold Aurora Store's self-update back into the existing update pipeline
instead of a dedicated sheet/viewmodel/helper. The feed entry is mapped
to a regular App and added to the update list, reusing the standard
download + install path; it is never auto-installed silently.
- Add a dedicated "Self-update" section in the Updates tab with the
app-details navigation disabled (it's served from the Aurora OSS feed).
- Gate eligibility via PackageUtil.isSelfUpdateSupported(): vanilla/preload
flavors, not debug, not F-Droid (huawei excluded by flavor).
- Add a build-aware Settings toggle as the opt-out, removing the row
immediately when disabled.
- Exempt nightly self-updates from deleteInvalidUpdates (static version
code) and drop any stale self-update row when none is offered, so a
phantom update doesn't linger after a self-install.
- This will allow isers to export there current installed app & then do bulk import as favourites
- Probably allowing a bulk install in favourites later would be a great addition
Merge updates checking logic into UpdateWorker and move trigger
methods to UpdateHelper class, similar to how DownloadHelper works.
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
No need to check connectivity as soon as URL is set as SplashFragment will
only let you login when a valid connection is available.
Use a modern dialog and EditText to do set the URL with minimal verification.
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
* Switch connectivitycheck URL to HTTPS as cleartext communication is disabled
* Use GlobalScope to verify and setup proxy URL
* Ignore proxy setup in HttpClient if its empty
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
Treat Aurora Store as a normal app for non-fdroid builds and check
for its updates based on auto-update preference.
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
Using raws with Markdown is not appealing to the user and hard to read. Using blobs will render Markdown readable on GitLab itself.
Requested from someone in Telegram group.
Signed-off-by: marchingon12 <augustthegreat.cool@gmail.com>
