[Galaxy S 4 General] mw86:
Was gone two days and the crud hits the fan. Little surprised it got this bad. Thanks for clearing this up. I am glad someone has put the foot down as its been getting worse and worse tone as thread has gone. This says it all! " This thread is not about who's is better or who knows more" thank you. The thread is to show benchmarks in its simplicity. Stock or modded the thread is for all GS4 benchmarks and discussion, discussion being the main thing and as Towle has put let's keep it civil and on topic.

Now to reply to the question I was asked.

---------- Post added at 05:57 PM ---------- Previous post was at 05:24 PM ----------

" Perseus kernel is setting 1.4ghz in antutu regardless of temp so i can't test my OC on that.??[/I][/B]ummm

w - t - HUH

? :confused: :eek: :confused: :eek:

what 1.4ghz Perseus? so the dev set it to 1.4 for antutu thats the weirdest thing i've ever heard. Doesn't make sense . why?"

I made an observation and a mistake. Over clock was only just added days ago. So since then I have been provided an answer as to the culprit. The appearance of what I posted was what actually a Touchwiz mechanism. Andrei has disabled throttle boost by default now and allowed it back via a config file. Now default throttle is 100c and the default state before boost is enabled (boost mode is stock on the exynos from Samsung themselves as in its built into stock rom gt i9500) is 90c. Apples to apples comparison im not sure on stock S600 throttle but on gs3 qualcomm it was low 55c :0. Now s600 gs4 custom kernel as KT kernel Ktoonsez provides custom throttle options he and his test bunnies put together from his Nexus10 kernel. Point being I have noticed the exynos has a default substantially high throttle temp. If GS4 s600 users want to try a similarly high throttle they will need a custom kernel. Users would need to see where throttle keeps mhz stable, as you raise heat the same mhz can require more voltage than stock. Getting back to why I on what I had stated previously of Antutu on perseus kernel is the new setup which modifies and locks Samsung boost mode by default when enabled still is effected when cpu in Antutu hits throttle it doesn't return to mhz as in all other apps now and stays on 1.4ghz and is due to in System/apps/TWdvfsapp. This app is tied to power systems and Antutu has code in it to set max mhz you can read changelog causing the problem where the app twdvfsapp and antutu together not having normal mhz set the cpu stays in throttle mhz because the proper way for it to work is the min mhz must be lower than that mhz 1400mhz and since it is not it stays on that till you either have no more load on and have exited the app. It is a throttle bug by having this custom kernel set up this way. It is not bad it is better Andrei Lux has set the throttle as is because really the 90c is much more realistic safe temp to start the throttle. 100c+ is asking to melt some silicon or Samsung plastic phone....

" Ok so those high scores you got de-stabilise after a few tests in a row... but your 1.7ghz so far is the highest you can go being stable on benchmark and you estimate it equivalent to my 2.1ghz Stable clocks for day/day + benchmarking? I seee "

No with more testing i have 1.9ghz in quadrant, geekbench, chainfire, passmark, rgbench, stability test and some more. It needs more than stock volts on the 1800-1900mhz for it to be stable run after run with heat. I did 30 quadrant yesterday at 1.9ghz and no crash with raised volt. I was playing woth the boost throttle and the lower and many volts the first day or so and had little experience on the setup to be commenting on stability yet. I can run 1.9ghz all day for daily tasks and i have to push throttle temp on boost and stability tests and bench at 100c+ tp see instabilities. Personally 1.8ghz seems stable on everything now.

I can disable twdvfsapp but i had to restore it as it causes inefficient sporadic throttling into a7 cores for no reason so i had to go back. I will get a bench for antutu eventually but will need to be messed with to do just the antutu run as the fix for antutu makes it not run right for all else. I hit 1.8ghz consistently crash free on antutu test and stability test of antutu and stability test app as well as chainfire geekbench etc. I have a lot of adjusting and observing to do to know where the sweet spot is but at this point 1.8ghz with a proper volt table matching the jumps lower voltages use it has been stable 100% for me in everything. See 1.8-2.0ghz has all same voltages on the stock table and they each need to be higher like all the other mhz go in steps. I can pop around the UI at 2.0ghz and doesn't crash on single core loads loading apps up but a bench crashes immediately. So 2.0ghz is operable highest and is the mhz which is not stable. Below that I am seeing full use. On my daily stable setup 1.9ghz i am getting consistent 15k runs with 16k every few. Many many just under my highest. Consistent 50-52k cpu runs and mem used to be 10k max and gets to 11k now on OC. 1.6ghz 44-45k cpu went to 50-52 @ 1.9/1.8ghz. Lowest runs now are 15k run after run.

Ill post more benches as I have time to do them but I only got a chainfire done other than what I posted been just observing it's handling mostly.