Describe the bug
Running Octoprint on an Android phone using octo4a. When Octoprint restarts after installing Filament Manager, going to the FM settings gives the "Still initializing check the logs" error. It fails specifically when trying to create a Lock.
Steps to reproduce
- Install and set up octo4a on an android device
- Install Filament Manager
- Restart Octoprint
- Attempt to do anything in Filament Manager
Expected behavior
I expect to be able edit the settings of Filament Manager
Did the same happen when all other 3rd party plugins are disabled?
Yes
Log file
octoprint (15).log
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Direct link to code line causing the issue
After doing some preliminary research on my own it seems multiprocessing tries to create files in /dev which is unavailable on android. I've played around a bit with rooting my device and changing permissions on /dev and still haven't had any luck.
Describe the bug
Running Octoprint on an Android phone using octo4a. When Octoprint restarts after installing Filament Manager, going to the FM settings gives the "Still initializing check the logs" error. It fails specifically when trying to create a Lock.
Steps to reproduce
Expected behavior
I expect to be able edit the settings of Filament Manager
Did the same happen when all other 3rd party plugins are disabled?
Yes
Log file
octoprint (15).log
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Direct link to code line causing the issue
After doing some preliminary research on my own it seems
multiprocessingtries to create files in /dev which is unavailable on android. I've played around a bit with rooting my device and changing permissions on /dev and still haven't had any luck.