Difference between revisions of "Android under webOS on Touchpad"
Jump to navigation
Jump to search
m |
|||
| Line 1: | Line 1: | ||
| − | = Project | + | == Project goal == |
| − | To implement Android (probably CyanogenMod 7) on the | + | To implement Android (probably CyanogenMod 7) on the TouchPad as a card using a <code>chroot</code> 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. | |
| − | This will allow use of Android apps (hopefully including market) while not having to leave webOS or reflash the | + | : However, it will probably not have 3D support, so people whining for "romz" will probably not be fully satisfied. ;) |
| − | |||
| − | However, it will probably not have | ||
== Required pieces == | == 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. | |
| − | |||
Revision as of 10:49, 4 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.