Background Service Killed even when whitelisted
Hello, I got a problem on a background service of an app (Gravity Screen :
Background Service Killed even when whitelisted
Hello,
I got a problem on a background service of an app (Gravity Screen : https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree) that got killed after a while even when whitelisted !
The background service last about 10 min and then it'll be killed by PowerSavingAppG3 ! => https://img42.com/FoFWk+
As you can see on the screenshot, PowerSavingAppG3 is killing the service of Gravity Screen App for no reason.
I already disable the battery optimization for this app but nothing happend ...
Any help could be great ! Thank you.
6
Howdy, Stranger!
Categories
- 32.2K All Categories
- 27.2K Phones
- 36 Nokia G50
- 10 Nokia C30
- 54 Nokia XR20
- 4 Nokia C01 Plus
- 69 Nokia X20
- 13 Nokia X10
- 65 Nokia G20
- 15 Nokia G10
- 6 Nokia C20
- 6 Nokia C10
- 13 Nokia 1.4
- 4 Nokia C1 Plus
- 269 Nokia 5.4
- 111 Nokia 3.4
- 80 Nokia 2.4
- 2 Nokia C3
- 258 Nokia 8.3 5G
- 380 Nokia 5.3
- 17 Nokia 1.3
- 147 Nokia 2.3
- 1.3K Nokia 7.2
- 245 Nokia 6.2
- 443 Nokia 9 PureView
- 160 Nokia 2.2
- 1.6K Nokia 8.1
- 889 Nokia 7.1
- 4.6K Nokia 6.1 Plus
- 1.9K Nokia 5.1 Plus
- 2.2K Nokia 7 plus
- 344 Nokia 8 Sirocco
- 1.4K Nokia 8
- 2.1K Nokia 6.1
- 2K Nokia 6
- 228 Nokia 5.1
- 1.2K Nokia 5
- 214 Nokia 4.2
- 103 Nokia 3.2
- 777 Nokia 3.1 Plus
- 290 Nokia 3.1
- 964 Nokia 3
- 239 Nokia 2.1
- 527 Nokia 2
- 75 Nokia 1 Plus
- 283 Nokia 1
- 50 Nokia X7
- 536 Feature Phones
- 11 Nokia 5310
- 14 Nokia 800 tough
- 20 Nokia 2720 Flip
- 4 Nokia 110
- 1 Nokia 105
- 7 Nokia 220 4G
- 4 Nokia 210
- 78 Nokia 3310 3G
- 283 Nokia 8110 4G
- 402 All phones
- 19 Tablets
- 3.3K General
- 89 Home of Nokia Phones
- 52 Announcements
- 2 Tutorials
- 177 All about Community
- 7 Rules & Guidelines
- 462 Community Feedback
- 192 Contest & Activities
- 14 #Campfire
- 25 Global Contests
- 4 Q&A's
- 36 #ShotOnNokia Challenges
- 867 Ideas
- 612 Anything goes
- 3.3K Tech talk
- 118 Software and Specs
- 2.2K Beta labs
- 305 Beta labs
- 214 Android Developer Preview
- 230 India
Comments
I got a TA-1033
Hi,
i'm developing an app which is running in the background (but as a foreground service, so user has to start it and is notified that it's running) But on my Nokia 7 Plus the app is killed after ~30min of inactivity. I found out that PowerSavingAppG3 is killing my app / service even when my app is whitlisted.
Are there any news on this topic?
Thank you!
why not remove PowerSavingAppG3 apk ?
It seems a memory saver app. maybe be you can remove and try it again.
Yes this PowerSavingG3 is the Power Saving of Nokia (developped by evenwell). It kills "Inactive" background services in order ta save battery and memory, but too many background are killed for wrong reason.
So I found recently a workaround : I removed this Power Saver using adb :
I uninstall the two following packages :
Thank you for your responses and tips.
Unfortunately i can't tell all my users with a Nokia phone to remove Nokias Power Saver.
In another thread i read that someone had the same problem while listening to music with spotify and that the problem was fixed with an update by nokia. So i think they just exclude spotify from beeing killed in their power saver.
Is it possible to ask Nokia if they can whitelist my app on their power saving? but the question is, why are they ignoring the whitelist made by the user in the system?
Yeah I understand ...
But sadly, this power saver has to be fixed by Nokia dev team, because what I know, they just have fixed the music player issue but not the rest ...
And yes I already tried to whitelist some apps to be power optimized, but the power saver of Nokia doesn't care about this whitelist .... It kills app even if it is whitelist ... And I don't know why this Nokia power saver is ignoring the system whitelist ...
I think the best solution is not to tell Nokia to directly whitelist your app inside their app but to tell them to rework their power saver in order to to take care of the system whitelist and stop ignoring it.
Do you know what is the best way to tell them to rework their power saver?
Guess you can do it there => https://www.nokia.com/en_int/phones/support#contact-us
Could you tell me if you obtain any update from Nokia dev team ?
Yes, i will tell you if i get any news from Nokia.
Thank you for your help!
Well, the chat with nokia wasn't that helpful. "As the app that you are developing might be in conflict with the Android OS."
@user1515303135223 are you developing on Strava or are you using it? Please let me / us know if you get any updates.
Same problem here. The PowerSavingAppG3 keeps killing my service, although it runs as a foreground service.
As I said earlier, If you're not developping your own app, you can just remove this package using adb.
But If not, I don't have any solution for you right now ...
Uninstalling com.evenwell.powersaving.g3 using adb doesn't work, app can't even be deactivated.
Also com.evenwell.powersaving.g3.overlay.base.s600ww can't be uninstalled, but at least I was able to deactivate it, but it didn't help to prevent the app being killed.
Using a TA-1043 with Android 8.1.0 (May 2018).
@user1527014908181 are you a developer? The app i'm devoloping is holding a wakelock. I think thats the reason why my app is killed. When i remove the wakelock my app isn't killed by PowerSavingAppG3. But i need a wakelock to guarantee my app is working.
@user1525840365956 yes, I'm using a partial wake lock.
Hi there
I am having the same problem using TA-1033, Android 8.1.0, May Security Update. The system kills my app after about 30 minutes. I am currently developing this app. If this is a Nokia problem/bug, please Nokia debug. It is really annoying.
My app is acquiring in a foreground service a partial wake lock and shows a notification. The service would be started using startForegroundService and immediately calls startForeground. The foreground service is working correctly. Even if I close the application. But after about 30 minutes the system (the com.evenwell.powersaving.g3.overlay.base.s600ww) is killing the service.
My service is actually listening for location updates and as it is a sports tracking app, I need to be informed every 2-3 seconds. So there is no other solution as a long running foreground service, is there?
Would that forum even by read by Nokia responsible people? Are there any confirmations from Nokia that this may be a bug?
Best regards
Masterida
Hi there
June 2018 Security Update - problem still exists. Apps get killed after about 30 minutes by the system, even if there is a foreground service running with notification.
Detailinfos:
com.evenwell.powersaving.g3.overlay.base.s600ww is on version 8888.
com.evenwell.PowerMonitor.overlay.base.s600ww is on version 8888.
Same problem on my new Nokia 7+ with 8.1 and June security updates. Strava Support says that it is a Nokia problem.
Surprised that Nokia has let this problem go on for so long.
If its not fixed soon I won't have any option but to return the phone for a refund. Might buy a Motorola instead and see it its any better.
OB
Hi there
August 2018 Security Update - problem still
exists. Apps get killed after about 30 minutes by the system, even if
there is a foreground service running with notification.
Detailinfos:
com.evenwell.powersaving.g3.overlay.base.s600ww is on version 8888
Nokia 7 plus, Android 8.1.0, security update Aug . 2018:
I have now reverted to my Samsung 5s to run Runkeeper/Spotify for workouts, there are no way I can get the Nokia phone to let these processes stay up. And any feedback from the company is non-informative and nothing indicates that they even care about this as an issue. More pressing is it kills company VPN app as well.
As a software architect/developer for more than 30 years I find this quite annoying and arrogant. And as a current IS manager I now stop all purchases of Nokia phones without exceptions.
As an AndroidOne phone I saw Nokia as a really good business alternative to Samsung phones, as they tend to be stuffed with loads of crappy apps, but if Nokia is not interested in correcting bugs like these which kills off VPN software for business users I have no choice but to go elsewhere.
Regards
f