Motorola phone screen sharing not working — what to do next (safe checks)

Hey! Let’s figure out why your Motorola phone screen sharing isn’t working using only safe checks (no risky resets, no random “toggle everything”). With Moto phones, “screen sharing” can mean a few different things, and the fix path depends on which one you’re actually using:

1) Google Cast / Chromecast mirroring: you tap Cast and mirror your screen to a TV with Chromecast built-in or a Chromecast dongle.
2) Casting from an app: YouTube/Photos/etc show a cast icon, but the TV/device doesn’t show up or won’t connect.
3) Ready For / Smart Connect: Motorola’s PC/TV experience (wired or wireless), sometimes called screen sharing/desktop mode.
4) “Screen mirroring” to a random smart TV: some TVs want Miracast-style mirroring — but many Moto models rely on Cast instead, so compatibility matters.

Tell me what you see (answer in any order):
• What Moto model (Moto G / Edge / Razr) and Android version, if you know?
• What are you trying to share to: Chromecast, Android/Google TV, Samsung/LG/Roku TV, Windows PC, or a projector?
• What exactly fails: TV/device not found, connects then disconnects, black screen, audio only, or lag/freezing?
• Did it start after an update, router change, new VPN, or switching to a guest Wi-Fi?

Perfect description — “TV not showing” vs “connecting forever” usually points to device discovery (phone can’t see the receiver) or a network path problem (they can see each other but can’t complete the handshake).

Before we touch any settings, I want to identify the receiver type because the checks differ slightly:
• Is it a TV with Chromecast built-in (Android/Google TV), or a separate Chromecast plugged into HDMI?
• Or is it a Roku / Fire TV / something else where you’re using a third-party casting option?

Safe Step 1 — Same Wi-Fi check (this catches a lot)
On the Moto: are you on your home Wi-Fi right now, or are you on mobile data? Casting/screen mirroring via Google Cast generally needs the phone to be on the same Wi-Fi network as the TV/Chromecast.

Also quick “when did it start”: did you change anything recently — router, Wi-Fi name/password, enabling a guest network, or using a VPN/ad-blocker?

Guest Wi-Fi is a big clue. Many routers isolate guest devices from the main network (sometimes called AP isolation or “guest clients can’t see LAN devices”). If your Chromecast is on the main Wi-Fi but your phone is on the guest Wi-Fi (or vice versa), they may not see each other reliably — which matches “doesn’t show up” and “connecting…” loops.

Safe Step 2 — Confirm both devices are on the exact same network name
• On your Moto: check the Wi-Fi name you’re connected to (not just “Wi-Fi on”).
• In the Google Home app (or on the TV input where Chromecast is active), check which Wi-Fi the Chromecast is connected to.

The important part is: same SSID (same network name), not “same router.” If one is on Guest, it can break casting even though internet works fine on both.

Safe Step 3 — Quick VPN sanity check
Even if you think the VPN is off, do you ever use “Always-on VPN” or a “block connections without VPN” option? Those can interfere with Cast discovery/handshake quietly.

When it fails, do you see your Chromecast at all in the Cast list, or is it completely missing?

Got it. If it appears but stalls at “connecting,” discovery is partially working — the next suspects are usually:
• Wi-Fi band mismatch (phone on 5 GHz vs Chromecast on 2.4 GHz is usually OK, but some routers handle it badly)
• router features that block local traffic (client isolation, “AP isolation,” some “security” modes)
• stale network session (Chromecast or phone network stack needs a clean restart)
• receiver/app updates (Google Home / Cast receiver firmware can get out of sync)

Safe Step 4 — Two low-impact checks (no settings changes)
1) Distance test: Stand a few feet from the router and try casting again. This isn’t superstition — weak local Wi-Fi can cause handshake failures even when browsing works.
2) Second device test: If you have another phone/tablet on the same Wi-Fi, can it see and connect to the Chromecast? This tells us if it’s a phone-specific issue or network/Chromecast-wide.

Also, do other apps fail the same way (Photos/Chrome mirroring), or is it mostly YouTube?

That’s a really useful comparison — it means the Chromecast and Wi-Fi are capable of working, but something about the Moto’s path to Cast is failing (not necessarily “hardware is broken”). On Android, casting involves a few moving parts: the app you cast from, Google Play services components, and the phone’s local network permissions/behavior.

