locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

Jim - N4ST

Just got hold of the beta an hour ago.

First glance, it is an improvement.

Definitely runs longer than the current non-Beta version.

When I change WSJT-X configurations, such as FT8 to FT4, JTAlert stops reporting decodes.  But, it is not hard frozen like before. 

The band activity still displays and the pop-up works.

Can still open settings and when moving WSJT-X window, JTAlert remains docked. 

Just no decode reporting.

Exiting and restarting JTAlert restores proper operation with the new WSJT-X configuration.

Not ideal, but it is at least usable again.




Jim – N4ST


From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Sunday, May 17, 2020 20:07
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Regarding JTAlert 2.16.5 randomly stopping display of Callsigns


On 18/05/2020 7:32 am, John, DK9JC / AK9JC wrote:

Please allow us some more hours of testing. So far I could not reproduce the bug on the beta. Looking very promising yet.

Will keep you posted. TU for the quick fix.


This message thread wasn't target at you as you had just reported the defect. The message was targeted at those who have had access to the new Beta for several days now without a word of feedback!

Tnx for reporting that the Beta is working for you.

de Laurie VK3AMA

Join Support@HamApps.groups.io to automatically receive all group messages.