Database Users

Whats the fastest custom rom?

yeah whats everyones fastest most stable combination?mine so far would be nfinitefx45 deoxed stock rom with a 768 overclocked kernal.and the new CyanogenMod-6 rc is pretty fast!with the uncapped kernal

Cyanogen 6 with dec s uncapped kernel clocked to 768. Using battery tweak, juice defender, jit enabled, surface dithering disabled, home locked in memory. I get about 420 on quadrant and around 5.2 mflops
Sent from my HERO200 using XDA App

cyanogen
i recently installed cyanogen 6 with the google addon.
What is the " with dec s uncapped kernel clocked to 768. Using battery tweak, juice defender, jit enabled, surface dithering disabled, home locked in memory" you are refering to?
I currently use set cpu to overclock to 691. I currently am only getting just under 3 mflops and just under 400 on quadrant.

jblair496 said:
i recently installed cyanogen 6 with the google addon.
What is the " with dec s uncapped kernel clocked to 768. Using battery tweak, juice defender, jit enabled, surface dithering disabled, home locked in memory" you are refering to?
I currently use set cpu to overclock to 691. I currently am only getting just under 3 mflops and just under 400 on quadrant.
Click to expand...
Click to collapse
Decad3nce has an uncapped Kernel - the stock cm6 one is capped so users with older chips (without the "With Google" branding) can boot.
Battery Tweak by Dec and Collin_Ph improves battery life by installing a small user defined service (I can't remember what exactly it does)
Juice defender is an app in the market that controls battery use of apps.
JIT - "Just In Time" compiling - very techy stuff here but more or less gives you more MFLOPS - but our Heros dont have enough ram for it to truely be effective.
Surface Dithering is a CM6 option that makes the screen look better. Google the term and see what it does for photos and stuff.
Home Locked in memory keeps the OS from flushing it from cache and causing a few issues, like hitting the home button and all the screens being blank for a second while it populates them.
So the above statement is just his lits of configs that make the device run best for him. But remember MFLOPs and Quadrants aren't everything Alot of it is feel.

Wow that was nice and detailed explanation. I'd up vote it if I could.
I haven't used the uncalled kernal. I have with google branding. I think I'll try it anyway.
Cm6 fresh install seems faster than any other rom I've ever tried. I turn off eye candy and it flies
Sent from my HERO200 using XDA App

lol
pancake 0.1 jk
RegawMOD 2.1t

regaw_leinad said:
lol
pancake 0.1 jk
RegawMOD 2.1t
Click to expand...
Click to collapse
Damn Regaw is on the ball lately.
Haven't seen you post in a while. Still in school?

My phone seems to be handling uncapped kernal quite well after all
Sent from my HERO200 using XDA App

Kcarpenter said:
Damn Regaw is on the ball lately.
Haven't seen you post in a while. Still in school?
Click to expand...
Click to collapse
haha, yeah I just got back into this again from that damn break. It's still summer time, but I'm playing on a cruise ship for a year starting in a few weeks.

regaw_leinad said:
haha, yeah I just got back into this again from that damn break. It's still summer time, but I'm playing on a cruise ship for a year starting in a few weeks.
Click to expand...
Click to collapse
I've though of doing that from time to time but don't seem to be suited for any of the jobs they offer Americans at decent wage. I'm best suited for engine room with my navy training. Reason to go with cruise line would be to see nicer destination ports
Sent from my HERO200 using XDA App

I gave up using Fresh ROM because it was getting laggy and we haven't had an update since August, so I finally made the switch to Cyanogen's RC1. Overclocked to 768 mhz, I've been getting 438 consistently on Quadrant. Linpack has been giving me varying results around 3 MFLOPS. The best I've gotten was 3.25.
I'm really curious as to how other Heroes do!

jcha said:
I gave up using Fresh ROM because it was getting laggy and we haven't had an update since August, so I finally made the switch to Cyanogen's RC1. Overclocked to 768 mhz, I've been getting 438 consistently on Quadrant. Linpack has been giving me varying results around 3 MFLOPS. The best I've gotten was 3.25.
I'm really curious as to how other Heroes do!
Click to expand...
Click to collapse
Switch to CM 6.1.0, very fast and stable

where can we find this Home Locked in memory app?
Kcarpenter said:
Decad3nce has an uncapped Kernel - the stock cm6 one is capped so users with older chips (without the "With Google" branding) can boot.
Battery Tweak by Dec and Collin_Ph improves battery life by installing a small user defined service (I can't remember what exactly it does)
Juice defender is an app in the market that controls battery use of apps.
JIT - "Just In Time" compiling - very techy stuff here but more or less gives you more MFLOPS - but our Heros dont have enough ram for it to truely be effective.
Surface Dithering is a CM6 option that makes the screen look better. Google the term and see what it does for photos and stuff.
Home Locked in memory keeps the OS from flushing it from cache and causing a few issues, like hitting the home button and all the screens being blank for a second while it populates them.
So the above statement is just his lits of configs that make the device run best for him. But remember MFLOPs and Quadrants aren't everything Alot of it is feel.
Click to expand...
Click to collapse

Jit, surface dithering and home locked are settings in cm6. Not apps. I have cm6 vanilla and tried extremely blue Rom, best things ever. And constantly updated. It's nice to know they care. Thanks to all u devs by the way

Best Way to Improve Performance

So I am wondering what others opinions are of the roms and kernels available for the SF. Doesn't seem to be much of an improvement on Quadrant scores utilizing another rom or even stupidfast kernels.
Are we just kind of screwed a bit until 2.2? Is there a kernel that is overclocked?
TIA.

Quadrant scores are mostly meaningless, and 2.2 is unlikely to be revolutionary. The phone performs well on 2.1 - keep reading the forum and you'll get there.

In my opinion the biggest performance increases ive seen werent in any benchmarks but in dj05. it runs amazing. If u havent tried it i dont know whether you should or not. With the impending froyo release no one knows if they are actually going to release DJ05 or not. I think they should release it and then put froyo on top of that foundation if at all possible
Sent from my SCH-I800(tab) using ksizzle9's crazy kool ROM(bone stock with root) from within the XDA App

What do you feel about DJ that helped it out?
I finally stayed with just a Voodoo lag kernel. There certain operations on the phone I had gotten used to that were slow. The kernel with lag fix did show me noticeable improvement, more than just a higher I/O score in Quadrant.
I think the phone is fairly solid on 2.1 but needs a little help. Hopefully the Froyo upgrade really is around the corner but Im not holding my breath

jfigura said:
What do you feel about DJ that helped it out?
I finally stayed with just a Voodoo lag kernel. There certain operations on the phone I had gotten used to that were slow. The kernel with lag fix did show me noticeable improvement, more than just a higher I/O score in Quadrant.
I think the phone is fairly solid on 2.1 but needs a little help. Hopefully the Froyo upgrade really is around the corner but Im not holding my breath
Click to expand...
Click to collapse
I'm running DJ05 deox, and the stock DJ05 kernel. I used Titanium Backup to remove all the bloatware, and I use ADW instead of TouchWiz crap. (I took TW off with Titanium Backup too). SetCPU to set max to 1ghz, and minimum to 400mhz. (NO PROFILES!!!) It runs just fine for me. Rather damn speedy actually!! I dont do the whole benchmark test business, doesn't really mean much IMO.

Yes benchmarks dont mean too much. But they are a good indication of overall performance in their specific areas that they test. As they fascinate test well in every area except i/o. But we already kne that. Im not sure what about DJ05 Made it feel so solid to me just overall improvement and actual working GPS
Sent from my SCH-I800 using XDA App

ksizzle9 said:
Yes benchmarks dont mean too much. But they are a good indication of overall performance in their specific areas that they test. As they fascinate test well in every area except i/o. But we already kne that. Im not sure what about DJ05 Made it feel so solid to me just overall improvement and actual working GPS
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
Where did you get the dj05 update?
Sent from my SCH-I500 using XDA App

Ive only tried voodoo/lagfix
It made a significant difference on my phone. I reverted and restored all the factory stuff in anticipation of JD05 because I want to get it OTA when it drops.
I tried to get the leaked one in IRC but people just kept calling me n00b so I gave up.
I am hopeful that it will solve all my woes and usher in a new era of speed only previously dreamt about

Powell730 said:
Where did you get the dj05 update?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
its been discussed dozens of times where and how to get dj05

joe3681 said:
I'm running DJ05 deox, and the stock DJ05 kernel. I used Titanium Backup to remove all the bloatware, and I use ADW instead of TouchWiz crap. (I took TW off with Titanium Backup too). SetCPU to set max to 1ghz, and minimum to 400mhz. (NO PROFILES!!!) It runs just fine for me. Rather damn speedy actually!! I dont do the whole benchmark test business, doesn't really mean much IMO.
Click to expand...
Click to collapse
ksizzle9 said:
Yes benchmarks dont mean too much. But they are a good indication of overall performance in their specific areas that they test. As they fascinate test well in every area except i/o. But we already kne that. Im not sure what about DJ05 Made it feel so solid to me just overall improvement and actual working GPS
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
@Joe: same setup here (DJ05 deo, Stock Kernel and Rom, Frozen bloat in Titanium) without SetCPU. It's FAST. My GF and both my sons have EVOs running 2.2 and my Fascinate is just as fast (or faster)
@ksizzle: I agree, it's hard to quantify exactly what is so good about it. I think it's not what's there, but what's NOT there (lag) I think there are going to be plenty of happy n00bs when the OTA hits. This phone will be a screamer right out of the box!

NOsquid said:
Quadrant scores are mostly meaningless, and 2.2 is unlikely to be revolutionary.
Click to expand...
Click to collapse
Actually, the real performance difference between 2.2. and 2.1 is very revolutionary, though I certainly agree with you about the irrelevance of Quadrant scores. The Java virtual machine, for example, executes code 450% -- that's not a typo -- faster, which directly impacts most apps.
And, 2.2's browser is also significantly faster than 2.1's -- and iOS4's, for that matter.
I like my Fascinate, and yes, I would consider it fast (especially running DJ05 with Geeknik's kernels) but like many others, I too see slowdowns sometimes that just shouldn't happen with the phone's hardware. Froyo isn't a magic pill, per se, but it should significantly reduce or eliminate those slowdowns (as it did on my old Droid 1, despite it's far-slower processor).
http://crave.cnet.co.uk/mobiles/and...r-vs-android-15-cupcake-speed-taste-49305763/
http://www.androidpolice.com/2010/0...-it-compared-to-2-1-oh-only-about-450-faster/
http://arstechnica.com/gadgets/news/2010/07/android-22-demolishes-ios4-in-javascript-benchmarks.ars

Actually, the real performance difference between 2.2. and 2.1 is very revolutionary, though I certainly agree with you about the irrelevance of Quadrant scores. The Java virtual machine, for example, executes code 450% in benchmarks -- that's not a typo -- faster, which do not directly impact most apps.
Click to expand...
Click to collapse
Fixed that for ya. Don't let marketing hype get the best of ya.

Everything I've read states that the performance improvements between 2.1 and 2.2 have little effect on Hummingbird processors (which is what is in all Galaxy S phones), and the biggest performance gains are seen on Snapdragon processors. As far as performance goes, I'll believe it when I see it.

imnuts said:
Everything I've read states that the performance improvements between 2.1 and 2.2 have little effect on Hummingbird processors (which is what is in all Galaxy S phones), and the biggest performance gains are seen on Snapdragon processors. As far as performance goes, I'll believe it when I see it.
Click to expand...
Click to collapse
This is because JIT was designed specifically around a Snapdragon processor.

wow...the vibrants ram is crap....

Im running on simply honey 3.5 gingerbread.... I cant even leave the browaer open to go back to check my facebook without comibg back seeng it reload... and i never get more than 150+ free memory... my aunts iphone 3gs has more free ram... and i know that it has 512mb shared but seriously.. Compared to other 512mb phones this is bull****... they get more than 200mb user ram...

Isn't that based on your internet connection, not ram? lol
and misclicked and hit thanks on accident. -_-

No...i cant multitask more than 4 simple apps at a time withought it shutting them off... terrible..

Mine's working just fine to be quite honest..what are these "simple apps" of yours?

Must just be the ROM.
I have facebook, web browser, twitter, engadget, xda, and more multi-tasked on Bi-Winning and they aren't ever closed.

helikido said:
Im running on simply honey 3.5 gingerbread.... I cant even leave the browaer open to go back to check my facebook without comibg back seeng it reload... and i never get more than 150+ free memory... my aunts iphone 3gs has more free ram... and i know that it has 512mb shared but seriously.. Compared to other 512mb phones this is bull****... they get more than 200mb user ram...
Click to expand...
Click to collapse
Are you retarded?
Really?
There's so much wrong with your post that I don't even know where to begin. Hence why I ask:
Are you retarded?

Text plus..... facebook... music and web

R u stupid?
all the people who have replied.underatood what i asked PERFECTLY!!
Hence i ask..
r u stupid?
@ruther...

Longcat14 said:
Must just be the ROM.
I have facebook, web browser, twitter, engadget, xda, and more multi-tasked on Bi-Winning and they aren't ever closed.
Click to expand...
Click to collapse
Well i dont have problems on 2.2.1 roms but on every ginger rom like asgard and simply honney.... the ram is basicly crap cuz ginger takes like 210mb on startup :/

Its not the rams fault for processes being killed. Its the ROM/ Kernel your on. You don't want processes being killed use less aggressive LMK settings. The ram on the vibrant works perfectly as it should, this is merely a case of your system not being optimized for what you want. So simply....go fix it. Use less aggressive setting for LMK and a kernel with more user ram. But to be honest this thread has been repeated 1billion times over and people just need to get over the fact that Linux/Android IS NOT LIKE WINDOWS...free ram is wasted ram
Sent from my SGH-T959 using Tapatalk

Well it's clearly the rom/kernel's fault. Just go back to 2.2 roms if you're facing issues.
Sent from my SGH-T959 using XDA App

ECOTOX said:
Its not the rams fault for processes being killed. Its the ROM/ Kernel your on. You don't want processes being killed use less aggressive LMK settings. The ram on the vibrant works perfectly as it should, this is merely a case of your system not being optimized for what you want. So simply....go fix it. Use less aggressive setting for LMK and a kernel with more user ram. But to be honest this thread has been repeated 1billion times over and people just need to get over the fact that Linux/Android IS NOT LIKE WINDOWS...free ram is wasted ram
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Thank you for having the patience to write it out. Perfectly put.

also, if youre using a RAM optimization app, that could be doing it as well...

ECOTOX said:
Its not the rams fault for processes being killed. Its the ROM/ Kernel your on. You don't want processes being killed use less aggressive LMK settings. The ram on the vibrant works perfectly as it should, this is merely a case of your system not being optimized for what you want. So simply....go fix it. Use less aggressive setting for LMK and a kernel with more user ram. But to be honest this thread has been repeated 1billion times over and people just need to get over the fact that Linux/Android IS NOT LIKE WINDOWS...free ram is wasted ram
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
This. Couldn't have said it any better Eco.

It's a setting you have on which is likely set to "Agrressive" meaning the minute the ROM doesn't think you need an app, it closes it, regardless of RAM. I can run quite a lot of apps simultaneously all the time. Not a RAM problem.

ECOTOX said:
Its not the rams fault for processes being killed. Its the ROM/ Kernel your on. You don't want processes being killed use less aggressive LMK settings. The ram on the vibrant works perfectly as it should, this is merely a case of your system not being optimized for what you want. So simply....go fix it. Use less aggressive setting for LMK and a kernel with more user ram. But to be honest this thread has been repeated 1billion times over and people just need to get over the fact that Linux/Android IS NOT LIKE WINDOWS...free ram is wasted ram
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Yes, +1.... I Also Say thank you to Ecotox for articulating how Android works so well.
Furthermore, 2.3 roms really only face a 2-3 of real issues:
Because of porting and lack of dedicated Vibrant drivers we have too much battery demand/drain.... the lack of GPS because of no source code or drivers.... because of lack of drivers there are a few small hesitations as a result of porting.
But that said, All in All, the developers have done nothing shy of remarkable work getting these ported roms to work nearly perfectly...... their skills is why we have such choices.
Rather than complaining.......... try to be part of the solution rather than part of the problem/noise..........

Thanx everyone... now I understand.
What app is there on the market or anywhere that can have me set the ram from agresive to least agresive cuz I don't think spare parts work.

Cm7- Vm Heap Size on Htc Wildfire- Performance optimization

Hello,
two days ago i changed the size of my Vm-heap to 32mb. I was curious after i read in some posts that this could affect the performance of resource-intensiv apps. As i am using navigon-navigation a lot i had to give it a try...
After ive changed it and rebootet the device, navigon works MUCH better then before, track calculation is much faster and the app is much more responsive and running fluent. The difference is highly noticeable. For other apps like my browser i experiecend the same.
I read that the downside of it is that it is possible that apps could be moved out of memory because some other apps now use more ram and so the jumping between apps could be more time intensive. But i have noticed no slow down at all.
(Wildfire is not a fast phone, but i think 384 mb ram is really good for that kind of phone, some other phones like galaxy ace have only 287 RAM with better cpu)
My experience is that a lot of apps running much better know, and for me its a absolute performance enhancement, I would even go so far that i would say it was the best performance-enhacement after overclocking the device. So if you are running resource-intensive apps (like navigation browsing) you should definitely give it a try.
Whats your experience with that ? Ever changed the vm heap size? Noticed differences??
Cheers.

im rocking 32 since i s-off my phone with alpharevx beta,and yes its better for intensive apps (imo) but the one thing i cant understand is way my phone i lagging when i get a call??some times the ringtone is playing and the screen is black,any tips thx

darkstep said:
im rocking 32 since i s-off my phone with alpharevx beta,and yes its better for intensive apps (imo) but the one thing i cant understand is way my phone i lagging when i get a call??some times the ringtone is playing and the screen is black,any tips thx
Click to expand...
Click to collapse
im running my phone with the ondemand governor with cpu-min:528 and cpu-max:691 and i have no lag when someone is calling.

Nhs666 said:
im running my phone with the ondemand governor with cpu-min:528 and cpu-max:691 and i have no lag when someone is calling.
Click to expand...
Click to collapse
It is indeed said that such lag is due to the 'extreme' underclocking of the processor.
I'm on CM7 RC1, use SMARTASS with 245 as a minimum, and haven't noticed any lag yet..
Sent from my HTC Wildfire using XDA App

ErwinP said:
It is indeed said that such lag is due to the 'extreme' underclocking of the processor.
I'm on CM7 RC1, use SMARTASS with 245 as a minimum, and haven't noticed any lag yet..
Click to expand...
Click to collapse
I didn't want to implicate that the ringing lag is about the low freq., but i noticed that with such low freq's the phone is not so responsive when pulling suddenly the notificationbar, get it out of standby and such things. Never noticed something like that??

I was testing about it too. i settled with 32mb heap size, which i've found to be the best practice. Anything lower would make apps like navigon or opera lag, anything higher, would give me force closes on apps for some reason.
I also tried to experiment with compcache, with the following settings "disabled, 18%, 26%" and i think 26% makes my wildfire a bit snappier, although it might be just a placebo effect, because there's no difference in quadrant/linpack benchmarks.

why placebo effect....the question is how good can a benchmark represent the practial application in daily usage. Anybody?
I tried vm heap bigger than 32mb too. But while running navigon it seems to me not much as a big improvement so i switched back.
The compcage thing will be the next thing im testing.

Nhs666 said:
why placebo effect....the question is how good can a benchmark represent the practial application in daily usage. Anybody?
I tried vm heap bigger than 32mb too. But while running navigon it seems to me not much as a big improvement so i switched back.
The compcage thing will be the next thing im testing.
Click to expand...
Click to collapse
I have to agree with you Whatever makes my phone "feeling" snappier and faster is good enough in my eyes!
You should really check Juwes Ram optimization thread in the Android development section for some serious performance gain. I flashed it yesterday in CM 7.1 Nightly 144 and the responsiveness boost is quite noticeable.

i agree the synthetic benchmarks are not that important its the daily use performance that mater to me

I have disabled compcache and enabled swap and my phone is snappier than 18%compcache may be Coz of compressing and decompression techniques that slow the process in compcache and scores 3.9 to 4.1 on linpack score with 576 MHz speed...
Sent from my HTC Wildfire

vijaykirann said:
I have disabled compcache and enabled swap and my phone is snappier than 18%compcache may be Coz of compressing and decompression techniques that slow the process in compcache and scores 3.9 to 4.1 on linpack score with 576 MHz speed...
Sent from my HTC Wildfire
Click to expand...
Click to collapse
Hmm i have a swap partition already made just in case and i might try it, but in theory a swap partition (even worse if it's a file) is much slower than the compressed cache due to the SD Speed limitations, unless we are discussing about class 10 cards.
anyone ?

[Q] V6 SuperCharger on MyTouch 4G?

It sounds like everyone would benefit from using this script, but there's no specific guidance for the MyTouch 4G. I assume option 8 or 9 would be best since the phone has 512MB of ram.
Are there some roms that we shouldn't be using V6 SuperCharger with?
Link to V6 SuperCharger: http://forum.xda-developers.com/showthread.php?t=991276

You're wrong on 2 points (possibly more):
1) This script is just the same as Autokiller app, with a small addition - it can (or can't) keep launcher in memory. Nothing new and revolutionary. This app exists for a couple of years.
2) This phone has 768MB of RAM. It won't benefit from a low memory killer (or actually, different settings for an existing in OS lowmemkiller), because it has TONS of memory. I just took a look at my phone, ~100MB of memory free, and ~300MB of remaining memory is taken by CACHED apps. If you don't know what it means - please read up on Android memory management, and I'll give you the short version - it's the same as free memory, but better.

It states in the first post:
Also Note: Nothing else does what The V6 SuperCharger does!
................Not AutoKiller Memory Optimizer, Not Auto Memory Manager, Not Minfree Manager...
The Nook Color has 512 MB of ram and people have noticed a big difference using this script on Cyanogenmod.

but since the Glacier has 768MB of ram, you won't notice much change.

saranhai said:
but since the Glacier has 768MB of ram, you won't notice much change.
Click to expand...
Click to collapse
I have found it useful on ports and ROMs that aren't tweaked specifically for this phone. For instance, if TDJ made the ROM, V6 is useless. In fact, it will only hurt.
Sent from my HTC Glacier using XDA App

I use this script on my evo and its great so I just rooted this phone and flashed the mik runny ROM, I was using it for a day and only stayed at about 100mb of RAM so I decided to use v6 with option 8 and now it stays around 200mb and is running super smooth.
IDK if that helps any but I always loved v6 and know a few people that use it on a few different phones and it always works for the better.
Sent from my HTC Glacier using XDA App

Why do people that know nothing or close to nothing about OS internals, decide that they have better knowledge of memory management should be, then OS and phone designers? The same people who don't know the difference between cached and active apps, and the only number they understand is the (useless) amount of free memory? I see it all over the forums, and it amazes me each time. How do people actually try to judge if something works well or not, without getting at least some basic understanding of how the things work?
Oh well, here it comes again:
http://forum.xda-developers.com/showthread.php?t=678205
Read this. Maybe you will understand something.
Few, if any, 512MB phones and no 768MB phones need this script, or any kind of tweaking for lowmemkiller values, especially not since Gingerbread and when not running Sense (which retains the ability to cache apps, removed in Gingerbread mostly to ease running the OS on older devices). The only thing it does, is to make garbage collector work harder and kick in earlier. It doesn't make your phone "smoother", and whoever think it does - should check the meaning of the word "placebo" in the nearest dictionary. The number that stands for "free memory" means something between "close to nothing" and "absolutely nothing".
I know I shouldn't be surprised, people always tend to have strong opinions on everything, even things they sometimes don't know a thing about. But still, it's XDA-Developers, not XDA-Phone-users, so at least something should be done about it. Even if the education attempts will fail, like they mostly do.

Jack_R1 said:
Why do people that know nothing or close to nothing about OS internals, decide that they have better knowledge of memory management should be, then OS and phone designers? The same people who don't know the difference between cached and active apps, and the only number they understand is the (useless) amount of free memory? I see it all over the forums, and it amazes me each time. How do people actually try to judge if something works well or not, without getting at least some basic understanding of how the things work?
Oh well, here it comes again:
http://forum.xda-developers.com/showthread.php?t=678205
Read this. Maybe you will understand something.
Few, if any, 512MB phones and no 768MB phones need this script, or any kind of tweaking for lowmemkiller values, especially not since Gingerbread and when not running Sense (which retains the ability to cache apps, removed in Gingerbread mostly to ease running the OS on older devices). The only thing it does, is to make garbage collector work harder and kick in earlier. It doesn't make your phone "smoother", and whoever think it does - should check the meaning of the word "placebo" in the nearest dictionary. The number that stands for "free memory" means something between "close to nothing" and "absolutely nothing".
I know I shouldn't be surprised, people always tend to have strong opinions on everything, even things they sometimes don't know a thing about. But still, it's XDA-Developers, not XDA-Phone-users, so at least something should be done about it. Even if the education attempts will fail, like they mostly do.
Click to expand...
Click to collapse
I do understand that in some cases you don't need a memory manager like if your running a stock ROM or an aosp ROM that doesn't take up as much memory.
Now I haven't had this phone long enough to say if this script is all that good for this phone but I know on the evo running a sense 3.0-3.5 ROM that wasn't meant for the phone and hugs up every little bit of memory that the phone has to offer, this scrip makes those ROMs usable.
Without it or something like it the phone can't handle doing simple tasks like using an app without fc something else like the launcher.
So you could say what you want and yes maybe this phone doesn't need it since it has more RAM and ROM but I'll still try things like this to try and see if it will better the phones performance.
Sorry if that doesn't make sense I'm still half asleep.
Sent from my HTC Glacier using XDA App

The instances where i have noticed that this works is while doing benchmarking with quadrant. It has shown increased framerates for me after running the script and I also get higher scores on quadrant, about 500-1k more than without. I dont know if its usefull for much other than benchmarking though. I think the phone runs fine without it though.

What you have to understand is performance is not measured via syntactic benchmarks (ex: Quadrant). The biggest issue with people is that they don't know enough to know that they don't know, so they compare it with silly numbers (ex: score) they can't comprehend what they see, much less put numbers behind real life activities that's not applicable in controlled environment.
Now far as V6-SC script goes its almost obsolete now due to few things. 1) Hardware advancement where now minimum spec requirements for "SmartPhone" are 1ghz single core proc with 512mb ram. But so called "SuperPhone" now has dual core 1ghz-1.5ghz with 768mb-1gb ram. So it make no sense as we don't use 256-566mhz proc with 64-256mb ram because we are more then enough hardware adequate for heavy daily usage. 2) OS development which elements most of it as hardware is more and more powerful. But on software level mostly all custom base rom (ex: CyanogenMod) is highly optimized and tweaked to run on optimal performance.
Now is it all placebo effect? Mostly, but not all. But does it mean it can't be tweaked any further? (Rhetorical) No. How do I know? We (scope outside of XDA) tweaked it to the next level. How you ask?
1) Optimized ext4fs: reduced r/w rate (healthy NAND lifespan), improved journaling (corrupted data writeback integrity) = Which improves the IOPs and performance access rate.
2) HC3.x fugu binaries, patched sqlite libraries, mSD read ahead buffer fix.
3) Modified VM: OOM (Out Of Memory), LMK (Low Memory Killer), VM heap (Virtual Machine), DRA (Dirty Ratio), DBR (Dirty Background Ratio), DWC (Dirty Writeback Centisecs), DEC (Dirty Expired Centisecs), SWP (Swap), VCP (VFS Cache Pressure).
4) Increased minfree value: Background, Foreground, Empty, Hidden, Visible, Secondary, Content.
5) Optimized cache: File and Drop cache, Forced cache (resident loop).
6) Custom kernel: OC/UC, UV/SVS/VDD, BFS/CFS, RSU/VR/SP supported.
7) Custom ROM: Optimized Rom script and props (ex: CyanogenMod).
I bet my superior MT4G can own your inferior MT4G. Cuz you can't touch this as its tweaked to THE next level. I'll stick with AOSP2.3.7GB until ICS4.X is more stable and we understand more as most memory grouping and adjustments might be changed.
Sent from my HTC Glacier

