Skip to content
New issue

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

Unable to Initialize Database on Android #239

Open
impatman opened this issue Nov 20, 2021 · 1 comment
Open

Unable to Initialize Database on Android #239

impatman opened this issue Nov 20, 2021 · 1 comment

Comments

@impatman
Copy link

impatman commented Nov 20, 2021

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

  1. Install and set up octo4a on an android device
  2. Install Filament Manager
  3. Restart Octoprint
  4. 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.

@jaavalli
Copy link

I have the same issue with this as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants