StakeClaimer App — Full Setup Guide
Install once, log in once, press "Run in background" — and the claimer works for you 24/7 while you use Chrome, Firefox, or any browser you like. The claim browser stays hidden.
Android 7.0+ · arm64 · 164 MB · v1.3.2
Requirements
Before you start
Android 7.0 (Nougat) or newer — any phone from the last eight years.
arm64 processor — every modern phone.
An active StakeClaimer subscription — codes come from the same relay as the PC script. The same username works on both.
~164 MB free space — the app ships with a real Firefox engine inside.
The app is not on the Play Store (auto-claiming tools don't fit store policies) — you install the APK directly from this page.
Step by step
Install & first run
1
Download the APK
Tap the green button above — StakeClaimer.apk. Your browser will warn you about unknown sources; that's normal for any APK.
2
Allow installs from your browser
Android asks for permission to install unknown apps. Allow it for your browser or Files app (the exact dialog differs per Android version — the key is tapping Allow from this source).
3
Install & open
Tap the downloaded file, confirm, and open StakeClaimer. On first launch the app asks for two permissions — grant both:
• Notifications — the "claiming in background" status lives here.
• Battery optimization exemption — this is the one that lets it claim 24/7. Without it, Android may throttle the app while locked.
Login
Log in once — two ways
You never see the Stake website. The app keeps the claim browser hidden behind your dashboard — you only ever see the StakeClaimer screen. Logging in happens through a quick overlay, then it disappears again.
A
Sign in with Google (recommended)
Tap 🔐 Sign in with Google on the dashboard. The app invisibly opens the login behind the scenes and pops up only the Google login window — you'll never see the Stake site. Choose your Google account, sign in, and the app captures the session automatically: "Session captured — claiming in the background", and you're back on the dashboard. Done.
B
Import a session key (works without a PC)
You can get a session key from your PC claimer's
🔑 Session setting — or straight from
your phone's own browser with the one-tap bookmark on the
session key page. Paste it into the app and you're in instantly.
The dashboard
Reading your stats
Once logged in, the login card is replaced by the live dashboard. Every number is read straight from the claim engine — it refreshes every couple of seconds.
● Operational
Top banner — green = claiming, amber = no subscription, red = banned
Drops today
How many of Stake's 10 daily code slots you've used (resets at UTC midnight)
Codes claimed
Total bonus codes claimed by the engine
Reloads
Reload bonuses claimed (hourly/daily faucet)
Est. earned
Running total in USD from claimed drops and reloads
Tokens ready
Pre-minted Cloudflare tokens waiting — the claimer's ammunition
Sub expires
Your subscription end date from the relay
Recent claims
The latest drops with code, value, and source (relay / socket / catch-up)
Background mode
Run in background — use any browser
1
Tap ▶ Run in background
The app sends itself to the background and a persistent notification appears: "StakeClaimer is claiming in the background." The claim engine keeps running with the screen off, the phone locked, or other apps on top.
2
Browse normally
Open Chrome, Firefox, Samsung Internet — whatever you like — and use Stake.com exactly as usual. The claimer runs in its own hidden browser, completely separate from yours. They never interfere.
3
Come back any time
Tap the notification to return to the dashboard and check your stats. The app never needs to be reopened for claiming — only if you want to look.
Don't swipe the app away from recent apps. Locking the screen and switching apps is 100% safe — but swiping it away kills the claimer. If you do swipe it, just open it again and press ▶ Run in background.
👁 Stake — peeks at the hidden claim browser (the actual Stake page). Tap ⟳ or the back button to hide it again. Useful if you ever want to see the site's own UI inside the app.
⋮ Menu — Screen stay-on, show over lock screen, reload, anchor toggle, and session import.
Claimer pill — the engine's floating pill on the Stake page can be hidden from the ⋮ menu if it ever sits over a game control.
Auto-updates — the claim engine is fetched from the server on every launch, so claimer updates reach your phone without an app update. App updates are announced on this page.
Troubleshooting
When something's off
Status chip says "no subscription"
Your Stake username has no active plan on the relay. Subscribe via the Telegram bot with the same username — activation is instant.
Google login gets stuck
Close and reopen the app, tap 🔐 Sign in with Google again. If it still hangs, use the PC import path instead — it always works.
Claims stopped after an Android update
Android sometimes revokes the battery exemption. Open ⋮ → check the app in your battery settings → set it to Unrestricted, then press ▶ Run in background again.
The pill blocks a game button
Open ⋮ → Claimer pill: OFF. Or hold and drag the pill somewhere else on the Stake page.
I see a Cloudflare "checking your browser" page in peek mode
That's the hidden claim browser passing Cloudflare's check on your behalf — leave it be; the dashboard is where you live. It usually resolves in seconds and never affects your own browser.
How do I uninstall?
Standard Android uninstall — remove the app and the background service stops. Your subscription lives on the server, not in the app, so you can reinstall any time.
Is it the same as the PC userscript?
Same claim engine, byte for byte, fetched from the server. The app wraps it in a real Firefox engine so it runs natively on Android.
Why isn't it on the Play Store?
Auto-claiming tools don't fit store policies. You install the APK directly — updates are announced on this page.
Do I still need a subscription?
Yes — code drops come from the same relay. Your plan works on both the app and the PC script simultaneously.
Does it drain my battery?
The hidden claim browser stops rendering while you're on the dashboard, and the wake lock keeps the CPU awake for claiming. Most phones lose only a few percent overnight.
