You won’t be able to actually go hands-on with the new G1 until October 22nd, but thanks to a new website by T-Mobile you won’t have to wait that long to start playing with it’s Google Android-based operating system.
Just head on over to the G1 site here and select “Emulator” and you’ll be presented with a [mostly] fully functioning virtual G1 (some screens aren’t working but there’s enough that is to give you a pretty decent idea what it will be like to use the G1.
The highly anticipated HTC G1 phone on T-Mobile, the first Google Android-based handset to go on sale, won’t be available until October 22nd but has already apparently sold out.
According to T-Mobile even after tripling production on the G1 there were so many pre-sales for the device that it has sold out. You can still order it but you won’t be able to get it right at launch.
Given the great anticipation and the heavy pre-sale demand for the T-Mobile G1 with Google, we nearly tripled the number of phones initially available for delivery on our Oct. 22 launch date, and have sold through them all. However, to accommodate additional T-Mobile customers who want to pre-order a device, they now have the opportunity to place a pre-order through Oct. 21, for delivery at a later date. Also, people can still pre-register on the T-Mobile G1 Web site to be notified prior to launch where they can purchase the device beginning Oct. 22.
For more info on the G1 check out T-Mobile’s dedicated site here.
Cellular carrier T-Mobile today announced the first commercial Google Android-based handset and as expected it’s by HTC.
The G1 (formerly known as the ‘Dream’) will include features like:
- GSM / GPRS / EDGE / UMTS / HSDPA support
- Wi-Fi support
- Full slide-out QWERTY keyboard
- 3.17-inch 65K color touchscreen display with HVGA resolution (480 x 320)
- 3.1 megapixel camera
- 1GB microSD card pre-installed, supports up to 8GB
- Built-in GPS
- Android Market (online store similar to Apple’s App Store for the iPhone)
- YouTube playback
Another neat feature that I hadn’t heard about before this morning is integration with the Amazon MP3 store for purchasing and downloading DRM-free songs starting at 89 cents. Just like the iPhone, you’ll need a Wi-Fi connection to purchase a song, but you’ll be able to preview it using your phones data connection.
Look for reviews to start hitting soon and check out the G1 in person beginning on October 22nd when it hit’s T-Mobile stores for $179 with a two-year contract.
When Google first released their Chrome web browser it’s primary target was Microsoft’s Internet Explorer and it looks like it as able to make a dent.
Last week Chrome averaged 0.7% (down form it’s peak of 1.2%) of all browsers used and IE lost 1.4%.
By no means is IE losing it’s strong position as the number one web browser (it still controls 71% of the market) but it’s encouraging news for alternative browsers overall. Firefox climbed 0.3%, Safari 0.4%, and Opera 0.01%.
When Google launched their Webkit-based web browser named Crome earlier this week it quickly surged to take 1% of the browser market, more than Opera or Netscape’s browsers.
Not everything was perfect with Chrome, however, as users who took the time to read through the EULA (End Users Licenses Agreement) found something that didn’t exactly make many of them happy:
11.1 You retain copyright and any other rights you already hold in Content which you submit, post or display on or through, the Services. By submitting, posting or displaying the content you give Google a perpetual, irrevocable, worldwide, royalty-free, and non-exclusive license to reproduce, adapt, modify, translate, publish, publicly perform, publicly display and distribute any Content which you submit, post or display on or through, the Services. This license is for the sole purpose of enabling Google to display, distribute and promote the Services and may be revoked for certain Services as defined in the Additional Terms of those Services.
11.2 You agree that this license includes a right for Google to make such Content available to other companies, organizations or individuals with whom Google has relationships for the provision of syndicated services, and to use such Content in connection with the provision of those services.
11.3 You understand that Google, in performing the required technical steps to provide the Services to our users, may (a) transmit or distribute your Content over various public networks and in various media; and (b) make such changes to your Content as are necessary to conform and adapt that Content to the technical requirements of connecting networks, devices, services or media. You agree that this license shall permit Google to take these actions.
11.4 You confirm and warrant to Google that you have all the rights, power and authority necessary to grant the above license.
Thankfully Google has said that such language is a mistake. Or they’re trying to save face after getting caught. Either way they have agreed to change the EULA retroactively.
Personally, I think I’ll be sticking with Firefox for the time being.
Google has confirmed that tomorrow they will be releasing their own web browser called Google Chrome, a Webkit-based browser that will include features like:
- Built-in support for Google Gears for taking web applications offline
- An Opera-like dashboard page.
- Privacy mode to allow surfing with out leaving behind cookies or browsing history.
- Built-in malware and phishing protection.
According to Google:
So why are we launching Google Chrome? Because we believe we can add value for users and, at the same time, help drive innovation on the web. All of us at Google spend much of our time working inside a browser. We search, chat, email and collaborate in a browser. And in our spare time, we shop, bank, read news and keep in touch with friends — all using a browser. Because we spend so much time online, we began seriously thinking about what kind of browser could exist if we started from scratch and built on the best elements out there.
We realized that the web had evolved from mainly simple text pages to rich, interactive applications and that we needed to completely rethink the browser. What we really needed was not just a browser, but also a modern platform for web pages and applications, and that’s what we set out to build. On the surface, we designed a browser window that is streamlined and simple. To most people, it isn’t the browser that matters. It’s only a tool to run the important stuff — the pages, sites and applications that make up the web. Like the classic Google homepage, Google Chrome is clean and fast. It gets out of your way and gets you where you want to go.
We owe a great debt to many open source projects, and we’re committed to continuing on their path. We’ve used components from Apple’s WebKit and Mozilla’s Firefox, among others — and in that spirit, we are making all of our code open source as well. We hope to collaborate with the entire community to help drive the web forward.
As you might already know, Apple’s Safari browser is also based on Webkit, but I’m assuming that Google Chrome will have some newer Webkit features not present in Safari at the moment.
Guess we’ll find out Monday…
As the release of the first Google Android-based smartphone, the HTC Dream, draws near, as expected more info is starting to leak out.
The shots above are leaked photos of the Dream, showing off the slide-out keyboard, a few screens, and it’s size compared to a couple of other devices.
Is it just me? It looks a bit…cheap.
Google has announced that it’s Android-based mobile phone platform will be getting it’s own online application distribution system similar to the iPhone’s App Store called Android Market.
While the Android Market will initially be released in beta form, it is expected to be available when the first Android-based handsets hit the market later this year.
The process for developers to add their applications to the Android Market seems pretty straight forward–register as a merchant, upload your apps content, then publish it.
For more info check out Eric Chu’s blog post here.
Android developers found something interesting with the latest Android SDK: Android 1.0 will not include a “comprehensive” Bluetooth API.
No one’s 100% sure what that means and so far Google isn’t elaborating.
I wouldn’t expect it to mean that you won’t be able to pair a Bluetooth handsfree device with an Android-based phone because that would be silly.
Instead I would assume it means that features like A2DP for stereo over Bluetooth won’t be initially supported but could be added down the road.
We’ll see, I suppose.
After some delays in getting an update to the Android SDK released to the masses, Google has finally rolled out their version 0.9 SDK r1 beta, the first formal release of the SDK.
This version includes some pretty significant UI changes along with some bug fixes and lots of new API enhancements.
Hopefully people that had been developing an Android application using the previous SDK build won’t have too many changes to make to their code to get things working on this new SDK release.