The G2 does NOT have connectivity issues - that's a lie!
As clickbaity as that title sounds, it's true. All these firmware updates that say they have improved the bluetooth stability and connectivity are full of crap, because the bluetooth connectivity and stability was never the problem. Hear me out.
When I got my G2 and R1 combo, I loved the hardware, loved the idea of what it should be able to do, but hated actually trying to use the janky, buggy, broken piece of crap. Like everyone else, I kept encountering endless disconnections, shitty AI, garbage-tier STT (speech to text) detection, janky software, unstable app, and all the rest.
So I decided to throw away Even Realities software entirely and make my own. Not using their SDK to create an app within their app, but to control the G2 entirely.
First, I spent a ridiculous amount of time and effort reverse-engineering the bluetooth signals the app uses to control the glasses and ring. I used BT Snoop and wrote a few custom apps in the SDK to allow me to test every single thing the G2 is capable of and document every bluetooth signal it corresponds to, as well as all keepalive signals and everything else. This documentation is here: https://github.com/expectbugs/G2CC/blob/master/docs/G2_BLE_PROTOCOL.md
With that in hand, I built a project I call G2 Control Center, starting with an Android app that replaces the Even Realities app entirely (I uninstalled it) and controls the G2 directly via bluetooth, and is a lot more strict and clean with the signals than the official app is. The app acts as a bridge or harness, it merely takes the content pushed from my home PC (over wifi or cellular) and serves it to the G2. On my Home PC the main system runs, where I build a whole OS (or rather a Window Manager) that has everything I want my G2 to be able to do, with a Display Renderer, image conversion to the 4bpp greyscale G2 image format, and everything else. Including a mirror so I can see (and control) the output in both the bridge app and on my PC directly, mirroring what the G2 displays, for testing and also for using the system while the G2 is charging.
First it was a simple format, menu to the left and content area to the right, but I didn't like how much space the menu on the left ate up, so eventually I redesigned it to a ribbon menu at the top, taking one line (with a clock permanently on the top right), and the full-width content area below it. My system, at this point, is incredibly feature-filled, with ereader, file manager, music player, several games, terminals (using tmux for portability), browsing, voice recognition (with QUALITY speech-to-text powered by my full PC), AI features (with QUALITY AI powered by my full PC), and lots lots more.
The entire system is open source on my github here: https://github.com/expectbugs/G2CC
Here's the kicker though, that justifies the title of this post: There are NO connection issues. NONE. One of the things I learned while doing this, is that the G2's go-to reaction when it receives any sort of signal it doesn't understand, or anything out of bounds, or anything not timed correctly, is to puke out a disconnection message and give up. That's just what it does. Once I ironed out all the bugs in my bridge app, I NEVER saw a disconnect again. I work in a steel mesh manufacturing plant, basically worst-case-scenario for bluetooth connections, full of wire mesh and massive industrial machines and forklifts and a hundred competing bluetooth and wifi signals from a hundred workers bluetooth speakers and earbuds and phones and more. I used to think that was why I would get disconnected so often. I was wrong. It was 100% buggy software in the official Even app. That's it. Once I dropped the app, months ago, I have not been disconnected ONCE, ever. Except, of course, when legit walking waaay out of range of my phone.
Better still, since the system runs on my home PC, every single app within my system is always running, full persistence. Switching from one to another is akin to ALT+TAB on a PC, no loading, no starting over, exactly where I left off. If I close the app and disconnect the glasses intentionally, the moment I reconnect I'm exactly where I was before, like turning off and on my computer monitor without touching the PC.
My program was made for me, using Linux, so unless you're a Linux user and rather savvy with things like tailscale and the like, you wont be able to use it as-is. However, the Bluetooth protocol I documented can be used to make your own, and it proves the G2 bluetooth connection is rock solid. I have not updated my firmware in months, and I use the G2 every day, and I never ever see that damned disconnection message. So all these firmware updates bragging about improved bluetooth connection are garbage. The firmware was never the problem, the app is.
I hope this helps somebody.