> The fundamental problem sounds like it's that SQLite insists on not running in its own thread. Pretty much all apps DO have SQLite running on its own thread,

> The fundamental problem sounds like it's that SQLite insists on not running in its own thread. Pretty much all apps DO have SQLite running on its own thread, or at least a background thread pool of some sort. Android gets very cranky at the developer if they don't do this - there's tons of warnings, both runtime and in the form of lint. Database access, or anything involving fsync(), is exceptionally rare on the UI thread or any user-latency-critical thread.