QUOTE(Baronic @ Sep 10 2013, 02:21 PM)
the bolded part is not quite true. ANd there is more that goes into a good custom rom (keyword good) than just shaving things off. There is actual optimisations being done. the simplest one i can think of is partitioning more ram for the UI usage.
the program again, is not enough ram. Lets take Note 2 for example. 2GB.
Out of 2GBram, how much ram is being used by TW UI? not 2GB. a fraction of that. So how is increasing the pool of available ram to 3GB gonna change anything? Its got to go down to the TW UI framework itself. You dont need the extra 1GB to become 3GB to increase smoothness. WHat you need to do is allocate more of the 2GB pool into the TW UI for example, but even then, by right, u shouldnt need to do that because to do it means that the UI has memory leak in the first place. :/
when your S3 lags, the TW UI, go to your ram, and see where is the pool of ram being assigned to. Then you can get a better picture of why your device is lagging.
so yea. Optimisation is the keyword
the rest of your post is more or less spot on
I use nearly all S III ROM, none is really make the S III run as smooth as Note II as it just can't. Unless you run pure AOSP ROM, but then what the point, you lost all Samsung features and the main reason I buy Samsung phone is I want Samsung features.
If want AOSP ROM only, just get the Nexus is fine.
S III is big nightmare once you open another RAM hunter app - Chrome.
But all this issue not happening under Note II, because simply as Note II had extra enough RAM to handle others app properly.
Off course Touchwiz itself never use up all the RAM, but the left out is not enough to proper handle others heavy task already, just a simple Chrome browser is enough to make the S III badly nightmare phone.
This post has been edited by Andrewtst: Sep 10 2013, 02:26 PM 
Sep 10 2013, 02:19 PM
Quote
0.0275sec
0.35
7 queries
GZIP Disabled