Jack_R1 said:
You're wrong on 2 points (possibly more):
1) This script is just the same as Autokiller app, with a small addition - it can (or can't) keep launcher in memory. Nothing new and revolutionary. This app exists for a couple of years.
2) This phone has 768MB of RAM. It won't benefit from a low memory killer (or actually, different settings for an existing in OS lowmemkiller), because it has TONS of memory. I just took a look at my phone, ~100MB of memory free, and ~300MB of remaining memory is taken by CACHED apps. If you don't know what it means - please read up on Android memory management, and I'll give you the short version - it's the same as free memory, but better.
Click to expand...
Click to collapse
Obviously, you never tried it lol
Here... you may learn something new...
http://www.rt-embedded.com/blog/archives/linux-memory-consumption/
http://forum.xda-developers.com/showpost.php?p=20163493&postcount=6695
Below a certain threshold of free ram (ie. not enough cached), the device WILL gag...
Hundreds if not thousands of users with 1 GB ram devices use it (Atrix, SGSII, etc.) and I know your phone stutters from time to time with a slight delay when pressing buttons from time to time since that's what my friend's Atrix does.
In fact, the biggest difference he notices is in the use of google maps... never a stutter.
So you're missing out.

zeppelinrox said:
[1] Obviously, you never tried it lol
[2] I know your phone stutters from time to time with a slight delay when pressing buttons from time to time since that's what my friend's Atrix does.
[3] So you're missing out.
Click to expand...
Click to collapse
First of all as dev of V6-SC you would be very defensive but at same times your not charging money to normal folks for it is a good thing, so thank you. Which I can say less about other folks editing same value claiming it new. Now I don't know about Jack but let's be clear on few points.
1) I did try your so called script and didn't like the whole script manger + busybox cast AFTER the OS startup. Which normally you can achieve via daemon or init.d script after kernel is initialized by declaring and using native shell. So no need for force apply afterwards as it was utilized before it was initiated via script manager. Also V6-SC couldn't keep the selected category minfree value which changed. But in short I didn't notice anything revolutionary as it was fully optimized long before I randomly landed on Android General section and saw your post claiming it maximize the devices performance. Which I was spectacle about as from your post you did seem to have basic knowledge hopefully not from wiki/google but *nix usr exp before landing on to Android.
2) Like I said I don't know about Jacky Boy but I can GRANTEE you I have NEVER had this so called "button delay" you specified. But I did modify the sampling rate and pressure density accommodated by tweaking transition speed. But now I run min:368mhz/max:1027mhz/gov:SmartAssV2. But even when I was battery conscience before I had MP1650mAh I ran on min:230mhz/max:768mhz/gov:SmartAssV1 with custom -75 to -100 VDD using ~14mA idle and ~60-90mA active per unit scale. I never had lag with 200mb used RAM running at least 18-20pcs and 14-15svc. So what your friend is running (Atrix) is irrelevant also isolated.
3) O-RLY am I really missing out? I think ill stick to my own. But don't take this post personal as it was ment for it to be argumentative. Difference is I actually know what I'm talking about as I have strong backgrounds on...
Sent from my HTC Glacier

