A major issue standing in the way of customized or virtualized Android these days is performance. Most developers approach Android performance issues as they surface, which results in spending a lot of time fine-tuning framework and application-level bottlenecks.
Performance optimization features enhanced in the paper include easier tracing of Android framework and drivers, improved localization of errors, more precise identification of poor function calls and some specific suggestions to improve performance.
This document primarily covers virtualized Android performance optimizations that can improve overall Android performance, but it's unlikely that these changes will result in dramatic performance effects in some cases. Choosing the right algorithms and function calls according to product phase should always be the priority. The suggestions in this paper should be used as general analysis/coding practices that can be incorporated into respective projects for performance efficiency.
This document was generated from the following discussion: HCL - Optimizing Android Performance in Virtual Environments