gopro / labs

GoPro Labs
Apache License 2.0
451 stars 39 forks source link

Labs command randomly continues after restart #720

Open hwy0010 opened 6 months ago

hwy0010 commented 6 months ago

Hi,

I scanned a qr few days ago: 'mVcFoMLOGB=400oMWIDE=1oMNR01=1' I only want to shoot log once, so I use oM, I believe it will reset to normal after restart. But after restart the camera shoots log videos randomly, I find a 'qr.bin' file in the TF card, its content: 'mVcFoMLOGB=400oMWIDE=1oMNR01=1'. When I shoot with a different card without this 'qr.bin', the camera acts normally.

Uploaded my 'QRLog' file since I scanned the QR code. qrlog-0104.txt

My Device is H11, when the log shows Continue command:mVcFoMLOGB=400oMWIDE=1oMNR01=1, it shoots log video, and it shoots normal video when it doesn't says 'Continue command'. I have my device connected to a external power without internal battery.

dnewman-gpsw commented 6 months ago

The reading of qr.bin is not directly the issue, that is happening because the camera is crashing just before, and the camera is trying to restore the last action (you are correct this is a stale qr.bin file.) However the camera should not be crashing.

[2024-01-10 16:03:32-delayed] wake reason:POWER_BUTTON 
[2024-01-10 16:03:33] Labs:Display Messages 
[2024-01-10 16:03:37] Features activated:  24HZ: 
[2024-01-10 16:03:38] Labs:Main Start 
[2024-01-10 16:03:38] Labs:H22.01.02.20.70 
[2024-01-10 16:03:38] Labs:Initialize 
[2024-01-10 16:19:50-delayed] wake reason:HEARTBEAT_TIMEOUT 
[2024-01-10 16:19:54] Labs:Display Messages 
[2024-01-10 16:19:55] Features activated:  24HZ: 
[2024-01-10 16:19:55] Labs:Main Start 
[2024-01-10 16:19:55] Labs:H22.01.02.20.70 
[2024-01-10 16:19:55] Labs:Initialize 
[2024-01-10 16:19:55] Continue command:mVcFoMLOGB=400oMWIDE=1oMNR01=1 

At 16:03:32 you powered on, and no other Labs commands where issued, but you may have been recording normally (not shown.) At 16:19:50 the camera awoke from a crash. Were you recording? What do you remember happening? The 24HZ extension seems to be the only thing permanent, are you shooting 24p modes? If so, which resolution and lens setting?

Do a factory reset, and format your SD Card, see if it reoccurs.

hwy0010 commented 6 months ago

Thank you, David.

I'm not shooting 24p modes, I'm shooting with 5.3K60P Linear HyperSmooth off, and the crashes are often caused by overheat, and I restart the camera after overheat, then this happens. I know that format my SD card will work because it won't remember what I scanned before, but my question is, how can this recover from crash thing read commands from days ago, I mean it's ok to read command that it was using before crash, but I didn't scan that log QR code for days, is it a bug?

dnewman-gpsw commented 6 months ago

There is a bug, but I an overheat should NOT cause a HEARTBEAT_TIMEOUT, so I still think there is something that is misconfigured on your camera. When a camera overheats, it knows it is too hot and shutdowns to protect itself, it is not a crash. Something else is crashing your camera.

You can also set !MDBGL=1 (to enable more debug logging)

I run 4K120 at 150Mb/s, and got thermal shutdown at 20 minutes, but it did not crash.

hwy0010 commented 6 months ago

I will try enable debug for more information next time, but it did says HEARTBEAT_TIMEOUT in the log.