FrostWire Files

FrostWire 3.0.14 build 768 DEC/30/2025

• crash:Race condition in BTEngine initialization - ConfigurationManager wasn't fully initialized before BTEngineInitializer read port preferences, causing port 0 binding failures
• crash:Session failed to initialize when BTEngineInitializer started without waiting for ConfigurationManager to load preferences
• crash:Torrent downloads never started despite successful session initialization - AsyncStartDownload was checking for old TorrentSearchResult interface but new search architecture returns CompositeFileSearchResult
• crash:Search results from torrent sources (TPB, 1337X, MagnetDL, etc.) weren't recognized as torrents after V2 architecture consolidation
• fix:Added support for both old TorrentSearchResult interface and new CompositeFileSearchResult.isTorrent() in AsyncStartDownload
• fix:Call ConfigurationManager.instance() to block until preferences are fully loaded before starting BTEngineInitializer
• fix:BTEngine now properly listens on configured port ranges instead of failing with port 0
• fix:Transfer status showing "Error" for newly started torrents - invalidated status cache now fetches fresh status instead of returning ERROR
• maintenance:Updated gradle plugin to 8.13.2
• maintenance:Updated yt_dlp to 2025.12.08
• maintenance:Updated androidx.exifinterface:exifinterface to 1.4.2
• maintenance:Updated androidx.swiperefreshlayout:swiperefreshlayout to 1.2.0
• maintenance:Updated com.google.firebase:firebase-bom to 34.7.0

# FrostWire for Android 3.0.14: Critical Stability Fixes & Engine Optimization

Just in time for the new year, we are rolling out a vital update for our Android users. FrostWire 3.0.14 (build 768) is now available, and it addresses several critical "day-one" issues introduced with our recent V2 architecture overhaul.

This release focuses on making sure the app starts correctly, downloads reliably, and accurately reports the status of your transfers.

What’s Fixed in Build 768?

🛠 Fixing the "Error" Status Bug

Many users reported that newly started torrents would immediately show an "Error" status even when the download was healthy. We found that the app was occasionally reading from an outdated status cache. We’ve implemented a fix to invalidate that cache immediately upon starting a transfer, ensuring you see the actual download progress instead of a false error.

⚡ Solving Initialization Crashes

We’ve eliminated two major race conditions that occurred during the app's startup sequence:

• Port 0 Binding Failure: Previously, the BitTorrent engine (BTEngine) would sometimes try to start before your settings were loaded, causing it to fail by trying to connect to "Port 0."
• Session Initialization: We’ve ensured the ConfigurationManager now blocks and finishes loading preferences before the engine starts, preventing session-related crashes.

🔍 Restoring Search-to-Download Functionality

Following our recent search architecture consolidation, some results from popular sources (like TPB, 1337X, and MagnetDL) weren't being recognized as torrents.

• We have added support for the new CompositeFileSearchResult interface.
• This ensures that when you click a search result, the download starts immediately as intended.

📈 Maintenance & Core Updates

We have refreshed our core dependencies to ensure maximum compatibility with the latest Android devices:

• yt-dlp Updated to 2025.12.08: Essential for high-speed cloud video downloads.
• Gradle Plugin 8.13.2: Optimized build performance.
• Library Updates: Updated Firebase BOM (v34.7.0), AndroidX ExifInterface (v1.4.2), and SwipeRefreshLayout (v1.2.0).

If you’ve been having trouble with downloads not starting or seeing unexpected errors in your transfer list, this update is highly recommended. Thank you for helping us make FrostWire better by reporting these issues!

Happy New Year and Happy Downloading! — The FrostWire Team