Background apps super low priority / not triggering - T-Mobile Samsung Galaxy S 4

My SGS4 (T-Mobile) is a bit over 2 years old now. I had been running a modified TouchWiz rom (I believe it was this one: http://forum.xda-developers.com/showthread.php?t=2679913), but recently I started having problems where the phone was missing triggers - alarms wouldn't go off, TextSecure would receive all my messages all in one big lump only after I opened the app, stuff like that.
I tried reflashing a number of ROMs, and I've currently landed on a recent CM12.1 nightly, but I'm still getting this problem where apps running in the background don't seem to have enough priority to get the phone to wake up and alert me that something is happening.
Does anyone know of a way to figure out what's going on? Any suggestions on diagnosing this?
(I have tried messing with PrivacyGuard on CM12.1, in case it's a separate issue, but the problem persists with it enabled or disabled).

Related

[Q] Missing Notifications

Hi again.
After a while of running with CM7.1, I took a chance on the KANG version of CM7.2. Now, I'm impressed so far with some of the little tweaks - the lockscreen torch is great, and just what I needed.
However, last night I noticed that two apps I use regularly had stopped giving me notifications. One of these is Wordfeud, which to be honest, I'm not fussed about - but the other is Sportmate, which gives me goal alerts etc when my team are playing. Has anyone else on CM7.2 had this issue? Is it fixable?
Try to install this. Looks like they changed the name of the app. Maybe they changed more than that.
Yeah, I actually saw that after I posted - not sure of the details, apparently the original app had breached Google's terms. However, while I'll see if the new app works fine, I doubt it's the app that's causing the problem, as Wordfeud also has the same issue.
Okay, I give up. Having reinstalled Wordfeud (well, replaced with the paid version)... notifications are now working. Assuming that the reinstall of Sportmate will now also works, it appears I'm just actual crazy.

[Q] Phone freezes and is slow after all kinds of troubleshooting

Hello,
I've done lots of searching for answers to my questions here and elsewhere and come up empty-handed, so I apologize if I've missed something and this has been covered already.
My phone occasionally runs smoothly and fast, like it's supposed to. More often -- pretty much every time I need to interact with the phone and across all apps I use -- it freezes when I tap on something, whether it's to open an app or interact with an app that's already running. It will completely freeze up for anywhere from five to 15 seconds before reacting, and it's extremely frustrating at times. Sometimes, the screen will time out before I can enter my PIN to unlock it; sometimes when somebody calls and I tap "answer," the phone doesn't react fast enough to actually answer and I miss the call. As I said, very frustrating. It did this both before the update to Lollipop last week, and after.
Here's what I've tried: Hard reset; restarting; deleting or disabling all the apps (including Blinkfeed) I thought I safely could, usually just one or two at a time. I've run it in safe mode, and the phone works normally that way -- I just can't figure out what's making it freeze up. I've run a CPU monitor program, and haven't seen any huge spikes from any apps; and according to the app manager in settings, I typically have about 1G of RAM free.
I'm very hesitant to root the phone, mostly because this is a warranty replacement for a Verizon M7 I had rooted (and returned to stock), and none of the ROMs I tried with the previous phone worked well -- if at all -- with the security policies I am required to use to log in to my employer's Exchange server. Those policies include data encryption.
I'm running stock Lollipop 5.0.2 and Sense 6.0 on Build number 6.22.605.3, Baseband 1.13.41.1209.
If anybody has ideas for me to try, I'd greatly appreciate it. My upgrade date is late August of this year, but it's getting harder and harder to live with this phone, which I absolutely need for my work.
Thank you very much in advance.
It's been a month now since the Lollipop update. I have read through a few threads about performance issues in general after the update. I am going to assume that your phone too has become a victim of the update. I have NOT updated to Lollipop. Mainly because of my recent root and install of TWRP custom recovery, EX Kernel and ViperROM 7.0.2. If these issues aren't resolved, I will not update. Besides, KitKat is doing great for me. I would suspect certain services not running in safe mode that allow the phone to react normally as opposed to all services running in normal mode. Have you contacted VZN and/or HTC for possible t/sing solutions? I see that you have done what I would've done. After failing I would assume it is because of the Lollipop update

Screen Waking Problem (Damaged S4)

Hellol
So I have an old S4 and have a problem that I imagine is due to my girlfriend dropping the phone but would like to hear if anyone has an idea of what is going on.
So basically the phone screen wakes every 5-30s (seems to be a random time interval I have used a stopwatch to make sure it wasnt predictable) I originally assumed it was a kernel problem so I switched kernels, then switched roms, then went back to 100% stock and this behaviour happens on every single rom and every single configuration Touchwiz / aosp / CM / Google Edition everything I have tried.
What is strange is something I noticed that is a work around which is that if I play music in the background it never wakes. So basically what I am doing now is having music playing 24/7 and the volume down all the way so I cannot hear it. This is a pretty acceptable work-around but I was wondering if one of you clever folks would maybe have some idea what is going on and why playing music fixes it.
Damage: Screen is cracked in the top left corner where the sensors are, this why I am just assuming is phyically damaged something that.
Current OS: CM 12.1 Nightly.
Tried stock battery + aftermarket battery just in case it was that.
Any insight would be greatly appreciated! Thanks.

Not receiving notifications unless I wake screen in OnePlus 3 running Marshmallow

Hi there, I was wondering if anyone might have any suggestions on how I could disable the Android Marshmallow doze/deep sleep mode that is default on new devices to save battery. I have a OnePlus 3 and have made every effort to check that all my notifications for calendar, whatsapp, emailing, etc. are set to both vibrate and make a sound, disabled all battery optimization features for apps, tried using screenlock wake apps to avoid missing notifications, and more. However, I am still unable to get notifications for whatsapp, emails, calendar reminders and events once my screen goes to sleep or I lock then phone and it's idle (so after about 15-30 minutes of it sleeping), but calls and texts seem to come through fine (or at least I haven't noticed these being an issue as much). This is a HUGE inconvenience, as my main reason to have a smartphone is so I can check emails, calendar events and such right as I receive them, and not only when I wake up my screen (which then bombards me with all my previous missed notifications from hours before). I have a feeling this is an android 6.0 issue and not due to the OnePlus 3, because it's been reported in other sites and by people with phones also using either this OS or lollipop. My older Samsung galaxy S4 running kitkat never had these problems, and at this point I'm very keen on going back if I can't get my new phone (or this OS, as I predict) to notify me right away even when my screen is locked and phone asleep (I can't always remember to check it especially if I'm busy at work). I am willing to root the phone and change settings if that's an option, but I would please like to see if you guys have any other suggestions for allowing my phone to receive notifications right away even when in sleep mode/idle/dozing. Thank you for your time in advance. Oh last thing, I also posted this question in other forums because I am honestly quite desperate to find out what I can do to resolve this issue, so I'm sorry if that's an inconvenience...
mblancoc said:
Hi there, I was wondering if anyone might have any suggestions on how I could disable the Android Marshmallow doze/deep sleep mode that is default on new devices to save battery. I have a OnePlus 3 and have made every effort to check that all my notifications for calendar, whatsapp, emailing, etc. are set to both vibrate and make a sound, disabled all battery optimization features for apps, tried using screenlock wake apps to avoid missing notifications, and more. However, I am still unable to get notifications for whatsapp, emails, calendar reminders and events once my screen goes to sleep or I lock then phone and it's idle (so after about 15-30 minutes of it sleeping), but calls and texts seem to come through fine (or at least I haven't noticed these being an issue as much). This is a HUGE inconvenience, as my main reason to have a smartphone is so I can check emails, calendar events and such right as I receive them, and not only when I wake up my screen (which then bombards me with all my previous missed notifications from hours before). I have a feeling this is an android 6.0 issue and not due to the OnePlus 3, because it's been reported in other sites and by people with phones also using either this OS or lollipop. My older Samsung galaxy S4 running kitkat never had these problems, and at this point I'm very keen on going back if I can't get my new phone (or this OS, as I predict) to notify me right away even when my screen is locked and phone asleep (I can't always remember to check it especially if I'm busy at work). I am willing to root the phone and change settings if that's an option, but I would please like to see if you guys have any other suggestions for allowing my phone to receive notifications right away even when in sleep mode/idle/dozing. Thank you for your time in advance. Oh last thing, I also posted this question in other forums because I am honestly quite desperate to find out what I can do to resolve this issue, so I'm sorry if that's an inconvenience...
Click to expand...
Click to collapse
Here is over 900 posts on this issue for your reading pleasure.
https://forums.oneplus.net/threads/push-notification-issues.451149/
Problem solved
Oneplus just released a new oxygen OS update which takes care of the notification issues. But to resolve this before this OTA came out I rooted and disabled the doze mode with dumpsys deviceidle. So all is good now!
mblancoc said:
Oneplus just released a new oxygen OS update which takes care of the notification issues. But to resolve this before this OTA came out I rooted and disabled the doze mode with dumpsys deviceidle. So all is good now!
Click to expand...
Click to collapse
Problem was NOT SOLVED with 3.2.1 OTA you still need to disable Doze in order to fix it.
Sent from my SM-T810 using XDA-Developers mobile app

Text messages / notifications not coming through

Hi!
First of all, I'm new to this phone - I owned it for about 2 weeks. and I'm very happy with it. Nonetheless I have noticed an issue that I hope someone can help me out with:
Since the phone doesn't have the notification LED, I have tried out a couple of apps to facilitate this function. I ended up uninstalling them. Now I experience that some notifications are not coming through (so far I've noticed text messages). I'm trying to figure out whether this is an issue with the phone, or if it might have something to do with the notification apps that I tested? I configured the apps and settings/permissions as necessary to get them to work, but I never reset those same settings before I uninstalled.
The issue I am facing is e.g. if a text message is sent to my phone (with display not on), the text and/or notification randomly doesn't get through until I wake the phone. After waking it, the message comes through immediately. Could this have something to do with testing those notification apps? If so, is there any way to find the specific settings and reset them or am I facing a factory reset to get it to work properly again?
Any help or hint is appreciated

Categories

Resources