glide VS dont-kill-my-app

Do you mean what I use to show the images? I am using the Glide library, you can find more information here: https://github.com/bumptech/glide

as mentioned in the other post i don't have too much insight in the art loading because its using https://github.com/bumptech/glide for all image loading. Resolution is the only thing i know for sure can prevent an imagine from successfully loading, whether or not that resolution is fixed or if its dependent on the device I have not been able to determine

Ah, yes, downloading images as a files works completely differently from displaying images and it doesn't use any cache. Though in theory you could rewrite downloading logic to use the same mechanism as display (which is Glide)

Glide

You can also take a look at Coil, Picasso or Glide which usually have some kind of crossfade animation when the image loads.

GitHub: https://github.com/bumptech/glide

Image loading: Glide, Picasso, Coil, Fresco

Shortly said, they use React generally with fast-image and Glide for better loading of images Hermes JS Engine for app optimization. The app itself seems to generally use Kotlin and a few Java libraries and they also implemented Sqlite but I'm not sure about the use case for it probably they use it for progress though (The Developer/Marketer needs to confirm this), lastly they seem to use IntellJ Idea for programming and probably compiling

If you see a file like this: https://github.com/bumptech/glide/blob/master/library/src/main/java/com/bumptech/glide/RequestBuilder.java tell me that your eyes don't immediately go to the comments first instead of the code.

Where did you bring this up? It would be interesting to hear their response. If you hadn't, I imagine their Github repo would be the best place to bring it up https://github.com/urbandroid-team/dont-kill-my-app

If your phone has a MediaTek chip then the DooGee page will help here: https://github.com/urbandroid-team/dont-kill-my-app/pull/464.

So this lead me on a search on how to fix this. Thanks to u/That_Upstairs_9288 and this XDA post I have found the culprit:

Then you can write them about it (maybe here: https://github.com/urbandroid-team/dont-kill-my-app/issues/297 ) , and also mention it on the issue tracker:

The Urbandroid (Sleep As Android and other apps) team is investigating and evaluating on this subject, too: Samsung Android 11: ChimeraPolicyHandler killing foreground services and even Google's Issue Tracker: OEM battery optimization saga.