Auto Notification Rules Bug - Moto G 2015 Q&A, Help & Troubleshooting

Hey, I've been using the automatic rules for priority/do not disturb mode in Marshmallow, but I've noticed that lately the phone doesn't automatically turn off this mode after the specified time. For example, I have my class schedule in Google Calendar, and it doesn't exit priority mode after class. Same with nighttime; come morning, its still in 'alarm only' mode.
My phone is rooted, stock rom, w/ xposed framework. I've tried disabling Gravitybox, but that didn't help. I'm thinking it might be a bug with N-ify, because I think it started after I used that, but even if I disable that module, it doesn't fix itself. Otherwise the phone works fine.

viggy96 said:
Hey, I've been using the automatic rules for priority/do not disturb mode in Marshmallow, but I've noticed that lately the phone doesn't automatically turn off this mode after the specified time. For example, I have my class schedule in Google Calendar, and it doesn't exit priority mode after class. Same with nighttime; come morning, its still in 'alarm only' mode.
My phone is rooted, stock rom, w/ xposed framework. I've tried disabling Gravitybox, but that didn't help. I'm thinking it might be a bug with N-ify, because I think it started after I used that, but even if I disable that module, it doesn't fix itself. Otherwise the phone works fine.
Click to expand...
Click to collapse
Are you rebooting after disabling N-ify?

Yeah, I am.

Tel864 said:
Are you rebooting after disabling N-ify?
Click to expand...
Click to collapse
Yeah, I am rebooting after disabling N-ify. In fact, I just restored a backup from before N-ify, and I still have the same problem. I just did the system, cache and boot partitions though, didn't restore data, to save on space.

Solved. Just figured out that SoundAbout's notification listener is interfering with that mode.
Thanks guys.

Related

Slow Reboot

I have two applications that are slow to start after a reboot. They are Dashclock and Lightflow.
With regards to Dashclock, as soon as my device has reboot it displays nothing on the lockscreen for roughly a minute. I can unlock the device, use it, lock it and still nothing until it finally loads.
Same issue with Lightflow. My device will boot up and I won't get the notification that it is running until roughly a minute in.
The only other app I have starting up is Lux and Lux starts up fine with the device. I've tried uninstalling and re-installing Dashclock and Lightflow, but no success.
This morning was the day I rooted my device. I unlocked, which wiped all data, installed TWRP and then installed root. After all that was finished I re-installed all my apps and started getting all my apps configured again.
Is this slowdown related to root opening up new locations such as data?
Is there anything can speed this up? It's strange that Lux starts up properly while the other two do not.
I'm going to try searching some more and looking into it, but thus far I've not found anything. Since I can't find much, it seems like this isn't a common issue with either application.
I'm using a Nexus 5.
alamarco said:
I have two applications that are slow to start after a reboot. They are Dashclock and Lightflow.
With regards to Dashclock, as soon as my device has reboot it displays nothing on the lockscreen for roughly a minute. I can unlock the device, use it, lock it and still nothing until it finally loads.
Same issue with Lightflow. My device will boot up and I won't get the notification that it is running until roughly a minute in.
The only other app I have starting up is Lux and Lux starts up fine with the device. I've tried uninstalling and re-installing Dashclock and Lightflow, but no success.
This morning was the day I rooted my device. I unlocked, which wiped all data, installed TWRP and then installed root. After all that was finished I re-installed all my apps and started getting all my apps configured again.
Is this slowdown related to root opening up new locations such as data?
Is there anything can speed this up? It's strange that Lux starts up properly while the other two do not.
I'm going to try searching some more and looking into it, but thus far I've not found anything. Since I can't find much, it seems like this isn't a common issue with either application.
I'm using a Nexus 5.
Click to expand...
Click to collapse
Are you on ART?
Aerowinder said:
Are you on ART?
Click to expand...
Click to collapse
No, I'm on dalvik. Haven't touched ART at all.
Some more information, it seems this isn't related to Dashclock or Lightflow. The default lockscreen will show the clock on reboot, but the date and alarm underneath don't show up for roughly a minute.
Are there logs anywhere that could help pinpoint the delay?
I've noticed the same thing with dashclock. Stock dalvik.
Sent from my Nexus 5 using Tapatalk
Loads of Apps have to start up. Its common for some to be delayed. Further more, many will have dependencies on other system processes that need to start up first.
Its normal and there's not a lot to be done about it
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Loads of Apps have to start up. Its common for some to be delayed. Further more, many will have dependencies on other system processes that need to start up first.
Its normal and there's not a lot to be done about it
Click to expand...
Click to collapse
That's understandable. I just found it weird that it behaved differently from non-root to root. Especially with Dashclock since you're greeted with nothing except for the lock pattern upon boot.
May be this coz of any type of virus In application.
Or in Your Phone

[5.0]WiFi shows as on in battery settings always

Hello guys, out of all the bugs this is the one bothering me the most.
Battery settings show WiFi as on all the time no matter how i switch it off.
I have disabled all the settings like scanning always.
I flashed the factory image yesterday (not OTA) and waited till a full charge, now today even after a full charge its still the same.
Is this a common bug or just me??
UPDATE :Tested with a clean flash of the factory image and without any apps, the result was that the issue has been solved. It could probably be some app which isnt updated to work in 5.0 yet. (Probably Viber app)
Sent from my Nexus 5 using XDA Free mobile app
I didn't flash the image, just flashed it via multirom. I don't have that problem...If that happened to me I'd try to reflash to see if I could replicate the issue with no apps other than what comes with the image.
I just flash my ROM yesterday with the factory image too and now I'm facing the same problem.
Battery usage shows that Wi-Fi is always on even the phone is sleep.
Really want to know why... I think it really consumes the battery.
I flashed the factory image too. I have the same problem. WIFI is always on. Any idea?
I've got it, too. Clean flashed 2 times. Well, hopefully Google gets on it soon.
Same here. Clean install, no root, no tweaks.
I opened issue here https://code.google.com/p/android/issues/detail?id=79326
Solution
had the same issue. what i found out was that it was not an android issue, the issue is with viber app(atleast in my case it was). to confirm it try booting to safe mode and check you battery stats. safe mode disables all 3rd party apps. if it works then reboot normally and uninstall viber.
IKnowIRock! said:
Hello guys, out of all the bugs this is the one bothering me the most.
Battery settings show WiFi as on all the time no matter how i switch it off.
I have disabled all the settings like scanning always.
I flashed the factory image yesterday (not OTA) and waited till a full charge, now today even after a full charge its still the same.
Is this a common bug or just me??
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I updated OTA and I have the same problem. Wifi always on, battery sucking. I don't have the viber app.
try booting to safe mode just to check if it was caused by any other 3rd party application
Caelrie said:
I updated OTA and I have the same problem. Wifi always on, battery sucking. I don't have the viber app.
Click to expand...
Click to collapse
Well, turning WiFi off and rebooting "resolves" this issue too, but it's no solution at all, the "bug" is still present.
nexus.freak said:
had the same issue. what i found out was that it was not an android issue, the issue is with viber app(atleast in my case it was). to confirm it try booting to safe mode and check you battery stats. safe mode disables all 3rd party apps. if it works then reboot normally and uninstall viber.
Click to expand...
Click to collapse
Right this could be the reason. I clean flashed the factory image once again and now its not there without any apps installed. Viber could be the reason.
And btw for those who doesnt know about "Scanning always available" feature, you have to disable "Scanning always available" option in Advanced WiFi settings to truly switch off WiFi when you disable it. Otherwise it will always be on even if the phone goes to sleep. This is an Android feature. I have shown it the pictures of the 1st post.
So regarding the OP, should install apps one by one and confirm who the culprit is.
IKnowIRock! said:
Right this could be the reason. I clean flashed the factory image once again and now its not there without any apps installed. Viber could be the reason.
And btw for those who doesnt know about "Scanning always available" feature, you have to disable "Scanning always available" option in Advanced WiFi settings to truly switch off WiFi when you disable it. Otherwise it will always be on even if the phone goes to sleep. This is an Android feature. I have shown it the pictures of the 1st post.
So regarding the OP, should install apps one by one and confirm who the culprit is.
Click to expand...
Click to collapse
there was no need to have clean flashed again, you could have booted in safe mode(press and hold power off option) which disables all 3rd party apps. you could have figured it there. anyways for other people with the same issue you could try this and to figure out which app causes it, reboot back to normal and try force stopping each app and check. thats what i did to figure it out. Viber was the cause of the issue for me as i mentioned earlier

The phone does not wake up properly after flashing Oreo?

Hi there, your comments would be greatly appreciated.
To keep data, I flash the whole 8.0 stock firmware after removing -w.
After using days, the phone can't be easily unlocked, even by power key or by FPR. Sometimes, I need to wait a more long time for the phone waking up.
Sometimes the incoming call can't even wake it up, I can't answer the call.
Have reflashed the firmware with -w available then restore all my app via titanium backup. the issue persists.
Please help! How to tell which app prevent the phone from waking
Try factory reset and not restoring data with titanium rather Google backup
Sent from my Pixel using Tapatalk
Thanks. have tried clean install. everything is fine before restoring data with titanium.
So there must be some app which prevent phone from waking. Is there any chance of find this app.
PunishedSnake said:
Try factory reset and not restoring data with titanium rather Google backup
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I'd say just start over....
I'd say it's titanium backup restore itself
Sent from my Pixel using Tapatalk
thank you dude, will take a try.
If the issue persists you could give a list of the apps you install if you don't mind.. maybe we can figure out which one affects the unlocking. :highfive:
Sent from my Pixel using XDA Labs
I'm having a similar issue, but in my case I'm having trouble waking up the phone after it's been unplugged from the charger. If I use my phone all day after a full charge (and after rebooting), it's silky smooth, but the second I plug it in, the issue starts until I reboot again.
It might be extreme, but I've done this multiple times on previous phones. I restore half my apps, say the ones starting with A through M. If there's no problem, then I install half of what's left, say N through S, etc. Keep doing this as a process of elimination. Yes it's tedious but eventually you can narrow down the problem app and/or app data. You could also try restoring all of your apps without data, and if there's no problem then restore the data for half of the apps, etc.
Otherwise, as @PunishedSnake said, don't restore data (or even apps) at all with Titanium Backup. It sucks but we all occasionally have to do that.
I've since factory reset my phone with minimal app installation (no Google restoring of apps), but am still experiencing this frustrating glitch, even with/without unplugging the charger and rebooting.
Debating whether or not I should root (and downgrade).
Safe Mode fixed the problem. I will try to find the apps which prevents the phone from waking up.
How can I do this.
boojay said:
I've since factory reset my phone with minimal app installation (no Google restoring of apps), but am still experiencing this frustrating glitch, even with/without unplugging the charger and rebooting.
Debating whether or not I should root (and downgrade).
Click to expand...
Click to collapse
bush911 said:
Safe Mode fixed the problem. I will try to find the apps which prevents the phone from waking up.
How can I do this.
Click to expand...
Click to collapse
I think I've found the problematic app in my case. I've been using immersive mode through Custom Navigation Bar and after disabling it, my phone has become responsive again. After double checking the app's description in the Play Store, it seems the dev hasn't updated it for Oreo yet.
#FirstWorldFragmentationProblems
Edited: In order to fix this problem, simply use Tasker to disable Custom Navigation Bar's Immersive mode whenever you turn off the screen, and re-enabling it either when you unlock the phone, or only for specific apps (which is what I do).
Yes. try to enable immersive mode via this command
adb shell settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
now everything is fine.
boojay said:
I think I've found the problematic app in my case. I've been using immersive mode through Custom Navigation Bar and after disabling it, my phone has become responsive again. After double checking the app's description in the Play Store, it seems the dev hasn't updated it for Oreo yet.
#FirstWorldFragmentationProblems
Click to expand...
Click to collapse
bush911 said:
Yes. try to enable immersive mode via this command
adb shell settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
now everything is fine.
Click to expand...
Click to collapse
Glad to hear you were able to resolve your problem. In my case, I actually don't want immersive mode activated all the time so I may still have to root in order to selectively choose which apps I apply this command to.
Edited: In order to fix this problem, simply use Tasker to disable Custom Navigation Bar's Immersive mode whenever you turn off the screen, and re-enabling it either when you unlock the phone, or only for specific apps (which is what I do).

[SOLVED] Extremaly delayed push notifications

[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.

Question Notifications not pushing

Hi all,
I have been facing a weird issue of notifications not being pushed (some apps) on my S22U.
It was bearable in the beginning but now I am missing notifications of MS Teams and other important apps. Which quickly turns it into a nuisance.
I am rooted with latest magisk, lsposed - zygisk.
I would like to resolve it without reflashing my firmware again. Any help is appreciated.
Few things I have tried.
Checking if the notifications settings is on of the app.
Checking if I have not accidentally enabled DND (which is off)
Restarting the device.
Googling if someone have similar issue.
Reinstalling the app.
Clearing app data.
Disabling and re-enabling the notifications.
Thanks in advance.
nishantgupta107 said:
Hi all,
I have been facing a weird issue of notifications not being pushed (some apps) on my S22U.
It was bearable in the beginning but now I am missing notifications of MS Teams and other important apps. Which quickly turns it into a nuisance.
I am rooted with latest magisk, lsposed - zygisk.
I would like to resolve it without reflashing my firmware again. Any help is appreciated.
Few things I have tried.
Checking if the notifications settings is on of the app.
Checking if I have not accidentally enabled DND (which is off)
Restarting the device.
Googling if someone have similar issue.
Reinstalling the app.
Clearing app data.
Disabling and re-enabling the notifications.
Thanks in advance.
Click to expand...
Click to collapse
Make sure battery optimization is turned off on the affected apps & that you have data enabled in the background as well on each affected app.
KOLIOSIS said:
Make sure battery optimization is turned off on the affected apps & that you have data enabled in the background as well on each affected app.
Click to expand...
Click to collapse
Tried on affected app. Bg data is on and gave unrestricted battery usage. Still nothing.
nishantgupta107 said:
Tried on affected app. Bg data is on and gave unrestricted battery usage. Still nothing.
Click to expand...
Click to collapse
How about in the phone's device care/battery settings? Is the power saving option turned on?
Just spit-balling here, but, I myself forget to turn it off (sometimes) on a new device set-up/after a factory reset. Guessing power saving option turned on could possibly affect timely notifications.....
Checked. Power saving is off. Appreciate the spit-balling, never know what will work.
same issue here, i hear notification sounds, but never pop-up message or screen wake-ups.
just beeps...no solution found so far
I don't even get the chimes. I have watch 4 too. Thought if not on phone it might get pushed on watch, but no luck there too
malikin said:
same issue here, i hear notification sounds, but never pop-up message or screen wake-ups.
just beeps...no solution found so far
Click to expand...
Click to collapse
This happens to me with LinkedIn: I get notif sound, but no pop up and icon on top bar. If I swipe down the notification is there though.
I am not getting any indication, no notification in statusbar and notification bar and no notif sounds. Weird that it is happening on some apps. I think some magisk module might be culprit but not certain.

Categories

Resources