I was almost there, getting error messages that made no sense, string division in a script that literally has no division in it !?!?!?!?

The program does not crash anymore, because I now have the csv files copied to the correct directory on first run only. The error messages are properly read even though I wrapped them in a tuple to return properly... the error just makes no sense.

I finally configured docker to keep a persistent container, wrestled with the kivy buildozer.spec file (the mother of all configuration files) and got a crash course on using String Search in Windows power shell, which is much better than running the android debug bridge from an elevated command line (that's just running CMD as administrator)

The maddening part is the app worked except for reading stale data... fix that and the functions break... I even asked the LLM about the error when the stack overflow search returned nothing useful (nor did the kivy site documentation), and the LLM had no idea... perfect!

Won't have a chance to get back to it until at least Wednesday, and then the plan is to add more diagnostic print statements to each python file that stands between game select and game action screens. Maybe the kivy discussion on discord or reddit may turn something up... but usually if it cannot be found on stack overflow, then it cannot be found... hey, at least the Windows version of the app is 100% functional!