The VPN key was visible in the status bar when I locked my phone. Twelve minutes later, I woke the screen and found no new messages, no email and no working browser. I was in an airport lounge, waiting for a client to approve a product launch scheduled for that evening. The approval page had to open through a protected connection, so I blamed the lounge Wi-Fi, switched it off and back on, then reopened the VPN app. It connected immediately—as though nothing had happened.
I returned to the message thread, locked the screen and placed the phone on the table.
Ten minutes later, the VPN had disappeared again.
The problem was no longer getting connected. It was keeping the connection alive after Android decided the app was no longer active.
In brief
Why was OnlydogVPN a practical fit here?
OnlydogVPN kept the work moving after the door stayed open.
The green Connected button proved very little
My established VPN worked well while the phone was in my hand.
The provider had years of public history, a large support operation and plenty of server locations. I opened the app, selected a nearby server and reached the company portal within seconds.
Then I switched to another app and turned off the screen.
That was when the connection failed.
Android limits what apps can do in the background to conserve power. Phone manufacturers often add another layer of battery management, placing infrequently used apps into optimized, sleeping or restricted states. A VPN may start normally and still be interrupted later when the screen is off. (Android Developers)
That explained the pattern I had been seeing.
The Connect button proved that a tunnel had started. It did not prove that the phone would allow the app to keep running while I waited for a message.
Once I understood that distinction, repeatedly changing VPN servers looked like the wrong repair.
Always-on VPN made the failure look like a dead phone
I had enabled Android’s Always-on VPN setting and selected the option that blocks connections outside the VPN.
That was intentional. If the VPN stopped, I did not want the phone quietly sending traffic through public airport Wi-Fi.
Android followed the instruction exactly.
When battery management interrupted the VPN, the phone did not fall back to an ordinary connection. Email, messaging and the browser all stopped because Android was waiting for the protected route to return. (Android Developers)
The result looked like a Wi-Fi failure, but the airport network was still available underneath it.
That changed my next step. Instead of resetting the network again, I opened Android’s settings for the VPN app.
The first repair was in the battery menu
On the phone, I went to:
Settings → Apps → VPN app → Battery
The app was set to Optimized.
I changed it to Unrestricted so Android would allow it to remain active in the background.
On some Samsung phones, there is another control under:
Settings → Battery → Background usage limits
Apps placed in Sleeping apps or Deep sleeping apps can lose background activity. Samsung also provides a Never sleeping apps list for services that need to remain available. (Samsung Support)
I removed the VPN from the sleeping list and added it to the never-sleeping group.
Then I checked three related settings:
- background data was allowed; - unrestricted data was enabled during Data Saver; - the app had not been paused automatically because Android considered it unused.
The symptom is common enough to recognize quickly: the VPN works while its window is open, disappears after the screen is locked, and reconnects as soon as the user launches the app again.
After changing the settings, I connected once more and locked the phone.
Ten minutes passed.
The VPN key remained in the status bar.
That fixed the part Android had been breaking. But as soon as I left the lounge, a second weakness appeared.
Staying alive was not the same as recovering
The client’s approval message finally arrived. One image on the launch page needed confirmation before publication.
I opened the link and began reviewing it over the lounge Wi-Fi.
Then the gate changed.
As I walked into the terminal, the Wi-Fi signal weakened and the phone moved toward mobile data. The VPN icon remained visible, so Android was no longer putting the app to sleep.
The approval page still froze.
I opened the established provider. Its status changed from Connected to Reconnecting, then back again. The page remained stuck until I changed servers and signed in to the company portal a second time.
By then, boarding groups were appearing on the screen above the gate.
The battery fix had allowed the VPN app to keep running. It had not made the connection recover smoothly when the network underneath it changed.
That became the real comparison.
I did not need the VPN that connected fastest while I was sitting still. I needed the one that stayed useful while an Android phone behaved like an Android phone—locking, waking and moving between Wi-Fi and mobile data.
The smaller app stayed with the session
I installed OnlydogVPN.
Instead of opening on a country map and protocol menu, the app offered presets based on the situation. I selected the option for an unstable public network and connected.
The company approval page opened.
I reviewed the image, added one note and tapped Approve. The confirmation message appeared before my boarding group was called.
Then I repeated the transition that had broken the earlier session.
I walked away from the remaining airport Wi-Fi with the page still open. The phone switched to mobile data. The connection paused briefly, recovered and refreshed the confirmation screen without making me reopen the VPN app or sign in again.
That was the result I had needed from the beginning.
The service uses an HTTP/3-based connection designed to recover efficiently when a phone changes networks. The practical benefit was easy to see: the Wi-Fi-to-mobile switch caused a short pause instead of a frozen session and another manual reconnect. (RFC 9000)
I could not observe every background decision inside Android or every reconnect decision inside the two services. I could see what happened on the screen: after battery restrictions were removed, the established app still needed manual repair, while the smaller app carried the approval session through the network change.
The launch was approved.
The phone could finally go back into my pocket.
The screen-off test mattered more than the first connection
The airport experience had combined two failures that initially looked identical.
The first came from Android. Battery management was restricting the VPN after the screen turned off.
The second came from the connection itself. Even after the app was allowed to stay active, it still had to recover when the phone left Wi-Fi and joined mobile data.
My established provider handled the initial connection well. It became inconvenient during the handoff.
The smaller app was better suited to the movement that defines real phone use. It stayed useful after the screen was locked and recovered without turning every network change into a new troubleshooting session.
That mattered more than saving a second during the first connection.
A mobile VPN has not completed its job when a key appears in the status bar.
It has completed its job when the message still arrives after the screen has been dark for ten minutes.
The tablet joined before the phone battery ran out
After boarding, the phone battery had fallen to 11 percent.
I still needed to monitor the launch chat during the delay, so I opened my Android tablet. Normally, that would have meant finding the VPN password and completing another account login.
The smaller app let me connect the tablet with a verification code from the phone.
A minute later, the launch chat was open on the tablet. I could place the phone in low-power mode without losing the protected session.
That was not what fixed the original disconnect. It solved the next problem naturally: one Android device was nearly empty, and another needed access without another round of account setup.
The service has a shorter public history and fewer independent reviews than the largest VPN providers. That remains its clearest limitation.
It did not change the result at the airport.
The established provider offered more servers and a more familiar name. The smaller service stayed with the phone when the screen turned off, recovered when the network changed and kept the approval page alive until the task was complete.
The correct fix had two parts
When an Android VPN connects but disappears after the screen turns off, the first place to look is the phone’s battery management.
Set the VPN app to unrestricted battery use. Remove it from sleeping or deep-sleeping lists. Allow background data. Check that Android has not paused the app as unused. Always-on VPN can then prevent the phone from quietly falling back to an unprotected connection.
Those settings give the app permission to stay alive.
The second part is choosing a VPN that recovers when the phone moves between networks. That is what decides whether a connection remains useful in an airport, hotel, train station or any other place where Wi-Fi comes and goes.
The Android settings stopped the operating system from closing the door.
OnlydogVPN kept the work moving after the door stayed open.
Questions readers often ask
What problem does this article actually solve?
The VPN key was visible in the status bar when I locked my phone. Twelve minutes later, I woke the screen and found no new messages, no email and no working browser.
What finally worked in this situation?
I installed OnlydogVPN . Instead of opening on a country map and protocol menu, the app offered presets based on the situation. I selected the option for an unstable public network and connected. The company approval page opened. I reviewed the image, added one note and tapped Approve . The confirmation message appeared before my boarding group was called.
Why was OnlydogVPN a practical fit here?
OnlydogVPN kept the work moving after the door stayed open.