International Journal of Advance Foundation and Research in Computer (IJAFRC)

Volume 1, Issue 6, June 21!" I##$ 2%!& ' !&(%

&( ) * 21!, IJAFRC All Ri+hts Reserved ,,,"i-afrc"or+
Customi.in+ A/#0 For 1ifferent 2m3edded 1evices And
Inte+ration at Application 4a5er"
Charan 6" V
718
, A" # 9an-unath
728
, #harmila
7%8

Department of C.S.E , S.I.T, Tumkur, Karnataka, India
[email protected]
[1
, asman!u@man"ish.com
[#]

A : # ; R A C ;
Android is a soft,are stac< that includes operatin+ s5stem, middle ,are, applications for the
development of devices" Android has evolved +reatl5 and user e=perience in addition to consumer
level efficienc5 alon+ ,ith inte+ration of android po,ered devices also e=panded" :ecause of its
core aspects li<e open source nature and architectural modal it is 3ecomin+ more innovative
operatin+ s5stem" Android is 3ein+ inte+rated and ported to various em3edded devices this
includes enterprise des<top I0 phones, cameras, modem, sensors, and set'up 3o=es and
automotive" /ne ma-or advanta+e of usin+ android frame,or< 3e5ond the mo3ile devices is the
android applications can tal< to the functionalit5 of all these devices po,ered 35 android and
developers need not to ,rite several applications for different em3edded s5stems" ;his paper
loo<s at the challen+es in android mi+ration to the different em3edded platforms and portin+
issues" >ere ,e presented description of preparin+ and 3uildin+ A/#0 in local environment and
implementation ,ith 0ro+rammin+ for inte+ratin+ user applications in android 3uild s5stem
permanentl5"
Inde= ;erms? Consumer level efficienc5, soft,are stac<, architectural modal, portin+ issues,
automotive, android frame,or< and android 3uild s5stem"

I" Introduction
$ndroid pro"ides complete soft%are platform and frame%ork rather than !ust operating s&stem for
mo'ile de"ices and no% a da&s it also creates possi'ilities of using in a much %ider range of de"ices in
"arious domains such as control s&stems, militar&, medicine and automoti"e. (racticall& the android
architecture consists of application frame%ork on top of modified )inu* 'ased kernel and it is !a"a 'ased
along %ith free licensing this facilitates its rapid deplo&ment in man& domains, allo%ing adopters to add
additional proprietar& "alue in the android source. $ndroid+'ased smart phones Surpassed $pple i(hone
shipments [, in "arious places of the %orld, clearl& sho%ing ho% $ndroid is open for inno"ation. $t the
'ottom of the stack is )inu* kernel %ith man& patches this pro"ides 'asic s&stem functionalit& process
management, memor& management, net%orking and securit& 'ut android does not uses all )inu* kernel
utilities some of them has 'een modified like (o%er manager and -inder to regulate it for mo'iles also.
.n top of )inu* the android includes a set of nati"e li'raries pro"iding support for C/C00 nati"e code
used '& "arious components of the $ndroid s&stem. The some of the core li'raries specificall& designed
for android are 'ionics, media support for audio, "ideo, S1lite for data'ase etc there are man& technical
reasons for reducing and optimi2ing some li'raries like -ionic in android. $nother ke& component of
android s&stem is Dal"ik "irtual machine 3456 it is optimi2ed and designed specificall& for android. The
$pplication frame%ork is a most e*tensi"e part of the android s&stem it pro"ides man& higher le"el
ser"ices to applications. The de"elopers can easil& make use of ser"ices pro"ided '& the android
including accessing location information, running ser"ices 'ackground, set alarms and much more.
$ndroid %ill ship %ith asset of 'asic applications including a calendar, email client, maps, and S5S
program, 'ro%ser and others. $ll applications are %ritten using the 7a"a programming language. .ur
International Journal of Advance Foundation and Research in Computer (IJAFRC)
Volume 1, Issue 6, June 21!" I##$ 2%!& ' !&(%

&6 ) * 21!, IJAFRC All Ri+hts Reserved ,,,"i-afrc"or+
application communicates in the !a"a code of frame%orks and it %ill intern makes a call to 78I to
communicate %ith C code in nati"e li'raries and C code determines %hat is the 'est %a& to do this for our
application and using hard%are a'straction la&er of kernel %e can make use particular hard%are [9.















Fi+ure 1" #ho,s the 9a-or Components In Android Architecture

II" Challen+es and Issues
:istoricall& $ndroid has 'een %idel& deplo&ed in mo'ile phones such as smart phones and ta'lets. 8o%
the android is gro%n+up %ith more patches and po%erful "ersions of android has come up %ith support
for ne% kind of things, as %ell as more strong multimedia processing, android is escalating 'e&ond its
origins and started migrating [11 into a %ider arra& of applications and products. $s a result, an
increasing num'er of de"elopers are educating them self on android and also 'ecause of the ad"ances in
android and kernel de"elopment %e got curiosit& to e*plore some of its 'enefits and challenging issues as
%ell as ne% possi'ilities it presents the& are

;or migrating android s&stem to the man& em'edded de"ices [#< %e ha"e to 'e a%are of the
differences 'et%een the )inu* and android.
The )inu* kernel dri"er polic& for android is to a"oid modules and it runs on a static hard%are
configuration unlike )inu* distri'utions that can run on a most hard%are as possi'le.
=e need to ensure that the kernel is appropriate %ith the target hard%are and %ith android, thus
ensure suita'ilit& 'et%een android and the hard%are [11.
)inu* kernel for an android needs to 'e compiled according to the hard%are of the target de"ice in
%hich %e %ant to 'uild android s&stem [1#.
-esides the kernel and dri"ers, the >?I of android needs to 'e adapta'le %ith the target platform.
$ccordingl& the changes made in the android kernel and codes for the hard%are emulator do not
%ork %ell %ith actual hard%are.
Creating patches so that the )inu* kernel is attuned for android and android intern is tailored for
the mo'ile phone or other de"ices [1@.
.nce &ou ha"e the )inu* kernel ported, it is a fairl& eas& to get the rest of the android s&stem in
place and then &ou can take ad"antage of a enormous num'er of the a"aila'le android apps that are
e*isting in the communit&.

