Android “Optimized” My VPN—Then Silently Cut Off My Connection

The approval link arrived when my phone was at 18 percent. I was leaving a conference hotel, and the document needed my signature before the finance team closed for the day. Earlier, Android’s battery screen had placed my VPN near the top of the usage list, so I had changed its battery setting from Unrestricted to Optimized. It seemed sensible: save the battery while keeping the protection running. Instead, the approval page stopped loading after the screen had been off for several minutes. I blamed the hotel Wi-Fi and reconnected to it. The signal returned; the internet did not.

The VPN key remained visible for a moment. Then it disappeared.

When I opened the established VPN app, it behaved as though I had launched it fresh. The connection was gone, while Android’s Block connections without VPN setting had correctly prevented the phone from sending traffic outside the tunnel.

I reconnected, reopened the approval page and signed the document.

Then I locked the screen again.

Ten minutes later, the same thing happened.

The battery percentage had sent me in the wrong direction

Android makes background battery use highly visible. Apps that keep working while the screen is off are easy to treat as wasteful, and a VPN often appears unusually active because nearly every online action passes through it.

That does not mean the VPN created all the activity shown beside its name. Hardware-based testing has found that Android’s battery screen can attribute much of a streaming session’s network activity to the VPN handling it, even when the tunnel itself adds relatively little power use. (Techradar)

I had seen a large percentage and assumed the app was draining the battery. By selecting Optimized, I had given Android permission to restrict the background process responsible for keeping the tunnel available.

The irony was hard to miss. I had tried to preserve 18 percent of a battery and disabled the connection I needed before that battery ran out.

Once that became clear, the disappearing key icon no longer looked like a Wi-Fi problem. It looked like Android had put the wrong app to sleep.

What Android was actually stopping

Android reduces background work when a phone sits idle. That is useful for games, shopping apps and services that do not need to remain active every minute.

A VPN is different. Its background activity is the product. The tunnel has to remain available while the screen is off so that email, notifications, links and other apps still use the protected connection.

Phone manufacturers can make these restrictions even more aggressive. Samsung separates apps into sleeping, deep-sleeping and never-sleeping groups. Other Android brands use labels such as battery optimization, background restrictions or automatic app management. (Google)

The wording changes, but the failure is familiar: the VPN works while the phone is in use, then disappears after the screen has been off. (Reddit)

That was exactly my pattern.

The first repair was therefore not another VPN server. It was removing the VPN from Android’s sleep routine.

On the test phone, I opened:

Settings → Apps → VPN app → Battery → Unrestricted

I also checked Samsung’s Background usage limits and removed the app from the sleeping lists. Then I enabled Android’s Always-on VPN again.

This time, the process remained active after the screen went dark. The key stayed in the status bar, and the app no longer opened as though Android had cleared it from memory.

That solved the first problem.

It also exposed the second one.

Keeping the app alive was not enough

I locked the phone while it was connected to the hotel Wi-Fi. A few minutes later, I walked outside and woke it after it had moved onto mobile data.

The established VPN was still present, but the approval page could not refresh. Sometimes the connection returned after a delay. Sometimes I had to open the app and tap reconnect.

The battery exemption had stopped Android from killing the service. It had not made the tunnel recover quickly after the network changed.

That distinction changed what I was comparing.

The established provider had years of public history, a large support operation and many server locations. Those were genuine strengths. On stable Wi-Fi, it was also fast.

But my problem was not a lack of server choices. It was the gap between waking the phone and having a usable protected connection.

A VPN can remain technically present while still failing the next thing I need to do. On a phone, that gap is not a minor inconvenience. It is the difference between seeing an urgent message and staring at a page that will not refresh.

So I stopped testing speed and started testing the moment after the screen woke.

The smaller app was ready when the phone woke up

I installed OnlydogVPN, changed its battery use to Unrestricted and selected its preset for a weak or changing connection.

Then I repeated the sequence that had broken the first app.

I connected on hotel Wi-Fi and opened the finance portal. I locked the phone for fifteen minutes. While the screen was off, I left the building and allowed the device to move onto mobile data.

When I unlocked it, the approval page refreshed.

The work chat synchronized immediately. A message from finance appeared, followed by confirmation that my signature had been received.

Nothing dramatic happened because nothing required my attention. There was no manual reconnect, no server search and no second attempt at the document. The protection had survived the part of phone use that normally stays invisible: sitting idle, changing networks and waking when something becomes urgent.

The smaller app uses HTTP/3-based transport and is designed to recover on weak or changing connections. The protocol name mattered less than what happened on the screen. Android had kept the service alive, and the app restored a usable tunnel before I needed to repair it myself.

I could not see every internal Android process-management or reconnection decision behind the two results. I could see the practical difference: after receiving the same battery exemption, the established app repeatedly delayed the next action, while the smaller one was ready when the screen came back on.

The approval page was not a benchmark. It was better evidence than one.

The battery number looked different after that

Later that evening, I checked Android’s battery page again.

The VPN was still listed as an active background app. That no longer bothered me. My browsing, messaging and document traffic was passing through it. Some visible background activity was expected.

The useful question was not whether the VPN appeared in the battery report. It was whether allowing it to run unrestricted made the phone unusable.

It did not.

The battery lasted through the evening, and the connection was available each time I woke the screen. I did not have to choose between protecting the phone and receiving the message I was protecting it for.

That also made the real troubleshooting order much clearer.

When an Android VPN dies after the screen turns off, start with the operating system:

• Change the VPN app’s battery setting to Unrestricted.
• Remove it from sleeping or deep-sleeping app lists.
• Keep Always-on VPN enabled when continuous protection matters.
• Lock the phone long enough for Android’s idle controls to take effect, then test it again.

The final step matters. A VPN that works only while its settings page is open has not passed the problem the user is trying to solve.

Once Android is no longer killing the app, watch what happens when the screen wakes or the phone changes networks. If every return requires a manual reconnect, the battery setting was only part of the failure.

That was the point at which the smaller app separated itself. It did not merely remain listed as active. It returned the phone to a usable protected state before the urgent page had time to fail.

What mattered more than the battery chart

The service has a credible limitation. It offers fewer server locations than the largest providers and has a shorter public history with fewer independent ratings. That matters when the task depends on reaching many specific countries.

It did not matter here.

This problem was not caused by a missing location. Android had been allowed to put the VPN to sleep, and once that setting was corrected, the established app still recovered too slowly.

The larger provider offered more destinations and a more familiar name. The smaller app was available when the screen woke and the document could not wait.

When Android battery optimization keeps silencing a VPN, the percentage beside the app matters less than whether the protected connection is already there when you pick up the phone.