Database Info

Facebook App Notifications

Am I the only one who doesn't get FB notifications?
The only way I know of anything is by email.
I have the notifications turned on in the app, and my wife's Hero gets hers all the time....
EDIT:
It seems this is an issue for some people across all the Android phones. Sure wish they would fix it. Wonder why my wifes works so well....

I become prone to flashing different Rom's alot lately. One thing I've noticed, is that, I NEVER got FB notifications on the stock Rom. Hell, I didn't even know it was possible. Only thing I got was the updates on the updates tab in contacts/sync. Once I started flashing Rom's, it's been hit or miss, depending on the Rom in question. And i have noticed, a few Rom's come with the notification disabled, by default. Meaning, all you have to do, is find the options page where it is located, and enable it. Hell, that might have been the case for the stock Rom.

HarveyStyles said:
I become prone to flashing different Rom's alot lately. One thing I've noticed, is that, I NEVER got FB notifications on the stock Rom. Hell, I didn't even know it was possible. Only thing I got was the updates on the updates tab in contacts/sync. Once I started flashing Rom's, it's been hit or miss, depending on the Rom in question. And i have noticed, a few Rom's come with the notification disabled, by default. Meaning, all you have to do, is find the options page where it is located, and enable it. Hell, that might have been the case for the stock Rom.
Click to expand...
Click to collapse
Ditto on hit or miss. Can't remember on stock, but right now I don't get them, I have gotten them. It beats me. Facebook sync is a little iffy but usually I get that one, and I have that synced now. I would rather get FB notifications than an email, but I guess I would be whining too much.

bump
Anyone have any more insight on this yet? I wasn't getting them, then removed all accounts, and the apps from the authorized section on my facebook account settings. Then readded the account on my phone. I got them for about a week, and they've stopped again. I'm running rooted stock 2.1.

Try opening the Facebook app, then exit it by hitting the Home button on the phone (not the back button). Seems like as long as the app is running in the background, you'll get the notifications, but if you've got a task killer or something and you kill the app, you're not gonna get them. That's what has worked for me, but your mileage may vary.

Rooting Cause More Processes to Run?

After rooting my phone and removing the ATT bloatware, I noticed that my Advanced Task Killer (Free) program lists more programs running in the background than before? Lots of programs that never popped up when the phone was stock now are showing up in the Task Killer program as running? Is this right? Did something screw up? If I kill all those processes the only ones that consistently comes back are HandCent SMS and Clock.

I've been noticing the default messaging app and clock open up a lot, and sometimes other apps too, like ESPN ScoreCenter, Facebook, etc. are opening up by themselves. Does anyone have any idea why this is happening?

I've noticed that my GPS kicks on every once in awhile too randomly. Usually when I can tell something's running in the background.
If you turn off Background Data in Settings>Accounts and Sync, it stops it almost in its entirety, but you have to turn it on to access the Market. My guess is it's just the programs collecting or sending data regarding use of the program, or with the clock (and possibly other programs) updating itself.

I can see the logic in that some apps need to update, but I never saw these same apps exhibit this behavior before I rooted. ie) Apps running themselves and showing up in my Advanced Task Killer program and now I have to kill them where before I never knew they were there in the first place. No changes to my phone except root. Are these based on the General Sync Settings options like Background Data or AutoSync? I just don't like the idea of all these apps running when I never started them in the first place.

I think you just didn't see them before... rooting isnt going to make apps randomly start doing things they didnt do before.
This needs to be in the gerenral section as well.

it shouldnt cause more to run :/

Sorry if this post is in the wrong section. But yeah, I know those apps that are popping up now weren't there before. I'm sure I didn't miss seeing them as I have all the settings for Advanced Task Killer program set the same in terms of security levels.
Are you saying that rooting my phone made the apps show up now (as in they were just hidden to the OS/program prior to rooting)?

eh
Well The same thing used to happen to me on my HTC desire so it must just be Android (maybe has to do with the build) or just Android in general. I would get stuff like settings and such in the task managers as well etc, exactly to what you guys are describing. They were not really used or needed programs so ending the tasks was no problem. No clue, but this is not only on this device
And yes my HTC DESIRE was rooted as well

Moved to General.

How to keep Apps running in the Background?

Hi everyone, ever since the update, my apps stop running in the background when I close the app. Example: I don't get Whatsapp notifications anymore unless I open the app and keep it open. If I close all open apps, I will no longer receive any of the notifications for any of them.
I went into the battery settings disabled battery saver mode but that didn't do anything.
I would appreciate any help you could provide.

