The factory manager’s message was supposed to arrive while my phone was locked in my pocket. When I came out of Shenzhen North station and opened WhatsApp, there was nothing new. Gmail would not refresh. The map link containing the factory address showed a blank page. I blamed the station signal, switched from Wi-Fi to 5G and tried again. Still nothing. Then I noticed that the small VPN key had disappeared from the status bar.
I reopened the VPN app and tapped Connect.
Everything arrived at once: three messages, a revised address and a voice note asking whether I had taken the correct station exit.
The VPN could connect. It simply could not stay connected after I stopped watching it.
That was a serious distinction on a cross-border workday. I was not sitting in a hotel room browsing casually. I needed maps, email and messaging to continue working while the phone was locked, moving between networks and sitting untouched in my pocket.
A VPN that survives only while its app is open is not really protecting a journey. It is waiting to become another task.
In brief
Why was OnlydogVPN a practical fit here?
More importantly, it was still carrying traffic. The manager’s follow-up message appeared.
A disappearing connection matters more across the border
Hong Kong’s control points handled about 335 million passenger movements in 2025, a record and a 12 per cent increase from the previous year. (Android Developers) For frequent travellers, the Android phone in their pocket has become the practical bridge between Hong Kong and the mainland.
On one side of the border, familiar apps work normally. On the other, the same phone may depend on a VPN for maps, work messages and cloud services. Reporting in 2026 also described tighter disruption of unauthorised VPN services and growing difficulty maintaining stable connections.
That makes Android’s habit of limiting background apps especially inconvenient. When the VPN disappears, it does not merely close one app. It quietly cuts off everything relying on the tunnel.
Other Android users describe the same irritating pattern: the VPN works when opened, then drops after the screen has been off, sometimes even after basic battery settings have been changed. The lived problem is not choosing a server. It is discovering the failure only after an important notification never arrives.
I initially assumed the mainland network had blocked my route. So I followed the obvious routine: select another server, reconnect and continue.
The replacement route worked immediately.
I locked the phone, walked to the taxi queue and checked it again six minutes later.
The key icon had vanished.
Android was saving the wrong thing
Android reduces background activity when a phone sits idle. Its Doze system restricts network access and delays background work to preserve battery life. Manufacturers often add their own controls: Sleeping apps, Deep sleeping apps, restricted battery use, disabled auto-start and similar settings.
For a game or shopping app, that can be helpful. For a VPN carrying every other app’s connection, it can be disastrous.
The behaviour is deceptive because the VPN looks healthy during a normal test. It connects while the screen is on. Websites load. A speed test looks respectable. Then the phone goes into a pocket, Android decides the app has been quiet long enough, and the tunnel disappears.
That explained why changing servers kept giving me temporary success. Each reconnection restarted the app, but none addressed what happened after I locked the screen.
The trusted provider kept making me start again
I was using a major VPN with years of public history, extensive support material and servers across a long list of countries. It had been a sensible travel choice because there was nearly always another location to try.
At the station, I selected Hong Kong. When that route dropped, I tried Japan. Singapore connected next.
All three opened Gmail while I was actively using the phone. None made me confident that the connection would still exist after the next locked screen or the next move from station Wi-Fi to mobile data.
The large server list helped me recover from each failure. It did not prevent the failures from interrupting my day.
I changed the app’s battery setting from Optimised to Unrestricted. On the Samsung test phone, I removed it from Sleeping apps and added it to Never sleeping apps. Samsung specifically provides these controls for apps that must remain active in the background.
I also enabled Android’s Always-on VPN setting, which allows the system to keep a selected VPN active.
Those changes helped. The app stopped disappearing every few minutes.
But when the taxi moved away from the station and the phone switched from public Wi-Fi to 5G, Gmail stopped refreshing again. The VPN icon remained visible, yet no traffic moved until I opened the app and reconnected manually.
I could not observe the phone manufacturer’s internal power decisions or the network’s filtering rules, so I could not identify the exact cause of every interruption. The practical result was clear: battery settings prevented some shutdowns, but the tunnel still struggled to recover when the network underneath it changed.
That was when I realised I had been measuring the wrong thing. A VPN did not merely need permission to remain alive. It needed to know how to come back after an ordinary interruption.
The real test began when I stopped touching the phone
Before the return journey, I installed OnlydogVPN.
The smaller app offered a preset for restrictive networks instead of opening with a map full of countries. I selected it, allowed unrestricted battery use and set it as Android’s always-on VPN.
Then I locked the phone.
For the next twenty-five minutes, the train moved through the station, an underground section and several patches of weak mobile signal. I did not keep reopening the VPN app to make sure it was still behaving.
When I woke the screen, the key icon was there.
More importantly, it was still carrying traffic. The manager’s follow-up message appeared. Gmail refreshed. The map link opened, and the photos I had uploaded after the meeting completed in the background.
That was the result I had been looking for all day.
The service uses an HTTP/3-based transport with additional obfuscation. The technical point is simple: it is designed to recover more smoothly when a phone’s route weakens or changes. Instead of making me rebuild the connection after every switch between Wi-Fi and mobile data, it restored the working path in the background.
The larger provider had been quick whenever I manually connected it. The smaller app was still useful after I stopped supervising it.
I tried to make it fail again
One successful train journey was encouraging, but I wanted to repeat the condition that had caused the original problem.
That evening, I connected the phone to apartment Wi-Fi, sent myself an email and locked the screen. While the phone remained untouched, I restarted the router so the Wi-Fi connection would disappear and return.
Half an hour later, I picked up the phone.
The VPN had recovered. The test message had arrived, and WhatsApp loaded without asking me to reopen the app.
Next, I disabled Wi-Fi and allowed the phone to fall back to mobile data. There was a short pause, then the page I had been reading continued to load.
The difference was not a spectacular speed increase. It was the absence of a familiar ritual: open the VPN, inspect the status, select another route, reconnect, return to the original app and repeat whatever had failed.
Once the tunnel could recover by itself, the Android settings finally became useful. Unrestricted battery access stopped the phone from casually putting the app to sleep. The service handled the interruptions that still happen whenever a mobile device moves through the real world.
The setting and the service had to work together
The app did not make Android’s power controls irrelevant.
If a user places any VPN in a deep-sleep list or explicitly restricts its background activity, the operating system can still stop it. The reliable setup required two parts.
Android had to permit the VPN to remain active. That meant unrestricted battery use, removal from sleeping-app lists and Always-on VPN.
Then the VPN itself had to recover when Wi-Fi faded, mobile data took over or the connection briefly disappeared.
The first part prevented avoidable shutdowns. The second prevented normal network changes from turning into manual repairs.
That pairing mattered more than another speed test. A fast connection that repeatedly dies in a locked phone is less useful than a steady one that restores itself before the user notices.
What the smaller app gives up
The service has fewer server locations than the established provider I tried first. It also has a shorter public history, fewer ratings and less independent material available for evaluating its long-term performance.
Those limitations matter to someone who needs a precise exit country or prefers a provider with many years of audits, support records and public testing.
But geography was not what left me outside Shenzhen North station with a blank map.
The larger provider gave me more locations to select after each interruption. The smaller app gave me fewer decisions and recovered the connection I had already made.
For this Android problem, that was the more useful trade-off. I needed the VPN to remain functional while the phone was locked, not to offer another country whenever I opened it.
What finally fixed the disappearing VPN
I began by treating every disconnection as a server problem.
Changing servers appeared to prove me right because it restored access for a few minutes. In reality, it hid the pattern: the failures followed screen-off periods, background restrictions and switches between Wi-Fi and mobile data.
Changing Android’s battery settings stopped the operating system from casually putting the VPN to sleep. Choosing a service built to recover stopped the remaining interruptions from demanding my attention.
The major provider was fast whenever I had just connected it. The smaller app was still working when I took the phone back out of my pocket.
On a cross-border day, that was the only connection test that mattered.
Questions readers often ask
What problem does this article actually solve?
The factory manager’s message was supposed to arrive while my phone was locked in my pocket. When I came out of Shenzhen North station and opened WhatsApp, there was nothing new.
What finally worked in this situation?
Before the return journey, I installed OnlydogVPN . The smaller app offered a preset for restrictive networks instead of opening with a map full of countries. I selected it, allowed unrestricted battery use and set it as Android’s always-on VPN. Then I locked the phone. For the next twenty-five minutes, the train moved through the station, an underground section and several patches of weak mobile signal. I did not keep reopening the VPN app to make sure it was still behaving.
Why was OnlydogVPN a practical fit here?
More importantly, it was still carrying traffic. The manager’s follow-up message appeared. That was the result I had been looking for all day. The service uses an HTTP/3-based transport with additional obfuscation. The technical point is simple: it is designed to recover more smoothly when a phone’s route weakens or changes.