Direct answer
For the Google Pixel Fold, app permission, channel/category, Focus modes, background restriction, account sync and network should be separated. First, send a controlled test while the app is open, then locked.
What this covers
- Google Pixel Fold (G9FPL)
- Foldable device; distinguish outer display, inner display and hinge behavior.
- The specific fault this record addresses: notifications are delayed or missing
What it does not cover
- ×The same symptom on a different Google product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
A focus mode or scheduled summary is holding them
What separates it Notifications appear later, in a batch, or not until the phone is unlocked. Focus modes, bedtime schedules and scheduled summaries all do this deliberately and quietly.
How to confirm Check for an active focus mode and any scheduled summary. This is the most common cause and it is invisible from the notification itself.
- 2
Battery optimisation is restricting the app
What separates it One app is late while others are prompt, on Android in particular. Aggressive per-app power management stops background work, and notification delivery depends on it.
How to confirm Set that app to unrestricted battery use. This is the single highest-hit-rate action on Android for this symptom.
- 3
Notification permission was never granted or was revoked
What separates it Nothing at all from one app, ever. Both platforms now require explicit permission and it is easy to dismiss the prompt at install time.
How to confirm Check the app's notification permission specifically rather than its in-app settings.
- 4
The app's own settings are off
What separates it The system permission is granted and still nothing arrives. Apps carry their own notification preferences, often per category and per account.
How to confirm Check inside the app as well as in system settings. Both have to agree, and each is capable of silencing the other.
- 5
The event never happened
What separates it Nothing appears in the app's own history either. A notification cannot be missing for something that was never generated.
How to confirm Open the app and look for the item. Present in-app but not notified is a delivery problem; absent in-app is not a notification problem at all.
- 6
Notifications are silent rather than missing
What separates it They are in the shade but made no sound and showed no banner. Delivery style is configurable per app — silent delivery is a real setting.
How to confirm Check the app's alert style for banner, sound and lock-screen settings separately.
- 7
The phone is on a network that blocks push
What separates it Notifications stop on one specific Wi-Fi network and resume on cellular. Restrictive workplace and guest networks block the ports push services use.
How to confirm Compare the same app on Wi-Fi and on cellular data in the same place.
- 8
Signed out of the account, or signed in on another device
What separates it Notifications stopped after signing in elsewhere. Some services deliver to the most recent device only.
How to confirm Check the account status inside the app rather than assuming the session persisted.
- 9
Do Not Disturb during a schedule nobody set deliberately
What separates it Notifications are silent at consistent times of day. Bedtime schedules and driving focus both activate automatically.
How to confirm Look at the focus schedule rather than the notification settings.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- Whether the item exists in the app's own history — this splits a delivery problem from an event that never happened, and costs one look.
- Whether it affects one app or all of them.
- Whether notifications are absent, late, or present but silent. Those are three different failures.
- Whether the problem follows a time of day, which points at a schedule rather than a setting.
- Whether it happens on Wi-Fi, on cellular, or both.
- The app's system notification permission, and separately its in-app notification settings.
- The app's battery optimisation state.
Check whether the item exists in the app itself
ReversiblePresent in the app but never notified is a delivery problem. Absent from the app entirely is not a notification problem at all, and no notification setting will produce an alert for something that was never generated. One look, and it halves the work.
Check for an active focus mode or scheduled summary
ReversibleFocus modes, bedtime schedules and scheduled summaries hold notifications deliberately and give no indication in the notification itself. This is the most common cause, and a problem that follows a time of day is almost always this.
Separate absent from late from silent
ReversibleAbsent points at permissions or the app. Late points at background restriction or the network. Silent points at the delivery style setting. Three different failures that get reported with the same words.
Set the app to unrestricted battery use
ReversibleAggressive per-app power management stops the background work that notification delivery depends on, and it is applied automatically to apps the phone thinks you use rarely. On Android this is the single highest-hit-rate action for late notifications.
Check the system permission and the in-app settings separately
ReversibleBoth have to agree and each can silence the other independently. An app with system permission granted and its own category switched off delivers nothing, and looking at only one of the two explains nothing.
Compare Wi-Fi against cellular in the same place
ReversibleRestrictive workplace and guest networks block the ports push services use, which stops notifications on that network only. Testing both takes a minute and identifies a cause no phone setting would reveal.
Confirm you are still signed in
ReversibleSome services deliver to the most recent device only, so signing in elsewhere silently stops delivery here. Check the account inside the app rather than assuming the session persisted.
Test with the phone locked
ReversibleNotification behaviour differs between an unlocked phone in your hand and a locked one in a pocket, and only the second reflects real use. A fix confirmed with the phone unlocked and awake has tested the easiest case.
Reinstall only after the settings are excluded
Signs you outA reinstall clears the app's own preferences and re-prompts for permission, which is why it sometimes works — but it teaches you nothing about which layer failed, and the same cause will take out the next app.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- G9FPL. Foldable device; distinguish outer display, inner display and hinge behavior.
- Type — book-style FOLDABLE (crease normal)
- Google's first book foldable — cover + large inner folding screen, centre crease normal. Tensor G2, stock Android with Pixel AI. Older foldable nearing its update window's later years.
- Inner screen care
- Soft-topped inner OLED — no hard styluses, no pressing hard, no forcing objects into the fold. Keep grit out of the hinge; check its IP rating before water exposure.
- Tensor warmth
- Tensor G2 runs warm under load — normal.
- Symptom boundary
- This record covers Google Pixel Fold when it notifications are delayed or missing. A different symptom on the same hardware, or this symptom on a different Google product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !Notifications fail across every app after every setting has been checked, which points at the system rather than any app.
- !The service itself is failing to send — the app's own status page or support is the path, not the phone.
- !The phone is on a managed network where push is blocked by policy and only an administrator can change it.
- !Notifications are being relied on for anything safety-critical, which no consumer push service is specified for.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Google Pixel Help publishes this as "Control notifications on your Pixel phone". Google's notification-control article for Pixel. Probed 2026-08-28, after the 2026-08-23 rate limit had cleared: title-verified. What that article does not carry is the model boundary — it is written for a product line, and G9FPL is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
Is the crease and the gap when closed normal on my Pixel Fold?+
Yes — the inner screen crease is normal on any book foldable (the bend line), and the first Pixel Fold closes with the two halves nearly flat. What is not normal is a spreading line across the fold, a dead strip, or the screen lifting, which indicate damage — often grit in the hinge or a hard object on the soft inner screen. Keep debris out of the hinge, use no hard stylus inside, and check its water rating before exposure.
My notifications arrive hours late.+
On Android this is usually battery optimisation restricting the app in the background, and setting that app to unrestricted use is the highest-hit-rate fix. On either platform, check for a scheduled summary or a focus mode — both hold notifications deliberately and neither says so.
I get nothing at all from one app.+
Check the system notification permission first, then the app's own settings. Both have to agree, and each can silence the other independently — an app with permission granted and its own category switched off delivers nothing at all.
How do I tell whether the notification was even sent?+
Open the app and look for the item in its own history. Present in the app but never notified is a delivery problem worth chasing. Absent from the app entirely means nothing was generated, and no notification setting can conjure an alert for it.
Notifications are silent but they are in the shade.+
That is a delivery-style setting rather than a failure. Banner, sound and lock-screen presentation are configurable per app, and silent delivery is a real option that gets applied without much ceremony. Check the alert style for that app.
They stopped working after a system update.+
Updates commonly reset per-app notification permissions and background activity allowances. Check both for the affected apps specifically — this is one of the most predictable side effects of a major update and it looks exactly like an app fault.
It only happens at work.+
Compare the same app on Wi-Fi against cellular data in the same place. Restrictive workplace and guest networks block the ports push services use, which stops delivery on that network only — and no phone setting would ever reveal it.
Should I reinstall the app?+
Only after the settings are excluded. A reinstall clears the app's preferences and re-prompts for permission, which is why it sometimes appears to work — but you learn nothing about which layer failed, and the same cause will take out the next app you install.
Notifications are quiet at the same time every evening.+
Look at focus schedules rather than notification settings. Bedtime and driving focus modes activate automatically on a schedule, and a problem that tracks a time of day is almost always one of them.
They work when I am using the phone but not otherwise.+
That is background restriction. Delivery depends on the app being allowed to do work while you are not looking at it, and power management removes exactly that. Set the app to unrestricted and test with the phone locked and in a pocket.
Does this answer apply to every Google model?+
No. It is scoped to G9FPL. Foldable device; distinguish outer display, inner display and hinge behavior.
What should I record before troubleshooting notifications or delayed alerts?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing notifications, delayed alerts. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Preserve emergency, security and authentication alerts.
Answer for the exact device and software version shown above.