Last reviewed: November 2, 2026
Find your symptom
| Symptom | Most likely cause | Go to |
|---|---|---|
| Screen turns off even though the tool is running | Tab hidden, battery saver, or a lock policy | Screen still turns off |
| Tool stops after a few minutes in the background | Browsers release wake locks in hidden tabs | Background tabs |
| Mouse does not move on the phone | Sensor not reading the screen | Phone pattern |
| Screen stays on but Teams or Slack show Away | No input is created | Teams guide |
| “Not supported” or “Blocked” | Old browser, http page or refused request | Browser messages |
The screen still turns off
- Check the tool's status. If it says Paused, the tab was hidden; if it says Blocked, the browser refused the request.
- Keep the tab in front, in its own window if you work elsewhere.
- Turn off battery saver or plug in: browsers may refuse a wake lock on low battery[2].
- If the computer locks rather than just dimming, a lock or screen saver policy may be in force. Check the Windows or Mac settings; on a managed device it may not be changeable.
It stops when minimised or in a background tab
This is how the Screen Wake Lock API is designed: the lock is released automatically when you minimise the window or switch tabs[3]. A page can only request it again when it becomes visible[1]. Our tool does that automatically and logs each interruption, so you can see when protection was off.
For keep-awake that survives a minimised browser, use an operating system method: PowerToys Awake on Windows or caffeinate on Mac.
Chrome, Edge, Firefox and Safari messages
- Not supported: the API exists in Chrome and Edge 84, Firefox 126 and Safari 16.4 and later[3]. Update the browser.
- Needs HTTPS: the API only works on secure pages[1].
- Blocked / NotAllowedError: the request was refused, for example because of low battery or because the page was not visible at that moment[2]. Make the tab visible and tap the status to retry.
- Embedded page: inside another site's frame the API is blocked unless that site allows it[1]. Open the tool directly.
The phone pattern does not move the mouse
- Use the sensor check on the phone jiggler page so you know whether any movement arrives.
- Raise phone brightness to maximum and turn off battery saver; some phones dim when warm.
- Try Stripes or Speckle, then change the speed.
- Clean the screen and remove a matte or textured protector if possible.
- Make sure the mouse sits flat and is switched on; wireless mice may sleep.
- Accept that some sensors will not track on glass: mouse makers advise against glass and reflective surfaces[4]. Trackpads and trackballs cannot work at all.
If the phone screen turns off during the pattern, see the timeout guides for Android and iPhone.
Battery and brightness
Keeping a screen lit uses power, and a phone at full brightness drains fastest. Use the timer, plug devices in for long sessions, and expect power-saving modes to shorten timeouts or refuse wake locks.
Frequently asked questions
Why does my online mouse jiggler stop after a few minutes?
The tab was probably hidden or minimised, which releases the wake lock[3]. Keep it visible.
Does the mouse jiggler drain battery?
Keeping a screen on drains battery faster, especially a phone at full brightness. Use the timer.
My mouse jiggler keeps the screen on but Teams shows Away. Why?
A screen lock creates no input. See the Teams guide.
Sources
Official documentation consulted when writing this page. Menus and defaults change between versions, so check the current documentation for your version.
- Screen Wake Lock API — MDN Web Docs
- WakeLock: request() method — MDN Web Docs
- Stay awake with the Screen Wake Lock API — Chrome for Developers
- Cursor does not follow mouse movements — Logitech Support