🔍 MyGlass APK Analysis – Key Findings
Critical Discovery: Glass Pairing Protocol Elements
From examining the original MyGlass APK structure, I found several crucial components that explain why the Glass 700C is stuck on “Install MyGlass”:
1. Glass-Specific Layout Files Found:
pairing_fragment.xml
– Main pairing interfaceglass_setup_fragment.xml
– Glass setup wizardconnectivity.xml
&connectivity_list_item.xml
– Bluetooth connection UIdevice_list_item.xml
– Device discovery/selection
2. Key Glass Connection Assets:
connection_status_glass.png
– Glass connection indicatorconnection_status_dots_anim*.png
– Connection animation framestap_touchpad.jpg
– Glass interaction tutorial
3. Missing Protocol Components:
The MyGlass app contains proprietary pairing logic that sends specific initialization commands to the Glass via Bluetooth. The Glass 700C expects:
- Initial Authentication Handshake
- Device Registration Protocol
- Glass-Specific Configuration Commands
- Setup Completion Signal
Why Our Current Approaches Haven’t Worked:
- Maestro Companion App: Modern alternative but lacks the legacy Glass pairing protocol
- Bluetooth HFP Connection: Working but incomplete – missing the application-layer handshake
- Companion Device Association: System-level pairing but not Glass-aware
Potential Solutions:
Option 1: Protocol Reverse Engineering
- Extract the pairing logic from the MyGlass
classes.dex
file - Analyze Bluetooth communication patterns
- Recreate the handshake commands
Option 2: Glass Factory Reset + Alternative Setup
- Reset Glass to bypass the MyGlass requirement
- Use enterprise setup methods if available
Option 3: Custom Companion App
- Build a minimal app that mimics MyGlass pairing protocol
- Focus only on the essential handshake commands
The core issue is that Google Glass Enterprise requires a very specific application-level protocol handshake that only the original MyGlass app knew how to perform. The modern Android Bluetooth and companion device systems can pair with the Glass hardware, but they don’t send the legacy setup completion signals that the Glass firmware expects.