• Announcements

    • PaulOBrien

      Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such software Nintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance) CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission) ROMs must give full credit to the original author ISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • PaulOBrien

      Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
Sign in to follow this  
Followers 0

A worthy manufacturer

2 posts in this topic


I just plan to buy some Android hardware. Originally I thought a phone would be best, but seeing tablets start from $99, I just can not imagine how throwing in a GSM raido triples the cost, as phones start form around $250...

Anyway... as 2.3 comes out and most manufacturers do not even bother to upgrade their products to 2.2 a question arises: Is there any manufacturer who has their firmware open-sourced, so the community would not need to get the compiled drivers form some similar phones?

And is there any such phone accepted by a decent developer community, who bother to recompile and push out upgrades regularly?

I'm new with Android, but I have some miles in my boots as a developer. I just don't understand why the 2.2 -> 2.3 upgrade is such a painful process. Android itself is open-sourced AFAIK, and I don't think the new version requires the individual drivers to change their API-s significantly (correct me if I'm wrong). The only obstacle I can think of comes from the closed-source nature of drivers provided by manufacturers (such as LG or Samsung).

Any suggestion is welcome.

Edited by vbence

Share this post

Link to post
Share on other sites

Two years passed without a single answer. I think I will share my understanding of the Android world and the root of the problems we all share. If you are interested in the topic you will find Steve Kondik's talk about CyanogenMod and its relation to manufacturers interesting. It is revealing and very enjoyable too.

Steve Kondik's presentation:

Q and A session:

Back to the original question: There is currently no such manufacturer. Causes:

  • SoC manufactureres (Qualcomm, Samsung, Nvidia, TI etc.): today's phones are driven by a so called system-on-a-chip, a single chip acommodating CPU, GPU, memory and other controllers which are needed for an embedded computer. Their SDK's are not public, their "drivers" are neither opensource nor distributed in a usable binary way (due to "competitive reasons").
  • Poor design of Android: Manufacturers want their phones to have the best possible performance (and you want that too). But the insufficient design of Android's (Linux-based) core makes them hack the living hell out of the kernel, like add custom parameters to function calls to directly access some things and circumvent the kernel's original logic. - This way the "driver" can not be put in a generic kernel because it is only compatible with the vendor's custom kernel.

    Not-so-terrible manufacturers:
    • Google: their phones (Nexus) have the longest lifespan in terms of firmware support.
    • Sony: they recently open-sourced their sensor framework and released the drivers they could (in binary forms).

      The future:

      • There are some signs that Google may open a Nexus-like program for all the manufacturers, so everyone will get early access to the next version of Android. - Maybe they will accept patches too.
      • With better engineering, and along the way kernels might become compatible across manufacturers.

      The dark future:

      [*]In the meantime (with Jellybean) Google closed the possibility of extracting binaries from a running device (the way modders could get their hands on binaries).

      Disclaimer: I might be wrong in one or more things, please add your thoughts.

Edited by vbence

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.