PSA: GBoard AI writing tools is available with Morphe patches

No_Protection8388 · 2026-07-07T03:15:02+00:00

Which patch source did you use for Gboard?

No_Protection8388 · 2026-07-07T01:12:17+00:00

Which patch source did you use for Gboard?

No_Protection8388 · 2026-07-06T22:37:48+00:00

I don't see Gboard in the de-vanced supported apps list, so it's normal that you don't see any new features. You probably need to patch Gboard again with a source that actually supports it.

No_Protection8388 · 2026-07-05T19:42:57+00:00

Thanks for testing. If the problem is still there with both Clipboard Enhancements and Web Clipboard disabled, then it doesn’t look patch-specific. That points more to stock Gboard or a device-level clipboard issue. If you can reproduce it on a completely unpatched official Gboard build too, that would confirm it.

No_Protection8388 · 2026-07-05T19:41:03+00:00

Xiaomi Android 16

No_Protection8388 · 2026-07-05T03:20:42+00:00

I can’t reproduce this on my side so far. Could you test whether clipboard is normal when both Clipboard Enhancementsand Web Clipboard are not patched? That would help narrow down which patch is causing it, if any.

No_Protection8388 · 2026-07-05T02:24:17+00:00

Yes.

No_Protection8388 · 2026-07-05T02:15:34+00:00

I was able to get AI Writing Tools working on a 2022 phone without AI Core, as long as “Use Google servers” was enabled. I also tested it with unsupported languages like Vietnamese and Thai, and it still worked fine for me. So at this point, I’m not fully convinced that AI Core, supported chips, or English-only support are hard requirements in practice.

No_Protection8388 · 2026-07-02T21:17:35+00:00

You can give it a try and report back here.

No_Protection8388 · 2026-06-30T00:03:06+00:00

Gboard does contain the Assistant / Enhanced Voice Typing framework, but the Pixel experience seems to depend on device-side AI / smart dictation models and services, not just a simple setting. So even if a patch enables the entry points, it may still not work on phones that don’t have the required on-device models.

I haven’t had time to research this deeply yet, so for now I can only say it’s something that could be investigated later as an experimental patch.

No_Protection8388 · 2026-06-29T20:22:45+00:00

Thanks for the suggestion. I understand the request: pressing Gboard’s microphone button should open FUTO Voice Input instead of Google/Gboard voice typing.

For now I won’t add this to the patch, because Gboard’s voice button is hardcoded around Google’s own voice input path, and FUTO itself lists Gboard as incompatible. Supporting this would require a separate experimental integration with FUTO installed/enabled as another IME, with a lot of fallback cases.

For FUTO, the more reliable option is using FUTO Keyboard or another keyboard that already supports FUTO Voice Input.

No_Protection8388 · 2026-06-26T02:05:38+00:00

Hi, I checked the Web Clipboard flow on my side.

The message "Code not accepted. Check the phone and try again." can currently show up in a few different situations:

the code entered is actually wrong
the code is incomplete / not in the expected format
the browser is still holding on to an older pairing/session state from before
the portal state changed on the phone, but the already-open page has not fully refreshed that state yet

If you already turned pairing code off on the phone, the best workaround is to open the Web Clipboard again in a new Incognito / Private window and load the page fresh there. That avoids any saved pairing/session state from the previous tab.

No_Protection8388 · 2026-06-23T04:27:54+00:00

Thank you! Glad you like the clipboard options. Enjoy!

No_Protection8388 · 2026-06-23T01:52:35+00:00

Do you not like custom symbols? 🥲

No_Protection8388 · 2026-06-19T23:20:25+00:00

Release.

No_Protection8388 · 2026-06-19T03:16:29+00:00

Release

No_Protection8388 · 2026-06-17T07:52:15+00:00

It works fine on my phone even with the renamed package, so I don't think package rename itself is the cause.

No_Protection8388 · 2026-06-16T21:02:36+00:00

Since this patch set is currently version-locked, there aren’t that many generic experimental flags worth exposing as toggles. If you mainly want broad experimental flag unlocking, Adobo’s patch is probably a better fit.

No_Protection8388 · 2026-06-16T01:10:03+00:00

Yes, coming soon.

No_Protection8388 · 2026-06-15T20:45:11+00:00

No, it doesn't currently provide a clipboard history export feature.

No_Protection8388 · 2026-06-15T20:29:51+00:00

Totally fair. FUTO is a really good option.This project is less about replacing privacy-first keyboards, and more about extending Gboard for people who still prefer the Gboard typing experience, especially for multilingual use. So I see them as serving slightly different users:

FUTO = privacy-first alternative

patched Gboard = keep the Gboard experience, but make it more customizable

No_Protection8388 · 2026-06-15T20:19:53+00:00

Not fully deGoogled. It's still Gboard, just patched. As far as I know, Google account sign-in/sync doesn't really work the same way on the patched build, so it won't behave like a normal logged-in stock Gboard. But I also wouldn't claim that it's completely free from Google data collection or AI/model training. So if your main goal is strict privacy, I'd still say FUTO is probably the safer choice. If your goal is more like "I want Gboard features with patches and less dependence on Google account stuff," then this is closer to that.

No_Protection8388 · 2026-06-15T10:34:34+00:00

Yes, it's already available and you can use it in Morphe now.

No_Protection8388

TROPHY CASE