Subject: General Tech | April 27, 2013 - 08:42 AM | Tim Verry
Tagged: wearable computing, ti omap, omap 4430, google glasses, android 4.0.4, Android
Earlier this month, Google announced some of the key specifications of its Google Glass project. However, the company left out just how much RAM the device would have or what the exact System on a Chip (SoC) would power the Android device.
Now that the Google Glass glasses are making their way to developers, those as-yet-unknown details are fairly-certain. Google Glass developer Jay Lee managed to access the device using ADB and discovered that the device offered up 682MB of RAM (accessible to developers) and a Texas Instruments OMAP 4430 SoC. Google Glass likely has 1GB of total RAM, but the operating system and other necessary device-level processes are likely responsible for reserving the remaining 342MB chunk of RAM. The TI OMAP 4430 is the same SoC that is powering the Amazon Kindle Fire and a number of other mobile devices released last year. Because of battery life constraints, Google is most likely not running the chip at its maximum 1GHz clock speed. In the Google+ discussion, developer Kevin Fitch speculated that it is likely clocked at 600MHz due to the cores’ BogoMIPS scores.
The remaining Google Glass specifications include Android 4.0.4 (Ice Cream sandwich), 16GB of internal storage, a 5MP camera, and support for both 802.11g Wi-Fi and Bluetooth. It is essentially a mid-range smartphone hidden away inside a pair of glasses. At $1500, the first round of Google Glass was solely for developers, but once Google rolls it into production next year, judging by the internals, it should be much cheaper.
Are you excited for Google Glass? If you are curious about the software or hardware, Jay Lee is taking questions on his Google + thread.
Subject: General Tech | June 27, 2012 - 11:12 PM | Tim Verry
Tagged: project glass, google+, google io, google glasses, google, explorer edition
One of the cooler presentations during today’s Google I/O Keynote events was the surprise reveal of Explorer Edition Google Glasses (the hardware emerging from Project Glass). They kicked off the presentation by live streaming a wing suit flight from a blimp using – you guessed it – Google Glasses and a Google+ Hangout. Extremely cool! The video of the event is embedded below for those that missed the live stream.
The Google Glasses have a built in camera and small transparent display mounted over the rim of the right glasses and is visible when looking slightly upwards. They have been constructed so that they are balanced, with the majority of the weight spread out behind and around the ears instead of being front-heavy and pushing down on the bridge of your nose. The Explorer (developer) Edition glasses are WiFi and Bluetooth only, and feature a touch pad on the right side and camera button on the top of the glasses rims. They further are able to locally store images or videos with the option to offload some or all of the media to your computer. (a 3G/4G modem would probably affect battery life too much to be useful).
Despite feeling a bit like a Universal Soldier, I wouldn’t mind getting my hands on a pair of Google Glasses. The catch is that they are only available to Google I/O attendees, won't ship until early 2013, and will run $1500 each. That’s a high price for what would amount to a toy for me, but it is not out of the question to expect from a developer – who in turn gets early access to the hardware and can get a head start at developing applications for it.
My only real problem with the idea of wearing Google Glasses is that the company already has a mountain of data about me (Google+, Google search history, Analytics, Adsense, Drive, Play, Android, Chrome... wow I never really have Google-fied my browsing is!), and Google Glasses sound like a device that is a bit /too perfect/ of a tool for gathering data on me and presenting me with “relevant ads” for Google to ignore! (hehe)
What do you think of Google Glasses? Could you see yourself wearing them? And if so, what would you use them for?