If Larix Broadcaster stops publishing after your Android phone loses Wi-Fi, reconnect the phone first, then open Settings > Connections > Advanced settings and enable “Don’t check network presence.” Return to the preview and manually resume or start the stream; this setting permits a connection attempt but does not guarantee recovery.
If Larix still will not publish, check that the phone has usable internet and that the selected saved connection still has the right destination details. The app cannot make an unavailable network or unreachable receiving server work.
When Wi-Fi returns, check the phone first
A Wi-Fi icon is not proof that the phone can reach the internet or the streaming destination. The phone may have rejoined the router while the router itself is offline, or it may be connected to a network that requires a sign-in page. Before changing Larix settings, open a familiar webpage or app on the phone and confirm that it loads over the connection you intend to use.
If the phone has mobile data available, be clear about which connection it is using. Switching between Wi-Fi and mobile data can change the network path while the stream is interrupted. For this recovery, establish one working connection, then try Larix again. If you are relying on Wi-Fi, look for the network name in Android’s Wi-Fi settings and confirm that it shows as connected, then test internet access separately.
Also check whether Android is showing a prompt that needs your attention, such as a captive portal or a request to sign into a public or shared network. Until that step is complete, the phone can appear connected without having unrestricted access. Do not assume Larix is at fault until the phone itself can reach an online destination.
This first check separates two different failures: the handset has no useful network, or Larix has a problem making its publish connection. A setting inside Larix can change when the app attempts to connect; it cannot repair a lost Wi-Fi link. For a broader view of how the encoder and destination fit together, see the practical YouTube live stream settings for 1080p at 30 fps, while keeping in mind that a reconnect issue is not necessarily a video-quality problem.
Find Larix’s Advanced settings
Once the phone has working internet, open Larix Broadcaster. The relevant control is in the app’s connection settings, not in Android’s Wi-Fi menu. Navigate to Settings > Connections > Advanced settings. Menu wording or layout can vary with an app version, but look for the connections area and its advanced options rather than searching the phone’s general network settings.
Before leaving settings, note which connection is selected. Larix may have more than one saved destination, and a correct setting for one connection will not fix a different selected entry. If you are unsure which one is intended, avoid editing or deleting saved details yet. First enable the network-presence option, then return to the preview and attempt to publish using the expected connection.
Softvelum’s Larix FAQ documents the network-presence option and describes the default behaviour: Larix checks for network presence and does not retry when the network occasionally goes offline. That distinction matters after a Wi-Fi interruption. You are changing whether Larix permits a start or resume attempt when its network check does not detect presence; you are not switching on a promise of unattended recovery.
Enable “Don’t check network presence”
In Advanced settings, turn on “Don’t check network presence.” The label is phrased as an instruction not to perform that check. In practical terms, Softvelum describes it as allowing Larix to connect when starting or resuming even if network presence has not been detected. It is intended to remove one gate before an attempt, not to create network access.
That limited effect is easy to misunderstand. If Wi-Fi drops and later returns, Larix may not automatically restore the interrupted broadcast. The option does not guarantee that an already interrupted session will restart, that an attempt will be made without you, or that the receiving service will accept the connection. You still need to return to Larix and choose to resume or start, and the phone needs working access to the destination.
Leave other advanced controls alone unless you know what they do and have a reason to change them. In particular, Softvelum’s FAQ identifies “Reconnect timeout w/o network” as an iOS-specific setting. It is not the Android fix described here, so do not spend time looking for it on an Android phone or assume a similarly named control is required.
Larix’s Android product information describes publishing over protocols including RTMP and SRT, so the exact destination and connection behaviour depend on the protocol you configured. Softvelum’s Android app page is the primary reference for the app’s supported Android context. This guide does not assume that every user is publishing through RTMP.
Resume or start the stream yourself
After enabling the option, go back to Larix’s preview or main streaming screen. Select the saved connection you intend to use, then use the app’s available control to resume or start the stream. Wait for the app to show whether it is connecting or publishing. If the attempt fails, note the actual status or error rather than repeatedly tapping the control without checking the destination or network.
The word “resume” can suggest that Larix will continue the exact interrupted broadcast automatically. Do not rely on that interpretation. In this recovery path, you are taking an action after Wi-Fi is back; the setting only permits an attempt despite a missing network-presence detection. A connection can still fail if the network is unstable, the receiving server cannot be reached, or credentials or destination details are no longer current.
If this is a YouTube destination, distinguish between the phone sending video and YouTube showing a live broadcast. Larix may report a publish connection while YouTube is still processing or waiting for the incoming feed. Check the destination side as well as the app, without exposing a stream key in a screenshot, message, or public post. For the wider question of what to do when a continuous programme has stopped, the guide to keeping a children’s story stream playing while OBS is closed explains a different, computer-based arrangement; it is not a Larix setting guide.
Check the saved server and stream details
If the phone is online, the correct connection is selected, and Larix still cannot publish, inspect the saved destination. Confirm that the server address, application or path, and stream name or key match the current values provided by the receiving service. If you recently changed a stream key, created a new broadcast, or selected another service destination, an older saved connection may no longer be valid.
For an RTMP connection, Softvelum’s Larix documentation reference describes the URL as combining the server and application address with the stream name or key. These pieces serve different purposes: the server/application part identifies where to send the feed, while the stream name or key identifies the particular destination or authenticates the publish session. A typo, missing separator, stale key, or wrong selected entry can prevent publishing even when Wi-Fi works.
Do not copy a key from an old note merely because it looks familiar. Open the current destination’s official settings and compare the values privately with Larix. If you replace the key in Larix, keep it out of shared screenshots and messages; anyone who obtains it may be able to use the destination. If the service provides distinct fields for server URL and stream key, follow its current instructions rather than combining values in a way the service does not request.
For SRT or another protocol, check the connection parameters against the receiver’s current configuration instead of applying RTMP URL assumptions. Larix supports more than one publishing method, and a diagnosis should follow the selected protocol. If you are unsure whether the problem is the phone app or the receiving side, use the receiver’s own connection instructions and status indicators before changing multiple Larix fields at once.
Diagnose a failed publish as a separate connection problem
If enabling the option and manually starting the stream do not work, treat the result as a new connection diagnosis. First test the phone’s internet again. Then check whether the selected saved connection is the intended destination and whether its details are current. Finally, look at the receiving service for an indication that a feed is arriving. This order avoids changing several variables at once and makes the failed step easier to identify.
A useful distinction is between “the phone is online” and “the destination is reachable and accepts this publish.” A webpage loading proves the former, not the latter. A receiving service may reject an expired key, an incorrect stream name, or a connection aimed at a different server. Conversely, a correct destination cannot receive anything while Android has no usable network. Write down the exact error or status shown by Larix, then compare it with the receiver’s current troubleshooting guidance.
If the stream has been configured for a local or managed receiver rather than a public platform, involve whoever maintains that receiving endpoint. Ask whether it is running and whether the expected protocol and destination are configured; do not expose credentials in the request. For a YouTube broadcast, check YouTube’s current live-control-room status and stream setup, using its official Help resources for any platform-specific message.
A saved connection can be useful because it avoids re-entering details after an interruption, but it also preserves stale values. When you do edit it, change only the field that the official destination instructions identify and make a note of the original value if appropriate. Avoid repeatedly creating new keys or connections as a first response: that can leave you uncertain which saved entry Larix is actually using.
For people operating an always-on channel, this incident also raises a separate design question: whether a phone should be the component that must remain connected and available. A phone-based stream depends on that handset, its network path, power, app state, and a person able to resume publishing. If your programme is a looped file rather than a live camera or mobile report, StreamNeo can remove the need to keep your phone or computer running by turning an uploaded video into a YouTube live stream, so a Wi-Fi drop on the handset is not the point of failure for that file-based channel. That does not make a live mobile contribution unnecessary when your format genuinely needs one.
A recovery check is still worthwhile even if you later choose a different operating arrangement. Keep the intended destination details securely available, know how to confirm the phone’s internet connection, and test the start/resume action when you can observe the result. A quiet devotional or study stream can be particularly hard to diagnose if you only discover a problem after leaving the phone unattended. Plan for what you will check, not for an automatic recovery that the setting does not promise.
If you are weighing a file-based continuous stream against a computer-managed workflow, the FFmpeg and GStreamer comparison for 24/7 YouTube streaming in India may help you think through the maintenance involved. It covers a different setup from Larix on Android, so use it to compare operating responsibilities rather than as an instruction to install another tool on your phone.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Will Larix reconnect automatically when Android Wi-Fi comes back?
Do not assume it will. Softvelum says the network-presence option permits Larix to attempt a connection when starting or resuming without detected network presence; it does not guarantee automatic recovery of an interrupted stream. Once internet access is back, return to the app and manually resume or start the stream.
Where is “Don’t check network presence” on Android?
Open Settings > Connections > Advanced settings in Larix Broadcaster and enable “Don’t check network presence.” It changes the network-presence check for a start or resume attempt. It does not repair Wi-Fi or confirm that your server and stream details are correct.
Should I look for “Reconnect timeout w/o network” on Android?
No. Softvelum’s FAQ labels “Reconnect timeout w/o network” as iOS-specific. On Android, use the documented network-presence option and take a manual start or resume action after the phone has working internet.
What should I check if Larix still will not publish?
Confirm internet access on the phone, verify the selected saved connection, and compare its destination details with the receiving service’s current instructions. For RTMP, check both the server/application address and the stream name or key; for other protocols, follow that receiver’s protocol-specific configuration. Keep stream keys private.