Hier eine Bug-Doku von Jason Reilly in englisch:
In der Version 3.1.1 bzw. 3.1.2 wurden ca. 13 bekannte Bug beseitigt. Also Software updaten. Mittlerweile ist die 4.08 draußen.
Well done to Radioddity GD-77 – New firmware / CPS v3.1.1, here’s THIRTEEN bugs (that I know of) that have been fixed in this release:
Radio will self transmit in analogue VFO mode
FIXED IN 3.1.1
If in VFO mode with analogue FM, but if DCDM option is set, but greyed out, radio will begin to
transmit an unmodulated carrier with no visible indications of transmit.
Stuck half way between memory & VFO mode.
FIXED IN 3.1.1
Start in double wait mode off. Set radio into memory channel scan. Leave scan going. Then press right
arrow to try to enter VFO mode. Then stop scan. Radio is stuck in a halfway mode somewhere
between memory mode and VFO mode. To clear the situation, press right arrow again.
Top panel LED in DMR mode
FIXED IN 3.1.1
While scanning a DMR mode channel, the green LED goes off when a new DMR ID begins transmitting
if the RF carrier signal does not drop in between the two DMR ID transmissions. Once RF carrier signal
disappears, the green LED operation returns to normal again. This problem is only apparent while
scanning, if sitting on a DMR channel and not scanning, LED operation is normal.
Scan channels above 256th channel
FIXED IN 3.1.1
In the CPS, you can’t enter a channel into a scan list if it is the 256th or above channel. Confirmed this
is an issue with the way the CPS generates data for the codeplug.
Viewing scan channels by radio menu for channels above 256
FIXED IN 3.1.1
When using the radio menu to view scan channels in a scan list, any channels above 256 show as blank
or corrupted. This is a firmware issue.
Contact above the 256th contact can’t be entered to a channel
FIXED IN 3.1.1
In the CPS, you can’t enter a Contact into a DMR channel if it is the 256th or above contact. Confirmed
this is an issue with the way the CPS generates data for the codeplug.
When transmitting on a DMR channel with a contact above 256, the radio will place that call to the wrong contact. This is a firmware issue.
FIXED IN 3.1.1
