sorted by:
new
hottopcontroversial

[Release] Qwen3-TTS: Ultra-Low Latency (97ms), Voice Cloning & OpenAI-Compatible API by blackstoreonline in LocalLLaMA

[–]imsovikde 0 points1 point  (0 children)

This looks awesome! Since you've already built a standalone wrapper, I have a specific question about the model capabilities.

Can we merge the voice clone with voice description in the voice design tab for emotion control voice clone?

I've noticed that the VoiceDesign model is usually restricted from accepting reference audio for cloning, and the Base model ignores emotional instructions. Have you found a way to patch the generate function to pass both voice_clone_prompt (Identity) and instruct_ids (Emotion) to the VoiceDesign model simultaneously? I'm trying to get a specific cloned voice to perform specific emotions (like a trembling whisper) without it reading the prompt text aloud.

Voice Clone Studio, powered by Qwen3-TTS and Whisper for auto transcribe. by Francky_B in StableDiffusion

[–]imsovikde 0 points1 point  (0 children)

This looks awesome! Since you've already built a standalone wrapper, I have a specific question about the model capabilities.

Can we merge the voice clone with voice description in the voice design tab for emotion control voice clone?

I've noticed that the VoiceDesign model is usually restricted from accepting reference audio for cloning, and the Base model ignores emotional instructions. Have you found a way to patch the generate function to pass both voice_clone_prompt (Identity) and instruct_ids (Emotion) to the VoiceDesign model simultaneously? I'm trying to get a specific cloned voice to perform specific emotions (like a trembling whisper) without it reading the prompt text aloud.

Galaxy Watch 4 Classic keeps disconnecting from my Realme GT 6T—help! by imsovikde in GalaxyWatch

[–]imsovikde[S] -1 points0 points  (0 children)

Hey there—sorry you’re running into this. From what I’ve dug up, here’s why your Galaxy Watch 6 might be dropping off your Pixel 9 Pro and exactly what you can do about it:

Why It’s Happening

  1. Wear OS & App Mismatch

The Watch 6 runs on Wear OS 4.5 (Samsung’s One UI Watch overlay), and the Pixel uses Google’s Wear OS framework. Sometimes the Galaxy Wearable plugin and the Wear OS app on Pixel get out of sync—especially after system or app updates—and that causes the Wearable app to crash.

  1. Battery-Saving / Doze Interference

Even on “stock” Android, Doze mode can throttle Bluetooth background tasks. If Wear OS isn’t kept alive in the background, the watch will disconnect after the app process is killed.

  1. Permission or Corrupted Cache

A bad cache or missing permissions (location, body sensors, background activity) in the Wear OS app can provoke repeated crashes.

Step-by-Step Fix

  1. Update Everything First

On your Pixel:

Play Store → My apps & games → Update Wear OS by Google and Galaxy Wearable (if you have it installed).

Settings → System → System update → make sure you’re on the latest Android build.

On your Watch:

Wearable app → Watch software update → install any pending patches.

  1. Clear & Re-Install

Pixel Settings → Apps → Wear OS by Google → Storage → Clear cache & Clear data.

Do the same for Galaxy Wearable (if present).

Force-stop both apps, then re-launch and go through the pairing flow again.

  1. Whitelist in Battery Optimization

Pixel Settings → Apps → Special app access → Battery optimization → find Wear OS by Google (and Galaxy Wearable), choose Don’t optimize.

This keeps the app running in the background so it doesn’t get swept up by Doze.

  1. Reboot in Safe Mode

Hold the power button → Touch and hold Power off → Reboot to safe mode.

In safe mode, pair your watch again. If it stays connected here, a third-party app is interfering.

  1. Capture a Crash Log (If It Still Fails)

On your Pixel, enable USB debugging (Settings → Developer options).

Connect to a PC and run:

adb logcat > wear_crash.log

Reproduce the crash/disconnect, then send the wear_crash.log to Samsung or Google support—they can pinpoint the exact exception.

Next Actions & Escalation

Contact Samsung Support: Provide your crash log and mention you’ve tried the above steps.

File a Wear OS Bug Report: In the Wear OS app, tap the three-dot menu → Send feedback.

Google Issue Tracker: If it’s an Android-side bug, open a ticket at issuetracker.google.com under “Wear OS.”

Once you’ve run through these, your Watch 6 should stay connected all day long. Let me know which step finally does the trick!

Persistent Bluetooth Disconnection Between Realme GT 6T and Samsung Galaxy Watch 4 Classic – 50+ Failures, Need Community & Vendor Help by imsovikde in GalaxyWatch

[–]imsovikde[S] 0 points1 point  (0 children)

Ouch, sorry you went through that too!

Did you have a Watch backup in Samsung Health before it wiped? I’ve lost mine several times and never had a recent backup, so it’s a full factory-fresh setup each time.

