Related
I had my HTC Desire which has 512MB of RAM.
on stock froyo rom i have managed to have around 300MB free while on rom's with sense around 220-250mb free after boot
on galaxy i have around 130-160mb top after boot. WTF?
The desire actually has 576mb of ram, which partially explains the difference. Don't know about the rest, maybe poor optimization of the touchwiz interface.
thats because of poor memory I/O management by Samsung.....
thats why you see lots of lagging complaints by end users....
widjaja74_us said:
thats because of poor memory I/O management by Samsung.....
thats why you see lots of lagging complaints by end users....
Click to expand...
Click to collapse
Is this true?
djglenn1337 said:
Is this true?
Click to expand...
Click to collapse
It's 100% guessing, and my bet is that it's the same amount of bullcrap. The lag is likely caused by many running apps, but for entirely different reasons than poor memory management. Samsung has no reason to fiddle with the memory management implemented in android, so I'm quite confident they didn't because it would be a waste of time.
Sent from my GT-I9000
mickeko said:
It's 100% guessing, and my bet is that it's the same amount of bullcrap. The lag is likely caused by many running apps, but for entirely different reasons than poor memory management. Samsung has no reason to fiddle with the memory management implemented in android, so I'm quite confident they didn't because it would be a waste of time.
Sent from my GT-I9000
Click to expand...
Click to collapse
Then why would it lag like hell fresh from the box without any form of tweaking or installing apps?
kenkiller said:
Then why would it lag like hell fresh from the box without any form of tweaking or installing apps?
Click to expand...
Click to collapse
because the lag is caused by slow internal storage also.
That is why the best fixes for lag involve moving things to external sdcards
kenkiller said:
Then why would it lag like hell fresh from the box without any form of tweaking or installing apps?
Click to expand...
Click to collapse
If I knew I'd tell you.. I'm not going to pretend that I know how the SGS is designed. Could be poor CPU-throttling, power management issue, maybe the sole cause for the lag is a poor gps driver that hogs up too much of a specific system bus... I have no clue, but there are tons of ways to make a phone lag that doesn't have alot to do with memory management.
Sent from my GT-I9000
Have any of you tried to flash to a newer firmware?
With JM2/JP3 you can see 305mb (rahter than the 256 of stock JF3), and the free memory is usually between 200-230mb.
We're supposed to see beter Himem memory in the final builds of froyo, resulting in more available memory, though endeed a large part of the 512mb is reserved for radio/gps/wifi/bt and other system uses.
I put on the new Voodoo Lag fix and have had no problems. My phone is as fast its ever been. Because before that I was using ryanzas lagfix on the market and kind of made my phone faster. So I removed ryanzas and put on the voodoo, and found I could still apply ryanzas, so I did and my phone is super fast. At least I feel like its faster. So for the devs I know this isnt a q&a but is this actually working, and can u guys apply this into ur future work?
lilsav55 said:
I put on the new Voodoo Lag fix and have had no problems. My phone is as fast its ever been. Because before that I was using ryanzas lagfix on the market and kind of made my phone faster. So I removed ryanzas and put on the voodoo, and found I could still apply ryanzas, so I did and my phone is super fast. At least I feel like its faster. So for the devs I know this isnt a q&a but is this actually working, and can u guys apply this into ur future work?
Click to expand...
Click to collapse
curious what tests have you run to determine it is indeed faster? I need to go back and read through Ryanzas lagfix but from memory I thought it created an EXT partition just as the Voodoo lag fix does.
If this is the case there would be no speed improvement as your system is only using one EXT partition so running the 2nd lagfix does nothing or changes the size of the EXT partition created by Voodoo.
rsfaze said:
curious what tests have you run to determine it is indeed faster? I need to go back and read through Ryanzas lagfix but from memory I thought it created an EXT partition just as the Voodoo lag fix does.
If this is the case there would be no speed improvement as your system is only using one EXT partition so running the 2nd lagfix does nothing or changes the size of the EXT partition created by Voodoo.
Click to expand...
Click to collapse
Ok so all I do is try to make my phone faster when I have time. But I partioned my sd on my mytouch with amon ra then I put my sd on ext 4. Than I ran the voodoo lag fix using the the deodex rom. Voodoo lag fix put my quadrant scores at 1700 about which seems realistic. Because with ryanzas I was getting 2400-2500. But I only had 500mb of app space left bcuz of the partition. But after voodoo I have 1.4mb and I ran ryan zas on top of that and I have the same 1.4mb left. I think I can run both because the voodoo lag fix is a system partition and ryanzas is only virtual. At least thats what I think thats why im asking for help. But I run about about 2000 to 2100 on my quandrant scores and my phone has no lag at all.
I say try it if u can because my phone has never been faster. I dont know why it works but I believe it does because I can see and feel a difference in the phone. Everything runs so smooth. Its fantastic!!!!
Why stop there? Install another lagfix and I'm sure your phone will be 3X as fast!!!
grennis said:
Why stop there? Install another lagfix and I'm sure your phone will be 3X as fast!!!
Click to expand...
Click to collapse
lmao!
my sides hurt.
grennis said:
Why stop there? Install another lagfix and I'm sure your phone will be 3X as fast!!!
Click to expand...
Click to collapse
Haha smart a** I just need someone else to try it it and tell if it works? Or explain to me why it wouldnt or doesnt?
lilsav55 said:
Haha smart a** I just need someone else to try it it and tell if it works? Or explain to me why it wouldnt or doesnt?
Click to expand...
Click to collapse
Rsfaze already explained to you why it wouldn't, both of the fixes do the same thing and by doing the same fix twice they do not combine to give you double the benefit.
Imagine your hard drive is fragmented and your PC is slow, well you defragment it and it becomes faster. What you are essentially saying is that if you keep on defragmenting it it will continue to become faster which is ludicrous, unless you can post a quadrant score of 3000
Iirc the virtual ext lag fix simply cached some of the data for quicker access, and that's the increase you're seeing.
Sent from my SGS Vibrant
Calcvictim said:
Rsfaze already explained to you why it wouldn't, both of the fixes do the same thing and by doing the same fix twice they do not combine to give you double the benefit.
Imagine your hard drive is fragmented and your PC is slow, well you defragment it and it becomes faster. What you are essentially saying is that if you keep on defragmenting it it will continue to become faster which is ludicrous, unless you can post a quadrant score of 3000
Click to expand...
Click to collapse
Ok true, but arent the lag fixes different? They arent set up the same and put on different ext's
And why did it improve my quadrant scores? and usually the phone wont allow u to apply two
Lag fixes at once when they are the same thing. Because I am using the lag fix apk and the voodoo lag fix through rom manager. Try it and tell me what u think?
tissimo said:
Iirc the virtual ext lag fix simply cached some of the data for quicker access, and that's the increase you're seeing.
Sent from my SGS Vibrant
Click to expand...
Click to collapse
Thx that makes sense. So do u think that is make making my phone faster?
Calcvictim said:
Rsfaze already explained to you why it wouldn't, both of the fixes do the same thing and by doing the same fix twice they do not combine to give you double the benefit.
Imagine your hard drive is fragmented and your PC is slow, well you defragment it and it becomes faster. What you are essentially saying is that if you keep on defragmenting it it will continue to become faster which is ludicrous, unless you can post a quadrant score of 3000
Click to expand...
Click to collapse
Hey man, if those placebo pills work so well for him, don't stop filling his prescription.
Well i honestly dont know the details behind it but I can say that my phone does feel faster. So try it for yourself and tell me what you think. It is perfectly safe and you can always remove it. But just apply the voodoo and then go on market, and get ryanzas lag fix and apply that too. I am using the deodex rom so I dont knkw if that makes a difference. But thx for explainations. Later
grennis said:
Why stop there? Install another lagfix and I'm sure your phone will be 3X as fast!!!
Click to expand...
Click to collapse
Haha, I seriously doubt this works, run 4 quadrant tests, the first being stock with no lag fix, second with one of the lag fixes, third with only the other lag fix that you did not use before, and lastly run a forth test with all of the lag fixes and post all the scores generated by quadrant.
Sent from my vibrant using XDA App
almyz125 said:
Haha, I seriously doubt this works, run 4 quadrant tests, the first being stock with no lag fix, second with one of the lag fixes, third with only the other lag fix that you did not use before, and lastly run a forth test with all of the lag fixes and post all the scores generated by quadrant.
Sent from my vibrant using XDA App
Click to expand...
Click to collapse
Stock odin 900
Ryanzas one click 2400 not believable but thats what quadrant says
Voodoo 1700 can see a real difference
Jacs kernal and no wake 1400 can feel diffrence mainly bcuz of overclock
Voodoo + ryanzas 2100 feels smoother and faster than just voodoo
Dont believe me than try for yourself.
If quadrant says so I believe it, though I am not able to try it I'm running the new leaked rom, I don't believe that is compatable with the voodoo lag fix.
Sent from my vibrant using XDA App
almyz125 said:
If quadrant says so I believe it, though I am not able to try it I'm running the new leaked rom, I don't believe that is compatable with the voodoo lag fix.
Sent from my vibrant using XDA App
Click to expand...
Click to collapse
Well the quadrant scores are just quadrant scores to me. I just go off of how many phone feels and what it does and it has never been snappier, my bro has same phone and he has the vodoo lag fix and we did a side by side comparison and mine was faster so I will let the people be the judge and let them try for them selves.
lilsav55 said:
I put on the new Voodoo Lag fix and have had no problems. My phone is as fast its ever been. Because before that I was using ryanzas lagfix on the market and kind of made my phone faster. So I removed ryanzas and put on the voodoo, and found I could still apply ryanzas, so I did and my phone is super fast. At least I feel like its faster. So for the devs I know this isnt a q&a but is this actually working, and can u guys apply this into ur future work?
Click to expand...
Click to collapse
The voodoo lagfix uses ext4, which is a little slower but far safer. By installing ryan's virtual ext2, youve merely regained ext2's speed at the expense of ext4' safety along with the improvements gained from an optimized kernel.
Sent from my SGH-T959 using XDA App
masterotaku said:
The voodoo lagfix uses ext4, which is a little slower but far safer. By installing ryan's virtual ext2, youve merely regained ext2's speed at the expense of ext4' safety along with the improvements gained from an optimized kernel.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Ext2 has a faster write but Ext4 has a faster read when tests where done on the two. You already mentioned the safety of ext4 which would be the journaling that Ext2 does not do.
I still don't think ext2 would be faster than ext4 but I could be wrong.
lilsav55 said:
Ok so all I do is try to make my phone faster when I have time. But I partioned my sd on my mytouch with amon ra then I put my sd on ext 4....
Click to expand...
Click to collapse
I don't get it. Why is this in the Vibrant forum at all?!!
now my SGS is lightning fast, just incredible!
Before the LagFix my device was just a lame duck
Does Samsung know what potential would be built in in this device?
hanzi54 said:
now my SGS is lightning fast, just incredible!
Before the LagFix my device was just a lame duck
Does Samsung know what potential would be built in in this device?
Click to expand...
Click to collapse
Hm, not really. Have you tried the browser?
huxflux2003 said:
Hm, not really. Have you tried the browser?
Click to expand...
Click to collapse
Browser, what browser?
the internet browser...
All of "lag fix patch" are crappy, just they are just temp solution. 1-2 wks and u will experience really strange behaviors. These "lag fix guys" are were smart and nice, but they make more problem. Don't install lag fix.
almaalma74 said:
All of "lag fix patch" are crappy, just they are just temp solution. 1-2 wks and u will experience really strange behaviors. These "lag fix guys" are were smart and nice, but they make more problem. Don't install lag fix.
Click to expand...
Click to collapse
How do they make things worse? You can't be serious? I mean, some of them may not cure it completely (though I reckon the voodoo one seems so far to get pretty close at least), but they definitely don't make things any worse than before the lag fix.
I have to say that i have OCLF that turns your file system into a ex2 instead of the stupid proprietary file system that samsung used and it's faster than a lightning right now.
Have it for a week now and it's running smooth so far.
I wonder if there is any logic explanation for Samsung to use the proprietary RFS filesystem instead of the regular ex2 or ex4? It's reallyyyyyyyy a bigggggggggggg difference on performance.
hanzi54 said:
now my SGS is lightning fast, just incredible!
Before the LagFix my device was just a lame duck
Does Samsung know what potential would be built in in this device?
Click to expand...
Click to collapse
Agreed, JPK+lagfix is awesome!
almaalma74 said:
All of "lag fix patch" are crappy, just they are just temp solution. 1-2 wks and u will experience really strange behaviors. These "lag fix guys" are were smart and nice, but they make more problem. Don't install lag fix.
Click to expand...
Click to collapse
I haven't had this problem, but... couldn't you just undo and then redo the lagfix after 2 weeks if it's slowed down for you? Then it would be fast again, right?
JPK was still just a little too buggy for me, nothing has come close to JM8+Voodoo in my experience. Also to the guy saying that the lag fixes make it worse, you obviously haven't tried voodoo, it perfects the SGS by converting to the file system the phone should have had in the first place.
almaalma74 said:
All of "lag fix patch" are crappy, just they are just temp solution. 1-2 wks and u will experience really strange behaviors. These "lag fix guys" are were smart and nice, but they make more problem. Don't install lag fix.
Click to expand...
Click to collapse
Many you should sell the phone and buy a iphone.
Lagfix do work. If they don't work then its because you have done something wrong with you phone.
A had lagfix on it with 2.1 and i did it when i upgrade to 2.2. It was the first thing i did so i knew that i did NOT had anything that would interfere with it.
All working super. No lag.
Sent from my GT-I9000 using XDA App
Daley87 said:
JPK was still just a little too buggy for me, nothing has come close to JM8+Voodoo in my experience. Also to the guy saying that the lag fixes make it worse, you obviously have. Haven't tried voodoo, it perfects the SGS by converting to the file system the phone should have had in the first place.
Click to expand...
Click to collapse
+1 lagfix is overrated. My wife's sgs is running on voodoo, and she complains of lag after about a week. Ran quadrant and score is only 1200+. Reboot her phone and it's snappy again. Quadrant score shot up to 1708. I reboot mine everyday and never have any issues with lags. So regardless of what lagfix you applied, nothing beats a regular reboot.
When I had just over 50 apps installed, I noticed a real lag issue, especially when trying to access any of the conventional phone utilities, like phone, contacts or messaging. Quadrant was returning a score of 851. Installed RyanZA OCLF after reading about it on here and I can confirm that there were no issues, worked like a charm. Quadrant score was now 2265 and the phone was noticably zippy. I dont tend to switch the phone off and have noticed the phone starting to lag a bit (after about a weeks use) however, a quick reboot and its just like when I first installed the lag fix.
Appart from the lag fix and of course root access, the phone is still standard with Eclair XXJM1.
LAg fix works man . . . i am on JPK with lag fix its works
Seifer1975 said:
+1 lagfix is overrated. My wife's sgs is running on voodoo, and she complains of lag after about a week. Ran quadrant and score is only 1200+. Reboot her phone and it's snappy again. Quadrant score shot up to 1708. I reboot mine everyday and never have any issues with lags. So regardless of what lagfix you applied, nothing beats a regular reboot.
Click to expand...
Click to collapse
Try using autokiller.. you dont need to reboot..
messatu said:
Try using autokiller.. you dont need to reboot..
Click to expand...
Click to collapse
She was already on autokiller on strict setting. I am beginning to suspect this is an android problem. All my friends on android phones experience lag after some time of usage, including desire
do you guys think we will still have to use a lag fix on a 2.2 rom that has the JIT compiler enabled?
The lag is mostly due to Samsung's poor file system. Unless they fixed it or abandoned it I'm guessing we will still have lag.
Sent from my SGH-T959 using XDA App
Tpavey said:
The lag is mostly due to Samsung's poor file system. Unless they fixed it or abandoned it I'm guessing we will still have lag.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Wow. You gotta be ****ting me!
the leaked 2.1 build fixed the lag for me so im guessing yes (if and when 2.2 comes out that is)
No lag i JI6 2.1
Tpavey said:
The lag is mostly due to Samsung's poor file system. Unless they fixed it or abandoned it I'm guessing we will still have lag.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Wouldn't the JIT fix the lag though? Or would samsung use their own even in 2.2? (just speculating)
presence06 said:
Wouldn't the JIT fix the lag though? Or would samsung use their own even in 2.2? (just speculating)
Click to expand...
Click to collapse
Their FileSystem still sucks. 2.2 with JIT might significantly speed up the phone and take away the noticeable lag, but it will still be crippled in terms of its true functionality.
sheek360 said:
do you guys think we will still have to use a lag fix on a 2.2 rom that has the JIT compiler enabled?
Click to expand...
Click to collapse
presence06 said:
Wouldn't the JIT fix the lag though? Or would samsung use their own even in 2.2? (just speculating)
Click to expand...
Click to collapse
tjhart85 said:
Their FileSystem still sucks. 2.2 with JIT might significantly speed up the phone and take away the noticeable lag, but it will still be crippled in terms of its true functionality.
Click to expand...
Click to collapse
JIT is CPU based execution while the lag is because of file system writes. they are 2 different things and not connected. If what i heard is correct (and if i'm remembering it correctly), RFS has issues with queuing write commands unlike ext2/3/4.
Tpavey said:
The lag is mostly due to Samsung's poor file system. Unless they fixed it or abandoned it I'm guessing we will still have lag.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
correct, it's file system related, not cpu related.
There are numerous issues with RFS.
See the following I9000 threads for more information:
lagfix pros and cons - http://forum.xda-developers.com/showthread.php?t=777610
discovery of filesystem errors on RFS - http://forum.xda-developers.com/showthread.php?t=797650
sync issues with RFS - http://forum.xda-developers.com/showpost.php?p=8445244&postcount=143
In my honest opinion, when does Samsung consider the cost benefit of maintaining this proprietary filesystem versus using "stock" ext*fs? At what point do they swallow their pride and realize their filesystem isn't ready for production?
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