You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The app sometimes begins calling a station that just called CQ even though Hunt mode is not enabled. Reported by Ron (N7BBQ) after a second day of testing FT8AF Android — happened "a couple of times." Ron notes the legacy FT8TW app exhibited the same behavior.
Expected
When Hunt mode is OFF, the app should never auto-initiate a call to a station that called CQ. Auto-answering an incoming reply to us is fine; auto-initiating a QSO is Hunt-mode behavior only.
Notes / likely culprits
Investigate the auto-answer / "call after no reply" path and whether the CQ-fallback logic (cf. closed Hunt mode: add CQ fallback when band is quiet #245 "Hunt mode: add CQ fallback when band is quiet") can fire while Hunt is disabled.
Intermittent — only a couple of occurrences observed across a day of operating, so likely a state/race condition rather than a deterministic path.
Repro
Not yet reliably reproducible. Operating on HF FT8 with Hunt mode off; app occasionally started calling a CQ'ing station unprompted.
Summary
The app sometimes begins calling a station that just called CQ even though Hunt mode is not enabled. Reported by Ron (N7BBQ) after a second day of testing FT8AF Android — happened "a couple of times." Ron notes the legacy FT8TW app exhibited the same behavior.
Expected
When Hunt mode is OFF, the app should never auto-initiate a call to a station that called CQ. Auto-answering an incoming reply to us is fine; auto-initiating a QSO is Hunt-mode behavior only.
Notes / likely culprits
Repro
Not yet reliably reproducible. Operating on HF FT8 with Hunt mode off; app occasionally started calling a CQ'ing station unprompted.
Reported by Ron N7BBQ via testing feedback.