Aros/Platforms/Installing on Android
Android-hosted port is a new, progressing development. Currently a number of issues exist, they are in the process of fixing.
Android OS can be viewed as a subset of Linux, so functionality of this port is the same as of generic UNIX-hosted port.
DOWNLOAD aros sources and others from here
In order to install AROS to your Android device, do the following:
- Extract the archive.
- Inside the archive you'll see AROS directory. Copy its whole contents to the SD card (or whatever else removable media your device uses.)
- Install the supplied AROSBootstrap.apk in your device.
Please note that minimum required Android version is 2.2.
Since Android OS has no command line, you can't watch debug output in real time without any external tools. However, you can redirect it to a file using bootstrap's own functionality. In order to to this you'll need to edit AROS/boot/AROSBootstrap.conf file and add 'logfile <file_pathname> option to it.
In a similar manner you may pass command line options using "arguments <your-options>" option in AROSBootstrap.conf.
Android OS currently supports i386 and ARM processors. AROS can be built for both these architectures, however currently only ARM build is in production. i386 version was not tested because no test environment was available.
A vast majority of modern ARM devices has ARMv6 or better processor with VFP floating-point unit. This configuration is currently the minimum requirement to run AROS. However, some Android devices are available on the market, whose processors are below this requirements. Known non-working processors are:
- Qualcomm MSM7225 (ARMv6 but no VFP at all)
- VIA 8650 (ARMv5)
This is a list of test results on various hardware and Android OS versions:
|Device name||CPU core||Android OS version||Linux kernel version||Test results|
|Ainol NOVO7 Aurora 2||1.5 GHz ARM Cortex A9
|4.0.3 (ICS)||Black screen, system halts during bootup|
|Archos 70||1 GHz ARM Cortex A8
|2.2.1 (Froyo)||Working fine. CacheClearU() is known to trigger host system reset (hardware-specific glitch)|
|Google Nexus One
|1 GHz ARM Cortex A8
|2.3.4 Build GRj22||2.6.35-7-59463-g52630a3||Working fine|
|HTC Desire||1 GHz Qualcomm Snapdragon (QSD8250)||2.2 (Froyo)||22.214.171.124||Working fine|
|HTC Evo Shift 4G||800 MHz Qualcomm Snapdragon S1 (MSM7630)||2.2 (Froyo)||126.96.36.199-gee557fd||Working fine|
|HTC One XL||1,5 GHz Qualcomm Snapdragon S4 Dual Core (MSM8960)||4.1.1 (Jelly Bean,
Viper XL 3.2.3)
|3.4.10-g240d4d5root@abm033#1SMP PREEMPT||Working fine|
|HTC Sensation||1,2 GHz Qualcomm Scorpion
HTC Sense 3.0)
|Error in C:Mount during DEVS:DOSDrivers processing|
|HTC Wildfire A3333||525 MHz Qualcomm Snapdragon S1 (MSM7225)||2.2.1 (Froyo)||188.8.131.52-g8f75634 htc-kernel||"Illegal instruction" crash. The processor is below AROS minimal requirements.|
|LG Optimus Black||1 GHz ARM Cortex A8
|2.2.2 (Froyo)||184.108.40.206||Working fine|
|LG Optimus One (P500)||600 MHz Qualcomm ARM1136EJ-S||2.2.2 (Froyo)||Working fine|
|LG Optimus Speed||1 GHz ARM Cortex A9
Dual Core (AP20H)
|2.2.2 (Froyo)||220.127.116.11-dirty||Black screen, system halts during bootup|
|RoverPad 3W T71D||1 GHz ARM Cortex A8
(Allwinner Boxchip A10)
|4.0.3 (ICS)||3.0.8+ (inet_hxj@InetSoftware) (gcc version 4.5.1 (Sourcery G++ Lite 2010.09-50) ) # 106 PREEMPT||Working fine|
|Samsung Galaxy S||1 GHz ARM Cortex A8
|2.3.3 (Gingerbread)||18.104.22.168||Working fine|
|Samsung Galaxy Tab 2||1 GHz ARM Cortex A9
Dual Core (TI OMAP4430)
|4.0.3 (ICS)||3.0.8||Working (but apparently not entirely crash free)|
|Samsung Nexus S||1 GHz ARM Cortex A8
|2.3.4 Build GRj22||2.6.35-7-ge382d80||Working fine|
|Sony Tablet S||1 GHz ARM Cortex A9
Dual Core (AP20H)
|3.2 (Honeycomb)||22.214.171.124||Working fine|
|Sony Ericsson XPeria X10 Mini Pro||600 MHz Qualcomm Snapdragon S1 (MSM7227)||2.1 (Eclair)||Working fine, keyboard needs specific keymap|
|VIA 8650||2.2 (Froyo)||"Illegal instruction" crash. The processor is below AROS minimal requirements.|
Status of bugfixing:
- LG (and possibly other dual-core devices): The problem has not been confirmed on all dual-core devices. In october, 2011, a bug has been discovered in icon generation tool, used in AROS build process, which caused trashing icon tooltypes. Corrupted icons caused system-wide memory trashing, which could be a reason for this problem. Icon generator was fixed, but there were no test reports.
- HTC Sensation: installation problem (MacOS X created accompanying dot-underscope files when the system was copied to phone's flash. The issue has been reproduced and addressed since 09.11.2011, but there is no confirmation (yet).