we are aim to increase ft8 decode efficience and make the app more powerful please opensource the libft8cn.so or the decode part of it.
believe in the power of commuity, we will make inprovment

Hello
With FT8CN v.091 and x6100 firmware 1.1.7_2 (sept 2023) CAT control and RX works.
Unfortunately, TX audio does not work. Reply in #69 says it is x6100 audio problem
I managed to have WSJT transmit audio through WFview on laptop using WFserver on x6100 by tweaking alsamixer (Change from DAC to Mixer and increase Volume of Mic1 Boost)
amixer -c 0 set 'Headphone Source' 'Mixer'
amixer -c 0 set 'Mic1 Boost' 24db
This can also be done from alsamixer
This tweak allows WSJT or JTDX to transmit through WFview and WFserver

Problem with ft8cn v.091 is that TX power is completely lost after connecting and testing ft8cn, only factory reset of x6100 brings back tx power.

Hello, tell me please, in version 0.85 of the program there is already the possibility of saving received callsigns in (adi) for the radio observer? (SWL) Thanks for the reply.

Hello, and thank you for this app.

When using WSJT-X on my laptop, I get 10-20 decodes per cycle. When using FT8CN, I get 0-2. A few details:

• I've confirmed that my clock is synchronized
• I've tried FT8CN versions 0.83 and 0.86
• I'm using a Xiegu G90
• the "DeNoise" feature doesn't help

Is there a "Decode" depth setting (Fast/Normal/Deep) that could be increased, like in WSJT-X? Please let me know if there are other details I can provide.

Dear BG7YOZ

I have been using FT8CN for some months now. I have had some problems, and these are now resolved. FT8CN is very impressive. I am amazed at what it does, and so well. What follows is not criticism, merely suggestions for a better (for me at least!) user experience.

There are three items;

1. The addition of a free text option. I appreciate FT8 is not a conversation mode, but I often have a pile-up and it would be useful to send a message such as “ZB2MD QRT” or “ZB2MD QSY 21.300” which of course also implies a change of mode to SSB.

2. Non-scrolling. Occasionally the FT8CN does NOT scroll, and it might take a few cycles to notice, by which time the QSO has moved on. I might be sending RR73 repeatedly despite the other station having sent 73s.

The most serious of the issues reported here;

3. FT8CN takes control! When the bands are quiet with few stations, FT8CN does an excellent job automatically, tracking the progress of a QSO and sending the next appropriate message. When I have a pile-up, it is a completely different matter.

I may be in QSO with Station A, and I am ready to send “Station A ZB2MD R-10”. Just before that message gets transmitted, Station B calls me and FT8CN IMMEDIATELY changes from the QSO with Station A and begins a QSO with Station B.
I then find myself holding two QSOs at the same time. The only way I can stop this is to stop transmission so that the string to Station B is NOT transmitted, but I have not transmitted to Station A either.
I prepare to send the wanted string to Station A, only to find that FT8CN at the last moment chooses to respond to Station C who has just called me.
At times when I have chosen NOT to correct this, to see what happens, I find FT8CN has started numerous QSOs but does not progress with any of them, as long as new stations keep calling.

Is there a means of locking FT8CN to the QSO that I choose to continue with, rather than have FT8CN override my choice?

Many thanks for your patience and attention.

Hi, all.

FT8CN looks like a really interesting application, for amateur radio, so I thought i'd have a quick look at it, with Qark. I was surprised to see quite a few warning/ issues with the code, many of which seemed to be security issues. I was unable to upload the html report file, produced by Qark, so have copied it, here. Please note that the URLs in the report are obviously pointing to a local directory, so will not resolve. For more detail, run the report yourself.

Would it be possible for the developers to run Qark on the application, and to comment on the issues?
Qark Report.odt

Many thanks,

Chris.

I can't see any source code in this repo.

Is this an Open Source project, ?

Tried apk with Android 12 phone with version 0.87 of FT8CN
Using both setups rig: X6100/G90S(USB) and X6100/G90S(U-DIG)
Xiegu X6100 last firmware installed
Connection: USB-C OTG cable phone<->Rig
Control: CAT
Receiving without problem, but CAT doesn't work, neither PTT / txmission achieved.
Am I doing something wrong?
Thank you

