Posts Tagged ‘google’

Google Earth for Android Phones

Thursday, February 25th, 2010

ge-android.jpg

It is done. Google Earth for Android has been published. I just ran it on my Nexus One and it seems to work fine. Very smoothly, nice 3D graphics and all the layers in there with your favorite restaurants. Zooming in and out as well as panning in the 3D world works totally fine. Besides that it is not doing much, but it shows your current location on the earth, of course. Still, well done Google!

Check it out here:

Linus Torvalds bought a Nexus One

Tuesday, February 9th, 2010

Linus Torvalds bought a Nexus One
Though the Nexus One does not seem to be a best-seller, it seems it found its way into Linus Torvalds’ hands. You know, the “Finnish software engineer [who is] best known for having initiated the development of the Linux kernel and git revision control system” (Quote from wikipedia).

I already wrote some stuff about the Nexus One and even about unboxing my device. Now Linus has one too and guess what he wants to use it for? He didn’t get it for the phone function or messaging because that would be too distracting during work. Well, he is right. It seems his favorite is “Google Navigation”; perhaps I should check that out too, some day?

Image source: wikipedia.org

Nexus One

Wednesday, January 6th, 2010

Nexus One

IMHO, this is quite chic. I have to say that I am kind of surprised by the design. While the OS itself is pretty much the same on all devices; we distinguish Android phones more by their design and usability. Respectively, reviews say that the phone feels very fast – faster than all other Android phones on the market. Well, the huge processor must be there for something. But despite that the Nexus One just looks cool. I think I have to get one for “testing purposes” … :) No seriously, this is one of the pretty phones I have seen so far. Not just Android phones, I am talking about all smartphones you can compare the Nexus with. Well, the iPhone still looks great and I am actually loving the design of the new BlackBerry Bold 9700 as well.

The best thing is that you can get it unlocked without any SIM card limitation for just US$529 directly from Google. That is exactly what the developer community needs. A quasi standard phone for cheap which can be used for developing anywhere. They tried that already with the G1 for Developers but that didn’t work that well. For example, I was not able to order one because they could not ship to my country or whatever. Anyway, the Nexus One seems to be great and it will kick off the Android developer community as we get a great phone for less money!

Technical Specs

Power and battery

  • Removable 1400 mAH battery
  • Charges at 480mA from USB, at 980mA from supplied charger
  • Talk time: Up to 10 hours on 2G; Up to 7 hours on 3G
  • Standby time: Up to 290 hours on 2G; Up to 250 hours on 3G
  • Internet use: Up to 5 hours on 3G; Up to 6.5 hours on Wi-Fi
  • Video playback: Up to 7 hours
  • Audio playback: Up to 20 hours

Processor

  • Qualcomm QSD 8250 1 GHz

Operating system

  • Android Mobile Technology Platform 2.1 (Eclair)

Capacity

  • 512MB Flash
  • 512MB RAM
  • 4GB Micro SD Card (Expandable to 32 GB)

Location

  • Assisted global positioning system (AGPS) receiver
  • Cell tower and Wi-Fi positioning
  • Digital compass
  • Accelerometer

Size and weight

  • Height: 119mm
  • Width: 59.8mm
  • Depth: 11.5mm
  • Weight: 130 grams w/battery; 100g w/o battery

Display

  • 3.7-inch (diagonal) widescreen WVGA AMOLED touchscreen
  • 800 x 480 pixels
  • 100,000:1 typical contrast ratio
  • 1ms typical response rate

Camera & Flash

  • 5 megapixels
  • Autofocus from 6cm to infinity
  • 2X digital zoom
  • LED flash
  • User can include location of photos from phone’s AGPS receiver
  • Video captured at 720×480 pixels at 20 frames per second or higher, depending on lighting conditions

Cellular & Wireless

  • UMTS Band 1/4/8 (2100/AWS/900)
  • HSDPA 7.2Mbps
  • HSUPA 2Mbps
  • GSM/EDGE (850, 900, 1800, 1900 MHz)
  • Wi-Fi (802.11b/g/n)
  • Bluetooth 2.1 + EDR
  • A2DP stereo Bluetooth

Nexus One Landscape

While the technical specs are interesting but not that astonishing let’s take a closer look to the supported formats:

Image

  • JPEG (encode and decode), GIF, PNG, BMP

Video

  • H.263 (encode and decode) MPEG-4 SP (encode and decode) H.264 AVC (decode)

Audio encoders

  • AMR-NB 4.75 to 12.2 kbps sampled @ 8kHz

Audio decoders

  • AAC LC/LTP, HE-AACv1 (AAC+), HE-AACv2 (enhanced AAC+) Mono/Stereo standard bit rates up to 160 kbps and sampling rates from 8 to 48kHz, AMR-NB 4.75 to 12.2 kbps sampled @ 8kHz, AMR-WB 9 rates from 6.60 kbit/s to 23.85 kbit/s sampled @ 16kHz., MP3 Mono/Stereo 8-320Kbps constant (CBR) or variable bit-rate (VBR), MIDI SMF (Type 0 and 1), DLS Version 1 and 2, XMF/Mobile XMF, RTTTL/RTX, OTA, iMelody, Ogg Vorbis, WAVE (8-bit and 16-bit PCM)

