Database Users

V6 supercharger for jellybean

I've been testing supercharger for jellybean for about a day now and I have noticed a boost in performance so I'd thought I'd pass it on.
I'm on cm10 jellybro 8/17 with air kernel #201 non bigmem and noticed the difference immediately after the reboot. Apps seem to open quicker and the phone doesn't lock up as much when multitasking. Also, even though it says I'm only 50% supercharged and I have a weak launcher I still haven't gotten a launcher redraw since running the script but IMA test that more for sure.
I installed all the tweaks it asks if you want before you get the part where you pick the oom groupings :including the 3g speed hack and I chose the moderate 512 HP I think its option 6.
http://forum.xda-developers.com/showthread.php?t=991276/
Hope this helps: )
Sent from my Nexus S 4G using xda app-developers app

Good to know...I tried a while ago and restored my backup since it said I was only 50%. I might have to give it another shot
Sent from my Nexus S 4G using xda app-developers app

jeremy112683 said:
Good to know...I tried a while ago and restored my backup since it said I was only 50%. I might have to give it another shot
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Do some research... As supercharger doesn't really boost your Nexus. It's more for low end devices with little rom. If you haven't had bigmem then maybe you'd feel it yes, I'm running new rasbeanjelly with bedalus and it runs soo smooth with at least 160 mb free ram
Sent from my Nexus S using xda app-developers app

kwibis said:
Do some research... As supercharger doesn't really boost your Nexus. It's more for low end devices with little rom. If you haven't had bigmem then maybe you'd feel it yes, I'm running new rasbeanjelly with bedalus and it runs soo smooth with at least 160 mb free ram
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Hate to break it to you but by modern standard the NS is low end. ICS and JB were built mainly for a device with a GB or more of RAM so every last byte counts.

kwibis said:
Do some research... As supercharger doesn't really boost your Nexus. It's more for low end devices with little rom. If you haven't had bigmem then maybe you'd feel it yes, I'm running new rasbeanjelly with bedalus and it runs soo smooth with at least 160 mb free ram
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
How low end? I heard the same thing when people were testing it on the epic touch which is understandable but for a phone with 512mb running a big os? Yes every little bit helps
Btw I did do my research thanks
Sent from my Nexus S 4G using xda app-developers app

Its not going away any time soon.
Nexus 7 and SGSIII users complain of lag after awhile and supercharging fixes it... as usual.

I, too, can confirm that the Supercharger works good on JB. Running the latest Codename with Air Kernel, supercharger does make a difference I've found but only when multitasking. Disappointing though to still see the occasional launcher redraw, but it's not that big a deal.
Sent from my Nexus S
---------- Post added at 10:55 PM ---------- Previous post was at 10:51 PM ----------
zeppelinrox said:
Its not going away any time soon.
Nexus 7 and SGSIII users complain of lag after awhile and supercharging fixes it... as usual.
Click to expand...
Click to collapse
You've just reminded me to root my N7, lol. Great work with supercharger btw
Sent from my Nexus S

You can easily afford to bulletproof the launcher if you have a redraw here or there

genaro12543 said:
I've been testing supercharger for jellybean for about a day now and I have noticed a boost in performance so I'd thought I'd pass it on.
I'm on cm10 jellybro 8/17 with air kernel #201 non bigmem and noticed the difference immediately after the reboot. Apps seem to open quicker and the phone doesn't lock up as much when multitasking. Also, even though it says I'm only 50% supercharged and I have a weak launcher I still haven't gotten a launcher redraw since running the script but IMA test that more for sure.
I installed all the tweaks it asks if you want before you get the part where you pick the oom groupings :including the 3g speed hack and I chose the moderate 512 HP I think its option 6.
http://forum.xda-developers.com/showthread.php?t=991276/
Hope this helps: )
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
You need to use the Jellyscreampatcher to patch files to patch files to get 100%, use this thread to guide you
http://forum.xda-developers.com/showthread.php?t=1869663
let me know if this helps you

i will try this supercharger too :good:.

Anyone has tangible numbers to represent the improvement? Anything that could be proven as not placebo?
The supercharger makes me think of kids ricing their Civics or a bad commercial with erroneous/random capitalization, funny made up words and flashy colors.
SuperCharger! BulletProof! Die-Hard! Hard To Kill! SuperClean! Cust-OOM! 3G TurboCharger! Kick Ass Kernel Tweaks! MegaRAM!
Where's Vince from Shamwow when you need him eh?
Not saying it doesn't work, but this is the kind of talk clearly made to pickup sheeple rather than to expose facts. How information is presented doesn't really change the end result but changes the target population. Don't all get offended now.

