Android RenderScript on LLVM
by 廖世偉 博士

Is parallel programming hard? And if so, what can you do about it?
by Paul McKenney

Guides To Analyzing WebKit Performance
by Holger Freyther and Jim (jserv) Huang 黃敬群

Linaro and Android Kernel
by Andy Green

There are still some slides missing and I’ll keep updating here.

0xlab is going to co-host this event on 2011/04/28. Please refer to
http://www.digitimes.com.tw/seminar/android_1000428.htm
for more information. The introduction page is in Traditional Chinese, but some of the sessions are in English.

We think there are quite some Android summits out there, but most of them are about application development and business trends. We want to focus on the system development aspect from a more technical point of view.

Oh by the way, did I mention it’s free of charge?

Our Ideas

We believe open source is the right thing to do. Its contribution could be shared by everyone around the globe and allows people to build upon each other’s work. Plus, as a developer, coding makes much more sense if you can see the whole source. It’s something that makes our job as a software developer fun and meaningful.

On the other hand, we believe there is a chance in Taiwan to make open source profitable. We’re not talking about the conventional thinking that business should lock up as much as possible and only release source code enforced by the GPL-like license. We are talking about being a good community member and opening up as much as possible, not only the source codes, but issue trackers, documents and discussions yet still making money because of openness.

This is not a new idea, but already a practice. Companies such as Apple, Google, IBM, Intel, Novell, Redhat, Sun, etc. open up to attract more brain power and get more publicity. Contradicting conventional wisdom, openness is actually becoming a good business strategy.¹

We believe that there exists an ecosystem that combines both the open source developers and the hardware manufacturers in Taiwan. Our focus is to strengthen this connection and make it profitable for both parties.

So, how are we going to do this?

1. Opening up the non-essential part of the software development and working with the communities. For the open source world, this means more contribution and feedbacks. For the business, this means minimized development and maintenance effort.
2. Focus on the unique advantage that is a combination of hardware and software. The actual profit comes from selling the physical product instead of selling the software, which is not a financially good idea anymore.

Businesses should cooperate on #1, so they could put more resource to build their own unique advantages #2.

A healthy ecosystem is the way to make open source prosper. So, by making this ecosystem strong, we can effectively make open source stronger in Taiwan, which is something we have long waited for.

Our Works

Timeline

2009/4/27 – 0xlab launched, sponsored by AzureWave Technologies, Inc.

2009/5/15 – Project Android Eee PC launched. It aims to bring Android to Eee PC but the current focus is 3D acceleration support.

2009/6/2 – Computex. 0xlab demonstrated Beagleboard and Samsung 6410 connected to the WiFi/Bluetooth combo module from AzureWave.

2009/6/10 – FreedomHEC. Talked about "Qi – Lightweight Boot Loader Applied in Mobile and Embedded Devices".

2009/6/22 – Project android obex launched. It provides obex file sharing via bluetooth in Android.

2009/7/1 – First code drop. 0xlab now has the following projects on gitorious: MadButterfly, Android Eee PC, 0xlab’s Linux Kernel Tree, esuit and android obex.

2009/7/14 – Project 0xdroid launched. It’s the 0xlab’s Android distribution with Beagleboard as the reference platform.

2009/8/7 – The first release of 0xdroid, Beagle-cupcake-0×1.

2009/8/15 – COSCUP, the biggest open source conference in Taiwan. 0xlab is a sponsor with 4 talks and 1 lightening talk.²

2009/10/9 – Beagle-cupcake-0×2 released.

2009/11/3 – Project FreeBroid created. It enables FreeBSD users to do Android development.

2009/11/6 – Created our branch of Qi supporting omap3530 (Beagleboard).

2009/12/18 – Beagle-donut-0×3 released.

2009/12/25 – Merry Christmas! Android with 3D Effects is our Christmas gift.

Business Review

Hardware is becoming more and more standardized and keeps converging to a few solution providers. From the technical point of view, businesses have to stand out in software and the hardware/software integration.

