v1.0.5 Released
Home Features About Documentation Download FAQ Contact
Knowledge Base

Frequently Asked Questions

Find clear answers to common questions regarding permissions, root status, networking, battery usage, and query performance.

No! PocketSQL runs 100% in user space without requiring root permissions, Busybox, or Magisk. It runs smoothly on any Android device running Android 10 (API 29) through Android 15 (API 36).
Yes. PocketSQL is released under the permissive MIT License. You are free to use it for personal projects, academic research, enterprise prototypes, or embedded IoT test fixtures without licensing fees or royalties.
Ensure your phone and laptop are connected to the same Wi-Fi network (or phone hotspot). Open PocketSQL on your phone, start the Background API Server, and note the IP displayed on the screen (e.g. 192.168.1.100:8080). You can now send HTTP POST requests to http://<phone-ip>:8080/api/query using your bearer API key.
PocketSQL features automatic intelligent port scanning. If port 8080 is taken by another app or system service, it will scan incrementally and bind to the first available port up to 8099, clearly displaying the active port in both the app interface and the foreground notification.
PocketSQL is engineered for ultra-low power consumption. When no queries are being executed, worker threads enter an idle wait state with near-zero CPU cycles. It operates as an official Android Foreground Service with standard battery optimization compliance.
Database capacity is limited only by your Android device available storage. PocketSQL employs a high-performance indexed B-Tree page engine and memory-mapped virtual disk storage capable of effortlessly handling multi-gigabyte databases.
Never. PocketSQL is strictly 100% offline-first. There are zero remote cloud telemetry, tracking, or analytics SDKs embedded in the app. Your tables, databases, credentials, and query logs remain exclusively on your device hardware.
API keys and sensitive configurations are encrypted using AES-256 GCM backed by the Android Keystore system (EncryptedSharedPreferences). Database files can also be exported with SQLCipher 256-bit AES encryption.

Still have unanswered questions?

Feel free to contact our engineering team directly or open an inquiry on our contact page.