AndroidExecutionEnvironment

Differences between revisions 1 and 2
Revision 1 as of 2009-04-29 00:00:35
Size: 4022
Editor: cpe-72-226-207-134
Comment:
Revision 2 as of 2009-04-29 00:02:26
Size: 3963
Editor: cpe-72-226-207-134
Comment:
Deletions are marked like this. Additions are marked like this.
Line 52: Line 52:
Should cover changes required to the UI, or specific UI that is required to implement this  * Window for running Android apps
 * Manager for installation of apk's outside the android environment
Line 56: Line 57:
Code changes should include an overview of what needs to change, and in some cases even the specific details.

=== Migration ===

Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.
 * Android will need a wrapper slipped under it to rewrite UI calls to a X11 window
 * All bits of android that manage networking and wifi should be disabled and removed
 * kernel support code will have to be merged in
  • Launchpad Entry: foo

  • Created: April 28th, 2009

  • Contributors: Michael Casadevall, Emmet Hikory

  • Packages affected: android, linux

Summary

This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples. ^?

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.

Rationale

This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

Assumptions

  • That the necessary Android kernel patches can be sanely merged into the Ubuntu mainline kernel
  • That we want to maintain ABI with Android and use their libc in the Android execution environment
  • That android actually uses /dev/fb*

Design

Android is not an X11 based environment, nor is it based on a standard userland. Therefore to support Android, we need to keep its execution environment separate from the main system, yet be accessible within Ubuntu

Implementation

Kernel Support

  • Some bits of the Android kernel will be merged
    • /dev/binder - acts as an IPC for Android processes

Android Execution Environment

  • Premade chroot with Android compiled for host environment (x86, arm, etc.)
    • This chroot will be built as a package. Android will require a new platform that doesn't built a kernel, but builds the rest of the environment in production mode
    • The android chroot will exist as /var/lib/android or something similar
    • Android will be modified to either replace the /dev/fb0 calls into an X11 hook, or otherwise wrap them in a way that allows the framebuffer to shown as a window
  • Will be available as an application
    • When run, this application pops open a window that will show the Android desktop
  • Android Package Files (apk) should be handled by the host system when double clicked; open source Android can't access the app marketplace thus installation should be possible from the host side
  • Only one AEE instance should be running at a given time
  • Apps for managing wifi, network and USB interfaces should be removed to prevent conflicts.

UI Changes

  • Window for running Android apps
  • Manager for installation of apk's outside the android environment

Code Changes

  • Android will need a wrapper slipped under it to rewrite UI calls to a X11 window
  • All bits of android that manage networking and wifi should be disabled and removed
  • kernel support code will have to be merged in

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.


CategorySpec

Specs/AndroidExecutionEnvironment (last edited 2009-05-26 09:53:45 by 80)