I am trying to run Notebook on the padlets of my students for my course on Python. The Région provides each year new students in high school with a padlet ; this year, like the last one, they are Lenovo padlets running on Android. But this time I cannot run Notebook.
More precisely, lauching Notebook in the terminal of Pydroid3, I have a few seconds to open or create a file, writing a piece of code and run it. But in a minute, I cannot run new scripts anymore, the mark at the beginning of the cell stays on [*]. After that, the message “File save Error for Test.ipynb / NetworkError when attempting to fetch resource” pops up. If I try to restart it, the Kernel is “Unknown”.
I would like to find a simple solution so that the students could fix the problem themselves, directly on the padlet.
P.S.: Last year, we just had to install Pydroid 3 from Playstore on the already Lenovo padlets with Android, install the repository plug-in also from the Playstore, “quick install” Jupyter with (the GUI for) Pip in Pydroid 3 and Notebook worked perfectly well.
Guessing that your issue may be that the working directory which Jupyter sees is not writeable.
I have previously tried to run Jupyter Lab within Pydroid on my Android device - and found it difficult to set the working directory for the ipynb files.
I just tried an another approach which seemed to work.
I have a directory /Documents/Pydroid in the regular “Internal Storage” area.
Run Pydroid, and run Terminal.
Change directory via
cd Documents/Pydroid
Then enter command
Jupyter Lab
That started up Jupyter Lab with the selected working directory. I could create and save an ipynb file
Doing this on an Android 12 phone. Not rooted or otherwise set up specially.
Hi, pretty sure you’ve already solved this, but I ran into the same issue on my Galaxy Tab, and after a lot of trying the apparent solution for me was very surprising: battery management. My jupyter lab server in Pydroid3 kept crashing after about a minute. I now changed the battery settings for Pydroid and for the add-on from ‘optimized’ to ‘unrestricted’ and the problem appears to be gone. Server continues to run for > 10 mins. Thanks to Google AI mode!