Hey! I can help you narrow down what’s causing ghost touches on your Motorola (also called phantom touches — the screen registers taps when you aren’t touching it). We’ll keep this safe and low-impact: no factory reset, no “download this random app,” and no risky steps.

On Moto phones, “screen acting by itself” usually falls into one of these buckets:

1) Surface / pressure / protector issues — a screen protector with lifted edges, bubbles, dust at the bezel, a tight case pressing the glass, or oily residue can trigger random taps and weird swipes.
2) Moisture or static — damp hands, condensation, or a slightly wet screen can cause “scrolling on its own,” especially near the edges.
3) Charging interference — a third-party charger, cable, or loose outlet can introduce noise so the digitizer “sees” touches (often happens only while charging).
4) App / overlay conflicts — chat heads, screen dimmers, automation tools, accessibility overlays, or a buggy app can create touches/gestures that look like ghost input.
5) Hardware digitizer problems — after a drop, screen crack, pressure damage, or internal connector issues, you can get persistent phantom touches (often worse in a specific area).

Tell me a few details — answer in any order:
• Your Motorola model (Moto G / Edge / Stylus, etc.) and Android version if you know it
• What exactly happens: random taps, phantom scrolling, keyboard typing by itself, back button triggering, apps opening, etc.
• When it started (after an update, new screen protector/case, a drop, or getting wet?)
• Does it happen only while charging or even on battery?

That timeline is helpful: new protector + “worse while charging” is a very common pattern for Motorola ghost touch. It doesn’t prove the protector or charger is the cause, but it makes them the best first suspects because we can test them without changing anything permanent.

Safe Step 1 — Quick “surface” check (no settings changes)
1) Wipe the screen with a clean microfiber cloth (dry first). Pay attention to the edges where a protector can trap dust.
2) If your case is tight, remove the case for a few minutes and see if the phantom touches calm down.
3) Look closely at the screen protector: any lifted corner, tiny bubble line, or speck near the edge? Even a small edge lift can cause “taps” along that side.

Safe Step 2 — Charging pattern test (very telling)
When it starts “clicking by itself,” unplug the charger and test on battery for 1–2 minutes. Then plug back in and see if it returns. If it mostly happens while charging, we treat this as potential charger/cable interference or grounding noise rather than “the phone is dying.”

Quick question: are the ghost touches stronger near a specific part of the screen (top edge, bottom navigation area, one corner), or is it random everywhere?

Bottom-area phantom input + a bubble right there + “better unplugged” is exactly the kind of combo that can mimic a digitizer failure even when the hardware is fine.

I’m not going to tell you “rip the protector off” as a blanket move, but here’s a safe way to narrow it down without committing to anything drastic:

Safe Step 3 — Is it the protector/case, or the touch sensor?
• Keep the case off for the test.
• Use the phone on battery only for a few minutes (no charger).
• Try a simple input test that usually triggers the issue: open Notes and slowly type, then slowly scroll a web page.

If ghost touches are mostly gone on battery with the case off, that pushes us toward external factors (pressure + charging noise) instead of a deeper screen fault.

Another important “real life” question: do you ever see it happening when the phone is just sitting on a table untouched (screen on), or only when you’re holding it?

Seeing it on the table is a good detail. That means it’s not just “how you’re holding it,” and it helps us take this seriously without jumping straight to a reset.

Since charging clearly worsens it, I’d treat the cheap cable/charger as a likely amplifier. Even if it’s not the root cause, it can make a mild issue look severe.

Safe Step 4 — Clean isolation test (no “fix,” just diagnosis)
For one short test session:
1) Use the phone not charging.
2) Remove any accessories connected to the port (USB devices, headphones via adapter).
3) If the screen protector has a bubble near the bottom edge, gently press around the bubble to see if the “ghost area” becomes more active (don’t press hard — we’re observing sensitivity).

If pressure near the bubble correlates with ghost taps near the bottom navigation/keyboard, that points strongly to the protector/adhesive or trapped dust at the edge. If it behaves the same no matter what you do on the surface, then we look more at software/app conflicts or the digitizer itself.

One more angle (because it’s surprisingly common): do you use anything like a screen dimmer app, a “one hand mode” tool, floating buttons, chat heads, or any accessibility feature that draws over the screen?

