Structured Bug hunting
This issue should help, checking all FreeDATA components in a structured way. If a component is going to be inspected, it can be marked as checked and new issues can be opened in case of bugs. There is no timeline, but work should focus on this continuously
Scope: Desktop and Tablet usage
It's a work in progress yet!
GUI General Layout
- [x] Modem health check
- Close button needs more space in mobile devices ✅
- Start/Stop of server not working reliable #874
- [x] Left Navigation Bar
- [ ] Footer Navigation Bar
- [x] #837
- [ ] hidden on android based tablets, see #846
- [x] Popups
- #837
GUI Main screen
- [ ] Grid-Settings Navigation Bar
- [ ] Grid-Settings Clear / Save / Restore
- [x] Grid-Settings default screen items
- [x] Grid-Item: Activities list
- #837
- [x] Grid-Item: Heard Stations list ( detailed )
- #837
- [x] Grid-Item: Heard Stations list ( small )
- [x] Grid-Item: Audio main
- [x] Grid-Item: Dbfs meter
- [x] Grid-Item: Tune widget
- [x] Grid-Item: Beacon button
- [x] Grid-Item: Broadcasts main ( horizontal )
- [x] Grid-Item: Boradcasts main ( vertical )
- [x] Grid-Item: CQ button
- [x] Grid-Item: Ping widget
- [x] Grid-Item: Frequency widget
- [x] Grid-Item: Rig control main
- [x] Grid-Item: S-Meter
- [x] Grid-Item: Tx/PTT Indicator
- [x] Grid-Item: SWR
- [x] Grid-Item: Stats ( waterfall ... )
- [x] Grid-Item: Scatter graph
- [x] Grid-Item: Speed/SNR graph
- [x] Grid-Item: My callsign widget
- [x] Grid-Item: My callsign widget (small)
- [ ] Grid-Item: Stop widget
- [x] Grid-Item: Station Map
- #839
GUI Chat Screen
- [ ] Layout
- [x] Start new chat
- [x] Conversations area
- [x] Conversation items
- [x] Chat top navigation bar
- [ ] Chat top navigation bar settings ( beacon history, delete chat )
- [x] Compose new message
- [x] Compose new message - add attachments ( image, files ... )
- [x] Compose new message - emoticons
- [x] Transmit message item
- #838
- [x] Receive message item
- [x] #837
- [x] #838
- [x] ADIF logging
- [x] Repeat message
- [x] Message info
- [ ] Delete message
GUI Settings Screen
- [x] Layout
- [x] Station settings
- [x] GUI Settings
- [x] Chat settings
- [ ] Rig control settings
- [x] Modem settings
- #874
- [x] Web settings
- [x] Exp settings
- #886
- [x] Link settings
Server
- [ ] Start server after installation
- #874
- [ ] Load config from custom location
- [ ] Load database from custom location
- [x] API Endpoints
- [ ] Callsign Blacklist
- [x] Installation Scripts ( Linux )
- [ ] Remove unneeded code and tools
- [ ] Events are correctly
- [x] Heard stations is filling all information correctly
- [x] CPU usage is ok
Documentation
- [ ] API Documentation
- [ ] Installation ( !!! )
- [ ] Reduce wiki so its as simple as possible without missing information
- [ ] Known problems
I've do several tests regarding to the Linux installation. Debian 11, install OK, works, CPU normal Debian 12, install OK, works, CPU normal Ubuntu 22, not tested Ubuntu 24, install OK, works, CPU normal Fedora 40, not tested Fedora 41, works if VERSION_ID=41 is added to the Fedora install section. Raspberry Pi 4 aarch64, install OK, works, but CPU is over 95% most of the time.
Two notes: Maybe the script should check if the user is in the sudo group. This would help newbies. Depending on the used transceiver, the user needs to be in the dialout group. If it is not, everything works fine, but the radio would not respond. Or just mention this in the installation dokumentation.
Added support for Fedora 41 to the install script.
I've added a check for the account being in the dialout group in the install script, and exits with a warning if it isn't there. Checking if an account has sudo privs is a little more complicated, so I opted to simply write out a warning on the screen saying if the sudo command fails with "Sorry", or "not in sudoers file", or something to that effect, to make sure your account has sudo privs. At least this gives a hint of where to look if there is an issue.
@LA3QMA any news regarding deleting messages? If its working, just let me know, so we ken mark this task as "checked"
The message is now deleted from the table "p2p_message" and "message_attachment" when i delete it from a individual message. But the attachments is still in the table "attachment". Using the "Delete Chat" i think also deleting the attachments would be useful
Also at restart there is a check now if orphaned attachments are there. Maybe this solves this in your case because of old unclean state