yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] simms22:
set your high and low cpu speeds to be the same, 1512mhz high/1512mhz low. if you let it scale, you dont actially know what cpu speed it decides to test.

---------- Post added at 09:55 AM ---------- Previous post was at 09:52 AM ----------

yup, trinity default is 1026mhz. but its 1026mhz is as fast as many 1512mhz kernels. and its good on battery. you can always raise the cpu speed higher if you want.
[Nexus 4 General] yabbandroid:
Thank you, simms22. Yes Trinity Kernel seems pretty amazing. Like I said, I got with the standard underclocked Trinity Kernel better results than on stock or on Franco. But you are right I guess for those benchmarks to be sure you should always set the CPU fixed so you know what it's running at, I didn't do that. But I'm happy now with trinity. Maybe I will set it to 1500Mhz just to run an antutu :) Should be fast. :cyclops:
[Nexus 4 General] meangreenie:
I'll update to 4.3 later today and let you know how it goes. I'm surprised no one has given it a try yet.. probably all trying to get used to 4.3
[Nexus 4 General] kszaq:
I am getting some nice CF-Bench and Quadrant improvements thanks to STE's dalvik patches. It's also good to see that CyanogenMod Team has already included them for the upcoming CM 10.2. :)

I'm trying to merge libm patches at the moment to boost AnTuTu floating point score right now, wish me luck.
[Nexus 4 General] sicto:
Ok guys, I wanted just to share this video, showing results on AnTutu benchmark on Google Nexus 4 running stock 4.3.

It's not mine, but sorry for bad camera and sound

http://www.youtube.com/watch?v=jMUOIiBkSPM
[Nexus 4 General] kszaq:
I managed to merge additional bionic patches that boost AnTuTu score for 4.3. Please find the libs attached - simply flash the zip over Android 4.3 in recovery, no wiping needed.

The differences between stock and this are:

cherry-picked all STE dalvik patches from AOSP Gerrit,

added Krait-optimized memcpy and memmove routines in bionic,

added optimized sqrt and pow in bionic,

compiled with mcpu=cortex-a7 flag to make use of hardware division instructions.

Here's before and after comparison for the sqrt and pow patches:

I'm quite convinced that without thermal throttling it can score even higher.
[Nexus 4 General] Ace42:
If you can do this fairly quick, then I wonder what stops a single worker from adding this into official ROMs?
[Nexus 4 General] kszaq:
Firstly, what I did is an ugly patch that makes the code not compile for other targets - I simply needed it to work for mako and did not care about how it conforms to the standardsor whether it compiles for any other device. :angel:

Secondly, it is not that simple. The code that goes into official ROMs needs to be tested thoroughly to make sure it gives performance improvements and does not cause any regressions or bugs - it's quite a long process to do this. The kind of patches that I merged are submitted by companies working on their "forks" of Android and they need to submit those to AOSP code review.

As for dalvik patches, they are already submitted for review and are waiting to be tested and merged - I think that Google simply didn't want to merge something that might cause some serious bugs to release code.

As for bionic patches, it's up to Qualcomm (or Code Aurora Forum) to make them work with Android 4.3 code and submit to AOSP. They have been asked to do so about a month ago (see here) but I think they wanted to have release code for Android 4.3 and then produce and submit patches.
[Nexus 4 General] Yusei:
4.2.2
[Nexus 4 General] meangreenie:
Antutu on 4.3 with kszaq patch :good::good:

also i got just over 6000 in quadrant, a bit of a drop from 9200 :D but a nice boost still.
[Nexus 4 General] Knoxode:
RE: Nexus 4 Benchmark Thread

Here is mine with paranoid android 3.69 + trinity kernel
[Nexus 4 General] simms22:
The Nexus 4 as a dual core..

Trinity kernel compiled with the cores capped at 2, with ctfrommns' Rasbean(4.2.2 still), at 1836mhz of course.
[Nexus 4 General] kszaq:
I think there is a derp in dalvik code that is present since 4.2 that make our scores for Java-based benchmarks look like it was a dual-core device. You can find people complaining about lower Quadrant scores on the forums. I also guess that OEMs somehow worked it around so that Quadrant and CF-Bench Java scores are way higher for devices running stock ROMs (except for Nexuses, of course).