Totally fair — most of the time those apps are harmless. But anything that uses overlays, accessibility permissions, or aggressive gesture shortcuts can make the phone feel like it’s “tapping on its own.” That’s why a good diagnostic step is to check whether the ghost touches persist when third-party apps are temporarily out of the picture.

Safe Step 5 — Safe Mode test (Motorola-friendly diagnostic)
Safe Mode boots Android with only the original system apps. It’s not a fix, it’s a yes/no test:
• If phantom touches stop in Safe Mode, the odds shift toward an app/overlay conflict (launcher, filter, floating tools).
• If ghost touches continue in Safe Mode, we take hardware/surface/charging interference more seriously.

You don’t have to do it right now, but if you do: once you’re in Safe Mode, just open a simple screen (Settings or Notes) and observe whether the screen still randomly taps or triggers back/home.

Before that, quick safety question: is your screen cracked, or has it had any water exposure recently (even “light rain” or being in a steamy bathroom)?

Not automatically — Safe Mode is one data point, not a verdict.

If Safe Mode still shows ghost touches, we’d still consider a few “non-repair” explanations first, especially since yours is worse when charging and you have a protector bubble near the problem area:
• charging noise/grounding (cheap cable/adapter, bad outlet) amplifying touch jitter
• protector/adhesive edge issue making the digitizer overly sensitive in a zone
• moisture residue around the bezel (sometimes it takes longer to fully dry out than people expect)

Safe Step 6 — What you can observe to separate software vs hardware
Watch for these patterns (no settings changes required):
• Only while charging? That points to charger/cable/outlet influence.
• Only in one region (like the bottom nav/keyboard area)? That points to local pressure/protector/digitizer zone.
• Random everywhere even on battery, in Safe Mode, on a clean/dry screen? That raises suspicion of the touch sensor itself.

If you try Safe Mode: did it still “tap” by itself while sitting on a table for a couple minutes?

That’s actually a very “diagnostic” result: reduced in Safe Mode (apps might amplify it), but much worse while charging and when warm/bright (environmental + electrical factors can make touch instability more noticeable).

At this point, the safest path is to confirm the charging variable cleanly — because it’s the least invasive and often the biggest lever in ghost touch cases.

Safe Step 7 — Clean charging test
For one evening, try this pattern (no purchases required if you can borrow):
• Use a different known-good charger/cable (preferably original/OEM or a reputable brand) and a different wall outlet if possible.
• Observe whether the Motorola screen still does phantom taps while charging.

If ghost touches largely disappear with a different charger/cable, we’ve confirmed the main trigger without changing your phone at all. If it still happens the same way on multiple good chargers, then the charging “amplifier” is real but not the only factor.

One more quick check: is the protector a tempered glass one, and does it cover the entire front (edge-to-edge), or is it slightly smaller with a hard lip?

If a tempered glass protector is misaligned, lifting, or has edge tension, it can absolutely create “touchscreen going crazy” behavior — especially near navigation bars and keyboards where tiny false inputs are very noticeable.

I don’t want to push you into removing it blindly. The goal here is to use logic and confirm the cause with minimal disruption:

Safe Step 8 — How to confirm a protector factor without committing
• Check the exact spot where the bubble is: if ghost touches cluster near that edge/zone, that’s a strong correlation.
• If you can temporarily use the phone without charging + with the case off, and it behaves much better, that supports “surface/pressure/noise” rather than a failing digitizer.

If after the charger test you still suspect the protector, the next step is a decision point: keep it and live with occasional false touches, or replace/remove it. But you don’t need to decide that until the charger test tells us whether charging is the main trigger.

Last question (because it changes the risk level): is the phone still under warranty or recently purchased?

For “today,” the safest way to reduce chaos is to avoid the known amplifier while you gather evidence — without making permanent changes.

Low-risk “today” plan
• Use the phone on battery when possible (since charging makes it worse).
• Keep the screen clean/dry; if you were in rain recently, let it fully air-dry and avoid steamy rooms for a bit.
• Remove the case temporarily if it presses near the edges.
• If the ghost touches spike, briefly lock the screen and unlock (not a fix, but it can calm a runaway session).

Then do one clean diagnostic: try a different good charger/cable. If that dramatically reduces phantom taps, you’ve found a safe, practical workaround while you decide whether to replace the protector or pursue warranty support.

If you tell me what happens with the borrowed charger (better/same/worse), I can help you interpret it without jumping to a reset or assuming hardware failure.