Fuck-Storage-Access-Framework VS leakcanary

Well, unfortunately you can't avoid learning what you must learn. SAF for file access is one of those things... unless you bring in a promising looking third-party library, and read the source code. I used EasyImage for example for camera access and it did work. I also used the file picker in https://github.com/K1rakishou/Fuck-Storage-Access-Framework .

FSAF to the rescue.

FUCK STORAGE ACCESS FRAMEWORK

There were multiple topics about it in the sub during last two weeks. You might find this SO q-a useful + maybe this library.

I've been looking for that during half a year. Apparently there is no such thing as a simple example for this part of Android "simple" development kit. So far Fuck Storage Access Framework library is the closest thing I've found (thanks to Zhuinden).

Fuck-Storage-Access-Framework/FileManager.kt at 842c5fb558fabbeee86629a06c71e09d2f373f2d · K1rakishou/Fuck-Storage-Access-Framework (github.com)

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/