Not compatible with GGE1 running EE8

[thesammykins]

Thought I would give installing this a shot on my EE1 running the EE8 software. Shows the following in logs despite being connected to my phone's bluetooth. If there's anything further I can get from my device let me know (might spin up the repo locally and troubleshoot tomorrow)

[BenTech2]

Thanks for the report and apologies for the lag here — I had a hunch it was a manifest perm thing but ended up chasing the wrong tree. The phone-side read failed log just means nothing's answering on the GlassHole BT UUID, which can happen for a handful of reasons (service crashed at startup, stale BT pairing cache, package not installed, etc.) and I'd rather not guess.

If you're up for grabbing a quick log dump from the Glass side, that'd let me actually pinpoint it:

What I'd love to see:

1. Confirm the glass-side base APK is installed and which version:

   adb shell pm dump com.glasshole.glassee1 | head -20
   

2. Logcat from the glass while you trigger a connect attempt from the phone — start the capture, fail to connect on the phone a couple times, then stop:

   adb logcat -c
   adb logcat -v time GlassHoleBT:V AndroidRuntime:E *:S > glasshole-ee8.log
   # ... try the connect from your phone, give it 30s ...
   # Ctrl-C to stop
   

3. (Optional but useful) The OS build info so I know exactly what EE8 is:

   adb shell getprop | grep -E "ro.build.(version|fingerprint|description)"
   

Drop the log + props as a comment here (or paste-bin them, whatever's easier) and I'll dig in. The most useful single line is going to be whether GlassHoleBT: Opening server socket... and Phone connected! show up around the time the phone tries — that tells me whether the listener is even running or it's crashing before it gets there.

Re your offer to spin up the repo locally — I'd absolutely take you up on that if the log doesn't show anything obvious, but let's start with the log first since it's faster.