{\TeX\ Live for Android: Development and usage} {Clerk Ma} {The Android system is one of the most popular embedded systems for mobile devices nowdays. The word \textit{Android} was coined by Andy Rubin, the father of Android. The original functions of the Android were aimed at photography. But, with the growth of mobile phones, this has changed. Now, with Google's support, Android can runs anywhere. The kernel of Android is based on Linux. So, any binary which compiled by ARM toolchains can theoretically run on the Android. But, Android's directory structure do not obey the \acro{FHS} (Filesystem Hierarchy Standard). And, common users cannot access root permissions. Programs for Android must packed into a simple file, such as \code{foo.apk}, and run under the Dalvik \acro{VM}. The main programming language is Java, and the tools are provided by an \acro{SDK}. But Google provides an \acro{NDK} (Native Development Kit) for complex developing. My project uses both the \acro{SDK} and \acor{NDK}. The Java part acts like a native Android app, and the rest of my project's task is porting \TeX\ Live via the \acro{NDK}. \textbf{Portability of \TeX\ Live.} The engines in \TeX\ Live can split into three parts. Some engines are written primarily in Pascal, like \TeX82, Aleph, p\TeX\ and e(u)p\TeX. Two engines, pdf\TeX\ and \XeTeX, are written in Pascal with significant additions in C or \Cplusplus. One engine, Lua\TeX, is fully written in C/\Cplusplus. \TeX\ Live provided a set of tools to translate Pascal to C, so any engines' code can be translated to C when building the binaries of \TeX\ Live. Thus, \TeX\ Live runs on essentially any normal Unix or Windows platform.. Building \TeX\ Live on Linux is very simple, based on the \GNU\ autotools. However, porting \TeX\ Live to Android is not an easy task because Android's C library is \code{bionic}, not a standard \code{libc}. So, I needed to change some of the source. Another cause of problems is the \acro{RTTI} and exception support of the \acro{NDK}'s \acro{GCC}. \textbf{Native app as installer and terminal emulator.} In 2012, when I start my project, I only provided binary files to the users. They needed to ``root'' their Android devices to run these program. This is not convenient for many users. In 2013, I have developed a native app based on Android Terminal Emulator. This app is intended to eventually have three groups of functions: terminal emulator (done), \TeX\ Live package manager (work in progress), and an editor for \TeX\ (not implemented). \textbf{Showcase:} \XeTeX\ and font-caching; copy any text to get \PDF\ output; managing binary file and packages. }