Klick’r

Klick’r is an auto clicker: it taps and swipes on your screen for you, either as a fixed sequence or in response to what appears on screen. It was called Smart AutoClicker until version 3, in 2024, when its developer, Kevin Buzeau, rewrote it and renamed it Klick’r; the package name and the GitHub repository kept the old name. It is open source and actively developed: 4.0 came out in August 2026, followed by five bug-fix releases, and 4.1 in October.

Two kinds of scenarios

• Simple: “The regular auto clicker experience. Simply place clicks and gestures on the screen.” You set the positions, timing and how often it repeats.
• Smart: “Use image detection to create complex use cases.” Klick’r watches the screen and acts when a condition is met: a picture you captured appears (matched with OpenCV), or, since 4.0, a colour, a piece of text or a number, read with on-device text recognition.

Smart scenarios can also start from a timer, a counter or a system broadcast, and their actions go beyond taps: gestures, pauses, typing text into a field, sending an Android intent, showing a notification, pressing Back, Home or Recents, and turning other events on or off.

New in 4.1, from its release notes: the swipe became a gesture action that can change direction and pause along the way, with up to five fingers; existing swipes are converted and behave as before. A finger can also stay pressed while the scenario carries on, one at a time, with a choice of when to release it, and a counter can take the position of a detected condition. On Android 7, gestures can only move, without pauses, and can’t be held.

Two options are off by default: Anti-detection, which shifts each tap and pause by a small random amount, and keeping the screen on while it runs. A Quick Settings tile starts and stops it, and Volume Down stops a running scenario.

What it needs

• Accessibility service. Klick’r performs its gestures through it, listens for the Volume Down key and finds the text field for its type-text action. The code doesn’t use accessibility events for anything else; the handler for them is empty. The app’s own prompt says “No data is collected by Klick’r”.
• Display over other apps, for its floating controls.
• Screen capture, for Smart scenarios only, which Android confirms in its screen-recording dialog. Since Android 15 that dialog defaults to a single app; a setting asks for the entire screen, which “Might not work depending on your device”.
• On Android 13 and later, Android blocks accessibility access for apps installed from a file until you allow it: Settings › Apps › Klick’r › the menu › Allow restricted settings, as Google’s help describes. A user in the project’s issue tracker ran into this with the GitHub build.
• Phones that kill background apps aggressively can switch the accessibility service off; the app then shows help that links to dontkillmyapp.com. Pixel phones on Android 15 have a known touch-screen freeze with auto clickers, which an optional setting works around.

Some apps and games ignore taps made by software: an open issue reports exactly that. The developer has also noted that “Klick’r is starting to get detected in some apps”.

Why we host this build

Klick’r is published on GitHub, F-Droid and Google Play. We host the developer’s own current GitHub build, version 4.1.2. F-Droid had caught up to 4.1.1 by 25 October 2026, and that APK now includes the Latin detection and recognition model files, so the missing-model problem in its older 4.0.5 build is no longer a reason to avoid F-Droid. The two sources use different signatures: choose one and keep it for future updates.

The developer has also warned about copies, writing in 2024 that Klick’r “is only available here, on FDroid and Google PlayStore. If you have downloaded the application from any other sources, your phone is in huge security threat, as the application have complete visibility on your screen and can inject touch input as will.” Several closed-source copies have appeared on Google Play under other names. The file here is byte for byte the APK on the project’s GitHub release, signed by the developer, as the hash under More Information shows.

What goes online

Very little. The only network code in this build downloads extra text-recognition alphabets, such as Arabic, Chinese, Cyrillic or Japanese, from the project’s GitHub releases, and only when you tap to download one; Latin is built in. The downloads aren’t checked against a hash. There are no trackers. The Google Play version is different: it contains Google’s AdMob, Play Billing and Firebase Crashlytics.

About this file

• This is the developer’s GitHub release of 4.1.2, the universal APK of the F-Droid flavour (smartautoclicker-fDroid-universal-release.apk), signed by Kevin Buzeau. In this flavour Pro is unlocked and ads are off in the code. This bug-fix release automatically stops a recorded gesture one millisecond before Android’s one-minute limit and handles invalid gestures in simple scenarios without crashing; its other change refreshes Play purchases more aggressively, which does not affect this F-Droid-flavour build.
• It can’t update, or be updated by, F-Droid’s or Google Play’s Klick’r: they are signed with other keys. Export your scenarios before switching.
• The 53.5 MB file runs on Android 7.0 and later, on ARM and x86, 32- and 64-bit, and declares 7 permissions: the overlay, screen capture as a foreground service, notifications, keeping the screen on when you ask, and internet for the alphabet downloads.
• The code is under the GPL-3.0 or later. F-Droid still lists GPL-2.0-or-later, which only applied to the earliest versions. It bundles OpenCV (Apache-2.0), Tencent’s ncnn (BSD-3-Clause) and text-recognition models converted from PaddleOCR (Apache-2.0).
• The screenshots are the project’s own, from 2023, and show the interface before the version 3 redesign.

CPU types in this build: arm64-v8a (64-bit ARM, almost every phone since 2017); armeabi-v7a (32-bit ARM, older and budget phones); x86 (32-bit Intel, emulators); x86_64 (64-bit Intel, emulators and Chromebooks).

Recent releases on the project’s GitHub. We host and check only the newest one. Full changelog.