The diagnostic prints proved instrumental in zeroing in on the issue, the Android path join was being read as a string division error, so a change to the correct path for Android solved days of frustrating troubleshooting.

Updating works as well, so now the start of the pick5 cycle will be done from the phone!

There will undoubtedly be a few minor cosmetic changes as I take time to go over every screen with both the windows and android versions, but everything is holding up well. Hard to believe my Python app, which uses Numpy, Pandas, requests, beautiful soup 4 AND reads and writes to csv files is alive on 2 different platforms...

I was giving myself ALL of 2026 to get to this point... got there with PLENTY of time to start the other projects I have planned.

Also nice to know that my OLD MSI G62 Apache Pro is up to the task after all of these years. I bought that to start going part time for a degree in 2016... graduated in 2023 (not exaggerating the part time aspect), and have always used it to practice the Python coding craft.

Cannot update to windows 11 (too old, according to Microsoft), 16GB of RAM and a 1TB SSD... powered through building this app inside of a persistent docker container from the WSL/Ubuntu Linux command line, one big 6 hour build to start, a smaller 3 hour build when I realized I did not need a 32 bit version of the app, dozens of troubleshooting rebuilds (about 10 to 15 minutes each), side loading the APK onto my phone from a USB cable, running ADB in windows power shell... all on a completely unknown (to me) tool chain that included kivy, kivyMD, Docker, WSL, Buildozer (a tool for packaging python apps for Android, P4A, a tool for running Python apps in Android's OS, Inkscape for the graphics... so much stuff to get a handle on all at once., and now I have the app right in my hand... crazy!