FARMFix a running PhoneFarm phone that will not connect
Diagnose blank screens, Connecting, autoplay blocks, sleeping displays and dropped sessions without confusing live-control failure with phone or app failure.
A phone can be marked Running while its live-control screen is unavailable. Running describes the phone's power or execution state. Live control also needs a working connection between your browser and that phone, a video stream, and a responsive display.
The first useful question is not “should I create another phone?” It is “which part of the existing connection is failing?” The sequence below narrows that down while preserving the phone and account session you already configured.
Start by identifying what you can see
Open the affected phone's detail page and read the message in the live-control panel. Note whether you see a phone image, a loading state, Play, Wake screen, Connect, Reconnect, or an error.
| Symptom | Likely area to investigate first |
|---|---|
| Phone setup is incomplete | Creation or proxy setup, before live control |
| Click Play / Play button | Browser playback permission |
| Black display with Wake screen | Phone display may be asleep |
| Connecting or Reconnecting, no image | Browser-to-phone live session |
| A still image that does not change | Frozen stream, unresponsive phone or an input problem |
| Home works, but TikTok does not load | App or phone internet connection |
| Multiple phones fail in the same browser | A shared browser, local network or service issue |
These are starting points, not guaranteed diagnoses. Use the next check to confirm which layer is affected.
1. Confirm the phone has finished setup
If the phone was just purchased, return to its setup runway. Check whether creation is still processing and whether the proxy step reached Proxy verified. A partially configured phone may exist in the dashboard before it is ready for normal use.
Continue the original setup instead of creating a new purchase. If the page says provisioning is still in progress, record that state and revisit the same purchase. The first-phone guide explains the difference between paid capacity, a created phone and a ready connection.
If setup completed previously and the phone is now marked running, proceed to the live panel. Do not assume that a network or screen failure has erased the device or its account session.
2. Resolve browser playback and display sleep
If Play appears, select it. Browsers can block a media stream until you explicitly allow playback. A playback block can leave the connection established without displaying video.
If Wake screen appears, use it. The phone display can sleep while the underlying device remains running. Then select Home and look for a screen change.
A successful Home response is useful evidence: the browser received a current image and the phone accepted an input. If you can navigate Android normally, live control is working even if a particular app remains stuck.
3. Reconnect the live session once
Use Connect or Reconnect as offered. Allow the connection state to advance and note the result. Avoid pressing reconnect repeatedly before the previous attempt has finished; that makes it harder to distinguish a persistent failure from a session still establishing itself.
Keep one live-control tab for the phone while diagnosing it. If several tabs are open, close the duplicate views and continue from the intended phone's detail page. This simplifies the test and prevents accidental inputs from another view.
If reconnect fails, reload that detail page and try again once. Record whether the symptom changes—for example, from no image to a visible but frozen screen. A changed symptom helps support identify how far the connection progressed.
4. Separate a frozen app from a frozen phone
Try Home or Recent apps rather than repeatedly tapping an unresponsive button inside TikTok. If Android responds but TikTok does not, the control channel is usable and the problem is more likely in the app or its connection.
If Android navigation does not respond, check whether the image itself is updating. A clock, animation or screen transition can help distinguish a live view from a stale frame. Do not type passwords or submit posts while you cannot tell what state the phone is actually in.
If the screen responds but websites and several apps fail to load, use network troubleshooting. The phone's app internet path is a separate question from whether your browser can display its screen.
5. Determine whether the failure is isolated
If you already have another configured phone, open it for a simple screen check without starting any app actions. One affected phone points toward a phone-specific session or setup problem. Several affected phones point toward a shared dependency, although you still need evidence before attributing the cause.
Check whether the PhoneFarm dashboard itself loads and whether your computer has a stable internet connection. A restrictive office network, browser extension or local connection interruption can affect live streaming differently from ordinary page loading.
If possible, compare the same phone from another supported browser or a different trusted internet connection. Make one controlled comparison at a time. The purpose is to determine whether the failure follows the phone or your local environment, not to reconfigure every device in the fleet.
Before considering a restart
Check whether the phone has a running task or an unresolved publishing attempt. Restarting during a post can interrupt the workflow and make the publication outcome harder to determine. Inspect the current task and verify publication first when submission may have occurred.
Use only the recovery controls available for that phone and follow any PhoneFarm guidance attached to the error. Repeated restarts, resets or replacement purchases are not a substitute for identifying the failed layer. In particular, do not erase the phone or clear app data as an initial response to a browser stream problem.
What to include if the issue persists
Send the phone's visible name or reference, the failure time with timezone, the live-control message and a screenshot of the panel. Include the results of these specific checks:
- Whether Play or Wake screen was offered and what happened after using it.
- Whether Home or Recent apps changed the screen.
- Whether one reconnect or a page reload changed the symptom.
- Whether another phone or another trusted local connection worked.
- Whether the affected phone had active work or an uncertain publish result.
Do not include account passwords, proxy credentials or a raw session token. The support guide provides a copyable report format.
Confirm recovery at the level that originally failed
When the screen returns, use Home or Back and confirm the image responds. If your original problem was app internet access, also load a page inside the phone. If it was a publishing interruption, inspect the actual account result before retrying the task.
This last check matters: a restored stream proves you can operate the phone again, but it does not retroactively establish what an interrupted app action did.