Sounds very interesting! What optimizations are possible? I mean, does the user or the developer select the optimization type? Do you maybe know something where it is explained in detail?
Thanks! On Sep 2, 3:18 pm, lbcoder <[email protected]> wrote: > This can vary greatly from build to build and depends HEAVILY on the > optimizations selected. > > Memory use is a really tricky one to measure -- the memory will > typically be full. As new applications are opened, old ones are dumped > and their memory reclaimed. This is mainly on an as-needed basis. > > As for the flash memory install base... so far typical size is about > 60MB, but again, you can add or remove features given this same space > by various available optimizations. Much of this may have to do with > the fact that the actual available space on DREAM hardware is 67.5MB. > > On Sep 2, 4:55 am, salza <[email protected]> wrote: > > > I have seen many benchmarks about Android but not yet found a > > benchmark were the memory consumption of Android on a Qualcomm > > processesor has been measured. > > I have already found a discussion in here where someone emulated > > Android but that is not representative for a smartphone evironment. > > Has anyone of you already experimented with that and knows the typical > > Flash an RAM consumption for the standard implementation with core > > applications? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