Could you possibly post a comparison for 2, 3 and 4 cores enabled?
[Nexus 4 General] simms22:
all my other posts are 4 cores(8550-8700). ill do 3 cores. but im still on 4.2.2, not 4.3(in case you think its 4.3).
[Nexus 4 General] kszaq:
Yeah, I can see that looking at your screenshots - there is no customizable 4.3 ROM yet. :) Thanks in advance for testing!

I just did a quick look at top -m 20 -d 1 -s cpu -t while running CF-Bench and I noticed that it is running 4 threads but they are always distributed between 3 cores only:

PID TID PR CPU% S VSS RSS PCY UID Thread Proc
20150 21770 1 24% R 883144K 37736K fg u0_a78 Thread-495 eu.chainfire.cfbench
20150 21768 3 22% R 883144K 37736K fg u0_a78 Thread-493 eu.chainfire.cfbench
20150 21769 2 21% R 883144K 37736K fg u0_a78 Thread-494 eu.chainfire.cfbench
20150 21767 2 20% R 883144K 37736K fg u0_a78 Thread-492 eu.chainfire.cfbench

Project Butter probably leaving one core left for the UI?
[Nexus 4 General] simms22:
no can do 3 cores at the moment, sorry. this test version locks me into 2 cores at all times, and cant edit manually. next version kernel i can enable only 3, ill post it.

thats just how its reading our core i think. we have core 0, 1, 2, and 3. 0 is our main core. 1,2, and 3 get turned on and off. i could be wrong, but i think im right.
[Nexus 4 General] kszaq:
Yes, I'm aware of how cores are numbered. The point is that benchmarks threads are running on 3 cores only. That is: CPU 0-1-2, 0-2-3 or 1-2-3. I have never seen these threads run on cores 0-1-2-3 at the same time.
[Nexus 4 General] PeITeeR:
cm10.1.2+francoM3
[Nexus 4 General] manpildo:
Quadrant: 5558

Antutu: 16725

Running Carbon ROM with its default kernel and settings.
[Nexus 4 General] kszaq:
Great news! Developers from Code Aurora have already amended their bionic patches and everyone can use them right now for Android 4.3 builds: https://www.codeaurora.org/cgit/quic/la/platform/bionic/diff/?h=jb_mr2

Also, the patches have already been merged into CM 10.2 bionic. :)
[Nexus 4 General] tiru.adi13:
Will this work for custom kernels Luke faux's one? Or only the stock 4.3 kernel?

Sent from my Nexus 4
[Nexus 4 General] Ümit:
Without OC?
[Nexus 4 General] chrisjcks:
Stock 4.3

Stock kernel

& this was the very first benchmark!

Our GPU performance is a beast!
[Nexus 4 General] cobyman7035:
I ran geekbench2... Got like 2333

Via my NeXus⁴ using Tapatalk² app
[Nexus 4 General] kszaq:
Yes, it will. In this case kernel doesn't matter at all. By the way: all these patches will be used in upcoming CM 10.2 and probably all other custom ROMs, so this applies only to stock ROM.
[Nexus 4 General] Dark Fear:
haven't these optimizations already added in 4.3 custom kernels?
[Nexus 4 General] meangreenie:
These optimisations can't be done on the kernel, they are rom side improved code.

[MENTION=3905077]kszaq[/MENTION] Are you going to do a 9505 dalvik mod for 4.3 too? Your 4.2.2 one made the stock launcher feel like TSF shell!
[Nexus 4 General] Dark Fear:
well.. what about 4.3 custom roms? any of them has these?
[Nexus 4 General] sicto:
http://www.youtube.com/watch?v=95O8C8NGp5k - Antutu, weird score, don't know why

http://www.youtube.com/watch?v=q5E5PdyHdXo - Quadrant, not really good