DominionChamber said:
Hi everyone, ever since the update, my apps stop running in the background when I close the app. Example: I don't get Whatsapp notifications anymore unless I open the app and keep it open. If I close all open apps, I will no longer receive any of the notifications for any of them.
I went into the battery settings disabled battery saver mode but that didn't do anything.
I would appreciate any help you could provide.
Click to expand...
Click to collapse
It's apparently one of the issues with the latest OTA update, where closing all running apps will terminate the background processes associated with the apps closed. Prior to the update and the Close All button being added to the recent apps list, I don't think it had this problem (I don't use Whatsapp, but my Skype and Discord notifications still come through even if I don't have them on my recent apps list).

This is a little frustrating. Noticed that I wasn't getting any notifications from tasker, pushover, textra, hangouts, inbox and etc.
Also noticed that pushover will not update unless it is off of wifi. All my other devices receive notifications on this wifi. IE nothing blocked.
I have had to open all the programs that I want to receive notifications from, open. Not the best work around.
J

I noticed that on occasion there will be small text under the new button that says "long press to set up apps that could run in the background" I do it but it doesn't seem to do anything, maybe free up some of the RAM but that's about it. I'm wondering if there is a bug and if it's supposed to show something.
Has anyone else tried the long press?
As of now all I do is keep a folder on the desktop labeled background apps. It helps big time when I accidentally tap the close all button. But my solution as of now is to keep things open that don't seem to work in the background. I've been experimenting with what works and it seems like in some recent app updates they begin to work without being open. I know for sure that facebook and now facebook messenger work without being open, as well as some google services. I have a memory clearer app that I use when I'm not using my phone so it clears whatever it can without killing the apps. But that's what I have as of now, trial and error to figure out what I need to leave open and what I can close. And I strongly recommend the folder, I have had many times where I accidentally close everything and forget what I had to leave open.
It's a bummer though, I just bought the phone and then this update came out. Kinda kills the excitement of getting a new awesome phone if I have to deal with this frustration :/ Other than that, it's definately a nice step up from a Samsung S4.

Jmoore4 said:
I noticed that on occasion there will be small text under the new button that says "long press to set up apps that could run in the background" I do it but it doesn't seem to do anything, maybe free up some of the RAM but that's about it. I'm wondering if there is a bug and if it's supposed to show something.
Has anyone else tried the long press?
As of now all I do is keep a folder on the desktop labeled background apps. It helps big time when I accidentally tap the close all button. But my solution as of now is to keep things open that don't seem to work in the background. I've been experimenting with what works and it seems like in some recent app updates they begin to work without being open. I know for sure that facebook and now facebook messenger work without being open, as well as some google services. I have a memory clearer app that I use when I'm not using my phone so it clears whatever it can without killing the apps. But that's what I have as of now, trial and error to figure out what I need to leave open and what I can close. And I strongly recommend the folder, I have had many times where I accidentally close everything and forget what I had to leave open.
It's a bummer though, I just bought the phone and then this update came out. Kinda kills the excitement of getting a new awesome phone if I have to deal with this frustration :/ Other than that, it's definately a nice step up from a Samsung S4.
Click to expand...
Click to collapse
does it misbehave after rebooting? or all the time?

sensorsweep said:
does it misbehave after rebooting? or all the time?
Click to expand...
Click to collapse
Misbehave as in not show anything after a long press?
Yes, nothing happens anytime I try it. After reboot, the first time I pull up the running apps is when I get the prompt. After the first long press after a reboot, the prompt is gone. If I have an app open and then I do the long press, I am taken back to the desktop, but no matter what I try, nothing seems to happen after the long press other than being taken back to the desktop if I had an app open.

I have the same issue, I thought it was a Internet connection issue (see my thread) but after digging deeper realised my background apps werent running after closing them and the long press option does nothing.

I have the same problem. Any solution?

MatisasB said:
I have the same problem. Any solution?
Click to expand...
Click to collapse
I've just installed the new update and it looks like the issues I had with background apps closing when clearing all apps has been fixed. I've got no apps running in the foreground yet can see Whatsapp, Fitbit, etc still running and I'm receiving notifications for them.

How to prevent from stopping background processes

Hello, (sorry for my english ) I have a Samsung Galaxy S8 plus SM-G9550 and I would like to know how I can prevent the system from stopping important processes running in the background, since the widgets can not be used without manually activating the app to which the widget belongs. Don´t Synchronize the weather widgets for example, also applications widgets to record or play audio, only work a few minutes after application was manually opened and then stop working, also close streaming applications running in the background as "radiocut" . I already tried everything, even removing the apps from the energy saving settings, I put those applications in the list of apps without supervision of the power monitor and still do not work, only work for a few minutes and then the system stops the process, Could you help me solve this problem?
Thank you very much

