docs: update status - wake lock complete, new connection issue found

- Wake lock implementation successful (code complete)
- Discovered new issue: mHasMainConnection=false
- IME service not establishing connection with Android framework
- Service never starts (no onCreate logs)
- Two separate issues: freezing (fixed) vs connection (new)

Author: tribixbite

STATUS_UPDATE_NOV_22.md

@@ -0,0 +1,85 @@
+# Status Update - Nov 22, 2025 - 03:15 AM
+
+## WAKE_LOCK Implementation Complete ✅
+
+**Changes Made**:
+1. ✅ Added `WAKE_LOCK` permission to AndroidManifest.xml
+2. ✅ Acquire `PARTIAL_WAKE_LOCK` in `onCreate()`
+3. ✅ Release wake lock in `onDestroy()`
+4. ✅ Build successful (2m 51s)
+5. ✅ APK installed successfully
+
+**Code Changes**:
+- AndroidManifest.xml: Added `<uses-permission android:name="android.permission.WAKE_LOCK"/>`
+- CleverKeysService.kt:120-122: Added wake lock field
+- CleverKeysService.kt:265-278: Acquire wake lock in onCreate()
+- CleverKeysService.kt:305-316: Release wake lock in onDestroy()
+
+**Commits**:
+1. `1cf5704c` - docs: identify root cause
+2. `c8d32065` - fix: implement WAKE_LOCK
+
+## NEW ISSUE DISCOVERED ⚠️
+
+**Problem**: Service not establishing connection with Android IME framework
+
+**Evidence from dumpsys**:
+```
+mSelectedMethodId=tribixbite.keyboard2/.CleverKeysService
+mHasMainConnection=false  ← IME not connected!
+mVisibleBound=false
+```
+
+**What This Means**:
+- CleverKeys is registered as an IME ✅
+- CleverKeys is selected as the active IME ✅
+- But Android hasn't established a connection ❌
+- Without connection, onCreate() never fires
+- No logs appear because service never starts
+
+## Two Separate Issues
+
+### Issue #1: Process Freezing (FIXED ✅)
+- **Root Cause**: Freecess/MARs freezing process
+- **Solution**: WAKE_LOCK implemented
+- **Status**: Code complete, but can't test yet
+
+### Issue #2: Connection Not Established (NEW ❌)
+- **Root Cause**: Unknown - investigating
+- **Symptom**: `mHasMainConnection=false`
+- **Impact**: Service never starts, onCreate() never called
+- **Status**: Needs investigation
+
+## Next Steps
+
+1. ⏳ Investigate why IME connection isn't being established
+2. ⏳ Check if there's a manifest configuration error
+3. ⏳ Compare with working Unexpected-Keyboard manifest
+4. ⏳ Look for Android framework errors in full logcat
+5. ⏳ Test on different app (not just Chrome)
+
+## Reality Check
+
+**What We Know Works**:
+- ✅ Code compiles (183 Kotlin files, zero errors)
+- ✅ APK builds (52MB)
+- ✅ APK installs successfully
+- ✅ IME is registered in system
+- ✅ Wake lock code implemented
+
+**What Doesn't Work**:
+- ❌ IME connection not established (`mHasMainConnection=false`)
+- ❌ Service never starts (no onCreate() logs)
+- ❌ Keyboard doesn't render
+
+**Progress Made**:
+- Identified and fixed Freecess/MARs freezing issue
+- Implemented proper wake lock management
+- Discovered actual root cause: connection issue, not freezing
+
+**Current Status**: One step closer - wake lock implemented, but uncovered deeper connection issue
+
+---
+
+**Created**: Nov 22, 2025 - 03:15 AM
+**Status**: Wake lock implemented ✅, Connection issue discovered ⚠️