So I thought about overclocking. I never overclocked any CPU by now. No PC cpus, no mobile cpus
I just always read: Do not overclock! More heat production, more energy costing and of course: probably decrease device life-time and may damage the phone.
On the opposite there is: more cpu-power. WFS seems to be able to get OC'd to 800 MHz (which is 200 above standard and only 200 below Desire)
So, what can you tell me about the above conclusions?
Next question: Do I need overclocking, or is it just to win a p.... length comparing ?
I'm on stock European rom 2.3.5. I know I need custom kernel. which one I could use, how to flash? Which apps do I need furthermore?
theq86 said:
So I thought about overclocking. I never overclocked any CPU by now. No PC cpus, no mobile cpus
I just always read: Do not overclock! More heat production, more energy costing and of course: probably decrease device life-time and may damage the phone.
On the opposite there is: more cpu-power. WFS seems to be able to get OC'd to 800 MHz (which is 200 above standard and only 200 below Desire)
So, what can you tell me about the above conclusions?
Next question: Do I need overclocking, or is it just to win a p.... length comparing ?
I'm on stock European rom 2.3.5. I know I need custom kernel. which one I could use, how to flash? Which apps do I need furthermore?
Click to expand...
Click to collapse
No it's not just for a pissing contest.
Jikantaru's new kernel will allow you to set your clock to vary between 120 Mhz and 806 Mhz although 787 Mhz tends to work for those unlucky enough to have phones that freeze up at 806 Mhz.
The CPU doesn't run balls out all the time. It speedsteps as needed to save battery power.
You flash the kernel that you download to your SD card through CWM Recovery's Install zip from SD card feature.
Reboot and you now have Ext4 support for Link2SD, etc, and overclocking capabilities as well as a host of other kernel tweaks to handle memory management, etc.
As far as programs to set the clock with? SetCPU, Rom Toolbox, Nofrills CPU, Antutu CPU, etc.
I would choose "Smartass" as your governor and 120 and 806 as your min and max CPU settings and choose to set it at boot.
That's just my preference.
I personally bought Rom Toolbox Pro and manage the CPU settings through it.
It's got a host of other cool features all in one place and jrummy updates it very often with new fixes, features, etc.
thanks for that.
so what about damaging the cpu or the device? is there nothing to worry about?
and what is a govener? do I need it in addition to setcpu ?
theq86 said:
thanks for that.
so what about damaging the cpu or the device? is there nothing to worry about?
and what is a govener? do I need it in addition to setcpu ?
Click to expand...
Click to collapse
The governor is the method by which the phone plans it's stepping up and down of frequencies. Smartass is a tried and true good combination of power savings and stepping to the plate with high clock frequencies when needed.
No you won't need anything extra. It's one of the settings in any of those programs.
Sorry for asking again:
It won't damage my device or burn the cpu as overclocking a normal PC CPU would do?
edit: using nofrills now. Seems to work.
theq86 said:
Sorry for asking again:
It won't damage my device or burn the cpu as overclocking a normal PC CPU would do?
edit: using nofrills now. Seems to work.
Click to expand...
Click to collapse
Overclocking comes with no promises man. Mine's been overclocked since August so that's all I have to go on.
There is always a danger or risk when overclocking. The manufacturers determine the safe frequencies, temperatures, voltage, etc. based on scientific experiments in different environments. However, with that said, obviously, they are not infallable either. The best way to determine your risk is to think about what conditions you'll be using it in the most and what kind of stress it'll put on your phone's internals. Do some research and see what other people have problems with and under what kind of stress was the phone. Use common sense. Things like raising voltage and frequencies raise the temperature of the phone's internals, also. So, in turn, do you also have a case on the device that retains heat? Do you live in an humid/dry or warm/cold area? Do you do a lot of multitasking? Are you constantly on it? Hope this helps.
Sent from my myTouch_4G_Slide using XDA App
i heard/read about it in my SGS2's time... It was implemented by Gokhan in his kernel but later stripped out because of some problems. PegasusQ is said to be made to handle Quad-core like our One-X, and SGSIII is said to be using this governor by default... Will we be able to see this governor in future Kernel build? or its not compatible technically with Tegra-3 since its a 4+1 setup? Can someone with the knowing enlighten us?
it seems that no one is interested with this
The latest Siyah kernel for SGS2 actually uses pegasusq by default.
jaytana said:
it seems that no one is interested with this
Click to expand...
Click to collapse
Murag wala gyud intresado.which is better for sgsII in terms of battery life?this governor or the hotplug?
I'm afraid I can't help with this, sorry, I do have a Question however.
I've seen people talking about Governors etc, is that something to do with the Chips in the Tegra 3?
The-Last-Hylian said:
I'm afraid I can't help with this, sorry, I do have a Question however.
I've seen people talking about Governors etc, is that something to do with the Chips in the Tegra 3?
Click to expand...
Click to collapse
A governor changes when the CPU changes frequency. More time spent at lower frequencies will, of course, mean better battery life - but lower performance. The trick is to find one you like.
Read this: http://forum.xda-developers.com/showthread.php?t=1369817
It is missing a few governors I've seen (such as PegasusQ) but is fairly complete.
Check this post Pegasusq Governor
Re: Post by user splus in Franco.kernel thread
Sorry to post in this forum, but I don't have the minimum post count yet to post in the development forums
I read a post today by splus which I found very interesting,
In r220 hispeed_freq parameter in governor control has been changed from 1200000 (was an old value from first version of Franco JB kernel) to 1228000. As a result CPU now spends most of its time at either at 384 or 1228 MHz, and much less time at higher frequencies.
For some reason if speed_freq value is set to a step lower than 1228000 then it will make CPU to use all higher frequencies in a more balanced way.
What I noticed is that for 1036 it needs to have slightly higher value of 1037000, because 1036000 will put the CPU only to 729 MHz. This is probably because the real 1036 MHz frequency is something like 1036.xx MHz, so it's best to set speed_freq value to a 1000 more than the desired frequency.
Hispeed_freq parameter is just an initial higher speed frequency that CPU will jump to when there's some CPU load. And if the CPU load is still high after the CPU goes into this frequency (in other words if this frequency is not enough to finish the job) then interactive governor will put the CPU in even higher frequencies.
On stock JB kernel max frequency is 1200 MHz, and hispeed_freq is 700000.
When speed_freq is set to 1228000 it will use mostly 384 and 1228 MHz frequencies.
Set speed_freq to 1037000 (or previous 1200000) and more higher frequencies will be used.
There's certainly many possibilities to play with min and max CPU values, together with speed_freq to come to the best values. And probably for each max CPU frequency different speed_freq value would work best...
Click to expand...
Click to collapse
but I wanted to learn more so I did a lot of Googling about the parameters of the interactive governor. Unfortunately, I kept finding the same few beginners' guides to the different governors available, explaining and comparing their capabilities. There was no advanced explanation of the parameters or their possible valid values.
I found this post by RootzWiki user abqnm, which shed a little more light on the hispeed_freq parameter, and input_boost also. From what I've read on various sites, the input_boost seems to be a binary parameter, so setting it to 1 should jump the CPU up to the frequency specified in hispeed_freq immediately upon detecting a screen touch event. This would make your GNex feel a bit more responsive, without having to wait for the CPU to hit load, but it could negatively affect battery life. In my case, running 729/1612 with hispeed_freq set down at 1036MHz (1037000 in governor control), it's not that big a jump and opening a couple of apps would likely push my speed up beyond it soon anyway, so the battery hit would probably not be much.
As splus said:
After lot of fiddling I found it works best when hispeed_freq is set to 1037000 (not 1036000, it looks like that frequency is actually closer to 1037 MHz so 1036000 doesn't "reach" it).
Click to expand...
Click to collapse
so using 1036000 in governor control would correspond to the next step down, 729MHz. I know it's easy enough to stick on an extra 1000 for safety, to ensure we hit the right steps, but I'd be curious to know the exact kHz values we could be using.
I'm off to start experimenting with undervolting these new CPU freqs, and my 512GPU Core to reduce my temps a bit.
In case anyone asks, I'm on stock JRO03C w/Franco r220 512GPU.
Very good post! Welcome to XDA! :good:
I'll link to your post on the franco thread just so it gets a couple views from people there.
Edit: I see that you've actually been here awhile! Go help a few more people so you can contribute in the Dev forum.
Yup, that's me... total lurker! I usually defer to the wisdom of the devs and seasoned members, and 99% of the time if I've had a problem/question re my Nexus it's already been posted and there are whole conversations for me to read and digest. I hate the idea of clogging up a thread with a "me too" or "thanks" post, so generally if I don't have something useful to contribute I keep quiet and hang in the shadows. I only come out to feed.
So basically, I'm a knowledge vampire.
That's enough OT... Franco stuff!
I've previously read droidphile's governors thread to which splus linked in their reply to your repost in Franco.kernel. In post #2, containing the governor tweaks (which I found very useful) even droidphile seems to have the wrong idea about the "hispeed_freq" parameter, stating:
(Default value is scaling max freq)
Click to expand...
Click to collapse
The same section also omits any mention of the "input_boost" parameter.
My undervolting is going well. Inspired by the voltages on rogersnm's signature, I'm currently running these:
Code:
1612 - 800 mV
1536 - 750 mV
1420 - 750 mV
1305 - 750 mV
1228 - 725 mV
1036 - 725 mV
729 - 700 mV
384 - 700mV
CORE -
512/384 - 900 mV
307 - 900 mV
153 - 825 mV
IVA -
266 - 600 mV
133 - 600 mV
I added an extra 100mV to the seemingly rock bottom CPU voltages for safety, but I'll try to reduce them gradually. I've been stable for over 40 hours so far on this setup. With r220, Franco really seems to have nailed it!
BTW, thanks for reposting in the Franco.kernel thread :highfive:
Fantastic. Keep us updated on your progress with voltages, seems like you're doing a great job!
Also, happy to help!
nemotheblue said:
Code:
1612 - 800 mV
1536 - 750 mV
1420 - 750 mV
1305 - 750 mV
1228 - 725 mV
1036 - 725 mV
729 - 700 mV
384 - 700mV
CORE -
512/384 - 900 mV
307 - 900 mV
153 - 825 mV
IVA -
266 - 600 mV
133 - 600 mV
I added an extra 100mV to the seemingly rock bottom CPU voltages for safety, but I'll try to reduce them gradually. I've been stable for over 40 hours so far on this setup. With r220, Franco really seems to have nailed it!
BTW, thanks for reposting in the Franco.kernel thread :highfive:
Click to expand...
Click to collapse
I'm trying these too. So far so good!
Hi nemotheblue. Good post and findings!
I'm just looking at those voltage values you wrote - are you sure you turned off the SR?
If you haven't don't turn it off with those voltages because you'll get an instant reboot, they seem super low.
Rogersnm wrote and fiddled a lot with voltages, some very good posts.
Better go back to stock voltages, turn off the SR, and then go little by little down with frequencies. When adjusting each frequency best is to set that particular frequency as min (or max if it is higher) frequency so the CPU actually uses it.
And when you get a reboot then just use 25mV higher than the one with reboot.
I'd suggest to have fsync turned on when you fiddle with voltages because that will lessen the possibility of loss of data when phone reboots.
Another thing to have in mind is that even some combinations of frequencies do not work together. Some frequency might work OK with certain voltage with certain max/min frequencies but might not with other min/max frequencies. It looks like the actual change from one frequency to another (and depends from which to which) can determine a lot if a voltage is stable or not.
Also, it apparently very much depends on a ROM you use - different ROMs will probably need readjustment of voltage table.
Undervolting actually won't help much with battery life, smart reflex does a very good job already. It would help most if you game a lot or use your phone heavily, so then when higher frequencies are used the phone would get less hot and use slightly less power.
Otherwise, and especially if you change ROMs, I'd say it isn't worth the trouble.
nemotheblue said:
..................................
I've previously read droidphile's governors thread to which splus linked in their reply to your repost in Franco.kernel. In post #2, containing the governor tweaks (which I found very useful) even droidphile seems to have the wrong idea about the "hispeed_freq" parameter, stating:
..............................
Click to expand...
Click to collapse
Since there's lot of info to cover, mistakes can happen. I'll correct it if something is wrong.
Anyhow, if you check the interactive governor code,
if (!hispeed_freq)
hispeed_freq = policy->max;
This means if kernel default for the value of hispeed_freq=0, then it's assigned to policy_max aka scaling_max.
hispeed_freq is kinda like max_load_freq for ondemand.
Btw, input_boost is not available for interactive governor 'designed' for i9100 GS2 with Exynos chip. I don't know about Gnexus' Omap. Since i take one of the GS2 kernel as reference, governors params are kinda specific to i9100 and exynos architecture.
splus said:
Hi nemotheblue. Good post and findings!
I'm just looking at those voltage values you wrote - are you sure you turned off the SR?
...
I'd suggest to have fsync turned on when you fiddle with voltages because that will lessen the possibility of loss of data when phone reboots.
...
Undervolting actually won't help much with battery life, smart reflex does a very good job already. It would help most if you game a lot or use your phone heavily, so then when higher frequencies are used the phone would get less hot and use slightly less power.
...
Click to expand...
Click to collapse
@splus Wow, thanks for joining in on my little thread! Rest assured, before I started my tinkering I turned SR off and fsync on. I've read all 2306 pages of the Franco.kernel thread and avidly followed several conversations within it. I don't mind being a bit adventurous and trying out tweaks and mods; I just prefer to let other, more educated people try it first! I'm a measure twice, cut once kinda guy.
I followed rogersnm's undervolting saga in the Franco thread up to a couple of weeks ago, and recently caught up with his linaro thread, but I was as amazed as you seem to be at the tiny numbers he's currently reporting.
That being said, the voltages I reported were totally stable for me the last 3 days, until tonight. Tonight, I went to a double bill of Batman Begins and The Dark Knight - 5 hours in a huge, sold out cinema with easily 1,000 people. By the second movie, the room temperature was in the high 30s, if not 40C. I got an email, had a read, tapped back to inbox and BAM! The screen froze for about 3 seconds, then rebooted. The crazy thing is, I tried an hour later to reapply the undervolt and it froze straight away. I'm back on SR for a while, but I might try again tomorrow.
My original intention with the undervolting was just to drop the CORE, because I'm getting great performance from the 512GPU, but I notice the area under the camera on the back of the phone can get pretty hot if I'm playing games or watching a video for >30mins. Granted, I don't do that too often, but I figured it'd be nice to eliminate the extra heat. Once I saw the power saving calculations in rogersnm's chart, I was convinced to go the whole hog. The jury's out...
droidphile said:
Since there's lot of info to cover, mistakes can happen. I'll correct it if something is wrong.
Anyhow, if you check the interactive governor code,
if (!hispeed_freq)
hispeed_freq = policy->max;
This means if kernel default for the value of hispeed_freq=0, then it's assigned to policy_max aka scaling_max.
hispeed_freq is kinda like max_load_freq for ondemand.
Btw, input_boost is not available for interactive governor 'designed' for i9100 GS2 with Exynos chip. I don't know about Gnexus' Omap. Since i take one of the GS2 kernel as reference, governors params are kinda specific to i9100 and exynos architecture.
Click to expand...
Click to collapse
@droidphile Thanks for taking the time to reply. I didn't mean to sound like I was attacking your guide; I'd just read conflicting information from multiple other sources and played the numbers. I was labouring under the false assumption that all interactive governors are created equal. Is there some kind of official/original reference/guide/man page for the governors and their parameters, or are you devs left to interpret the code for yourselves?
I must admit, I'm more confused than ever now. I just can't reconcile your explanation with splus' claim that hispeed_freq=1037000 is the sweet spot for getting interactive to use the intermediate freqs up to a max well above 1036MHz???
nemotheblue said:
@splus Wow, thanks for joining in on my little thread! Rest assured, before I started my tinkering I turned SR off and fsync on. I've read all 2306 pages of the Franco.kernel thread and avidly followed several conversations within it. I don't mind being a bit adventurous and trying out tweaks and mods; I just prefer to let other, more educated people try it first! I'm a measure twice, cut once kinda guy.
I followed rogersnm's undervolting saga in the Franco thread up to a couple of weeks ago, and recently caught up with his linaro thread, but I was as amazed as you seem to be at the tiny numbers he's currently reporting.
That being said, the voltages I reported were totally stable for me the last 3 days, until tonight. Tonight, I went to a double bill of Batman Begins and The Dark Knight - 5 hours in a huge, sold out cinema with easily 1,000 people. By the second movie, the room temperature was in the high 30s, if not 40C. I got an email, had a read, tapped back to inbox and BAM! The screen froze for about 3 seconds, then rebooted. The crazy thing is, I tried an hour later to reapply the undervolt and it froze straight away. I'm back on SR for a while, but I might try again tomorrow.
My original intention with the undervolting was just to drop the CORE, because I'm getting great performance from the 512GPU, but I notice the area under the camera on the back of the phone can get pretty hot if I'm playing games or watching a video for >30mins. Granted, I don't do that too often, but I figured it'd be nice to eliminate the extra heat. Once I saw the power saving calculations in rogersnm's chart, I was convinced to go the whole hog. The jury's out...
@droidphile Thanks for taking the time to reply. I didn't mean to sound like I was attacking your guide; I'd just read conflicting information from multiple other sources and played the numbers. I was labouring under the false assumption that all interactive governors are created equal. Is there some kind of official/original reference/guide/man page for the governors and their parameters, or are you devs left to interpret the code for yourselves?
I must admit, I'm more confused than ever now. I just can't reconcile your explanation with splus' claim that hispeed_freq=1037000 is the sweet spot for getting interactive to use the intermediate freqs up to a max well above 1036MHz???
Click to expand...
Click to collapse
Yeah, if you do some gaming and more intensive stuff then it might be worth to find some good voltage values.
Still, those voltages seem pretty far from what hardware would be capable of running so that makes me think the SR check box wasn't really displaying its actual state somehow.
If you were using Franco's app did you check the last tab to see if mV values at certain frequencies were the same as in your table? If yes then I'm just amazed you were able to run it that way...
Anyway, good luck with further undervolting, please post your stable voltages when you find them...
If you have higher OC CPU frequency as max value in interactive (I'm talking about GNex, every chipset behaves differently) then it looks to me that if you set hispeed_freq to 1228000 the CPU would often just stay at that frequency, as if the system decides that it's enough to finish the job. But if you set it to 1037000 then it often determines it is not enough and scales the CPU to higher frequencies, and then you get the CPU to actually use higher frequencies as well.
Other direction would be to set hispeed_freq to even higher frequencies and that'll definitely make it more responsive but at a battery life cost.
The most responsive system would be that CPU goes to max whenever there's something happening. Google actually said at their IO that they tuned JB to go to max frequency at any touch but if you use the stock kernel and check CPU Spy charts you'll see that CPU goes initially only to 700 MHz.
There are other parameters, but it's all about finding a sweet spot for performance and battery life...
Needless to say, tuning all those governor parameters is greatly dependent on available frequencies, programmatically implemented governors and its parameters (which can be changed, a kernel developer can design and implement his own governor and its parameters) and especially chipsets and the way they behave. Every device is very different...
I think we would have better performance if there would be less frequencies in a kernel than currently in Franco's, but if the CPU is really efficient at scaling frequencies up and down through many steps all the time then maybe not.
Either case life goes on and I'm looking forward to see that new Batman myself in couple of days!
Fine folk of XDA,
Apologies for my long absence! I wasn't abandoning the thread; I got a call to work on a short film and had an insane 10 days of 13-16 hour working days and my brain was just too tired in the evenings to keep up with testing and tweaking. Plus, I needed my phone 24/7 stable to handle the continuous flow of calls, texts and emails from the production office.
So, I reverted to SR and dropped my max freq to 1228 and had no problems.
Catching up on the Franco thread tonight, I read a post by daggerxXxsin saying
I am running 600mv on 384-729 and 675mv on 1036-1228. Only works when I'm on 512gpu though. No random reboots or nothin'. Plays games like a champ and never heats up (temp never goes higher than 45°)
Click to expand...
Click to collapse
I'm currently trying these out on 729-1228 with SR off and fsync on, along with the following:
Code:
CORE -
512/384 - 900 mV
307 - 900 mV
153 - 825 mV
I'm gonna leave IVA alone on SR. I never really noticed any difference undervolting it before, and I figure if I'm pushing my MPU voltages so low, I'm just begging for crashes so it's best not to mess with anything that would affect I/O.
I'm currently running r225 512GPU, and I had some wifi issues where the indicator would frequently switch from blue to grey and lose the connection. However, having read some frequent posts in the Franco thread, I've switched from CWM to TWRP, wiped caches and reflashed Franco so I'll wait and see if the problem resurfaces.
BAH! Screw it, I just refreshed the Franco thread and r230 is out. Gonna flash and see how I get on...
Hi again nemo, just stumbled on this thread again
Wondering what posts indicate that CWM vs. TWRP recoveries would make a difference for the booted OS's Wifi/Google Services connectivity?
As I understand it JB in general just has a bit of a Wifi problem vs. ICS and even with ICS the Galaxy Nexus does vs. any other phone. I'm currently having acceptable Wifi using franco 241 (which has a new IO scheduler which makes things feel extremely snappy).
I'm pretty sure all I based that decision on was this discussion in the Franco.kernel thread. In retrospect, kinda half-baked but I must say I'm impressed with this recovery anyway!
I'm still following the thread religiously, rocking M5 at the moment though I'll likely jump on the first 512GPU nightly that comes out. I spent hours yesterday reading the MiNCO and MiNCO+ threads, very carefully backed up, then flashed v4 and immediately ran into this major roadblock and ended up reverting. Further study is required...
A few things come to mind with that storage problem:
1) Maybe that the sdcard bin (as is also in franco's cwm zips) is installed and messing things up weirdly. You'll need to push the stock one back (first post of franco.Kernel thread iirc).
2) A recent ROM Manager bug where .nomedia files were getting placed in the /sdcard/ top level folder, so you might want to investigate that with adb shell (though this would be weird considering you say you're using TWRP and ROM Manager is CWM).
3) Go to Apps > All > MediaStorage, Force Stop and clear data+cache. Reboot to have MediaScanner rebuild the MediaStore.
Edit: Just saw your post in the linked thread... looks like you tried 2+3... so try 1?
osm0sis said:
...1) Maybe that the sdcard bin (as is also in franco's cwm zips) is installed and messing things up weirdly. You'll need to push the stock one back (first post of franco.Kernel thread iirc)...
Click to expand...
Click to collapse
Very clever! Way to think outside the box, ossie :highfive:
I should have time to try again tonight, so I'll let you know how it plays out. While I'm at it, I'm excited to try out DarkJelly's inverted gapps, but I'll make sure to tackle the storage problem before flashing any apps/mods
So I couldn't wait!
I was unable to shake the feeling I might have just had a bad download of MiNCO, so I grabbed a fresh copy before I began. Flashed the ROM, Gallery worked fine. Flashed a navbar/battery icon mod, Gallery still ok. Gapps, no problem. Inverted apps, smooth sailing!
I now have a fully functional, customised ROM and no storage problem whatsoever. I must've just borked the first MiNCO download...
All's well that ends well
And I successfully tricked you into making your 10th post, so my work here is done! :laugh:
Now come join us in the main thread :good:
osm0sis said:
And I successfully tricked you into making your 10th post, so my work here is done! :laugh:
Now come join us in the main thread :good:
Click to expand...
Click to collapse
Nice one! :highfive:
I started one for g4 plus now for g5 plus .
Cosmic os 2.1 unofficial
Elemental x kernel over clocked
What benchmark program are you using?
username8611 said:
What benchmark program are you using?
Click to expand...
Click to collapse
Antutu
PureNexus using ElementalX stock CPU speeds and GPU governor, CFQ, custom CPU governor settings
Lineage OMS with ElementalX kernel stock CPU speed and governor. ZEN with custom readahead.
This is kind of useless, benchmark comparison means nothing if it is not on the same device with same set of apps installed.
Sent from my LG G5 using XDA Labs
suhridkhan said:
This is kind of useless, benchmark comparison means nothing if it is not on the same device with same set of apps installed.
Sent from my LG G5 using XDA Labs
Click to expand...
Click to collapse
That doesn't make any sense. Devices are manufactured to a certain tolerance and winning the "silicon lottery" doesn't make a device faster, it makes it more overclockable. Device to device, stock for stock, the difference should be at most a few thousand points from each other. It should be pretty obvious to kill all background apps and processes before benchmarking so apps installed don't matter either. If Facebook is too important to kill for 10 minutes then that person shouldn't worry about benchmarking.
Device to device are obviously going to vary. But a varience of 10k+ points is a pretty good indicator of one set up running slightly better than the other and it's interesting to compare what is the most optimized settings. I can play with my CPU governor all day and get repeatable results +/- 500 - 1000 points. Both me and my wife had a Nexus 5 and with identical settings we both benchmarked very similar. To say it is a useless test is ignorant. If people look at this as a pissing match to see who's "better" then yeah, I see this being a dumb and useless thread. But I think most people who do this want to know what settings, ROM, and kernel are best optimized for performance.
Edit: https://www.phonearena.com/phones/Motorola-Moto-G5-Plus_id10398/benchmarks
63,191
https://www.youtube.com/watch?v=345eKlssdH8
62,769
http://www.fonearena.com/blog/214719/moto-g5-plus-review.html
62,893
https://www.pcmag.com/review/352573/motorola-moto-g5-plus
63,845
http://www.guidingtech.com/65986/moto-g5-plus-vs-redmi-note-4/
62,896
5 different devices, all tested stock within right around 1,000 points of each other.
username8611 said:
That doesn't make any sense. Devices are manufactured to a certain tolerance and winning the "silicon lottery" doesn't make a device faster, it makes it more overclockable. Device to device, stock for stock, the difference should be at most a few thousand points from each other. It should be pretty obvious to kill all background apps and processes before benchmarking so apps installed don't matter either. If Facebook is too important to kill for 10 minutes then that person shouldn't worry about benchmarking.
Device to device are obviously going to vary. But a varience of 10k+ points is a pretty good indicator of one set up running slightly better than the other and it's interesting to compare what is the most optimized settings. I can play with my CPU governor all day and get repeatable results +/- 500 - 1000 points. Both me and my wife had a Nexus 5 and with identical settings we both benchmarked very similar. To say it is a useless test is ignorant. If people look at this as a pissing match to see who's "better" then yeah, I see this being a dumb and useless thread. But I think most people who do this want to know what settings, ROM, and kernel are best optimized for performance.
Edit: https://www.phonearena.com/phones/Motorola-Moto-G5-Plus_id10398/benchmarks
63,191
https://www.youtube.com/watch?v=345eKlssdH8
62,769
http://www.fonearena.com/blog/214719/moto-g5-plus-review.html
62,893
https://www.pcmag.com/review/352573/motorola-moto-g5-plus
63,845
http://www.guidingtech.com/65986/moto-g5-plus-vs-redmi-note-4/
62,896
5 different devices, all tested stock within right around 1,000 points of each other.
Click to expand...
Click to collapse
Thank you for taking the time to write a long response. But, I believe you may have just proved my point. I believe the test results of different roms should be well within 'around 1,000 points of each other'. Unless-
a. the rom is very poorly optimized - score would be lower.
b. the kernel is overclocked - score could be slightly higher.
c. user error (lots of background apps).
suhridkhan said:
Thank you for taking the time to write a long response. But, I believe you may have just proved my point. I believe the test results of different roms should be well within 'around 1,000 points of each other'. Unless-
a. the rom is very poorly optimized - score would be lower.
b. the kernel is overclocked - score could be slightly higher.
c. user error (lots of background apps).
Click to expand...
Click to collapse
I really don't know how else to explain this to you. OP got a lower score than me, yet is overclocked. So it stands to reason that either "a. the rom is very poorly optimized - score would be lower" or "b. the kernel is overclocked - score could be slightly higher" or "c. user error (lots of background apps)" is the reason for it. But wait, the performance should be slightly higher for an overclock except that it isn't. That's the whole reason to benchmark. Another possibility is that since I've heard ElementalX is currently having overclock issues, it may be reverting to its nominal frequency, which I believe is 1.4Ghz. How would this person have known that if not for comparing benchmarks? According to you, they can't compare to stock benchmarks because it's a different set of apps installed and a different ROM and in fact can't compare it to anyone because it's a different device, albeit the same model.
Benchmarks show performance differences, regardless of whether or not they are large enough to even notice on a day to day basis. It shows technical differences and if you think technical differences mean jack squat, then why are you even commenting in this thread? It's the same theory when you throw a car on a dyno. You're going to notice small differences between each run, but when you have two of the same model cars with the same engine, and one consistently puts out 30HP more than the other, there's probably a reason for it.
To reiterate what I said in my first reply, for people who want to compare optimization between different ROMs, kernels, and technical settings such as CPU governors and schedulers, benchmarking is not useless. Not in this method of testing and not across identical devices with different software. The baseline or "stock vs stock" comparison shows that the benchmark is measuring with an adequate amount of accuracy and that multiple devices in stock form are performing equally before being modified. Just because it doesn't mean anything to you doesn't mean that it means nothing at all.
I did some research and things like backround apps running in airplane mode scripts like lightning blade. all these things make a difference. I was running kernel over clocked in interactive mode with lightning script. If I set to performance my score was significantly higher I was hoping this would give users a better way to set up and optimize their device not to compare roms running same device. Yes at first I thought about that then realized it wouldn't make a lot of sense. Im hoping some of u guys will hop on board and help test kernel roms and other mods so maybe we can get the best out of our device thanks guys.