A la mobile, leading Linux systems platform and open source technology company for mobile devices, announced this week the first Android platform running on HTC Qtek 9090 advanced smartphone. Application demonstrated include : browser, phone dialer, audio player, maps, camera, games, calendar, contacts manager, calculator, tasks manager and notes. Below a screenshot of the a la mobile Android-based demo phone :

While all rumors and breaking news were about HTC to provide the first Android phones, a la mobile confirmed this orientation and got better : the first HTC phone using a complete mobile Linux stack based on Android.

“While mobile Linux has made steady progress in the industry since 2006, Google’s advocacy with the unveiling of the Android framework further substantiates the position of Linux as a major mobile operating system alongside Windows Mobile and Symbian,” said Pauline Lo Alker, President and CEO of a la Mobile, Inc. “However, despite the market enthusiasm about Google Android, many questions remain concerning the technical details, and skepticism exists concerning its readiness. As the leader in mobile Linux, we believe it is our responsibility to take the initiative to allay the ‘mystery’ and dispel any skepticism surrounding Android by first demonstrating a complete mobile Linux system stack, including drivers, middleware, and a suite of Android-based applications running on an existing advanced smartphone manufactured by one of the premier handset vendors in the market.”

It’s true that there are many missing information about Android platform itself until today, but according to a la mobile they are providing a complete mobile stack solution : device drivers, Linux kernel, system utilities, mobile middleware (such as security, device management, provisioning, etc.), an application framework (Android) that supports JAVA services, browser, and miscellaneous applications for the end device.

“Despite the open-source nature of the Android framework, developing a complete mobile system solution with customized, differentiated features continues to present major technical challenges requiring considerable time, effort, and resources — a barrier and reach beyond the scope of many handset vendors,” continues Alker. “Our mission is to remove the complexity for handset vendors and mobile operators to enable them to accelerate their device time-to-market, ensure high quality while reducing total development and device costs. The experience we have gained in putting together this demo will enable us to trim a device’s time-to-market by at least half!”

About A la mobile

Founded in 2005, a la Mobile has already established itself as the leader in developing and delivering one-stop, commercial-grade complete Linux system stacks for mobile devices: integrated, customized, certified, supported and maintained. The Company’s first Linux system offering - Convergent Linux Platform (CLP) version 1.0 - based on the Qt application framework by Trolltech, was first introduced in 2006 and adopted by several handset vendors.

Popularity: 47%

McObject announced today that Perst, its all-Java object-oriented, open source embedded database, has been verified as compatible with the Android mobile device platform backed by Google and the Open Handset Alliance.

McObject is offering the Android-ready Perst, as well as TestIndex, a demo application showing Perst and Android’s bundled SQLite database performing the same tasks side by side. Both are available as free downloads, with complete source code, from http://www.mcobject.com/android.

With Perst, users of Android-based phones will benefit from responsive, richly-featured embedded software made possible by a database system that delivers high performance and a small footprint, and by the efficiency that results from true Java developer-oriented features.

Perst stores data directly in Java objects. This eliminates the need for data-packing or unpacking code to map between the application’s data model and the database’s data model, as is required by relational and object-relational databases. The Perst API is flexible, easy-to-use and very fast compared to alternative commercial Java OODBMSs.

Perst is a very compact embedded database, with a core consisting of only five thousand lines of code. This small footprint imposes little demand on system resources. Moreover, Perst does not require administration. Perst supports transactions with the ACID (Atomic, Consistent, Isolated and Durable) properties, and expands developers’ coding efficiency by making Java objects as easy to use as possible.

For example, for access to objects, Perst implements 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).

In addition to its core functionality, Perst provides optional features such as garbage collection, detection of hanging references, automatic schema evolution, XML import/export utilities, master-slave replication support (with the option to run read-only queries on slave nodes), an SQL subset to filter elements of any collection, and integration with the AspectJ and JAssist AOP tools.

To read McObject’s complete announcement of Perst and TestIndex for Android, see http://www.mcobject.com/pressroom.php?step=3&article=91.

Popularity: 43%

Some of the very cool tools that popped out from Android developers, a Java applet called DroidDraw, which aims to provide a complete GUI creation tool for developers. OHM had an interview with Brendan Burns, who is behind the DroidDraw and Android-GL projects.

OHM : Can we know a little about yourself ?

Brendan : I’m a professor of computer science at Union College in Schenectady, NY. I just graduated a year and a half ago from the University of Massachusetts with a PhD in Robotics. Before grad. school, I worked in the software industry for a couple of years; mostly web-apps. I’ve done a bunch of different development over the years.

OHM : So you have a PhD in robotics, and you are interested into mobile development also ?

Brendan : I like to code. My term ended in the middle of November, and I wanted a project to keep me busy.

I had just taught graphics as my fall course and so I thought I’d play around and port some of the code from the class over to Android. Since I’d never done OpenGL on an embedded device, then I was thinking about building an app for the Challenge and I realized it was really annoying to build a GUI in XML. So I wrote the GUI builder.

