Game Development Reference
In-Depth Information
Configuring a Real Device
Personally, I think using a real device is the best way to develop games and apps that use
OpenGL. The emulator is painfully slow, plus not all the OpenGL API calls are implemented.
A real device has many advantages the emulator does not, namely speed and API reliability.
The only caveat is that the emulator gives you the chance to test multiple screen sizes and
API versions. All in all, a real device is the way to go if you are building an OpenGL game;
use the emulator as a backup test tool to check your game.
Before Android Studio can recognize your device, you need to install a USB driver required
for communications.
Note
Before installing the USB driver, try to plug in in the device to your PC and see if it shows
up in the Android Studio devices view (because the required driver may already be installed in your
computer). If the device won't show up, then you need to install the USB driver.
MORE ON THE USB DRIVER
Notice that the Google USB driver is required for Windows only to perform Android Debug Bridge (ADB)
debugging with any of the Google Nexus devices. The one exception is the Galaxy Nexus: the driver for Galaxy
Nexus is distributed by Samsung (listed as model SCH-I515). Please take a look to the OEM USB drivers
Windows drivers for all other devices are provided by the respective hardware manufacturer, as listed in the
OEM USB Drivers document.
Here are some of the devices compatible with Google's USB driver:
•
ADP1 / T-Mobile G1
•
ADP2 / Google Ion / T-Mobile myTouch 3G
•
Verizon Droid
•
Nexus One, Nexus S, Nexus 4, Nexus 5, Nexus 7, and Nexus 10
•
Galaxy Nexus
•
PandaBoard (Archived)
•
Motorola Xoom (U.S. Wi-Fi)
•
Nexus S
•
Nexus S 4G
Using the Nexus 7 that was originally sold with 4.1.2 or newer is not recommended. If you have other devices,
you'll need to contact your vendor. A list of OEMs and more details on the USB driver for Windows is available at
