With this app, ALL of the engineering happened on the windows side. The Android part was basically assembling the app from the blueprint I had made in windows.

The plan...

I know that I must copy the csv from the data folder to the folder in the app that holds user data. I need to see what that path is so I can get it there. So, I am recompiling with some diagnostic prints that will spell out the path clearly in the ADB (Android Debug Bridge) logcat output, filtering the exact output of that print statement rather than going through thousands of lines of output. The print statement will reveal the exact path to the user data folder... then I will have my destination to put into the config file that will make the data "live" and will allow appending draws with the updater. Right now the "data" folder in the project files is read-only. This should be the last step in having the app 100% functional on 2 platforms!

And the ultimate test for data validation will be to match exact output of the windows and android versions for a few table and stats screens... 100% match = mission accomplished.

Anything else done to the app will be ui tweaks to make it look better... until they sunset Cash4Life...

At that point I will need to insert Millionaire 4 Life and remove Cash 4 Life, but here is the challenge... for that game, classifier sample data, following the formula, will require 870 draws (58 balls x the chance for each number to appear 15 times), so I am building logic that will keep the classifier button grayed out until the csv file has 870 draws in it (871, counting the header)

The Markov/Follower will run clean even with 0 draws, it just outputs nothing, but the classifier is not designed to run data starved.

After this, the work shifts back to the script lab for the major follower back test script that should provide some clues on how to best interpret the output. Also to determine if full history vs a sample yields better results... if the sample does a better job of holding onto the volatility, that can be changed in the app following the same formula... engineer on windows, assemble on Android.

Though this part is absolutely frustrating... 10 builds in and still the stale data problem... checking the data consuming funtions....