http://www.youtube.com/watch?v=akNLFOUqAFQ - Geekbench 2
[Nexus 4 General] clocinnorcal:
Performing nicely on 4.3 so far. I have also noticed an increase in battery life with 4.3
[Nexus 4 General] kszaq:
We will have to wait for official 4.3 ROM for S4 or HTC One. At the moment the binary included in the leaked S4 ROM showing lower Dalvik Virtual Machine version than is needed (27 vs. 28) and it makes Nexus 4.3 ROMs not to boot. Or there's a second option: Qualcomm decides to share headers for their proprietary optimization binaries and we can compile Dalvik library linking to it. But this most likely won't happen.

Please read my post two posts above yours. ;)
[Nexus 4 General] Dark Fear:
well.. that wasn't my point.. i mean is there any of these available custom roms, including these optimizations by itself ? or we have to apply it in every rom?

second question.. hasn't it bad effect on battery life?

tnx :fingers-crossed:
[Nexus 4 General] kszaq:
As far as I know there is only one custom 4.3 ROM available at the moment: CM 10.2. The CM Team has merged some bionic and all dalvik patches I posted earlier. I think more or them will be merged very soon (probably even before the first official nightly pops out). As most custom ROMs will be probably forking/using CM's bionic, there won't be a need to apply them.
[Nexus 4 General] Raiden350:
About benchmark on Android 4.3, my Antutu score descended from 3k points (21k > 18k) ::(

I'm waiting for franco kernel r17x zip file, anyone know when we can get it ?
[Nexus 4 General] kszaq:
[MENTION=4531983]meangreenie[/MENTION]: Stupid me! It turns out that libraries from leaked S4 4.3 ROM actually do work on Nexus 4 4.3, I just forgot to include an updated dexopt binary! The thing I said about Dalvik VM version: AOSP uses version 27 and leaked S4 uses 28, so it's actually higher.

I'm attaching a flashable ZIP for you and also a revert ZIP with stock libs in case something goes wrong. Tested on self-built CM10.2 and should work with any 4.3 ROM! Make sure to wipe your dalvik cache after flashing.

Don't use it on odexed ROMs.
[Nexus 4 General] tuilalnvinh:
So, i'm on JSS aosp build, it is safe to try your patch, isnt it ? :D
[Nexus 4 General] kszaq:
Yup, should be safe on both JWR and JSS builds.
[Nexus 4 General] eddiecho59:
I'm on stock image clean flashed and rooted 4.3 jwr build but it seems doesn't boot after flash it. Aurora on X mark keeps moving but it didn't stuck like bootloop. Any suggestions?
[Nexus 4 General] kszaq:
I guess there might be a problem if you use odexed ROM. Please flash the revert ZIP to make it boot and try flashing deodexed ROM. Sorry for that.
[Nexus 4 General] meangreenie:
Yeah, didn't work for me either on stock odexed too.

Downloading deodexed to try.

Edit..... [MENTION=3905077]kszaq[/MENTION], confirmed working with deodexed :) , will run some benches now

---------- Post added at 12:03 PM ---------- Previous post was at 11:06 AM ----------

Quadrant on stock official 4.3 deodexed with new kszaq patch and thracemerin alpha 3 kernel running stock 1.51mhz cpu

First run...

http://imgur.com/0HfhMHW

Score was.. 7897!!!
[Nexus 4 General] sicto:
Help

http://www.youtube.com/watch?v=95O8C8NGp5k

How to get better score on stock 4,3 ?

Why is about 14000 ? On 4.2.2 it was better ?
[Nexus 4 General] IRX120:
Is there a way to.make it work on an odex rom?

Sent from my Nexus 4 TMO @1.728 GHz on Stock 4.3.0
[Nexus 4 General] Nikitozin:
View attachment 2153134 View attachment 2153135

Here it is, my results with Jarjar AOSP Build (JSS15J) JB 4.3 .

The only thing i used was Greenify to close and hibernate all apps before doing the Benchmark test :)

EDIT: Here the Benchmark with Kszaq Patch .

View attachment 2153132 View attachment 2153133
[Nexus 4 General] chrisjcks:
I hope the mods well allow this.

