Code Organization Patterns For Android Activities

In case of complex activities, UI related code for data loading and data binding / updating views can become rather lengthy.

What's even more frustrating you end up with lots of very closely coupled UI & Biz / Model layer type code that's not very reusable and hard to refactor.

Just read this post on MVP implementation in Android: http://ift.tt/1iTvxeo

To someone who is familiar with MVP implementations in other languages/platforms this seems to solve the problem, but before jumping to familiar territory I wanted to see what the community consensus is.

What pattern / approach do you use to organize your UI / Model related code?