You can't really stop the S8 from killing processes. It has very bad memory management and constantly kills processes and running apps. It's very annoying.

jorgemackay said:
Hello, (sorry for my english ) I have a Samsung Galaxy S8 plus SM-G9550 and I would like to know how I can prevent the system from stopping important processes running in the background, since the widgets can not be used without manually activating the app to which the widget belongs. Don´t Synchronize the weather widgets for example, also applications widgets to record or play audio, only work a few minutes after application was manually opened and then stop working, also close streaming applications running in the background as "radiocut" . I already tried everything, even removing the apps from the energy saving settings, I put those applications in the list of apps without supervision of the power monitor and still do not work, only work for a few minutes and then the system stops the process, Could you help me solve this problem?
Thank you very much
Click to expand...
Click to collapse
I think you have to turn off the app from Battery Optimization. Try Settings; Apps; touch the three DOT menu on the right corner, select Special access; Optimize battery usage; on the top left select "All apps" by default it shows "Apps not optimized" and Turn off Battery Optimization from the app you want to keep running... Let see if it works...

dhorgas said:
You can't really stop the S8 from killing processes. It has very bad memory management and constantly kills processes and running apps. It's very annoying.
Click to expand...
Click to collapse
Like Emby, when you're in the middle of casting

disturbd1 said:
Like Emby, when you're in the middle of casting
Click to expand...
Click to collapse
I don't know is what that means.

In device manager under battery there is the ability to add apps to the whitelist so the device manager won't stop them.

ShrekOpher said:
In device manager under battery there is the ability to add apps to the whitelist so the device manager won't stop them.
Click to expand...
Click to collapse
This doesn't work. The issue is with memory management on the device. It's pretty well documented in a few places on XDA already and is by no means a new problem for Samsung. It has gotten a lot worse since Samsung started moving to Nougat though.

Can you give a reproducible scenario?

The original post already mentioned that he already removed the apps at battery optimization.
Sent from my SM-G955F using Tapatalk

lopri said:
Can you give a reproducible scenario?
Click to expand...
Click to collapse
Open 6-8 apps, in my case phone, messages, email, browser with 10 tabs, BBM, calendar, Nine Email, and Slack and watch the phone shut down apps on its own even if they are removed from all optimization features. It sometimes takes a few hours, other times it's quicker, but sooner or later the phone just shuts down apps on its own. Most of the time it kills the phone app and messages first. Then all the browser tabs go into refresh mode.

dolbylogic said:
I think you have to turn off the app from Battery Optimization. Try Settings; Apps; touch the three DOT menu on the right corner, select Special access; Optimize battery usage; on the top left select "All apps" by default it shows "Apps not optimized" and Turn off Battery Optimization from the app you want to keep running... Let see if it works...
Click to expand...
Click to collapse
Nobody else responded to this, but it seems to work for me.

I am a j7 pro user, android 7. I have tried all the oprions mentioned here but those are of no use. problem is getting worse day by day. desperately need a solution.

adattabd said:
I am a j7 pro user, android 7. I have tried all the oprions mentioned here but those are of no use. problem is getting worse day by day. desperately need a solution.
Click to expand...
Click to collapse
I suggest the J7 forum section then, this post hadn't been touched for a year.

iworkout said:
Nobody else responded to this, but it seems to work for me.
Click to expand...
Click to collapse
It worked for me too.
I had an Galaxy S6 and used to sync FolderSync with an FTP account.
After migrating to Galaxy S8+ FolderSync doesn't work anymore.
It does sync once while the app is opened and after that it stops syncing, no matter if it is closed not.
Removing Battery management for FolderSync app makes syncing to stay running in background even with all apps closed.
Thanks!

Keep apps running in background?

I am still having trouble running apps in the background. Specially WhatsApp. I've disabled many evenwell apps and duraspeed using adb commands but not working. I am on the latest release of PIE. Is there a definitive guide to make this phone multitask?

Did you already try the instructions at dontkillmyapp.com?
I tried everything, and I haven't still got the Screentime app to work. Something keeps closing it when the phone is on battery and screen off. If the phone is charging over the night, the app stays in the background as it should. Also if the screen is on, there is no problems. An app like Screentime is quite useless if something keeps killing it all the time.
Quite annoying, as I selected Nokia because of Nokia having close to stock Android.

