Jim Wilson (a.k.a. hedgehogjim)
30+ years as a professional software dev, 17+ years developing mobile solutions, Pluralsight Author, Founder JWHH, LLC
Packt is celebrating the release of their 2,000th title and has a special offer!
Packt is throwing in a free eBook of your choice with the purchase of my book, Creating Dynamic UI with Android Fragments.
Actually they’re doing that for all of their eBook titles but I thought I’d take this chance to plug mine. 🙂
Whatever titles you choose, it’s a great deal!!
Recently my Google Glass arrived … Needless to say, I was excited and ready to start working on building apps for Glass.
I unbox and fire up Glass, go through the initial setup steps, and turn on debug (Settings -> Device Info -> Turn on debug). So far, so good.
I then walk over to my PC, fire up the Android SDK manager to confirm that I have the latest revision of the Google USB Driver (Rev. 9 at the time of this writing).
I then connect Google Glass to my PC’s USB port and wait for the USB setup window to tell me Glass is ready to use.
The USB setup appears to be going well but just as the setup process is about to finish, my PC displays a message indicating that there were some problems. At first I was somewhat concerned but, things start looking better…
The Auto Play window opens showing options for the Glass device…
… and Glass 1 is suddenly listed as an option in the Windows File Explorer.
Using both the Auto Play window and File Explorer I’m able to browse around the device file system. I can even copy files between the Glass file system and my PC file system.
Clearly the USB setup window was mistaken. 🙂
Feeling confident, I open up a command prompt and enter the command to display the list of Android devices currently connected.
adb devices
Which then displays the following.
List of devices attached
Notice that no devices are listed. Clearly the USB setup had not completed successfully … there is a problem with the USB driver.
If ADB doesn’t see that Glass is attached, tools like Android Studio, Eclipse, DDMS, etc. are not going to see the device either. We need to fix this.
For the USB Driver to work with Glass, some tweaks need to be made to the USB driver’s android_winusb.inf file (located in [android sdk install folder]\extras\google\usb_driver ). The list of steps to manually modify the file can be found here.
Alternatively, you can download a modified version of the USB driver from AndroidFileHost.com.
If you choose to use this download be extremely careful! USE THIS DOWNLOAD AT YOUR OWN RISK!!
This is not an official USB installation but rather one created by a person who has been kind enough to share it. I’m using this download on my development PC and it’s working great. That said, you still need to be very careful because there’s always the potential for someone to do something malicious.
Once you have the modified USB driver files (whether you manually make the changes or you download them) you can easily update your PC to use the modified USB Driver installation.
You’ll probably receive a warning that the USB driver can’t be verified. As long as you’re confident that you’re dealing with a safe driver installation (either you made the changes to the android_winusb.inf file yourself or you’ve validated that the USB driver files you downloaded are safe) allow the installation to run.
Once the USB driver installation completes … Your PC is ready to connect to Glass.
You can verify that the USB driver change worked by again running the adb command.
adb devices
But this time, you should see a device listed.
List of devices attached 015DA77204015006 device
And now you’re ready to go … time to start creating those killer apps for Glass !!
Hopefully Google will soon release a USB driver that supports Glass without requiring these extra steps. But until they do, these steps allow us to begin working with Glass right away.
Jim is currently working on an online course for Pluralsight about creating apps for Glass with the Glass Development Kit. That class should be available at the end of April 2014.
Remember though that developing native apps for Glass requires a solid understanding of Android app development so checkout Jim’s many Android programming courses and cross-platform iOS/Android programming courses at Pluralsight.
I’ve been working with Xamarin a great deal the past several months and am increasingly becoming a fan of the product. The ability to leverage the Visual Studio IDE, familiar .NET class libraries, and C#programming language to create both Android and iOS apps provides incredible power.
The beauty of working with Xamarin is that it allows us to share code when doing so makes sense but Xamarin also embraces the unique features of each platform. Xamarin does this by going beyond the many .NET classes that we’re all familiar with to also include .NET classes that expose the features of each platform.
As an example, the features of Android activities are available through a .NET Android.App.Activity class. Similarly, there’s a .NET MonoTouch.UIKit.UITableViewController class that makes the iOS UITableViewController features available. The platform-specific features provided by Xamarin are extremely rich and comprehensive giving us access to most any platform features we’re likely to use.
By having both the standard .NET classes and platform-specific .NET classes we’re able to build our application’s core logic just once, sharing that logic across both platforms, while also having full access to each platform’s unique capabilities and features.
If you’d like to learn more about working with Xamarin, I encourage you to checkout my 2 part course series on cross-platform app development with iOS and Android. Pluralsight just published part 2 of the series this week.
BTW: Although the 2-part series on cross-platform iOS/Android development with .NET/C# is complete there’s still a lot more to content to come. Keep watching for more courses on using Xamarin to create Android and iOS apps.
Jim Wilson (a.k.a. hedgehogjim) 