I've been using the 3.1 (US) for a couple of weeks and am having issues with the phone not triggering notifications from background apps. I first noticed this with Google Hangouts, where a new message would arrive in my browser but the notification on the phone would not fire. After opening Hangouts, the notification would be triggered.
This pattern extended to a 3rd party alarm clock that I use (Alarm Clock Xtreme), which when set displays Androids "alarm set" icon in the notification area. In this case, after some passage of time the icon will literally disappear. I missed one alarm like this before switching back to the native alarm clock (which seems to work just fine).
It seems as if something on this phone is stopping processes that normally run in the background. I've tried disabling battery optimization at both the per-app and OS level with no change. I've dug around the settings (to include, those under developer mode) and nothing else jumps out as being able to control these types of behavior.
Is anyone else having trouble like this? I really want to like this phone, but this is a bit of a show stopper for me.
I had this problem few years ago with another Android phone, and I had it yesterday also.
Unfortunately I just did it now and it seems that the problem cannot be reproduced.
Few years ago it was with the Timer, on a Nexus 4 phone. 5 Minutes timer. 7 Minutes later, I hear nothing, I go to the phone, I turn the screen on... It started ringing displaying "-2:17", "-2:18" and so on. I felt a little bit angry in front of this kind of things ! It was one of the numerous reasons why I went on Windows Phone from 2015 to 2018. But now it's Android for everybody (or iPhone !).
I have the same issue. Love the phone expect for this. It keeps booting background tasks.
The same here. For me, it´s noticeable when I´m in a Whatsapp conversation, the screen times out and the phone doesn´t ring for new messages. Opening whatsapp then reveals new messages.
Something that might is related: I´m using Twilight to dim my screen at evening. But it´s kind of unuseable, because when opening ram intensive apps like Firefox, Twilight gets force closed in the background, even when i´ve disabled battery optimization for that app. Maybe the same thing is happening to messengerapps...
There's some comfort knowing that I'm not the only one. I believe I speak for all of us that I hope Nokia issues a fix in a future release.
I received the following from Nokia support:
Also, you can may also try the following steps:
Menu >> settings >> Battery>> 3 dots on the right corner >> Battery optimization >> show All apps >> choose the Apps you want to run background (Alarm Clock Xtreme, Google Hangouts, and Twitter) >> Don't Optimise
( you can set only one by one of course)
We understand how frustrating this situation could be but please accept our sincerest apologies for this inconvenience and note that we appreciate your feedback and are building upon it to further constantly improve our services.
In the case you're describing, there is no fix we could apply from a distance also please note that there are some special procedures which need some time to be finished. That's why we would highly appreciate your patience
For the moment - indeed we would bring suggestions about the White List to the appropriate department - as it may take some modifications but perhaps we should indeed await the developers to work on that matter.
Once again - we really appreciate the feedback and the additional ideas that you had provided.
It is very helpful and we will keep your case in our database
The battery optimization suggestion did not fix the notifications for me. If it does not fix it for you either, please consider opening a support case so there are more documented incidents of this issue and hopefully a fix is released down the road:
I've tried all the different things from the internet, which certainly included the "Battery Optimization" change. Nothing has helped. We likely need Nokia to do something at this point.
Having this fixed, which may fix some other bugs people are talking about on this board, is critical. A phone that can only seems to have one user background task going, fails a critical use case.
I completely agree, and would encourage you and anyone else having this issue to contact support to have the case documented there as well:
I had all sorts of problems with background-ed apps being killed off no matter what the settings. In the end I just blew away _every_ built-in com.evenwell package (a lot of it looks very dodgy!) using adb and my phone is behaving so much better now! So far zero issues or missing features. Presumably they'll all be back again with the next update.
I have exactly the same problem, in addition to bluetooth not working properly. I've tried all the same things re. battery optimisation - nothing makes a difference.
I contacted Nokia today, and they are completely disinterested in even investigating this problem. Without any diagnostics whatsoever, they informed me that the problems of apps being killed are "probably" due to my choice of apps & their usage. Dropbox camera uploads fail because the app gets killed by Nokia's Android One OS. Nokia say "Dropbox's problem". I got no notifications from Words With Friends or Tweetcaster, because the apps are being killed. "Not our problem" say Nokia. They say my RAM usage is "probably" too high (without actually diagnosing anything). Even a tiny app like 'Twilight' that uses a tiny amount of RAM (to filter blue light for night reading), even this app gets inexplicably killed after just a few minutes. Apparently, ALL app developers are wrong, but Nokia are right.
I'd way their support is awful, but a company has to actually offer support in the first place to be rated this highly.
@Paul D - would you be willing to post a brief "how to" on how you made your phone better? What do these com.evenwell packages even do?
I'm going to try returning my phone to the shop to swap for something else, but if they also say "no, not our problem either" then I'd like to try your method to get this brick useful again.
Is it no wonder that Nokia used to be kings of the mobile phone world, and are now nothing but bit-part players.
I think it has something to do with Android One, not with Android 8, RAM or anything else. I had another Sony device with Android 8, and had no problems there. Also in the past older devices with just 2GB RAM had never this problem.
@Annoyed Customer, your problem is the same as mine - it was my night filter and various IM apps being killed every few minutes that p*ssed me off enough to investigate further. And yes, the phone is most certainly to blame.
There are plenty of guides on the 'net already on how to use adb to remove unwanted packages. In short I simply installed adb on my PC, enabled developer mode on the phone, enabled USB debugging on the phone, plugged in the USB, opened a shell using adb, 'pm list packages', grabbed the name of _every_ com.evenwell package, 'pm uninstall --user 0 packagename' for every one of them. So far I've encountered zero issues but all my "app randomly killed" issues have gone. Why HMD felt that Android (especially with doze) isn't capable enough to manage apps I have no idea.
@Jannis, no it's definitely the evenwell junk that HMD add on that's the cause - not Android One's patching and updates.
Now if only the Bluetooth audio didn't suck so hard when my smart watch is connected via BLE...
Thanks for that @Paul D. I'd heard of ADB before but never tried it (never had need to). Glad to see there are versions for Windows, Mac and Linux. I have both Win & Mac, and dabble with Linux sometimes too, so it is good to know I can play with this on any of my boxes.
Do I assume correctly that if (when) I do this, if anything goes pear-shaped then I can just factory reset back to normal? (Nokia's idea of 'normal', anyway...)