android on e680

[swifty]

Nice find, thanks Ge6!

[shantanu]

nice man

[*~Nimsrules~*]

My personal opinion is not to be messing around with the original software the phone comes with. You can land in trouble if the trick doesn't work. However stable the trick be always consider it a BETA thing and Handle With Care. Just my personal view.

[sieunhancop]

Linux mobile phone the strongest voice - the success of transplantation to the Google Android operating system on the E680 motor

by admin on Feb.03, 2009, under Network Technology
1. INTRODUCTION
Today more and more fans started to Google Android transplantation Android system to an existing handheld devices. The first successful transplantation
Android system is in the Zaurus, and then in the OMAP chipset based on the N810.
Some developers will be running Android in the coming PXA270 development board. We know that the Motorola MOTO E680 Series
EZX phone use intel XScal-PXA270 application processor chip, while using the Linux 2.4.20 kernel. After some research
Study, we think that the E680 fully meet the transplant Android system.

2. Transplant Android to E680
In fact, transplantation is the transplantation Android system Google ndroid kernel to the target device, while Android root file system
And android kernel with working in the target system. Google in the Android SDK provides a binary Android root file
system file system as well as the android kernel source. Therefore, we can easily Android SDK from Android root extract text
Pieces of the system, but we have to consider how to migrate to Android kernel above to our E680.
There are two ways to transplant to the E680 on the Android system.
a) all the Android firmware ported to E680 on the overall
b) to E680 of the kernel upgrade to 2.6.x, and then into the Android firmware.
It is obvious that a method takes more effort, because the E680 is a kernel of 2.4.20, and Android is based on 2.6.23 the Kernel
Of.
Fortunately, there is a open source project called
Simple OpenEzx can help us to E680 upgrade the kernel to 2.6.x. This document explains in detail how to approach b Transplantation
Android system on to the E680.
2.1 Android Kernel / Root file system
First of all, we need the latest version of Android simulator system. (Using the original android-emulator-m5-rc14.tar.gz)
Download link Downloads - android - Google Code
Android Root file system, access from the SDK.
Download link Redirecting...
Access to Android upgrade patch to upgrade to 2.6.x Linux kernel, you need to Android SDK kernel from the official 2.6.23 kernel in
Separation, and then verify that all drivers have the right to change the Android. The Linux 2.6.24 for Android patch to do the installation
Package
For Android Root file system, you need some time to produce. You to extract from the SDK in the three mirror ramdisk.img,
system.img and userdata.img to resume you need root file system. You can here and OMAP’s Android make a
In contrast. Address: Android on OMAP - eLinux.org.
E680 is now not able to use the Root file system, I use busybox toolkit to produce their own Android SDK and a
The new Android NFS Root file system. You can find many of the NFS Root File System to establish the article, here
Not more than a speech. Similarly, I also patch package Add the Android NFS Root file system.
2.2. SW / HW environmental requirements
We have established in the Android kernel and Root file system, so we need to use a list of hardware and software environment.
2.1.1 Software Environment
Linux Host:
You can use any mainstream Linux system environment, such as Redhat, Fedora, etc.. Look like your own.
tool-chain:
SDK of Android Root System is to use the ARM EABI compliant compiler to compile, so we need to ARM EABI compliant compilers
Browser to compile our kerne.
ARM EABI compatible too-chain Download Address
Download Sourcery G++ Lite Edition for ARM
You should download arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.tar!
Others do not download!
Patch tool:
We need to OpenEzx 2.6.24.x-patch A1200 set of tools to upgrade kernel.
Download Address: Quilt - Summary [Savannah]
USB Boot:
OpenEzx developed a tool that allows you to use USB to boot kernel.
Download 0.2 version: / - Revision 2477: /trunk/src/host/boot_usb
Busybox 1.1.3:
Like I said before, I used busybox to build Android NFS Root file system. I’m using 1.3 version, and I
Add in the upgrade package in the busybox config configuration file for your reference.
2.1.2 Hardware environment
We only need a E680 phone and a USB cable to transfer Android.
Well, now we are speaking about the details of the implementation of transplantation. Is not very excited about it! - -0
# The following is my environment set up process
Linux Host: VMwareStation + TurboLinux 10
Tool-Chain: arm-none-linux-gnueabi-tool chain installed in the directory / home/arm-2007q3
Patch tool: a tool to install in the directory / home/quilt-0.46 directory
USB Boot tool: the compiler will put / home / testKernel / ezx_usb_boot
Established for the kernel I / home / android folder for Android root file system set up / home / android_nfs folder.
2.3 E680 Android transplantation works
1) unzip Linux-2.6.24 kernel tar file (linux-2.6.24.tar.bz2) to / home/android/linux-2.6.24
You can download from the following address to the linux-2.6.24.tar.bz2
Index of /pub/linux/kernel/v2.6
2) Resume patch directory in / home/android/linux-2.6.24 below and then copy all the OpenEzx patchset folder of documents under
To this directory
3) in the directory / home/android/linux-2.6.2 applied OpenEzx patches, through via cad command: quilt push-a
4) in the directory / home/android/linxu-2.6.24 use cmd command are as follows: patch-p2 <.. / ***. patch
u android-core.patch
u android-config-nfs.patch
u android-e680 *- pcap.patch
u android-e680 *- 16bpp.patch
u android-framebuffer.patch
u android-touchscreen.patch
Note: must be in step 3) and successfully completed after the completion of steps 4)!
5) In the OpenEzx patchset with the following methods Makefile.openezx amendment variable CROSS_COMPILE:
PHONES = e680 *
CROSS_COMPILE? = / Home/arm-2007q3/bin/arm-none-linux-gnueabi-
Here, I will be my tool chain on / home/arm-2007q3 directory, you can change lightly.
6) in the directory / home/android/linux-2.6.24 compiled under the android kernel, use the following command: make-f patches /
Makefile.openezx
After about half an hour, you can / home/android/linux-2.6.24 directory to see the zImage-e680 * and modulese680 *.
tar.gz
Now we begin to Android via NFS
A. extracting android_nfs_root-m5-r14.bz2 to the Portable Document specified directory
Note: This directory must be the core document set-top operating parameters command defoncif-e680 * line. Here, we use / home /
android_nfs this directory.
defconfig-e680 *
Here, I use the directory / home / android_nfs
Files migrate to E680
B. extracting e680 *. tar.fz compile phase from the same content to the document directory android_nfs_root-m5-r14.bz2 in. Derived from tar extension with
Yung extract to / home / android_nfs / lib directory
C. Add a USB data cable to the E680 and let the phone enter mbm flash mode (the screen as a red state)
D. use us_boot software to boot the kernel to / home / below. Testing whether through cmd. / ezx_usb_boot zImage-e680 * ‘in this life
Order
From the core to the E680, the E680’s screen you see the core is loaded.
Screen will scroll the display to load the information parameters
E. about a few seconds, from the LINUX host terminal through the command parameters’ telnet telent 192.168.1.2 ‘remote landing E680 phone
F. Run ‘. / Init’ implementation of long-range land-to-phone, you can see the string android
G. Run ‘/ system / bin / runtime’, it will, you can see the red is always exciting on the screen have left the cycle of doing.
Then about 2 minutes or so, you can see feel extremely close android desktop. Rahman you can touch-screen mobile phone open
Before application (dial-up devices, maps, browser, etc.)
There is no doubt that if you use cmd_line order to modify the default settings of the A1200 core parameters allow android from the SD card-activated, then
android startup procedure will be faster
Now, I have sought to amend android keyboard mapping so that the camera phone to do the hardware keyboard, while allowing the virtual hardware to the end of phone. You can
E680 to click the center of the joystick to select the key places to return to the desktop.
Note: You can choose to use cmd_line order to modify the default parameters of E680 to make it more easy for the compiler to generate in the mmc card, the same as you would have to
Android system reform under the root directory of / etc / init.rc document
3. Known Issues and Status
Status
l Android to the normal load. (android characters show that red-eye cycle of operation, Android desktop display)
l touch screen can work A1200/E680
l hardware (VR, camera, select button) to be able to run in some A1200
l The main procedures of individual requests (Dialer. maps, browser, contacts) from the user interface boot loader
l voice does not work
Question:
l display colors in the use of the 18 pin A1200/A910 after the panel on the screen to produce a good, but the android file system variable 16
Bit color
l Although the touch screen can be used, but will have to calibrate
l or other hardware does not work
4. Original author, following the work to be done
l BP MUX run in A1200
l Implement RIL (Radio Interface Layer) shared libraries, so that a normal GSM phone
l Android audio running in A1200
l keys in A1200 on the normal use
l touch screen calibration
l solution A1200 touch screen color display problem
5. Tips
l When building Android root file system by yourself, several critical dev nodes (/ dev / binder,
/ dev / log / main, / dev / log / radio, / dev / log / event) must be created correctly.
l If your touch screen does not work, you should check whether touch screen driver is assigned
to event1 via ‘cat / proc / bus / input / devices’ which Android application use / dev/input/event1 to
get touch driver info.
l You can modify / system / usr / keylayout / qwerty.kl file to change Android key mapping.
l You can use strace to debug during your porting.
6. Reference source
[1] OpenEZX homepage - OpenEZX homepage - Home
[2] Google Android homepage - Google Projects for Android
[3] Benno’s engineering Blog - Benno's blog
[4] Android on Zaurus - Android Zaurus: Google Android runs on Sharp Zaurus SL-C3000
[5] Omegamoon Blog
Omegamoon blog - Android patches
egory = 1
[6] AndroidPortingOnRealTarget
KLDPWiki: Android Porting On Real Target
7. The availability of resources
1) OpenEZX-patchset.zip - OpenEZX patchset for 2.6.24-x.
2) android-patches.zip - android specific patches including
ü android-core.patch
ü android-config-nfs.patch
ü android-a1200-pcap.patch
ü android-a12000-16bpp.patch
ü android-framebuffer.patch
ü android-touchscreen.patch
3) android-nfs-root-m5r14.bz2 - Android NFS root file system package.
4) android_nfs_kernel - Android test kernel
5) modules-a1200.tar.gz - Android test modules package
6) busybox.config - busybox config file for NFS root file system. Finally, offer a running Android in the E680 video YouTube - Android running on E680
It so happened that I have in hand a E680g, also no need, the winter vacation, the period of time, intending to carry out research, At the same time, Google’s support, I believe Android will be doing an extremely good job, let alone Linux-Mobile is no longer fighting the military!

[shantanu]

thansk for this useful info brother

[swifty]

Linux mobile phone the strongest voice - the success of transplantation to the Google Android operating system on the E680 motor

Nice find!
Thanks for your first post

[ndiesign]

cool works...thanks dude