Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

351F-B04 update for Nokia SDM63x/660 devices seems disabled Power Saver G3 by default #55

Closed
HikariCalyx opened this issue Apr 3, 2019 · 19 comments

Comments

Projects
None yet
5 participants
@HikariCalyx
Copy link

commented Apr 3, 2019

Recently HMD pushed 351F update (March 2019) for Nokia 6.1/6.1Plus/7.1/7Plus and disabled Power Saver G3 from system, although they didn't remove it.

Power Saver G3 was originally designed for handling Chinese bloatwares, such as WeChat, Alipay, Taobao, TikTok, Kuaishou, etc. China variant uses "Whitelist" policy instead of "Blacklist". For some reason, looks like they didn't realize Power Saver G3 is unnecessary for Global release until now. Power Saver G3 will always exist in China Variant Nokia Phones.

Following URLs are Full OTA for both Nokia 6.1 and Nokia 7 Plus Global, if you want to analyze:

https://android.googleapis.com/packages/ota-api/nokia_pl2sprout_plate200ww/3601a351ff7577ed5a013d6f4fe5fdd64d32355c.zip

https://android.googleapis.com/packages/ota-api/nokia_b2nsprout_onyx00ww/5255f45225061bdc1c3525a32cf7361480e45ea3.zip

If you want to know your current Firmware Build, you can either dial * # * #227 # * # * to check "Version" in BBox app, or use command "fastboot oem getversions" under Fastboot/Download mode if BBox app displays nothing.
Expected build version looks like this: B2N-351F-0-00WW-B04, which is stored at systeminfo partition or /proc/fver .

@petrnalevka

This comment has been minimized.

Copy link
Collaborator

commented Apr 4, 2019

Incredible, big thanks for sharing this! We will check the resources and hopefully test the update soon on the Nokia 6.1 we have around @Artaud

@IvanFrederiks

This comment has been minimized.

Copy link

commented Apr 10, 2019

I installed the update, but known power saver apps are not disabled. Maybe their behavior was changed? @petrnalevka, is there any way to test it?

@petrnalevka

This comment has been minimized.

Copy link
Collaborator

commented Apr 12, 2019

@IvanFrederiks good question. In Sleep as Andoid we already have a screen always on hack for Nokia.. so it is not that easy, maybe we could prepare a test case APK but I do not have the time now..

It could be tested with one of the older APKs of Sleep as Android from here - e.g. version 20181212 did not do the hack:
https://sleep.urbandroid.org/wp-content/uploads/release/sleep-20181212-prod-release.apk

@Artaud did you get an update on your Nokia 6.1?

@Artaud

This comment has been minimized.

Copy link
Collaborator

commented Apr 16, 2019

I did get the March update but it did not disable the Power Saver for me on my Nokia 6.1.
My build version is PL2-351F-0-00WW-B04

@IvanFrederiks

This comment has been minimized.

Copy link

commented Apr 19, 2019

@petrnalevka, I installed the old build, hope I will test it this weekend on updated Nokia 6.1. Any suggestions on test conditions?

@petrnalevka

This comment has been minimized.

Copy link
Collaborator

commented Apr 19, 2019

@IvanFrederiks I guess you can simply start sleep tracking and leave it for few hours.. if you get a complete data from the sensor all is fine, i fyou see any red areas in the result - this means the service was killed..

@Artaud

This comment has been minimized.

Copy link
Collaborator

commented Apr 20, 2019

We had the sleep tracking service stopped after about 20 minutes. Also if you set up an alarm for the morning, it only rang very rarely.

@IvanFrederiks

This comment has been minimized.

Copy link

commented Apr 20, 2019

@petrnalevka @Artaud
This night everything worked well: tracking completed successfully, Amazfit data was collected. The only thing I tweaked before tracking was to disable battery optimization in app settings.

@IvanFrederiks

This comment has been minimized.

Copy link

commented Apr 22, 2019

