A Quick security update of the Android SDK have just been released fixing mainly a security issue involving handling of image files. Android SDK version m5-rc15 is available for download. There is no API change or new features introduced in this release, but it is recommended to upgrade.

The update doesn’t change any of the Android APIs or introduce any new ones. Eclipse users don’t need to update the ADT plug-in either. Once you’ve unzipped the file on your machine, you will want to update things like your PATH variable and, if you’re using Eclipse, the SDK location setting for ADT (hint: Preferences > Android).

Notice that if you did not yet upgrade from m3 to m5, you might take a look at the upgrade instructions and then the API changes overview. For even more details on the changes, there is an API differences report.

No big changes should be expected after the m5 release and the major API change in the SDK, in the next months at least. There will be more bug fixes and API improvments until we get hands on the first Android Handset.

Popularity: 72%

McObject has added support for the KD-Tree, a database index with uses in spatial and pattern-matching applications, to its Perst open source, object-oriented embedded database system available for the Android mobile development platform.

The new k-dimensional tree or KD-Tree index adds a structure in Perst that stores and manipulates point objects in a k-dimensional space by partitioning that space. Practical uses include computer graphics, geographical information systems and biometric applications such as fingerprint matching. In addition to their efficiency in handling multi-dimensional data, KD-trees are useful in “normal” applications in which query predicates contain various combinations of object fields. For example, KD-Trees are used to construct Query-By-Example (QBE) features in which the user selects fields and values, and the application builds database queries based on these selections.

While many Java databases offer limited index support, Perst implements rich options for data access, including specialized collection classes optimized for different data layouts and access patterns, including:

• Classic B-Tree implementation;
• R-tree indexes for spatially-oriented applications such as GIS and navigation;
• Main-memory database containers, based on T-Tree indexes, optimized for real-time memory-only access;
• Patricia Trie index, which speeds searches in networking and telephony applications;
• TimeSeries class to efficiently deal with small fixed-size objects;
• Specialized versions of collections for thick indices (indices with many duplicates), and bit indices (keys with a restricted number of possible values);
• KD-Tree indexes

For McObject’s announcement of KD-Tree support see http://www.mcobject.com/pressroom.php?step=3&article=93.

For general information about Perst for Android, including links to the open source, complete Perst database source code, and to McObject’s Android-ready TestIndex database benchmark, go to http://www.mcobject.com/android/.

Popularity: 84%

Iambic is one of the already established mobile software companies that started developping for the Android platform. You have probably met with one of their Android applications GoogHelper or Tipper that we announced in previous posts . Adriano Chiaretta - Chief Operating and Information Officer at Iambic - accepted to answer our questions and share their development experience with Google Android.

Q1 : We have introduced iambic in the last weeks to OHM readers with GoogHelper and Tipper, What can we know more about the company ?

iambic was founded at the end of 1993. At the time, the company had two people developing solutions for one of the very first PDAs, the Apple Newton. Making it easy to do time and expense tracking while on the go was the primary focus. Later in 1994 the company expanded its area of focus to include personal information management (PIM). As a result, Action Names was born. Through the years, that application evolved to what is now Agendus, currently available for Palm OS, Windows Mobile, Symbian, as well as Windows desktop PCs.

During the last few years, we expanded our portfolio of Windows Mobile applications — with the development of titles that had a broader reach in areas that include: personal productivity, including vehicle managers, health and diet applications, and call management and action taking. In a nutshell, our mission is to empower users to make the most out of their time wherever they are –on the go or at the desk–, through the creation of easy-to-use, yet powerfully customizable solutions.

Q2 : Why the interest to create applications for the Android platform ?

Since the announcement of the new Android mobile OS and related SDK, we have been intrigued by what it promises to deliver at a variety of levels. From a development standpoint, being able to access any tiny detail of the platform without having to jump through hoops is a great time saver, and also saves from countless “back and forths” with device manufacturers for updated handset specific SDKs.

Having the ability to closely interact with the built-in applications and related data storages (love Sqlite and I’m glad it’s the storage engine of choice of Android) is another definite plus. This without forgetting the new operating system is backed by a rather consistent number of prominent companies, leaders in their industry and market specific area. All this, of course, so far on “paper” or “bits” if you want in the form of a quickly evolving SDK, and slick emulator. Will the promises I mentioned above become reality when the first handsets hit the market? I truly hope so.

