-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The back button hangs when using a subghz file #854
Comments
Not sure, but it can be not bug but a feature. Check with long press back button. |
Definitely not a feature when it takes multiple presses, long presses, and
it still may not exit.
…On Wed, Jan 15, 2025, 2:57 AM Dmitry422 ***@***.***> wrote:
Not sure, but it can be not bug but a feature. Check with long press back
button.
—
Reply to this email directly, view it on GitHub
<#854 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AULD4GYROWQPJYOPWQQ326L2KW57TAVCNFSM6AAAAABU24KC66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJRGQ3TCOJXGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I try replay your problem in dev.build - but I can't. |
https://imgur.com/a/yLKEzgx
Video of the issue. As I said it doesn't occur every time in Subghz, but it occurs often. Sometimes I literally wonder if it will ever "catch"
As I said this in no way happens on/in any other app.
…On Wed, Jan 15, 2025, 7:36 AM Dmitry422 ***@***.***> wrote:
I try replay your problem in dev.build - but I can't.
From shortcuts and from sub-ghz app - short press not exit (its normal)
and long press exit every time when I long press key.
—
Reply to this email directly, view it on GitHub
<#854 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AULD4G2ONMNBFBYPN7X7HDT2KX6WDAVCNFSM6AAAAABU24KC66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJRG42TONZUGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I sow 2-3 short (not exit) and after 1 long press (exit). Its right ? |
Long doesn't always exit. Seriously, with the Tesla raw, when the bug
happens, it makes me wonder if I will have to let the battery die.
In addition why would MMX deviate from short press exit that is in every
single other app, and if he did why is it not in any changelog?
I don't understand why you are trying so hard to make aberrant behavior
seem like it's "correct".
I have been on unleashed since v 1x. This behavior is not "normal"
…On Wed, Jan 15, 2025, 12:47 PM Dmitry422 ***@***.***> wrote:
I sow 2-3 short (not exit) and after 1 long press (exit). Its right ?
Looks like all work correct.
—
Reply to this email directly, view it on GitHub
<#854 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AULD4G6W2PFD3YX67OR3COT2KZDFRAVCNFSM6AAAAABU24KC66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJSGQ4TAMZQGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Here you go.
Multiple long presses doing nothing. If I had this issue in every app, I would think it was my button, but it has never happened to me in any other app.
This is a bug.
https://imgur.com/a/6EDsdLO
…On Wed, Jan 15, 2025, 1:14 PM ***@***.***> wrote:
Long doesn't always exit. Seriously, with the Tesla raw, when the bug
happens, it makes me wonder if I will have to let the battery die.
In addition why would MMX deviate from short press exit that is in every
single other app, and if he did why is it not in any changelog?
I don't understand why you are trying so hard to make aberrant behavior
seem like it's "correct".
I have been on unleashed since v 1x. This behavior is not "normal"
On Wed, Jan 15, 2025, 12:47 PM Dmitry422 ***@***.***> wrote:
> I sow 2-3 short (not exit) and after 1 long press (exit). Its right ?
> Looks like all work correct.
>
> —
> Reply to this email directly, view it on GitHub
> <#854 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AULD4G6W2PFD3YX67OR3COT2KZDFRAVCNFSM6AAAAABU24KC66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJSGQ4TAMZQGU>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Finally we can make a tests - you try dev build and me try you file. And after we can find right answer for this bug. |
|
Hello! |
As I have said MULTIPLE TIMES it is intermittent, also why I provided a video. Just this morning i tried it 20 times without triggering the bug. I am not going to go through this any more with you. You started off by telling me "long press for back is a feature" even when I told you it isn't and there was no changelog stating that change was made. Now you said "well I tried it 3 times so there is no issue" despite two literal videos. While I find flipper's source too abstracted, I have contributed numerous features and fixes to both Radiolib, Rfcat and others and I can write C and C++ well enough to do what I want (if inefficiently). I am not an unreliable reporting source. This issue will stay open because it is a bug, with proof, both on the decoded as you observed with 2-3 short presses doing nothing, and on the raw with multiple long presses doing nothing. |
Im not often use sub-ghz - my experience not so big. In some cases like barriers (locks) sub-ghz record exit only with long press, in another cases like your file exit by short press. So different cases - different presses. I think in your cases may be hardware problem with key pad. But if you sure that isn't hardware - no problem, will be wait the same reports from another users. |
No. Long press is not a thing with the back button in subghz.
As I have previously mentioned, if it was the keypad it would happen in ALL
apps. It doesn't.
…On Sat, Jan 18, 2025, 5:26 PM Dmitry422 ***@***.***> wrote:
Im not often use sub-ghz - my experience not so big. In some cases like
barriers (locks) sub-ghz record exit only with long press, in another cases
like your file exit by short press. So different cases - different presses.
I think in your cases may be hardware problem with key pad.
—
Reply to this email directly, view it on GitHub
<#854 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AULD4GZXKOYY2CAL2C4CFKL2LJ6DDAVCNFSM6AAAAABU24KC66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJZG43TMMZWGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Additionally if this were a hardware issue, decoded subs that "stick" would exhibit the same "long press doesn't exit" they don't. A long press always exits a decoded sub. Raws hang for forever when they hang |
"No. Long press is not a thing with the back button in subghz." - my barrier subghz record exit only with long press. In subghz source we can find string if(event->key == InputKeyBack && event->type == InputTypeLong). And did you try last dev build ? |
Describe the bug.
Pressing the back button is not always responsive when using a Subghz file. This is not the case in any other app or when using any other function. It is worst with RAW's but still exists when using decoded protocols. It feels like a function is blocking.
Subghz menus are fine. It only appears after selecting a file to playback and not every time, but it is fairly frequent. It happens heavily with the Tesla Charge port files.
Reproduction
Favorites or subghz via a shortcut, select a file, Select Emulate (if not a raw), play it, press back. It does not go back often necessitating multiple fast presses, holding the back button, etc.
If you do not experience the issue, repeat the above a few times, going into a file, playing and trying to exit
Target
This did not happen with v73, but is present in the most recent 79 and the version previous to that (when I first updated past 73)
Logs
Video:
https://imgur.com/a/6EDsdLO
No response
Anything else?
Happy to provide a video if needed.
The text was updated successfully, but these errors were encountered: