Posts tagged as ' Android ' ...

Posted By Tommy

Create new Froyo Virtual Device for Nexus One


So it’s time to start developing Android apps, but you have a Nexus One running Froyo 2.2. What are you supposed to do at the stage “Create new Android Virtual Device (AVD)”? That’s exactly the question I was tackling today. In fact it’s not too important, since you would be developing for all types of Android phones, not just Nexus One, but in principle it seems right to set up the emulator exactly for the Nexus One.

So the first thing to do when creating a new virtual device is to give it a name. I was thinking about calling mine “NexusOne” but then I thought I should add a little more detail. However, there is a restriction in the naming policy: you are only allowed to include letters and numbers, no spaces or decimal points (but yes to underscores). This means the logical name “Nexus One Froyo 2.2” is no good. Finally I settled on “Nexus_One_Froyo_2-2”. I selected Target: “Android 2.2 – API Level 8”. If you don’t have it as an option, you need to run the Android SDK updater.

Next select the size of the SD card. I put 2000 MiB.

And the skin of the Nexus One would correctly be WVGA800, which corresponds to 800 x 480 resolution. Technically it’s a slightly different since the particular screen used, but it’s effectively the WVGA800.

Next there’s a bunch of settings to add. I’ve seen some people suggest you need to add all the hardware components manually, but according to the following chart most of the stuff is there by default. (Chart is from

Characteristic Description Property
Device ram size The amount of physical RAM on the device, in megabytes. Default value is “96”. hw.ramSize
Touch-screen support Whether there is a touch screen or not on the device. Default value is “yes”. hw.touchScreen
Trackball support Whether there is a trackball on the device. Default value is “yes”. hw.trackBall
Keyboard support Whether the device has a QWERTY keyboard. Default value is “yes”. hw.keyboard
DPad support Whether the device has DPad keys. Default value is “yes”. hw.dPad
GSM modem support Whether there is a GSM modem in the device. Default value is “yes”. hw.gsmModem
Camera support Whether the device has a camera. Default value is “no”.
Maximum horizontal camera pixels Default value is “640”.
Maximum vertical camera pixels Default value is “480”.
GPS support Whether there is a GPS in the device. Default value is “yes”. hw.gps
Battery support Whether the device can run on a battery. Default value is “yes”. hw.battery
Accelerometer Whether there is an accelerometer in the device. Default value is “yes”. hw.accelerometer
Audio recording support Whether the device can record audio. Default value is “yes”. hw.audioInput
Audio playback support Whether the device can play audio. Default value is “yes”. hw.audioOutput
SD Card support Whether the device supports insertion/removal of virtual SD Cards. Default value is “yes”. hw.sdCard
Cache partition support Whether we use a /cache partition on the device. Default value is “yes”. disk.cachePartition
Cache partition size Default value is “66MB”. disk.cachePartition.size

Thus according to the chart we should add “Camera” and the 5.0 megapixel camera on the Nexus One corresponds to 2592 Maximum Horizontal Camera Pixels and 1944 Maximum Vertical Camera Pixels (The exact number of pixels is a guess of mine based on the 5.0 Megapixels, but unless you’re doing some hardcore testing I think it will be fine). Set the Device RAM Size to 512 MB for the Nexus One.

Ok, that’s about it. Now click “Create AVD” and the program will appear to freeze for a while. Finally, the AVD will be created and Nexus_One_Froyo_2-2 is located in the .android\avd folder.

Posted By Tommy

Building Ångström | The Ångström Distribution

Building Ångström | The Ångström Distribution.

Now that I have OPIE installed on my PDA (ASUS MyPal A716), I feel really happy. However, after a little more research I realize that OPIE hasn’t been officially maintained since about 2006. I contacted the guy who maintains the OPIE image for the A716, and he kind of suggested if there was any work to be done, it would be on the OPIE end.

Finally, I discovered that another group, Angstrom, has been working towards making Linux avilable for embedded devices such as the A716. And since they support the OPIE GUI, that’s cool. The next step, then, is for me to see about running Angstrom on my A716. Despite it’s age, the A716’s processor is a 400 MHz ARM PXA255, still a strong processor, I believe.

An additional thing that’s interesting about Angstrom is that people have succeeded using it to run Google Android with a Zaurus, a PDA which happens to have a PXA255. The question is, how much time do I have? My first step will be to get Angstrom running on the A716… Then, I’ll take it from there. ‘ll keep you posted.

Android Netbooks: Fact or fiction? | Nanotech – The Circuits Blog – CNET News.

Just as I expected, people are realizing that Google’s Android isn’t just for cellphones. It’s an operating system that’s built with openness in mind, so that means it can run on Eee PC. With one big advantage: Developers can write in Java and run their code on any Android. Only drawback right now, there aren’t many Androids around.

Posted By Tommy

Android Eyes the Enterprise – PC World

Android Eyes the Enterprise – PC World.

Google’s Android OS is going to get some software that enables viewing of MS Office documents. I looked for an HTC in Taiwan that has Android, but I guess I’m going to have to wait for a while until something like that comes here.