Solos AirGo 3: Calendar Synchronization Failure - Diagnosis

SAFETY WARNING. This device contains lithium batteries. Improper puncturing or bending during disassembly can cause explosions or flames. Furthermore, being micro-electronics, intervention exposes components to the risk of electrostatic discharge (ESD) and permanent PCB damage. Intervention requires precision and the assistance of a specialized technician is recommended. ReeFix provides this diagnosis EXCLUSIVELY for educational and informational purposes.

OBSERVED SYMPTOMS

The Solos AirGo 3 fails to synchronize the calendar and does not receive push notifications from the smartphone. Curiously, audio functionality (calls, music playback) remains fully operational. This behavior often occurs after a prolonged phone standby period or following the installation of software updates, both for the operating system and the Solos application.

WHAT TO EXCLUDE

• Total Bluetooth connectivity failure: Since audio works, the Bluetooth module is active, and the basic connection is established. The problem is limited to the Bluetooth Low Energy (BLE) protocol and the management of specific data (GATT profiles) for notifications and the calendar, not classic Bluetooth.
• Severe primary hardware damage: Synchronization failure is rarely an indication of irreparable hardware failure. The probability of a software or configuration issue is significantly higher than a physical malfunction that would require immediate device replacement.
• Direct charging problems: If the glasses turn on and hold a charge, the USB Magnetic Charging Cable for Solos AirGo 3 is not the primary cause, although unstable charging can, in rare cases, affect the general stability of the BLE module.

FINAL CAUSE

1. Software conflict and operating system restrictions (iOS/Android) - High probability (60-75%)

• Key signs: Notifications only arrive when the Solos AirGo app is actively open on the smartphone screen. The calendar does not update after the phone has been in a pocket or on standby for a while.
• Why it happens: Modern mobile operating systems implement aggressive power-saving strategies (e.g., "Out-Of-Memory Killer", battery optimization) that can "freeze" or terminate background apps. If the Solos application is blocked, the BLE communication channel with the glasses is interrupted, preventing synchronization.
• Quick checks (DIY):
  1. Access your smartphone settings: look for "Battery", "Apps", or "Notifications".
  2. Locate the "Solos AirGo" application and disable all battery optimizations or background restrictions. Ensure the app can auto-start and has full access to "Notifications" and "Calendar".
  3. Verify that "Location (Always On)" permissions are granted, as the BLE protocol often depends on it to maintain a stable connection.

2. Glasses firmware or application bug - Medium probability (15-25%)

• Key signs: The problem persists even after meticulously configuring permissions. Reports of unstable behavior from other users are noted after the latest app or glasses firmware update.
• Why it happens: A failed software update or a defect in the glasses' firmware code (microcontroller) or the app can corrupt synchronization protocols.
• Quick checks (DIY):
  1. Hard reset of the glasses: Press and hold the virtual button on the right temple for more than 10 seconds, until the status LED flashes alternately red/blue. This restores the firmware to factory settings.
  2. Check and install any available updates for the Solos AirGo app in your smartphone's store.
  3. If possible, try pairing the glasses with another smartphone (perhaps with an older operating system version) to understand if the problem is related to your device or the glasses themselves.

3. Bluetooth pairing profile corruption (GATT Cache) - Low probability (5-10%)

• Key signs: The glasses appear connected for calls, but the Solos application does not detect the device or shows a persistent connection error.
• Why it happens: GATT (Generic Attribute Profile) profiles define the data structure exchanged via BLE. A corrupted Bluetooth cache on the smartphone or a misalignment of these profiles can prevent proper service data transmission.
• Quick checks (DIY):
  1. In your smartphone's Bluetooth settings, select Solos AirGo 3 and choose "unpair" or "forget device".
  2. Clear the phone's Bluetooth cache (usually found in system app settings, under "Bluetooth").
  3. Uninstall the Solos AirGo app, restart the phone, reinstall it, and re-perform the entire pairing procedure from scratch.

4. Hardware damage to the antenna or micro-power interruptions - Very low probability (less than 5%)

• Key signs: Frequent disconnections even at a very short distance from the smartphone (less than 2 meters). Abnormal overheating of the right temple during charging.
• Why it happens: Micro-fractures in the integrated antenna (often in the right temple) due to mechanical stress can attenuate the RF signal and drastically reduce BLE range. Even micro-voltage drops from the battery can cause brown-outs that reset the BLE chip.
• Quick checks (DIY):
  1. Test the maximum Bluetooth signal range in an open environment without obstacles. If the connection drops at less than 2 meters, the internal antenna may be damaged.
  2. Visually inspect the golden charging contacts of the glasses for any oxidation that could cause unstable power.
• Useful tools (for technician):
  • USB Bluetooth dongle for protocol sniffing to analyze BLE packets.
  • Precision digital multimeter to measure battery voltage.

Output for Technician: The Solos AirGo 3 exhibits BLE synchronization failure (notifications/calendar) with audio functioning. App blockage by OS, firmware bug, or GATT corruption is suspected. App permission verification, firmware hard reset, and if unsuccessful, RF antenna analysis and battery voltage stability check are requested.

Costs and Operational Decision: For most cases (85-90%), the solution is software/configuration, with zero cost to the user. If quick DIY checks do not resolve the issue, a specialized wearable technician can intervene with an estimated cost of €20-€40. Device replacement is recommended only in case of confirmed and uneconomical hardware damage, given the low cost of software intervention.

Operational decision: Perform quick software checks in order of probability; if the problem persists, consult a technician; replacement is the last option only in case of confirmed and uneconomical hardware damage.