PTT Button Not Responding
Symptom: Pressing the media button on your headset doesn't trigger PTT.
Troubleshooting Steps
Check BT PTT is Enabled
Go to Settings and verify Bluetooth PTT is toggled on. It should show your connected device name.
Verify Headset Connection
Check your device's Bluetooth settings to confirm the headset is connected (not just paired).
Test the Button
Open a music app and press the headset button. If play/pause works in the music app, the button sends standard media events and should work with CrewTalk.
Check Permissions (Android 12+)
Go to device Settings > Apps > CrewTalk > Permissions and ensure Nearby devices or Bluetooth permission is granted.
Reconnect
Disconnect the headset from Bluetooth settings and reconnect it. Then toggle Bluetooth PTT off and back on in CrewTalk.
Common Causes
- Non-standard buttons: Some headsets have buttons that don't send standard media events (e.g., custom voice assistant buttons)
- Multiple media apps: If another media app has focus, it may consume the button press before CrewTalk gets it. Close other media apps
- Firmware: Headset firmware updates can change button behavior. Check for updates from the headset manufacturer
Audio Routing Problems
Symptom: Audio plays from the phone speaker instead of the headset, or vice versa.
How CrewTalk Routes Audio
| Audio | Route | Profile |
|---|---|---|
| PTT playback | Speaker / BT A2DP / Wired | USAGE_MEDIA |
| PTT recording | BT HFP mic / Device mic | Communication mode |
Fix Audio Routing
- Toggle Bluetooth: Turn BT off and on in device settings
- Reconnect headset: Disconnect and reconnect your headset
- Restart CrewTalk: Close and reopen the app
- Check other audio apps: Close music/video apps that might hold the audio session
Samsung devices are particularly prone to audio routing quirks. Their custom audio HAL sometimes doesn't release the communication device properly. The nuclear option: restart the phone. This resets all audio routing state.
Bluetooth PTT Auto-Disables
Symptom: Bluetooth PTT keeps turning itself off.
This is Expected Behavior
CrewTalk uses a dual-state model:
bluetoothPTTUserEnabled— Your preference (persists)bluetoothPTTEnabled— Active state (changes with BT connection)
When your headset disconnects (out of range, battery dies):
bluetoothPTTEnabledgoes tofalse(BT PTT deactivates)bluetoothPTTUserEnabledstaystrue(your preference is remembered)- When the headset reconnects, BT PTT automatically re-enables
You don't need to manually re-enable BT PTT after a headset reconnect.
Permission Issues (Android 12+)
Android 12 introduced the BLUETOOTH_CONNECT runtime permission. If CrewTalk can't access your Bluetooth device:
- Open device Settings > Apps > CrewTalk > Permissions
- Find Nearby devices (or Bluetooth)
- Set to Allow
- Restart CrewTalk
On Android 11 and below, Bluetooth permissions are granted automatically as part of the location permission group. The explicit Bluetooth permission prompt only appears on Android 12+.
Multiple Bluetooth Devices
If you have multiple Bluetooth devices connected:
- CrewTalk uses the most recently connected audio device
- Disconnect devices you're not using for PTT
- The Settings screen shows which device BT PTT is using
Headset Compatibility
Most Bluetooth headsets work, but some have quirks:
| Headset Type | PTT Button | Notes |
|---|---|---|
| Wireless earbuds | Play/pause | Most reliable |
| Over-ear headphones | Play/pause | Usually reliable |
| Motorcycle intercoms | Play/pause | Usually works |
| AirPods | Squeeze gesture | May not trigger reliably |
| Bone conduction | Play/pause | Usually reliable |
For the most reliable experience, choose a headset with a physical play/pause button rather than touch/gesture controls.