FlipperZero crashed while idle (Deep sleep)

[UrSuLa360]

Describe the bug.

Unleashed version 046e I leave flipper zero with screen locked and after a while i found "Flipper crashed and was rebooted NULL pointer dereference" on screen.

I also found "Flipper crashed and was rebooted furi_check failed" message

Reproduction

Flipper with Unleashed version 046e Linked to Flipper iOS app via bluetooth Just lock the screen and leave it. The error will appear (you need to wait some hours, i found it three times in three days)

Target

os

Logs

Some logs i could recover:
Log 1
[23:24:45][error]: COUNTLY_APP_KEY not found
[23:24:45][info]: session started
[23:24:49][info]: canceling tasks...
[23:24:49][info]: canceling tasks done
[23:24:49][info]: session started
Log 2
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][debug]: widget connection time is out
[20:42:09][info]: session started
[20:42:10][info]: canceling tasks...
[20:42:10][info]: canceling tasks done

Anything else?

No response

[UrSuLa360]

Still happening in 047e.

A new error message appears "Flipper crashed and was rebooted MPU fault, possibly stack overflow"

[UrSuLa360]

The bug doesn't happen if you change the sleep method for FlipperZero to legacy.

Settings-> System ->Sleep Method = Legacy (No crash) Settings-> System ->Sleep Method = Default (will crash)

[UrSuLa360]

Still happening in 048e.

Only me having this bug? 😓

[TheWebMachine]

I haven't had this problem at all. 🤷🏻‍♂️ Maybe you just have a faulty unit?

Edit: I have 0045

[T3CHKOMMIE]

48e here. I've had the idle crash the last two days

How can I help diagnose?

I have flipper connected to android BT app. I don't lock the flipper. Usually happens over night when I come into work I see the crash message first thing in the am.

[K-Dog98]

When I try uploading, the new firmware unleashed to my Flipper zero using the iOS mobile app it gets to about 70% and then says couldn't connect to Flipper. Has anyone got some ideas on what to be going on?

[xMasterX]

This is a known issue that happens only on Some flippers, not at all units, no, its not a hardware fault, issue comes from core 2, and can be fixed in software, official team is working on solution, also its very hard to debug since core2 cannot be debugged, debug interface is not accessible, and its firmware is encrypted and closed, we can use binary files provided by manufacturer

DO NOT do factory reset, or any other things, just wait for fix, all will be published as soon as it gets done

[FoxLy1312]

Use a short cable like the original one Am 12. Mai 2023, 23:46 +0200 schrieb Sam Unknow @.***>:

Do a factory reset first, mostly if i got this problem internal storage is full Am 10. Mai 2023, 22:27 +0200 schrieb K-Dog98 @.***>:

When I try uploading, the new firmware unleashed to my Flipper zero it gets to about 70% and then says couldn't connect to Flipper. Has anyone got some ideas on what to be going on? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[xMasterX]

As temporarily solution, you can try using this - Settings -> System -> Sleep Method = Legacy Battery life will be as on older releases We can't say when fix will be ready, since it depends from ST, chip manufacturer, core2 runs closed encrypted firmware made by them

Also as we find out, only some flippers are affected, but there is nothing similar between them, revision, manufacturing date, this is fully random So if you have 2 flippers and only one of them crashes, that doesn't mean its chip revision or manufacturing defect, core2 happens to act a bit different on some devices which has nothing similar between them Current solution -> Use it with Sleep Method = Legacy and wait for next updates

[UrSuLa360]

Core2 (Crash in idle) issues was reduced to current possible minimum, you can try using DeepSleep again (Sleep Method = Default) (+ more checks was added, if you get Slow HSE/PLL startup message more than one time, create issue with steps what to do to reproduce it again)

Still happening in 053. Anything you need to help let me know

[niko-lay]

I have faced same issue with 052 firmware, flipper connected via Bluetooth to ios (looks like it start doing auto-connect few versions ago) and stay locked for few hours. Also sleep method=default Error message on screen: "Flipper crashed and was rebooted. STR(R) Copro(R) HardFault"

[niko-lay]

I have faced same issue with 052 firmware, flipper connected via Bluetooth to ios (looks like it start doing auto-connect few versions ago) and stay locked for few hours. Also sleep method=default Error message on screen: "Flipper crashed and was rebooted. STR(R) Copro(R) HardFault"

just googled few and found this is known issue with https://forum.flipperzero.one/t/message-on-screen-flipper-crashed-and-was-rebooted-st-r-copro-r-hardfault/16948/2

[EvanVS]

This is still occurring on the 055 release. Had it happen 5 times in the past 48 hours. This is on the default sleep setting.

[xMasterX]

Test it with latest 064 release, should be fixed now

[UrSuLa360]

Testing for next 2 days, if no error found will close it. Thank you @xMasterX for your work

If anyone want to test this issue, please dont forget this steps: 1. Update flipper with 064 of unleashed version 2. Settings-> System ->Sleep Method = Default

[UrSuLa360]

No trace of the error during last 2 days on my unit. Closing the issue.