国内可能就这里对FT8_lib最熟悉了，看了好长时间，快速傅里叶变换后云里雾里，还用到科斯塔斯环，可否给讲一下kiss_fftr后如何解调得到码元？也欢迎老外帮忙讲解一下。

The person most familiar with FT8_lib in China may be here. After looking at it for a long time, it is foggy after fast Fourier transform, and Costas loop is also used. Can you tell me how to get the channel symbols or FT8 Bits after kiss_fftr? Foreigners are also welcome to help explain.

Hi,
It could be very useful a step by step guide to prepare the development environment ready to generate the apk file.

FT8CN is a wonderful project!

Best regards,
Iz0zpb, 73

Crashes when starts decoding on Google Pixel 4C

Кто-то уже писал про ic-7300, аппарат прекрасно управляется по usb, но периодически он не может передавать, хотя динамик в программе показывает наличие передачи, в чем проблема? Пробовал на планшете и телефоне, производители устройств разные
В первый раз, когда программа открыта, передача есть, но последующие qso невозможно провести, такое ощущение, что программа не может перевести трансивер на передачу, хотя переключение диапазонов работает

Some of us on the QRPLabs forum have noticed that a problem recently appeared when using FT8CN 0.89 with QRPLabs QMX transceivers.
(See https://groups.io/g/QRPLabs/topic/100738548)
At least two of us are running FT8CN on Google Pixel 6A Android phones.
We see that the first FT8 transmission happens normally.
But after that every subsequent transmission has no or little audio.
This continues until exiting FT8CN.
After re-running FT8CN, the first transmission is normal again and every transmission after that has low/no audio.
This seems to have started happening pretty recently so it may be due to an Android update.
I am willing to help troubleshoot it on my phone if you are unable to reproduce it.
Thank you and 73.

--Mike

Since i updated to the latest version i can't download the contacts. I am connected to the same network. and with previous versions I didn't have this problem. Does anyone else have the same problem?

Is it possible to add support for external services?

For example:

• PSK Reporter
• qrz.com
• HRDLOG.net
• eQSL

That would be awesome

Is it possible to make the time window a little bit longer. It never happens that I have enough time to react in 2 seconds. Transmitting is always starting in the next time window, 30 seconds later.

73 Ron
PD7RON

please add free tx/rx massage for using at emergency

Would love a manual for the app and why isn't anyone coming back to me does the phone speaker have an affect on it using ft817 and Bluetooth
Nothing on psk reporter as well but all seems to decode via ft8 app

Thanks andy

version 0.86
need manual put file into path ft8CN\app\src\libs\osmdroid-android-6.1.14.aar

Can you support TX1; form of command?

Hi! First of all, thank you for making such a great app. I have used it for several months and there are some small issues that may be able to be fixed in future:

1. When the sender and the receiver have the same grid, or the receiver's grid is unknown, the comment shows Distance: , QSO by FT8CN. Maybe it is possible to hide the Distance field and only show QSO by FT8CN here in this case.
2. When downloading the QSO records, if the phone is not connected to a Wi-Fi, it shows http://null:7050 as the URL. Is it better to replace it with some prompt like "Please connect to a valid Wi-Fi" or something else?
3. When uploading ADIF file to the app, some log software will ignore the rst_rcvd & rst_sent field if it is 0 (0dB). In that case, FT8CN will show -120dB for this missing field. This only happens when importing a log. Is it better to change the default value to 0?

Hope these suggestions will help improve the software.

Rig: Yaesu FT-991A
Cable: few different USB-OTG cables, few different USB cables
Phone: Samsung A51 / UI5.1 (testing with Samsung S21FE), change UI lang w/ no results
Problem: no rig control / no TX
Freq not set, no transmission possible. Rig was set to its default values (MENU reset), already tried different speed, port, etc.

WSJT-X working just fine. All permission for app was done.

If I set freq - no changes, but if I then disconnect cable = rig change freq. It seems stuck somewhere somehow in transit (???).

Step to reproduce:

• connect phone
• start FT8CN (automatically or manually)
• make correct port selection
• set Freq (eg start TX) - no changes on rig
• disconnect rig = freq changed momentary after cable disconnection

Any ideas?

UB6LUM
73!

A few issues......

First issue. The QSO log records errors in the names of countries worked. See the attached files, where many of the prefixes recorded do not correspond with the countries identified. There were many more such occurrences, but this is sufficient to illustrate. For example, in the first image...

N9 is identified as European Russia when it should read USA
KB6 is identified as Asiatic Russia when it should read USA
JK3 is identified as Poland when it should read Japan etc etc

The country is not recorded in the adi file, so this should not be an issue with electronic logbooks - I think.

Second issue. IM76 is my GRID square, not my GIRD square.

Third issue. I have difficulty accessing my log and other files in my PC browser, as instructed in FT8CN. MOST of the time I simply cannot make the connection. What can I do to make a reliable connection? Mostly "192.168.1.5 has taken too long to respond". I have looked for but cannot find the files in my smartphone. I have made hidden files visible, but still I cannot locate them. If I could locate them I could transfer them easily.

Hello, tell me, is it possible in the program to save the log in the adi format in the receive mode? or somehow save a log for radio surveillance without a PC?

Hello
FT8CN crashes when Network connection is attempted to newest Xiegu X6100 firmware which supports WFserver (Icom IC705 emulation)

FT8CN ver0.9

please check crash information from Android device.

FT8CN ver0.9 works normally when connection is USB to Xiegu X6100 previous firmware version 1.1.6

73
HB9TXB Branko

08-16 16:23:51.981  2162  2257 D IcomUdpBase: start PingTimer: local port:41707,remote port 50001
08-16 16:23:51.981  2162  2162 E ViewRootImpl: sendUserActionEvent() mView == null
08-16 16:23:52.001  2162  2257 D IcomUdpBase: start Idle Timer: local port:41707,remote port 50001
08-16 16:23:52.001  2162  2257 D IcomControlUdp: connection mode:WFVIEW
08-16 16:23:52.001  2162  2257 D IcomControlUdp: onReceiveLoginResponse: Login succeed!
08-16 16:23:52.001  2162  2257 D IcomControlUdp: onReceiveLoginResponse: send token confirm 0x02
08-16 16:23:52.001  2162  2257 D IcomControlUdp: start Toke Timer: local port:41707,remote port 50001
08-16 16:23:52.011  2162  2257 E IcomControlUdp: onReceiveConnInfoPacket: send 0x90
08-16 16:23:52.011  2162  2257 E AndroidRuntime: FATAL EXCEPTION: pool-16-thread-1
08-16 16:23:52.011  2162  2257 E AndroidRuntime: Process: com.bg7yoz.ft8cn, PID: 2162
08-16 16:23:52.011  2162  2257 E AndroidRuntime: java.lang.ArrayIndexOutOfBoundsException: length=32; index=32
08-16 16:23:52.011  2162  2257 E AndroidRuntime: 	at com.bg7yoz.ft8cn.icom.IComPacketTypes.stringToByte(IComPacketTypes.java:911)
08-16 16:23:52.011  2162  2257 E AndroidRuntime: 	at com.bg7yoz.ft8cn.icom.IComPacketTypes$ConnInfoPacket.connInfoPacketData(IComPacketTypes.java:524)
08-16 16:23:52.011  2162  2257 E AndroidRuntime: 	at com.bg7yoz.ft8cn.icom.IcomControlUdp.onReceiveConnInfoPacket(IcomControlUdp.java:105)
08-16 16:23:52.011  2162  2257 E AndroidRuntime: 	at com.bg7yoz.ft8cn.icom.IcomControlUdp.onDataReceived(IcomControlUdp.java:79)
08-16 16:23:52.011  2162  2257 E AndroidRuntime: 	at com.bg7yoz.ft8cn.icom.IcomUdpBase$1.OnReceiveData(IcomUdpBase.java:122)
08-16 16:23:52.011  2162  2257 E AndroidRuntime: 	at com.bg7yoz.ft8cn.icom.IcomUdpClient$DoReceiveRunnable.run(IcomUdpClient.java:211)
08-16 16:23:52.011  2162  2257 E AndroidRuntime: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
08-16 16:23:52.011  2162  2257 E AndroidRuntime: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
08-16 16:23:52.011  2162  2257 E AndroidRuntime: 	at java.lang.Thread.run(Thread.java:818)
08-16 16:23:52.021  3027  4277 D InputDispatcher: Focus left window: 2162
08-16 16:23:52.651  2162  2162 D ViewRootImpl: #3 mView = null
08-16 16:23:52.971  2162  2275 W System.err: java.net.SocketException: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2275 W System.err: 	at libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:542)
08-16 16:23:52.971  2162  2275 W System.err: 	at libcore.io.IoBridge.sendto(IoBridge.java:511)
08-16 16:23:52.971  2162  2275 W System.err: 	at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:184)
08-16 16:23:52.971  2162  2275 W System.err: 	at java.net.DatagramSocket.send(DatagramSocket.java:305)
08-16 16:23:52.971  2162  2275 W System.err: 	at com.bg7yoz.ft8cn.icom.IcomUdpClient$SendDataRunnable.run(IcomUdpClient.java:84)
08-16 16:23:52.971  2162  2275 W System.err: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
08-16 16:23:52.971  2162  2275 W System.err: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
08-16 16:23:52.971  2162  2275 W System.err: 	at java.lang.Thread.run(Thread.java:818)
08-16 16:23:52.971  2162  2275 W System.err: Caused by: android.system.ErrnoException: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2275 W System.err: 	at libcore.io.Posix.sendtoBytes(Native Method)
08-16 16:23:52.971  2162  2275 W System.err: 	at libcore.io.Posix.sendto(Posix.java:211)
08-16 16:23:52.971  2162  2275 W System.err: 	at libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:278)
08-16 16:23:52.971  2162  2275 W System.err: 	at libcore.io.IoBridge.sendto(IoBridge.java:509)
08-16 16:23:52.971  2162  2275 W System.err: 	... 6 more
08-16 16:23:52.971  2162  2275 E RadioUdpSocket: IComUdpClient: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2278 W System.err: java.net.SocketException: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2278 W System.err: 	at libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:542)
08-16 16:23:52.971  2162  2278 W System.err: 	at libcore.io.IoBridge.sendto(IoBridge.java:511)
08-16 16:23:52.971  2162  2278 W System.err: 	at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:184)
08-16 16:23:52.971  2162  2278 W System.err: 	at java.net.DatagramSocket.send(DatagramSocket.java:305)
08-16 16:23:52.971  2162  2278 W System.err: 	at com.bg7yoz.ft8cn.icom.IcomUdpClient$SendDataRunnable.run(IcomUdpClient.java:84)
08-16 16:23:52.971  2162  2278 W System.err: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
08-16 16:23:52.971  2162  2278 W System.err: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
08-16 16:23:52.971  2162  2278 W System.err: 	at java.lang.Thread.run(Thread.java:818)
08-16 16:23:52.971  2162  2278 W System.err: Caused by: android.system.ErrnoException: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2278 W System.err: 	at libcore.io.Posix.sendtoBytes(Native Method)
08-16 16:23:52.971  2162  2278 W System.err: 	at libcore.io.Posix.sendto(Posix.java:211)
08-16 16:23:52.971  2162  2278 W System.err: 	at libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:278)
08-16 16:23:52.971  2162  2278 W System.err: 	at libcore.io.IoBridge.sendto(IoBridge.java:509)
08-16 16:23:52.971  2162  2278 W System.err: 	... 6 more
08-16 16:23:52.971  2162  2278 E RadioUdpSocket: IComUdpClient: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2276 W System.err: java.net.SocketException: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2276 W System.err: 	at libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:542)
08-16 16:23:52.971  2162  2276 W System.err: 	at libcore.io.IoBridge.sendto(IoBridge.java:511)
08-16 16:23:52.971  2162  2276 W System.err: 	at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:184)
08-16 16:23:52.971  2162  2276 W System.err: 	at java.net.DatagramSocket.send(DatagramSocket.java:305)
08-16 16:23:52.971  2162  2276 W System.err: 	at com.bg7yoz.ft8cn.icom.IcomUdpClient$SendDataRunnable.run(IcomUdpClient.java:84)
08-16 16:23:52.971  2162  2276 W System.err: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
08-16 16:23:52.971  2162  2276 W System.err: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
08-16 16:23:52.971  2162  2276 W System.err: 	at java.lang.Thread.run(Thread.java:818)
08-16 16:23:52.971  2162  2276 W System.err: Caused by: android.system.ErrnoException: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2276 W System.err: 	at libcore.io.Posix.sendtoBytes(Native Method)
08-16 16:23:52.971  2162  2276 W System.err: 	at libcore.io.Posix.sendto(Posix.java:211)
08-16 16:23:52.971  2162  2276 W System.err: 	at libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:278)
08-16 16:23:52.971  2162  2276 W System.err: 	at libcore.io.IoBridge.sendto(IoBridge.java:509)
08-16 16:23:52.971  2162  2276 W System.err: 	... 6 more
08-16 16:23:52.971  2162  2276 E RadioUdpSocket: IComUdpClient: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2277 W System.err: java.net.SocketException: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2277 W System.err: 	at libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:542)
08-16 16:23:52.971  2162  2277 W System.err: 	at libcore.io.IoBridge.sendto(IoBridge.java:511)
08-16 16:23:52.971  2162  2277 W System.err: 	at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:184)
08-16 16:23:52.971  2162  2277 W System.err: 	at java.net.DatagramSocket.send(DatagramSocket.java:305)
08-16 16:23:52.971  2162  2277 W System.err: 	at com.bg7yoz.ft8cn.icom.IcomUdpClient$SendDataRunnable.run(IcomUdpClient.java:84)
08-16 16:23:52.971  2162  2277 W System.err: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
08-16 16:23:52.971  2162  2277 W System.err: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
08-16 16:23:52.971  2162  2277 W System.err: 	at java.lang.Thread.run(Thread.java:818)
08-16 16:23:52.971  2162  2277 W System.err: Caused by: android.system.ErrnoException: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2277 W System.err: 	at libcore.io.Posix.sendtoBytes(Native Method)
08-16 16:23:52.971  2162  2277 W System.err: 	at libcore.io.Posix.sendto(Posix.java:211)
08-16 16:23:52.971  2162  2277 W System.err: 	at libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:278)
08-16 16:23:52.971  2162  2277 W System.err: 	at libcore.io.IoBridge.sendto(IoBridge.java:509)
08-16 16:23:52.971  2162  2277 W System.err: 	... 6 more
08-16 16:23:52.971  2162  2277 E RadioUdpSocket: IComUdpClient: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2279 W System.err: java.net.SocketException: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2279 W System.err: 	at libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:542)
08-16 16:23:52.971  2162  2279 W System.err: 	at libcore.io.IoBridge.sendto(IoBridge.java:511)
08-16 16:23:52.971  2162  2279 W System.err: 	at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:184)
08-16 16:23:52.971  2162  2279 W System.err: 	at java.net.DatagramSocket.send(DatagramSocket.java:305)
08-16 16:23:52.971  2162  2279 W System.err: 	at com.bg7yoz.ft8cn.icom.IcomUdpClient$SendDataRunnable.run(IcomUdpClient.java:84)
08-16 16:23:52.971  2162  2279 W System.err: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
08-16 16:23:52.971  2162  2279 W System.err: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
08-16 16:23:52.971  2162  2279 W System.err: 	at java.lang.Thread.run(Thread.java:818)
08-16 16:23:52.971  2162  2279 W System.err: Caused by: android.system.ErrnoException: sendto failed: EINVAL (Invalid argument)
08-16 16:23:52.971  2162  2279 W System.err: 	at libcore.io.Posix.sendtoBytes(Native Method)
08-16 16:23:52.971  2162  2279 W System.err: 	at libcore.io.Posix.sendto(Posix.java:211)
08-16 16:23:52.971  2162  2279 W System.err: 	at libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:278)
08-16 16:23:52.971  2162  2279 W System.err: 	at libcore.io.IoBridge.sendto(IoBridge.java:509)
08-16 16:23:52.971  2162  2279 W System.err: 	... 6 more
08-16 16:23:52.971  2162  2279 E RadioUdpSocket: IComUdpClient: sendto failed: EINVAL (Invalid argument)
08-16 16:23:53.781  2162  2162 D IcomRigConstant: setOperationFrequency: fe fe a4 e0 05 00 40 07 28 00 fd
08-16 16:23:53.781  2162  2279 W System.err: java.net.SocketException: sendto failed: EINVAL (Invalid argument)
08-16 16:23:53.781  2162  2279 W System.err: 	at libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:542)
08-16 16:23:53.781  2162  2279 W System.err: 	at libcore.io.IoBridge.sendto(IoBridge.java:511)
08-16 16:23:53.781  2162  2279 W System.err: 	at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:184)
08-16 16:23:53.781  2162  2279 W System.err: 	at java.net.DatagramSocket.send(DatagramSocket.java:305)
08-16 16:23:53.781  2162  2279 W System.err: 	at com.bg7yoz.ft8cn.icom.IcomUdpClient$SendDataRunnable.run(IcomUdpClient.java:84)
08-16 16:23:53.781  2162  2279 W System.err: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
08-16 16:23:53.781  2162  2279 W System.err: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
08-16 16:23:53.781  2162  2279 W System.err: 	at java.lang.Thread.run(Thread.java:818)
08-16 16:23:53.781  2162  2279 W System.err: Caused by: android.system.ErrnoException: sendto failed: EINVAL (Invalid argument)
08-16 16:23:53.781  2162  2279 W System.err: 	at libcore.io.Posix.sendtoBytes(Native Method)
08-16 16:23:53.781  2162  2279 W System.err: 	at libcore.io.Posix.sendto(Posix.java:211)
08-16 16:23:53.781  2162  2279 W System.err: 	at libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:278)
08-16 16:23:53.781  2162  2279 W System.err: 	at libcore.io.IoBridge.sendto(IoBridge.java:509)
08-16 16:23:53.781  2162  2279 W System.err: 	... 6 more
08-16 16:23:53.781  2162  2279 E RadioUdpSocket: IComUdpClient: sendto failed: EINVAL (Invalid argument)
08-16 16:23:54.581  2162  2257 I Process : Sending signal. PID: 2162 SIG: 9
08-16 16:23:54.771  2350  4398 W AudioFlinger: session id 233 not found for pid 2162
08-16 16:23:54.771  3027  4224 D ActivityManager: removeProcessNameLocked mProcessNames.remove pid=2162 ,hash=59484991 ,name=com.bg7yoz.ft8cn
08-16 16:23:54.771  3027  4224 I ActivityManager: Process com.bg7yoz.ft8cn (pid 2162)(adj 9) has died(102,538)
08-16 16:23:54.771  3027  4224 D ActivityManager: cleanUpApplicationRecord -- 2162```

FT8CN ver 0.90 (checked w/ 0.88 (problem confirmed) /0.87(not sure about version)).

Rig Yaesu FT-991A

Problem: incorrect MODE setting while using FT8CN.

Reproduce:

• rig is powered on, freq is set to 18100, MODE = DATA-USB, width, agc, already set as expected.
• connecting cable to smartphone, run FT8CN - freq still here, MODE changed to USB (here is problem = limited bw and transmission not possible at all) = expected mode DATA-USB (MD0C?)
• change MODE to D-U/DATA-USB manually, freq shifting +70hz, manually correct it on rig = made some some good stuff, CQ and DXing, works perfectly
• ... until I go to Settings to change freq, for example - MODE change again to USB, need to revert it back after completing setup.

Of course, rig already checked and work just fine on WSJT-X setup in field and stationary.

Not a big deal, but sometimes it's a bit annoying especially when forgot to change settings and lost interesting CQ 😵‍💫

Also this can be my ordinary mistake and some kind of mis-configuration on rig, I'll can get it )

TNX DE UB6LUM

Please release for YAESU FT-100(D) , Because there is no suitable profile for FT-100(D) rig in the FT8CN setting. Thanks！

73
BU2AE

Hi. Have the latest version of FT8CN, v.0.88
All works as advertised using a Motorola android smartphone, lining to the rig with a (USB-B - to - USB-A cable) and a (USB A-to-C) OTG adaptor. I have tried a (USB A to C) cable but this will not permit the phone to recognise a radio.
The decoding happens without issue, and everything works fine EXCEPT THAT the radio will NOT transmit.
When the time comes to transmit, the rig is activated accordingly but no output ensues.
Without a specific profile for the 710, I have entered the nearest available which is the FT-DX10 profile

I have uploaded a screenshot of my settings
Help!

Moin,

while sending works fine it's not possible to receive. Error message:

Cannot record. Please check permissions. startRecording() called on an uninitialized AudioRecording

Phone is a Samsung S10+. Permission to access the microphone while using the app is granded.

Please release for IOS , Because there is no suitable software on IOS for FT8.
73, EP7NIM

Using USB, It decodes audio. It will not transmit through radio. Phone just sounds through phone speaker. Doesn't seem to change frequencies from app either.
Tried using Q900 and FT817. Neither work.

Hello, I have a Belka DX (great radio BTW) and I would like to use it with FT8CN.
The Belka has 2 output: audio or IQ and have SSB.

Is there a configuration that can work with it?
Thank you

Love this app. Works great on my galaxy s9 phone but not on my new android 10 tablet or android TV box. They both give an error of "cannot record. Please check permissions. Start recording () called on an uninitialized audio record" any thoughts?

Hola, me podrían ayudar indicando, si se puede conectar una yaesu ft-840 por medio del cat

Hello.
Can you ignore vid/pid of serial port adapter?
For example, my TRX compound usb device appear as VID=0xFFFF and various PID in depend of configurations, CDC ACM port appear...
Then I change vid/pid to 0x0483/0x5732 - Kenwood TS-590S CAT work as expected...

Hello, there is no APK file in version 0.86, I really want to have the ability to save received callsigns in the program for radio observers. SWL. Thank you, regards.73!

Hi everybody,
I have installed FT8CN ver 0.88 patch 2 on my Samsung Galaxi note 8 . So to understand how the program works I used it only in reception using the micro of the smartphone. Honestly, the program demodulates the callsigns well, but if I click on a call that is making a call, the call window at the bottom of the smartphone screen remains empty. Only a few times the command is executed and the callsign I have chosen appears in the window at the bottom of the screen. I didn't understand if to do this test is necessary to connect the radio and I would like some of you to give me some information about it.
I thank you in advance for the answer.
Vincenzo i8bvw

Hello everyone, contrary to what was stated in the new release, the problem identified as

Fixed QSO sequence sometimes stuck at sending RR73 if not received any reply

in my case it appeared, while with the previous release 0.88 patch2 I didn't have it.

(I posted these comments elsewhere on this site but thought they may be best addressed here with some edits)

I noticed that prior to FT8CN ver 0.89 the decoded signals in the decode/call screens displayed as "band 1m" band 2m" etc. and frequency as "155.XXXXXX" for example, as opposed to the traditional ham band format descriptors (17m, 20m, etc,) and frequency (14.074mHz, 18,100mHz, etc.) The QSO log reflected this non-traditional format which required that I edit the exported adi file to comform to other logging programs.

After updating to ver 0.89 I noticed that the decode/call screens were displaying the band and frequency in the traditional ham band format (20m,14-074mHz) which was also displayed in the QSO log after one contact.. Suddenly after initiating a second call I noticed that the decode/call screens would revert back to the non-traditional format upon the second 15 second transmit cycle and remain that way until the frequency (band) was changed. Then the reversion process would repeat itself. As i mentioned there was one initial QSO that logged the contact in the traditional ham format. Those that followed reverted back to the non-traditional format,

Is the FT8CN app decode/call screens supposed to display the traditional ham band logging format (ie 17m, 18.100mHz)? And if so, should that tradutional format carry over to the QSO log?

Thanks.

Hello, I work in reception mode SWL(US-I-777) .Please help me to deal with the problem, I'm uploading the log to eqsl and this error is displayed, please help with advice,My QTH КN 78 😋😓73!📻

The app has CAT control over the X6100 over bluetooth, but does not seem to be sending the audio to the rig over the BT connection as there is no power output on the radio.

Hello, thank you for an amazing piece of software.

I've got a trusdx that I'm trying to get working, and I wonder if a setting can be added to control the DTR/RTS serial port lines - for trusdx they should be:

• DTR: high
• RTS: low

See this video from the creator of trusdx for context:
https://www.youtube.com/watch?v=W5M2C7rW0b0&t=174s

from #62.

I found a problematic part from FT8Package.java

https://github.com/N0BOY/FT8CN/blob/40d3e95e/ft8cn/app/src/main/java/com/bg7yoz/ft8cn/ft8signal/FT8Package.java#L119-L122

        //当双方都是复合呼号或非标准呼号时（带/的呼号），我的呼号变成标准呼号
        if ((toCall.contains("/")) && fromCall.contains("/")) {
            fromCall = fromCall.substring(0, fromCall.indexOf("/"));
        }

I think here is if both call is non-standard, transform fromCall to std call.

btw, when you trip to another country, local bureau allows temporary callsign such as HL1/BG7YOZ
(you can't use BG7YOZ directly in South Korea)

so, if two trip operators communicate each others, HL1/BG7YOZ and HL5/N0BOY, fromCall is only remained HL1.

we have to detect correct callsign pattern, then extract it using regex or specific rules.
some weeks ago, I saw similar issues in qlog logger project;

• foldynl/QLog#227
• foldynl/QLog@12dd9f91c9

The application crashes often at start of transmit. Seams stable in recieve. The crash is not consistant, but is often and only when going into transmit.
Do you have a way to submit the debug dumpstate without posting it here? or can you tell me how to send only the part of the log you need, or specifics on what to send if different than the debug dumpstate?

Hello, when I connect to the trusdx, I am able to see the decoded signals. I am unable to transmit and PTT does not work. When I choose the serial port, it connects successfully, but within one second, I then receive a message saying, "Communication error with rig, the connection is broken". Then some Chinese writing and at the end of that is "2>1"

Using:
trusdx firmware 2.00u (latest)
Samsung S23 Ultra (updated)
Baud rate/connection- 115200, CAT
50 ohm coax to steppir antenna (very good swr)
USB cable: https://www.officedepot.com/a/products/795902/Ativa-USB-20-Type-C-to/?utm_source=google&utm_medium=cpc&mediacampaignid=71700000113868766_20488703163&utm_source=google&utm_medium=cpc&gclid=Cj0KCQjwvL-oBhCxARIsAHkOiu19jyyzvgNkTaNjuiCrhvcJXwZQzdJV2X4VasF4A2ZKWersmbSuwJwaAu00EALw_wcB&gclsrc=aw.ds

Ver: 0.91
Rig: YAESU FT-991A
Problem: incorrect mode selected (RTTY-USB), when selecting Yaesu FT-891/991 (USB or DATA-USB). Mode alwayes to R-U (RTTY-USB).

This could be related to #73 ?

I can provide logs (which one), etc per request if you need to.

BTW, frequency jump problem completely solved, tnx :)

TNX de UB6LUM

First of all this app is great! I've used it on a few POTA and SOTA activations without any trouble. Thank you for developing it.

I was curious if there are any plans to support FT4?

Thanks so much!

Will it be possible to add support for the (tr)uSDX alpha firmware that supports audio via the cat interface? This device does not have a built-in usb sound card and I haven't had much success with vox. Most times the transmit audio goes out of the phone speaker instead of the headphone cable.

How to setup IC718?
Now I use IC746 setup and I change hex address to 5E.

When a station calls in time window 00/30, and I respond on his cq directly after in time window 15/45. It does not directly Transmits my message.. it waits untile time window 15/45 is over, then goes over to 00/30, and after that back in 15/45 goes to transmit.
This is too late.

I should directly transmit after I hit reply. and partially sends out my message in 15/45. no matter if this time window is already halfway.