auto-capitalization
must be turned on in device settings for it to work!! don't ask why.
it is my understanding that device settings can only be managed by the user, so you'll have to do things the hard way and simply change the input to all caps after the fact. no biggie, and probably irrelevant to the user.
also found another curiosity: if you look at the tool tips for edittext, check the tip for "edittext.input =". it says that if you change the input type, the view becomes single line. apparently not true. when i changed the input type from text to allcaps (after having turned on autocaplitalization in device settings),
my input appeared in all caps,
and the view continued to be multi-line. not sure what the issue is there. (and, to be clear, all caps did not work using any of the methods suggested here
until i activated auto-capitalization in my device settings. i stumbled upon this gem hidden
here
* i shouldn't say you can't manage the device settings for the user; technically, at least in the case of all caps, you can modify the manifest, but i think you'd have a problem within the b4a framework as the manifest is generated automatically. i'm guessing you can alter it after the fact, but someone more familiar with the process will have to comment. if the b4a developer can't make the modification, then you will have to change the input manually from whatever it is to uppercase, which is trivial. (maybe a custom view set to all caps would work. i think you create your own manifest as part of that process.)