International Journal of Advance Foundation and Research in Computer (IJAFRC)
Volume 1, Issue 6, June 21!" I##$ 2%!& ' !&(%

&@ ) * 21!, IJAFRC All Ri+hts Reserved ,,,"i-afrc"or+
Some functionalit& like Ethernet, $5/;5 radio is not supported '& default in android stack.
5odularit& is not included in stack designing so that packages and package features canAt 'e
changes easil&.
$ndroid stack has a strong dependenc& on hard%are of a de"ice. It is e"ident that the largest
dependenc& is on the touch screen as user interacts "ia the touch screen. $ ma!orit& of the
em'edded s&stems still does not contain an& displa& [1#.



Fi+ure 2" Fi+ure sho,s steps in portin+ android into AR9 3oard

(orting is the a'ilit& to create target hard%are specific images to 'ring life to target hard%are '& using
host machine and de"eloping suita'le en"ironment to compile and 'uild the source %ith the help of cross
platform tool+chain and finall& do%nloading those images to the target hard%are.
III" 9i+ration of android 3e5ond the mo3ile phones

This section takes look at "alue of android migration and descri'es android porting procedure for $B5+
'ased 'oard and non $B5+'ased 'oard. $ndroid is tr&ing to surpass 'e&ond the mo'ile terminal space
and is generating an increased interest in the consumer electronics, automoti"e, home entertainment,
"ideo sur"eillance and industrial eCuipment control domains. $lthough $ndroid is the standard fit for
$B5 processor technologies, commercial ports of android are a"aila'le toda& on (o%er(C, S:D
3Beneasas6, 5I(S, and *9E platforms. This porta'ilit& makes it the most %idel& used mo'ile .S among all
the other )inu*+'ased open platforms. The design of android .S originall& onl& for the $B5 processor
architecture, %hich made it the genuine choice for mo'ile phones as the first complete phone soft%are
stack 'ased on )inu*. Since android is 'ased on )inu* kernel, thereAs a lot of opportunit& to make it
a"aila'le on other processor technologies. The task of porting $ndroid to other processor technologies is
not of little "alue, as $ndroid is hea"il& influenced '& the $B5 architecture.

