BG7PUW The main interface also incorporates the call sign as a design element, which can be customized to your preferences.
Regarding the issue of displaying time on the calling page: Both WPSD and PI-STAR do not transmit time data on the calling page; only the MMDVM main page updates the time. If you want to display the time on the calling page, you can either set variables on each page and update them using a timer, or simply not do it (which is essentially just being lazy).🤪)。 Alternatively, you could use a screen with an RTC (Real-Time Clock), which simplifies the implementation of time codes (although only K0 and X5 currently support this).
Regarding the issue of not displaying the flag: The code in my firmware that displays the flag in DMR mode retrieves data from "t17.txt" and "t22.txt" via serial port, which are then used to determine the country based on the "COUNTRY" column in the RadioID database. If the system does not provide this data, it will not display the country or flag. The most likely reason is that the RadioID database (stripped.csv) contains incomplete information. I found that many call signs in the RadioID database have empty values for the "COUNTRY" column, which could also be due to a code issue. There were no abnormalities detected during the monitoring test on the TG91 previously.
However, in modes such as YSF, the national flag code is determined by the call sign. I modified PD0DIB's code to include a province-specific judgment function, but I haven't tested it specifically.
Providing more specific details, such as the mode and the friend's callsign without displaying the flag, would be helpful in identifying bugs. Providing the original data would be even better.