With rich native multimedia capabilities and a user-friendly touch interface, Android provides many potential benefits for embedded applications and devices. However, as Android was designed with consumer mobile devices in mind there are a number of bottlenecks which must be overcome to make Android suitable for an embedded environment.
The first bottleneck lays in how to go about skinning Android to achieve the required behavior, look and feel for an embedded scenario. As a leader in providing Embedded Android solutions to the market we have come up with the three most common skinning requests to present in detail during the VIA Embedded Android Forum 2015 being held May 27th at the ShanghaiTech University (Yueyang Road Campus).
Start-up Screen Customization
One of the most frequently requested modifications we receive is how to replace the start-up screen image with a custom logo or animation. What may seem like a simple request is not as straightforward due to the complex nature of the numerous boot devices such as the SPI-ROM, SD Card, Flash, eMMC, the x-loader, Uboot, and Linux Kernel. We will delve into the complexity of the boot process, covering all aspects of coding and configuration in order to help developers fully understand how to overcome the challenges they face when trying to customize the start-up screen.
Application Launch Automation
One of the most critical modifications required to make Android suitable for an embedded device is the ability to boot directly into a specific application. The session will introduce the 4 Android application components (activities, services, content providers and broadcast receivers) with special focus on the broadcast receiver as this is the core component which must be modified in order to enable a device to directly boot into an application. How to troubleshoot problems encountered after booting will also be covered in order to ensure tight integration of hardware and software into embedded applications.
Full Screen Display Mode
The third most common skinning request we receive is how to control full screen display mode behavior. By default, Android provides system bars located at the top and the bottom of the screen; however for many embedded applications this is not the optimal usage of the screen space. During this session the various aspects of the system bar will be discussed; from how to enable and disable it as well as how to hide it permanently to achieve an immersive mode.
To learn all about skinning for Embedded Android applications as well as how to overcome other key bottlenecks, be sure to join us at our VIA Embedded Android Forum 2015. Sign-up now*
*Please note the forum will be held in Chinese only.