I am not syre if I am the only one who has this issue, but any Android device I had had never really has had good push notifications. Basically, it is hit or miss, mostly a miss. Various apps I never seem to get notifications, such as the eBay app. Notifications are enabled and it seems like they only work if I am actually in the app, but if it is not open, no notifications. Or same with Words with Friends, it pretty much never sends me a notification and when it does, it could take 30 minutes for it to show up while my iPhone would show up immediately. Even when using the Lumia 920 for a few weeks, the notifications came through with out delay. Anyone have any ideas to why this is?
are you closing processes? task killer apps may stop them
I am not closing anything.
Does each app have their own process for push? And how does push work? What I mean by that is I know with Apple, push is controlled through their backend. Is Android the same way?
Related
Is there any way either via buildprop, xposed, etc.. to disable the App crash notifications? Even better only for specific applications?
I have one application that misbehaves and forces closes randomly. The obvious answer would be "Don't use it then" BUT there is no other keyboard that works like this/the way I want. There doesn't appear to be any rhyme or reason and it opens/restarts itself just fine. In short, I don't care that it is crashing.
bump
Bam, a year later and I still have this question because it resurfaced.
Grab a logcat and send it to the app developer is your best option.
Hey,
I just installed H2OS and I can say it's pretty nice. I could configure anything to meet my demands.
Only one thing bothers me. For example if I close the Facebook Messenger from task manager I no longer get notification when I receive messages. I even tried to give app permission to autorun but no success. Also the apps hibernation feature is turned off.
Does anyone know how to fix this?
Thanks!
raulx222 said:
Hey,
I just installed H2OS and I can say it's pretty nice. I could configure anything to meet my demands.
Only one thing bothers me. For example if I close the Facebook Messenger from task manager I no longer get notification when I receive messages. I even tried to give app permission to autorun but no success. Also the apps hibernation feature is turned off.
Does anyone know how to fix this?
Thanks!
Click to expand...
Click to collapse
The Task Manager of h2Os is different from the normal Recent App Killer on Android, when we swipe to left it kills the app as well as all the background services associated with it ... SO I suggest you swipe it to the right and lock it in Recent's menu ...
Also many times when on Wifi and phone goes in deep sleep mode the apps are automatically closed or put in hibernation mode and don't come out of it until we open that app .
Hello @oasisfeng
Ive been using of greenify since the beggining ive rooted my device and now that MM is out which im also using since it was released on my nexus 5 device i still used greenify
Right now i have to uninstall it for one particular reason. It doesnt sync in notifications anymore.
I do know that "doze" limits notifications but opens background sync up in a short time for every minute or hours of interval. I do know greenify forces apps to go to "app standby" mode or forces apps to defer background process without exiting them on 6.0+ this means that the general "wait time" for push notifications are also deffered.
I do know there is a "wake up service" for greenify that intends to wake up device services again when hibernated from time to time but to be honest i think it is inefficient.
So haveyou tried creating an alarm that cuts the hibernation off for a small second to quickly sync in background process and push notifications from apps such as xda labs or messenger? You can do it by creating an alarm with a code of setandallowwhileidle()
Hope you read this and ill be waiting for your feedback, in the meantime ill be uninstalling greenify also its donate package and wait for further improvements
Cheers!
Instant messaging apps should generally be excluded from Greenify unless it supports GCM "high priority" push on Android 6.0+. This is the recommended solution mentioned in the app description and FAQ.
Do you mean the Greenify did sync in notifications in the past but not now? Can you give me a specific version number of Greenify that worked for you?
If I understand correctly, you want to wake-up apps periodically. It has been discussed actively in the early time. That derived a large set of functionality requirements, such as interval settings, settings per app, black-out duration, conditional wake-up, and etc. Even the worse, the longer interval, the less timely notification while the shorter interval, the more battery consumption. It is hard to balance, compared to the real right solution - GCM push. In summary, this idea introduced too much complexity.
As always, if you want to achieve that purpose, I'd suggest using Tasker together with the "wake-up" plug-in function provided by Greenify. Why do you think it is inefficient?
BTW, the solution of setAndAllowWhileIdle() is not the answer you may expect. If you are a developer and have read the documents, you should know this API is strictly limited and it also defeats the purpose of Greenify.
oasisfeng said:
Instant messaging apps should generally be excluded from Greenify unless it supports GCM "high priority" push on Android 6.0+. This is the recommended solution mentioned in the app description and FAQ.
Do you mean the Greenify did sync in notifications in the past but not now? Can you give me a specific version number of Greenify that worked for you?
If I understand correctly, you want to wake-up apps periodically. It has been discussed actively in the early time. That derived a large set of functionality requirements, such as interval settings, settings per app, black-out duration, conditional wake-up, and etc. Even the worse, the longer interval, the less timely notification while the shorter interval, the more battery consumption. It is hard to balance, compared to the real right solution - GCM push. In summary, this idea introduced too much complexity.
As always, if you want to achieve that purpose, I'd suggest using Tasker together with the "wake-up" plug-in function provided by Greenify. Why do you think it is inefficient?
BTW, the solution of setAndAllowWhileIdle() is not the answer you may expect. If you are a developer and have read the documents, you should know this API is strictly limited and it also defeats the purpose of Greenify.
Click to expand...
Click to collapse
I havent tried testing whileidle() to be honest i just read it multiple times on google sources and the likes.
For your suggestion on tasker i would not recommend it. There has been an endless discussion on tasker if it was battery friendly or not and i know for a fact that it is not. The problem with tasker is its constant background monitoring which depends on your "trigger" and "event" so yep i wouldnt use tasker to automate things anytime soon.
And yes. Waking up apps periodically is the thing that i would like to propose though it might contradict M's doze mode. So overall just now im with you that its not a good solution for messaging apps.
I dont remember it was years ago way back when im using kitkat and a non-famous brand phone locally made here in our country, but as far as i remember messenger really still doesnt tickle a notification update.
So bottomline right now theres no solution for messaging apps other than leaving it as it is right? The problem is that those messaging apps have the highest background drain so i guess i had to adjust myself using messenger lol
phantom146 said:
I havent tried testing whileidle() to be honest i just read it multiple times on google sources and the likes.
For your suggestion on tasker i would not recommend it. There has been an endless discussion on tasker if it was battery friendly or not and i know for a fact that it is not. The problem with tasker is its constant background monitoring which depends on your "trigger" and "event" so yep i wouldnt use tasker to automate things anytime soon.
And yes. Waking up apps periodically is the thing that i would like to propose though it might contradict M's doze mode. So overall just now im with you that its not a good solution for messaging apps.
I dont remember it was years ago way back when im using kitkat and a non-famous brand phone locally made here in our country, but as far as i remember messenger really still doesnt tickle a notification update.
So bottomline right now theres no solution for messaging apps other than leaving it as it is right? The problem is that those messaging apps have the highest background drain so i guess i had to adjust myself using messenger lol
Click to expand...
Click to collapse
IM app without GCM push is such a pain, since it usually tries its best to improve the real-time notifications, at the cost of power consumption. In my experience, even a 5 minutes interval wake-up is far from enough for a IM app, but already increases the power consumption a bit.
oasisfeng said:
IM app without GCM push is such a pain, since it usually tries its best to improve the real-time notifications, at the cost of power consumption. In my experience, even a 5 minutes interval wake-up is far from enough for a IM app, but already increases the power consumption a bit.
Click to expand...
Click to collapse
Agreed and again facebook and messenger is to blame for the poorly written codes and the messy services they all have.
Right now my issue is solved and im glad for such a quick and concise response. Ill be waiting for the future beta releases and in the meantime if you need my help for an upcoming feature on M count me in, and ill also throw down "possible suggestions" for you and maybe give you some codes for it
Cheers bud
So I've had some annoyances with my new S9+ that I've never seen before. I'm not sure if it's a Samsung issue or an Oreo one.
So I'm getting some warnings in my notifications area. Now I get the idea behind it, but there's no way to approve apps. For instance, I get a warning that Waze was using the microphone. I approved that permission, yet every time I use Waze, I get the warning. I get a warning that Google Music is using a lot of CPU. Lastly, I'm getting a warning that Handcent SMS is accessing, you guessed it, SMS.
Again, I understand the idea behind it. However, two of these are working "as intended". I'm wondering if there's a way to whitelist apps so this notification doesn't appear every time.
If anyone needs to know how to fix this, I found it on Google.
Settings > Lockscreen and Security > App Permission Monitor.
Then you can turn that all the way off, or off for specific apps.
As the title suggests lately I've been having issues with Kik, maybe it's just the latest builds that rolled out with the recent updates or maybe even prior to them perhaps, before that I was rather using an year old Kik version since I never update my phone for long.
I updated (time and time again after the issue, reinstalling/installing it back again and again) without any success with the issue. Messages just lag randomly and might take up from 15 minutes to hours before I receive them if the device is on standby mode or sitting idly.
For instance, if the app is running in the foreground/background when the screen turns off, any message I receive 15 minutes after that screen off will delay unless I do something on my phone. If I am using another application as simple as discord or a simple game as Delight Choice text based app it does the same, if someone doesn't text me during those 15 or so minutes after that app switch, after that any messages that are sent to me I never get them and the people sending me those texts reported that the messages were stuck on S. Another example of the delayed message would be this, I tried turning the caffeine mod on and just kept the app in the foreground with no other apparent app running in the background except for the system ones. I just kept my phone as such, the screen was on but I just didn't do anything at all on it, thought maybe I could avoid it with that perhaps but nada, I picked up my phone touched kik entered a chat randomly and messages suddenly started popping up in my notifications.
It's either a recent bug or server issues, I've had them before too but not to this extent which would be back to normal once I uninstalled and installed the application back. I thought maybe it was the modified Kik perhaps, or maybe Xkik since I used to use that before but even that wasn't the case. I would just disable xkik module and kik would have been back to normal if there were any issues. But not this time, even the normal Kik is giving me the same issues with delayed messages.
Since there isn't any support forum for kik, no support email either and I got on the play store to find some of the users complaining about the same issues. Well at least I am not alone, and the issue is not easy to reproduce on other devices so I am stuck with this right now.
Also, I am not using any power saving apps (I was but I uninstalled them all to see if they were causing the issue), kik is not being optimized for battery, my battery is on performance mode along with kernel adiutor which I have set the CPU on performance mode. There isn't any low memory killing going on since I have plenty of ram remaining and have set LMK at very low. I am at a real stalemate here and hope to find some answer or resolution to it.
Right now I have activated heads up notification and put kik notifications to be treated as a priority. I will post the results if any, hope that helps me out with these delays.