-
Notifications
You must be signed in to change notification settings - Fork 20
Open
Labels
Description
Problem
Background notifications are inconsistent across Android devices. Some devices work
correctly, others don't receive notifications even with all permissions granted.
Root Causes
- Background service runs with low priority (
isForegroundMode: false) - Android kills it - FCM handler doesn't start the service when it's dead
- Missing Android permissions (WAKE_LOCK, battery optimization, boot completed)
- No subscription persistence - lost when service restarts
- No heartbeat/keep-alive for WebSocket connections
Proposed Solution
Hybrid approach:
- No active trades: Background mode (no persistent notification), FCM can wake service
- Active trades: Foreground service (protected, persistent notification)
Implementation Plan
- Fix 03: Add Android permissions
- Fix 02: FCM handler starts background service
- Fix 04: Subscription persistence
- Fix 01: Smart foreground service (only with active trades)
Reactions are currently unavailable