We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Frequency Analyzer crashes at random time intervals. Sometimes it can run several hours without crashing, sometimes just a few minutes.
FZ.1 unlshd-078e (...) release-cfw
Nothing fancy, just go to Sub-GHz -> Frequency Analyzer.
No response
The text was updated successfully, but these errors were encountered:
Tried capturing logs via https://lab.flipper.net/. When it crashes all I can see is:
... 16:0:55 [DEBUG] Device: guiStartScreenStream: OK 16:0:55 [DEBUG] Main: systemSetDatetime: OK 21:10:45 [INFO] Main: Flipper has been disconnected 21:10:49 [INFO] Main: Flipper connected 21:11:7 [ERROR] Main: Error while starting RPC: RPC timeout: systemPingRequest 21:11:7 [INFO] Main: RPC started 21:11:23 [ERROR] Device: RPC error in command 'guiStopScreenStream': RPC timeout: guiStopScreenStreamRequest 21:11:23 [DEBUG] Device: guiStopScreenStream: OK
I have set log level to "Trace", Log device - USART, Debug - ON, Heap trace - Main.
Any hints how to troubleshoot this crash?
Sorry, something went wrong.
Update: reverted to stock firmware and Frequency Analyzer works fine there. Running for couple of days with no crashes.
Please stop your investigation and read my reply here in first issue, this one will be closed as duplicate later: #817 (comment)
No branches or pull requests
Describe the bug.
Frequency Analyzer crashes at random time intervals. Sometimes it can run several hours without crashing, sometimes just a few minutes.
FZ.1
unlshd-078e (...) release-cfw
Reproduction
Nothing fancy, just go to Sub-GHz -> Frequency Analyzer.
Target
No response
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: