I dabble a bit in B4A and have one production app, but spend most of my time in MS Visual Studio working on Desktop applications, web sites, and Windows Services.
With Erel's help I resolved the issue stated at the top of this thread. But along the way I was reminded of some helpful strategies.
The B4A translator provides a number of warning messages when compiling. Things like naming classes same as activities, and various other things. I have NOT been able to change my code to eliminate ALL warnings, but I find that striving to minimize the number of these is helpful.
The ACTIVITY PAUSE event is a bugger to debug, because of Android imposed limitations. Can not set a break point here, or linger. Also, I find crash info seen in the LOG is not always the core cause of a problem. In general I find putting up a temporary button that basically will execute the logic in ACTIVITY PAUSE and THEN either finish the activity, or else start another activity. Caution to avoid executing this twice. But through this technique I was able to trace through a number of problems I was having in the ACTIVITY PAUSE. This is probably like "well... yeah, duh!" for those who live in B4A, but for any relative beginner, such as I consider myself, this approach can save you many hours trying to hunt down an elusive problem.