However, the cost of creating your own proprietary OS is sky high and it requires a dominating power on the market to create enough acceptance, such as Apple. Solutions like Windows Mobile require royalty and the room to customize is rather limited because it depends on the kindness of its provider. Open source solution is a way out, but it’s not without its problems.

The Impact of Open Source

There are mainly three obstacles that are often missed by project owners:

1. The technical understanding of the code: most of the time the existing projects can only partially meet the requirement, so a certain amount of engineering resource is required to fill the gap. However, just because the code is opened does not mean it could be modified easily. A big, complex project can be very difficult to trace and understand. Inappropriate modification to the source code leads to maintenance hell, while the ability to change properly is rare. Without a thorough understanding, the exact effort to develop/fix/maintain the code could be hard to estimate, as well as the risk of the project.
2. Lack of overview: a Linux based product usually consists of multiple projects. These components may base on different technologies and work in different system levels with different functionalities. The way they interact with each other and the rule they play in the system could be hard to understand without prior knowledge of these projects. Thus, to obtain the overview of the system and to get a grip of the project status could become a challenge. The project owner must understand what’s the core advantage/business value of the project and the rest should be opened to save development effort.
3. Don’t know how to work with upstream: the best way to understand the source code and to get support is maintaining a good relationship with upstream. The best practice is working directly with them and merging back new functionalities and bug fixes. However, communication could be difficult because open source communities have their own development model, tool and culture, and will react rather badly if you don’t follow.
4. Legal issues: many businesses intentionally or unintentionally violate open source license. This puts them under the risk of being sued by people like our friend Harald Welte. These businesses need experienced people to deal with license issues, especially when you mix codes with different licenses.

How to Deal with It

1. Work with businesses that provide open source services. These are people who not only understand open source, but also bear the business value in mind. They have experience in commercial projects before, so they are very likely easier to communicate with.
2. Hire experts. If you can’t directly hire upstream developers, hire developers who are familiar with your target projects.
3. Train your own experts. You still need to find some ‘seeds’ first. This takes longer but in the end you get your own group.
4. Managers with rich experience in open source is a must.
5. Seek legal consult familiar with different open source licenses.

New Challenges from Android

1. Multilayer debugging: Android is a complex combination of various technologies. Most of its platform services are a mix of different computer languages and run across multiple layers. Debugging (inside the platform itself, not the application layer) often requires tracing back and forth between the java framework and native libraries across different processes. This is significantly harder then tracing the old fashioned pure c/c++ codes.
2. Follow the fast paced upstream: Android evolves really fast, i.e. two major releases per year. This means your product will become outdated during the development phase and you will have to do the catching up and the product development (polishing, bugfixes, new features, etc.) at the same time. This will be a new challenge to a software team.
3. Knowledge of various technical areas: as mentioned before, Android is a complex mix of different technologies. Peripherals, power management, mobile phone protocols (2G/3G/…), graphic 2D/3D acceleration, virtual machine (Dalvik), toolchain (bionic, gcc, …), the design of user interface, certifications, etc. , each one of these could be a big topic. Android provides a basic platform to build on, but the entry barrier to build on top of it properly is still high, if not even higher.

Where We Stand

0xlab has an unique standing facing all all these new challenges. Most of us are both professional engineers experienced in shipping end products and active open source developers.

We consist of experts in different areas. Experience in major smartphone brand/ODM R&D, User interface, virtual machine, compiler, low-level kernel development, multimedia codecs, Mesa 3D contributor and Openmoko, the world’s first open phone, gives us everything we need to do Android platform development.

We offer the following:

1. Reduced development effort by working with the communities. Short time-to-market. Automatic testing suite to ensure quality.
2. Contribute back to the industry to make a bigger pie.
3. Cutting edge technology by following upstream development closely.
4. Commercial friendly license because we use the same license as Android.

Work with Us

