Table of Content

About this project

Project Goal

The goal of the tinkerphones community is to provide a complete community driven and independently developed hardware, software and services platform for portable operation, that is as free and open as we can achieve it within our environment.

This includes kernel, drivers and application software a well as documented hardware, and open discussion.

It continues where the Openmoko project did end.

Reasons for this project

This project was originally triggered by a lot of complaints by the Openmoko GTA02 users that everything (CPU, GPU, Wireless) is so slow and far behind state of the art. Since we felt that we can dramatically improve that by building on the OMAP3 based BeagleBoard and using some off-the-shelf UMTS modem module, we started the GTA04 project as a motherboard replacement. After a while it became clear that a long lasting success of the project needs to deliver complete devices. Consisting of complete hardware, software and services. This is what the tinkerphones community aims to be: a roof and central point of contact for all the individual activites, being GTA04-Hardware, QtMoko, SHR, 3D case designs and 3D printing etc.

Philosophy about Hardware

Why do we develop and produce our own devices? Why don't we buy cheap $DEVICE from $MANUFACTURER and get it opened?

  1. $MANUFACTURER is not willing to provide schematics and documentation - unless we pay a lot of money
  2. $MANUFACTURER may change the device hardware for production optimization - and we are the last ones to be informed
  3. $MANUFACTURER may have choosen chips for which there is only a non-open driver - we try to avoid this (as good as possible)
  4. $MANUFACTURER may not have all features (e.g. sensors) we would like to attach, develop and write drivers for
  5. $MANUFACTURER produces anywhere and we do not know anything about it
  6. $DEVICE may be replaced by $DEVICE2 faster than we can engineer a kernel for $DEVICE

Licences / Openness

  • hardware schematics and user manual are usually open (CC)
  • u-boot, kernel, user-space software is usually under GPL or similar open source licenses
  • applications you write yourself can be closed source - if you know what you are doing

Contributions and Community

How can you, the (new) community member contribute?

Just hanging around and discussing

Even plain participation in discussion without contributing a single line of code is a very imporant part of a project. It helps to get new ideas, find clarifications, understand what others don't understand in the same way. Please let the core team and others know through the mailing lists, what you need and see as improvements. You can also add entries to the "Issues" list.

Contributing to development

  • write your own Applications
  • publish them through the Software Index
  • participate in the software projects (QtMoko, SHR, Replicant, ...)
  • make proposals for new chips to be considered
  • participate in the OHSW.org events
  • subscribe and use the mailing lists


Funding such a project isn't easy since we are small and independent (from banks and VC) and therefore don't have the purchasing power to get down the price for the components like others can.

Donations help to:

  • organise events like OHSW.org
  • fund hardware and software development (because people who do something have to pay their expenses like everyone else)


  • there aren't many rules
  • everything is allowed to say as long as it is kept friendly
  • what we don't want to see is illegaly leaked information (e.g. beyond legal reverse engineering) or links to such information



There is currently no formal organization behind tinkerphones. The domain is hosted and the project is driven by Goldelico and you. If we grow and need a more formal organization, one option is to found a tinkerphones e.V. (similar to OpenEmbedded e.V.) where there are members, elections, trustees, etc.

Contact and Social tools