Anyone else experiencing this?

Nope been using it for a while and never received this warning

Saaame

Only oneplus users I think

This only happens on the Oneplus from my understanding, and everyone who has looked into it more deeply says it's incorrect and others have gotten it for a number of other apps too.

@Farazz Ah, yup! One Plus user here.

Once or twice since i upgraded to Android Oreo

I'm on OP3T and never seen it. However I am running LaOS and ForceDoze.

@dfox Until the most recent update, I had an issue with devRant where leaving it open on my Xperia Z5C would eventually slow it to a crawl (12s to get to the launcher when closing any app). Seems fixed now, but maybe you have some memory leaks?

OnePlus 3T here, been seeing this more and more before the last play store update. Not only devRant, I got it for Play Store too when it was updating apps. That's when I knew it was a bug.

@globalvariable

Stock rom, rooted, nouget. Few apps are not responding quite often. Did you notice any similar behaviour?

Which rom do you suggest?

One plus 3 t can confirm doesn't drain. Is it just me or devs have a lot of one plus phones.

One my oneplus 3t it happens sometimes, but other apps have this more frequent

OnePlus 3T user here. I can confirm this hairnet if you leave the so open in the background. If you look at the per usage it really isn't that bad as described. Also the same happens with other apps like 9gag or solid explorer. I think it's just the system that is like Gollum with the battery, even when not needed

I don't know what happened to the autocorrector, what I mean is: you leave the app open, if it does some work in the background, like precaching or something, the system shows that notification.

@julianmd that's pretty funny, that it happens for the Play Store too :) They really need to fix this. We get a lot of people who don't use a lot of apps and then think it's something we're doing, understandably, when they see the alert come up.

@pily thanks for the information.

@CptFox it's possible something was fixed in the latest version as we updated a number of frameworks. We had some issues with the app freezing on occasion, but not sure if that was related to memory.