Confirmed on real hardware: setting POCSAG frequency to 155MHz makes
MMDVMHost exit immediately with "Received a NAK to the SET_FREQ
command from the modem" - the MMDVM_HS_Dual_Hat's ADF7021 chips are
tuned for UHF and can't physically retune to VHF 150-160. Since
MMDVMHost controls DMR/YSF/NXDN/P25/POCSAG through one process, this
takes the whole modem down, not just POCSAG - matches the "DMR turns
red after setting POCSAG" symptom reported.
The earlier commit (that added this range as green/valid) was wrong;
it gave false confidence for a frequency that hard-crashes the radio
service. Back to the original 144-148/220-225/420-450/842-950 ranges.
- Remove admin/config_backup.php (backup/restore page) and all nav
links to it across the admin pages and the expert-mode shared header.
- Remove factory reset: the full-device version in configure.php
(JS confirm, POST handler that reset three git repos + wiped /etc
config, and the hidden form) and the CSS-only version in
expert/edit_dashboard.php.
- Remove the PiStar-Remote and BM API full editors
(admin/expert/fulledit_pistar-remote.php, fulledit_bmapikey.php)
and their links from the expert-mode menu.
- Add a "custom" option to the APRS server dropdown in configure.php
so operators can type their own server + port instead of picking
from APRSHosts.txt; wires the port through to ircDDBGateway,
YSFGateway/YSF2DMR/YSF2NXDN/YSF2P25, and APRSGateway (previously
only the hostname was ever configurable, port was hardcoded 14580).
- Extend the POCSAG frequency band validator (functions.js) to also
treat 150-160MHz as a valid/green range.
yuancheng