🔧 Device & Software Details Phone: Realme GT 6T, Realme UI (Android 15), Security Patch May 2025
Watch: Samsung Galaxy Watch 4 Classic, Tizen-based wearable OS (latest update)
Apps: Galaxy Wearable & Galaxy Watch Manager (latest Play Store versions)
🕒 Problem Overview Since late February 2025, any time I pair my Galaxy Watch 4 Classic to my Realme GT 6T—whether immediately after a factory reset or days later—the watch will automatically un‑pair after 6–12 hours. My health data (steps, sleep, heart rate) vanishes, and I’m forced through the full setup again. I’ve now endured 50+ of these disconnect cycles over four months.
📜 Chronology & Key Facts March 2025: First hard reset of GT 6T triggered disconnections.
March–June 2025:
Cleared cache/data on Wearable apps; reset network settings; whitelisted apps against battery optimization; tested in Safe Mode—no effect.
Samsung service center confirmed the watch hardware & firmware are sound. Pairing with an Infinix Note 30 5G remains stable, ruling out watch-side faults.
June 2025: Repeated resets of both devices still lead to the same drop after hours of normal operation.
🔍 Troubleshooting Steps Already Tried Full factory reset of Realme GT 6T (twice)
Clearing cache & data for Galaxy Wearable & Watch Manager
Disabling all aggressive battery‑saving / “deep sleep” features
Whitelisting Wearable apps in Realme UI’s auto‑launch settings
Installing older versions of Watch Manager plugin
Testing in Safe Mode (no third‑party apps)
Resetting network settings & Bluetooth pairing list
Updating both phone and watch to latest firmware
⚙️ Likely Root Causes Realme UI’s Aggressive Background Management: Suspends BLE‑critical apps, dropping the connection after a few hours.
Bluetooth Stack Incompatibility: Samsung’s BLE implementation may conflict with Realme’s firmware/drivers.
📝 What I’m Asking From the Community & Vendors Realme Engineers: Please release a firmware patch/fix for BLE background stability and app‑suspension conflicts.
Samsung Community & Devs: Any known workarounds or logs I should capture to help prove this is a phone‑side issue?
Reddit & Quora Members: Have you faced similar BLE drops on Realme phones? Any hidden settings, custom scripts, or ADB tweaks to keep the watch alive?
🔜 Next Steps (if unresolved) If this isn’t fixed by July 1, 2025, I’ll be:
Filing formal grievances with the National Consumer Helpline (NCH) & e-Jagriti
Escalating via consumer‑rights portals (PG & NCH)
Sharing my documented experience on broader tech blogs
🙏 How You Can Help Realme Users: Confirm if you see the same on any Realme device + Galaxy Watch.
Developers: Advice on log‑capture (e.g., Bluetooth HCI snooper) or hidden debug flags.
Moderators / Community Managers: Please escalate to Realme’s firmware team or Samsung’s wearable support.
Thank you all in advance—this community has solved countless device puzzles, and I hope together we can get my flagship phone and watch talking reliably again!
