Impetus webcast ‘Android Customization - Creating New Possibilities’ available at http://lf1.me/SO/

1. Webinar: Android Customization – Creating New Possibilities
September 28‚ 2012
Question and Answers Session
Q. What are the various hardware options by which any external hardware can be
connected with standard Android Phone/Tablet?
A. Audio jack and USB port are the two standard options available for hardware
connectivity. Other optional components include HDMI port, SDCard slot, and so on.
Q. What licensing intricacies are involved when customising Android for embedded
solutions?
A. There are two parts to Android: an Android-compatible Linux kernel and an AOSP
Release.
Even though it is modified to run the AOSP, the Linux kernel continues to be under
the GNU GPLv2 license. It is not allowed to distribute any modifications made to the
kernel under any license other than the GPL.
However, Applications that run on top of the kernel are not considered "derived
works." Therefore, feel free to create applications that run on top of the Linux kernel
and distribute them under the license of your choice.
Q. Can I modify a standard android phone and convert it into a data collection
utility in which I would require the support of just GSM and Camera?
A. Sure. Putting Android on an embedded device is a complex task! It involves an
intricate understanding of its internals and a clever mix of modifications to the
Android Open Source Project (AOSP) and its Linux kernel.
In simple words, this particular problem would involve creating the specific Android
OS version build ported on your desired Android phone with OEM specific kernel and
device drivers embedded to support GSM and Camera.
The next step would be adding the data collection utility app in the build. Finally, the
unused apps and features that are part of the standard AOSP build should be
removed to achieve the customised solution.

2. Q. Is there any brand specific limitation or any android phone can be re-flashed
with custom image of Android?
A. As discussed in the webinar, you will need OEM specific kernel and hardware
components specific device drivers to get your custom AOSP build working on a
specific OEM phone.
There is option of using Android developer phones for which complete builds are
available online on AOSP git repository. Finally, In order to get your custom ROM
flashed on the target device, the device needs to be rooted.
Q. What makes Android a preferred platform for me as an embedded system
vendor?
A. We did cover this in our webinar..
Android platform has a few characteristics that make it an especially interesting basis
for embedded use. The broad app ecosystem (with 200,000+ apps on Android
Market) allows for a large pool of apps available to choose from; should you want to
pre-package applications with your embedded device.
Android’s consistent and forward compatible App APIs make sure that custom apps
you develop for inclusion on your embedded system should continue working in the
future Android versions.
Because Android is open source, a lot of its components can be replaced outright.
For instance, if you don't like the default app Launcher (home screen) you can write
your own.
Another benefit from Android's openness and its architecture is that adding support
for additional features and hardware is relatively straightforward. You just need to
emulate what the platform is doing for other hardware or features of the same type.
For instance, you can add support for custom hardware to the HAL by adding a
handful of files.
And lastly, whether it is tuning the pre-built app behavior or changing their look and
feel, you are again free to modify the AOSP as needed.

3. Q. What type of an eco-system does Android enabled Embedded system enjoy?
A. Android is poised to make its mark on the embedded-system marketplace. We
believe that it is well on its way to becoming the defacto standard UI for a vast
majority of user-centric embedded devices.
An entire ecosystem is therefore rapidly building around Android. Silicon and system-
on- chip (SoC) manufacturers such as ARM, TI, Qualcomm, Freescale, NVidia and TI
have added Android support for their products, and handset and tablet
manufacturers such as Motorola, Samsung, HTC, Sony-Ericsson, LG, Archos, DELL,
ASUS, etc. ship an ever-increasing number of Android-equipped devices. This
ecosystem also includes an increasing number of diverse players, such as Amazon,
Verizon, Sprint and Barnes&Nobles, creating their own application markets.
Q. Do I need to take OEM permission in order to customise Android for a particular
device in bulk?
A. We do not require OEM permission for the same, but need the kernel and device
drivers for that device. Also burning custom image requires device rooting, so
warranty may be void in some OEM’s case.
Write to us at inquiry@impetus.com for more information