You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using Read RAW under the Sub-GHz module, after it's done recording, tapping left will not erase the recording completely (it only seems to clear the screen). The raw recording will still appear under Saved
To Reproduce
Press OK button
Sub-GHz -> Read RAW
Press OK button to record
Press OK button to stop recording
Press Left to delete
(screen clears at this point)
Go back one menu
Select Saved
Raw_signal_ file will be present
Expected behavior
Seems like it should erase the RAW recording completely, not just clear it from the screen? At least that's what I gather it should do
Additional context
It make me sad :(
The text was updated successfully, but these errors were encountered:
no, it shouldn't. when recording a RAW file, the file is immediately written to SD, since the flipper does not have enough RAM to store such large files, with a new recording, the old file will be overwritten and a new one will be written or renamed when saving. but if suddenly you pressed the wrong button, you still have a chance to save the record by renaming the temp file manually
And here I got all excited cause I thought I was helping :(. Perhaps, the wording needs to be changed to be more clear? I know I wasn't the only one who thought this was a bug.
Anyway, thank you for all your work 🙏🏼🙏🏼🙏🏼. Uh, I'll let you close it, I'll keep it open just in case lol
Describe the bug
When using Read RAW under the Sub-GHz module, after it's done recording, tapping left will not erase the recording completely (it only seems to clear the screen). The raw recording will still appear under Saved
To Reproduce
Expected behavior
Seems like it should erase the RAW recording completely, not just clear it from the screen? At least that's what I gather it should do
Additional context
It make me sad :(
The text was updated successfully, but these errors were encountered: