Memory consumption of a typical Android implementation

by salza » Wed, 02 Sep 2009 16:56:23 GMT


Sponsored Links
 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?


--~--~---------~--~----~------------~-------~--~----~



Memory consumption of a typical Android implementation

by lbcoder » Wed, 02 Sep 2009 21:22:53 GMT


 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.




--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Memory consumption of a typical Android implementation

by salza » Wed, 02 Sep 2009 23:33:26 GMT


 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!




--~--~---------~--~----~------------~-------~--~----~



Memory consumption of a typical Android implementation

by lbcoder » Thu, 03 Sep 2009 22:31:46 GMT


 At the very simplest level, compiler optimization, such as the "-O"
parameter for gcc. Also, use of executable compression, like "upx".
Compressed or optimized filesystems -- certain read-only filesystems
can be packed in a way that maps multiple segments of code that just
happen to match over to the same physical location... Leaving out
redundant code segments. Image optimizations (i.e. reduced colorspace,
pngcrush, etc). There are literally hundreds of little tricks that can
be used to make things (*MUCH*) smaller.






--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. partner_setup command not found.

Building Android for a new Mobile Device..
I am trying to build android for new mobile device..
after making the directory and including the .mk files for every
product..
i am trying to build with ./envsetup.sh..
and then partner_setup <first_product_name>
getting error : command not found....

can anybody help plz....

refer the below link:
http://www.kandroid.org/android_pdk/build_new_device.html#androidOHDPortingDeviceBuildingProcess

-- 

2. HTC Desire 2?

Semoga menjadi kenyataan...
Siap aja ya :D

http://gpgo.in/ze

Follow us on twitter @gopegodotcom


---------------------
@yopiesuryadi
www.gopego.com
http://about.me/yopie

-- 
===============

3. [WTA] Tanya provider yang bagus untuk daerah depok ciracas

4. Driver usb fastboot ngak detek

5. galaxy 5 gabisa browser

6. failing to mount data partition with ubifs

7. Contact wrapper uses