(I didn't start a new thread with this, but feel it's interesting to all android manufacturers and users who are interested in benchmarking our phones)

Samsung found to be cheating in benchmarks:

http://www.anandtech.com/show/7187/looking-at-cpugpu-benchmark-optimizations-galaxy-s-4

Disgusting. (Think we all expected this on some level, but not as much as this....)

Enjoy.
[Nexus 4 General] kszaq:
No, sorry.

Let me explain why: when the ROM is built and odexed during compilation (just like the stock ROM is), a dexopt binary is used to odex framework system apps. This binary is compiled from Dalvik Virtual Machine sources and it is of the same version as Dalvik Virtual Machine library libdvm.so and dexopt binary that are included in the ROM (dexopt is being used every time you install a new app to create an optimized classes.dex). When the version of the Dalvik library changes, every apk/jar needs to be re-optimized - this is being done when "Android is upgrading" dialog is shown every time you upgrade your ROM (or clean Dalvik Cache). If the ROM you are using is deodexed, every system apk and framework jar files contain a non-optimized classes.dex file, which is optimized (odexed) during first boot and put into Dalvik Cache. So when you change the version or code of the Dalvik Virtual Machine library, the Dalvik Cache can be cleared and optimized classes.dexs are generated.

When system apps had been pre-optimized (odexed ROM) and the version of Dalvik Virtual Machine changed, Android won't boot because it can't re-optimize them and won't let them start because of purportedly different Dalvik Virtual Machine behaviour in the newer version.

Now, as I mentioned before, the libs from S4 ROM report Dalvik Virtual Machine version 1.6.0.28, whereas AOSP is 1.6.0.27. This is why you need to use an deodexed ROM.

Hope it's clear enough. :)
[Nexus 4 General] IRX120:
Thanks, so if both versions of dalvik were 1.6.0.28 then it would work on odexed? Correct

Sent from my Nexus 4 TMO @1.728 GHz on Stock 4.3.0
[Nexus 4 General] kszaq:
Correct. We can change that in a hex editor and force it to work, but I won't recommend doing that - the devs from Qualcomm must have changed the DVM version for a reason.
[Nexus 4 General] -JFK-:
Hello,

I know that Quadrant is not the best one but one of my biggest score !

SiMaRom + Bricked Kernel [MENTION=4149147]1.8[/MENTION]Ghz

Edit : New score [MENTION=1811927]simms22[/MENTION], it's 4.3 JSS
[Nexus 4 General] simms22:
4.2.2 or 4.3?
[Nexus 4 General] -JFK-:
4.3, I have edit my previous post with a new score
[Nexus 4 General] Ace42:
What did you do to the colors...They seem sorta whacky in that shot.
[Nexus 4 General] raze599:
No this phone definitely features a quad core processor.
[Nexus 4 General] wurzelsepp3:
http://www.glbenchmark.com/phonedet...4&testgroup=overall&benchmark=glpro25&var=top

looks comparable to what the Optimus G scores.
[Nexus 4 General] Nooby Arc S User:
I bet your Arc S would score higher on CM10..... I did a Antutu on my Arc S running Cm10 and I got 5309.
[Nexus 4 General] ocula:
Geekbench scores are what I would expect

Quoted from TechCrunch:

"It should go without saying that Quadrant scores are far from a perfect metric, but I suspect the Nexus 4’s abnormally low showing has more to do with software than it does with bum components. The device’s Geekbench performance seems to stand as proof of that — the Nexus 4 scored 1961, handily beating its cousin the Optimus G."

And a comparison graph of various smartphone Geekbench scores:

ubergizmo.com/2012/11/google-nexus-4-review/google-nexus-4-geekbench/

So it seems to me that right now the low benchmark scores are mostly caused by software issues, and not hardware ones. But I'm still not sure why Geekbench is one of the only benchmarks where the Nexus 4's score is comparable to the Optimus G's..
[Nexus 4 General] Ace42:
I wonder how far you can overclock the CPUs, imagine running quads at 2.xGHz on this thing!
[Nexus 4 General] XSJoJo:
Not sure what AnandTech tested, but Nexus 4 beats Optimus G in both on and offscreen GLBenchmark 2.5 Egypt HD C24Z16:

http://www.glbenchmark.com/compare....certified_only=1&D1=Google Nexus 4&D2=LG E973

Also, this page reveals that AnandTech uploaded two much better runs, but didn't take that into account in their review?

http://www.glbenchmark.com/subtest_results_of_device.jsp?D=Google+Nexus+4&id=448&benchmark=glpro25

Interesting.
[Nexus 4 General] theoneofgod:
Why would Google push "test" phones with such poor performance?

Do they want bad reviews, then those bad reviews to be updated saying it's now good? Makes no sense.
[Nexus 4 General] The_Double:
being "not optimized" (wtf would be a optimized benchmark?) doesn't have such a big effect on the scores. Especially when every test confirms that the phone isn't as fast as it should be. There is either a problem with throttling, slow RAM, or bad motherboard design. Or the Review units might be in debug mode, meaning that they are constantly pushing debug data, but even that shouldn't make it this much slower than what it should be.
[Nexus 4 General] InvalidUsername:
I have never seen a thread with more lame Android fanboys than this one. Yes, we understand that this is not release hardware, HOWEVER, these issues are MORE LIKELY to be due to THERMAL THROTTLING than a kernel issue, since 4.2 is only a minor update (and in fact, most of the new features are in the apps and not the OS). Thermal throttling is a HARDWARE issue, and is therefore impossible to fix with a software update.

With that said, I still intend to buy this device, but please don't come into this thread acting like you know absolutely everything there is to know about everything and claim that everything is fine. People writing comments like "OMG GUYS, IT'S JUST PRE-RELEASE SOFTWARE AHAHA NO BIG DEAL LOL TEHEHEHE" can shut up and move to a different thread where they talk about their ridiculous love of Google. A lot of us are here, because we want a good device, and not to be delusional Google lovers.

Exactly what he just said...
[Nexus 4 General] Nbsss:
Amen bro

Sent from my Ipad Mini
[Nexus 4 General] Venekor:
It makes no sense though as the LG Optimus G didn't suffer from these issues, why would they design the exact same phone again with thermal issues? I mean it's not out of the question but it would take a complete idiot. I mean maybe LG didn't want it to make the Optimus G pointless so designed it worse? lol.

It would make much more sense for there to be a major software flaw but again it makes no sense for it to be so bad in what is barely any different from 4.1. Also why is the exact same battery on the same hardware performing much worse if the hardware is throttled?

No one knows, we'll just have to see.
[Nexus 4 General] Mael5trom:
I would think all the evidence points to a software issue, there's at least 4 good reasons for this assumption.

1. Some benchmarks are extremely good. (geekbench)

2. Performance on benchmarks is very inconsistent but the best runs are consistent or above optimus g.

3. Many of the phones are running different pre-release firmware.

4. Battery performance is heavily affected by bad software and many reviews have pointed out bad battery performance, whilst others have been very promising.

There's way too much inconsistency at this time to draw any valid conclusions, but I think performance looks promising despite this at this time.
[Nexus 4 General] wurzelsepp3:
Actually the Optimus G also seems to have the Overheating issue, I read an Optimus G review yesterdah talking about the device thermal throtteling under high (graphics) load.

Let me also quote Anandtech:

Despite of what other members are saying, I do believe that this problem can be adressed by a software update, the is always the possibility to tune voltages or even reduce clockspeeds a bit.
[Nexus 4 General] jader13254:
+1 haha i just watched a benchmark video optimus g beating s3 and hox and thought: haha he is a Genius... Bad motherboard design... Its based on optimus g, which doesnt have this issue (but other issues) so its definitely a software issue or an kernel prob..

Wait for release and check if Lg sucks again as well as qualcomm
[Nexus 4 General] draugaz:
Oh, there are a lot of of things could directly influence benchmark results, but not the "real" performance.

