I've traditionally kept my heap for other Android devices at 32MB. I've noticed with the Charge that it defaults to 48mb for Froyo and 64 for the newer GB releases. I've also noticed that putting it back to 32 seems to stop the home screen from continuously redrawing and a couple of other issues. Is there any downside to having a slightly smaller heap?
The way I understand it is it's for more performance when we use apps that require more memory. I keep mine at 40.
Where can you change the heap size?
It's in build.prop
I just use the VM Heap Tool, saves messing around in SQLite Editor.
I just use script manager.
Related
Hi everybody,
the new phone is great so far...
When go to Menu-Settings-Applications and click on Running on the bottom I see RAM stats. The readings are : 173 MB used and 383MB free. Adding them together getting 556MB. Isn't Desire S quoted to have 768MB of RAM???
heh ... mine currently adds up to 542.
cache and system reserved memory are not visualized
well... is there any app where you can check RAM ??? The ROM is 1.1Gb which is OK (main reason getting rid of Desire std) but really need to know if there's any "restriction" regarding RAM.
@heavyhms: I don't think cache and system reserved memory could eat up 200MB+ of RAM...
Taskpanel reports it as 611MB for me. But yeah, even the DHD only has 623MB of usable RAM.
pasan said:
Taskpanel reports it as 611MB for me. But yeah, even the DHD only has 623MB of usable RAM.
Click to expand...
Click to collapse
Thanx for the enlighting ...
So if D HD and D S having 600+MB of RAM (from quoted 768) then poor SEX10... quoted RAM is 384MB...
But SE X10 does not have sense ...
Also my DS RAM adds up to 559MB, so I'm guessing the rest must me cache and SR...
Most i have is almost 600MB.
System Panel reports:
/system 549.2MB
/data 1156.5MB
/cache 295.3MB
/mnt/sdcard 7572MB
So cache should be in /cache right? So what's actually using the "lost" RAM? Is it Internal System Processes? But it doesn't really add up to the total RAM.
Also, every time i open System Panel, there's always around 100MB of RAM available. I believe if there's a shortage of memory, it just puts some unused apps in the /cache.
Do correct me if i'm wrong.
+! always noticed that in android.. extra ram is cached for faster performance...?
Ion my sgs 2, i have 1Gb RAM, but only 800mb + altogether in system settings!
So the cache & SRM along with Sense UI. That makes me think how to get rid of Sense UI...
However,phone is smooth and fast...
Rexton270 said:
So the cache & SRM along with Sense UI. That makes me think how to get rid of Sense UI...
However,phone is smooth and fast...
Click to expand...
Click to collapse
Indeed it is. And I have not been using a task manager either, the OS is doing a very good job handling stagnant applications while maintaining a buffer of unused memory I use Tasker to automate several tasks, and Minimalistic Text for custom widgets (some invoking Tasker tasks), and even with all that in the background I have not yet had a slow down.
Hey.
I've been doing some odd work for a lower memory 7" tablet (256MB).
All it has so far is a stock android kbd, but Im wanting more (mainly because the port was horrible -- word predictions do not work, and its buggy at best).
I've tried quite a few different free kbds, but most sit over 20Mb -- 20Mb which I cant spare (since this device has about 60Mb of RAM available on a fresh install of my ROM).
So far the best kbd I've found is tap n tap, but thats still a little hefty in the RAM dept.
I don't need glam or shiny, just a regular kbd that is functional, working, low on memory/resources, and possibly designed for a tablet (although not necessary.).
Anyone have any suggestions?
Thanks in advance!!
Have u tried ultra Kb, or smart Kb?
☞★sent from my Galaxy SL!!
♪drajax!! *♂ツ
Keep in mind, I will be wanting a FREE kbd, as I will be incorporating it into my public ROM
What about Multiling Keyboard by Honso, it even has small apk file size.
i had a similiar issue and found those two
Simple Large Button Keyboard
- no permissions required*
- only 45kb size !!
- only 6,2 mb ram consumption on Android 4.0
Big Buttons Standard Keyboard
- no permissions required*
- only 135kb size
Other apps require more RAM, multicore, permissions and space (plus they come with ads and want your money). Some of them even rely on the integrated AOSP keyboard so you wont be able to disable this system app.
Mind: The integrated Android AOSP Keyboard (not Google Keyboard!) also has very low memory footprint (4,2 mb ram on Android 4.2 with all input "features" [like spelling corrections, etc. ] deactivated in settings) *BUT* is a pretty low performer with single cores and <= 1GHz. Therefore i prefer "Simple Large Button Keyboard" over the competitors for a low ressource/max effeciency scenario.
(*the privacy risk of keyboard sniffing is much lower without granted internet permissions)
I'd like to come up with a list of performance and battery optimizations for AOSP android devices. I will base this off of cyanogen, and it's derivatives, like evodeck, which is what I use.
I have a few questions. I will edit when I get answers, to include them.
For raw performance, which is better, Yaffs, or EXT2. Also, does that question actually fluctuate depending on which partition? I just became aware that EXT4 will be the new standard partition, but that's just EXT2, with extents (which on flash is worthless overhead), and journaling, which uses a lot of write cycles.
Does 3g turbocharger affect battery usage? Does it actually work?
What is people's opinion on v6 supercharger and 3g turbocharger?
Basic optimizations that I start off with for pure battery
Setup power control widget. Disable autosync on disable wifi, have 2g/3g disable or enable based off of background data.
Use HAVS custom kernel, with undervolt as far as you can go while maintaining stable, using vipermod. Use smartass governor. Some people perfer interactiveX.
If for whatever reason, you can not use a HAVS kernel, use setCPU to set your screen off settings to go to powersaver governor, just so it doesn't have to monitor use. Underclock your lowest speed to comfort level. I like 128MHZ on my evo.
For amoled screens, use black as often as you can, while for LCD screens, use white as often as you can.
Shut off haptic feedback, and other input based sounds.
Performance and battery
Disable Animations, of nearly any kind in settings. Set transparency to 16bit.
Consider lowering VM heap size, to prevent garbage collection, experiment as necessary.
If you have sufficent memory (512+), then lock messenger and homescreen in memory.
Consider using v6 supercharger to make android properly setup for the amount of ram that you have, instead of a generic value.
Remove DSP, since it increases processing usage.
Set noatime and nodiratime, to prevent disk writes.
Use push mail instead of polling to save battery.
Use a static wallpaper, or no wallpaper.
OK I understand Vm heap size has to do with memory and allocating a certain amount but from what I saw today I found to be kinda confusing...
I haven't changed it but when I went to go mess with it it was at a quite high value of 288.
That seems awfully high to me from the 24s and 32s I was reading today. So I have to ask what is the default VM heap size for the Tab Plus? I did a decent amount of googling but apparently my google mojo is working well today
Update on the matter. Rom toolbox says the heap is 288 when VM heap tool reports a default of 288 and a current value of 64.
Honeycomb on the SGT7+ defines three total heap sizes, that can be found in /system/build.prop
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=288m
heapstartsize is the size of a new Dalvik VM heap when initialized.
heapgrowthlimit is the size limit for normal Dalvik VM heaps.
heapsize is the size limit for Android apps that specify android:largeHeap=true in their application manifest.
heapgrowthlimit is the value that you would use to compare your tablet to phones running Android 2.3 and earlier.
Ah OK that makes sense now! Thank you good sir! (Or mam)
Haven't been around in a while. My wife has the MikTouch-0.5 Rom on her phone. Looking for a ROM recomendation with options to increase font size. I understand that ice cream sandwich can?
qwerty3656 said:
Haven't been around in a while. My wife has the MikTouch-0.5 Rom on her phone. Looking for a ROM recomendation with options to increase font size. I understand that ice cream sandwich can?
Click to expand...
Click to collapse
One method is to adjust the DPI setting on the rom. Using buildprop editor, you can adjust the setting "ro.sf.lcd_density". The default for the doubleshot (at least with the CM 9.1 build) is 240. Lowering this number reduces the size that objects display, but I assume that increasing it will increase the size. I do have to warn, I have not tried to do this--I generally use 200 as my dpi setting. Changing this setting may also adjust what market applications are available, just as a warning.
ebrandsberg said:
One method is to adjust the DPI setting on the rom. Using buildprop editor, you can adjust the setting "ro.sf.lcd_density". The default for the doubleshot (at least with the CM 9.1 build) is 240. Lowering this number reduces the size that objects display, but I assume that increasing it will increase the size. I do have to warn, I have not tried to do this--I generally use 200 as my dpi setting. Changing this setting may also adjust what market applications are available, just as a warning.
Click to expand...
Click to collapse
Adjusting the LCD density on my phone made it to where no Market app was available for download/update. The Amazon Appstore and SlideME still worked.
there are also some free and paid apps on the market now that do this, you'll find them if you search 'font size' in Google Play. they won't affect how the market sees your device, but with the bigger font but the space where the words go remaining the same, there will be places here and there where words might get cut off at the top or bottom.
Hello,
what I'm looking for is to change only some font sizes.
I tried some Market apps and modified also the DPI value in build.prop, but these change all font sizes (small, medium and big fonts).
I come from a HTC Desire with Sense 3.5 and now I have a rooted S-off DS4GS with CM 9.1 using this rom:
http://forum.xda-developers.com/showthread.php?t=1912582
Actually, text labels under homescreen icons, app drawer etc, look perfect, exacty the same as at my previous Desire, but with DS4GS some in-app texts or menu options look quite bigger now.
Are there different font sizes for small, medium and big fonts? If so, is it possible to configure each of them?
Thanks