I confirm that I have read the CONTRIBUTING guide before opening this issue.
I confirm that I have read the FAQ before opening this issue.
I am running motionEyeOS version: motioneyeos-raspberrypi-20190911.img.
I am using the following board/model: Raspberrypi zero w.
I am using the following type of camera: Raspberrypi zero w camera.
My camera model is: Raspberry pi camera v2.
My motionEyeOS unit is connected to the network via: WiFi.
I consider the following log files relevant to this issue:
MotioneyeOs keeps getting errors and then rebooting after awhile.
There's a huge number of stack traces in your dmesg.log. I'd suspect a hardware issue (including possible overheating).
Or you could remove Raspberry Pi 1/Zero from the supported devices and get far less bug reports like this. It is too weak hardware. It gets the same treatment by almost all the open source projects out there. Nobody is interested in investing serious time to optimize for such weak hardware. The CPU is the same as used in the first Roku device and worked fine as a simple Netflix set top box SoC with properly optimized OS (with licensed VideoCore stuff I bet).
Nobody really cares about the Zero or firs gen Pi for anything but simple GPIO/sensor stuff. I'm sure the Raspberry Pi 2 is also going to be soon forgotten.
Nobody really cares about the Zero or firs gen Pi for anything but simple GPIO/sensor stuff. I'm sure the Raspberry Pi 2 is also going to be soon forgotten.
I have several Zero W devices running MotioneysOS...they are fine.