post our own download progress notification

The platform posts one notification per download, so queueing an album buries
the UI in them and they can be swiped away. Hiding them (VISIBILITY_HIDDEN,
which needs DOWNLOAD_WITHOUT_NOTIFICATION) and posting one aggregated
notification instead gives a single ongoing entry with the overall progress and
a Cancel action that stops everything in flight.

It is refreshed from the download state the poller already maintains, so it
tracks the engine without extra queries, and it is tied to this process: if we
are killed the downloads continue with no notification, which is the trade for
not writing a service.
This commit is contained in:
austinried
2026-10-04 00:30:03 +00:00
parent 20814a10f8
commit ce035f457b
9 changed files with 222 additions and 5 deletions
+3
View File
@@ -1,4 +1,7 @@
<?xml version="1.0" encoding="utf-8"?>
<resources>
<string name="app_name">Subtracks</string>
<string name="download_cancel">Cancel</string>
<string name="download_channel">Downloads</string>
<string name="download_channel_description">Progress while songs download</string>
</resources>