@petrnalevka @Artaud
3 nights in a row, everything works fine! Even smart alarm.

@petrnalevka

This comment has been minimized.

Copy link
Collaborator

commented Apr 23, 2019

@IvanFrederiks very interesting, maybe @Artaud can confirm it om his Nokia 6.1?

@HikariCalyx

This comment has been minimized.

Copy link
Author

commented Apr 23, 2019

Thanks you for replying.

A friend of mine @luzhnan , who is using a Nokia 7 Plus with B2N-351F-0-00WW-B04 build installed found a secret about Power Saver G3.
The interface of Power Saver G3 is actually controlled by the overlay placed at "/system/product/overlay/com.evenwell.powersaving.g3.overlay.base.[SKUID].apk".

Where [SKUID] need to be replaced to your actual SKUID, like 600WW.

If you attempt to disable the overlay package, the Power Saver G3 will become into the "Whitelist" Policy like CN releases.

Also, the overlay for SKUID=600CN is attached here.
com.evenwell.powersaving.g3.overlay.base.600CN.apk.zip

@IvanFrederiks

This comment has been minimized.

Copy link

commented Apr 23, 2019

@HikariCalyx do you mean that after 351F update Power Saver G3 uses "Blacklist" policy (which is correct for most cases) and disabling overlay package would be harmful (because "Whitelist" policy does not honor most of apps)?

@HikariCalyx

This comment has been minimized.

Copy link
Author

commented Apr 24, 2019

@HikariCalyx do you mean that after 351F update Power Saver G3 uses "Blacklist" policy (which is correct for most cases) and disabling overlay package would be harmful (because "Whitelist" policy does not honor most of apps)?

If you disable the overlay instead of the power saver, you'll get Whitelist Policy.

@IvanFrederiks

This comment has been minimized.

Copy link

commented Apr 30, 2019

@petrnalevka, I would like to switch back to most recent version of the app without increasing battery consumption. Is it possible to disable the screen always on hack?

BTW, old version worked well all nights since 351F update.

@petrnalevka

This comment has been minimized.

Copy link
Collaborator

commented Apr 30, 2019

@IvanFrederiks many thanks. I did check now and in fact you can do it in settings - misc - disable experimental features.. a side effect it it will also disable some of the latest features of the app.. but hopefully this will help and we will hind something better for the later releases..

@petrnalevka

This comment has been minimized.

Copy link
Collaborator

commented Apr 30, 2019

@HikariCalyx many thanks for the further details we try now to verify it on our Nokia 6.1.. it seems promising, this would be a great news really...

I'm wondering what is the penetration of this update if dev could already rely on it and revert any workarounds they did..

@Artaud

This comment has been minimized.

Copy link
Collaborator

commented May 6, 2019

I can confirm that it worked for me on Nokia 6.1 March update, after I again enabled the powersaving.g3.overlay.

@hb0

This comment has been minimized.

Copy link

commented Jun 3, 2019

We have a sensor and location capturing SDK (background process/ForegroundService) and I checked all reviews since May 2019:

I haven't seen any Nokia Users reporting background tracking problems.

Last year there were quite a few Nokia user, too. Since May 2019 I only saw Huawai, Xiaomi and some Samsung and OnePlus users report tracking problems, so it seems like Nokia really did something here in Europe.

Fingers crossed, that other vendors might follow.

@petrnalevka

This comment has been minimized.

Copy link
Collaborator

commented Jun 11, 2019

Hello, we are also seeing a lot less Nokia issues reported so I'm confirming this on our end. In our apps we have started disabling the hacks we did on Nokia devices.

I did removed one crap of the Nokia crap score for now and we can improve this further as we see the issue got fully resolved.

So far I did add a caution text which is explaining this briefly and links to this thread for details.

Big thanks to everyone and especially to @HikariCalyx for the details on this..

See https://dontkillmyapp.com/nokia

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.