leakcanary VS FGA

If your app exposes a LeakCanary Launcher activity, you will be able to quickly access it through the App Details bottom sheet.

Highly recommend you try out Leak Canary https://square.github.io/leakcanary/

First of all, grab the LeakCanary to check if you actually have a leak. Because just the memory increasing might be completely unrelated to your ViewPager.

It's strictly mContext otherwise it won't work as intended.

Knowing when root views are detached, e.g. to detect if they might be leaking (LeakCanary).

https://github.com/square/leakcanary + don't try to over optimise. In the end R8 / proguard / art runtime will do so many change between what you write and what actually is done that you may be loosing time doing something that the tools does for you.

LeakCanary

LeakCanary will help you find memory leaks in your code: https://square.github.io/leakcanary/

I JUST USE AUTOMATA.

On Running FGA with Emulators

https://github.com/Fate-Grand-Automata/FGA They also have a video if you are interested.

Here an Example of an App which automates the game "Fate/Grand Order" the way I described above.

You can check it out here.

Everyone uses Fate/Grand Automata for the boring grinds. There's a big lottery event on right now where the more runs you do the better, and my phone has been grinding on autopilot in the corner while I've been working all day.