Tasbih uses Android’s Bluetooth Low Energy (BLE) APIs. Three checks fix nearly every pairing issue:

1. Bluetooth permission. Settings → Apps → Tasbih → Permissions → ensure Nearby devices (Android 12+) is allowed.
2. Bluetooth on, location off (Android 12+). The app declares neverForLocation, so it should not require Location. If your device still refuses to scan, toggle Bluetooth off and back on once.
3. Forget and re-pair. If the bead was bonded by another phone, hold the bead’s reset button for 5 seconds (or follow your specific bead’s reset procedure), then re-pair from inside Tasbih’s connect tray rather than from the system Bluetooth menu.

Building your own bead? The Maker Mode UUIDs are documented under Settings → Smart Tasbih → Maker Mode in the app.

Android OEMs are aggressive about killing background processes. If reminders go silent:

1. Disable battery optimisation for Tasbih (Settings → Apps → Tasbih → Battery → Unrestricted).
2. Allow exact alarms (Android 14+: Settings → Apps → Special access → Alarms & reminders → turn on for Tasbih).
3. On Xiaomi / Oppo / Realme / OnePlus, additionally enable Autostart for Tasbih in your device’s security/Battery menu.
4. Check Do Not Disturb. If DND is on, only sounds set to bypass DND will be heard. The reminder still appears as a banner.

Account sync uses a magic-link email (no passwords). If sign-in succeeds but your sessions and counts haven’t come back, two scenarios are common:

• You used a different email previously. Tasbih only restores data linked to the exact address you sign in with. Sign out, then sign in with the original address.
• Sync hasn’t completed yet. Pull to refresh on the History screen. The first sync after sign-in can take up to a minute on a slow connection.

If the data is still missing after a refresh, email officialtasbihapp@gmail.com with your account email and we’ll look it up directly.

Re-add it from your launcher: long-press an empty area → Widgets → Tasbih → drop it on the home screen. The configuration sheet that appears lets you pick which tiles render (count, prayer times, streak, etc.).

If the widget shows but the tap target doesn’t increment, ensure background data is allowed for Tasbih (Settings → Apps → Tasbih → Mobile data & Wi-Fi → Background data).

Tasbih is supported by Google AdMob (banner, interstitial, and opt-in rewarded). Ads can’t be turned off completely — that’s how the charity pool grows — but you can control how they’re personalised:

• EEA / UK / Switzerland / Brazil: in-app Settings → Privacy options opens the UMP consent flow. Choose between personalised, non-personalised, or limited ads at any time.
• All regions: Android → Settings → Privacy → Ads → reset or limit your advertising ID.
• Rewarded ads (“Watch an ad to add to charity”) are always opt-in. We never auto-play one.

Where the money goes is documented on our Charity Statement.

Two ways:

• In-app: Settings → Account → Delete account. The deletion is queued immediately and your row in our Supabase profiles table is removed within 24 hours; encrypted backups roll off after 30 days.
• By email: send a deletion request from the address you signed up with to officialtasbihapp+privacyrelated@gmail.com.

Deletion removes your synced sessions, custom dhikr, charity ledger, and preferences. Anonymous AdMob impression counts that fund the charity pool are not tied to your account, so they remain in the pool.

iOS is on the roadmap. Tasbih is built on Flutter so the lift is mostly the platform-specific bits (background notification, BLE permission strings, CallKit-style focus). Subscribe to release notes on Google Play or follow tasbihapp.com for the announcement.

Email officialtasbihapp@gmail.com with:

• Device model + Android version
• App version (Settings → About → Version)
• Steps to reproduce, ideally with a screen recording
• What you expected vs. what happened

JazakAllah khair for taking the time — bug reports go to the same inbox the founder reads daily.