Difference between revisions of "Android under webOS on Touchpad"

From WebOS Internals
Jump to navigation Jump to search
m
Line 9: Line 9:
 
* The kernel may need to have Android bits compiled in. This could be added to the standard UberKernel without impacting regular operation.
 
* The kernel may need to have Android bits compiled in. This could be added to the standard UberKernel without impacting regular operation.
 
* The Android graphics and devices need to be rerouted to use SDL and other PDK-supported APIs.
 
* The Android graphics and devices need to be rerouted to use SDL and other PDK-supported APIs.
 +
 +
==References==
 +
*[http://bitbucket.spencerelliott.ca/palmdroid/wiki/Home Palmdroid project!] The end goal for this project it to be able to run Android applications within webOS using the Dalvik virtual machine.
 +
***[http://forum.xda-developers.com/showthread.php?p=17558046#post17558046 (ANDROID) Official Palmdroid Development Thread]

Revision as of 08:32, 30 September 2011

Project goal

To implement Android (probably CyanogenMod 7) on the TouchPad as a card using a chroot execution environment. Perhaps eventually putting each Android app as a card.

This will allow the use of Android apps (hopefully, including market) while not having to leave webOS or reflash the TouchPad.
However, it will probably not have 3D support, so people whining for "romz" will probably not be fully satisfied. ;)

Required pieces

  • The kernel may need to have Android bits compiled in. This could be added to the standard UberKernel without impacting regular operation.
  • The Android graphics and devices need to be rerouted to use SDL and other PDK-supported APIs.

References