Skip to content
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

Sub-GHz Read RAW function does not completely erase when tapping Erase #1252

Closed
pliable opened this issue May 20, 2022 · 3 comments
Closed
Labels

Comments

@pliable
Copy link

pliable commented May 20, 2022

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

  1. Press OK button
  2. Sub-GHz -> Read RAW
  3. Press OK button to record
  4. Press OK button to stop recording
  5. Press Left to delete
  6. (screen clears at this point)
  7. Go back one menu
  8. Select Saved
  9. 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 :(

@pliable pliable added the Bug label May 20, 2022
@Skorpionm
Copy link
Member

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

@pliable
Copy link
Author

pliable commented May 20, 2022

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

@Skorpionm
Copy link
Member

#1262
fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants