OpenGD77

Like me, Mike
(My usual setting for the level of "beep" is -9dB or -12dB)

n1id wrote: ↑

Thu Jan 16, 2020 1:58 pm

I placed this latest update on all 3 of my GD77s Audio sounds great. For me one one GD77 i didn't have beep till i just turned it off and on again.. Actually I wouldn't mind an option to shut off the startup beep. That was i can get on and not wake anyone!! Thanks it is working great here

to disable the sounds at startup you must enter the EXTRAS menu and under the OPENGD77SUPPORT item you must delete the string BOOT TUNE.

I loaded the firmware into both of my GD77s and they are working fine, however, one of them no longer does the boot CW at startup, the same as Thierry reported. As others indicated, increasing the BEEP level from my usual -18dB to +3dB restores it. Not a big deal but just reporting that I am seeing that little anomaly as reported by others.

Thanks for the update!

73, Rob W1AEX

ADDED NOTE: Curiously, when I operate both GD77 radios side-by-side there is a noticeable difference in the delay of received DMR audio with the unit that does not produce the beep tones at startup compared to my other unit with the same firmware. I'm wondering if one of the units does not have the 1 frame buffer active for some reason.

Thanks for the feedback, Rob, that confirms this weird reaction to this version on some GD77s.
The solution I experienced is very simple, but the problem needs to be deepened by our specialists
Good luck for them

to disable the sounds at startup you must enter the EXTRAS menu and under the OPENGD77SUPPORT item you must delete the string BOOT TUNE.

Or if you have a custom opening screen you can have a "tune" like 0,30 which will not play a sound but will allow the custom screen to display for a short period of time.

did the cpu optimization improved the refresh rate of the signal meter on screen? because it is alot faster and better? im just curios and want to know if the code was changed or it was the improved cpu usage on decode optimization.

Riku wrote: ↑

Thu Jan 16, 2020 8:40 pm

did the cpu optimization improved the refresh rate of the signal meter on screen? because it is alot faster and better? im just curios and want to know if the code was changed or it was the improved cpu usage on decode optimization.

I did not notice an improvement in signal meter response, but I was not specifically looking for that sort of thing.

Seems like the battery drains faster with that firmware. Normally I listen on a group with not much traffic and the battery has to be charged every 3 days. Yesterday I changed firmware and battery is on 55% after half day listening. I have no proof for that, it just feels like.. Gonna have a closer look at this the next days..

I have a radio which is supplied only via a PSU, and no battery.

I compared the current drain when not receiving and it was the same on this version as on the version from 25th December.
When just listening on DMR with no signal, the current consumption is 83mA, and when a signal is received the current rises to 87mA

These values are with the display backlight set to Manual so that the backlight was not on.

The backlight takes around 20mA when on full brightness.

backlight turns off automatically after 15 seconds.. as I said before, I have no proof, it's just a feeling..