k701 said:
Did you already try the instructions at dontkillmyapp.com?
I tried everything, and I haven't still got the Screentime app to work. Something keeps closing it when the phone is on battery and screen off. If the phone is charging over the night, the app stays in the background as it should. Also if the screen is on, there is no problems. An app like Screentime is quite useless if something keeps killing it all the time.
Quite annoying, as I selected Nokia because of Nokia having close to stock Android.
Click to expand...
Click to collapse
Well... I have managed to (somewhat) solve the issue with keeping the apps running on the background, so I'll share which my experience was, so you can check through it and see if it fits your needs and/or it helps you.
IT MUST BE NOTICED that some of the described stuff is because my personal needs, but nonetheless it can bring some ideas about what could work for you (or anyone else).
First of all, according to a discussion here on XDA there are a couple of evenwell apps that can be disabled and/or deleted from the device. I found that thread a little too late after I've done some of the following steps, but I wanted to point it out just in case you can find something useful.
So, as we have learn on https://dontkillmyapp.com/nokia (DKMA) there are two probable culprits regarding the killing of the apps:
The Powersave App
The Duraspeed process/daemon
Powersave/Evenwell Apps
For this ones I followed the given instructions on the DKMA page to no avail, as they worked only for a certain time and then the background processes started to get killed after a while.
So, after digging on the Nokia Forums I found this discussion and specifically this comment where an user when full ballistic and created a one-line script to delete/uninstall all evenwell applications (this needs to be run on the ADB shell). I must add that after some "trial-error" loops I noticed that sometimes there were some background processes running, so I done the following:
This is for doing a Force Stop to every Evenwell process. I would suggest to running it a couple of times, just in case there are some processes that refuse to be stopped:
for crap in $(pm list packages | grep even | cut -d ":" -f2) ; do am force-stop $crap; done
This is for Disabling every Evenwell process for the current user. Same additional suggestion as above:
for crap in $(pm list packages | grep even | cut -d ":" -f2) ; do pm disable-user $crap; done
This is for Uninstalling every Evenwell process. Same suggestion as above. Please note that this uninstalls the apps ONLY for the current user, that means, only for you (hence the [--user 0] parameter). As rooting is not possible yet, is not possible to get rid of these apps at system level:
for crap in $(pm list packages | grep even | cut -d ":" -f2) ; do pm uninstall --user 0 $crap; done
What those commands do is, first get all the packages that have "even" on their name (you can go and use the full name "evenwell", I left it as it is because I performed this steps after a factory reset), and for each one of them it performs the indicated operation (disabling, force stopping, uninstalling).
After that, I read somewhere else (can't recall exactly were) that it could be useful to clear the cache of Google Services and Google Play Store, and reboot the device afterwards.
Those steps solved most of the issues, as now the applications weren't killed after the screen goes black, or the device is idle. But, after a couple of hours (~3 hours) I still had some issues as the processes were still being killed, so that's when I went to the next item.
Duraspeed
As we know, this is a major annoyance as this thing (service/daemon) is impossible to uninstall, and it's very annoying to disable. What was most annoying is that my device (TA-1074) it wasn't listed on DKMA as a device having that thing, but it seemed that I had it.
So, this is where the fun starts, because although the instructions posted on DKMA works, it seems (basically) that it only works on the current session of the device, meaning that if the device was rebooted the operation was needed to be performed again. There's a discussion on Github where this is explained more lengthy and in more detail.
To add more fun to the mix, it seems that even if the setting was disabled, the Duraspeed service ignores the current value of that setting while booting the system, only taking notice of it when the value changed, meaning that we need to change the value to something else, and then setting it again to 0 (zero) in order to make a successful disabling of Duraspeed. There's no need to say that doing that on every reboot is a PIA.
Any way, on the thread some users suggested using some automation applications (like Tasker or Macrodroid), but not before granting some permissions to the automation apps, similar to what the guys of Syncthing-Android (fork) suggested (just changing the package name, of course).
But, for me here's the catch: none of the automation apps worked for me. It could be for several reasons, because I needed to setup some other things that I need to run at startup, but, well, YMMV.
Anyway, it seems that the developer of Syncthing-Android has added a routine to its application that makes the change of the setting and therefore disabling the Duraspeed service and that such change is live on production, and I can say that it works as intended.
---
After doing all of that, I was able keep the background apps alive doesn't matter if I rebooted my phone or not.
I hope that this could be of any help.
Kind regards.

Quick question
Thank you for the awesome write-up.
So, just to make sure: is the Syncthing-Fork the solution? I tried the DuraSpeed/MacroDroid/Evenwell route, but Whatsapp and IFTTT still refuse to cooperate.
Please advise.

Hi!
Well... To be honest, as far as I've seen, the thing that is causing most (if not all) of the issue is the DuraSpeed daemon/service, and in my particular use case, the only thing that worked is how Syncthing handles the "workaround". Let me explain...
It seems that DuraSpeed is controlled by a global setting named setting.duraspeed.enabled, and as weirdly as it sounds, it seems is that the value of that setting its taken into account when its changed and not during system boot. On other words, if we configure the value of the setting to 0 (zero), and we reboot the phone, although the value is persistent (I mean, it is not changed during the reboot/shutdown), DuraSpeed tend to ignore during the startup and will work as "designed" (that is, going in a killing spree from time to time) and giving us all the issues that we are aware of. As DuraSpeed will take into account the value of the setting only when it's changed, what is needed to do is to change the 0 to another value (let's say 1), and then changed again to 0 in order to be disabled.
Also, there's a funny thing about DuraSpeed: it seems that DuraSpeed start killing processes almost since the startup process, and not only after all the OS/UI has been loaded/is ready... What is frustrating enough, as it kills some processes just before we can use them.
So, according to what I've seen on some captured catlogs, is that Syncthing makes that change during startup, and not after the OS/UI has been loaded. I don't know how they do that (I have not taken a look into the codebase), but according to what I have read on the logs, the change is made on the early steps of the startup, just before any damage could be done.
So, my guessing is that, perhaps the Automation applications (Tasker, Macrodroid) are being killed before they can make any change into the setting, and DuraSpeed do all its nasty things.
By the way... Did you grant to the app that you're using, the ability to write to the settings store (using ADB)? The procedure that I am referring to is the one that is described on this response on Urbandroid's GitHub thread. I ask because I forgot to do that after the factory reset and was having the "DuraSpeed issues".
If you haven't, it could be that it's the only missing thing on your setup, and that probably it will solve the issue for you. If you already have done that, I'm guessing that you're on the same boat as I, and those applications are not able to perform the workaround.
Other thing (that I can think of) to check is the "Battery Optimization" setting. This is located on "Settings -> Apps & Notifications -> Advanced -> Special App Access -> Battery optimization". There you can configure if an application will be optimized or not, by clicking/pressing on an application and selecting "Don't optimize"/"Optimize" (according to your needs). It will probably be less severe as DuraSpeed, but I've configured some apps there too, just in case.
I hope this is useful for you.
Kind regards.

