You are correct in that AspectJ, for some pointcuts, has to do a deeper analysis of type information including digging out the super types etc, more so than is required for straightforward compilation. However, your pointcuts don't immediately suggest a huge amount of digging is required - for example you have no declaring type specified in your 'onCreate' reference so that can simply be matched by name.
If you don't supply the android.jar which types does it complain that it cannot find? Or does it not complain and just fails to weave? (the latter would be strange) Does it complain about Activity? Given that you didn't say execution(* Activity.onCreate(Bundle)) I don't immediately see why it needs more than just the method name, especially as you are not binding any context. Does Bundle come from the same android jar? You could (as a quick experiment) change it to Bun* instead of Bundle (partial type names with wildcards are treated in a slightly more relaxed way than fully specified types).
I did do some work a while ago to do less type chasing but it is certainly possible this could be taken further.
cheers,
Andy