I’m going to keep this strictly diagnostic and safe, but here are the “what changed?” angles that usually matter on Motorola/Android:
• Local network behavior: some Wi-Fi security settings or router “isolation” can affect one device more than another.
• Permissions & discovery: Android can restrict device discovery for some apps if permissions were changed (even accidentally) or if Wi-Fi scanning is limited.
• Network filters: VPNs, DNS filters, ad blockers, or “security” apps can break device discovery/handshake without breaking normal browsing.

Safe Step 5 — A quick “environment” snapshot
Answer any that you know:
• Is your Moto connected to a guest network ever (even previously), or is it always on the main SSID?
• Are you using a router feature like “device isolation,” “AP isolation,” “WLAN partition,” “privacy separator,” or “guest access only”? (Names vary.)
• When the Moto tries to cast, does it fail instantly, or does it spin for 30–60 seconds and then error out?

That timing (spins, then fails) fits a handshake/route problem more than “Chromecast missing.” And the fact you see “AP isolation” in the router UI is relevant because that exact feature can block devices from talking to each other on Wi-Fi even while they still have internet access.

I won’t tell you to flip settings blindly, but here’s a safe way to diagnose without committing changes:

Safe Step 6 — Identify whether local device-to-device traffic is being blocked
• If your router has a status page that shows connected devices, check whether your Moto and the Chromecast appear under the same Wi-Fi band/SSID group and at the same time.
• If the router offers an “isolation” setting per SSID (main vs guest), just note what it says for the network you’re using. Don’t change it yet — the goal is understanding the current configuration.

Another low-risk clue: if your Moto can cast successfully when connected to a mobile hotspot (Chromecast joined to the hotspot network), that strongly suggests your home router’s local traffic policy is the barrier — not your phone’s screen sharing feature itself.

Have you ever tried casting at a friend’s place (different Wi-Fi) with this same Motorola?

That pattern is very consistent: browsing uses the “internet path,” but casting/screen sharing relies on local discovery and local device-to-device traffic on your Wi-Fi. So it’s completely possible for web pages to be fast while casting fails repeatedly.

Safe Step 7 — Keep variables clean
If you do the hotspot test, try to keep it simple:
• Connect the Chromecast to the hotspot network.
• Connect your Motorola to the same hotspot network.
• Then try casting from one app (like YouTube) and see if it finds/ connects more reliably.

If that works, we’ve basically proven your Moto’s Cast feature is OK and the issue is the home Wi-Fi environment/router policy. If it fails even on the hotspot, then we focus back on the phone-side Cast components (still without jumping to “wipe everything”).

Quick question: when you open the Cast menu on the Moto, do you ever see other devices (like smart speakers), or only the Chromecast sometimes?

Yes, it can matter — not always, but it’s a good diagnostic angle. Some ad blockers work by running a local VPN-style filter (even if you don’t call it a VPN). That can interfere with local discovery or the Cast connection handshake, especially if it’s trying to “protect” connections on your network.

I’m not going to push a “turn it off and you’re done” claim, but as a controlled test it’s useful: one variable at a time. The cleanest diagnostic order is usually:
1) Confirm both devices are on the same non-guest Wi-Fi and close to the router.
2) Confirm the receiver (Chromecast/TV) is reachable and updated (Google Home / Cast receiver side).
3) Temporarily remove network filters (VPN/ad blocker) only for testing to see if discovery/connect changes.

Also: do you have multiple Wi-Fi extenders/mesh nodes, or just one router? Sometimes phones and Chromecasts end up on different nodes/bands and it makes discovery flaky.

Safest next step is to prove the pattern with two controlled comparisons — no big changes, no door-closing moves:

1) Network comparison (best evidence): try casting when both devices are on the same hotspot network. If it works there but not on home Wi-Fi, you’ve isolated the cause to the router/Wi-Fi environment (guest isolation, AP isolation, router security mode, or band/node behavior).

2) Filter comparison (one variable): keep everything else the same, and briefly test casting with any VPN/ad-blocker filtering paused. If discovery/connect changes immediately, the issue may be the filter app interfering with local connections.

If both tests point to the home router environment, then the “next step” isn’t “replace your phone” — it’s confirming which router feature is blocking local device-to-device traffic and whether the Chromecast/receiver is fully updated. If the tests point back to the phone, we focus on phone-side casting components and permissions — still step-by-step, without jumping to disruptive resets.