We are accepting the following possibilities if they are technically related to Android:

1. Community: follow the convention. Join our mailing lists, chat on IRC, fire questions and share your knowledge just like any other open projects. Get helps for free by helping others.
2. Project: we’re accepting offers to work on a specific project as long as our work could be opened as well.
3. Consulting: contact us to get more info.

For Developers

0xlab is a virtual organization consists of full time employees and freelancers. We welcome passionate developers to join us. It doesn’t matter if you’re employed or self-employed as long as you share the same idea with us.

For Businesses

We encourage businesses to change mindset and open up non-essential parts to gain more developers’ eye balls. The more eye balls you get, the more powerful you’ll likely become. You don’t need to own every part of the software to sell the product. You just need your own unique advantage and that’s where you should really focus on.

Background

Why Android

Android is the event of the year with regards to mobile devices, which is our primary interest. Many OEM/ODM manufactures and brand names in Taiwan have put development resources into it, while the government agencies provide budgets to encourage Android research and development. We want to reuse as much resource as possible, so we picked it as our development focus.

Beagleboard

One of the problem we faced when 0xlab was just getting started is that it’s not easy to get a hardware platform. We picked Beagleboard because it’s modern, powerful, cheap and open with an active community. We do not have any business relationship with TI, but we do like their idea of opening up hardware. However, we are indeed the world’s no.1 RMA customer with the highest return rate since we broke a lot of boards while trying to do hardware modifications. We are software developers, after all…

Beagleboard is the platform we focused on, but it’s not the only platform we are interested to work on. We welcome people sending us their cool gadgets. If you want to find out what Android can do on your device, send us some sample. We may work on them and try to keep them in one piece.

More Info

We use git as our primary SCM, and use gitorious to host all of our projects. Some projects with the same name were created on google code as well for issue tracking and an easier to use wiki.

0xlab.org is hosted on our own cost and acts as an entry point. It provides basic information about us. The most interesting page is perhaps Planet, since it acts as a aggregation of our blogs.

Here is a list of all the rss feeds about our blogs and projects:

• http://0xlab.org/atom.xml
• http://code.google.com/feeds/p/0xdroid/updates/basic
• http://code.google.com/feeds/p/0xlab-kernel/updates/basic
• http://code.google.com/feeds/p/esuit/updates/basic
• http://gitorious.org/0xdroid.atom
• http://gitorious.org/0xlab-kernel.atom
• http://gitorious.org/android-eeepc.atom
• http://gitorious.org/android-obex.atom
• http://gitorious.org/esuit.atom

About 0xlab

0xlab is founded on 4/27, 2009 in Taiwan by a group of enthused FOSS³ developers, some of the finest. Most of its members are of Linux background with rich experience in embedded systems and created/contributed to various open source projects such as Linux kernel, opkg, OpenOCD, OpenEmbedded, QT Extended, Packagekit, FreeType, Kaffe and LXDE.

They met each other in the local FOSS community and at the startup Openmoko, from where they became familiar and connected with developers worldwide. This differentiated them in pan-Asian because they stay much closer with the mainstream and are actively attending the ongoing development.

The list of its current members could be found on our gitorious page. 0xlab aims to be a virtual organization, but at the moment it mainly operates in Taipei. 0xlab could be reached at:

Contact Us

• IRC: #0xlab
• mailto:contact@0xlab.org

Links

• http://0xlab.org/
• http://gitorious.org/+0xlab
• http://www.youtube.com/group/0xlab

Mailing Lists

• http://groups.google.com/group/0xlab-devel
• http://groups.google.com/group/0xlab-discuss

2. http://jserv.blogspot.com/2009/07/0xlab-coscup-2009.html

3. Free and open source software, http://en.wikipedia.org/wiki/Free_and_open_source_software

