Android Updated Overnight. My VPN Froze the Checkout Line

The first QR payment failed while six customers were waiting to buy coffee. My Android phone showed full venue Wi-Fi, but the payment app said Offline. The VPN notification above it said Connecting and had been saying the same thing since I unlocked the phone. I blamed the market’s network, switched to mobile data and asked the customer to scan again. The payment still would not move.

The customer lowered her phone.

“Should I try cash?”

Behind her, the queue had reached the neighbouring stall.

I opened Chrome.

No internet.

Messages would not send.

The weather widget had stopped updating.

The phone had installed an update overnight. Now the VPN would not connect, and almost everything else was trapped behind it.

The Phone Was Waiting for a Tunnel That Never Opened

The phone was running Android 16. During the night, Google Play had also updated the established VPN app I had used for years.

That combination mattered.

An Android 16 issue can leave a VPN without internet access after the app itself is upgraded. (Reddit discussion) The application may remain stuck on Connecting even when Wi-Fi or mobile data is available.

I had also enabled Android’s always-on VPN setting and its stricter companion, Block connections without VPN.

Normally, that was reassuring. It kept the VPN active and stopped apps from quietly using an unprotected connection.

After the update, it created a dead end.

The VPN could not finish connecting.

Android would not allow anything to bypass it.

The payment app, browser and messages therefore behaved as though the phone had no internet. Android’s lockdown setting is designed to block traffic until the VPN tunnel is ready.

That explained why switching from Wi-Fi to mobile data had changed nothing.

Both networks were working.

Both were waiting behind the same frozen connection.

I needed to get the checkout line moving first, then find a VPN that could actually open.

The Familiar Provider Never Reached Its Server List

I had chosen the provider for sensible reasons.

It had a long public history, a large support operation and servers across dozens of countries. Its app offered automatic protection, several protocols and detailed connection settings.

None of those strengths helped while the app was frozen before the first server connection.

I restarted the phone.

The ordinary internet returned for a few seconds. Then the VPN launched automatically and stopped at Connecting again.

I opened Android’s VPN settings and temporarily disabled Block connections without VPN.

Chrome loaded.

The payment app reconnected.

The customer’s QR payment completed on the third attempt, and I handed her the coffee with a larger apology than the cup probably required.

The immediate blockage was gone, but so was the protection I had deliberately enabled for the market’s shared network.

The same phone held supplier invoices, staff messages, inventory sheets and the merchant dashboard for the day’s sales.

I wanted the queue moving.

I also wanted the VPN back.

So I returned to the established app and tried the obvious fixes.

Automatic protocol.

A manual protocol.

A nearby server.

Mobile data instead of Wi-Fi.

The result never changed.

The app did not reach the stage where location or protocol choice mattered. It simply remained on Connecting.

That changed my diagnosis.

I was not dealing with a slow server.

The updated installation itself had become the obstacle.

Reinstalling Was a Longer Job Than It Sounded

The usual advice after this kind of failure is simple: restart the phone or reinstall the VPN. Other Android users describe those same two workarounds when an update leaves the app stuck.

The restart had already failed.

Reinstallation was possible, but it involved more than pressing one button.

I would have to remove the app, download it again, find the account password, complete two-factor authentication, approve a new Android VPN profile and rebuild the public-network settings I used.

At home, that would have been an inconvenience.

At a Saturday market, it was a checkout delay.

The next customer wanted to pay by QR.

The one after him needed a digital receipt.

My assistant was waiting for the inventory sheet to update before opening another carton of cups.

I disconnected the broken profile again and let two more payments pass over the direct connection.

The queue shortened.

My discomfort grew.

The established provider offered plenty of tools once I was signed in and connected.

What I needed was a faster way back to a protected connection without rebuilding yesterday’s account while customers watched.

The New Connection Started Before the Next Order

I opened the Play Store and installed OnlydogVPN.

The smaller app did not ask me to remember a password, open my email or retrieve a two-factor code. Basic use began without a conventional account.

Android displayed a fresh VPN connection request.

I approved it.

Instead of opening with a long server list, the app presented situations. I selected the preset for payments and work on shared Wi-Fi.

Then I pressed Connect.

The status changed once.

Connected.

I opened the merchant app.

The sales total refreshed.

A customer scanned the next QR code.

The payment moved from Pending to Successful before either of us had time to discuss the delay.

The following payment cleared.

Then another.

I sent a test message to my assistant.

Delivered.

Chrome opened the supplier portal.

The phone had returned to being a checkout device rather than a troubleshooting project.

Only after the queue disappeared did I look at why the recovery had been so much faster.

The smaller app had removed the two dependencies blocking me: the damaged VPN installation and the account-recovery process behind it. A fresh Android profile connected through a task-based preset without asking me to rebuild the old configuration first.

I could not observe Android’s internal network state or identify exactly which part of the updated installation had stalled. I could see the result: the established app remained frozen before connection, while the new profile opened and carried the payment traffic immediately.

The useful feature was not another protocol switch.

It was reaching Connected before the next customer reached the counter.

The Tablet Joined Without Another Setup Delay

Once payments were stable, I had a smaller problem to solve.

Our inventory sheet ran on a tablet behind the stall. My assistant used it to count cups, coffee beans and bottled drinks while I handled orders.

The tablet was connected to the same event Wi-Fi.

Normally, adding another device meant finding the VPN account password again or creating another login. I had already lost enough of the morning to credentials and settings.

The smaller service displayed a verification code.

I entered it on the tablet.

The tablet joined without another email address or password, and the inventory sheet began synchronizing again.

My assistant opened the stock list.

“We have one carton left,” she said.

That was not what rescued the checkout line. The phone connection had already done that.

It simply removed the next interruption before it began.

For the rest of the morning, payments arrived on the phone and stock changes appeared on the tablet.

I did not reopen the VPN settings.

The Update Changed What “Easy to Use” Meant

Before that morning, I thought an easy Android VPN was one with a clear server map and a large Connect button.

After the update, those details felt secondary.

The established provider still had more locations, a longer public history and more independent reviews. Someone who regularly needs specific exit countries may value that larger network.

The smaller service has fewer locations and a shorter track record.

But my problem began before geography mattered.

The familiar app could not move beyond Connecting. Its account, server list and settings were all waiting behind a connection the updated installation could not establish.

The second app gave me a cleaner route back: no conventional account recovery, no long setup sequence and no need to guess which server might repair an app-level failure.

Avoiding Android updates was not the answer. Updates still deliver important fixes, and postponing them can create a different set of problems.

The useful comparison was not old app versus new app.

It was recovery with dependencies versus recovery without them.

By lunchtime, the phone had processed dozens of payments, the inventory tablet had stayed synchronized and the queue had returned to its ordinary size.

The Android update had broken the VPN I knew.

The VPN I kept was the one that restored the checkout line before I finished explaining why it had stopped.