Is Model View Presenter and Dependency Injenction becoming a new Standard for Android Development?

In the last period i am having the chance to develop some apps for personal reason, and taking a look to what today the companies are organizing their work in the Android Ecosystem i encountered many and many times this kind of project configuration:

• MVP (Model-View-Presenter) as Design Pattern for app architecture;
• RxJava for Reactive programming event-based;
• Dagger2 for dependency injection;
• ButterKnife for fields binding with annotations, used in combo with Dagger2 in order to make your life simplier;
• Espresso and Mockito for testing (really nice to use in this kind of environment with this kind of settings)

So, is this becoming a new standard, in your opinion? If so, do you think that is a good idea apply this (relatively) new guidelines and you usually use this kind of project tools/pattern/libraries into your apps or you think there is something better? If you don't like, it, why? What do you think could be a better approach?

(Obviously each project is different, and for each project is always better engineerize the best solution/architecture possible for the kind of users/team/dev involved. I am trying to understand/discuss this kind of model that seems to become widely used in his concept in many, many companies)

Thank you for your time, i hope to create an interesting discussion on the argument in order to all improve our skillset/projects.

Enjoy your day!