Well, not much new in here too as those formats are supported by Android already. Still, I like the phone though. Well done Google!

More about the Google Nexus One:

Google’s Own Android Phone to go the BlackBerry Way

Thursday, December 17th, 2009

I just read that Google plans to sell its own Android phone in two versions:

  1. Branded T-Mobile version with contract.
  2. Unbranded version.

This brought up some memories on how BlackBerry devices are distributed. For those of you who don’t know: BlackBerry devices from Canada’s biggest and S&P 500’s fastest growing company Research In Motion are only available through Wireless Network Carriers; mostly branded. It is impossible to get such devices without branding (unless you are a BlackBerry Alliance partner and get an internal device for testing).

For Google it is a good move to have their device at network carrier’s shelfs because that is where customers get their phones mostly. I guess the mainstream user (not you and me) doesn’t really care much about what phone it is and who made. The phone user’s decision is usually based on

  1. Good deal with the carrier.
  2. Phone’s capabilities.
  3. Phone’s look.
  4. Phone’s reputation.

Obviously user’s of Apple’s iPhone have their preferences sorted differently. Well, the above sorting is mine, and I have to say: even though the iPhone looks cool and is supposed to be “hip”; and the Android phones are kind of geeky (from a technological point of view); I am still using a BlackBerry as my main device. In fact, as I am on the road right now, I am using two!

People now might say: “Why the f*** is that? You are running an Android blog man!” Well, I have to say: Android is not there where I would like to see it at – yet. I really like the Android approach of Android OS and I truly believe it will have a bright future for all of us, but there is still some way to go. The gap to Google’s competitors gets closer and closer but it is still there. Fortunately, our business is such a fast growing one that our world order could be upside down next year.

I am really excited about the mobile future; this includes but is not limited to Android. What devices are you using?

More about this on Two Google Phones Coming in January? (Reuters via internetnews.com)

Android Market counting 20k Apps

Wednesday, December 16th, 2009

Android Market Icon
The Android Market just took the leap and jumped above the count of 20,000 applications. While the iPhone’s iTunes App Store is still ahead with about 100,000 applications, I have to say respect guys!

Hammering out 20,000 applications in such a short time without the devices and market power (like Apple has for example) is not that easy. I know there are still a lot of ideas in your heads (as in mine) which just want to be brought to paper life. So get started! Open your Eclipse, hack some lines into it, press compile, test, sign and upload it to the Android Market. No matter if free or paid, every new app brings more variety, more diversity and more attraction to the Android Market, every Android phone and therefore it makes the whole platform more attractive to users all around the world.

Get more about this on internetnews.com

Motorola Droid with Android 2.0 on November 6th

Thursday, October 29th, 2009

Motorola Droid

Motorola is releasing this beaty very soon! Somehow it reminds me very much of the Google G1. A bit sharper edges and stuff but that seems to be “in” right now. Therefore, most specs are the same with one highlight: the screen resolution will be 854 x 480 pixels. That sounds pretty nice to me! Moreover, Motorola put a capacitive 3.7 inch display in there which means the display definitely supports multi-touch. Micro-SD, Bluetooth, WiFi, GPS, 5 MP auto-focus camera with double-flash.

The US CDMA model will be available for $200 with a 2-year contract on Verizon. Check out the Droid does website.

By the way, I found that note on Golem.

Help the Community

Wednesday, July 15th, 2009

Hi folks,

Android Glideras you might have already mentioned, I have not published an article for quite a while. I also haven’t published a proper developement article for even a longer while. Honestly, I really want to change this, but I got one problem: I am lacking in time. I don’t see much more space in future but I will definitely try to squeeze in more time for this blog. I really like the Android platform and basically the whole idea it. It is worth and fun to write about it!

Anyway, what I actually wanted to ask you guys: Is anyone interested in sharing simple code samples with the community?
(Example: DialANumber)

What I can see from the day-to-day increasing access to this site is, there are definitely lots of people interested in this blog and its content. This means I did something right with my previous articles :)

So if there is someone out there who would like to share his / her experience with the Android platform please drop a comment below this article. I am sure we can make the world better, and bring useful information to the Android community.

Android OS on more devices

Tuesday, February 24th, 2009

Huawei Android Phone
Android Phone from Huawei
About a week ago Huawei announced an Android powered phone at the Mobile World Congress ‘09. Huawei is not really known outside of China except as a mobile infrastructure provider. Though many people outside the People’s Republic do not know that brand, everyone in China knows it. Being the biggest mobile phone market (more that 400 mio. mobile subscribers) speaks for itself. The phone itself looks like a direct iPhone copy but with a good OS :)
ASUS Eee PC - running Google’s Android OS
Android on ASUS Eee PC
Besides the Chinese dudes I just read from other (free) Chinese dudes in Taiwan over at ASUS. They are working on a custom version of Android to run it on their Eee PCs which come with Windows XP right now. Google’s Carolyn Penner said that Android hasn’t been designed for phone exclusively. It is rather been intended to run on any kind of mobile device – this would include the Eee PC as well. Especially on such extreme mobile device it is quite important to use as less resources as possible. Microsoft’s Windows – no matter if it is XP, Vista or even WM Mobile – was never really fast.

HTC Magic w/o SIM Lock
I just found: HTC confirmed that the Vodafone / HTC Magic will not come with a SIM Lock like the T-Mobile G1. This is good news!

Signing an Android Application for Real Life Mobile Device Usage / Installation

Monday, January 19th, 2009

Android Certificate
If you want to publish an Android application you first need to write it :)

The result of your programming will be an .APK file which is the actual program binary of your application. However, the .APK file your compiler creates can only be used with the emulator on your desktop PC or Mac. You cannot use the same .APK file to install and run your app on your Android phone (like the G1, Kogan Agora, or else).

Why is that? Well, Google wants to protect its phone users from installing and running fraudulent software on their devices. Therefore, each and every application needs to be signed with a valid certificate that ensures where the application comes from. Meaning: the developer (you!) signs the application with his/her certificate to make sure it is always traceable where the application comes from. There are a bunch of more reasons to this so lets check out what Google is saying about this topic:

The important points to understand about signing Android applications are:

  • All applications must be signed. The system will not install an application that is not signed.
  • You can use self-signed certificates to sign your applications. No certificate authority is needed.
  • When you are ready to publish your application, you must sign it with a suitable private key. You can not publish an application that is signed with the default key generated by the SDK tools.
  • The system tests a signer certificate’s expiration date only at install time. If an application’s signer certificate expires after the application is installed, the application will continue to function normally.
  • You can use standard tools — Keytool and Jarsigner — to generate keys and sign your application .apk files.

3 Easy Steps for getting what you need to sign Applications
(this needs to be done once only)

  1. Create a keystore with your own keys and certificates
    First of all you need to create a keystore which stores your certificate. A certificate is always created by the developer himself without any interaction from Google. This actually means that Google does not approve certificates before you can use them for signing your application. (Note: other companies like RIM, Nokia/Symbian, Windows Mobile do such things.)

    Once you installed a Java SDK you can use the default keytool application to create your own keystore. A Java SDK is installed by default on Mac OS X machines and can also be installated additionally on your Windows PC or Linux machine. If you have Java SDK running on your system just go to any prompt and type in the following:

    Windows: START»Command
    $ keytool -genkey -v -keystore my-release-key.keystore -alias alias_name -keyalg RSA -validity 10000

    Windows: Mac: Terminal
    $ keytool -genkey -v -keystore my-release-key.keystore -alias alias_name -keyalg RSA -validity 10000

    You will be asked to enter a password for your keystore. Choose it wisely and remember it! You will need it every time you sign an APK file. Follow the instructions and finalize the creation of your keystore.

  2. Place the keys at a location that makes sense
    Choosing the right place for your keystore is quite important. Let’s imagine you write more than one application so it would not make that much sense to put this keystore into the project directory of the application you are currently working with. As I am using Mac OS X Leopard and Eclipse I got a project directory like /Users/YOUR_NAME/Documents/workspace/DialANumber. However, as mentioned before a more global approach might make so I copied the keystore to the directory:

    /Users/YOUR_NAME/Documents/workspace/androidkeys

    So we got our keystore prepared for signing now.

  3. Write a short script to make your life easier
    Just to make the life easier I wrote a short script which can be used each time to sign your Android APK file. You can download it below and place it in the same directory you placed the keystore at (see point 2).

    Download: Signing Script for Easy .APK Signing

Once you have done this we are ready for signing our application!

3 Easy Steps for getting your Application signed
(this needs to be done each time you build a binary that is going to be published)

  1. Build your application

    Right click your Android project in Eclipse and select Android Tools » Export Unsigned Application Package.... Follow the instructions and remember the directory your placed the .APK file at. E.g. cd /Users/YOUR_NAME/Documents/workspace/DialANumber/deploy/

  2. Go to your keystore & script directory

    cd /Users/YOUR_NAME/Documents/workspace/androidkeys/

  3. Sign your application
    In your androidkeys directory you need to execute:

    ./sign-mac-example.sh ../DialANumber/deploy/DialANumber.apk
    Enter passphrase:

    After you entered your passphrase the application should be signed.

You can now upload your app to your server and install it on an Android phone or you can even publish it on the Android Market!

Sources:

P.S.: The complete signing process (the part you need to do each time you sign an app) could be integrated better into Eclipse. I hope Google improves this in future. They could add an entry like Android Tools » Export Signed Application Package... so the developer just needs to enter the passphrase in a GUI dialog. This would make everyone’s life much easier. Perhaps a bored Eclipse PlugIn developer might want to write a plugin for this? It would make many people happy I guess :)