Well, first off I'm using a Galaxy S3 L710 with the AOKP 4.2.1 ROM and the KT747 Kernel. My processor's Max is set to 1809MHz and Min is set to 486, with all the voltages lowered to safe levels. I am using ktoonservative as my Governor and BFQ as my I/O Scheduler with the values altered to the values shared by mw86 and freecharlesmanson in the Kernelizers thread about extending battery life.
Now I ran a benchmark with no apps running in the background and here are the results:
{
"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"
}
Apparently, some are achieving scores of 9000-10000 but mine is right in the mid 6000s. Could someone share some advice on choosing a Governor/IO Scheduler and also the various variables that will help with performance/fluidity yet also keep battery life at a decent level?
I'd appreciate any advice or suggestions.
Well I switched my IO Scheduler to CFQ and my Governor to SmartAssV2 and my Benchmark Score jumped up to 8200, still not as high as some though. Is there a better Governor I could use? Are there any recommended settings/values for the SmartAssV2 Governor?
I noticed my graphics were a lot smoother during the benchmark too.
In my opinion bench marks mean nothing
If your phone feels smooth just leave it alone
Sent from my SPH-L710 using xda premium
gtuansdiamm said:
In my opinion bench marks mean nothing
If your phone feels smooth just leave it alone
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I understand that benchmarks aren't everything, but I would not say they mean NOTHING. You wouldn't buy a piece of PC hardware if the benchmarks for it were crap, would you?
Anyway, I switched Governors to Performance and my IO Scheduler to CFQ and here are my current results:
The phone runs much smoother, I'm just hoping my battery doesn't die in 2 minutes.
Related
After rooting, unlocking bootloader, flashing Flex http://forum.xda-developers.com/showthread.php?t=1589034 my score is 2729. Runs real nice now.
Uploaded with ImageShack.us
Here is mine with flexreapers with his a100 tweaked kernal (so i can control the cpu max feq for power saving)
Only setting out of the ordinary i have enabled is Force GPU rendering (just experimenting with things to see how well it all works0
{
"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"
}
very nice, what app are u using to tweak the cpu? if you wouldnt mind posting what runs smoothest with no crash. basically a limit threshold. with crossix sd mod i only got up to 2744
I got up to 2830 using set cpu and performance governor with flex rf1. On my usual interactive it got a hair lower, 2790-2800 over 4 runs. Overall I seem to pull about 2750 averaged out. Rf1 isn't any faster then my 3.1 but I was already using the kernel in rf1 ( i think anyways, it was the second kernel he released for 3.1) on it, which did boost the score up about 300 points.
Edit: my bad I used antutu cpu master not set CPU
Sent from my LG-P999 using Tapatalk 2
How do you turn on force GPU? No option like that in the menus. And does it cause any problems?
Its under developer towards the bottom of user interface. None that I've noticed so far, but I've only had it enabled for about 3 hours of use.
Sent from my LG-P999 using Tapatalk 2
That's mine.
Send from my A100
Hi,
The title says it all.. they are not working.. I am using ARHD with stock kernel.. each of them reset the values to default on waking up, reboot, or randomly, or an app pushes the on demand limit..
What I want to do is to limit the clocks to 640 ( or 10000 at least) on daily use..
_delice_doluca_ said:
Hi,
The title says it all.. they are not working.. I am using ARHD with stock kernel.. each of them reset the values to default on waking up, reboot, or randomly, or an app pushes the on demand limit..
What I want to do is to limit the clocks to 640 ( or 10000 at least) on daily use..
Click to expand...
Click to collapse
This is a known issue with Tegra 3. At some low level, those values are governed by the CPU. Whatever you set them to, doesn't stick. Only governor and IO Scheduler sticks.
However, this doesn't mean that your CPUs work at the maximum possible frequency all the time. The Tegra architecture manages the CPU frequencies and you see a distribution of times at different frequencies.
{
"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"
}
.
EDIT: There is one thing you can do. Using SetCPU, under Advanced tab, you will see Powersave Bias (0-1000). Set to 0 on mine. If you set it to 400, your CPU will never go above 1000-1100 depending on how many CPUs are online. I am not sure if this will stick though. If you test it, let us know.
Some useless benchmarks score for the Galaxy Nexus GSM.
All tests were made from a clean install of stock JB and Android Revolution HD. I used stock kernel, Glados and franco's latest nightly (r268/384mhz). Keep in mind that franco's kernel is clocked at a slightly higher frequency by default compared to Glados.
I used 4 benchmarking apps :
Benchmark & Tuning
Cf-Bench
Antutu
Quadrant
NUMBERS!
{
"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"
}
The point here is not telling you what's best or what. Keep in mind that there is a lot of inconsistencies in these results and that the user experience was great across the board regardless of the rom/kernel combination. Benchmarks have to be taken with a grain of salt, they don't really mean anything in terms of real world experience.
Battery life bench marks would be much more interesting
Sent from my Galaxy Nexus using xda app-developers app
With my Galaxy Nexus running stock (Google Developers images) Jelly Bean I got roughly 4000 - 4500 points in Antutu. I'm surprised you got more than 6000.
PURE odin jelly bean:
With controls for CPU frequency, voltage, and (most important) temperature, the chart would be much more meaningful. In my experience, benchmarks are a better test of your air-conditioner than your phone.
My guess is that Antutu is more consistent than Quadrant because it heats your CPU up a lot more than Quadrant. That makes Quadrant results more dependent on environmental temperature.
In this topic give out antutu benchmark results. In addition to the results give the name of the rom and the kernel.
Example :
Screenshot from antutu:
Rom:
Kernel:
Screenshot:
{
"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"
}
Rom: jellybro nightly
Kernel: Trinity alpha 11 1344-384
With this rom and kernel i don't have lags in games, and It's very good to daily use
Sorry for my bad English
ROM: XYLON 14-1 BETA
KERNEL:FRANCO R356
Sent from my Galaxy Nexus using xda premium
Stock deodexed 4.2.1
Franco kernel 348 @ 1.5ghz cpu & 512mhz gpu
Feels smooth enough for me with minimal to no lag at all during gaming
P/s: its over 9000!
delivered by FedEx
Xenon HD
Air Kernel
236-1350 CPU 384 GPU
Really proud of the results but i got an issue, whenever i go over those frequencies, i get lower scores. I´ve seen it throttling on dmesg but gpu does not throttle and if i put gpu at 512 or whatever it is, i get like 68-7400. Anyone know why?
In either case im happy cuz this gives awsome battery life and 0 lag.:laugh:
Try this thread instead. Much more matured with way more results.
http://forum.xda-developers.com/showthread.php?t=1443343
CyanogenMod
Franco Kernel
Paranoid Android
Fancy kernel, no OC
Not sure how to take a screen capture, but my score: 10312 (running Vanir 4.3 on toroplus)
Hello, so here's my situation.
I'm on a Galaxy S4 Mini, running Lollipop 5.1. Everything was fine with my kernel, until i finally discover that it was acting weird..
I was usually setting the governor as conservative, with a maximum frequency of 1350mhz. The problem is that it is effective for the core n°1, but the core n°2 randomly gets online and jump all the way at higher speeds than the limit I've set. Usually 1400 up to 1700mhz. Which makes my phone running hot and draining fast..
I tried to change the hotplug settings to make only core N°1 online, but when I do that, the core runs at 100% (1350mhz which is the limit I've set) all the time.
The only solution I've found ATM to not drain my battery is to set the governor to powersave and locking it to 700mhz.. But it's a crappy solution since the frequency stays at the same state all the time with that governor.
-- EDIT --
Now I'm setting the cpu at 162 min and 810mhz max, with conservative. The big problem is that whenever the phone is awake, it runs almost full time at full load (810 mhz) and never scale down the frequency, just see the screenshot.. This is obviously ruining battery life. Why the hell is it doing this ? Isn't conservative made to use the lowest possible frequency as often as it can ?
{
"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"
}
Do you have any idea on why this problem is occurring ? Thanks
Sent from my GT-I9195 using XDA Free mobile app
Up..
Sent from my GT-I9195 using XDA Free mobile app
Up again.
Sent from my GT-I9195 using XDA Free mobile app