In the world of open source, you gain credibility by contributing. The more credibility you have, the more powerful you become. Basically 0xlab’s initial and first goal is to open up our development, establish our credibility and get more publicity. Our policy to open up as much as we can turns out to be more beneficial then we have expected. Since we put our code in the open, any individual or business entity who is interested in us can evaluate our results directly. This leads to direct communication channel to developers inside some big companies such as Google, Qualcomm (Innovation Center), Broadcom, TI, EMBINUX (SQL Star) and Motorola, or even cooperation in business level.

We found out that since we don’t sell software for a living, but instead we use software to add value to the hardware (made by AzureWave), the work we did is actually beneficial to our sponsor, so they are willing to keep supporting us. This means a lot (in my opinion), since nobody in Taiwan believes that people can write open source for a living, until we proved them wrong. I believe we’re reproducing a ecosystem, which is not uncommon in Europe and US, but never shows up in Taiwan before.

Since we can support ourselves now, what’s the next step? I can’t disclose it, but suffice to say we are planning to take this a step further. We hope, once we proved that business can make money from openness, more Taiwanese companies can understand and duplicate our open source model, thus creates more modern software developers and stay closer to the world.

You can find all of our source code at: http://gitorious.org/+0xlab. Here is a brief introduction of each project:

1. MadButterfly: a git clone of the original project. The real project is hosted at assembla. MadButterfly is very likely to be the base of our 2D UI framework. It’s based on SVG instead of traditional toolkits such as gtk or kde, so it will give the UI designer a lot of space to unleash his/her creativity. The main developer’s (Thinker) blog is here.
2. Android Eee PC: it aims to ease the porting of Android to Eee PC. At the moment the most interesting thing is the 3D acceleration structure on it, which can use the existing hardware driver in Mesa. Check this video to see what it can do. (blog)
3. 0xlab’s Linux Kernel Tree: it contains several branches for different platforms, like Omap3, SMDK6410, and may be more in the future. Also, all of them are intended for being able to boot into Android. We tend to use the Beagle Board (OMAP) as our main development platform because it’s cheap and open.
4. esuit: the Embedded System Unit/Integrated Test cases framework. It aims to provide a unified method to verify the functionalities of a hardware platform. This project is in planning phase, so no source code is available yet.
5. android obex: it provides obex file sharing in Android. (blog)

From now on, we will direct all of our technical discussions to the 0xlab-devel mailing list. Plus, IRC #0xlab is the place we usually hang out. If you want to reach us directly, mail us.

make pdk pdk_all

in your top repo dir. You can find the pdk doc in out/target/common/docs/online-pdk . If you open index.html directly you will find the css is all messed up. The quickest way might be moving the directory to /var/www, install one web server (I use thttpd) then open http://localhost/online-pdk/ .

The document is far from complete but it’s still a good reference to save a lot of time.

First of all, we have been fairly busy recently. If you have tried to port Android to other platform, then you will know it’s not an easy task. We have some familiar porting issues, such as the documents provided by hardware manufactures are either vague or incomplete, the BSP is outdated (ancient), code is a mess or even completely unusable. And we also have some new issues, such as Android platform’s big code base and lack of proper document (I’m talking about lower level here), or what Goggle said in their presentations is way different then what’s in the code, and I don’t even want to start with many hard-coded assumptions about hardware (G1), etc.

Rant aside. What’s been keeping us busy:

• Port several wireless modules to several popular platforms.
• Graphic acceleration.
• Multimedia enrichment. (Reads: port other open source codes)

I’m not going to dive into details here. We will do a code drop sometime in June, and our members will blog about their work, so the technical details will be revealed then. We will also open up our development mailing list, so people can discuss there.

Next question is: how to join force? The answer is quite simple: just like any open source project. After the code drop, try it out, report bugs, send us patches, join mailing list, talk on the IRC (#0xlab), etc. – all the usual stuffs. That also means we won’t work on any specific product. So, if you’re interested in developing android based product, send your *own* developers to join and grow with us.

Now, advertisement time: join FreedomHEC Taipei, Matt and Jserv will talk about bootloader there.