-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APRSdroid AFSK receive issue with K1 cable using wrong microphone #388
Comments
I seem to be hitting this same issue with the AIOC... Pixel6/Android 15 |
I can look into this, but no guarantees on anything for a while. I don't own either of these so testing may be a challenge. I would highly suggest avoiding VOX by the way, unless you can do a very very short tail on the transmissions. I'll report back when I've been able to fully test it. I'll see if I can make up a cable or something similar to how those function. |
Hi @na7q, Thank you for taking the time to look into this issue. To reproduce the issue, you might not need the exact cable. Connecting any wired headphone to an Android device running APRSdroid should suffice. The problem is that even when a wired headphone is connected, APRSdroid appears to use the device's built-in microphone instead of the headphone microphone for receiving. Ideally, the app should prioritize the microphone of the connected wired headphone in this scenario. Best regards, |
You may be able to use the app if you uncheck high quality demodulation. I'm not certain but I use a USB mic/speaker (digirig lite)and I think APRS Droid ignores that mic when high quality is checked |
I have APRSdroid installed on my Galaxy S10+ (SM-G975F) running Android 12, and it works perfectly.
I recently bought an "APRS K1 cable" on AliExpress and it works fine for transmitting APRS audio from the app to the radio (with VOX enabled). However, even when the cable is connected, I noticed that APRSdroid appears to be using the device's built-in microphone instead of the wired headset's microphone, preventing it from properly receiving APRS messages.
Is it possible to fix this issue? I can provide more information if needed.
I'm currently running APRSdroid version 1.6.3d.
Best regards,
César
The text was updated successfully, but these errors were encountered: