2011/1/16 Mark Murphy <[email protected]> > On Sun, Jan 16, 2011 at 8:24 AM, Kostya Vasilyev <[email protected]> > wrote: > > It's actually a valid case for applications that have large code > > Bear in mind that a copy of the "large code" will also be on the > on-board storage. >
Thanks for the link - I just re-read it more carefully than before. It's too bad, seems like the only win is for application resources. Still, I have to agree with Jonas - the app management screen has all the necessary data to inform the the user about apps that contain widgets or listen for boot_completed (or other components listed at that page), and could do this even for apps that don't allow move to sd in the manifest. > > > or use a > > large amount of data / cache storage (so move to sd makes sense), and > also > > have a widget or a service. > > "The .apk file is saved on the external storage, but all private user > data, databases, optimized .dex files, and extracted native code are > saved on the internal device memory." > http://developer.android.com/guide/appendix/install-location.html > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > _Android Programming Tutorials_ Version 3.1 Available! > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
