How AndroidIRCX Keeps IRC Running in the Background

IRC expects a long-lived connection, while Android is designed to save battery by limiting background work. AndroidIRCX can maintain a foreground connection and reconnect intelligently, but no application can promise that every phone manufacturer will leave it alive indefinitely.

The two settings that matter first

Open Settings > Background & Battery and enable Keep Connection Alive. Check the displayed battery-optimization status and use Open Battery Settings to exclude AndroidIRCX if your device permits it. A foreground service normally uses a persistent notification; removing or restricting that notification on some Android versions can undermine background reliability.

Manufacturer “battery saver,” “sleeping apps,” autostart and background-data controls may exist outside standard Android settings. If connections disappear only after the screen has been off, inspect those controls and allow AndroidIRCX to operate in the background.

Reconnection is layered

Each network can enable Auto-Reconnect, Rejoin Channels After Reconnect and Smart Reconnection. Smart reconnection spaces attempts to reduce reconnect floods. The initial delay defaults to 1,000 ms, maximum delay to 60,000 ms, and maximum attempts can be set to zero for unlimited attempts.

Reconnecting a socket and restoring a session are not identical. The client must register, authenticate, regain IRCv3 state and then rejoin configured rooms. A nick collision, expired SASL credential, network ban or unavailable server cannot be solved by faster retries. Multiple servers on a network allow the app to try another endpoint when one fails.

Channel continuity

Favorite and auto-join settings determine what returns after a successful connection. Enable Rejoin Channels After Reconnect for transient disconnects and configure favorites/auto-join deliberately. Do not assume every manually opened private query or temporary channel should be re-created.

Server-time, chat-history capabilities and a bouncer make the experience more continuous, but they solve different problems. Server-time timestamps messages accurately; history retrieves what the server retained; a bouncer such as ZNC stays connected when the phone cannot.

Scripts and timers in Doze

Android may delay timers, suspend networking or reclaim the process. Therefore a script timer is suitable for reminders and best-effort automation, not a guarantee that a moderation job runs at an exact second while the device sleeps. Critical 24/7 automation belongs on a server-side bot or bouncer. After process restoration, scripts should rebuild transient state and use persistent storage only for data that genuinely needs to survive.

Connection-quality tools

Under Settings > Connection & Network, AndroidIRCX provides rate limiting, flood protection, lag monitoring and connection statistics. Ping measurements help distinguish an idle-looking channel from a dead socket. Flood limits protect against a reconnecting script dumping queued output. IRCv3 Diagnostics shows CAP, ISUPPORT and transport state when a problem is protocol-specific.

A reliable configuration checklist

Use TLS and a stable server/port.
Configure SASL so reconnection does not wait for manual NickServ login.
Enable Keep Connection Alive and permit foreground notifications.
Exclude the app from battery optimization where appropriate.
Enable smart auto-reconnect and rejoin.
Add more than one valid server to important networks.
Use a bouncer for guaranteed presence and offline history.
Test with the screen off, Wi-Fi/mobile handover and a device restart.

If reconnect loops continue, check the actual server error before raising retry limits. Bad credentials, TLS verification failure and network policy are configuration failures, not temporary outages. The Advanced Settings wiki contains the current menu paths and defaults.