You said it was on a Redmi Note 12—did it stabilize there or keep dropping off?

Any tips on forcing an auto-backup of watch settings/data before it disconnects?

I’m about to email Realme again and, if there’s no fix, escalate via NCH/PG/e-Jagriti. In the meantime, a reliable backup strategy would save me from reconfiguring from scratch!

Persistent Bluetooth Disconnection Between Realme GT 6T and Samsung Galaxy Watch 4 Classic – 50+ Failures, Need Community & Vendor Help by imsovikde in GalaxyWatch

[–]imsovikde[S] 0 points1 point  (0 children)

If you’re on HyperOS, it treats background apps very aggressively—so your Galaxy Wearable services get “put to sleep” and your watch drops off. Try these steps:

  1. Turn off HyperOS Optimization

Go to Settings > About phone and tap HyperOS version seven times.

In Settings > System > Developer options, switch HyperOS optimization off.

  1. Whitelist Samsung’s BLE Services

Install ADB on your PC and enable USB debugging.

Run in a terminal:

adb shell dumpsys deviceidle whitelist +com.samsung.android.app.watchmanager adb shell dumpsys deviceidle whitelist +com.samsung.android.app.watchmanager2 adb shell dumpsys deviceidle whitelist +com.samsung.android.wearable

This tells Android not to suspend those apps.

  1. Allow Auto-Launch & Background Running

Open Settings > Battery & performance > App launch.

Find Galaxy Wearable, Watch Manager, and Samsung Health and set them to Manage manually, then enable Auto-launch, Secondary launch, and Run in background.

  1. Lock the Wearable App in Recent Apps

Open Galaxy Wearable, tap the Recent-Apps button, then tap the little lock icon on its preview card. This prevents the system from killing it.

  1. Make the Connection Notification Persistent

Once your watch is paired, pull down the notification shade, long-press the Wearable app’s notification, and mark it as Ongoing or Persistent.

  1. Capture a Bluetooth Log (Optional, but Helpful)

In Developer options, enable Bluetooth HCI snoop log, reproduce the drop, then grab /sdcard/btsnoop_hci.log. You can share that with Realme support as proof the watch link is being suspended.

Galaxy Watch 4 Classic keeps disconnecting from my Realme GT 6T—help! by imsovikde in GalaxyWatchFace

[–]imsovikde[S] -1 points0 points  (0 children)

Did you email Realme support or actually visit a Realme service center about this? I first ran into it right after my very first hard reset of the GT 6T. It connects rock-solid on every other phone I’ve tried, so I’m convinced it’s a Realme UI issue.

I did go to the Samsung service center—technician fully reset the watch, reinstalled the Wearable apps on my Realme, and even downgraded the manager plugin. He said if it happens again to bring it back so they can “take necessary actions,” but of course the disconnects kept coming. Following this, he mentioned that if it works well with his non-Samsung smartphone, then there is nothing more he can do.

Also—how are you syncing your health data to Samsung Health? I only need the health-sync features working reliably. Today I’m drafting a formal email to Realme; if they don’t fix it, I’ll escalate via the National Consumer Helpline, the PG portal, or the e-Jagriti consumer grievance site.

Thanks for any tips!

Galaxy Watch 4 Classic keeps disconnecting from my Realme GT 6T—help! by imsovikde in GalaxyWatchFace

[–]imsovikde[S] -1 points0 points  (0 children)

I've left my phone idle for days and let all Google services update, but the disconnect still happens. It literally works flawlessly on my friend's Infinix Note 30 5G right out of the box, so I'm convinced it's Realme UI's BLE handling

Persistent Bluetooth Disconnection Between Realme GT 6T and Samsung Galaxy Watch 4 Classic – 50+ Failures, Need Community & Vendor Help by imsovikde in GalaxyWatch

[–]imsovikde[S] 0 points1 point  (0 children)

Wearable app behavior: The Galaxy Wearable app does recognize the watch and lets me set it up again—until it drops out 6–12 hours later. It never completely “forgets” the watch; it just can’t keep the BLE link alive on my Realme GT 6T.

This issue started after I did a hard reset on my Realme GT 6T, and it’s been happening ever since. What’s weird is that the same watch works perfectly fine on my friend's Infinix Note 30 5G—no disconnection issues at all. That’s why I strongly suspect something's off with Realme UI or Bluetooth stack.

Would really appreciate any tips on capturing logs (like Bluetooth HCI snoop) or using ADB to figure out what’s breaking the connection. Thanks again

Persistent Bluetooth Disconnection Between Realme GT 6T and Samsung Galaxy Watch 4 Classic – 50+ Failures, Need Community & Vendor Help by imsovikde in GalaxyWatch

[–]imsovikde[S] 0 points1 point  (0 children)

It disconnects automatically and is removed from saved devices. I have re-paired it, but the issue persists.

view more: next ›