To G1 the community.
Can I have your assistance in building a list of Current Roms, a Benchmark Speed Result and the settings you have your phone set at.
Benchmark Results are taking from 'Quadrant Standard' Market Link >https://market.android.com/details?id=com.aurorasoftworks.quadrant.ui.standard&feature=search_result
Here are my settings to kick things off, PLEASE NO CHAT, just pure stats & settings.
My hope is to find a ROM / Setup which is near as perfect and as fast as possible, I see a lot of post about an AWESOME Rom that is SUPER FAST but when I try it it either becomes unstable or is laggy.
The aim of this data gathering is try and achieve the best possible setup dependent on which ROM you are using.
COPY & PASTE & COMPLETE WITH YOUR PERSONAL SETUP.
ROM -
ANDROID VERSION -
KERNEL -
CPU -
MIN -
MAX -
COMPCACHE RAM -
JIT -
DITHERING -
VM HEAP SIZE -
LAUNCHER -
QUADRANT RESULT -
=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My Settings - based on a fresh SUPERWIPE and flash.
ROM - FROYO by LAZLO 5.2
ANDROID VERSION - 2.2.1
KERNEL - [email protected]#1
CPU - ONDEMAND -
MIN - 176
MAX - 595
COMPCACHE RAM - 18%
JIT - OFF
DITHERING - OFF
VM HEAP SIZE - 24m
LAUNCHER - LAUNCHER7
QUADRANT RESULT - 318
THANKS to all who provide details below.
My Settings - 4 weeks after flashing, no reboot for about 40 hours.
ROM - FROYO by LAZLO 5.2
ANDROID VERSION - 2.2.1
KERNEL - 2.6.34.8-cm6-
[email protected]#1
CPU - PERFORMANCE -
MIN - 176
MAX - 595
COMPCACHE RAM - ON
JIT - ON
DITHERING - ON
VM HEAP SIZE - 24m
LAUNCHER - Zeam Launcher
QUADRANT RESULT - 338
Phone G1
Radio/SPL 2825/1.33.0013d
ROM - COS-DS (self compile = repo sync 28th Apr a.m)
ANDROID VERSION - 2.3.3
KERNEL - 2.6.36.4-cos [email protected] #1
CPU - performance -
MIN - 245
MAX - 575
COMPCACHE RAM - OFF
JIT - ON
DITHERING - OFF
VM HEAP SIZE - 16m
LAUNCHER - ADW Ex (but launcher has nothing to do with it)
QUADRANT RESULT -500 , second run 442, third run 478 , 4th 512, 5th 525 = avg 491.4 ( discounting highest and lowest ) 496.666666667
Other- data data bind, ext4 no journal
Notes frequent reboots if usb is plugged in
with symlink /data/data/com.au... to /dev/ I get 569
its all down to I/O, no journal = faster r/w on sd-ext
Phone G1
Radio/SPL2825/1.33.0013d
ROM - CM7 Magpie 110324
ANDROID VERSION - 2.3.3
KERNEL - 2.6.36.4-s1-ezgb-v1
CPU - performance -
MIN - 245
MAX - 575
COMPCACHE RAM - OFF
JIT - ON
DITHERING - OFF
VM HEAP SIZE - 16m
LAUNCHER - ADW Ex (but launcher has nothing to do with it)
QUADRANT RESULT - 416
Other- data data bind, ext4 no journal
Notes steady as a rock (no issues with reboot when usb plugged)
ROM - SuperAOSP 6.0
Radio/SPL - 28.35/1.33.0013d (Noticed this added above and it made sense to include it)
ANDROID VERSION - 2.3.3
KERNEL - 2.6.35.9-SuperBler
CPU - On Demand
MIN - 128mhz
MAX - 614mhz
COMPCACHE RAM - Disabled
JIT - On
DITHERING - Off
VM HEAP SIZE - 16MB
LAUNCHER - LauncherPro (Yea, installed over stock ADW as usual)
QUADRANT RESULT - 338 (Seriously....... 500 above? -.- Seems a bit far fetched without moderate sacrifice of something valuable.
It's running as smooth as a peach though. I couldn't begin to ask for more.
you may also put a hyperlink to the rom you used. i think it is pretty usefull for those who see your results.
Chocolate Columbo said:
QUADRANT RESULT - 338 (Seriously....... 500 above? -.- Seems a bit far fetched without moderate sacrifice of something valuable.
Click to expand...
Click to collapse
Benchmarks (this one for sure) can be "cheated". That's why it says nothing what you score. My current tweaked Rom (Cya5.08) scores like sh*t on this benchmark but in practice it's faster than most GB-Roms. Especially after using the phone heavily for some time.
So while it's nice to brag about the scores but it doesn't necessarily mean the phone itself in use is any faster.
Thanks to all who replied - many people have read this thread but not left a comment I hope they found it as useful as I did.
It was more of a information gathering exercise than anything else.
Really helpful though.
Phone HTC Magic
Radio/SPL2825/1.33.0013d
ROM - ADS_Magpie_ezGingerbread 280411
ANDROID VERSION - 2.3.3
KERNEL - 2.6.36.4-s1-ezgb-v1
CPU - interactive
MIN - 176
MAX - 576
COMPCACHE RAM - 12MB (ZRAM)
JIT - ON
VM HEAP SIZE - 16m
LAUNCHER - Zeam Launcher 2.8.8
QUADRANT RESULT - 322
Other - No reboot / FC. A bit sluggish on startup, but better after a few minutes
ROM - ezGingerbread (self compiled about half an hour ago)
ANDROID VERSION - 2.3.3
KERNEL - 2.6.36.4-s1-ezgb-v1
CPU - conservative
MIN - 122
MAX - 537
COMPCACHE RAM - none
JIT - on
DITHERING - off
VM HEAP SIZE - 16m i think.... whatever is the stock setting
LAUNCHER - launcher2
QUADRANT RESULT - 315 (hm.... feels much faster.... oh well.)
Phone G1
Radio/SPL 2825/1.33.0013d
ROM - ADS_Magpie_ezGingerbread 280411
ANDROID VERSION - 2.3.3
KERNEL - 2.6.36.4-s1-ezgb-v1
CPU - performance
MIN - 245
MAX - 576
COMPCACHE RAM - OFF
JIT - ON
VM HEAP SIZE - 16m
LAUNCHER - ADW Ex
QUADRANT RESULT - 365 , 315 , 340 , 348 , 330
Other : ddb, ext4 with no Journal
Notes: I/O is around 200, half of what I get with COS.
Even after editing 05mountsd to mount as ext4 (not auto) I still get ~200
conclusion the high COS benchmarking is due to I/O tweaks
These tweaks may or may not improve real performance, but they certainly improve Quadrant Benchmark
in real use I find ADS more responsive than COS,
final conclusion
Quadrant is pants
PHONE - T-Mobile MyTouch 3G
RADIO/SPL - 2.22.28.25/1.33.0013d
ROM - CyanogenMod 6.1.0 Stable
ANDROID VERSION - 2.2.1
KERNEL - 2.6.35.13-farmatito-pershoot-ds+
CPU - ondemand
MIN - 245 MHz
MAX - 528 MHz
COMPCACHE RAM - OFF
JIT - OFF
VM HEAP SIZE - 16m
LAUNCHER - LauncherPro
QUADRANT RESULT - 316
ROM - COS-DS 4/27/11
ANDROID VERSION - Gingerbread 2.3.3
RADIO/SPL - 2708/1.33.0013d
KERNEL -2.6.36.4-cos [email protected] #1
CPU - on demand
MIN - 245
MAX - 528
COMPCACHE RAM - 18%
JIT - Enabled
DITHERING - Disabled
VM HEAP SIZE - 16m
LAUNCHER - Launcher Pro
QUADRANT RESULT - 324
Other: After a fresh superwipe.
ROM - COS-DS-04262011-Full
ANDROID VERSION - 2.3.3
KERNEL - 2.6.36.4-s1-cos
CPU - CONSERVATIVE
MIN - 128
MAX - 614
COMPCACHE RAM - DISABLED
JIT - ENABLED
DITHERING - DISABLED
VM HEAP SIZE - 12m
LAUNCHER - ADW (Stock)
QUADRANT RESULT - 354
ROM - COS-DS-07182011
ANDROID VERSION - 2.3.4
KERNEL - 2.6.36.4-s3-cos [email protected] #1
CPU - CONSERVATIVE
MIN - 245
MAX - 576
COMPCACHE RAM - DISABLED
JIT - ENABLED
DITHERING - DISABLED
VM HEAP SIZE - 16m
LAUNCHER - LauncherPro
QUADRANT RESULT - 470~520
SD-EXT enabled, data/data bind, no journal (that's what made it go to upper 400s)
T-Mobile MyTouch3G 1.2
ROM - SuperBler-MVZ-MD-4
ANDROID VERSION - 2.2.1
KERNEL - 2.6.34.8-cm6-biffmod ezterry
CPU - on demand
MIN - 245
MAX - 528
COMPCACHE RAM - no
JIT - no
DITHERING - no
VM HEAP SIZE - 16mb
LAUNCHER - Launcherpro
QUADRANT RESULT - 316
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.
I deleted SetCPU and SD Card Boost, installed Rom Toolbox since it has a lot of features including CPU slider.
ROM: Gummy Froyo 2.2
My Settings
CPU 1400 / 100 min / smartass
Build Prop Tweak:
VM Heap: 96m
Max Events: 60
Auto Memory Manager:
Preset: Mild
Foreground Apps: 1MB
Visible App: 3MB
Secondary Server: 78MB
Hidden App: 78MB
SD Boost: 2048kb
Sysctl Tweaks
Min Free Kbytes: 2746
Dirty Ratio: 90
Dirty Background Ratio: 65
VFS Cache: 25
Oom Kill Allocating Task (unchecked)
Problem:
Phone freezes when playing games such as GT Free+ HD and Homerun Battle 3D
I don't play games but my
vm heap 80m
max events 150
memory 10mb
16mb
24mb
48mb
52mb
72mb
sd boost
2048kb
min free 2098
dirty ratio 65
dirty backround 35
vfs cache 48
oom checked
Thanks. Anyone else?
Sent from my SCH-I510 using XDA App
Though you may have a newer and more powerful 1GHz processor, otherwise your phone is not unlike the HTC Evo 4G. Give the following a try. A bit of it will seem quite unorthodox, but I believe that you may be stunned by the improvement:
My Settings
CPU 1400 / 100 min / smartass
Build Prop Tweak:
VM Heap: 48m (or 64MB works well, too)
Max Events: 150
Auto Memory Manager:
Preset: Mild
Foreground Apps: 6MB
Visible App: 12MB
Secondary Server: 40MB
Hidden App: 60MB
Content Provider: 80MB
Empty Application: 100MB
SD Boost: 2048kb
Sysctl Tweaks
Min Free Kbytes: 8192
Dirty Ratio: 95
Dirty Background Ratio: 60
VFS Cache Pressure: 200
Oom Kill Allocating Task (unchecked)
Good luck!
What about for a LG G Stylo LGMS631
how much you is VM heap size ?
Stock ICS has 120+ MB VM heap size
bump ....
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)