Of those that actually used it, if I remember the math (too lazy to do it now):
50% say it's the best mod ever... It jumbs to...
65% when you add those that say Big Performance Boost... It jumps to...
80% when you add those that say Noticeable Performance Boost.
Are those numbers ok, Frenchy?

zeppelinrox said:
Of those that actually used it, if I remember the math (too lazy to do it now):
50% say it's the best mod ever... It jumbs to...
65% when you add those that say Big Performance Boost... It jumps to...
80% when you add those that say Noticeable Performance Boost.
Are those numbers ok, Frenchy?
Click to expand...
Click to collapse
Boost™ with zOOM zOOM features?
That's a nice poll, but it's flawed in the sense people that will answer it are very likely users of the mod. Kinda like asking an Android user if he thinks Android is better than iOS. Wouldn't be surprised to see the majority answer YES there, and NO if asked on Apple boards.
Other than a poll, any other data to look at? Is the performance measurable in any kind of way?

And you fail to take into account that the majority of respondents have used other tweaks and mods.
This XDA...duh...
And yet, BEST MOD EVER was the most clicked response.
I see you just like to blow hot air and listen to yourself talk before actually knowing anything first hand.
Any more ignorant musings will only qualify as trolling and make you look stupider (I know it's not word but fits perfectly)

Can use supercharge v6 on NS4G? I
Sent from my Nexus S 4G using xda premium

zeppelinrox said:
And you fail to take into account that the majority of respondents have used other tweaks and mods.
This XDA...duh...
And yet, BEST MOD EVER was the most clicked response.
I see you just like to blow hot air and listen to yourself talk before actually knowing anything first hand.
Any more ignorant musings will only qualify as trolling and make you look stupider (I know it's not word but fits perfectly)
Click to expand...
Click to collapse
Shall I gather that you fell down to insults because you're unable to bring anything else than a zany poll? :good:

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Somehow performance should be measured. However as this tweak is said to improve system smoothness and available ram I think it is difficult to measure it.
My own experience is that I don't feel the difference as my phone has enough ram available and never experience launcher redraw anyway.
But as the poll concludes, people say they feel the difference. Don't think all of these votes are fanboy votes so there must be improvements.
Sent from my Nexus S

polobunny said:
Shall I gather that you fell down to insults because you're unable to bring anything else than a zany poll? :good:
Click to expand...
Click to collapse
I stated a fact.
You've been trolling.
Nothing you have posted in this thread has benefited any single molecule in the entire universe.
I brought something.
You've brought NOTHING but BS.

You failed statistics in high school didn't you? We could go on and on, and I could troll all day, but so far only kwibis has tried to justify the use of supercharger through a coherent approach.
You're the biggest troll here, touting all sorts of improvements without being able to calmly back it up with anything else other than a ridiculously flawed poll. You step low enough to get insulting and try to nit pick on someone to discredit them rather than to work on a way to prove your claims. And yes, there's actually a way to test for UI smoothness just as there's a way to test for UI animations. You should try to improve your scientific approach a bit instead of getting your panties in a bunch and getting huffy at the first non believer. I swear it'll help you in life as a whole.

[Q] 4cyl turbo engine NOS mod

I've been keeping my eye on this mod for sometime now and just wanted to know if any other N4 owners have installed it, on what ROM and kernel, and what their opinions are.
This device already flies pretty fast and lag free for me. Don't ever really have low mem issues. But I sure do love mods, tweaks, playing around with this device, and anything that could potentially boost performance even more.
I'm currently using XenonHD with Franco kernel r110.
Cheers and look forward to the responses and discussion.
Link to NOS thread:
http://forum.xda-developers.com/showthread.php?p=38262233
Sent from one device or another.

Hi,
In my opinion do not waste time with it. I've just take a look in the init.d scripts... Some of them are not for our devices like the "touchscreen" and "kernel" (for the shed_features" parts...
The rest is... , test and see but these kinds of "turbo mega lag free extra smoothess performance with extreme RAM performance and giga boost" is to be avoided.
Make a Nandroid backup before testing with all the system files that are modified with these "all in one" scripts, be carefull to the bootloop .
With ours Nexus 4... do they really need these kinds of scripts? Like you said your device is fast and lag free, so no need of these scripts. At best it does nothing, at worst it's counter productive... and after one day after flashing this "turbo" thing you have some lags here and there... Often these scripts for RAM management are not optimized for a device with 2 gigas of RAM and JB 4.2.2, I speak about these "megacompilation" scripts and there is a bunch in the Android Software and Hacking General section. If you want to test something, maybe try V6 Supercharger at worst, and yet I'm not sure we need this...
I've tested a few of these scripts with my Gnex and SIII so I saw that there was nothing impressive at all (as for the title of these threads ) and sometimes it was the opposite (very often) or no improvement at all.
It's like all the build.prop edit for tweaks that we find with these scripts: does nothing, are obsolete, etc...
Googled for some tweaks for VM and RAM management like for some build.prop tweaks, you will be surprised about the real effectiveness
Android, for me, manages very well its RAM so I let Android manages its RAM , maybe some multitasking things to improve but with my Nexus I have not any issues with multitasking like closed apps too quickly or lags after 5 days of use without a reboot. Maybe this is how I use my phone...
So in short your phone works perfectly: don't care about this stuff and focuses you on the CPU settings with your custom kernel (Franco like you use or another one) :angel:

for 2GB RAM in nexus 4 ;
We still have 1GB RAM free, check it in running service, setting -> apps -> running service.
there is no RAM tweaks needed.
This is for device who only has 512MB but running Jelly Bean ROM, such as Nexus S , etc etc.
With QuadCore and 2GB RAM, it is really unnecessary to ahve this kind of tweaks.
There are so many developer in nexus 4 Development Thread.
You can have Customs ROM to optimize or to make more beauty for the User Interface, there are so many options.
For a bit more performance and battery savings, you can try Custom Kernel, I used Franco, It is a good Kernel, to save more battery when idle.
and also you can tweak for color saturation IPS screen, etc etc.
Its all you need.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

viking37 said:
Hi,
In my opinion do not waste time with it. I've just take a look in the init.d scripts... Some of them are not for our devices like the "touchscreen" and "kernel" (for the shed_features" parts...
The rest is... , test and see but these kinds of "turbo mega lag free extra smoothess performance with extreme RAM performance and giga boost" is to be avoided.
Make a Nandroid backup before testing with all the system files that are modified with these "all in one" scripts, be carefull to the bootloop .
With ours Nexus 4... do they really need these kinds of scripts? Like you said your device is fast and lag free, so no need of these scripts. At best it does nothing, at worst it's counter productive... and after one day after flashing this "turbo" thing you have some lags here and there... Often these scripts for RAM management are not optimized for a device with 2 gigas of RAM and JB 4.2.2, I speak about these "megacompilation" scripts and there is a bunch in the Android Software and Hacking General section. If you want to test something, maybe try V6 Supercharger at worst, and yet I'm not sure we need this...
I've tested a few of these scripts with my Gnex and SIII so I saw that there was nothing impressive at all (as for the title of these threads ) and sometimes it was the opposite (very often) or no improvement at all.
It's like all the build.prop edit for tweaks that we find with these scripts: does nothing, are obsolete, etc...
Googled for some tweaks for VM and RAM management like for some build.prop tweaks, you will be surprised about the real effectiveness
Android, for me, manages very well its RAM so I let Android manages its RAM , maybe some multitasking things to improve but with my Nexus I have not any issues with multitasking like closed apps too quickly or lags after 5 days of use without a reboot. Maybe this is how I use my phone...
So in short your phone works perfectly: don't care about this stuff and focuses you on the CPU settings with your custom kernel (Franco like you use or another one) :angel:
Click to expand...
Click to collapse
Ya I've always been cautious when it comes to random build.prop/init.d tweaks and have used zeprox v6 supercharger on older android phones. But was hesitant on this one, despite my desire to tweak and mod to my hearts content and then some. In the OP it says confirmed working on N4 so I was just curious if anyone had actually tried it and with what results. Thanks for the response.
Sent from one device or another.

Hi,
Yep with some old phones with an old Android version and a low hardware compared to the Nexus 4 it can help...
With the Nexus 4 I don't see the point, but yes you can try and see if you feel that there is some improvements, but I honestly doubt.
Yes the OP said it works in the sense that there are no issues (like bootloop) it does not mean, for me, there will be some huge improvements (at least nothing or very little ...).
Personally I will no longer test these scripts since I never see any kind of improvement with my last phones...
It can improve something but can brake something else, I mean for example smoother UI but lagger games, better experience in X or Y situation but your battery will be killed faster, etc... yes it exists
If you like playing with some tweaks and maybe you can find some good results by modifying some values in these scripts but not like as they are here.Try but it takes a lot of time and you need to do some search like on some Android / Linux forum to understand how Android works (and not on a forum or threads with a "turbo mega giga smoother faster script ever seen with NOS injection RAM script of the death" as title :laugh: , other than that... It's worth playing with your CPU settings, governors. At least for me.
And keeps in mind that with these kind of scripts that promise better battery life with much better performance, there is a moment where these two things are not compatible (in certain proportions). If you realy want some extra perfs, you'll need to sacrify the battery life and vice versa

RAM Usage and performance vs installed OS

Having had the latest OTA popup today to update to 14.3.A.0.757 I was keen to look into it and see if it would be any better.
I did a quick Google of the firmware version and read some posts, mostly on here, about issues, the touch screen issue (which has never presented itself to me), battery usage, but most importantly to me, RAM usage.
Well I'm currently running 14.2.A.0.290 on my Z1, and have been for a while.
I have various apps installed, Facebook, Twitter, Netflix, Zedge, Flickr, Photobucket, Sko Go, and various others. I do use my phone a lot.
My phone has been running for 239 hours and some minutes, at time of posting, and is currently showing 520mb free RAM.
I note that when I got this phone new, on 4.1 I think it was, I had 0.9Gb free RAM.
Every time I update, I end up with less RAM.
Now my concern with upgrading again to Kitkat means I am worrying about RAM usage, specifically, if it uses even more, then I am going to be facing force closes and random crashes. Deja Vu.
I bought an Xperia Z, then a Z1 because my old Arc S couldn't cope with all the upgrades. My Arc S worked briliantly when I bought it, but the updates soon made it sluggish, and force closes were common place.
My Xperia Z is running fine on 4.3, but even that phone has lost RAM to the upgrades - that phone was showing 1.2Gb RAM free when I first got it, now that is down to 750mb
Updates alaways seems to equal less performance.
Has anyone compared the Antutu benchmark results before and after updates?
Installed Antutu and ran without restarting my phone, so after ten days -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm downloading and installing the update now, so we'll see how it goes.
I'll post up the results when I'm done.

Factory resets?
Sent from my C6903 using XDA Premium 4 mobile app

Destroyedbeauty said:
Factory resets?
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I haven't factory reset the phone, no, in fact I rarely do after running updates.
Factory resets mean having to set everything up again, accounts, settings, preferences, etc.
I have all the backup options set, and I know Google are great for maintaining my contacts, but I still have to reset Facebook integration, and re-link all of my contacts, and so on. I also like to keep my messages, so that means backing up my SMS before resetting, so it does mean some work to do a full reset.
I have never found it necessary to do a full reset.

Well the verdict is this.
Some nice improvements visually, and some extra free RAM, now seems to run with 700mb free RAM after letting the phone settle for a while.
This is an improvement, so I'm quite happy with that.
I like the unlock animation, and the fact that you can swipe in any direction now. It looks more like fairy dust, compared to the shutter effect previously.
Camera launch is now at the bottom of the lock screen, which is ok.
I had heard that the dialler app was supposed to be improved, showing favourite numbers, and pulling in info about local business on incoming calls, however, I notice no difference when accessing the app, other than the ICE (In Case of Emergency) contact at the top in the contacts listing.
I re-ran the Antutu benchmark, and it does show a DECREASE in performance
It's not much, but is is definitely a decrease.
In all honesty, the update seems to run well, seems fast, and responsive. Really good.
The notifications are grouped now so the fast links to turn off your sound, etc, are now tabbed.
I did notice that the fast links are no longer themed - they are not red, or blue, just white.
A small difference, but I like themes, and like coloured fast links, so a bit of a shame.
The icons themselves look bigger, although they take up the same amount of room.
There's probably other differences, and I'm sure I'll discover them in time.
Overall verdict - good update, impressed.

MickieH said:
Well the verdict is this.
Some nice improvements visually, and some extra free RAM, now seems to run with 700mb free RAM after letting the phone settle for a while.
This is an improvement, so I'm quite happy with that.
I like the unlock animation, and the fact that you can swipe in any direction now. It looks more like fairy dust, compared to the shutter effect previously.
Camera launch is now at the bottom of the lock screen, which is ok.
I had heard that the dialler app was supposed to be improved, showing favourite numbers, and pulling in info about local business on incoming calls, however, I notice no difference when accessing the app, other than the ICE (In Case of Emergency) contact at the top in the contacts listing.
I re-ran the Antutu benchmark, and it does show a DECREASE in performance
It's not much, but is is definitely a decrease.
In all honesty, the update seems to run well, seems fast, and responsive. Really good.
The notifications are grouped now so the fast links to turn off your sound, etc, are now tabbed.
I did notice that the fast links are no longer themed - they are not red, or blue, just white.
A small difference, but I like themes, and like coloured fast links, so a bit of a shame.
The icons themselves look bigger, although they take up the same amount of room.
There's probably other differences, and I'm sure I'll discover them in time.
Overall verdict - good update, impressed.
Click to expand...
Click to collapse
Correct me if I am wrong, but why would more free RAM necessarily be a good thing in an OS like Android? I would be happy if it would use more RAM to keep things like web browser tabs etc. in memory and improve multitasking.
I see why a memory leak is bad but otherwise I can't understand the hunt for as much free RAM as possible.

dape16 said:
Correct me if I am wrong, but why would more free RAM necessarily be a good thing in an OS like Android? I would be happy if it would use more RAM to keep things like web browser tabs etc. in memory and improve multitasking.
I see why a memory leak is bad but otherwise I can't understand the hunt for as much free RAM as possible.
Click to expand...
Click to collapse
I would be happy also to be able to run several tabs/apps and still have RAM spare.
RAM basically is the OS's workspace.
Less workspace = less room for apps to function, hence force closes and slow performace.
For example.
My old Sony Ericsson Arc S had a very small amount of RAM in comparison to todays devices, but when I bought it, it ran with over 100mb free RAM which meant I could install other apps and they would run happily. Once I upgraded the OS from Gingerbread to ICS, the amount of available RAM was less than 75mb and often 40mb, with hardly any 3rd party apps installed. This meant that the phone would look nice, running ICS, but would run slowly, and apps would force close due to insufficient RAM.
I do not want to have a great phone in the Xperia Z1 (or my Xperia Z for that matter) that will run like a bag of crap because it has not enough RAM to work in.
Imagine running the Z1 with only 100mb spare - how would it function? How fast would it be? How many force closes would the user endure? How many apps would you be able to install then??
How would you open the tabs, and apps like you say with a smaller amount of RAM?
You would try, but you would get force closes as the OS shuts down what it thinks are unnecessary processes to maintain the system.
So, this is why I hate to see RAM eaten away by updates.
That is my opinion anyway.
I understand what you are saying, and I agree in a way, I don't mind apps using RAM at all, as long as the phone has sufficient RAM to allow those apps to run alongside the system, with good speed, and no force closing.
In all honesty, I do not mind the slight reduction in the Antutu benchmark, but I do love the increase in RAM demonstrated with this update.
It's early days yet, but it's looking good.

The question is the phone uses 1 gb ram for what?!!!!
My old galaxy s2 was using just 400mb ram
And my old s3 used 500 mb ram
And my friend's galaxy s4 uses 1.1gb ram!!
What is the huge difference between s3 and s4 to use the twice amount of ram?? (this is related to the first question)

Iam running 4.4.2 now and I think 4.2.2 was better for ram consuming
My advice for you disable apps what are unnecessary for you
Enjoy!

Since KitKat is optimized for devices running with 512 MB RAM there shouldn't be any lag or force closes due to RAM usage. The RAM used on my Z1 is mostly 60-70% of the total amount but it doesn't mean that there are any slow downs. In fact it runs as smooth as it should ( a few hickups in the UI now and then but fixed with latest update) and never had I problems with multitasking yet. It would be nicer to see that the OS decreases the RAM usage but it is not a big deal as long as ii doesn't affect the performance.

Linux handle memory differently as compared to other OS.. More free ram is equal to wasted ram in Linux.. Unless you could find memory leak..
Sent from my C6903 using Tapatalk

Lag solutions

I've seen a good amount of people complaining about lag, so i thought i'd share what i've done to get my g3 running smoothly.
* See below for kernel settings
First off I rooted my d850 with towelroot. Using titanium backup, I froze all at&t apps along with apps I don't use like kindle, uber, beats music. Also froze messages back & sync since it was always running, and I backup up my texts manually.
Everything I froze:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now there's the whole art debate. I have noticed a big improvement in smoothness and battery life using art, but there's also compatibility issues with some apps, and xposed. When switching back to dalvik runtime you can definitely see some general UI stuttering, here's what can be done.
Kernel settings
I installed (and highly recommend) Kernel Toolkit and played around with a few settings. You'll have to install busybox too which worked fine. KEEP IN MIND we don't have a recovery to save our asses in case of bootloops so if you make any changes in trickster do so at your own risk, and when using set on boot, apply a long enough delay for you to fix any bootloops in the event that your phone doesn't like your settings.
That being said I would be surprised if anyone manages to find settings that causes reboots on the stock kernel, given that theres no voltage table to mess up, or any unique cpu governers.
Onto my settings:
I/O scheduler = cfq
Governor control (with interactive governor) -> hispeed_freq = 1267200
Here are some other changes you can make in governor control for better performance:
go_hispeed_load - change from 90 to 85
min_sample_time - change from 40000 to 50000
target_loads - change from 85 to 80 or 75 (75 = better performance)
NOTE: I have tested my settings for a few days and they seem to be stable. If you want even better performance (at the cost of some battery life) you can try some more changes DON'T use the set on boot option until you're sure they don't cause reboots! Once you deem them stable you should use set on boot with a 30 second delay. Without the set on boot option you'll have to manually reapply your settings after every bootup as kernel settings get set back to default on boot.
NOTE: I've found using the ondemand governor causes reboots.
With these settings i'm not missing art anymore. I've found that setting the scheduler to cfq takes care of most of the lag. Keep in mind that tweaking the kernel for better performance USUALLY comes at the cost of a little battery life. So you'll have to find a sweet spot that your happy with in terms of performance and battery life. Feel free to discuss and share your kernel settings

I'm probably the only one experiencing more lag with ART than not. With ART enabled my G3 was stuttering everywhere and I had to pull the battery ~3 times in 2 hours because the screen just wouldn't turn on.
It's silky smooth on dalvik though, lol

KiNG OMaR said:
I'm probably the only one experiencing more lag with ART than not. With ART enabled my G3 was stuttering everywhere and I had to pull the battery ~3 times in 2 hours because the screen just wouldn't turn on.
It's silky smooth on dalvik though, lol
Click to expand...
Click to collapse
Yeah sounds like compatibility issues with some of your apps.

Tested ondemand governor, caused reboots.

Surely a third party launcher will just sort all lag issues out?

Why would it do that? Of course it helps with launcher lag but not with lag occuring in menus etc.
Oh and thanks to Heisenberg! Tried your settings and with art enabled everything works nice and smoothly. No more stuttering.

Please let us know how stable these settings end up being. Thanks!

I think people are getting confused over what is lag and what is not.
Lag is when the UI is delayed when it shouldn't be - this can be caused by a number of factors including wrong cpu clock speeds, overheating or lack of quality ram management (usually due to one or two poorly coded apps eating everything up!)
What most of you are experiencing on Dalvik is not lag, its just the way the JIT compiler works, apps on Dalvik will take a split second to open while it compiles what it needs, generally speaking this is not noticable, but we all know people on XDA always notice everything....
If you are experiencing lag then it is most likely caused by something other than Dalvik the ART build on this device is outdated doesn't offer anything (seriously!) over Dalvik, this in no way reflects what we will see on Android L.

My g3 suffers terribly from redraw it just should not be happening on something this powerful

Lennyuk said:
I think people are getting confused over what is lag and what is not.
Lag is when the UI is delayed when it shouldn't be - this can be caused by a number of factors including wrong cpu clock speeds, overheating or lack of quality ram management (usually due to one or two poorly coded apps eating everything up!)
What most of you are experiencing on Dalvik is not lag, its just the way the JIT compiler works, apps on Dalvik will take a split second to open while it compiles what it needs, generally speaking this is not noticable, but we all know people on XDA always notice everything....
If you are experiencing lag then it is most likely caused by something other than Dalvik the ART build on this device is outdated doesn't offer anything (seriously!) over Dalvik, this in no way reflects what we will see on Android L.
Click to expand...
Click to collapse
I had some noticable stuttering in many actions like in menus and scrolling. After changing to ART and enabling these tweaks they are gone. Placebo or not I'm happy with the results, no stutters or lag of whatever you want to call it I'm aware the ART included is nothing like ART on L, but to me it just helps that little bit.

Lookinen said:
I had some noticable stuttering in many actions like in menus and scrolling. After changing to ART and enabling these tweaks they are gone. Placebo or not I'm happy with the results, no stutters or lag of whatever you want to call it I'm aware the ART included is nothing like ART on L, but to me it just helps that little bit.
Click to expand...
Click to collapse
That's placebo.
ART only affects lag, that is the time between pressing on an icon and the app opening. ART pre compiles the bytecode needed to run an app beforehand thus eliminating the need to do it on the fly which dalvik does (it should also improve battery life as converting it to bytecode takes cpu cycles). It doesn't do anything for stutter or scrolling. By yeah the ART in 4.4.2 is old code as well and not optimized yet so there will be little improvement in lag also.

So be it. It doesn't matter to me if its placebo or not. Feels nicer to use and that is what matters.

Still not getting the ART love. For milli seconds of improvement you lose 25% of storage space. Not seeing the net positive at all, but a big a$$ net negative.

rushless said:
Still not getting the ART love. For milli seconds of improvement you lose 25% of storage space. Not seeing the net positive at all, but a big a$$ net negative.
Click to expand...
Click to collapse
You'll have no choice when "L" is released

Batfink33 said:
You'll have no choice when "L" is released
Click to expand...
Click to collapse
I will miss Xposed if they can't get it to work right on ART

I'll try your guide. Lag and redraw is not what I prefer in a new flagship. Art is more than placebo, it's notable better but I'll like to use Xposed.

Batfink33 said:
You'll have no choice when "L" is released
Click to expand...
Click to collapse
SadLy true

Seems to do some difference. Even with art I had some lag in app drawer and it seems to be gone. Placebo or not, it's feels a bit more snappy in app drawer so that's another one to beat the dust ? So far I'll keep art on, I have loads of space and launcher and apps are notable snappier with it in. Its not like my M8 but it's a bit closer.

art
Sorry for a very noobish question, but can someone tell me what art is? I got my lg g3 last week and quiet playing a bit with it. I got the international version 3/32gb (LG-D855 V10a) and wanted to root it to somehow boost my battery life. Its fine and my battery can last a day with my normal usage and im very happy with it (waaaaaay much better than my ip5), but if i can squeeze more juice and make it last a day and a half or even more, im willing to root and take full pledge over my device.
I also experience having error that my device is heating up and won't be able to max out brightness, weird coz when it happen im actually doing nothing with my device, i just adjust brightness and it wont let me to max it out, so as of now im considering it as a bug and hoping that an update will fix it. It does warm up a bit but not the same as my toasty galaxy note 2 and galaxy s4 so i can live with it, but if i can remove the energy being waste and boost battery life by rooting it, ill forget OTA.
Anyway, back to my main concern,,, what is art? Hue hue

Hey mate. Art is android run time. Do a quick google search on how to change it or one of the pro's on here can go into the finer details on the benefits of using it.

Speed up your Moto X (Fastest ROM/Kernel/Settings)

Hi guys and gals, so I started doing some benchmarks a while ago on my moto x after seeing how poorly mc5 preformed on both it and my old Droid Maxx. My goal was to find the absolute best settings and kernel/ROM combination possible. It just so turns out that n5xpa was the absolute fastest ROM available for our device. Not only is it stock aosp/pa with all the pa beta features but it has a couple of extras added on. There is also a custom AOSP CAF kernel that is also over clocked with fast charge built right in.
If you want to boost your in game fps download resolution changer in the play store and set the resolution to 583 x 1024 and set your dpi to 240.
Attached are my benchmarks in antutu 5.2.0 and all my settings. P.S. I do use seeder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Feel free to post the settings and apps you use and your highest benchmarks.

This was using n5xpa? What version? Link?

Heres a link http://n5x.mobi/motox
There are two versions of the ROM. The paranoid android version and cyanogenmod version. Cm is the only one posted in the xda forums.
Updated benchmark

Those are really impressive scores. It is hard for me to break 29000 on my Maxx overclocked to 1.944 GHz running Faux's kernel. Well done.
This is using Interactive governor for CPU and on demand for GPU, stock voltage, fiops for I/O scheduler. I ran this setup for a few months but currently running on Intelliactive governor to see if there is a noticeable difference on battery life. But with how big the battery is on the Maxx, I don't think it matters. Antutu score suffers greatly when on intelliactive. Usually scores around 27000 but the phone is just as snappy.

Johnny Wong said:
Those are really impressive scores. It is hard for me to break 29000 on my Maxx overclocked to 1.944 GHz running Faux's kernel. Well done.
This is using Interactive governor for CPU and on demand for GPU, stock voltage, fiops for I/O scheduler. I ran this setup for a few months but currently running on Intelliactive governor to see if there is a noticeable difference on battery life. But with how big the battery is on the Maxx, I don't think it matters. Antutu score suffers greatly when on intelliactive. Usually scores around 27000 but the phone is just as snappy.
Click to expand...
Click to collapse
I run a lower res around 563 x 1024 to 583 x1024 and I get major bench scores. And yes you really don't need a battery saving kernel on the maxx with its crazy battery. I had a locked maxx for a while. Just couldn't stand not having
cm or pa on it so I got a moto x
Sent from my Moto X using XDA Free mobile app

What app are you using in the screenshot that shows your kernel's governor and clock speeds?

I don't see how crippling your device's functionality makes it better, outside of your benchmark score. Lowering a device's native screen resolution just to show off to all your friends some amazing benchmark score is pointless.

I couldn't keep my battery drain down on n5xpa ROM. For AOSP I've found Liquid to be the best stablity/speed + battery once I set it right, intelliactive bfq with intelliplug on, mpdecision off. I'm finally back to stock now that there's a custom kernel option for sprint users finally. And to be honest stock is much better all around for me. It's faster, good ole stock touchless and active Features and my battery is doing quite well.
Sent from my XT1056 using XDA Premium 4 mobile app

I have a small issue regarding contacts while trying to import my list from SIM. It simply says No Contacts anyone know why or how to fix? Also selecting 2G and the signal disappears 3G and LTE are the only working options. This is on PA 4.0 version.

So...you crippled your Moto X by flashing a custom ROM (removing any unique Moto features), lowered its screen resolution, overclocked it, and used a placebo application (Seeder) to get a slightly higher benchmark score.
And then made a post about it.
Good job.

Don't listen to imnuts or Lyokacanthrope. They always p1ss on anyone who actually does something.
Pathetic.

Sorry? It seems pretty pointless to reduce the functionality of a flagship smartphone just to get 3000 more points in a useless synthetic benchmark.
Doing this, your screen clarity will be drastically reduced, your battery life will go to hell, and you'll lose most of the features that make this phone interesting.
I love tinkering as much as the next guy, but this is just plain silly.

Quantumstate said:
Don't listen to imnuts or Lyokacanthrope. They always p1ss on anyone who actually does something.
Pathetic.
Click to expand...
Click to collapse
Did something? It is completely crippling the phone just to get better benchmark numbers. I'll stick to my low benchmark, but still usable phone over anything mentioned in the OP. Installing AOSP is one thing, but the rest of the stuff that was done offers no increase in usability and is solely for increasing you e-peen.

You two just criticize and find fault, while never offering an alternate solution. This is the lowest and sickest (in the old sense of the word) mindset, afaic.
Researchers must explore new methods and boundaries in order to make breakthroughs, which are always unforeseen by you ignorant lot.
Oh, you happily take advantage of new developments, which you'd impeded right up until they mature, and never give credit nor acknowledge your role in discouraging innovators.
Good job there.

I see everyone's point here. Though i feel it is very important that someone browsing this forum understand in order to get the "speed" gains that are being promoted, features are being removed and shortcuts are being taken. Nothing wrong with that. "Knowing is half the battle" - G.I. Joe

Alternate solution: Leave your phone stock so it's actually usable. I'm not sure what you're looking for here, or in other threads with similar topics. There are times where alternate solutions are not useful, like this thread where the OP is illogical.
Turning down the resolution on a smartphone is like trying to get somewhere in a race car during rush hour traffic. Sure it goes fast, but what's the point?
Maybe it seems overly critical, but there isn't anything left when there are unreasonable, illogical, or some other similar post made.
Sent from my Moto X

does it impact battery positively?
i can see using a 800x600 resolution on days that all i want is 24h of voice gps and texting.

Quantumstate, you treat this whole thing like it's some major scientific breakthrough that will cure cancer.
It's just getting a higher benchmark score on a year old phone. (while, of course, outright gimping it)
Nothing more.
It's akin to buying a brand new PC and slapping Windows XP on it because it uses less RAM.
Actual, GENUINE, improvement would probably be something along the lines of getting increased real-world framerates and stability while not sacrificing any functionality. Say, a rewrite of the kernel hotplug driver and GPU governor. That'd be neat to see.

No. Experimenting with various aspects of Android and taking a characteristic to an extreme, often leads to surprising results. It's the way science has always been done. If you perpetually follow the well-beaten path, you will always get average results.
This is what a few of you can not understand. But you go further than just dismissing these experimenters -- you go out of your way to criticize them. And that's when y'all deserve to be slapped, or else the whole development environment suffers.
It doesn't matter if you don't recognize the value. Take your frustrations out on something else.

gcbxda said:
does it impact battery positively?
i can see using a 800x600 resolution on days that all i want is 24h of voice gps and texting.
Click to expand...
Click to collapse
No, changing the resolution doesn't really do anything appreciable for the battery. You might get a little more due to the CPU and GPU working a little less, but nothing statistically significant.
Quantumstate said:
No. Experimenting with various aspects of Android and taking a characteristic to an extreme, often leads to surprising results. It's the way science has always been done. If you perpetually follow the well-beaten path, you will always get average results.
Click to expand...
Click to collapse
How is doing what's always been done differ from what is a given? I'd be more concerned if all of the changes in the OP decreased performance. You do all of that stuff, you are guaranteed to get better benchmark scores, I'd say that is lower than average results.
Quantumstate said:
This is what a few of you can not understand. But you go further than just dismissing these experimenters -- you go out of your way to criticize them. And that's when y'all deserve to be slapped, or else the whole development environment suffers.
Click to expand...
Click to collapse
I encourage legitimate development, but none of that ever shows up g here anymore. Legitimate experimentation would be getting significantly better benchmarks without hurting the hardware, battery life, or functionality of the device. Installing AOSP is one thing, kernel another. All credibility went out the door when the screen resolution was lowered and benchmarks used as the only measure of results.
Quantumstate said:
It doesn't matter if you don't recognize the value. Take your frustrations out on something else. Take up sports, if you're not too fat.
Click to expand...
Click to collapse
I go to the gym regularly, as long as my schedule permits. Maybe you should try taking some classes in engineering, critical thinking, and logic, your posts suggest they are needed.
Sent from my Moto X