To make a macro with TG Macro, open the Android app, grant only the permissions it needs, record a short sequence of screen actions, then replay it and adjust the timing until it behaves correctly. TG Macro is generally used as a touch-automation tool; this guide assumes you mean that Android app, not a Telegram bot or a macro feature inside another program. App versions and Android settings differ, so treat the labels below as a guide and check each action on your own device before relying on it.
What You’ll Need
- An Android phone or tablet that can install the TG Macro version you intend to use. Check the developer and source before installing; do not download an APK from an untrusted mirror.
- The app or screen you want to automate, plus a simple, repeatable task to record. Start with a harmless test rather than a purchase, message, or other action with consequences.
- Permission to use the app’s required Android features. Depending on the version, these may include Accessibility access or permission to display controls over other apps.
- A few minutes to test the recording. Macros often depend on screen size, orientation, app state, and timing.
Step-by-Step
- Choose a small, repeatable task. Decide exactly what you want the macro to do and where it should start and stop. For instance, you might want to open a particular screen, tap a control, wait for a result, and return to the starting screen. Write the sequence down first. A clear beginning and ending make it easier to record, test, and stop safely. Avoid choosing an action that sends a message, deletes information, spends money, changes account settings, or could cause harm if it repeats.
- Install and inspect TG Macro. Get the app from a source you trust and confirm that its name and developer match the listing you intended to use. Open it and review any permission explanations before accepting them. If you cannot confirm the source, or the requested access does not make sense for touch automation, do not grant it. An app with Accessibility access may be able to observe or control aspects of your screen, so treat that permission as sensitive.
- Grant only the permissions the app requires. Follow TG Macro’s in-app prompt where possible. Android commonly puts Accessibility services under Settings > Accessibility, then a section such as Installed apps or Downloaded apps; the wording varies by Android version and phone maker. If the app needs an on-screen floating control, Android may ask for display-over-other-apps access, often found under Settings > Apps > Special app access. Read the confirmation screen, enable access only for TG Macro if appropriate, then return to the app. Do not enable unrelated permissions just to get past a prompt.
- Set up the target screen. Open the app or page you want to automate and put it in the exact starting state for the recording. Close pop-ups, dismiss notifications, and make sure the relevant controls are visible. Keep the device orientation and display scaling consistent with how you intend to replay the macro. A tap recorded at one screen position may hit a different control if the app layout changes or the screen rotates.
- Start a new recording in TG Macro. Use the app’s recording or new-macro control; its wording and placement can differ by version. If TG Macro provides a floating control, place it where it will not cover a button you need to tap. Start recording only after the target app is ready. Perform the actions once, in order, at a steady pace. Include a pause after actions that need time to load, and avoid tapping extra areas while the recorder is active.
- Stop the recording at the right point. Use TG Macro’s stop control as soon as the intended sequence is complete. Check the saved recording or its action list, if your version shows one. Remove accidental taps and confirm the final action does not leave the target app in a state that would make the next replay behave differently. Give the macro a clear name that describes its task, such as Open report screen, rather than a vague label like Test 2.
- Adjust timing and replay options. If the app offers a delay or interval setting, use it to give screens enough time to load before the next tap. Begin with a conservative pause, then shorten it only after several reliable test runs. If repeat or loop options are available, leave them off for the first replay. Check any repeat count, stop condition, or playback speed setting before enabling it; a loop can continue making taps after you have stopped watching.
- Test once while watching closely. Return the target app to the exact starting state, run the macro once, and follow every tap on screen. Be ready to stop playback if it selects the wrong item or the screen changes unexpectedly. Confirm that the macro reached the intended result and did not trigger an unintended action. A successful recording is not necessarily a reliable macro: replay it several times from a fresh starting state to check consistency.
- Use repeat playback cautiously. Only use a loop or repeat feature after single runs work consistently and you understand how to stop it. Choose a low repeat count if the app offers one, keep the device in view, and avoid unattended playback. Do not use a macro to evade an app’s safeguards, violate a game’s or service’s rules, or automate actions that require a person’s judgment. If the target app updates or its layout changes, pause use and record or test the sequence again.
- Disable access when you are finished. Stop the macro, close or pause TG Macro, and turn off any permission you no longer need. You can usually manage Accessibility access from Android’s Accessibility settings and overlay access from the app’s special-access settings. Exact routes vary. Keeping permissions limited reduces the chance that an accidental tap or another app interaction triggers automation later.
Common Mistakes
Recording before the target screen is ready: A notification, loading screen, or dialog can change what your taps do. Clear interruptions first and begin from the same screen each time.
Making the first macro too long: Every extra tap adds another chance for a layout change or delay to derail playback. Build and test a short sequence first. If a task has distinct stages, record and test them separately before combining them, if TG Macro supports editing or separate recordings.
Using delays that are too short: A tap can occur before a page or control is ready, especially on a slow connection or busy device. Add a longer pause after transitions and test under ordinary conditions, not only when everything loads quickly.
Ignoring screen changes: Screen rotation, display scaling, pop-ups, keyboard visibility, and app updates can move controls. Keep the device setup consistent and recheck the macro whenever the target app changes.
Turning on repeat too soon: A macro that is slightly wrong can repeat the same mistake. Test one run first, keep repeat disabled until the sequence is reliable, and know the stop control before starting.
Granting permissions without checking them: Accessibility and overlay permissions can have broad effects. Review what Android says the permission allows, use only the official app source you trust, and revoke access if the feature is no longer needed.
Tips
- Make a brief test macro with one or two taps before recording a longer task. This helps confirm that the recorder, overlay, and playback work on your device.
- Keep a consistent starting state: same app screen, orientation, and visible controls. If the task starts from a different screen, the macro may still run but act on the wrong controls.
- Use deliberate pauses around page loads, animations, and dialogs. A pause is often more dependable than trying to tap quickly through a changing interface.
- Give recordings descriptive names and keep only versions you understand. If you revise a macro, test the revised version rather than assuming the earlier result still applies.
- Keep your finger or attention ready to stop playback during early tests. Do not leave a newly created macro running while you walk away.
- Use TG Macro only where automation is permitted. Some games, workplace tools, and online services restrict automated input, and accessibility tools should not be used to get around those rules.
- After an Android update, app update, or change of display settings, run a supervised test. Permission settings or tap positions may behave differently after a change.
Troubleshooting
TG Macro will not record or replay: Reopen the app and check its permission status in Android Settings. If Accessibility access is required, verify that TG Macro’s service is enabled; if a floating control is required, check its overlay access. The exact setting names depend on your device. Restarting TG Macro or the phone can help after a permission change, but do not grant additional access unless the app explains why it is needed.
The floating control is missing: Check whether TG Macro is open and whether Android permits it to display over other apps. Some battery-management settings may also restrict background activity. If you change a setting, test the control again and turn off any permission you do not actually need.
Playback taps the wrong place: Return to the screen size, orientation, and app state used during recording. Check for display scaling changes, a keyboard, a notification banner, or a layout update. If the position still differs, record the sequence again with the current layout instead of repeatedly trying to compensate with random settings.
Actions happen too quickly: Increase the delay between actions or add a pause around slow transitions, if your version supports timing adjustments. Test the macro again from the beginning. Network speed and device workload can vary, so a delay that worked once may not be sufficient every time.
The macro stops partway through: Check whether the target app displayed a confirmation, permission prompt, login screen, or error. Automation generally cannot safely guess what to do when a new screen appears. Handle the prompt yourself, restore the normal starting state, and then test again. Also check that battery restrictions are not interrupting TG Macro during playback.
You cannot stop a repeating macro: Use the stop control shown by TG Macro or its floating control. If the device is not responding, use Android’s app switcher to leave the target app or force-stop TG Macro from Settings > Apps. Afterward, disable the repeat setting and confirm playback is stopped before reopening the target app. Never start a loop unless you know how to interrupt it.
Frequently Asked Questions
Is TG Macro a Telegram feature?
No. In this guide, TG Macro means an Android touch-automation app. It is separate from Telegram and does not create Telegram chat macros. If you meant automation inside Telegram, the steps and risks are different.
Does TG Macro work on every Android phone?
Not necessarily. Compatibility depends on the TG Macro release, Android version, phone manufacturer, and the permissions available on the device. Check the app’s current requirements and test a short recording before relying on it.
Why does TG Macro ask for Accessibility access?
Touch-automation apps may use an Accessibility service to interact with screen controls. Android treats this as sensitive access because it can enable broad interaction with the device. Read the system warning, verify the app source, and enable it only if you are comfortable with the access it grants.
Can I use TG Macro while the screen is off?
Do not assume so. Screen-off behavior depends on the app, Android restrictions, and the type of actions being recorded. Many screen-based macros need the display awake and the target app visible. Test the exact setup under supervision and do not rely on it for a task where an unnoticed failure would matter.
Can a TG Macro recording be shared with another phone?
That depends on whether your version offers export or import, and a shared recording may not fit another device’s screen or app layout. Check the app’s own options and test an imported macro carefully. Never run a file from an unknown source without understanding what actions it contains.
Is it safe to automate a game or online service?
It depends on that service’s rules and the actions involved. Some services prohibit macros or treat automated input as unfair use. Review the relevant terms and avoid automation that bypasses protections, makes consequential decisions, or repeats actions without supervision.
Related
- Excel: Add Superscript to the Ribbon Button and Use It
- Excel Superscript Button: Where to Find It and Add It
- Excel Add Button to Refresh Power Query Data Easily
Try it: the Column Letter to Number: aA is 27, XFD is 16,384. Converts both ways.
More in VBA & macros
- Excel Macro Goal Seek: Automate a Target-Value SearchAn Excel Goal Seek macro uses VBA’s Range.GoalSeek method to make a formula cell reach a target by…
- VBA Dictionary SumIf: How to Group and Sum Data in ExcelTo perform a SUMIF-style total in VBA, use a Scripting.Dictionary: make each category a key and add each…
- Dim VBA String: How to Declare and Use Text VariablesIn VBA, declare a text variable with Dim variableName As String, such as Dim customerName As String. The…
- Excel VBA AutoFilter: Filter Rows by a Specific ValueTo filter a range by one exact value with Excel VBA, call AutoFilter on the range that includes…
- VBA Find: Check Whether a String Contains a SubstringIn VBA, use InStr to check whether one string contains another: if the function returns a number greater…
- Excel UserForm: Change Font Size at Design Time or in VBATo change an Excel VBA UserForm’s font size, select the form or a control in the Visual Basic…
Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources
Spotted an error in this guide? Let us know.