lingochamp/FileDownloader
FileDownloader
FileDownloader is an Android HTTP download manager and multi-threaded download engine designed for managing file transfers. It functions as a resumable transfer framework that utilizes a foreground service to maintain persistent background execution and prevent the operating system from terminating active tasks.
The project features a pluggable networking library architecture, allowing the replacement of default network, storage, and database implementations with custom components. It employs a multi-threaded engine that increases transfer speeds by splitting files into chunks for simultaneous retrieval over multiple concurrent connections.
The system includes a download queue for managing tasks by priority and supports breakpoint-resume capabilities through database-backed progress tracking. It provides task control for pausing or canceling jobs, network constraint configuration to limit transfers to specific connection types, and throttled event dispatching to maintain interface performance during real-time monitoring.
Features
- Concurrent Downloader Managers - Provides a client-side system for managing multi-threaded file downloads with support for resuming interrupted transfers.
- Multi-threaded Downloading - Increases transfer speeds by splitting files into chunks and downloading them simultaneously over multiple concurrent connections.
- Transfer Offset Tracking - Implements database-backed tracking of byte offsets to enable resuming interrupted file transfers from the exact position.
- Download Progress Tracking - Records byte offsets and task states in a local database to facilitate recovery of interrupted downloads.
- Foreground Service Implementations - Utilizes Android foreground services with persistent notifications to prevent the operating system from terminating active downloads.
- Download Traffic Controllers - Provides controls to start, pause, or cancel individual download jobs or all active transfers globally.
- Resumable Downloads - Tracks download progress and restarts transfers from the last successful byte after a pause or failure.
- Resumable File Transfers - Provides a framework for recovering interrupted downloads from the last received byte using progress tracking.
- Download Priority Queues - Manages a queue of download tasks that execute based on priority, supporting sequential or parallel processing.
- Parallel Download Queues - Manages multiple simultaneous downloads with prioritization to optimize bandwidth and transfer speed.
- Download Retry Policies - Automatically attempts to restart failed download tasks a specified number of times upon network or file errors.
- Core Logic Customizations - Allows replacing default implementations for network connections, data streams, and database storage with custom logic.
- Download Behavior Configurations - Allows adjusting network thread counts, file pre-allocation, and synchronization intervals via properties files.
- Download Progress Listeners - Tracks the status of downloads through listeners that provide real-time updates on bytes transferred, speed, and completion.
- Pluggable Network Layers - Provides a pluggable network layer allowing the replacement of default communication components with custom implementations.
- Connection Type Constraints - Limits file transfers to specific connection types like Wi-Fi to prevent unexpected data charges on mobile networks.
- Pluggable Component Architectures - Provides a pluggable architecture to replace default networking, storage, and database implementations with custom classes.
- Process Isolation - Launches the download engine in a separate system process to isolate the user interface from engine crashes.
- Throttled UI Updates - Limits the frequency of progress updates sent to the main thread to prevent interface lag and frame drops.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
