Move all Wait For's to Activity_Resume. This is just how resumable subs work with Android's app life cycle. Android calls Activity_Create and upon it finishing, Activity_Resume is called (in B4A's case). With the first Wait For in Activity_Create, you are pretty much exiting/finishing Activity_Create, upon which Activity_Resume is called. Once your first Wait For completes, Activity_Create is resumed at where it waited, but in Android's life cycle, Activity_Create has already finished.
You could also create a global flag that is set upon finishing the Wait For on Sub2. In Activity_Resume, you could check for that flag (right at the start) and if it is not set use a while loop and sleep to periodically check on the flag. I would only do this if the first two Wait Fors have to happen in the Activity_Create portion of the app. Otherwise, I would move them all to Activity_Resume and use a flag to see if I need to run the first two or if I can skip straight to the third Wait For.