A" 0ortin+ android to an AR9'3ased 3oard"

The t%o steps procedure in porting to an $B5+'ased processor architecture 'oard. ;irst, (reparing the
)inu* kernel for the 'oards [1@ this reCuires sta'le )inu* 'oard support package 3-S(6, including the
'oot+loader, )inu* kernel, and de"ice dri"ers for the $B5 'oard. =e need to get 'oard specific patches
for android and ?+'oot the& can 'e freel& do%nloaded from )inaro instead creating from the scratch this
%ill reCuire time and efforts to de"elop, test, and harden the patches 'efore it can 'e used on the target
International Journal of Advance Foundation and Research in Computer (IJAFRC)
Volume 1, Issue 6, June 21!" I##$ 2%!& ' !&(%

&& ) * 21!, IJAFRC All Ri+hts Reserved ,,,"i-afrc"or+
'oard. .nce sta'le )inu* kernel, )inu* -S(, specific ?+'oot is a"aila'le for do%nloading onto the 'oard,
the ne*t step is to preparing android and all images for the specific processor 'oard and %e can follo%
this procedure.
Bemem'er to %ork using ED 'it machine for >inger'read and later "ersions of the android and @#
'it machines %ill support fro&o and earlier "ersions.
.ur local en"ironment is eCuipped for do%nloading and 'uilding android $.S( '& installing
packages as per the instructions of the official %e'site [@.
Do%nload the 'oard supporti"e android source from >oogleAs android site using repositor&
management tool repo once successfull& getting into the %orking director& it contains these su'+
directories.
Initiali2e the en"ironment using en"setup.sh shell script it %ill generate lunch command.
F . 'uild/en"setup.sh
E*ecute shell script generated lunch command and choose 'uild name that is the name of the
target de"ice and choose 'uild t&pe for targeting emulator %e can use full+eng.
-uild the $ndroid in local en"ironment using make tool. Fmake +!
The successful 'uilding using make tool %ill create an image files named s&stem.img,
userdata.img, ramdisk.img in generic director&.
Then the image file is read& to 'e do%nloaded on the 'oard.

;igure #. gi"es high le"el details of android porting steps reCuired for an $B5 processor+'ased 'oard.
The illustration assumes the )inu* -S( is de"eloped from scratch. If a )inu* -S( is alread& accessi'le
freel& from 'oard "endors and it is full& configured for the target hard%are, then the first step is not
necessar& or ma& 'e reCuired for incorporating additional de"ice dri"ers for the target 'oard.

:" 0ortin+ android to non AR9'3ased 3oard"

$ndroid open source pro!ect can run on an& C(? in the %orld as android supports $B5, 5I(S, po%er
architecture, *9E processors like Intel atom and other C(?As and as long as %e are programming in !a"a
the architecture does not matters. 5a!orit& of the C(?As in em'edded de"ices are alread& $B5 'ased 'ut
still %e ha"e some non+$B5 'ased C(?As the& o'ligates to port android on a different non $B5+'ased
processor architectures like Super+: and Intel atom the follo%ing general steps are essential [11. a large
amount of code needs to 'e re%ritten and updated to achie"e this portG $lter the android 'uild s&stem to
support the other architecture.

(orting of the Dal"ik 45 for other processor.
Include architecture and 'uild support.
=iden 'ionic run+time li'rar&/linker support to ha"e room for the other architecture.
:ard%are+related tunings are needed to control audio, "ideo, and graphics.
(ort the android media frame%ork and other li'raries.
Integrate android+specific )inu* Kernel patches into the 'oardAs -S(.
Support the other architecture technolog& in the android SDK and android targets in the
customi2a'le de"elopment s&stem.
Conduct the platform and integration testing of android stack components, "er& thorough testing is
reCuired.

The dal"ik 45 and 'ionic C li'rar& are optimi2ed for the android and the& are "ital components in the
stack at the same time porting of these components on non+$B5 'ased C(?As is "er& difficult and
comple* task. ?pon completing the porting acti"it& thorough testing is mandated to "alidate the port.
International Journal of Advance Foundation and Research in Computer (IJAFRC)
Volume 1, Issue 6, June 21!" I##$ 2%!& ' !&(%

&A ) * 21!, IJAFRC All Ri+hts Reserved ,,,"i-afrc"or+
=hile these illustrated procedures are 'rief, to turn these into realit& %e %ill reCuire lo%+le"el and
platform+le"el e*perience and a thorough understanding of the target en"ironment, especiall& for the
non+$B5 platforms.

C" Android applications in em3edded devices 3e5ond mo3iles"

There is no full fledged usage of android in all em'edded de"ices 'ecause lack of interface reCuirement
for so man& de"ices this is also one of the reason to limit android 'ut %e can find it in onl& fe% of the
em'edded de"ices like set+up 'o*es, cameras, enterprise desktop I( phones and also in future %e can get
more num'er of em'edded de"ices ena'led %ith android some of the applications of android that %e can
claim in different em'edded de"ices and real+time features [#H[## the& are.

?sing android po%ered set+up 'o*es increases user e*perience %ith the tele"ision and it is 'etter
for the operators and also eas& to de"elop [1D.
The applications de"eloped using android .S can support EC> monitoring in mo'ile de"ices [1<
[#@ and also for collecting sensor& data from "arious em'edded sensors [1E.
Beal+time s&stem features and se"eral capa'ilities of android are used for implementing Body
area networks [1,.
The android penetration into the desktop I( phones used %ithin enterprises offers more securit&
and also rich interface.
?se of android in camera generates more applications in the de"ice 'ecause %e can %alk around
the strong app store of the android communit&.

Fi+ure %? Fi+ure sho,s su3'folders in A/#0 folder"

IV" >o, to customi.e for transportin+ android into ne, device

This sections starts %ith introduction a'out $.S( %ith 'rief description a'out directories in android
source then %e 'rings glimpse of the customi2ation to 'e made to design and get android life onto the
ne% de"ice.

A" Bhat is A/#0C

(ro!ect responsi'le for creating android s&stem is called $.S( it is primaril& de"eloped and maintained
'& >oogle as of free a"aila'ilit& it is more open to inno"ation that &ou often donAt see in I.S and 'ecause
of more fle*i'ilit& in customi2ing android it facilitated creation of more custom B.5As, rooting options
and the& all pro"ide plent& of features [1I. $fter s&nching $.S( from official %e'site &ou %ill get su'+
folders as sho%n in ;ig @ some of the important su'+folders are.

/'ionic/ it is %here 'ionic C li'rar& optimi2ed for em'edded de"ices is stored.
/'oota'le/ 'oot and start up related code.
/de"elopment/ pro!ects associated to de"elopment such as source code for sdk and ndk tools.
?suall& not a folder &ou tap %hen %orking %ith the platform for a target.

International Journal of Advance Foundation and Research in Computer (IJAFRC)
Volume 1, Issue 6, June 21!" I##$ 2%!& ' !&(%

A ) * 21!, IJAFRC All Ri+hts Reserved ,,,"i-afrc"or+
/'uild/ it is one of the comple* part of the s&stem and it %ill pick specific 'oard, specific target and
product.
/cts/ the compati'ilit& test suit director& made to test reCuirements for the android s&stem to 'e
an android s&stem and each android "ersion has its o%n compati'ilit& definition document and
compati'ilit& test suit that runs tests on target hard%are.
/dal"ik/ this director& contains the Dal"ik "irtual machine at /dal"ik/"m, the de* compiler at
/dal"ik/d* and core class li'raries as %ell as related tools.
/de"ice/ this is place %here most of the de"ice specific things %ill 'e stored and some of the
commonalities %ill 'e stored in /de"ice/common.
/e*ternal/ E*ternal refers to e*ternal open source li'raries. That means li'raries that the $ndroid
platform dependent upon 'ut that are not primaril& de"eloped and maintained '& $ndroid open
source pro!ect. T&pical e*amples are %e'kit for the 'ro%ser, ;reeT&pe for fonts.
/frame%orks/ the director& contains android frame%ork to support all the s&stem and user
applications for e*ample if %e %ant media support is pro"ided through /frame%orks/media folder
and for graphics /frame%orks/graphics folder.
/hard%are/ + this is %here "er& hard%are specific things %ill go. The /hard%are/li'hard%are
folder 'asicall& contains things to a'stract real ph&sical hard%areJs. This folder also contains the
reference radio interface la&er implementation.
/ndk/ + this ndk ha"e tool+chain for 'uilding nati"e code that ma& 'e lo% memor& footprint code,
C(?+intensi"e code and cross compiling &our nati"e code for target de"ice architecture.
/packages/ this is the place %here things 'ound to the applications are stored for e*ample apps
that get included into the pro!ect are stored in /packages/apps folder and the& %ill goes to de"ices.
The %allpapers and content pro"iders also stored here.
/pre'uilt/ the things that are pre'uilt and also distri'uted files in the 'inar& form %ill goes here.
/s&stem/ this is a director& a lot of s&stem related things as %ell as source code files for the core
android s&stem %ill 'e stored. This also includes source code for the init process and default init.rc
script that pro"ide d&namic configuration of the platform.
/out/ the out/target/product/generic location contains reCuired images that &ou can run using
emulator command and also the& can 'e do%nloaded and flashed to a de"ice if &ou are 'uilding for
target hard%are.

It is a !ust partial "ie% of the tracking and customi2ing the files in $.S( in order to prepare for
transporting [D android into ne% de"ice 'ut real implementation needs lot of %ork to 'e done. %e need
minutes of all components making up android including kernel androidism to optimi2e and de"elop
patches for kernel to%ards make it compati'le %ith specific hard%are as %ell as android and also %e
need to learn adding support for ne% hard%are in the de"ice [#.

V" ;rac<in+ A/#0 for portin+ into the ne, device

(orting android to the de"ices the& are not meant to support for android is more challenging task 'efore
starting first %e need to find out ho% does ne% de"ice hea"il& differs from usual android de"ices,
s%itching into an& one of the specific android "ersions like >inger'read, Ice cream sand%ich %e need to
go through the compati'ilit& guidelines including memor&, storage, displa& resolution, >raphics
reCuirements specifications that our ne% de"ice should satisf& and de"ice should pro"ide android
applications compati'ilit&, pro"ide android marketplace support, pro"ide access to >oogle ser"ices
%ithout modif&ing an& >oogle $(IAs and frame%ork.

International Journal of Advance Foundation and Research in Computer (IJAFRC)
Volume 1, Issue 6, June 21!" I##$ 2%!& ' !&(%

A1 ) * 21!, IJAFRC All Ri+hts Reserved ,,,"i-afrc"or+
The >oogle $.S( is up+to date reference 'ut limited de"ice support mainl& it support for >oogleAs official
de"ice >ala*& 8e*us. The )inaro $.S( [D is most integrated %ith %ide hard%are support and 'ecause of
its $ndroid added "alues like e*tra and optimi2ed packages it gi"es more hard%are de"ices support than
stock >oogle ICS, it supports for TI panda'oard, TI -eagle-oard, ;reescale i.5K<@, ST Sno%'all, Samsung
.rigen de"ices.

Take &our $.S( and create director& for our ne% de"ice %ith complete product description
under de"ice director& of the $.S( sources.
Create "endersetup.sh file that is e*ecuted '& 'uild/en"setup.sh and can use an&thing defined in
en"setup.sh
Create $ndroid.mk, $ndroid(roducts.mk, ne%Lde"iceLname.mk files and enter ne% de"ice name,
de"ice 'rand and specif& all make files. The "alues %e put here is "er& important 'ecause that
%ill 'e referenced '& some other scripts during the run time.
Create de"ice.mk file it is the de"ice specific product definition file. It lists all the o"erla&s, files,
modules, properties that are specific to hard%are of the ne% de"ice. $nd set
(B.D?CTL($CK$>ES, (B.D?CTL(B.(EBTML.4EBBIDES and some other make file rules specific
to our ne% de"ice.
'uild/core/product.mk file in $.S( contains 'uild options like Target and compiler options,
Ena'le 8E.8 feature, ;ile+s&stem and partitioning and some other options that %e need to edit
according to our target ne% de"ice.
Create a de"ice/m& compan&/m& de"ice/o"erla& director& %ith same depth and files &ou %ant to
o"er%rite for ne% de"ice specific settings that &ou ma& %ant to customi2e for target de"ice, this
%ill a"oids &ou touching the files from $.S(.
If &ou ha"e ?+'oot customi2ed for &our specific ne% de"ice !ust replace it %ith the generic 'oot+
loader pro"ided '& >oogle at 'oota'le/'ootloader/legac& and if &ou not using pre'uilt "ersion of
the ?+'oot &ou ma& !ust specif& true for the T$B>ETL8.L-..T).$DEB, T$B>ETL?SEL?-..T
and specif& customi2ed configuration file using ?-..TLC.8;I> commands in -oardConfig.mk
then ?+-oot 'oot+loader is 'uilt '& the specified configuration file.
In android kernel no dri"ers are 'uilt as modules and according to )inu* kernel dri"er polic& the
dri"ers can 'e loaded or unloaded, if &ou do not %ant to use pre'uilt kernel then %e need to
specif& our o%n kernel configuration file through KEB8E)LC.;I> command.
The net%ork and connecti"it& for &our ne% de"ice reCuired to o"erla& some resources in
frame%ork/'ase/core/res/res/"alues/cofig.*ml.
=ithin this file %e need to change fe% lines 'ased on %hat are the interfaces the processor 'oard
of our ne% de"ice %ill support and edit net%ork attri'utes and radio attri'utes.
;or media support %e create mediaLprofiles.*ml file and used to declare the multimedia profiles
and capa'ilities like decoding and encoding rate that our ne% de"ice 'oard %ill support.
."erride in -oardConfig.mk for phone or ta'let mode.
:$) 3hard%are/li'hard%are6 acts as a 'ridge 'et%een regular kernel implementation and
android frame%ork.

It is a !ust partial "ie% of the tracking and customi2ing the files in $.S( in order to prepare for
transporting [D android into ne% de"ice 'ut real implementation needs lot of %ork to 'e done and %e
need minutes of all components making up android including kernel androidism to optimi2e and de"elop
patches for kernel to%ards make it compati'le %ith specific hard%are as %ell as android and also %e
need to learn adding support for ne% hard%are in the de"ice [#.


International Journal of Advance Foundation and Research in Computer (IJAFRC)
Volume 1, Issue 6, June 21!" I##$ 2%!& ' !&(%

A2 ) * 21!, IJAFRC All Ri+hts Reserved ,,,"i-afrc"or+
VII" Implementation

$ndroid is customi2a'le in all the < le"els 'efore porting into an& $B5 'ased 'oards in this %ork %e
started customi2ing from the application le"el. $.S( porting into ne% de"ices consists of t%o ma!or steps
as descri'ed in the paperN here %e ha"e done preparing $.S( on host machine making it %orking on
android "irtual de"ice. $ndroid %ill al%a&s arri"es along %ith man& applications, this forms an
application la&er in the android stack including -ro%ser, camera, Email, phone etc. =hen it mo"es
'e&ond mo'iles and ta'lets to some other em'edded de"ices, all the core applications need not 'e
reCuired and some of them need to 'e ne%l& integrated to the operating s&stem. =e ha"e prepared make
file to descri'e an& user defined application sources to the android 'uild s&stem and integrate to it
permanentl&.

>o to packages/ apps/ in this location %e need to cop& application source code as %e de"eloped
using android SDK.
(rogramming $ndroid.mk file in application to descri'e user source code to the android 'uild
s&stem.

(B.D?CTL($CK$>ESGO P
4o+in D EEEEEEthis is the additionEEEEEEEE
$pplications(ro"ider P
-ackupBestoreConfirmation P
-ro%ser P
-ugreport P
Contacts P etcQ..

Then add make file to the product packages for that %e need to edit /'uid/target/core.mk file that
means add our application in the list of product packages.
Content of the make file.

).C$)L($T:GO F3call m&+dir6
Include F3C)E$BL4$BS6
).C$)L5.D?)ELT$>S GO tests
).C$)LST$TICL7$4$L)I-B$BIES GO P
android+common P
gua"a P
android+support+"1@ P
android+support+"D P
).C$)LSBCL;I)ESGO F3call all+!a"a+files+under, src6
).C$)L($CK$>EL8$5EGO )ogin
).C$)L(B.>?$BDL;)$>L;I)ESGO proguard+pro!ect.t*t
).C$)LSDKL4EBSI.8GO current
include F3-?I)DL($CK$>E6
includeF3callall+makefiles+under,F3).C$)L($T:66

International Journal of Advance Foundation and Research in Computer (IJAFRC)
Volume 1, Issue 6, June 21!" I##$ 2%!& ' !&(%

A% ) * 21!, IJAFRC All Ri+hts Reserved ,,,"i-afrc"or+

Fi+ure !" Fi+ure sho,s emulator ,ith inte+rated ne, application"

VIII" Conclusion and future ,or<
In this paper %e look at challenges and 'enefits of android migration into ne% em'edded de"ices and %e
presented general procedures to port android to $B5 and non+$B5 'oards including partial "ie% a'out
:o% to customi2e android source for preparing it to port onto ne% de"ices. $fter 'uilding $.S( on the
local host %e prepared top le"el file in the director& for the user application to run directl& along %ith
e*isting operating s&stem. .ur implementation is help full in integrating ne% applications 'ased on the
target de"iceN ne% applications can 'e carried along %ith the generated operating s&stem images. The
success of android %as onl& possi'le due to eas& porta'ilit& of )inu* to "arious hard%are platforms 'ut
android is a %atered+do%n, limited )inu* distri'ution [< that %orks for one specific purpose and )inu*
kernel inside %as al%a&s unaltered %e need to appl& some patches to add features that %e %ant for our
ne% de"ice [#1. The customi2ing a'ilit& of $.S( and also as an em'edded android %ith )inu* kernel it
pro"ides ne% possi'ilities [19 for porting into man& more de"ices. Creating androidism in the kernel for
different target hard%areAs %e can definitel& make android to support for ne% kind of de"ices other than
mo'iles [E.

IF" References

[1. 5arko >argenta learning android first edition .JBeill& pu'lications #H11.

[#. Karim Maghmour Em'edded $ndroid first edition .JBeill& pu'lications #H1@.

[@. official google android %e'site de"elopers.android.com

[D. -en!amin Rores $-S #H1# + 1@th ;e' #H1# + Bed%ood Shores, S; -a&,C$, ?S$ android de"ice
poring %alkthrough guidelines.

[<. $l+Ba&es, :adeel TariC. SStud&ing 5ain Differences 'et%een $ndroid T)inu* .perating S&stemsU.
In. (rocG International 7ournal of Electrical T Computer Sciences I7ECS+I7E8S 4olG1# 8oGH<

International Journal of Advance Foundation and Research in Computer (IJAFRC)
Volume 1, Issue 6, June 21!" I##$ 2%!& ' !&(%

A! ) * 21!, IJAFRC All Ri+hts Reserved ,,,"i-afrc"or+
[E. Colin =alls, 5entor >raphics $ndroid de"elopment for em'edded s&stems 'e&ond mo'iles.

[I. 5arianne )oes, 5apusoft Challenges in porting em'edded applications.

[9. 5arko >argenta founder and CE. at 5arakana )earn a'out $ndroid internals and 8DK .

[,. Top Smartphone .perating S&stems, Shipments, and 5arket Share, 1# #H1@ 3?nits in 5illions6
anal&sed at httpG//%%%.idc.com

[1H. a'himan&u das, aricent technologies $ndroid opens up the operating s&stem for inno"ation
5o'ile De" and Design.

[11. =hite paper '& Darren Etheridge, $ndroid 5ultimedia Engineering 5anager, DS( and $B5 Te*as
Instruments SDe"eloping $ndroid applicationsfor $B5 Corte*+$9 coresV.

[1#. Soum&a Kanti Datta 5o'ile Communication Department E?BEC.5 Sophia $ntipolis, ;rance
S$ndroid Stack Integration in Em'edded S&stemsV.

[1@. $'h&udai Shanker CSE Department 7a&pee Institute of Information technolog& 8.ID$, India,
Som&a )al S$ndroid porting conceptsV In.(rocG Electronics Computer Technolog& 3ICECT6, #H11
@rd International Conference 4olG H<.

[1D. Ku2mano"ic, 8. 5aruna, T. Sa"ic, 5. 5il!ko"ic, >. Isailo"ic, D >oogleJs android as an application
en"ironment for DT4 decoder s&stem#H1H IEEE 1Dth International S&mposium on Consumer
Electronics 3ISCE6.

[1<. 7okic, S.(okric, 5. Krco, S.Delic, 4. 7okic Sapplication for =$)K acti"it& and EC> monitoring on
mo'ile de"ices 'ased on $ndroid .SVTelecommunications ;orum 3TE);.B6, #H11 1,
th.


[1E. >il, >.-. -erlanga et all, SinConte*toG $ ;usion $rchitecture to .'tain 5o'ile Conte*t Information
;usion 3;?SI.86V (roceedings of the 1Dth International Conference (u'lication MearG #H11 ,
(age3s6G 1 W 9.

[1I. I!!ina Earnest (aul, et all S$ndroid .S Customi2ationV International 7ournal of Engineering and
Inno"ati"e Technolog& 3I7EIT6 5a& #H1# 4olume 1, Issue <.

[19. )oc perneel,et all SCan $ndroid 'e used for real+time purposeV International conference on
computer s&stems and industrial informatics3I7EIT6 Dec #H1# pages 1+E.

[1,. 5atthias =agner, S$ndroid -ased -od& $rea 8et%ork for the E"aluation of 5edical (arametersV
In procG 1H
th
International =orkshop on Em'edded S&stems pu'lication &earG #H1# , (age3s6G @@ W
@9.

[#H. Claudio 5aia, SE"aluating $ndroid .S for Em'edded Beal+Time S&stemsV (u'lished in
(roceedings of the Eth International =orkshop on Em'edded Beal+Time $pplications, 7ul& #H1H.
pp. E@+IH.

International Journal of Advance Foundation and Research in Computer (IJAFRC)
Volume 1, Issue 6, June 21!" I##$ 2%!& ' !&(%

A( ) * 21!, IJAFRC All Ri+hts Reserved ,,,"i-afrc"or+
[#1. Igor Kalko", $achen, Dominik ;ranke S$ real+time e*tension to the $ndroid platformV
(roceedings of the 1Hth International =orkshop on 7a"a Technologies for Beal+time and
Em'edded S&stems pu'lication &earG#H1# (ages 1H<+11D.

[##. -hupinder S, et all. IEEE SBelia'le Beal+Time $pplications on $ndroid .SV su'mitted for
pu'lication 7une+19 #H1H.

[#@. =olfgang 5auerer, et all SBeal+Time $ndroidG Deterministic Ease of ?seV InG (roceedings of
Em'edded )inu* Conference Europe, < + I 8o" #H1#.

[#D. Ching+=ei Chen, =ei+Chieh Chou, Mi+)%un :o S)i"e DemonstrationG $ 5o'ile EC> :ealthcare
(latformV (u'lication MearG -iomedical Circuits and S&stems Conference 3-ioC$S6, #H1# IEEE ,
(age3s6G 9I.

[#<. Charan K.4, Sharmila S.(, 5an!unath $.S SCustomi2ing $.S( for different em'edded de"icesV 9
th

IEEE International Conference on Computing for Sustaina'le >lo'al De"elopment 3I8DI$Com6
#H1D.