Time Runs While Your Phone Is Locked on Piso WiFi: WiFi Auto Off, Battery Saver, and Pause Checks

Up: Troubleshooting · Also in Troubleshooting and Fixes: Session Wrong Time Left · Portal Not Loading

Time that runs while your phone is locked is one of the most frustrating Piso WiFi problems, because you did nothing wrong on purpose. You locked your phone, stepped away, and came back to find minutes gone. In most cases the cause is not a stolen session. It is a phone setting that turns WiFi off, switches to mobile data, or lets the portal session drop when the screen locks, combined with a pause setting that was not used or was not enabled.

This post covers only the locked phone, WiFi auto off case. If your session expired while paused, go to the Session Expired While Paused guide. If you cannot resume a paused session, go to the How to Resume guide. If the portal itself will not load after a drop, go to the Portal Not Loading guide.

Symptom Check: Did Time Run, or Did the Session End?

Note which of these you saw, because the fix is different.

What you saw after unlocking	What it may mean	First check
Timer shows less time, but the session is still active	Time ran while locked, because WiFi stayed on but pause was not used, or pause was not enabled	Check whether you tapped Pause before locking, and whether pause is enabled on that machine
Timer shows zero, or no session, after unlocking	Session ended during lock, through expiry, a reconnect as a new device, or a machine reboot	Check the original device, portal, and pause records before paying again
Phone switched to mobile data while locked, and the portal shows no session	WiFi was turned off or switched away during lock, and the session dropped	Check WiFi sleep, battery saver, and mobile data switching settings, as below
Phone shows WiFi connected after unlocking, but the portal timer is gone	Session record was cleared, replaced, or expired during lock	Note lock duration, pause use, and whether other customers were affected, and report it before paying again

Do not pay again until you know whether the original session is still recoverable. A second payment can replace a session that might still be resumable.

Likely Causes, in Order

Cause 1: Pause was not used before locking

On most systems, locking a phone does not pause the timer. Closing the browser, turning off WiFi, or disconnecting does not pause the timer either, unless the platform offers auto pause and it is enabled for that machine. If you locked your phone without tapping Pause on the portal, time will run normally while locked. This is the most common cause, and it is a habit fix, not a phone fault.

Cause 2: Pause was enabled, but a limit or expiry passed while locked

If you did pause before locking, time should freeze, but only within the pause limit and auto expiry window for that machine. LPB commonly reports a 60 minute pause limit, configurable by the operator, and auto expiry is commonly 24 hours, operator configurable. AdoPiSoft pause is count based, with reported counts varying, so check your own machine. If you locked the phone for longer than the pause limit, or past auto expiry, the session can end while locked, even though you paused correctly.

Cause 3: WiFi sleep or battery saver turned WiFi off during lock

Android WiFi sleep settings, and battery saver settings on both Android and iPhone, can turn WiFi off, switch to mobile data, or restrict background WiFi while locked. That can drop the portal session, especially if the machine treats a reconnect as a new device. Check these settings before your next paid session, not in the middle of a paid session, because changing a private address setting mid session can make recovery harder.

Cause 4: Private address change on reconnect after lock

A private WiFi address or randomized MAC that changes between connections can make the machine treat the same phone as a new device after unlock. This affects resume after a pause more than first login, but it can also affect a session that dropped during lock. Set the private address behaviour before you pay, if you are troubleshooting a machine that repeatedly fails to recognise your device, as explained in the Login pillar and the Pause Time pillar.

Cause 5: Machine reboot, power cut, or ISP drop during lock

If the machine rebooted, lost power, or lost its internet source while your phone was locked, a local session can clear, even if you paused correctly. On a cloud connected system, the session record may survive, but you still need to reconnect and resume on the same device. Note whether other customers were affected, and whether the machine restarted, before concluding your phone caused the loss.

User Checks, by Phone Type

Android checks, before your next paid session

1. Open WiFi settings for the Piso WiFi network, and check WiFi sleep or “Keep WiFi on during sleep” settings. Set it to keep WiFi on during sleep for that network, if the option exists.
2. Check battery saver and battery optimisation for the browser and for WiFi, and test whether battery saver turns WiFi off while locked. Turn battery saver off for a test session if needed, and note the result.
3. Check mobile data switching: turn off mobile data until the portal opens and the session starts, and check whether the phone switches to mobile data while locked.
4. Check Private DNS, and set it to Off or Automatic while you log in, if the portal behaves strangely after a drop.
5. Before you lock the phone, tap Pause on the portal if pause is enabled, and note the pause time and limit. Do not rely on locking alone to pause.

iPhone checks, before your next paid session