Q3 : How many developers are currently working on Android projects ? Did you hire or is it from the current dev team?

We have a developer fully dedicated to Android projects, from the current development team, while another one is playing with the SDK “just for fun” — creating small tools so to speak. I’m getting my hands dirty too. I’ve been checking out examples, documentation, and thinking about what else we can creatively use out of what made available through the SDK.

Q4 : Are you just porting current iambic mobile projects to Android or planning new ones also ?

So far, in order to start getting our “feet wet,” we ported a few titles while exploring the possibility of the platform, along with the expected rough edges of the SDK.

Q5 : Any commercial application for Android in your plans ?

We do plan to release commercial solutions for Android. GoogHelper and Tipper themselves might get revised and “enriched” to become commercially distributable.

Q6 : Will any of your iambic projects will take part of the Challenge ?

Yes, we are currently working on a project we plan to submit to the Developer Challenge.

Q7 : How do you compare development under Android to other mobile platforms ?

So far we are finding the development for Android a much more streamlined experience compared to other platforms. I believe this is because the operating system is young (there are no phones based on it yet), and therefore getting up and running with the development environment is extremely quick and straightforward. Unzipping the latest Eclipse, the Android SDK, getting the Android plug-in setup in Eclipse and being off stepping through a few breakpoints while debugging the app on the emulator took less than 15 minutes. On mature mobile platforms such as Palm OS, Windows Mobile, Symbian, or BlackBerry the process of installing a development environment, main SDK, various licensees’ customizations, etc. can easily take half day.

That said, the SDK itself is clearly a work in progress. Its documentation is sort of “hit and miss” at the moment and definitely not super clear. And a few of the API calls are not working as expected. Then again, this is the type of stuff I’ve seen in SDKs that are much more mature, so no real news there. It often comes down to looking around forums and message boards for solutions, and spicing up the approach with some trial & error.

The latest SDK released just a few days ago is quite a step forward, although it introduces a variety of changes both from an API/development standpoint as well as from a user interaction / usage model standpoint. The latter according to what the UI showcased by the emulator is telling us. We are investing quite some time now getting the projects we are currently developing up to speed with the latest SDK. Hopefully we won’t see a similar rather deep change in the coming updates.

Popularity: 90%

This week all eyes are on the Mobile World Congress 2008; probably that we will see very soon a Weekly Android Handsets on OHM. We’ll be back on this event with more details, but today we have another selection of Android applications including a tipper, a translator, in addition to OpenIntents - the open interfaces project for Android.

OpenIntents

OpenIntents defines and implements open interfaces for improved interoperability of Android applications. Another interesting Android project which aims to make your mobile experience unique on Android handsets. The project is very open; anyone can participate into OpenIntents with code or ideas. Many interesting experiments and applications are already available with OpenIntents; most notable the Sensor Similator, and the central shopping list.

Tipper

Tipper is the second cool utility from iambic, a handy “split tip” calculator for dining out. It saves time and effort by calculating the total and displaying the actual tip amount.

SeaThreePO Android Translator

Even if it’s a quick Synday project as David announced on his blog, SeaThreePO is a pretty useful Android translator. SeaThreePO is based on dims’ code and using simply Android XMPP and Google translation bots.

Popularity: 100%

This Thursday, Reuters had a news about ARM to demonstrate a prototype of Google Android mobile phone platform in action during the Mobile World Congress 2008 this monday in Barcelona. ARM, the British chip designer, got 7 billion from 10 billion chips shipped into mobile devices.

ARM will be showing advanced technology enabling the “Full Web in Your Pocket” experience, including the latest ARM® Cortex™ family of processors; the ARM Mali™ graphics stack; and the newest RealView® development tools. ARM technology is powering over 90 percent of the handsets on display at Mobile World Congress 2008, including graphics-rich, large-format, low-power Mobile Internet Devices.

We got the confirmation from ARM, if there will be really an Android phone to be shown Monday :

“ARM will have a demonstration of an ARM Powered prototype of the Android platform from the Open Handset Alliance.” an ARM spokesperson told Open Handset Magazine.

Currently there is no image or photo to show, but visitors of the Mobile World Congress 2008 will have the chance to see the first Android-based mobile phone powered by ARM. We will keep you updated as soon as we get more information.

Popularity: 34%