bug: after sending a string of DTMF using the * key, next keypress is eaten.

[prokrypt]

Affects all keys except for PTT and channel buttons, both short press and long press.

[armel]

Sorry, I don't understand where is the problem.

[prokrypt]

Ah, while trying to make a video, I discovered the problem is a little more complex...

• Turn on radio
• Press "*"
• Input some DTMF
• Press PTT to send
• Press "*"
• Press PTT to send
• Next keypress (other than PTT or up/down) is ignored.

It doesn't ignore the subsequent keypress the first time after boot, but will do so every time after.

[prokrypt]

demo.mp4

[armel]

Ok.
I have no idea where this is coming from.
I tag the issue as a bug, if someone wants to take care of fixing it.

Armel F4HWN.

[prokrypt]

demo2.mp4

getting closer to figuring it out... maybe

[f1ixx]

Hello

I read and try to understand. Waw, high level for me.
But after many UART_printf to read data, may flash, i make this :
in file app/app.c :
line 1872 :

if (!bKeyPressed) {
	bFlag           = true;
	gPttWasReleased = false;
	}

change to

if (!bKeyPressed) {
	//bFlag           = true;
	gPttWasReleased = false;
	}

I make small test and it sames to work but but but as usual, fixes
a bug adds new bug(s).

If more harm than good, return to the origin and/or report the new problem(s)

Forget idea. Thank's

73's
Boris

[prokrypt]

@f1ixx getting very close! That does indeed fix the problem, but it is probably the wrong place to change code as it introduces a new bug:

• press * twice. oops!
• press * once then long press * again. hmmmm... interesting.

[prokrypt]

I tried to have a go at it...
comment out line 681 (gPttWasReleased = true;) in main.c:

uv-k5-firmware-custom/app/main.c

Line 681 in 15ff3d1

gPttWasReleased = true;

It seems to work fine so far. Hmm.

[prokrypt]

I've been testing this for the past few days, still no bugs! 🎉

[armel]

Ok thank you 👍🏼 This issue will be fiexed in the next version.