Thank you for the very detailed response - greatly appreciated.
I have done all of the above, I even reached out to the maker of Syncthing-Fork who took the time to write back almost immediately with additional help.
So far - WhatsApp is still dead. Unless the phone is being charged or the screen is on, messages and voice calls do not work (the other thing that wakes it is an incoming cell phone call or a cell text message). Similarly - IFTTT: I have yet to get it to trigger anything when the screen is off.
I use MacroDroid to perform the DuraSpeed value change at boot time and I had granted it the required permissions - exactly as described on the forums that you reference. Not sure what else to try.
I now see why some comments on DKMA call Nokia phones "dumbphones" - the phone and texts are the only things that work consistently.
Anyway, thank you again for taking the time to reply.

Hi there!
Well, I can't deny that it's a downer that your device is refusing to cooperate and just work as you, the owner/user, are expecting it and not how the developers/makers thought it should work...
The only last thing that I can think of is a little bit of an overkill, and it is making a factory reset, and perform any/all of the suggested steps (by DKMA, catfriend1, myself, etc) before installing anything else (besides, perhaps, the automation app)... Just in case that something else is interfering with the workarounds, and to have a "blank state" to start to work... As I stated before, I think that it's an overkill, specially because all that implies doing that (backups, mainly), but well... I can't think about anything else.
I now see why some comments on DKMA call Nokia phones "dumbphones" - the phone and texts are the only things that work consistently.
Click to expand...
Click to collapse
Yeah, I fully agree with you, although the specs (for a budget phone in my case) aren't so bad, all the battery customization (and bloatware) just sucks... To say the least.
I hope that you can find a solution for your issues, or at least a device that doesn't let you down as Nokia does...
Kind regards!

Still no luck
Did the factory reset, installed Macrodroid, gave it the required permissions. Disabled the evenwell packages that have also been identified as culprits. Checked duraspeed status via adb - it is disabled.
No luck. Dumbphone it is.
The annoying part? I have a nexus 4 and a nexus 5 with just as little ram and likely an inferior processor. Both phones work great (albeit really slow, not to mention the battery life). I feel the principle "don't fix it unless it is broken" applies here...