Full FT8 mode integration (user chose scope C: complete port, keep original visual style): - feature/ft8 module: 213 Java classes from FT8CN 0.93 source (com.bg7yoz.ft8cn namespace preserved so code needs zero changes), DataBinding enabled, BuildConfig fields (APPLICATION_ID/VERSION_NAME/ apkBuildTime) restored for AGP9 - libft8cn.so from the user's FT8CN_0.93 APK (armeabi-v7a, 1.53MB; differs from repo copy, APK version used) - 237 res files + 58 assets + 4 local libs (MPAndroidChart spectrum, commons-net, nanohttpd, osmdroid map) copied verbatim - Proguard keep rules for JNI classes (RegisterNatives) - Entry: More menu "FT8" (default sub menu, after AMSAT) launches MainActivity via Intent (external activity, LAUNCHER filter removed to avoid double launcher) - Manifest merged via module (RECORD_AUDIO/BT/location perms) - Version 4.5.5/455 + What's new 5 languages (REPLACED per rule) Verified: :feature:ft8:compileDebugJavaWithJavac + :app:compileDebugKotlin BUILD SUCCESSFUL; check_strings 9 files OK.
3 lines
543 B
Plaintext
3 lines
543 B
Plaintext
关于发射监管
|
|
与JT65等协议的1分钟通联时序,用户可以有大约10秒钟的时间来决定是否继续下一阶段的动作,而FT8和FT4的较短序列需要更快的响应,在实际使用中需要软件内置适量的自动化,这就是FT8CN中使用自动程序的原因。
|
|
FT8CN赞同乔尔·泰勒理念,反对使用机器人用于FT8操作,只能有限度地使用自动化程序,所以FT8CN要对自动程序进行监管,当无人干预超过发射监管时间限制后,发射程序将自动停止。 |