Status Update
Comments
st...@gmail.com <st...@gmail.com> #2
Information redacted by Android Beta Feedback.
ak...@google.com <ak...@google.com>
ne...@gmail.com <ne...@gmail.com> #3
The phone is at full charge most of the time and on WiFi. I have Battery Saver and Adaptive Battery turned off. Many apps are affected including Gmail, Signal, Slack, and Phanpy (a PWA in Chrome). I'm running Android 14 on a Pixel 8, Build Number AP1A.240305.019.A1.
I made a Reddit post about this about a month ago which people keep finding. New comments every day saying "this is happening to me too, is there a fix?" Not many details in most of the comments but may be a source of info from other affected users.
fg...@gmail.com <fg...@gmail.com> #4
fg...@gmail.com <fg...@gmail.com> #5
go...@colinpritchard.com <go...@colinpritchard.com> #6
I've set various apps to unrestricted battery usage in case that affected things but continue to expressive the opportunity!
Searching again today because WhatsApp (which I have set to unrestricted battery usage) notifications didn't arrive until I unlocked my phone and were from 15 minutes ago. Battery is >80% and both WiFi and 4G were available. My phone was not in DnD mode.
I have a Pixel Watch 1 which the phone is connected to via Bluetooth but I was not wearing this at the time.
Don't remember encountering anything similar with my Pixel 7 Pro or any other android devices.
fg...@gmail.com <fg...@gmail.com> #7
ak...@google.com <ak...@google.com> #8
an...@gmail.com <an...@gmail.com> #9
ne...@gmail.com <ne...@gmail.com> #10
I think I fixed this problem on my phone by turning off "Adaptive Connectivity". I don't know what that setting is supposed to do but it seems to be breaking timely notifications. Details in
ro...@gmail.com <ro...@gmail.com> #11
For me at least following apps are affected (most important for me): Whatsapp, Gmail, MS Teams.
The notifications are not always delayed, but most of the time (could be 5 mins, 10 mins, ... , 45 mins, etc.).
And if I pick up the phone and unlock the display, the notifications come in or in some cases only when I open the related app.
The most unpleasant thing for me is, that also MS Teams calls (not only messages) are sometimes affected. Suddenly I get a missed Teams call notification, but the phone was not ringing. I have a very good and stable Wifi connection, so it's definitley not related to a bad network connection.
qd...@gmail.com <qd...@gmail.com> #12
th...@gmail.com <th...@gmail.com> #13
to...@gmail.com <to...@gmail.com> #14
Been like this since March I think. The the screen is turned in the notifications comes.
bl...@gmail.com <bl...@gmail.com> #15
Turning off "Adaptive Connectivity" and "Battery Manager" as adviced does not solve the problem.
Can confirm this bug was introduced with QPR2 in March and no following updated solved it.
29...@gmail.com <29...@gmail.com> #16
Notifications from the security GPS tracker for my kid don't arrive in time for me to respond in an emergency rendering the service almost useless. My wife's iPhone continues to receive them instantly.
I get a deluge of other delayed notifications when I wake up the phone after the screen has been off more tha 5 minutes or so. This is a critical bug that needs fixing ASAP..
ic...@gmail.com <ic...@gmail.com> #17
ak...@google.com <ak...@google.com> #18 Restricted
ak...@google.com <ak...@google.com> #19
Thank you for reporting this issue.
From the log analysis, things look normal to us.
If the issue persists, please file another bug with a newer bug report that includes:
- the time at which the notification was expected
- the time it was actually received.
- the app which the notification is expected
We also took a look at some of the other comments and they do not appear to be related to the issue described by the original issue.
In the future we would need a separate bug with bug reports to investigate each issue further.
st...@gmail.com <st...@gmail.com> #20
What
Feature request
I've raised another bug. Bumping this.
Where
Build and device data
- Build Number: google/oriole_beta/oriole:VanillaIceCream/AP31.240426.023.B4/11882682:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 242213038 (24.22.13 (190400-638740827))
System App (Updated)
Android System WebView
com.google.android.webview
Version 642216533 (125.0.6422.165)
System App (Updated)
Network operator: EE
SIM operator: EE
Filed by Android Beta Feedback. Version (Updated): 2.43-betterbug.external_20240522_RC03 (DOGFOOD)
To learn more about our feedback process, please visit
st...@gmail.com <st...@gmail.com> #21
Information redacted by Android Beta Feedback.
ve...@google.com <ve...@google.com> #22
ve...@google.com <ve...@google.com> #23
st...@gmail.com <st...@gmail.com> #24
What
Feature request
This is still an issue in the latest android 15 beta.
Where
Build and device data
- Build Number: google/oriole_beta/oriole:15/AP31.240517.031/12012872:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 242335038 (24.23.35 (190400-646585959))
System App (Updated)
Android System WebView
com.google.android.webview
Version 647813433 (126.0.6478.134)
System App (Updated)
Network operator: EE
SIM operator: EE
Filed by Android Beta Feedback. Version (Updated): 2.43-betterbug.external_20240522_RC03 (DOGFOOD)
To learn more about our feedback process, please visit
st...@gmail.com <st...@gmail.com> #25
Information redacted by Android Beta Feedback.
ak...@google.com <ak...@google.com> #26
We have taken a look at the bug report and do not see any sent messages for a specific app.
Could you please help us with the following information to investigate further?
1. Name of the app/app package
2. Expected receipt time of notification
3. Actual receipt time of notification
bl...@gmail.com <bl...@gmail.com> #27
2 and 3. (Actual notification receipt time - Expected receipt time) varies from notification to notification, if the device is awake notifications show up immediately, if it is not it must either be awaken manually or the notification may come up from 2-3 minutes late to 1-2 hours.
Disabling doze from adb resolves the problem but obviously kills the battery, it's not a solution.
ak...@google.com <ak...@google.com> #28
Thank you for your response.
ak...@google.com <ak...@google.com> #29
-
Would you be able to clarify what the original "banking transaction" app is?
-
We are currently trying to verify that the messages are actually being delayed due to doze. However from the bug report we are not seeing any messages queued up due to doze being delivered upon exit from doze.
-
Furthermore, we are not seeing any push notifications from the mentioned apps.
st...@gmail.com <st...@gmail.com> #30
st...@gmail.com <st...@gmail.com> #31
gy...@gmail.com <gy...@gmail.com> #32
sa...@gmail.com <sa...@gmail.com> #33
Support told me to reset the phone, but that didn't help. As a result, I lost all my data in vain. This is a really big problem :/ I hope Google will solve it soon....
se...@gmail.com <se...@gmail.com> #34
The application that I used is LINE Messaging. it already set to receive the message in background (Unrestricted) but the issue still happens.
This is very critical issue to me. I hope google solve this issue as soon as possible.
te...@gmail.com <te...@gmail.com> #35
te...@gmail.com <te...@gmail.com> #36
Quite frankly, I have to wonder if Google did this change on purpose to improve notoriously bad battery life on Pixels, and probably won't fix the fact this murders notifications. I switched from Samsung - think I may have made a mistake.
te...@gmail.com <te...@gmail.com> #37
As you can see, this is a longstanding issue by design that Google will likely never fix. If they would just give us the option to disable doze on a per-app basis, that would be a decent workaround. As it is, it's all or nothing. Having instant notifications is EXTREMELY important for certain applications, such as security cameras and doorbells.
You can use an app called Doze Stopper on the playstore to fix this, instead of relying on the adb command.
Finally, Google are increasing the speed at which a phone enters Doze by 50% for Android 15 - they are making this issue worse, not better.
te...@gmail.com <te...@gmail.com> #38
Guess what else - Gmail. That's why you often see complaints about Gmail stuff not being pushed through properly versus other 3rd party clients.
Since we can't rely on app devs to use their notification overrides for doze properly, we NEED to be able to manually turn off doze on a per-app basis. This used to be possible when it was first introduced in Android 6. I have no idea why this is no longer possible.
ad...@gmail.com <ad...@gmail.com> #39
je...@gmail.com <je...@gmail.com> #40
This kind of thing is happening ALL THE TIME with the Pixel phones, and it's been an issue for a while. My wife's Pixel 6 is doing the same thing.
This needs to get addressed ASAP. I miss calls, texts, and important emails all the time because of this issue.
ad...@gmail.com <ad...@gmail.com> #41
Total waste of time so I've booked it in for collection and will either return to using my iPhone SE or look for an alternative with a ≤6.1" screen.
ad...@gmail.com <ad...@gmail.com> #42
I realised that notifications were almost instantaneous during charging, which pointed to doze as the culprit. I also discovered that Gmail, Ring etc., notifications would arrive <6 minutes after locking the device, but beyond that, nothing. Someone on Reddit suggested disable doze via ADB, but the terminal command failed due an issue with permissions, so I tried out an app called "Doze Stopper" which seems to work fine.
Not sure what impact on the battery this will have but to have to go to these lengths just to receive time-sensitive and important notifications really isn't good enough.
sa...@gmail.com <sa...@gmail.com> #43
gy...@gmail.com <gy...@gmail.com> #44
For now I disabled doze with "dumpsys deviceidle disable" in a local terminal with root, most of the times seems solved (and I noticed no battery impact, the device still goes into deep sleep without doze), even though some times I still get delays
ds...@gmail.com <ds...@gmail.com> #46
How many of these impacted apps actually send ttl 0 and property high with their firebase messages to make sure notifications are received timely? Android purposely delays certain notifications not sent with high priority which is not a user controlled parameter.
se...@gmail.com <se...@gmail.com> #47
ad...@gmail.com <ad...@gmail.com> #48
sw...@gmail.com <sw...@gmail.com> #49
la...@gmail.com <la...@gmail.com> #50
kc...@gmail.com <kc...@gmail.com> #51
dp...@gmail.com <dp...@gmail.com> #52
jf...@gmail.com <jf...@gmail.com> #53
I have a thousand f*cking dollar paperweight. F*ck you.
My P8P will be my first and last Pixel.
kc...@gmail.com <kc...@gmail.com> #54
pe...@gmail.com <pe...@gmail.com> #55
None of the suggested fixes are working: adaptive battery is off, impacted apps are having the battery setting to always allow in the background, notifications are on, etc. It's kind of annoying one of the most widely used messaging applications has this problem.
xx...@gmail.com <xx...@gmail.com> #56
For notifications not being received at all, it seemed to be related to apps that were transferred over during device setup. If I reinstalled those apps, it seemed to resolve it.
However, even after fixing that, I am still seeing delayed notifications for many apps.
I'm a huge fan of this platform, but please take this seriously and find a fix.
lu...@gmail.com <lu...@gmail.com> #57
Perhaps turning off "Adaptive connectivity" could be a workaround?
If this isn't fixed, I'm jumping ship to another phone manufacture by Christmas time since Google doesn't seem to care (or have the capability to fix bugs).
fr...@gmail.com <fr...@gmail.com> #58
Notification lasts few minutes, sometimes more than 20...
iPhone XR with iOS 18 sends them instantly, I keep my gmail account open on my PC and when the email appears, iphone rings.
vv...@google.com <vv...@google.com> #59
In regards to gmail, since the priority of the message is set as Normal, this is WAI. If you have a report for a specific app then file a bug with the details including:
1.Which app, 2.Timestamps for the issues 3.The bugreport. For all other reporters, please open a new bug with a relevant bug report.
mu...@gmail.com <mu...@gmail.com> #60
I am facing it with almost every app except messages and WhatsApp (but sometimes get delayed).
The main apps that I use face this issue:
Fiverr
Gmail
Upwork
Messenger
Banking apps
I have two more phones a Realme C11 and a Realme 5 with Android 9 and they have fewer issues sometimes the notification gets delayed but most of the time it is instant. While on pixel 7a I only get a notification when I unlock the phone. Have tried everything such as: turning off adaptive connectivity, adaptive battery, allowing unrestricted internet use, background use, etc. Nothing works This makes the phone experience very bad. I have to buy another phone just to get notifications on time
ne...@gmail.com <ne...@gmail.com> #61
The app Doze Stopper seems to help. It sets an alarm for itself every few minutes which wakes up doze mode.
I do not understand how Google thinks it is acceptable for Gmail notifications to be delayed 30+ minutes when the phone is fully charged and sitting on a Pixel Stand.
ad...@gmail.com <ad...@gmail.com> #62
st...@gmail.com <st...@gmail.com> #63
ge...@gmail.com <ge...@gmail.com> #64
sa...@gmail.com <sa...@gmail.com> #65
st...@gmail.com <st...@gmail.com> #66
gy...@gmail.com <gy...@gmail.com> #67
kc...@gmail.com <kc...@gmail.com> #68
kc...@gmail.com <kc...@gmail.com> #69
Online: Visit the Consumer Complaint Center at
By phone: Call 1-888-CALL-FCC (1-888-225-5322).
By mail: Send a letter to:
Federal Communications Commission
Consumer and Governmental Affairs Bureau
Consumer Inquiries and Complaints Division
45 L Street NE
Washington, DC 20554
29...@gmail.com <29...@gmail.com> #70
a new bug report, as the dev. team has basically said they won't be
following this thread anymore. Based on the feedback they have a while
back, I don't think they don't consider this issue relevant anymore because
it was posted about an Android version that is out of date. To the end
user, the problem was introduced with the DOZE function in whatever that
version was and persists now, but apparently we need to make a new thread
about the current version of Android every time there is an update.
Luckily for me, the issue has gone away for all of the apps that I care
about after finding the now hidden menu to allow apps to run Unrestricted.
Android changed all of my apps to Optimized at the same time that menu was
hidden. I still get a deluge of notifications every time I wake up the
phone after it's been in sleep for for a while, from apps that I don't
really care about that much, so the issue is still there.
On Sun, Oct 13, 2024 at 2:39 AM <buganizer-system@google.com> wrote:
vi...@google.com <vi...@google.com>
sa...@gmail.com <sa...@gmail.com> #71
zi...@gmail.com <zi...@gmail.com> #72
ak...@google.com <ak...@google.com> #73
ad...@gmail.com <ad...@gmail.com> #74
Why have people raise a new issue when this could serve the purpose perfectly well?
Why not merge the multitude of issues raised around this bug and actually investigate it properly?
There are people being threatened with termination of their employment because of delayed Android notifications and all you can offer is "intended behaviour".
The problem persists with 15. My Pixel is now a cross-platform test device while I carry a proper phone that lets me know when I have emails/messages, or when someone's ringing my doorbell.
ar...@gmail.com <ar...@gmail.com> #75
So delayed notifications, messages, calls, is intended for a smart phone?
I've bought ever pixel since the first one, currently using a Pixel 8 pro.
I just have to express I'm disappointed in google. I have advocated for pixels and gotten multiple people to buy and use pixel phones and I feel responsible for them having to experience this.
Truly disappointing. I would never suggest a phone that receives delayed notifications, let alone miss phone calls.
I hope that there is a class action lawsuit that holds google accountable for this.
Absolutely unacceptable, I feel betrayed as a fan and advocate.
mg...@gmail.com <mg...@gmail.com> #76
For years, after every reboot I forced to use terminal to disable your ****** deviceidle mode, by issuing command:
./adb shell dumpsys deviceidle disable
And after years, you just tell that THE PHONE THAT DID NOT RECEIVE MEET CALLS (and does not deliver any other notifications in time) is Intended behavior.
I can't believe. F*** you GOOGLE.
gy...@gmail.com <gy...@gmail.com> #77
It's unbelievable that Google refuses to acknowledge such a huge design issue.
kc...@gmail.com <kc...@gmail.com> #78
FCC REPORTING INSTRUCTIONS:
You can file an informal complaint with the Federal Communications Commission (FCC) online, by phone, or by mail:
Online: Visit the Consumer Complaint Center at
By phone: Call 1-888-CALL-FCC (1-888-225-5322).
By mail: Send a letter to:
Federal Communications Commission
Consumer and Governmental Affairs Bureau
Consumer Inquiries and Complaints Division
45 L Street NE
Washington, DC 20554
29...@gmail.com <29...@gmail.com> #79
important like make a payment, confirm 2FA, unlock something, etc., I get
bombarded with irrelevant notifications that block my interaction with what
I'm trying to do and I have to quickly swipe them away one by one.
Obviously I can't read each one as I do that, and I end up missing some of
those delayed notifications because I've now swiped them away. So even if
your critical notifications are somehow coming through, having the other
ones delayed is a useability disaster.
On Fri, Nov 1, 2024, 19:53 <buganizer-system@google.com> wrote:
tt...@gmail.com <tt...@gmail.com> #80
mi...@gmail.com <mi...@gmail.com> #81
bs...@gmail.com <bs...@gmail.com> #82
A little history of my discovering of notifications delays. I was always sort of a fan of Nokia phones and the last one was 5.4, where I noticed the described problem for the first time. In particular, delays were seen after a long idle, i.e. the phone wasn't used for 5-6 hours, just lying at the table. Though it is not normal, as no Don't disturb mode was on, I thought it might be reasonable. Well, like if you are not using your phone actively let it slow down to reduce a battery drain. But later all became worse, notifications stopped just after an hour of the phone inactivity and flooded right after the screen awakening. I assumed that it was the phone itself, that it has slow memory, that it generally degraded by time (2+ years), that the HMD manufacturer dropped the software quality, etc. By the way, it was Android12 then. There were no such problem in previous versions or previous HMD phones.
Considering that the Nokia phone brand was discontinued and further HMD plans were generally vague, I decided to switch somewhere. For a number of reasons, the Pixel 8a was chosen. One of the reasons was that it's a "reference" phone with decent hardware and the direct Google vision of UX, which means expectations of smooth work in every aspect. And you know, that's true for most ...except the notifications! With the Android14 on my new phone this bug was still there, i.e., just give it a little idle time and it will stay silent. Thank God SMS/Calls are not affected, but the rest of the software, starting from any kind of messengers to different online banking, postal services, market apps, etc. is like going offline with the screen off. Kind of a workaround was to unlock the phone more often and it was really annoying. And then the Android15 arrived and now it's a total nightmare! Even if you unlock your phone, you can't be sure that you have no notifications, because some of them will appear while others you may not see till you open the app.
The worst is that there is nothing you can do. I've tried reboots, cash/data cleaning, apps reinstalling, turning off all battery restrictions and "clever" adaptations... So, it's definitely an intended. Intended core system behavior. Behind the battery life extention and all that AI crap Google has forgotten the main purpose of a personal electronic communicator - to send and receive messages immediately, and to be able to adjust your device behavior to your own needs. Now, you have neither. You have no a reliable channel to receive notifications and stay informed and be ready to react timely, but should be happy with having the AI assistant, AI wallpapers, AI photo effects, AI battery.
m4...@gmail.com <m4...@gmail.com> #83
sl...@gmail.com <sl...@gmail.com> #84
What are they smoking in engineering that "Thing that's supposed to get your attention" is permitted to be delayed for hours in the name of battery life? I'd like to go down there and program their refrigerator to turn off if the door hasn't been opened in a few minutes, in the name of "power saving". Or maybe turn off the lights every minute if someone isn't flailing their arms around. Or escrow their paycheques until they walk to the bank.
Jesus H Christ what is going on such that I can't rely on a state-of-the-art communication device to notify me of communication AS IT OCCURS.
Do I have to go back to a pager to get real-time communication?
What do we have to do to get Google to reopen this case and take it seriously? Just give me a menu option to switch this "intended behaviour" off. How hard can that be?
ad...@google.com <ad...@google.com> #85
Each case might have a different root cause. We request you to please create a new issue if this is still happening on the latest build along with the bug report and reference this bug for context.
12...@gmail.com <12...@gmail.com> #86
Root cause is something to do with the "adaptive" battery/data settings since Android 12, if all the threads I've read are painting an accurate picture. I've made all recommended changes, at the expense of my battery life, but the problems persist.
I was holding out for a 9a. I wouldn't have bought another Pixel if I'd researched & found out this bug is so prevalent. It's getting returned ASAP. I may let my partner finally talk me into finally joining Apple.
I'm willing to support devs if you reach out (info, logs, how to reproduce problem), but seeing how old this issue is is very frustrating.
ap...@gmail.com <ap...@gmail.com> #87
Quite disappointed in the pixel experience so far... should have stayed with cheap xiaomi phones.
am...@google.com <am...@google.com> #88
ry...@gmail.com <ry...@gmail.com> #89
I've turned off adaptive battery and adaptive connectivity and set my important apps to run in the background, but it's made no difference whatsoever.
I'm close to resorting to custom ROMs.
bs...@gmail.com <bs...@gmail.com> #90
./adb shell dumpsys deviceidle disable
(this method works only till reboot, so you need to repeat it after system updates and check whether your phone didn't reboot automatically)
ry...@gmail.com <ry...@gmail.com> #91
Really hope this gets fixed so that I don't have to resort to janky workarounds, though.
Description
- Build Number: google/oriole_beta/oriole:14/AP21.240119.009/11395453:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this?
User Interface
When did this happen?
Mar 6, 2024 4:46 PM GMT+00:00
What steps would let us observe this issue?
1. Carry out a banking transaction
2. Notification takes 10-30 minutes for to popup
What did you expect to happen?
Notification to push to phone straight away
What actually happened?
Delay in push notifications
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
Moderate
Debugging information
Google Play services
com.google.android.gms
Version 240713038 (24.07.13 (190400-607434947))
System App (Updated)
Android System WebView
com.google.android.webview
Version 626106433 (122.0.6261.64)
System App (Updated)
Network operator: EE
SIM operator: EE
Filed by Android Beta Feedback. Version (Updated): 2.40-betterbug.external_20240103_RC06 (DOGFOOD)
To learn more about our feedback process, please visit