Google Glass has been making waves across the tech segment, and those waves finally culminated in a teardown of the product itself – something which we certainly have nothing against checking out. With a Torx T5 Screwdriver in hand, and some time (and money) to kill, someone did just that, and this is the result.
When we first got our hands on Google Glass awhile back, we struggled to fully comprehend how Google had fitted so much useful tech into such a slim, streamlined package. Yes, from time to time, we did look like dorks wearing them in public, but the most astonishing thing about them was their capability, and the way they could interact with the real world to provide an almost effortless user interface. We didn’t quite know how they did it, but now we at least have a clearer picture.
The teardown comes courtesy of Star Simpson and Scott Torborg who picked up a Google Glass and in no time at all bought some prescription lens before beginning the teardown (the goal of which being to add prescription lens to the device itself). To take it apart, they carefully pryed the plastic from the main unit close to the display, which in turn revealed both the Proximity and the Ambient light sensor.
With the rest of the plastic, they did face some trouble, the results of which included slight permanent damage to the unit. This happened through the cutting of plastic around one of the internal screws. After this screw however, it was smooth sailing.
Once free of the plastic, they then took out the main board, which was covered in a typical adhesive mixture. After clearing out the mixture, they also managed to find a TI OMAP4430 chip and a 16GB SanDisk flash chip. After that, came the battery, but this too required some plastic cutting. The rest of the intense process is detailed on the Catwig site, should you be interested. It’s obvious however that the teardown of Google Glass is doable, but perhaps not advised unless you have a skilled hand in taking apart small devices.
Via: SlashGear
Its a shame Google was not forthcoming with specifications of this hardware from the begining. Because of this they probably lost a lot of time getting quality apps on this platform…
It’s not even commercially available yet. Not until next year. They have plenty of time to get quality apps on the platform. If you ask me.
If tommorow another company released similar device with the full specs then Google would only have couple days head-start on them rather than the year they wasted. More so, if that other company released the full access to the hardware tommorow, then Google would be behind until they release their GDK. All there is to work with now is a crippled API that has probably scared off a lot of developers already.