Database Users

[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

Gaming on stock kernel

GAMING (This post).
Added: THE RETURN OF ATIFROYO (http://forum.xda-developers.com/showpost.php?p=29546400&postcount=14).
Added: TWEAKAGE (http://forum.xda-developers.com/showpost.php?p=30130560&postcount=23).
Gaming.
Let's face it. For some their phones are just a gaming console... that can also happen to make phone calls! For whatever reason you ended up with a Xperia X8, case in point: my younger brother.
I happen to have a knack for computers, he just cares about what they would do. So, this is my small journey trying to help him. Probably someone can benefit from it.
So, here's my experience with ROMs running on stock kernel without overclocking. Why no overclocking? For the life of me, I couldn't tell the difference, even tho I really wanted it to work.
I judged the performance on gaming running Fruit Ninja: Puss in Boots and Dead Space. Arbitrary, I know; but it has worked in determining how stable and fast a ROM would be. Dead Space was specially helpful in determining stability since some ROMs would reboot or would close Dead Space after trying to open a saved state. What's more, I would have a frame of reference to test the ROMs with what would prove to be two demanding games for the X8.
· Stock 2.1.1 doesn't run PiB. I don't know about Dead Space because at the moment I didn't even know about that game.
· FroyoPro 2.5 would occasionally run PiB, when it would open it would be lag free. Dead Space wasn't tested on this ROM either.
· GingerDX from v26 onwards runs both. PiB runs with a little bit of lag. Dead Space would become laggy at parts, tho it is quite stable.
After those three ROMs, I tried a few more, mainly Gingerbread ROMs. Most of them were quickly changed. The next are the few who lasted more than half an hour to an hour, also a few of the most popular oner, which are bound to bring up questions.
· FroyoBread v23b. PiB would seldomly open and it would be laggy. Dead Space wouldn't open saved states.
· KuyaDroid 4.5.4. Fast first boot... that caught my eye, plus the cool bootanimation. Dead Space was slow and wouldn't open saved states. PiB had some lags, but it was playable.
· XG!N V8 (LinuXperia Xgin v.0.10). This one caught me by surprise, my first thought was: "This is one ugly ROM"; however both Dead Space and PiB were for the first time fast. Too bad Dead Space wouldn't open saved states. On a second run of this ROM, I might have made a mistake. The ROM originally tested couldn't possibly be XG!N V8 (not the same looks), it probably is LinuXperia Xgin v.0.10.
Tests up to this point seem to leave no clear winner... until:
· AtiFroyo 5.2. Both PiB and Dead Space run smooth. Dead Space opens saved states. First boot is fast... That fast that it deserves mentioning. The only drawback is auto brightness. I like installing Lux Auto Brightness so my brother doesn't burn his eyeballs at night but it's rendered useless since autobrightness is always ON. I tried changing hw_config.sh values, but nothing. I even tried deleting the whole settings that are supposed to manage auto brightness and it would still be active.
My advice: if you can live with the autobrightness bug, use AtiFroyo. Hands down. Use x8toolbox to install the DualTouch modules without hussle.
So, what's my brother's phone running now?
He needs Lux Auto Brightness. So AtiFroyo is ruled out. A shame, really.
Here's the set-up, keep in mind that I want my brother to mess with the settings as little as possible:
· GingerDX v28b. Minus lots of apps (see: http://forum.xda-developers.com/showthread.php?p=26683929).
· RAM Manager Pro. Balance is checked at all times. Couldn't tell the difference with the other settings. In fact the only difference I could tell while using RAM Manager Pro, is that when an app starts acting funny, it gets killed faster.
· Chainfire3d. With Reduce Texture Quality always ON. It makes even the games that don't need it run a little bit faster, or at least start faster. The only time you'll notice the difference is when there are gradients present.
· Zeam Launcher. It's a launcher. Seriously, if you only care for getting to your apps/games, this is the answer. For an ICS look go: http://forum.xda-developers.com/showthread.php?t=1558419. Word of caution: apparently what this modded version does, is pull the icons from the theme; so, if you're using, for example, the system theme the icons won't be the ICS icons.
The results of this set-up: PiB is not as fast, but playable. Dead Space is stable, some lags are still noticeable, but overall is playable.
A final note:
Thanks to all the developers here. You all pushed/discovered, and continue to push, the limits of what the X8 can do.
Who would have thought that some of the X8 phones had real dual touch capabilities?
This list/post is not, by any means, a final judgement/call on the ROMs on the forums. My brother has a very narrow specific use for his phone and this has been my experience trying to fill what he wanted.

You know that there are benchmarks
Yea ati froyo and froyopro are good but 2,2 android.
Sent from my E15i using xda app-developers app

Lukenda said:
You know that there are benchmarks
Click to expand...
Click to collapse
Benchmarks only tell part of the story.
Which is why, for example, I should expect a considerable boost in performance from overclocking; but no noticeable difference.
Lukenda said:
Yea ati froyo and froyopro are good but 2,2 android.
Click to expand...
Click to collapse
You mean old, right? Then, the question would be old for what?
And if you paid atenttion, with the tests GingerDX came on top: it would open PiB every single time.

2.2 cant play some new games...i love sas3.
Cyagenmod rc1 v4 seems to be perfect rom by xperiafan.
Based on minicm7 and stock kernel
Sent from my E15i using xda app-developers app

Hey Fortun, I really like your post and how you wrote it. Hope to see more of you,
Cheers,

elderduke said:
Hey Fortun, I really like your post and how you wrote it. Hope to see more of you,
Cheers,
Click to expand...
Click to collapse
Glad you enjoyed it.
I really can't think of any other threads to start... Will see how it goes.

I'm sure u spent some time to test them & write here.
Tnx & waiting for more.
Is it important how did i send this?

floyo by racht (latest)
Sent from my X8 using xda app-developers app

Fortun, continuing the quest for the perfect stock kernel rom , have a look on this:
http://forum.xda-developers.com/showthread.php?t=1776643
Cheers,

elderduke said:
Fortun, continuing the quest for the perfect stock kernel rom , have a look on this:
http://forum.xda-developers.com/showthread.php?t=1776643
Cheers,
Click to expand...
Click to collapse
sorry but I think the UI is [email protected] lol. nvm we need good performance tho. I'll try it later. thanks for the info mate ! :good:

that OP is a girl...so what did u expect.... LOL

elderduke said:
Fortun, continuing the quest for the perfect stock kernel rom , have a look on this:
http://forum.xda-developers.com/showthread.php?t=1776643
Cheers,
Click to expand...
Click to collapse
Saw that ROM but wasn't actually going to try it since the latest LinuXperia, the base of this new ROM, didn't passed the tests. Plus: http://forum.xda-developers.com/showpost.php?p=27499552&postcount=241.
But I might give it a go this weekend along a few things.
There's this one ROM I would really want to try: LinuXperia Mika v9b. If anyone of you could hook me up with a working download link, it would be great.

PM'ed.
Since Alessio was disabled due to problems in paradise, I will send you the link by PM.
But as far as I remember, it was not so great in terms of batery or 2d/3d.
Also, he developped starting from XGin + Xperiafan, but lately he started to OC @691 and appeared is faster, but once you revert to 600 then is quite normal.
Also quite heavy on theme and colors.
Cheers,

The Return of AtiFroyo.
There. You already know how this post is going to end. However you may want to ditch RAM Manager if you're in it to play games. Wait. What?
In this second batch of testing, a few games come into play: Aby Escape, Ninja Fishing and the ARMv6 ported version of Sushi Chop. Fruit Ninja: Puss in Boots was also tested and runs more or less the same on all ROMs with the underdog being GingerDX.
The candidates? GingerDX v28b, LinuXperia Mika v9b (the one with amazing AnTuTu score), GingerCruzt Revision 8.4, LinuXperia FreeDom S1, VivoPrime V01 and AtiFroyo 5.2.
Let's start:
· LinuXperia Mika v9b. One more reason you shouldn't put too much weight on benchmark scores. Aby Escape and Sushi Chop are laggy to the point of making them unplayable. Aby Escape would just close when starting the actual gaming; had to reopen it to make it work. For Sushi Chop, phone just froze when trying to exit the game; had to reboot the phone.
· GingerDX v28b. Aby Escape would close when starting the actual gaming. No apparent solution. Sushi Chop, unplayable.
· GingerCruzt Revision 8.4, LinuXperia FreeDom S1 and VivoPrime V01. Why put the three together? Because they would perform on par with each other. Both Aby Escape and Sushi Chop would be playable. The edge on performance goes to GingerCruzt, which would be a little bit more responsive in Aby Escape. Now LinuXperia FreeDom makes my eyes bleed. So, in looks, the edge goes to VivoPrime. Also GingerCruzt is bloated with a lot of widgets, a few apps, and some manga and anime wallpapers I have no use for.
· AtiFroyo 5.2. Both Aby Escape and Sushi Chop are playable. The difference with the last three ROMs? Responsiveness. Aby Escape would get a little bit laggy in some parts just before a jump, costing you the game. In AtiFroyo, the lags are less frequent and briefer. Sushi Chop is also more responsive, resulting in cutting more sushi. Also, in the last three ROMs, Aby Escape would close if I played for a few minutes and then try to enter the in-game shop. Guess what. In AtiFroyo, it doesn't happen.
So, AtiFroyo is winning... and not in a Charlie Sheen kinda way. If it only weren't for the auto brightness bug, right? Well, now it's solved. Modify the hw_config.sh values in the ROM zip before flashing it. Done.
But if you just have to have a Gingerbread ROM for playing, I'd probably go with VivoPrime V01.
Where does Ninja Fishing enter into all of this? You won't play it. Here's the thing in all the ROMs, it would enter the game, but when you tried to actually start gaming by entering a level it would close. Enter Chainfire3d. In all ROMs but GingerDx, with reduced texture quality and size, you would be able to actually play the game until the end of the level. Then it would close. Winse and repead. The end.
Obvious question now is: can't I just change the looks of the ugly ROMs? Of course. The easy way is with themes. However most themes don't go that deep into the framework to change everything you might not like... especially some colors. Then, a stock look is preferable because its colors won't clash with most themes. Now, if you want you can go the hard way and modify the framework... Too much work.
That's all. Wait. RAM Manager, right? Don't get mad. Here we go.
Here's the thing. If you are with a Gingerbread based ROM, you might want to disable/uninstall it. How come? Remember when I said there was no apparent solution for playing Aby Escape? Well, the "apparent" part was intentional.
After testing GingerDX, I went ahead and installed GingerCruzt. After playing the games, I wanted to see performance with RAM Manager. Aby Escape would close when attempting to start the actual gaming with Balance enabled. Hard Gaming? Same experience. Hard Gaming (Less aggressive)? No luck. Déjà vu. Didn't this happened before with GingerDX? Which, by the way, had RAM Manager enabled? Let's first disable it, the game starts. Time to go back to GingerDX without RAM Manager. Confirmed. The culprit is RAM Manager. Aby Escape starts. Laggy to the point of making it unplayable, but it starts. Sushi Chop would cause less problems, but playing it would make you very angry.
Back to AtiFroyo. The games would behave the same with or without RAM Manager enabled. So, for now, no RAM Manager in the phone.
One last thing. What does AtiFroyo look like? Well, for sure it doesn't look like Froyo, it's modified to look like ICS. It even has a Sensified option... which I haven't tried. The font may upset some people, my brother likes it and I think it's got some flair. This is easily changeable, tho.
I might put some screenshots later to finish up this paid advertising for AtiFroyo...
... At least, I'm hoping Attis112 will give me something.

Well, as you stated, benchmark is not everything. But also playing games is not everything.
For some reason, on my device the one Rom with the best quality of sound into calling is FroyoPro 2.5. Also is the only rom who can score higher than stock in AnTuTu. that's why I allways go back to it when I'm tired of "trying out".
On the other hand , I tried the HoneycombFroyo also by Attis and it looks really nice but it has 2 problems: the backlight and the floating point which scores 17 ???? Please test AnTuTu on AtiFroyo and see if there is the same issue on variant 5.2. - maybe that is one cause also for lags....Anyways maybe I did something wrong when installed. I downloaded it from this thread: http://forum.xda-developers.com/showthread.php?t=1763389
Please let us know if is any way to improve it.
Cheers,

elderduke said:
Well, as you stated, benchmark is not everything. But also playing games is not everything.
Click to expand...
Click to collapse
Of course. Unless we're talking about a person whose phone is just a gaming console... that can also happen to make phone calls!
elderduke said:
On the other hand , I tried the HoneycombFroyo also by Attis and it looks really nice but it has 2 problems: the backlight and the floating point which scores 17 ???? Please test AnTuTu on AtiFroyo and see if there is the same issue on variant 5.2.
Click to expand...
Click to collapse
Sure: 146.
HoneycombFroyo is build based around MiniCM6 as AtiFroyo. There shouldn't be such a big difference. Tho, the file sizes certainly differ: 106 MB against 80.6 MB (including fixes).
If you have the time, you could try formatting cache, data and system. Then doing a full wipe and wiping the dalvik cache. Install the ROM and see if that does something. I had a nasty GingerCruzt problem that I could only fix by doing that.
As for the backlight, if you mean it's always ON, I can give you the propper values for hw_config.sh.

My nasty experience with the backlight was that it was allways OFF. I had black screen and no chance to see what's going on for seconds, and after several pressing of menu button finally backlight would be revived....But also, I downloaded a variant of AtiFroyo 5.2 of 100.9 Mb from a polish site linking to a hotfile link....since I did not find it in xda.
As opposed to this HoneyFroyo - also by attis - here:http://forum.xda-developers.com/showthread.php?t=1449144&highlight=froyo
So I would appreciate if you could send me both: the link to your AtiFroyo 5.2 and the hw_config.sh (values of the file itself) - but I guess by PM because there must be a reason it was removed from XDA...
Thanks a lot,
Cheers

elderduke said:
My nasty experience with the backlight was that it was allways OFF. I had black screen and no chance to see what's going on for seconds, and after several pressing of menu button finally backlight would be revived....But also, I downloaded a variant of AtiFroyo 5.2 of 100.9 Mb from a polish site linking to a hotfile link....since I did not find it in xda.
As opposed to this HoneyFroyo - also by attis - here:http://forum.xda-developers.com/showthread.php?t=1449144&highlight=froyo
Click to expand...
Click to collapse
Interesting since both have the same hw_config.sh values. And, yes, I have HoneyFroyo downloaded but I haven't tested it yet.
Here go the proper values:
# lm3530 LMU configuration
dev=/sys/devices/platform/i2c-adapter/i2c-0/0-0036
echo linear > $dev/br::mapping # linear exp
echo 32768 > $dev/br::rate::up # 8, 1024, 2048, 4096, 8192, 16384, 32768, 65538
echo 32768 > $dev/br::rate::down # 8, 1024, 2048, 4096, 8192, 16384, 32768, 65538
echo 255 > $dev/br::limit # 0 - 255
echo 19.0 > $dev/br::fsc # 5.0, 8.5, 12.0, 15.5, 19.0, 22.5, 26.0, 29.5
echo 30,70,110,150 > $dev/curve::borders
echo 100,115,130,175,254 > $dev/curve::targets
echo high-z > $dev/als::r1 # high-z, 9360, 5560 .. 677.6 (see chip mnual)
echo high-z > $dev/als::r2 # high-z, 9360, 5560 .. 677.6 (see chip mnual)
echo 512 > $dev/als::avg-t # 32, 63, 128, 256, 512, 1024, 2048, 4096
echo i2c > $dev/mode # i2c, pwm, i2c_pwm, als, pwm_als, i2c_pwm_als, i2_als
Don't forget to change the values directly in the zip ROM before flashing it. And just to be sure that you won't get an episode similar to what you experienced with Honey Froyo, find the next value in build.prop:
settings.display.autobacklight=1
Change it to:
settings.display.autobacklight=0

Could you pm me a link to atifroyo? Just wanna test it out. Just curious. Thanks!
Sent from my rooted tomato using xda app

Screenshots for both the normal look of the ROM:
And the one you obtain with the Xperia theme:
For anyone wondering, the first picture showcases the Holo Launcher, changed from Launcher Pro which comes in the original zip.

Reviving your slow SGS.

So I recently changed over to the nexus 4, and I say, it is AMAZING. I just got to the point where the SGS just didnt cut it anymore. It has hung in there for a long time, but its starting to become under-powered for new versions of Android.
So in this guide, I am going to show you how to speed up your Galaxy S, and push it to its max performance.
You will need a custom kernel like Semaphore. I made this guide with no regard to battery life, but i did avoid using un-necessary power.
1. Live OC
- This increases the Bus, Ram and GPU speeds.
- This is very good because information can only be transferred as fast as the bus can transfer it. So if your CPU is fast, but your bus is to slow, it creates a bottle neck. So upping bus speed as well as CPU/GPU/Ram speeds can drastically increase performance.
- Find settings that are stable for your phone. For me this was 123%.
- Note that this will change the CPU clock speed choices that you have. Normal.
Click to expand...
Click to collapse
2. CPU Clock Speed / Governor
- Increasing Clock Speeds allow your processor to calculate more per second, therefore increasing performance.
- Start by finding the maximum frequency that your device is capable of handling, while still keeping stability. For me, this is 1400MHZ.
- Set lowest clock speed to 200 or 400. 200 is the best all-round, and actually uses less power than 100MHZ due to faster race to idle. I use 400 for performance.
- Use a snappy governor. Min/max is great, it is what i use.
- For more battery. lulzactive, ondemand, and smartass are all good.
- Enable smooth UI tweak.
Click to expand...
Click to collapse
3. RAM settings / management.
A. MOAR RAM.
- The Galaxy S has very limited ram, so we must make the best of it.
- It has 500mb, but some is allocated for the camera and GPU, so we only get ~400 in the end.
- Use the Bigmem option. Around 400mb, but breaks 720p recording. Its a good sacrifice.
- Also, Un-install any apps that you are not using! This can free up cache space and leave it for important processes. Go to settings/running/caches for more info.
- Go to settings/developer options/background process limit, and set this to keep more ram free. I use 3.
Click to expand...
Click to collapse
B. Enabling Swap
- Enabling swap allows the kernel to use specially allocated memory (on your SD card) to store cached pages that aren't currently being used, instead of storing them in RAM.
- Frees RAM for foreground or heavy processes.
- Make sure you use a fast SD card, and do not set the swappiness to high, both of these can slow your phone down.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
4. CM Performance Settings.
- Setting these properly can also increase performance on your device. It will not create any instabilities.
- I/O schedulers are all very similar. I personally prefer SIO, CFQ, or VR
- Under Memory management, Allow purging of assets and enable Kernel same page merging. Both use more clock cycles, but free needed RAM.
- Avoid ZRAM. Performance gain is not enough for the number of clock cycles needed to compress and decompress the RAM.
- Enable 16 bit transparency. Lighter load on the system when drawing graphics, and has never causes visual artifacts for me.
- Disable surface dithering. One less thing for your device to do, equals more performance.
Click to expand...
Click to collapse
5. Animation Scales (not necessary)
- This simply makes your device LOOK faster buy increasing the speed of the animations.
- Go to developer options and find Window Animations scale, Transition Animation Scale, and Animator Duration Scale.
- Turn them all to 0.5 for a faster UI.
Click to expand...
Click to collapse
Questions? Feel free.

But OC my phone will make my phone die faster yea?
Because I afraid to destroyed my phone
Sent from my GT-I9000 using xda app-developers app

It does reduce life for sure. As does live OC.
I over clocked my phone for a long time, and it has had no bad effects. It works great to this day. It reduces, but not significantly that you should worry about.
Most CPUS are designed to last for 10+ years, and you may take a year or two off. Nothing major!
Sent from my Nexus 4 using xda premium

AlwaysDroid said:
It does reduce life for sure. As does live OC.
I over clocked my phone for a long time, and it has had no bad effects. It works great to this day. It reduces, but not significantly that you should worry about.
Most CPUS are designed to last for 10+ years, and you may take a year or two off. Nothing major!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I think even less, Ive never heard of anyone suffering at anything from oc anything.
This is an amazing guide and it has everything explained in one place thank you!
Sent from my GT-I9000 using xda app-developers app

Where/how do you enable swap?

good guide but currently not necassary to do,more and more roms are made with enough to tweak the perfomance already done,ive not found anything that has pushed my phone while on a decent custom rom

beardedwonder said:
Where/how do you enable swap?
Click to expand...
Click to collapse
Try this. I never used this guide myself, i just searched it up. Maybe ill add it to the OP if you have success with the guide.
http://forum.xda-developers.com/showthread.php?t=1610835

friartuckme said:
good guide but currently not necassary to do,more and more roms are made with enough to tweak the perfomance already done,ive not found anything that has pushed my phone while on a decent custom rom
Click to expand...
Click to collapse
it is not necessary at all, but there is nothing wrong with getting as much bang for your buck as you can!

AlwaysDroid said:
Try this. I never used this guide myself, i just searched it up. Maybe ill add it to the OP if you have success with the guide.
http://forum.xda-developers.com/showthread.php?t=1610835
Click to expand...
Click to collapse
This thread isn't really a guide then, it doesn't look like you can use swap with semaphore.

beardedwonder said:
This thread isn't really a guide then, it doesn't look like you can use swap with semaphore.
Click to expand...
Click to collapse
I'm abit out of the loop. I used devil kernel and it had it. I know cyancore kernel has it!
Sent from my Nexus 4 using xda premium

AlwaysDroid said:
it is not necessary at all, but there is nothing wrong with getting as much bang for your buck as you can!
Click to expand...
Click to collapse
very true,i agree

Tips to increase performance and increase battery life |Xperia X8/W8

Hey people, this is my first post.
So basically this post is for people still using xperia x8 / w8.
TIPS to increase performance :
1. Install a custom ROM (with a custom kernel). It's no use installing a ROM on stock kernel because it's not very fast and battery life is low too ( I like Minicm7 and Minicm10)
2. After installing the kernel and rom, install a nice launcher. (LauncherPro for gingerbread and nova /apex for ice cream sandwich or jelly bean).
3. Tweak cyanogenmod performance settings : increase vm heap size, allow purging of assets, disable surface dithering, set cpu governor to smartassv2. Overclock if you want but not too much.
4. Use v6 supercharger script. (easy to follow and works great). Do it only if you have custom kernel, because on stock it asks to update busybox which soft bricks the phone).
5. Use autostart manager to remove unnecessary apps from boot.
6. Install apps that you need.
7. Enable "long press to kill apps" in development and kill after you use them like browsers etc.
8. Don't use task killer.
Battery life tips (I assume you are on custom ROM with custom kernel) :
1. Use setcpu and enable profiles. Make the following
A) Screen off - Set Minimum and maximum values of clock the lowest.
B) Battery levels - Choose the maximum to any value below 600 mhz but above 320 when say, the level is less than 40 percent or maximum 480 when the level drops below 50 percent.
2. Make sure you uninstall Dsp manager with titanium backup or root uninstaller.
It sucks lots of battery.
3. Don't set auto brightness.
4. Keep vm heap size to 32.
5. Set governor to on-demand using set cpu for all profiles. AS WELL as for normal usage. (where there are sliders)
6. You may use antutu battery saver. It may or may not work for you.
7. Use v6 supercharger script.
That's it. Press thanks if I helped.
Sent from my E15i using xda app-developers app

I appreciate you for the effort you made.
But there are already many threads about it and also I think that most of the x8 users do have knowledge of these basic things..
Cheers..:beer:
sent from my phone using hands and brain...

dagger said:
I appreciate you for the effort you made.
But there are already many threads about it and also I think that most of the x8 users do have knowledge of these basic things..
Cheers..:beer:
sent from my phone using hands and brain...
Click to expand...
Click to collapse
Sir, Thank you for your review and the beer Yes I am aware of the fact that many people know about it but are tired going through many threads so I compiled a list. That's all.

Exactly this thread will be helpful for noobs much. Nice info :thumbup:
Sent from my XPERIA X8 using Tapatalk 2

@op you may want to review some info. for example, for performance, smartassv2 isn't really the best choice (interactive or ondemand, anyone?). you may also want to remove v6 supercharger since noobs will ultimately ask a lot of questions about it (specially ics/jb users). conversely, ondemand is NOT the best choice if you want to save battery. it has a hair trigger that jumps to max freq and stays there for a long time (like interactive but with different conditions for scaling iirc). there are also lighter launchers than nove/apex/launcherpro. uninstalling or freezing unused apps can also help performance instead of trying to kill them (specially with apps that simply restart themselves). you also have the undervolt option. and updating busybox will not necessarily cause issues if you're on custom kernel. i've updated mine on cm7&10 without issues. i do think gdx (at least on stock kernel) bootloops if you update it. as daggre said, we already have lots of tuts about this, so it would be best to give accurate info or else it will just confuse users.

Hey i heard that if i use my sd card for page file i can increase ram or something like that but is it safe i heard that sd card life will get decreased

KillForFun said:
Hey i heard that if i use my sd card for page file i can increase ram or something like that but is it safe i heard that sd card life will get decreased
Click to expand...
Click to collapse
Yes you can use Swapper 2. Useful only if you use class 6 SD card or above. otherwise no use.

cascabel said:
@op you may want to review some info. for example, for performance, smartassv2 isn't really the best choice (interactive or ondemand, anyone?). you may also want to remove v6 supercharger since noobs will ultimately ask a lot of questions about it (specially ics/jb users). conversely, ondemand is NOT the best choice if you want to save battery. it has a hair trigger that jumps to max freq and stays there for a long time (like interactive but with different conditions for scaling iirc). there are also lighter launchers than nove/apex/launcherpro. uninstalling or freezing unused apps can also help performance instead of trying to kill them (specially with apps that simply restart themselves). you also have the undervolt option. and updating busybox will not necessarily cause issues if you're on custom kernel. i've updated mine on cm7&10 without issues. i do think gdx (at least on stock kernel) bootloops if you update it. as daggre said, we already have lots of tuts about this, so it would be best to give accurate info or else it will just confuse users.
Click to expand...
Click to collapse
Sorry for the mistakes. I wrote smartass v2 because interactive sucks too much battery and isn't practical to use. I would like to delete the thread. I'm new here so please tell me how. I will update the facts and then write

tsinghxda said:
Sorry for the mistakes. I wrote smartass v2 because interactive sucks too much battery and isn't practical to use. I would like to delete the thread. I'm new here so please tell me how. I will update the facts and then write
Click to expand...
Click to collapse
you'll have to ask a mod to delete the thread. why not just update it though? it's a good thread for new guys. just update some info and you're good to go.

cascabel said:
you'll have to ask a mod to delete the thread. why not just update it though? it's a good thread for new guys. just update some info and you're good to go.
Click to expand...
Click to collapse
Alright, I'll update by Monday. Thanks

Haha, thanks for the tips :good:

Low memory killer values

Hello my nexus 6 always slow down after days of use, too much apps on memory and low free ram, so I started stuying other devices oom settings, and found that two of fastest devices I can observe have this settings, so try it if you want , for me these fixed slugginess after days without reboot.

lol!
btw, rebooting your device every once in a while will also keep it fast.

fedef12evo said:
Hello my nexus 6 always slow down after days of use, too much apps on memory and low free ram, so I started stuying other devices oom settings, and found that two of fastest devices I can observe have this settings, so try it if you want , for me these fixed slugginess after days without reboot.
Click to expand...
Click to collapse
which kernel are you using ?
normaly the stocl lmk values are good enough to not be laggy

Dead-neM said:
which kernel are you using ?
normaly the stocl lmk values are good enough to not be laggy
Click to expand...
Click to collapse
All the kernels have the same lmk values, that are too low

fedef12evo said:
All the kernels have the same lmk values, that are too low
Click to expand...
Click to collapse
yes these are the stock value for 3gb of ram i guess but they're not too low. the android will kill old apps when necessary to free up the ram.
with gravitybox i can see that on recent tab my memory can be around 130mb free ( not feeling laggy) and when reopen the recent tab again there is around 400mb free and i don't touch lmk value
i think it's a kernel related problem this is why i ask which one he's using.

fedef12evo said:
All the kernels have the same lmk values, that are too low
Click to expand...
Click to collapse
No... not really...
I highly doubt it truly has to do with your lmk... and probably more to do with vmpressure
I bet you have that either set too low... or its broken all together... which means garbage collections isn't happening when it's supposed to...
If you were to drop_cache... your lag would be gone...
Messing with lmk without proper knowledge just leads to an unstable device

rignfool said:
No... not really...
I highly doubt it truly has to do with your lmk... and probably more to do with vmpressure
I bet you have that either set too low... or its broken all together... which means garbage collections isn't happening when it's supposed to...
If you were to drop_cache... your lag would be gone...
Messing with lmk without proper knowledge just leads to an unstable device
Click to expand...
Click to collapse
Maybe yes you are right, I am using aicp rom that has some tweaks about swappiness and vm cache pressure, what are the best values?

fedef12evo said:
Maybe yes you are right, I am using aicp rom that has some tweaks about swappiness and vm cache pressure, what are the best values?
Click to expand...
Click to collapse
Swappiness: no swap file(why do you need one with 3 GB of ram?) No change...
Vmpressure:
This is kinda grey...
There are 2 schools of thought...
HIGH: run between 100 and 200... your device will drop caches as necessary... with error on the side of... dump early dump often...
LOW: run at like 20... or even 0... but then run a cron.d job every 2 hours or so to "manually" drop caches... and when you realize you can make it longer between drops... you do...
Pros & Cons... I have no bloody idea...
Me personally... I like running between 150 and 200... it keeps my phone happy enough...

rignfool said:
Swappiness: no swap file(why do you need one with 3 GB of ram?) No change...
Vmpressure:
This is kinda grey...
There are 2 schools of thought...
HIGH: run between 100 and 200... your device will drop caches as necessary... with error on the side of... dump early dump often...
LOW: run at like 20... or even 0... but then run a cron.d job every 2 hours or so to "manually" drop caches... and when you realize you can make it longer between drops... you do...
Pros & Cons... I have no bloody idea...
Me personally... I like running between 150 and 200... it keeps my phone happy enough...
Click to expand...
Click to collapse
On aicp stock value is swap 0 and cache pressure 20 , so I am going to try 200 thank you

i used to set my low memory killer values, a long time ago. but ive found that rebooting every day or two does a better job.

I know it's not exactly on topic but what about scrolling cache? I hear if you disable it, scrolling in the UI is glassy smooth.
I don't know how to disable except I did see a setting once when I was running Dirty Unicorns.
Don't know if this was only valid on previous OS version or if it still works for MM.
Sent from my Nexus 6 using XDA Labs

MrBrady said:
I know it's not exactly on topic but what about scrolling cache? I hear if you disable it, scrolling in the UI is glassy smooth.
I don't know how to disable except I did see a setting once when I was running Dirty Unicorns.
Don't know if this was only valid on previous OS version or if it still works for MM.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Already tried, without scrolling cache, device is very laggy, dont know why, but having it enabled is better