In google's Calendar app for Android OS, you will encounter this line in the onCreate method of CalendarActivity.
// Eliminate extra GCs during startup by setting the initial heap size to 4MB.
VMRuntime.getRuntime().setMinimumHeapSize(INITIAL_HEAP_SIZE)
Can someone explain why setting it to 4MB will eliminate GCs ? Thanks
View 1 Replies
I could set minimum heap size in the source code like below.
--> VMRuntime.getRuntime().setMinimumHeapSize(INITIAL_HEAP_SIZE);
But I want to set this value in android.mk or androidmanifest.xml.
I noticed when you create an AVD now that you can set an application max heap size. I found that when I did WVGA800 it was set to 24. So it looks like it's more than the 16 we are used to.
I there an API method to get the value of this max heap size? I haven't looked into that yet.
I am using SeekBar in my application, currently seek bar minimum value is zero, but as per application requirement seek bar value should not be zero. how to set minimum value for SeekBar.
View 2 Replies View RelatedI have an app which does a bunch of image manipulations, and those images are ideally full-screen sized. It works on a G1 (or HVGA emulator), but runs out of memory on a WVGA emulator instance, because full-screen images use twice as many pixels. Fine, I can work around it by manipulating smaller images, then scaling up to WVGA at the end. There's some loss of image quality, but this is unavoidable on a WVGA device with a 16MB heap limit, so I'll live with that.
When a real WVGA device hits the streets in the next couple of months, though, it's likely to have more than 16MB heap per app, for just this kind of reason. So for best image quality, I'd like my app to adapt to this situation, and use full-screen-sized images on such a device. IOW, I'd like to implement a heuristic which sets the image size based on heap size.
In order to do so, however, the app needs to know what the maximum heap size is, and I haven't yet found an SDK call which will return this information. The various Debug.get* memory calls all seem to be to do with how much heap you have *allocated*, not how much you theoretically *can* allocate. I understand that this isn't necessarily a hard number, that issues like fragmentation and GC mean that you may not actually be able to allocate every last byte, but a theoretical number would still be useful.
Can anyone point me to an SDK call I've missed?
I know that's a subject which was discuss a lot of time and I try to find a solution since more than 6 day for the memory leak which appears in my application.
I've read this page: http://www.curious-creature.org/2008/12/18/avoid-memory-leaks-on-andr...
So, I don't use static member fields, I always use recycle() and I don't use inner class.
My application use a gallery and some bitmap. I use finalize to monitor garbage collection in each class of my application: protected void finalize() throws Throwable {try {Log.d("FINALIZE", this.toString());} finally {super.finalize();}
I am developing an application in android..but i got an issue of getting an error..that is out of memory exception while i am converting my file contents to byte array..i think this is the problem of reduced heap size..can u plz tell me how can i increase the vm heap size..i am using eclipse...
View 1 Replies View RelatedHow do you programmatically detect the application heap size available to an Android app?
I heard there's a function that does this in later versions of the SDK. In any case, I'm looking for solution that works for 1.5 and upwards.
What exactly is this? What benefit do you get by changing it?
View 3 Replies View RelatedAnyone know (with our phones running 2.2) what the optimal heap size should be? The leaked 2.2 came with 24m preset. Some ROMs run 32m. Bigger always seems better, but I've been reading other sites/forums and get conflicting thoughts.
That's why I thought I'd ask here.
I ran Linpack with both and average about 37.5 - 37.9 with either 24m or 32m.
I learned from several discussions of this group that BitmapFactory.decodeFile() allocates heap memory outside of the "java heap". My app receives encrypted files from a remote server. Decoding those files needs a lot of heap space. After finishing this decoding step most of the allocated heap space will be freed by the GC. But the (total) heap size - as displayed by the DDM - remains large. In this situation there is not enough heap space outside of the "Java heap" to decode even medium sized image files using BitmapFactory.decodeFile(). At the moment I limit the size of encrypted files to ensure that the Java heap space never increases to more than 10 MB. This ensures that there is enough memory for BitmapFactory.decodeFile(). But this is not very elegant.
Is it possible to tell the dalvik-vm to reduce the (total) heap size to have more space for decoding images or is there another solution?
I'm wondering why the Nexus7 doesn't allow you to slow scroll/pan down at single pixel steps. Always seems to be in 2-3 pixel jumps. I got a bad habit of scrolling web pages while reading from iOS but on my N7 I get these kinda annoying start/stop jerks.
Is this related to the virtual pixel resolution being lower than the actual screen resolution? And would changing it allow one to match the virtual pixels to the screen pixels and get smoother slow speed panning?
The software team in our graduation project asked for increasing the heap size per process in Android. They said that the default is "16MB" which isn't sufficient for them.
How could I custom the size?
I found a commented line in the file: /acme/my_board/BoardConfig.mk in my android source code:
# USE_CUSTOM_RUNTIME_HEAP_MAX := "64M"
At the moment I am attempting to set my camera on my Motorola Droid phone to take an image that matches the size of my screen (854 x 480 pixels), and I am attempting to accomplish via the parameters for the camera as such:
CODE:.................
I have my activity implement the Camera.PictureCallback method of onPictureTaken (excluding log calls), so when the takePicture method is called it runs this method:
CODE:..........
For some reason though, my camera is taking pictures in 1280 x 960. Is this some sort of minimum size the camera can capture an image in? From log calls I can see that the Camera's parameters are still set to have a picture size of 854 x 480, but image keeps coming out as 1280 x 960. Am I decoding the image incorrectly, am I setting the camera's parameters incorrectly, or am I doing something else wrong?
It is clear that cross compilers will not be allowed by the Apple App Store, so a developer will need to be familiar with Objective-C to create applications for the iPhone.I was wondering, is there a cross compiler that will take Objective-C application code and rebuild it into a similar Java application that can be packaged for Android? That way, a developer could still learn just one language (obj-c) but put out applications on many devices.I understand that the Java port would be less optimal than a natively coded application, but could conceivably save a developer some time.
View 4 Replies View RelatedIs there off screen drawing possible in android like a imageContext in objective C. if it is kindly tell me the link or some kind of hint.
View 2 Replies View RelatedI've been playing with the K9 Email app as a replacement for the stock program. I rather like it, but there is a deal breaker. On my secondary gmail account (not the one the Eris is set up with, but another one that I set up in K9) the font size in the message is so tiny I can't see it. I've searched the options over and over to find a setting to increase the font size, but apparently I can't find it. Would any of you happen to know where it is?
View 12 Replies View RelatedI meant objective-c, not c#. Some reason I got it into my head it was c# the iphone used. So the answers for c# were great, thanks, but theyre a bit irrelevant, sorry about that.
I've had a look but can't find anything that answers this, though a few have shortened the question by answering parts of it. Between a small group, we were planning on doing some work on iPhone and Android, the 2 seperate for the most part but helping each other out, and with some guys doing graphics work split between them.
But we were thinking about the possibilities of moving things between the two, not necessarily apps, maybe just useful classes or something. Looking at objective-c and Java, they seem to have about the same features that the biggest obstacle would be system interface stuff, so we were wondering whether, if we created an abstraction over these on each system so they could be given the same input (which unless I'm wrong wouldn't put too much strain on the system?), would there be any problems in writing something to convert between objective-c and Java, worse than the locations of methods in the sdks? Or are there key features or something in one language that the other doesn't have which we've missed that would mean the only way to do it would be rewriting from scratch.
Does anyone know how to define a SeekBar's minimum value? Is this done in the XML layout or do I need to define it programatically?Basically I need to change my minimum value from 0 to 0.2
View 1 Replies View RelatedWhat's the minimum memory needed to run a RAR decompression algorithm? I want to port a RAR decompression algorithm to mobiles (iPhone, Android and BlackBerry) and want to know if there's a bare minimum of memory needed before starting. I've heard that RAR decompression requires much more memory than ZIP decompression.
View 3 Replies View Related07-01 11:32:02.192: VERBOSE/QualcommCameraHardware(35): state transition QCS_WAITING_JPEG --> QCS_IDLE 07-01 11:32:02.232: ERROR/dalvikvm-heap(395): 6291456-byte external allocation too large for this process. 07-01 11:32:02.232: ERROR/(395): VM won't let us allocate 6291456 bytes 07-01 11:32:02.242: DEBUG/AndroidRuntime(395): Shutting down VM 07-01 11:32:02.242: WARN/dalvikvm(395): threadid=3: thread exiting with uncaught exception (group=0x4000fe70) 07-01 11:32:02.242: ERROR/AndroidRuntime(395): Uncaught handler: thread main exiting due to uncaught exception 07-01 11:32:02.302: ERROR/AndroidRuntime(395): java.lang.OutOfMemoryError: bitmap size exceeds VM budget My app shut down when i load a jpg file,i can avoid it by call system.gc().But I think memory limit will be 14M or 16M.
View 24 Replies View RelatedDoes the 1.5 SDK still have the 16mB application heap limit? Is there any way to change it? Do you think this limit will persist into the forseeable future?
View 3 Replies View Relatedwhat do the following mean in the Heap view of *DDMS*:
1) Data Object
2) Class Object
3) 1,2,4,8-byte *array* : which arrays are we talking about here??
4) non- Java object
My question may look naive but I do not know how to formulate it more correctly. The problem is that I create and use large simple type arrays in my application.
And I get errors like: ERROR/dalvikvm-heap(1763): Out of memory on a 7907344-byte allocation.
Yes, it's big enough but task management tools claim that my application is using only 30MB of memory, while other at the same time use 50MB and even 110MB (have seen once) and there is still 190MB of free memory in the system (not system applications, just other ordinary applications I have installed). If all applications are provided with the same heap size at startup how can they grow so big?
I'm an Android game developer and I need to ask you a couple of questions about Android heap limit.
Does the 16 MB heap limitation also applies to OpenGL ES textures or SoundPool sound effects? Since they are managed by native code, is it correct to affirm that there is no problem in using more than 16 MB of RAM in app/game resources/assets? If it is possible right now, it is guarantee to be possible in the future?
I am working on an application for android and we since we have lots of graphics, we use a lot of memory.
I monitor the memory heap size and its about 3-4 Mb , and peeks of 5Mb when I do something that requires more memory (and then goes back to 3). This is not a big deal, but some other stuff is handled outside the heap memory, like loading of drawables.
For example if I run the ddms tool outside eclipse, and go to sysinfo, I see that my app is taking 20Mb on the Droid and 12 on the G1, but heap size are the same in both, because data is the same but images are different.
So the questions are: How do I know what is taking the memory outside the heap memory? What other stuff takes memory outside the heap memory? Complex layouts (big tree) ? Animations?
So from my understanding each application normally gets 16 mb memory to work with. This is what is shown on the heap tool for eclipse:
Heap Size: 4.5 mb
Allocated: 3.2 mb
Free : 1.5 mb
Used : 66.7%
Which one is the total memory being used? Heap size, or Allocated?
I want to give max and minimum limit of seekbar to 50 and 20 respectively. Seekbar has a direct option top provide max value,but how can i set its minimum value to 20 rather than 0?
View 2 Replies View RelatedWe're seeking advice for our application in the Android Market, in relation to nominating a suitable minimum SDK version for the APK files published through the market. We understand that at this juncture there's no facility to provide associate multiple APK files (supporting different minimum SDK versions) within a single listing in the Market.
We have updated our existing application with new Android 1.6 API features and are keen to release it to the Market. However we're concerned about the general availability (and uptake) of version 1.6 firmware and seeking to ensure that we don't inadvertently release an updated APK should there be limited release of this firmware.
Can anyone provide an indication as to how widely the 1.6 firmware has been released? To that end, what are generally acceptable practices for supporting multiple SDK versions from within the market?
I'm looking into using Monodroid for Android app development. I'd like to know what minimum version of Android is required for runnning Monodroid applications.
View 2 Replies View Related