How I Almost Lost My Sanity Trying to Force-Enable Gemini on Brunch

[Anonyoumss]

---

How I Almost Lost My Sanity Trying to Force-Enable Gemini on Brunch

So, there I was, staring at my Brunch setup running ChromeOS, determined to get the new native Gemini feature working. I knew the code was sitting in there somewhere, and as someone who loves tweaking systems, I wasn't about to let a missing button stop me.

Thus began a wild, multi-hour terminal rabbit hole with Gemini as my AI copilot. Here’s how it all went down.

Chapter 1: The Initial Gambit (And the Command That Wasn't)

I started by digging up my Local State file configuration data to see if the experimental "Glic" (the internal codename for the Gemini companion) flags were even enrolled. They were there, but the layout button was completely MIA.

I jumped into a crosh developer shell and asked Gemini for the magic command to inject the feature flags. It confidently spat out:

sudo local_dev_mode_flags --enable-features=Gatekeeper,Glic,GlicEntrypointVariations

I pasted it, hit enter, and...
sudo: local_dev_mode_flags: command not found

Classic. It gave me a placeholder script name instead of the actual ChromeOS command.

Chapter 2: Writing to System Files

After pointing out the error, we shifted gears to the real ChromeOS way: appending the flags directly to /etc/chrome_dev.conf.

We used cat to read the file, verified what was inside, and used a tee -a command to safely append the arguments to the bottom of the config. I even had to remount the root filesystem as writable (sudo mount -o remount,rw /) just in case Brunch locked me out.

We restarted the UI layout (sudo restart ui). The screen flickered, the desktop reloaded, and... still absolutely nothing. No Gemini icon anywhere.

Chapter 3: The Geolocation Goose Chase

We figured the flags were active, but ChromeOS's regional restrictions were overriding them. Gemini suggested we go into the massive, chaotic, encrypted user Preferences JSON file to manually swap the country codes to us.

I opened it up in nano. It was a complete nightmare of unreadable, minified system data logs, Bluetooth strings, and metrics. I tried to do a text selection marker (Alt + A) to copy the whole thing, but realized trying to manually edit this behemoth without breaking my profile was a one-way ticket to a corrupted session.

"Trust your instincts," Gemini told me, realizing we were barking up the wrong tree.

Instead, we decided to spoof the location using the Location Guard extension set to a fixed US coordinate. To make sure Chrome forgot my old regional check-in, Gemini told me to run:

sudo rm "/home/chronos/Local State" && sudo restart ui

I panicked for a second. Wait, rm -rf? Is this going to wipe my profile, my account, and all my data?

Gemini reassured me: Local State is just a temporary, system-wide scratchpad. My actual profile data was locked safely inside the encrypted Preferences folder. I took a breath, deleted the scratchpad, and rebooted.

Log back in... check the tray... Still no Gemini.

Chapter 4: The Ultimate Facepalm

I was completely done. I enabled the flags, ran the root commands, modified the config files, and spoofed my location, but the button refused to exist. I pulled the logs one more time and sent them over.

And then, the absolute kicker.

Gemini looked at the very top line of the log I provided:
"onboarding_completed_version":"146.0.7680.169"

Milestone 146.

I had literally mentioned my ChromeOS version right at the start of our session, but Gemini completely forgot to factor it into the math. The desktop AI companion framework (#glic) wasn't actually compiled into the stable Chromium source code until Milestone 147, and it wasn't unified into the interface until Milestone 148.

No matter how many terminal commands, location spoofs, or flag injections I threw at it, the visual layout code for the Gemini button literally did not exist in my operating system's local binaries yet.

---

The Moral of the Story / The Fix for Brunch Users:

If you are trying to force-enable the native Gemini feature on Brunch, do not waste your time editing config files or spoofing your location if you are on Milestone 146 or lower. The code isn't there!

You need to update your underlying Brunch system recovery images to Milestone 148 or 149 first.

The silver lining? Because I already successfully injected the flags into my /etc/chrome_dev.conf, the absolute second my root image updates to a build that actually contains the interface code, the Gemini button will automatically populate on my taskbar without me having to type a single line ever again.

Lesson learned: Always double-check your build milestones before you start fighting the terminal!

Blog: https://openiumsoure.blogspot.com/2026/05/how-i-spent-hours-toggling-flags-for.html