zeppelinrox said:
Obviously, you never tried it lol
Here... you may learn something new...
http://www.rt-embedded.com/blog/archives/linux-memory-consumption/
http://forum.xda-developers.com/showpost.php?p=20163493&postcount=6695
Below a certain threshold of free ram (ie. not enough cached), the device WILL gag...
Hundreds if not thousands of users with 1 GB ram devices use it (Atrix, SGSII, etc.) and I know your phone stutters from time to time with a slight delay when pressing buttons from time to time since that's what my friend's Atrix does.
In fact, the biggest difference he notices is in the use of google maps... never a stutter.
So you're missing out.
Click to expand...
Click to collapse
I didn't need to try it to know. I tried Autokiller, I played with lowmemkiller settings and watched the results, and I did it on Nexus One with 512MB of memory. It never needed anything since Gingerbread, and unless I made the settings super-aggressive, Autokiller actually failed to make any difference whatsoever - the apps were killed based on their age and never dropped by replacing apps.
In the current system, I have 100MB free + 250MB cached apps (which is just the same as free - theoretically and practically). The main difference you're not accounting for is - Android isn't a Linux distro, it's a Linux-derived OS, with many changes for mobile activity, especially on the kernel level, especially in the memory management area. "Linux memory consumption" isn't Android memory consumption, since they manage things differently. Linux isn't build to kill running apps, its lowmemkiller can't do it. Linux doesn't have concurrent garbage collector. Many Linux examples are irrelevant. Cached apps in Android aren't cached pages in Linux, freeing cached pages in Linux isn't killing cached apps in Android, and the most important - "performance degradation" doesn't exist in Android, since you ALWAYS have enough memory for any size of task (the largest loading task requires 50MB of memory, and there's 100MB free on my phone), and concurrent garbage collection is ALWAYS present in the system, the only thing you're doing - is calling it earlier, making it actually work more and getting the system more laggy than it could be.
I understand that you want to protect your creation, but in this case, you're wrong, sorry. You won't convince me.
And yes, I don't know what "button lag" are you talking about.

HTC Glacier said:
First of all as dev of V6-SC you would be very defensive but at same times your not charging money to normal folks for it is a good thing, so thank you. Which I can say less about other folks editing same value claiming it new. Now I don't know about Jack but let's be clear on few points.
1) I did try your so called script and didn't like the whole script manger + busybox cast AFTER the OS startup. Which normally you can achieve via daemon or init.d script after kernel is initialized by declaring and using native shell. So no need for force apply afterwards as it was utilized before it was initiated via script manager. Also V6-SC couldn't keep the selected category minfree value which changed. But in short I didn't notice anything revolutionary as it was fully optimized long before I randomly landed on Android General section and saw your post claiming it maximize the devices performance. Which I was spectacle about as from your post you did seem to have basic knowledge hopefully not from wiki/google but *nix usr exp before landing on to Android.
2) Like I said I don't know about Jacky Boy but I can GRANTEE you I have NEVER had this so called "button delay" you specified. But I did modify the sampling rate and pressure density accommodated by tweaking transition speed. But now I run min:368mhz/max:1027mhz/gov:SmartAssV2. But even when I was battery conscience before I had MP1650mAh I ran on min:230mhz/max:768mhz/gov:SmartAssV1 with custom -75 to -100 VDD using ~14mA idle and ~60-90mA active per unit scale. I never had lag with 200mb used RAM running at least 18-20pcs and 14-15svc. So what your friend is running (Atrix) is irrelevant also isolated.
3) O-RLY am I really missing out? I think ill stick to my own. But don't take this post personal as it was ment for it to be argumentative. Difference is I actually know what I'm talking about as I have strong backgrounds on...
Sent from my HTC Glacier
Click to expand...
Click to collapse
Sounds like you never got it working properly.
Also, if you have init.d support no need to run anything on boot with script manager.
Maybe the rom's kernel was applying settings late.
And no my friends atrix is not isolated there is a rather big thread in the atrix forums.
SGSII users see benefits too so seems there is always room for improvement.
Jack_R1 said:
I didn't need to try it to know. I tried Autokiller, I played with lowmemkiller settings and watched the results, and I did it on Nexus One with 512MB of memory. It never needed anything since Gingerbread, and unless I made the settings super-aggressive, Autokiller actually failed to make any difference whatsoever - the apps were killed based on their age and never dropped by replacing apps.
In the current system, I have 100MB free + 250MB cached apps (which is just the same as free - theoretically and practically). The main difference you're not accounting for is - Android isn't a Linux distro, it's a Linux-derived OS, with many changes for mobile activity, especially on the kernel level, especially in the memory management area. "Linux memory consumption" isn't Android memory consumption, since they manage things differently. Linux isn't build to kill running apps, its lowmemkiller can't do it. Linux doesn't have concurrent garbage collector. Many Linux examples are irrelevant. Cached apps in Android aren't cached pages in Linux, freeing cached pages in Linux isn't killing cached apps in Android, and the most important - "performance degradation" doesn't exist in Android, since you ALWAYS have enough memory for any size of task (the largest loading task requires 50MB of memory, and there's 100MB free on my phone), and concurrent garbage collection is ALWAYS present in the system, the only thing you're doing - is calling it earlier, making it actually work more and getting the system more laggy than it could be.
I understand that you want to protect your creation, but in this case, you're wrong, sorry. You won't convince me.
And yes, I don't know what "button lag" are you talking about.
Click to expand...
Click to collapse
I was tempted to stop reading when you admit to not even using it.
If it did the same as AKMO or Auto Memory Manager why on earth would anybody bother.
I sure as hell wouldn't bother writing a 4500+ line script lol.
I totally agree that Android memory is not the same as linux (see my sig) but the similarities are there and the article I posted applies 100%.
Its not about free ram.
Its about the right balance.
In fact, many report LESS free ram, ie. better multitasking, along with better performance and smoother performance.
Because I don't think Android memory should work the same as linux memory either.
Also, you tried AKMO because you felt there could be improvement and it didn't work.
THAT'S why I wrote a 4500+ line script that blows anything else out of the water

zeppelinrox said:
Sounds like you never got it working properly.
Also, if you have init.d support no need to run anything on boot with script manager.
Maybe the rom's kernel was applying settings late.
And no my friends atrix is not isolated there is a rather big thread in the atrix forums.
SGSII users see benefits too so seems there is always room for improvement.
Click to expand...
Click to collapse
Well my highly optimized as is but I am aware of V6 and others using it but personally I would stick to my.
Sent from my HTC Glacier