Lines Matching refs:to
7 application enables Android to interact it more efficiently at run time and thus
8 has the potential to make it and the overall system run faster. We strongly
9 encourage you to use <code>zipalign</code> on both new and already published
10 applications and to make the optimized version available — even if your
12 <code>zipalign</code> helps performance and how to use it to optimize your
16 multiple processes: the installer reads the manifest to handle the
18 reads resources to get the application's name and icon; the system
19 server reads resources for a variety of reasons (e.g. to display that
26 apk), it has to fall back to explicitly reading them — which is slower and
39 pressure, thus causing the system to thrash around by having to constantly start
43 <p>Luckily, it's very easy for you to align the resources in your application:</p>
50 align release application packages if the export wizard is used to create them.
61 aligned by the <em>Ant</em> build script and need to be manually aligned.</li>
65 information to sign the packages, since aligning has to happen after signing. In
66 order to be able to sign packages, and therefore to align them, <em>Ant</em>
67 needs to know the location of the keystore and the name of the key in
70 properties are present, the signing tool will prompt to enter the store/key
79 <li>In order to manually align a package, <code>zipalign</code>
81 it to align application packages targeting any version of Android. You should run
96 on your currently published applications and to make the newly aligned
97 versions available to users. Also, don't forget to align any new