OHM : Are you entering the challenge alone or in a team ?

Brendan : I’m not sure, probably by myself. I’m not 100% committed to entering. I have to come up with a really good idea, and so far my ideas are only ok.

OHM : So what about Android-GL, are you planning to build something with it ?

Brendan : I was thinking about it, but the renderer still has some bugs in it. While I was working on that I found a reported and number of them and I’ve seen reports from other people as well.

Also, I’m not 100% convinced that 3D plus mobile is the best solution, since most devices still don’t have accelerated graphics

OHM : how did you find coding on Android platform ?

Brendan : Its pretty easy I think. Its very similar to J2SE, more similar than J2ME which I did a little coding for.

There are some major differences between the OpenGL ES API and the regular OpenGL API - no glBegin(…)/glVertex(…)/glEnd() - that took some getting used to, but that’s the direction that the regular OpenGL API is headed also as far as I’ve heard. I think OpenGL 3.0 does away with that style of 3D coding. So it wasn’t a bad thing to learn more about.

OHM : so Java before Android was not much different than after Android ?

Brendan : Yeah, I think so, because I’m not in the mobile industry, and I don’t have a strong sense for the use of Java in that market. So I don’t really know if Android will mark a major shift toward Java or not.

One thing that is interesting about Android is that after two quick SDK releases, its slowed down !

You can tell that there are internal releases being developed, because the release stamp on the bottom of the docs pages keeps changing (Today its: Build m3-rc31 - 04 Dec 2007 17:47). So I’m curious about Google’s SDK release plans/schedule.

OHM : Which feature are you waiting for in the next release ?

Brendan : I’m waiting for Bluetooth support to be activated, So I can drive my Lego NXT Robot from Android !

Thanks Brendan for your time.

Popularity: 54%

Monday December 10th, the Linux Phone Standards (LiPS) completed the release of 1.0 specifications, to targets interoperability and marketability of Linux-based mobile phones through shared open standards and implementations. LiPS forum have been founded in 2005 and include operators and services providers from France, Italy and UK, in addition equipment and Chip manufacturers, and software vendors.

With Android release, LiPS published an FAQ on the differences between their standardization effort and OHA :

LiPS and Android both seek to reduce fragmentation among Linux-based mobile platforms. LiPS seeks unity through open standards, while Android/OHA does so through shared code.

Effort for Mobile linux stardization isn’t new at all, and beside the LiPS we count also the ELC Mobile Linux Initiative (MLI), Linux Mobile Foundation (LiMo), the embedded linux consortium, and the Gnome embedded initiative. There are also many others individual efforts by companies acting in the linux mobile business. According to ABI research, by 2012 there will be approximately 127 million Linux smartphones shipped each year.

It’s true that OHA and Android are boosted by Google, so should the LiPS profit from Android or should Android learn from the LiPS ?

Popularity: 30%

db4objects, provider of object oriented database for the .NET and Java, have just announced officially the availability of their solution db4o for the Android platform. Db4o is a distributed company with engineers from all over the world, but really hats off for their amazing work to make their entire solution ready for Android in record time. So for now, Android developers have full object oriented solution ready to use.

Java programmers are delighted with Android’s full object oriented platform they are frustrated by its bundling with a relational database, requiring cumbersome plumbing between objects and tables. db4o fills the gap by providing a fast and secure, native Java object database that makes storing objects and sharing of data between applications simple and easy.

It’s true that Android came with “Content providers” but as Carl Rosenberger, db4object’s Chief Software Architect, said in a blog post “this is not Java, it’s not object-oriented, it’s not even SQL.” Which is the missing element in Android platform : The object database solution.

This Tuesday we had the chance to talk to Nik Wekwerth, the VP of Marketing db4objects, and he told us about db4o solution for Android and how it could help developers to make fully advanced object oriented applications. “It’s all about simplicity” he told us, “In Java you prefer always to stay in Object Oriented. Object is more flexible than SQL, it doesn’t lock your memory”.

There are currently two applications ported to db4o, the Password Manager application and MapMe. It shows the capabilities of db4o and the simplicity of using objects to store and retrieve data. There is no real benchmark at this time Nik told us, but it’s clear from these two samples that using db4o is much easier and very simple to maintain.

Where can you use db4o ? “If you look at our customers, database usage is very large from planes, high speed trains, photocopiers, research …” Added Nik. DB4o proved its performance in many critical usage and their world class leaders customers like BMW, Boeing, Bosch, IBM, Intel, Ricoh, and Seagate, are certainly enough for Android developers to make sure that they have in hands a high level database solution.

Developers can write software applications that enable the backup of user data to a back-end server or their home PC. A consumer use case could be to start a game on the phone, freeze it, and continue playing at home in the evening. Business use cases include field force automation, data acquisition such as with RFID, and complex navigation systems that use locally cached geodata.

Db4o is open source under GPL, you can get started by downloading db4o for Android and start porting your current relational application, or start your new project in a fully object oriented environnement.

Popularity: 32%