For example, where does the benchmark take its reference time from? Is the source granular enough? What about linux cpu time scheduler? Linux has several different of them. Which one is active?

What about those "project butter" enhancements? Anyone with experience in multitasking systems knows, that tuning for raw performance (i.e. benchmarks) is not the same as tuning for responsiveness (perceived "performance" by the user).

How was that android 4.2 configured? Were there any new tweaks? What about power management? When does it kick in?

An "optimized" benchmark is the one where such things are taken into consideration.

If you measure CPU integer performance, you don't want some power management automagic kicking in.

Or getting just 10% of CPU time only because OS thinks you are just some unimportant background thread programmed by an not very bright developer who does not know what he is doing (which sadly are very common).

An so on.

---------- Post added at 12:05 PM ---------- Previous post was at 12:00 PM ----------

Of course, no one knows. And that 4.1->4.2 upgrade is not necessary a minor thing. They did not change the optics and functionality, but this does not mean the underlying code remained the same. Even small changes in underlying OS or drivers or their configuration can have huge consequences.
[Nexus 4 General] FISKER_Q:
So basically what they're saying is that they have deceived us in the LG Optimus G tests? Oh ok, great argument from Anandtech :)
[Nexus 4 General] stubborn_d0nkey:
I would really like to see real life uses used in benchmarking, however, I do know that there are not many uses that can properly be used for benchmarking, especially when it comes to (just) the cpu. Though one that is perfect for it (albeit not commonly used) does come to mind; chess engines. Chess engines are cpu heavy, (usually) multihread and already have a metric for benchmarking (nodes per second). I do, of course, realize that they are not commonly used but I cant really think of any other real life use that is as optimized for benchmarking, and I think any real life use is better than none
[Nexus 4 General] hamdir:
thermal issues can definitely be improved by kernel

the original firmware for the Tegra 3 one x was a mess with the device heating to screen damaging effect

with the subsequent OTAs it got a lot a better to a point were heat stopped being an issue and its rock stable

however the One X' Tegra 3 throttles down 200mhz on the CPU and the GPU is rarely affected

but the highly awaited GPU scaling down so severely with heat is surely worrying for now
[Nexus 4 General] yeti101:
Beast chip but can't run flat out for any length of time. Definitely waiting to see if this is fixed

padfone 2 using the same chip destroys everything in quadrant - scores 7500
[Nexus 4 General] yahyoh:
thread updated :)
[Nexus 4 General] simms22:
your lucky that we only started seriously testing trinity 4.3 today, and that we are only using 1512mhz for the time being. but.. im not very far away, at 1512mhz ;)

---------- Post added at 04:39 AM ---------- Previous post was at 04:37 AM ----------

it happens.

sometimes quadrant fears fast cpus, and shows it :silly:
[Nexus 4 General] -JFK-:
I'm waiting Trinity !!!

For now, I need something to play with, so I test all that I can.

It's the first Quadran 9K break ?

Yes, the colors are very strange on that run... I have not touch it.
[Nexus 4 General] simms22:
after the first day of trinity 4.3 testing, this is at 1512mhz.. 3DMark ice storm and ice storm extreme, and a quadrant.
[Nexus 4 General] FuPete:
Latest CM10.1 nightly (barebone), using Anarkias Kernel.

GPU at 487mhz On Demand governor, CPU at 1,836ghz.
[Nexus 4 General] -JFK-:
Same config + some tweeks.
[Nexus 4 General] meangreenie:
No, I got 9200 with kszaq's 4.2.2 ROM using trinity tf133 clocked at 1.78 a few pages back.

[MENTION=1007992]everyone[/MENTION] antutu 3.4 is updated with opengl3.0 which gives more realistic lower 3d scores.

Also @ everyone, 215 downloads of kszaq's patch but only 9 thanks? .. bit tough?
[Nexus 4 General] Ace42:
I wouldn't be surprised, not everyone is grateful. :(
[Nexus 4 General] sharky2013:
I find quadrant to be unreliable, antutu and 3D mark are far better IMO. I'm usually around or over 20,000 on antutu.

with PA and faux kernel tbm.