What do you need help with?

R-8 Developer Kit Summary


Congratulations! You are among a small, select group that are leaning forward with us to bring new applications and experiences to the ODG smartglasses. It’s a very exciting time!

This "CES 2017 R-8" Dev Kit will allow you to optimize your applications and work on new Applications that harness the new Snapdragon 835 processor, cameras, sensors, and software of the R-8 and R-9 glasses. That said, there are a few limitations we need to make you aware of so that you can hit the ground running.

This kit is based on the R-8 glasses. It was designed and manufactured for our first engineering model (EM1) that many of you saw earlier this year. It features:

  • Qualcomm 835 processor
  • Dual 2mp RGB Stereo camera – future versions will be 5mp
  • Camera with Fish-eye lens (for 6DoF)
  • Android 7.1 Nougat
  • Wi-Fi, Bluetooth

There are differences from complete glasses and some hardware limitations of note, they include:

  • No display panels (though has a Micro HDMI out port)
  • No GPS
  • Dual Stereo RGB Cameras upside down
  • 6DoF sensor is flipped. Down is up and up is down. Right is right and left is left though. (This happens because when the glasses are assembled the camera and flex are folded over the board.)
  • 5GHz Wi-Fi works. 2.4 does not. (Dual band will work in EVT, DVT, and Production)
  • Ambient Light Sensor will be different and behind the lenses on the glasses
  • No microphones – Mics are on flexes in the glasses
  • No audio out; Bluetooth headphones could be paired.
  • Batteries will be different affecting fuel gauge and capacity and run time calculations
  • No 13 MP RGB camera like the R-9
  • USB C to USB C is not supported

As we have time, we will try to fix some of these issues and provide an OS update.


Interacting with the Dev Kit

It is our strong recommendation that the developer uses Vysor (http://www.vysor.io) for viewing and controlling the Dev Kit, and Android debug bridge (adb). These are the best ways to interact with the it. See these Dev Site articles:


How-to-enable-MTP-on-the-Marshmallow-R-7 (same basic procedure on Nougat)

Importantly, please note that the resolution shown on the Vysor App session on your development host is far below the resolution in the glasses. Also, while you can use a cable directly into a USB A socket on your computer, a externally powered USB 3.0/3.1 bc 1.2 hub will ensure that the system gets the power it needs (some laptops don’t supply more than about 100 mA @ 5V, which is not enough to charge the kit).


Getting started

Turn on sequence:

  1. Plug in USB C cable into Dev Kit and the other end into USB A on computer with Vysor running (or USB Power Source if only charging)
  2. Optional - Plug in Micro HDMI cable into Dev Kit port, other end into HDMI monitor
  3. Turn on the switches:
    • battery right on
    • battery left on
    • main power to USB position
  4. Blue LED by main power switch, and multicolored LED by heat sink, should both turn on.
  5. Must be plugged in for at least 5 min for batteries to charge enough to boot.
  • If after 5 min, its still not registering on adb or Vysor, press and hold power button for 20 seconds.


QualComm VR SDK Support

We initially shared a zip folder with the VR SDK 2.0 Binary and some sample projects for native Android as well as Unity Applications: SnapdragonVR-SDK-binary.rel.2.0.0.zip
A later version of this SDK is also available : SnapdragonVR-SDK-binary.rel.2.1.0.zip
which you should use if you are just starting out. 
To begin developing Unity based Apps, we suggest you use the reference empty Unity project like Boxworld to start off with as a baseline, make sure that you can build it and it works the way you expect, and then pour your content into it. The sample project embedded in the SDL zip is not customized for the glasses, so use this version of the Boxworld Project (let us know if you have trouble downloading).
Or, as another reference, you can use this Unity Package in a fresh project (attached to this article).
Note that the current R-7 samples on our developer site will not work on the R-9 & R-8 devices right now; they were designed to work on the R-7, which does not support VR SDK yet. So, focus on the samples included in the VR SDK zip.   



How do I tell if the Dev Kit is charging correctly?  Normally, you would see in the status bar the battery icon with a lightning bolt thru it, indicating charging. However, the current version of OS and hardware, there can also be instances where the battery is not actually charging. To check if the Dev Kit has recognized your USB C 3.0 or 3.1 power source, and is therefore charging, type the following commands in via adb:

adb root

adb shell cat /sys/class/power_supply/usb/uevent | grep POWER_SUPPLY_CURRENT_MAX

You will see in response something like:


which is the max current in amps X 10+6. In this case, the source will supply .5A max. This would be the minimum needed to keep the Dev Kit charged.

If this returns -22, this means your source is unrecognized, and so the kit will eventually discharge and turn off.


How do I update the OS?

Stand by; We'll update this info once we have an OS update.


Reporting Issues

Since we are still in the process of software development and hardware bring up, there are a number of bugs that we have identified and know that you will find some too. Please report issues and bugs by going to our Support Request Page and select the ReticleOS Developer Program pulldown option in the How can we help you? field.  Thank you.

Developer.OsterhoutGroup.com will contain updates and tips under the heading 835-Hardware-R-9-R-8 


Samples on the Dev Kit

We have installed 2 sample 6 DoF applications we wrote, Planets SVR and AR Medical. Additional sample code will be made available this month.



Have more questions? Submit a request


Powered by Zendesk