I have not made any changes to my phone settings but recently I noticed Tasker stopped working when the screen is locked. I use AutoRemote to receive a timed message from IFTT which is used in a profile in Tasker to execute some tasks. This has worked flawlessly for months but recently it stopped. The profile and task work correctly when the screen is on though. I have tried all the various battery and Tasker settings but cannot seem to fix this new problem.
Anyone else having this problem?
Related
I've got this weird problem. I installed Tasker and originally restored a backup of my tasks from my OG Droid....none of them worked. Tasker shows that a certain profile is triggered in the Notification Shade but none of the tasks in the profile happen. My sound isn't changing automatically anymore, the speech engine isn't announcing the name of the caller, etc.
I thought maybe it was due to restoring a backup from a phone without the Sense UI...that perhaps certain calls were different. I uninstalled and reinstalled Tasker and just started to rebuild the profiles manually. They still don't work.
At this point I thought it was Tasker and I uninstalled and instead, for now, setup a couple of events in Sound Manager to just mute the sound (and unmute) during certain hours. They didn't trigger...I had to manually change the sound (which I can do in Sound Manager).
I'm lost as what would prevent these from going off when they should. They worked fine on my old Droid and I have pretty much all the sames apps, so I don't think anything should be conflicting. I'm just hoping someone smarter than I might have seen this behavior or might have an idea on what to check next....
Thanks
Ryan
I restored my tasks from my OG Droid to my Thunderbolt, and they all worked!
That's weird. I thought perhaps it was the Sense UI that was causing problems. I wonder why these events in Tasker and in Sound Manager aren't happening.
On a side note, possibly related. Cardio Trainer (in the music settings) doesn't let me pick from any of my playlists (where you select which it should use when playing music in a workout). Anyone else seeing this?
Could Kickback, Talkback and the other back app from Google cause a problem? I'm not really sure what they do....there were installed with CM7 and then auto-installed on the TB.
rckymtnrfc said:
Could Kickback, Talkback and the other back app from Google cause a problem? I'm not really sure what they do....there were installed with CM7 and then auto-installed on the TB.
Click to expand...
Click to collapse
Doubtful, I run those same apps too!
Well it's working again although I can't say why. It turns out I did have a dead touch point on the screen, right where the Y is on the landscape keyboard. Went into VZ and didn't have that problem on the 2 display models....and the tech confirmed it wasn't just me.
All my apps just finished auto-installing after signing into my Google account and Sound Manager is working fine. Odd.
It's funny you posted this, I downloaded tasker yesterday because I was going to set it to change to wifi for when I got home but I havn't done it yet. Good to hear it works
Fwiw, tasker has no effect on my tbolt. I'm running 12.605.9 (latest leaked fw)
---
Sent via Thunderbolt
In case anyone was wondering, I was running the stock version of Android that comes on the TB, hadn't even rooted yet.
Every night since I got this amazing phone I've been using the command "wake me up at..." or "wake me up in..." or "set an alarm at..." to set alarms for the next morning. Few days ago I noticed that the command stopped automatically setting alarm and instead prompts me to click the "Set alarm" button instead. Why is this happening? Every other commands seems to work - play music, open camera etc, etc. It's not a major problem but it bugs me. Do you guys have this problem? Can I fix it somehow or is it a server-side bug?
Apparently Google fixed the issue as of now, but it was definitely not working these past few days. Just to let you guys know, it was probably a bug in their servers or something
Hi All,
When i use Whatsapp-web, i noticed my phone has to be with display always on to 'not lose connection'.
If display goes off for a while, and phone is going in sleep mode, Whatsapp-web says; Connection lost, trying to reach phone..' It then reconnects automatically in some minutes, or immediately when i put the screen on. I did disabled 'doze' for Whatsapp, so battery optimization is not applied on the Whatsapp app itself.
Seems like on wifi, connection is more stable, but still get this message now and then.
Might not be a Galaxy S7 specific problem, but i have this problem since i use this phone.
I can't remember that i had this problem on android 6, or android 4.
Is there some way to fix this?
Probably a WhatsApp problem, I know to stop apps from being closed with Nougat they have started adding a permanent notification whilst they are running, this stops Nougat closing them after a while of the screen being off
*Detection* said:
Probably a WhatsApp problem, I know to stop apps from being closed with Nougat they have started adding a permanent notification whilst they are running, this stops Nougat closing them after a while of the screen being off
Click to expand...
Click to collapse
Seems that setting the app to 'high priority' it does the trick. Thanks.
Hi everyone,
I'm running 6.0.1 and recently performed a hard reset and cleared caches to try and resolve the problem.
Did not resolve. Also disabled power managment for apps. Problem persists.
Whenever a calendar event is skipped (by the device) all future events stop working and I have to reboot to get the alerts back.
Mostly the problem comes when there is one emty day, but it also happened when I got a notification in the morning and in the evening nothing anymore.
Thus I thought it could be powersaving related, but powersaving is disabled.
It's really driving me crazy, my calendar is verry important to me as I tend to forget things.
Anyone knows how to resolve the problem ?
How to debug ?
Your input is verry much appreciated.
Thanks.
[June 25 2018]
It looks like I solved my problem by reading about push notifications here:
https://help.moengage.com/hc/en-us/...not-receiving-push-notifications-sent-by-you-
It got me thinking that GCM service in my Nokia 7 plus is not properly connecting with Google’s servers. So I looked around how to hard reset my device using this tutorial:
NOTE: [THIS WILL ERASE ALL YOUR DATA. MAKE A BACKUP OF YOUR FILES FIRST]
http://www.techeligible.com/2018/05/27/unlock-pattern-nokia-7-plus/
select Wipe data/factory reset.
After restart configure your phone as a NEW DEVICE. Push notifications seem to work as they should. They are waking the device from sleep mode immediately.
This method will most likely work for all Android devices.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[June 5 2018]
I really like this phone but the push notification problem just kills me.
When phone is in sleep mode push notification don't wake it up.
Just leave the phone on the desk for 15 minutes and send yourself an email from different device.
Same applies to WhatsApp. If someone sends me a message it can take half an hour before phone will show notification.
This is frustrating and apparently there is no fix.
I did even factory reset and the problem persists.
Tweaks like exclude app from battery optimazation don't work.
This clearly Android Oreo fault.
Google is so fixated to save battery that it castrates crucial functionality
+1 to the delayed notifications problem!
As you wake the device up, the Whatsapp icon also keep showing in the taskbar - "Checking for new messages" quite often.
that also happens at intervals while the device is ON & other apps are being run.
I hope this, the fingerprint navigation (left+right), battery SOT, stability will improve with proper update to Andro-P. and SOON!
Same problem here. "Heartbet" apps dont work either.
Same here! Maybe it's push notifications server problem?
pls. make sure that notification apps have permission to work in back ground as it may be restricted for battery saving
fady saher said:
pls. make sure that notification apps have permission to work in back ground as it may be restricted for battery saving
Click to expand...
Click to collapse
[SOLVED] First post.
----------------------------------------------------------------------------------------------------------------
Gmail and WhatsApp are excluded in battery optimazation. It makes no difference.
Gmail is a Google app. It comes with system but push notifications are not working properly.
There in no other way to set apps to work in background. At least I didn't find such option...
Didn't work for me. Anybody else managed to fix this?
Bump
Android Pie
Bump...ish
Anyone experiencing delayed push notifications on Android Pie?
Do you have location enabled (saving battery location setting)? Disabling location can cause notification delays.
yatoya said:
Do you have location enabled (saving battery location setting)? Disabling location can cause notification delays.
Click to expand...
Click to collapse
I never really turn off location services. Is this setting you are talking about the battery optimization for apps? I can turn that off for location services.
I have 1062 with pie sideloaded and i'm not getting any push notifications from apps except for gmail. Factory reset and setting phone as new device didn't help.
rooks_by said:
I have 1062 with pie sideloaded and i'm not getting any push notifications from apps except for gmail. Factory reset and setting phone as new device didn't help.
Click to expand...
Click to collapse
1062 (if chinese with custom global rom) its not really possible to install Pie, its not stable in this one, Oreo still best for 1062
rooks_by said:
I have 1062 with pie sideloaded and i'm not getting any push notifications from apps except for gmail. Factory reset and setting phone as new device didn't help.
Click to expand...
Click to collapse
I had the exact same issue and it was really frustrating me. Resetting my phone didn’t help as detailed here. But finally after some playing around i fixed mine
In the battery settings i enabled Adaptive battery and then went into background activity manager. I enabled both auto activate and lock screen on all the apps i had problems with receiving notifications. Now i get all app notifications straight away with no delays
nurrishd said:
I had the exact same issue and it was really frustrating me. Resetting my phone didn’t help as detailed here. But finally after some playing around i fixed mine
In the battery settings i enabled Adaptive battery and then went into background activity manager. I enabled both auto activate and lock screen on all the apps i had problems with receiving notifications. Now i get all app notifications straight away with no delays
Click to expand...
Click to collapse
I've tested this solution for a couple of days and it seems it's working, thanks.
nurrishd said:
I had the exact same issue and it was really frustrating me. Resetting my phone didn’t help as detailed here. But finally after some playing around i fixed mine
In the battery settings i enabled Adaptive battery and then went into background activity manager. I enabled both auto activate and lock screen on all the apps i had problems with receiving notifications. Now i get all app notifications straight away with no delays
Click to expand...
Click to collapse
Is this for Android 8? I am having the same problem but I cant seem to find the auto activate and lock screen settings in the BAM. The only option is to blacklist. I am on Android 9.