1) Mintoris front end, being mostly white writing on a black background, is not suited to eInk. Some things like file names are completely invisible. Any way of changing the native color scheme?
2) Secondly, it would be nice to be able to make use of the four hardware buttons on the reader, being page forward and page back on left and right sides. Is there any possibility to re-map them or capture their state in any other way?
3) There is some underlying functionality on the reader which seems to suspend program execution when there is no user interaction. It only happens when the unit
This symptom is peculiar to the ereader. The same program on a normal cell phone works fine.
BASIC calls Androids API's, the manufacturer integrates Android to the hardware. This should make BASIC hardware independent, but that is not always the case, there are changes made to work around different devices.
Check the reference manual:
1) try the TextColor statement. There are different color statements for each screen modes, some will cross over to different screen modes.
Look up Event Triggers:
2) SetOnKeySub, this should work for hardware keys, this may work for you if the hardware buttons are mapped to keys. This does not work for me.
3) SetOnPauseSub and SetOnResumeSub this should indicate state of BASIC. Take a look at WakeLock, this should keep Android from putting BASIC to sleep.
For what its worth, the onXXX subroutines are callbacks, as with any callback, if you do anything to "block" callbacks Android will do strange and unexpected things. To "block" is to not returning in a timely manner, long loops, pauses, polling loops. With callbacks you are on Android's clock.