-
-
Notifications
You must be signed in to change notification settings - Fork 6
FAQ.md
KNOOP edited this page Jan 9, 2026
·
2 revisions
This page collects common questions and solutions for using Ava.
Possible causes:
- Device and HA not on same network
- Firewall blocking connection
- Ava service not started
Solutions:
- Ensure device and HA connected to same WiFi
- Check router firewall settings, open port 6053
- Start voice satellite service in Ava
- Try manually adding device (enter IP address)
Possible causes:
- Unstable network
- Ava killed by system
- Battery optimization restrictions
Solutions:
- Check WiFi signal strength
- Disable battery optimization for Ava
- Add Ava to system whitelist
- Keep device charging
- Open phone Settings
- Go to Battery or App Management
- Find Ava
- Select Unrestricted or Allow background activity
Checklist:
- Microphone permission granted
- Mute mode disabled
- Device volume not muted
- Wake word configured correctly
Solutions:
- Check microphone permission in phone settings
- Disable mute in Ava settings
- Press volume keys to increase volume
- Try different wake word
Possible causes:
- Environment too noisy
- Pronunciation unclear
- Too far from device
Solutions:
- Use in quiet environment
- Speak wake word clearly and slowly
- Move closer to device
- Try other wake words
This is usually a Home Assistant issue:
- Check HA voice assistant configuration
- Ensure Whisper and other components working
- Check network latency
- Try speaking more clearly
Checklist:
- HA TTS configured correctly
- Ava volume not muted
- Network connection normal
Checklist:
- Screensaver enabled
- Overlay permission granted
- Timeout configured
- Screensaver URL correct (if using web screensaver)
Solutions:
- Enable screensaver in settings
- Grant overlay permission
- Set appropriate timeout
- Try built-in Xiaomi Wallpaper
Checklist:
- Weather enabled
- City selected
- Chinese city selected
- Network connection normal
Note: Weather feature only supports Chinese cities.
Checklist:
- Overlay permission granted
- Scene ID correct
- HA service call successful
Solutions:
- Check overlay permission
- Confirm scene ID spelling
- Test service call in HA Developer Tools
Possible causes:
- URL incorrect
- Network issue
- Rendering issue
Solutions:
- Check if URL is accessible
- Check network connection
- Try switching render mode (hardware/software)
| Permission | Purpose | Required |
|---|---|---|
| Microphone | Voice input | Yes |
| Overlay | Display screensaver, notifications | Yes |
| Foreground Service | Keep service running | Yes |
| Camera | Photos and video | No |
| Bluetooth | Presence detection | No |
| Location | Bluetooth scanning | No |
- Open phone Settings
- Go to Apps -> Ava
- Find Permissions or Special permissions
- Enable Display over other apps or Overlay
- Open phone Settings
- Go to Apps -> Ava -> Permissions
- Manually enable required permissions
Possible causes:
- Screen on for extended periods
- Video stream frame rate too high
- Too many background tasks
Solutions:
- Lower screen brightness
- Use screensaver (moves content)
- Lower video frame rate and resolution
- Disable unused features
Solutions:
- Keep device charging
- Enable light sensor screen off
- Lower screen brightness
- Reduce background refresh frequency
Solutions:
- Restart Ava service
- Clear app cache
- Reduce simultaneous features
- Check device storage space
Auto update: Ava checks for updates hourly and auto-downloads new versions.
Manual update:
- Visit GitHub Releases
- Download latest APK
- Install over old version
Settings stored in app data, normal updates won't lose them. If lost:
- Check if uninstalled then reinstalled (clears data)
- Reconfigure settings
Common issues:
- Background service killed
- Overlay permission restricted
- Auto-start disabled
Solutions:
- Settings -> Apps -> Ava -> Battery saver -> No restrictions
- Settings -> Apps -> Ava -> Permissions -> Background pop-up -> Allow
- Settings -> Apps -> Auto-start management -> Allow Ava
- Add Ava to battery optimization whitelist
Common issues:
- App killed by battery management
- Overlay permission needs extra setup
Solutions:
- Settings -> Apps -> App launch management -> Ava -> Allow manual management
- Settings -> Battery -> App launch management -> Ava -> Allow all
- Settings -> Apps -> Ava -> Permissions -> Overlay -> Allow
Common issues:
- Background running restricted
- Notification permission needs separate enabling
Solutions:
- Settings -> Battery -> More battery settings -> Optimization strategy -> Ava -> Don't optimize
- Settings -> Apps -> Ava -> Permissions -> Allow background running
- Settings -> Notifications -> Ava -> Allow notifications
Common issues:
- Background service restricted
- Auto-start needs manual enabling
Solutions:
- Settings -> Battery -> Background power consumption -> Ava -> Allow high power consumption
- Settings -> Apps & permissions -> Auto-start management -> Ava -> Allow
Common issues:
- Battery optimization kills background service
Solutions:
- Settings -> Apps -> Ava -> Battery -> Unrestricted
- Settings -> Battery and device care -> Battery -> Background usage limits -> Add Ava to Never auto disable
Usually fewer issues, but still need:
- Settings -> Apps -> Ava -> Battery -> Unrestricted
Most issues are permission-related, general solutions:
Background running permission:
- Settings -> App management -> Ava -> Battery/Power saving -> Unrestricted/Don't optimize
- Settings -> Battery -> Background management -> Allow Ava background running
Overlay permission:
- Settings -> App management -> Ava -> Permissions -> Overlay/Display over other apps
- Some systems may have it under "Special permissions"
Auto-start permission:
- Settings -> App management -> Auto-start management -> Allow Ava
- Some systems may have it in "Security Center" or "Phone Manager"
General tips:
- Add Ava to battery optimization whitelist
- Lock Ava in recent tasks (tap lock icon on card)
- Keep device charging
Possible causes:
- WebView version outdated
- Insufficient memory
- Web content too complex
Solutions:
- Update system WebView (via Play Store)
- Switch to software rendering mode
- Ava has built-in crash recovery, will auto-rebuild WebView
Possible causes:
- Network cannot access GitHub
- Cache corrupted
Solutions:
- Check network connection
- Restart Ava app
- Scenes cache locally, next startup loads from cache first
Checklist:
- Bluetooth permission granted
- Location permission granted (Android requirement)
- Bluetooth enabled
- Device slots configured
Ava is a personal project, originally just for my own use. Code for features like Bluetooth proxy is not open source to prevent copying.
All other feature code is available on GitHub.
Pull Requests welcome. But honestly, few people contribute. This project isn't meant to please everyone - it was originally just for myself.
- Visit GitHub Issues
- Describe the problem
- Provide device info and logs
- Attach screenshots (if any)
GitHub Issues: https://github.com/knoop7/Ava/issues
- Go to Settings -> Voice Satellite
- Tap Stop Service
- Wait a few seconds
- Tap Start Service
Use ADB to view logs:
adb logcat | grep -i ava- Visit GitHub Issues
- Describe the problem
- Provide device info and logs
- Attach screenshots (if any)
GitHub Issues: https://github.com/knoop7/Ava/issues
Back to Home