Hey! When someone says their Google Pixel works only after restart, I try to pin down what “works” means — because there are two common situations that feel the same but have different causes:

1) The phone stays on, but gets unusable (apps won’t open, keyboard lags, notifications arrive late, Wi-Fi or Bluetooth acts odd) and a restart temporarily clears it.
2) The phone actually restarts on its own (random reboot / crash & restart).

We’ll keep this in safe diagnostics mode (no wipe-style steps). First, which one is closer to your experience — and what’s the “first thing” that fails when it goes bad: calls/texts, Wi-Fi, apps, camera, or general slowness?

Perfect clarification — so we’re not in a bootloop or “random restart” case. This is the classic “Pixel becomes unusable until restart” pattern, where a reboot acts like a temporary reset button.

The most helpful way to approach this (and avoid doorway-style generic advice) is to classify which “bucket” is building up over time:

• Storage / background update pressure (phone feels heavier over hours/days).
• A third-party app or launcher conflict (home screen, app switching, notifications get weird).
• Work profile / device management (weekday-only slowdowns, policy sync, notifications delayed).
• Heat / charging pattern (worse after overnight charging, warm while plugged in).

Quick questions — and I’m mixing the order on purpose to spot patterns fast:
1) When did it start? After an Android update, after installing something (launcher/VPN/security), or gradually?
2) Does it happen on a schedule? Like mostly mornings, mostly weekdays, or after heavy use?
3) Any “System UI isn’t responding” or app crash popups?

That’s a strong cluster: new launcher + work profile + “worse after overnight charging.” None of those automatically means “the launcher is bad,” but together they fit a pattern where background tasks pile up (sync, indexing, app updates, policy checks) and the phone feels “fixed” only after reboot.

Related search phrases people use for this exact vibe: Pixel slow until restart, apps not responding until reboot, Pixel notifications delayed, System UI not responding, Pixel lag after update, work profile causing issues.

Let’s map what “works only after restart” looks like for you — because it tells us whether this is system-wide pressure or one subsystem:
• When it’s bad, is typing laggy everywhere (keyboard delay in every app) or only in a couple apps?
• Do calls/texts still behave normally or do you get missed notifications and late message delivery too?
• Does Wi-Fi/Bluetooth act weird (drops, won’t connect) or is it mainly app slowness?

If any charging-related symptoms show up (like charging unusually slowly), that can be a separate clue too: charging very slowly.

“Heavy everywhere” + notifications arriving in a burst after unlock is very consistent with system-wide backlog (the phone is busy in the background, then catches up). That’s different from a single app bug.

Two “safe facts” usually separate this into the right lane:

Fact A: Storage headroom. Low free storage can make updates and background tasks fight for space and time, which shows up as slow app launches, delayed notifications, and occasional System UI timeouts. (Not saying “delete everything,” just: how much free space do you have?)

Fact B: Third-party involvement. If a launcher or another installed app is contributing, the phone often behaves differently when third-party apps are temporarily disabled (that’s what safe mode observation is for). It’s not a “fix,” it’s a test.

Before any tests: roughly how much free storage is left — like under 5 GB, around 10 GB, or plenty? And does the issue feel worse on weekdays when the work profile is active?

Totally fair to be cautious. Safe mode is often scary-sounding, but conceptually it’s just a temporary diagnostic state where third-party apps don’t run. It doesn’t wipe photos or uninstall anything — and you exit it by restarting normally. You don’t have to do it today; I’m mentioning it because it’s high-signal and low-risk when you’re stuck in the “only works after restart” cycle.

Your two clues are very strong, though:
• 4–6 GB free is tight enough that background installs/updates can feel rough, especially overnight.
• Weekday bias points to work profile sync/policies being part of the load (even if it’s not the only factor).

If we keep this purely diagnostic, here are three safe observations you can do without changing anything big:
1) Note what happens right after reboot (how long it stays smooth).
2) Notice if mornings after charging are worse (suggests overnight background work).
3) Check if the Play Store shows lots of updates pending on the days it gets sluggish (background updating can mimic “phone broken”).

Also, if your battery is draining overnight around the same time this started, that’s worth noting too: battery drains overnight. Is battery drain part of the story, or mostly performance?

That “smooth for ~a day, then degrades” timing is classic buildup. It’s also why this issue feels so frustrating: reboot doesn’t solve the cause, it just clears the backlog temporarily.

The consent screen note isn’t a smoking gun, but it fits the “something changed recently” theme (people often mention odd post-update prompts; similar topic: consent screen confusing).

Here’s how I’d decide what to do next, without jumping to big changes:

• If the phone is system-wide slow + storage is tight, treat storage headroom as a primary suspect (because it amplifies everything else).
• If weekday/work profile strongly correlates, treat managed profile activity as a major variable (not “bad,” just load).
• If a new launcher was installed right before this started, treat it as a plausible contributor (it sits in the path of home screen, gestures, and sometimes notification behavior).

One more safety question (risk/urgency): have you had any moments where the phone won’t unlock, gets stuck on “Phone is starting”, or shows repeated “app isn’t responding” popups? Or is it mainly slow/lag + delayed notifications until restart?

That’s exactly the right mindset: you can get a clear direction here without going anywhere near a factory reset.

If I summarize the safest “what to do next” logic for a Pixel that works only after restart, it’s this:

1) Confirm it’s not true random restarting (you’re not seeing that, good).
2) Identify the dominant load (tight storage + weekday work profile + overnight charging pattern).
3) Use one high-signal, low-risk test if needed (brief safe mode observation to separate “app/launcher stack” from “system pressure”).

You already have enough clues to narrow it down to two main lanes: storage/background updates and managed profile + launcher/app interactions. The next safe step is simply collecting a bit more context (not changing everything):
• how much storage is free tomorrow morning before you open apps
• whether the Play Store shows pending updates on slow days
• whether slowdowns happen even if you don’t use the phone while charging overnight

If you want to keep internal notes: list the first 2–3 symptoms you notice (typing lag, notifications burst, apps hang), because that pattern helps separate “pressure” from “one rogue app.” And if camera ever becomes part of it (black screen / won’t open), that’s a different branch: camera black screen.