Editing Openai/693e48dd-ce3c-800a-b636-9b3efde0fdec (section)

=== Assistant: Got it. ===
Got it. “Visible all day” is an important detail — and it still fits cleanly with what we’ve narrowed this down to. It does not push this into anything exotic.

Here’s what that persistence means, in plain terms.

==== If a display artifact: ====
* ❌ does not show in screenshots or screen recordings
* 🔄 disappears briefly on rotation, then returns
* ⏱️ stays present for hours
* 📍 moves relative to content

then it is not accumulating from use in real time — it’s a stuck display-controller state that never fully clears during normal operation.

Think of it like this:

: 

Rotation temporarily flushes part of that state, but not the underlying condition, so it keeps coming back.

That’s why:
* it doesn’t worsen dramatically
* it doesn’t spread
* it doesn’t crash anything
* but it also doesn’t go away on its own

==== Modern phones keep the display controller in a low-power persistent mode: ====
* it survives app switches
* it survives lock/unlock
* it can even survive normal restarts sometimes

Only hard resets, thermal changes, or full power cycles reliably clear it.

So “all day” does not imply:
* damage spreading
* something external interacting
* escalation

It implies stability, actually — just in a faulty configuration.

==== If any of these were happening, we’d reassess: ====
* dots multiplying rapidly
* dots becoming permanent and fixed to the glass
* dots showing up in screenshots
* dots appearing in screen recordings
* dots appearing after the screen is completely off

You’ve reported none of those.

==== ### ====

If you haven’t already today:
# Shut the phone completely off
# Leave it off for 5–10 minutes
# Turn it back on

This drains residual display-controller state more fully than a quick reboot.

: 

===== At that point, this is no longer a “wait and see” thing. It’s a documented hardware/display-controller issue. =====

If you talk to Apple (or a repair tech), use this exact phrasing:

: 

That sentence hits the right diagnostic flags immediately.

==== I want to be very clear here: ====
Nothing about ‘all day’ makes this more concerning. In fact, it makes it less ambiguous.

Random, external, or software-driven issues don’t behave this consistently.

What you’re seeing is:
* boring
* internal
* well-bounded
* annoying
* real

And you’ve done everything right to understand it.

If you want, tell me:
* did you already do a full power-off today?
* does it look identical now as it did this morning?

We’re past guessing at this point — it’s just deciding how much energy you want to spend fixing it.