Introduction
Hotspot automation is one of those routines that sounds trivial until Android makes it difficult. You want the phone to share its connection when you open your laptop, and stop sharing when you close it, without digging through settings menus twice a day. On older Android versions, an automation app could often toggle the hotspot directly. On Android 16, that direct toggle is restricted for ordinary apps, which means the old macro that worked for years now fails silently, leaving you tethered to a manual process you had deliberately automated away. The frustration is understandable, but the situation is not hopeless; it simply requires a different, legitimate mechanism.
That mechanism, for many users, is Shizuku combined with MacroDroid’s Fake UI option. Shizuku is a tool that lets approved apps use system-level functions through a secure, user-authorised channel, without root access. MacroDroid’s Fake UI option, in this context, refers to an approach where the automation interacts with the hotspot control through the system’s own interface layer rather than calling a blocked direct toggle. Together, they restore a working hotspot automation on Android 16, while keeping the phone within its normal security model. This guide explains what each piece does, how to set them up safely, and how to test the result so you are not left guessing whether the hotspot actually turned on.
A word of caution before you begin: Shizuku setup involves granting elevated access through a deliberate, multi-step process, and you should only install Shizuku from its official source and grant it to apps you trust, such as MacroDroid. Never grant this kind of access to an app you do not recognise, and never follow instructions that ask you to disable security protections wholesale. The method in this guide keeps the phone’s normal protections in place and uses only the permissions Shizuku and MacroDroid legitimately request. If any step asks for something that feels unrelated to hotspot control, stop and re-check the official documentation before continuing.
Prerequisites
You need a phone running Android 16, MacroDroid installed, and Shizuku installed from its official app store listing or official website. You also need a computer or a wireless debugging setup to start Shizuku initially, because Shizuku’s activation typically requires a one-time authorisation step through Android’s developer options, either over a USB connection or through wireless debugging on the phone itself. Enable developer options on your phone if you have not already, and read Shizuku’s own startup instructions carefully, since the exact steps vary slightly by manufacturer. Keep your phone charged and connected during setup, because an interruption during authorisation can leave Shizuku in a half-started state that needs a clean restart.
Before building the hotspot macro, decide exactly when the hotspot should turn on and off. Common designs include turning it on when a specific Bluetooth device, such as a laptop or car system, connects, turning it on at a scheduled time, or turning it on from a home-screen shortcut. Equally important is the off condition: the hotspot should turn off when the device disconnects, after a period of inactivity, or on a schedule, because a hotspot left running drains the battery and shares your connection longer than necessary. Write both conditions down, and check your mobile plan for tethering terms, since some carriers restrict or charge differently for hotspot use. Finally, back up your MacroDroid macros before making system-level changes.
Step-by-Step Setup
First, get Shizuku running. Open Shizuku, follow its guided start process, and authorise it using your chosen method, USB or wireless debugging, exactly as its instructions describe. When Shizuku reports that it is running, open MacroDroid and grant it the Shizuku-related permission it requests, so MacroDroid appears in Shizuku’s authorised apps list. Confirm that authorisation in Shizuku itself; an app that is not listed there cannot use the channel, no matter what MacroDroid’s settings say. Restart both apps once after authorisation, so the connection is established cleanly, and verify in Shizuku that MacroDroid remains authorised after the restart.
Next, build the hotspot macro in MacroDroid. Name it clearly, such as Hotspot for Laptop, and add your chosen trigger, for example Bluetooth device connected to your laptop, or a shortcut trigger for manual control. For the action, use the hotspot control action that MacroDroid exposes when Shizuku support is available, and select the Fake UI option if it is offered for your device. The Fake UI approach works by driving the hotspot control through the system’s interface layer, which is why it succeeds where a direct toggle is blocked. Test the action on its own before adding anything else, and confirm in Shizuku’s log, if available, that MacroDroid used the authorised channel.
Then add the off macro, which is just as important as the on macro. Its trigger should mirror your off condition, such as Bluetooth device disconnected, and its action should turn the hotspot off through the same Shizuku and Fake UI path. Add a short delay before turning off, perhaps two to five minutes, so a brief disconnection does not kill the hotspot while you are still working. Add a notification to both macros during testing, so you can see exactly when the hotspot changes state, and add a variable that records whether the hotspot is supposed to be on, so a second macro can check and correct it. Save both macros, enable them, and keep logging switched on.
Testing and Verification
Test the hotspot automation end to end with the real device you intend to share with. Trigger the on macro, wait for the confirmation notification, and check on the receiving device that the hotspot network appears and that you can connect and browse. Then trigger the off condition, wait for the delay to expire, and confirm the hotspot disappears and the receiving device disconnects cleanly. Check MacroDroid’s log after each stage, and check Shizuku’s status to confirm it remained running throughout. If Shizuku stops, for example after a reboot, the hotspot macro will fail until Shizuku is restarted, so note that dependency in your testing.
Test the failure modes as well. Restart the phone and confirm whether Shizuku restarts automatically or needs manual re-authorisation on your device; this varies, and knowing the answer determines whether your hotspot automation is truly hands-free or needs a quick start step after reboot. Test with the phone locked, with battery saver on, and with mobile data already off, to see how the macro behaves when its preconditions are not met. If the macro tries to enable a hotspot without mobile data, it should fail gracefully with a notification, not loop or crash. Test the delay logic by disconnecting briefly and reconnecting, confirming the hotspot stays on through a short dropout. Only remove the test notifications after a full day of successful real use.
Troubleshooting
If the hotspot never turns on, check the chain in order: Shizuku is running, MacroDroid is authorised in Shizuku, the macro is enabled, the trigger fired according to the log, and the Fake UI option is selected where offered. A break at any link produces the same symptom, so checking in order avoids guessing. If Shizuku reports that it is not running, restart it using its own start process; do not reinstall it as a first step, since re-authorisation is usually sufficient. If MacroDroid is not listed in Shizuku’s authorised apps, revoke and re-grant the permission, then restart both apps.
If the hotspot turns on but never turns off, the off macro is the problem: check its trigger, its delay, and whether it is enabled. A common mistake is setting the off trigger to a device name that differs slightly from the on trigger’s name, so the disconnect event never matches. If the hotspot toggles repeatedly, a flapping Bluetooth connection is usually responsible; lengthen the off delay and add a cooldown. If the Fake UI option does not appear on your device, your MacroDroid version or device software may expose hotspot control differently; check for a MacroDroid update and consult its current documentation for your device, rather than forcing an option that is not offered. If a carrier restriction blocks tethering entirely, no automation method will override it, and you will need to check your plan terms.
Tips for Safe Hotspot Automation
Always pair an automatic on with an automatic off. A hotspot that turns itself on but relies on you remembering to turn it off will drain the battery and expose your connection unnecessarily. Set a maximum runtime as a safety net, for example turning the hotspot off after two hours regardless of other conditions, so even a missed disconnect event cannot leave it running all day. Use a distinctive hotspot name and a strong password, and never automate a hotspot with no password, since automation makes it easy to forget that the network is open.
Keep Shizuku’s authorisation minimal. Authorise only the apps that genuinely need it, review the authorised list occasionally, and remove apps you no longer use. After major Android updates, re-check that Shizuku still starts and that MacroDroid remains authorised, because update processes sometimes reset developer or debugging settings. Finally, document your hotspot macros clearly, including the trigger, the off condition, and the delay, so that a future change to your laptop or your routine does not leave a forgotten macro turning the hotspot on unexpectedly.
Frequently Asked Questions
Do I need root access to automate hotspot on Android 16?
No. The Shizuku method described here does not require root. It uses a user-authorised channel that Shizuku provides, with MacroDroid listed as an authorised app, while the phone’s normal security protections remain in place.
What does the Fake UI option actually do?
It drives the hotspot control through the system’s interface layer rather than calling a direct toggle that Android 16 blocks for ordinary apps. That is why it can succeed where a plain hotspot action fails, on devices where MacroDroid offers it.
Will Shizuku keep running after I restart my phone?
That depends on your device and how Shizuku was started. Some setups restart automatically, while others need a quick manual start after reboot. Test this on your own phone and plan your hotspot macro around the actual behaviour.
Why does my hotspot turn on but my laptop cannot connect?
Check that mobile data is on, that your plan allows tethering, that the hotspot password matches, and that the hotspot is not set to turn off immediately. A macro that enables the hotspot and then immediately disables it, through a conflicting off macro, produces exactly this symptom.
Is it safe to grant Shizuku access to MacroDroid?
Shizuku is a widely used tool for this purpose, but you should still install it only from its official source, authorise only apps you trust, and review the authorised list periodically. Never grant this access to an unfamiliar app.


