N0BOY / FT8CN

Run FT8 on Android
MIT License
357 stars 38 forks source link

Three problems..... #54

Open ZB2ham opened 1 year ago

ZB2ham commented 1 year ago

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.

IMG_20230715_202947688 IMG_20230715_203009648 IMG_20230715_203044448 IMG_20230715_203059225

Rafltdcpa commented 1 year ago

Concerning "Third issue".....did you add the port number 7050 to the device ip address (ie. 192.168.1.5:7050)?

ZB2ham commented 1 year ago

I have tried 192.168.1.5 and 192.168.1.5:7050, both many times, and both equally difficult to reach. In all cases my laptop and smartphone have been connected to my only home network. In both cases the message is the same;

"This site can’t be reached192.168.1.5 took too long to respond"

As I said, my problem could disappear if I knew where in my 'phone the files are stored, then I could transfer the adi file manually - but I cannot locate them.

Many thanks,

Ken

bg7yoz commented 1 year ago

第一个问题:位置归属地在FT8CN中的数据库是正确的,因为Android RecyclerView控件采用了内存复用机制,FT8CN没有采用合理的代码,造成复用其它的Item而没有及时更新位置信息,实际显示成其它QSO的位置信息了。这个问题争取在下一个版本改正。 第二个问题:拼写错误,Gird--->Grid。下一个版本改正。 第三个问题:在开发中没有遇到此类问题,在使用FT8CN之前,请关闭所有后台的APP,也许是其它APP占用了7050端口?请确认手机的ip地址是不是正确,并尝试把访问地址写全:http://xxx.xxx.xxx.xxx:7050。 FT8CN对于QSO数据并没有以adi文件保存在手机中,而是以数据库(sqlite格式)的方式保存的,文件名是data.db,您需要使用数据库访问工具才能查看数据。

ZB2ham commented 1 year ago

The first question: the database of the location attribution in FT8CN is correct, because the Android RecyclerView control uses a memory multiplexing mechanism, and FT8CN does not use reasonable codes, resulting in the reuse of other Items without updating the location information in time, and the actual display It becomes the location information of other QSOs. This problem will be corrected in the next version. The second problem: typo, Gird--->Grid. Corrected in the next version. The third question: I have not encountered such problems during development. Before using FT8CN, please close all background apps. Maybe other apps occupy port 7050? Please confirm whether the IP address of the mobile phone is correct, and try to write the entire access address: http://xxx.xxx.xxx.xxx:7050. FT8CN does not save the QSO data in the mobile phone as an adi file, but saves it as a database (sqlite format). The file name is data.db. You need to use a database access tool to view the data.

Many thanks, v helpful!

The mobile phone I use is a 'phone which I used previously (Samsung J5), a year or two ago and is running Android 6. I did a factory reset before installing FT8CN, and this is the only purpose I put this phone to.

I have just quizzed ipconfig with the command "arp -a" and I have nothing on 192.168.1.5, and nothing using port 7050.

Ken Untitled

bg7yoz commented 1 year ago

也许是网络问题? 你可以使用手机的浏览器访问http://127.0.0.1:7050(不要关闭FT8CN),看看是不是能访问到FT8CN。如果能访问,就是网络问题,如果不能访问,很有可能FT8CN没有启动HTTP服务(如果是这个问题,暂时没有解决办法 :-( )。 good luck! 73!

ZB2ham commented 1 year ago

Maybe a network problem? You can use the browser of your mobile phone to visit http://127.0.0.1:7050 (do not close FT8CN) to see if you can access FT8CN. If it can be accessed, it is a network problem. If it cannot be accessed, it is very likely that FT8CN has not started the HTTP service (if this is the problem, there is no solution for the time being :-( ).

Well, the 'phone can see itself! Which is an end to the problem, because I can now download the file to the 'phone itself and from there I can put it anywhere else! Excellent! problems solved - except I appear to have a network issue to resolve....

Many thanks indeed,

Ken