The 16MB is not a hard limit built in to the APIs, it is a current limit based on the hardware we are actually running on. It is also a little tricky to raise the limit, because it would require making the VM's garbage collector smarter in how it manages memory: right now it mmaps a memory region that is this maximum size, so if we make that maximum larger we can start running out of address space. This is something that can be fixed relatively easy (again it is not baked into the APIs), but won't be done for 1.0.
On Jun 12, 1:22 am, whitemice <[EMAIL PROTECTED]> wrote: > >>...On top of this, by the time Android is fully loaded on a 64MB device > >>only 10-20MB of RAM will probably remain.* So, essentially your application > >>would use all system resources...<< > > "640K ought to be enough for anybody" > - Bill Gates (apparently) --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
