All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim.yaghmour@opersys.com>
To: linux-kernel@vger.kernel.org
Subject: Headless Android (no FB required)
Date: Wed, 15 Feb 2012 14:41:22 -0800	[thread overview]
Message-ID: <4F3C3492.9080207@opersys.com> (raw)


As an FYI, I thought some of you might be interested in knowing that 
Android's user-space can be modified to run on headless systems (i.e. 
without a framebuffer.) IOW, you can configure the FB stuff completely 
out or have a kernel port that doesn't have an FB (yet?) and still run 
the Android use-space.

I've put this up as part of the Cyborgstack project:
$ repo init -u git://github.com/cyborgstack/android.git -b headless
$ repo sync
$ ...

The relevant presentation from the Android Builders Summit is here:
http://www.cyborgstack.org/www.cyborgstack.org/sites/default/files/headless-android-120214.pdf

Essentially, Headless Android is the AOSP but WITHOUT:
- SurfaceFlinger
- WindowManager
- WallpaperService
- InputMethodManager

It gives you is all the Android framework but for ui-less systems (no 
FB.) What it means, is that, save for Activities, you can use the 
standard Android development tools (Eclipse, SDK/NDK, etc.) to create 
apps that use:
- ContentProviders
- Services
- BroadcastReceivers

Why would you want this instead of using "Embedded Linux"? Honestly I 
was very skeptical when some developers first mentioned to me that they 
were interested in doing this. I was in fact very dismissive of it. But 
I kept getting more and more inquiries about this. So I decided to bite 
the bullet and give it a try.

Now that I have, I think there are 2 clear benefits to using this 
instead of "embedded Linux":
1) you get one platform for all your device development, whether it has 
a UI or not
2) your devices become programmable by any developer that knows the 
Android API (and, as you may know, there's growing number of those.)

That said, what I've done is very much a proof of concept. It's in fact 
a dirty hack at this point. Please don't ship this just yet. It needs a 
lot more eyeballs and certainly a lot more work. But, it's good enough 
to give you a taste of what's possible and allow you play with it.

Cheers,

-- 
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour

                 reply	other threads:[~2012-02-15 22:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F3C3492.9080207@opersys.com \
    --to=karim.yaghmour@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.