Nokia - Interrupted Trainings

Modified on Wed, 10 Apr at 10:05 AM

On some devices, you may need to edit some settings to avoid trainings getting interrupted. Se below for a guide on how to allow the app to keep running in the background during your whole training

Most Nokia phones (Power saver AKA com.evenwell.powersaving.g3)

To fix this issue, please do the following:

  • Go to Phone Settings> Apps > See all apps.
  • Tap on the right top corner menu > Show system.
  • Find the Power saver app in the list, select it, and Force close. It will remain stopped for a while but will restart itself eventually.

From now on, background apps should work normally and use the standard Android battery optimizations.

Still, 3rd party alarm clocks or any task scheduling of foreground tasks at a particular time won’t work. We do not have any solution for this at the moment UPDATE: in our preliminary tests, it seems that force stopping or uninstalling the Power saver app also fixes alarms and starting of foreground services, until the Power saver restarts.

Alternative solution for tech-savvy users:

Most Nokia models

The Evenwell Power saver *(com.evenwell.powersaving.g3)* has been disabled by HMD Global for devices running Pie or greater as of 8/2019.

Disable the com.evenwell.powersaving.g3 package via the following adb commands:

adb shell
pm disable-user com.evenwell.powersaving.g3

Nokia 1 (Android Go)

Disable the com.evenwell.emm package via the following adb commands:

adb shell
pm disable-user com.evenwell.emm

Nokia 3.1 and 5.1

Regrettably, HMD did not include any sort of Settings switch to control DuraSpeed’s operation. And since the task killer is a system service and not an app, it cannot simply be uninstalled. Fortunately, DuraSpeed does have a hidden kill switch: It watches the setting.duraspeed.enabled setting and will stop itself when the flag is set to any value that does not equal 1. Once DuraSpeed stops itself, the phone is cured and all background apps will function normally. However, this workaround does not stick across reboots, so the flag has to be cycled at every boot using an automation app like MacroDroid.

First, use adb to grant MacroDroid (or your choice of automation app) the ability to write to the global settings store:

adb shell pm grant com.arlosoft.macrodroid android.permission.WRITE_SECURE_SETTINGS

Then create a task, triggered at Device Boot, that performs the following:

  1. System Setting: type Global, name setting.duraspeed.enabled, value 2

  2. System Setting: type Global, name setting.duraspeed.enabled, value 0

MacroDroid example task

Tasker example task

Run this task and verify there are no errors. If all is well, then DuraSpeed will be immediately disabled, and it will also be disabled on reboot.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article