The forum was down or something yesterday and I couldn't post my findings (Navigating to pages loaded them about 1/3 of the way then hung...looked like it was having issues polling database)
I think I fixed it, but I'm not sure what the difference is. Templates and Interface type stuff in C++ based languages was never my strong point. I discovered the List was storing fine, but the part that was crashing was in my library when I passed an array of the List to the Alert Dialog to show. I was doing a .getObject().toArray() on the list and casting it to a String or CharSequence array. This worked fine for the B4A Array as String() parameters I was passing, but failed for the File.ReadList parameters. I got to reading the documentation for the other variation of toArray and tried getObject().toArray(new String[0]) on the List and passed it to the dialog. This now appears to be working, but to me seems like the same thing I was doing. The "new String[0]" stuff is new to me and the "0" I'm kinda curious about as to whether if other numbers are passed it would return from that part of the array on or something.
In the end it is working though and I have a nice Custom Combobox/Spinner. I'm a little disappointed at how Android handles SetSelection for the List of the dialog in Touch Mode though. I wanted to use the list without the Radio/Option Buttons, but SetSelection didn't appear to actually select a value or even scroll to it (I was fine without a highlight, but couldn't even get that). So, I switched to the Radio/Option button variety that does both, and much simpler by just passing the selection to the same method used to pass the list.