1. Check that WiFi stays on during lock, and that the phone has not switched to mobile data while locked. Turn off mobile data until the portal opens and the session starts, for a test session.
2. Check Low Power Mode and any VPN or private relay that starts automatically, because these can affect portal behaviour after a drop. Turn them off for a test session if needed.
3. Check the Private WiFi Address setting for the Piso WiFi network, before you pay, if the machine repeatedly fails to recognise your device after a drop. Do not change it in the middle of a paid session.
4. Before you lock the phone, tap Pause on the portal if pause is enabled, and note the pause time and limit.

After unlocking, what to do first

1. Stay on the exact WiFi name, on the same device, and open the portal. Do not switch devices to check the timer.
2. Check the timer in an incognito window if the normal portal page looks stale, without paying again.
3. If you paused before locking, tap Resume on the same device, and note whether the timer returns.
4. If the session is gone, note lock duration, pause use, battery saver state, and whether other customers were affected, and report it before paying again.

Operator Checks, Labelled as Operator Only

Customers should not change machine, access point, or platform settings themselves. For the operator, the checks are:

• Check the session list for the device and lock window: start time, pause records, pause limit, auto expiry, reconnect records, and whether a reboot or power cut happened during that window.
• Check pause settings for the payment mode used: enabled or disabled, limit, and auto expiry, and whether auto pause on disconnect is offered on that platform build, such as some Ruijie and SmartFi builds reported in operator notes.
• Check machine clock and reboot history, because a wrong clock or a reboot can make a valid paused session look expired.
• If the session record still exists, help the customer resume on the original device through the platform’s own session tools. Do not ask the customer for banking passwords or social media passwords to check a session.

Proof to Show the Operator

Include, in one message:

• Machine location and WiFi name.
• Device type, Android or iPhone, and whether battery saver or Low Power Mode was on.
• Time you started, time you locked the phone, time you unlocked it, and whether you tapped Pause before locking.
• Timer before locking, and timer after unlocking, with screenshots if you can take them safely.
• Whether other customers were affected, and whether the machine restarted or lost power during lock, if you know.

Prevention

For users, prevention is a habit, not a phone fix: tap Pause on the portal before you lock the phone, if pause is enabled, and note the pause limit. Keep WiFi on during sleep for that network, turn battery saver off for a test session if it drops WiFi, and turn mobile data off until the session starts. For operators, prevention is clear pause information on the sign and portal, correct pause limits and auto expiry settings, and a test as a customer that includes locking a phone, pausing, unlocking, and resuming, so a lock problem is found before customers lose time.

Frequently Asked Questions About Time Running While Locked

Does locking my phone pause my Piso WiFi time?

No, not on most systems, unless you tapped Pause on the portal and pause is enabled on that machine. Locking, closing the browser, or turning off WiFi does not pause the timer by itself. Some builds offer auto pause on disconnect, but that is platform and operator specific, so check the portal for a Pause button before you rely on it.

I paused before locking, but time still ran. Why?

Check whether pause was actually confirmed, whether the pause limit or auto expiry passed while locked, whether the machine rebooted, and whether a private address change made the machine treat your phone as a new device on reconnect. Note the pause time and limit, and report them with the session times.

Should I turn off battery saver for Piso WiFi?

For a test session, yes, if battery saver turns WiFi off while locked. Battery saver can save power by restricting WiFi, which can drop a portal session. Test with battery saver off, from the same spot, and compare the result, before concluding the machine is at fault.

Will changing my private address setting mid session recover lost time?

No. Changing a private address setting in the middle of a paid session can make recovery harder, because the machine may treat the phone as a new device. Set private address behaviour before you pay, if you are troubleshooting a repeat recognition problem.

My phone locked for only a few minutes, but all my time is gone. Is that normal?

No, not if you paused correctly and the pause limit had not passed. A few minutes of lock should not erase a session on its own. Report it with lock duration, pause use, and timer readings, so the operator can check for a reboot, clock error, or session replacement during that window.

Can I prevent this by using a laptop instead of a phone?

A laptop can help if the problem is phone WiFi sleep or battery saver, because laptops often keep WiFi on differently. It will not help if the problem is pause not used, pause limit passed, or a machine reboot, because those affect any device. Fix the pause habit and settings first, regardless of device.

What to Read Next

If your session expired while paused, go to the Session Expired While Paused guide. If you cannot resume, go to the How to Resume guide. If the portal will not load after a drop, go to the Portal Not Loading guide. If the portal loads on one phone but not another, go to the Portal Loads on One Phone Not Another guide. If you want the full pause rules, go to the Pause Time pillar.