yashsingh1/xdaforums huggingface dataset:
[Nexus 5 General] jjhiza:
I'm going to ask this, and please don't get mad, but did you even Google what you're looking for? I did a quick Google search for "dalvik optimizations SGS4" and immediately got the result I was looking for...an Xda thread, discussing this same topic, for the S4... :what:
[Nexus 5 General] Chelonee:
Was curious and just flashed it on SGS4 version of newest Mahdi Rom. Works nicely! Everything feels smoother and faster, but could be imagination. :o
[Nexus 5 General] bblzd:
Correct me if I'm wrong but I believe all OEM devices already have their own optimizations included and installing this should not be necessary. Samsung, LG, HTC, Motorola all already have this it's only Nexus devices that are lacking.

Even the GPE version of the S4 and HTC One should not need this according to the Anandtech review.
[Nexus 5 General] Chelonee:
I'm not entirely sure either, but as far as I know, this is only true for stock (TouchWiz in case of samsung) roms or custom roms based on stock. I could be wrong though. The only thing I know for sure is, that the custom rom I'm currently using is based on AOSP Kitkat not TouchWiz. In late december the developer added the updated libarys from the Nexus 4 thread in his rom. So I thought I might give it a try and flash these newer files on top of it. :)

Could be that this was totally unneccessary, but the rom feels smoother and snappier since then. :cyclops:
[Nexus 5 General] Algotis:
Hey!

I am on full stock now! Is it possible to flash it by booting into fastboot and then booting into twrp by command?
[Nexus 5 General] :
I guess you'll need to flash a custom recovery since you are fully stock.
[Nexus 5 General] Algotis:
But i can boot into TWRP from the command prompt with the TWRP image, but do i need to have an unlocked bootloader?
[Nexus 5 General] LeoRex:
Well... fyi.... my 5 has been consistently scoring around 28k in antutu. I loaded the patch, 28k...

But not so fast, I noticed that the CPU had been dropped from 2265 down to 1728. It had been charging and felt a wee bit warm. So I set it aside and let it cool down.

When cooler, at 2265, I scored a 32, close to a 20% improvement.. must everything scored higher, with the biggest jump in the runtime score.. 50%.

So.... I am deciding on keeping the top at 2265 and keeping the speed, or dropping to 1728 and getting some battery savings...
[Nexus 5 General] xboxfanj:
Manufacturers do on their own stock ROMs, but AOSP (non stock ROMs) and Nexus do not.
[Nexus 5 General] bblzd:
Oh, so everyone flashing custom ROMs on their OEM devices could still use this. Thanks for clarifying. :good:
[Nexus 5 General] xboxfanj:
Custom being not stock based. Ex: any sense ROM already has these, as does any touchwiz, xperia, etc on Qualcomm hardware.
[Nexus 5 General] LeoRex:
Correct... I ripped the guts out of my 5 the day I got it... Currently, it's loaded with one of the unofficial PA 4.0 B3 builds.

Frankly, I'm glad I did it... Going off the Antutu score... it improved by 20%... and the sub-scores showed improvement across the board. It was a little bit of luck that Antutu thermally throttled my cpu after I patched, since that showed me that I could drop the max speed down considerably (18% less) and still perform the same as it had been without the patch. I'll have to see, but dropping from 2265 to 1728 HAS to lead to an improvement in the battery consumption.

But I'm still pretty pleased... with the optimized cache, this leaves the other phones in it's weight class (HTC One, S4) and moves on up to the processing big boys of the phone world (like the Note 3). Makes sense, considering the processor they packed in this thing. And that's with a kernel (franco) geared more towards battery life and not performance. I might throw on one of the speed kernels to see what the top speed on mine actually is.

All the reviews I've read where they wonder why the N5 wasn't scoring as high as devices with the same chip, they all make sense now.... Google just never optimized things. I wonder why that's the case. Maybe these optimizations don't jive with the Nexus philosophy or something. I don't know. But I do know that with the optimization in place, I'm seeing scores equivalent to similarly decked out phones, but for a fraction of the price.

This is one hell of a phone.
[Nexus 5 General] Enddo:
not as much as you would think. there's only 100mV difference between those two frequencies. you can get apps to watch how much of your usage is actually at the max frequency. so it all depends on usage, most phones sit in deep sleep or at 300MHz unless doing active tasks. i think stock touch boost is 1.2GHz, maybe 1.6GHz

you would probably see a little difference in heat generation though. so while your device is being pushed to the limits, it will not run as hot since it's 100mV less
[Nexus 5 General] aavvaallooss:
1.6 GHz in my case according to System Monitor
[Nexus 5 General] Lownita:
Is this on par with ART in day to day usage?
[Nexus 5 General] jwee5467:
I've found it on par and sometimes smoother. Also there are some apps that still don't play nice with art.
[Nexus 5 General] Enddo:
scrolling, recent apps button, and switching between open apps is still faster on ART in my opinion
[Nexus 5 General] ChazzMatt:
Yeah, but need Dalvik for Exposed/Gravity.

_______

Sent from my Nexus 5 (LG-D820)
[Nexus 5 General] ScumDroid:
Yes it will work i did it, but you have to unlock the bootloader to fastboot boot .img :good:
[Nexus 5 General] P3nkiln:
Hi, I've been clean flashing roms for the last couple weeks trying out all the main contenders and flashing these files as well. I'm definitely finding it makes a real world difference. Much smother.
[Nexus 5 General] Enddo:
because the N5 isn't smooth without it? ;)
[Nexus 5 General] :
Hi,

From the Nexus 4 thread:

I know you are working on it, but just to test I used the Dalvik files from the HTC One Google Play Edition (.lib and bin files):

dalvikvm
dexopt
libcutils.so
libdvm.so
libqc-opt.so

For the "installd" .bin file I kept he one here.

The phone boots, no issues but I haven't noticed any improvements (and benches are about the same) compared to the ones here.

It was just for testing since you were speaking about new libs from the HTC One GPE... :D

:)
[Nexus 5 General] gpvecchi:
Could you please post your version? Thanks!
[Nexus 5 General] :
Hi,

The HTC One Dalvik files?

Yes I think it's what you mean (I'm tired) :D

Here in attachment, I tested on AOSP based rom, like the others files here it should work on stock rom and CM roms too (since I kept the "installd" file), Nandroid backup first just in case ;)

Wipe Dalvik cache then flash the zip file.

:)
[Nexus 5 General] gpvecchi:
Thanks, I'll try later!
[Nexus 5 General] cellsafemode:
Been following this for a while. Seems that every few pages testers contradict previous conclusions. On stock ROM, do these files make a measurable difference with no other changes or do they not? If so, why so few actual numbers? There are native only and dalvik only tests on play store to illustrate the changes if any exist.
[Nexus 5 General] :
Hi,

As you see some contradictions on each pages of this thread, the better in my opinion, is to test by yourself to make your own conclusions...

Try both Dalvik and Bionic patches (or maybe separately if you prefer) to see if for you there is an improvement in day to day use, in general UI...

For sure in benches there is an improvement...

If you follow the thread I think you should see this post: http://xdaforums.com/showpost.php?p=49449807&postcount=613, it's the general idea... Each users have their own perceptions of the improvement or not in general UI and maybe you will have a different too, so as I said to have a real opinion the best is to test yourself. Because asking again if there is an improvement or not and if it's only in benches or not and there will be again 10 pages when everything has already been said about it... some users don't see anything, some users see something and for others... they don't know (I speak here in general use, UI, not in benches).

For me it's the advice I can give you, to test by yourself and see, the reply is in your question ;)

:)
[Nexus 5 General] cellsafemode:
Optimization isn't a perception. Either the code was improved or the device already has the same or similar improvements stock. What changes is whether the user is testing the particular cases the improvements are made use of. That is why I was wondering why nobody has been doing in depth testing rather than opinions or just overall benchmarks.

I'll run some in depth ones, but I'm in art land and don't care at all about improvements to dalvik specifically.
[Nexus 5 General] :
For some users it's the case, some improvements can be perceptible or not in my opinion. What kind of tests do you want to see? Benches are a part of the results to see the improvement, at least for me...

For me it's the same thing with a custom kernel, how you measure exactly or for real the improvement or not other than with benches for "raw power" (or "benches" about battery life), or with feedback from users like about smoothness or responsiveness, etc...?

Well, we can measure the time for the opening of an application (or xx applications) with and without, but honestly, me, I have not the time... And maybe we will see a difference in real measure, is that the user will really see it?

And even with some numbers (other than the ones in benches) there will always some people for saying something about it, or even if we gain 0,5 seconds to open X app, some users won't see anything (it's what I meant about perception).

In any case there is some videos on Youtube to see opening apps, switching apps, etc... with and without patches with two phones side by side (it can give an idea).

For sure if you are running ART runtime, the only benefit will be from the Bionic patches...

What can we say more, you say yourself that there is a lot of contradictions and you're asking again the statement about these patches, in short useless or useful. The replies will be again the same way like I said in my previous post.

After that, sorry, but I can't said more, at least for me ;)

If you run some depth tests, don't hesitate to provide an objective feedback or some real tests with real conclusions ;)

:)
[Nexus 5 General] cellsafemode:
Prior to installing patch. Typical run.. I ran the bench multiple times waiting to cool between runs. Green is native, blue is art/dalvik. Art for me. I had to take two shots for each run to get all tests. Numbers are in seconds and represent an average... First test is single core, then two core then 4 for each test
[Nexus 5 General] cellsafemode:
I then installed bionic only. Rebooted, let cool and ran the tests the same way
[Nexus 5 General] cellsafemode:
Then I reverted and after art rebuilt. Rebooted and let cool and reran the tests
[Nexus 5 General] cellsafemode:
As you can see, some (very few) tests improve with motox bionic. Many important ones get much worse like the memory test. The overall time increased significantly. The question then is will real use tilt more towards the operations yielding worse numbers or the few better... Unknown. But I would base a conclusion that it is very unlikely to improve user experience based on the horrible memory test results, which are more likely to impact general use than some of the specific algorithm tests.

Sum: bionic mod is a regression on stock ROM.

Edit: the numbers per test are cumulative... The total number at top of first shot is total time for the final 4 core run.
[Nexus 5 General] P3nkiln:
Always room for improvement :)

We'd be bored if there wasn't anything to optimise or modify.
[Nexus 5 General] :
Re,

Interesting and thanks, but I'm not at all familiar with this app bench but at least we see almost the same results for your different tests...

I use, like many others, Antutu, Quadrant and Cf-Bench (sometimes Linpack) and here you see the improvement in benches.

Take a look here: http://xdaforums.com/showthread.php?t=2506965, there is some benches with stock kernel/rom and the patches and you can see the improvement compared to stock kernel/rom without patches (even with ART runtime and Bionic patches).

See the last pages compared to the first pages (before the patches came here) and you'll see the difference in overall scores, in short Antutu it's about 28 000 vs 35 000 and Quadrant it's about 8000 vs 20 000, at stock CPU freqs, right with Dalvik runtime and both patches.

If I remember right you'll see also an improvement under ART runtime with the Bionic patches, there is some benches with and without Bionic running ART.

The part with improvement are in memory and CPU test. If you want to try with these bench apps with ART+Bionic and with Dalvik+Dalvik/Bionic patches...

Your results still based on benches... and your conclusion too, like I said or tried to explain in my previous posts... Or I didn't explain right my point of view.

And for you in day to day use, so in general UI, did you see a difference?

:)
[Nexus 5 General] cellsafemode:
You don't know what antutu and other large single number benchmarks are doing to get that number and what the tests involved use... Native or java. This benchmark has equivalent tests written for both and gives you the raw data... Not weighted scores with no transparency.

In any case, the difference in daily use would not be measurable because they are differences in code paths that are faster or slower by millionths of a second that only show up in benchmarks because those functions are called thousands of times as fast as possible.

Ie. The difference would be within the regular difference a user sees with no change to the system simply due to random hardware and android activities. Like opening app drawer one minute and opening it later taking slightly different amounts of time.
[Nexus 5 General] :
Is it really better than the others? I mean is it 100% more reliable/accurate than the others?

Right, never said the opposite...

Right but it's what I said in all my previous posts here (yes you need to keep in mind different situations and configurations)... whether I speak really bad either I don't know...

In short I said with a custom rom with Dalvik optimizations from AOSP and Bionic optimizations from Codeaurora you won't see a difference, with stock rom, maybe you will see a difference but not sure (plus maybe the placebo effect)...

In benches there is an improvement even with ART/Bionic, except for your benches....

The thing is, and maybe here is the difference, I speak mainly about Dalvik runtime with Dalvik/Bionic patches. Here we won't agree together since in fact we don't test exactly the same thing (even about the benches) :D

So maybe you're totally right :)

After to compare Dalvik vs ART runtime there is already two threads ;)

But to resume, it seems all the opposite of what you have said in your first two posts, just my opinion, you ask for advice, opinion or feedback not only in benches (nor about user experience LOL) then 10 minutes later all is clear for... But it's ok :good:

In any case thanks for your feedback.

:)
[Nexus 5 General] Lownita:
On Cataclysm Rom running dalvik, do I need to flash both dalvik and bionic patches? Also, do the revert .zips also revert bionic patch?

Thanks a lot!
[Nexus 5 General] :
Hi,

You can flash boths and test for see (at least with Dalvik runtime obviously the Dalvik patche is used)...

The revert zip restore boths Dalvik and Bionic. In any case you can make a Nandroid backup, maybe more convenient.

:)
[Nexus 5 General] Lownita:
Thanks, I just wasn't sure if cataclysm already has the bionic stuff baked in! I also might try just bionic with ART, lets see :)
[Nexus 5 General] :
Re,

It seems they are not included nor there is AOSP Dalvik optimizations or Bionic optimizations (but without sources)..., I just made a quick search but it seems these patches here at least are not included.

Run a bench with Cataclysm rom without the patches and see..., you will know :D

:)
[Nexus 5 General] blackdragoon:
Sorry for the noob question but is there a way to flash these without using a custom recovery?
[Nexus 5 General] Dungeon47:
Performed a similar experiment on my N5 running the latest OMNI nightly and Faux kernel.

Stock was 5.21

Dalvik Opt was 6.69

Bionic+Dalvik Opt was 11.92

TL;DR: bye bye, Bionic; jury out on Dalvik Opt.
[Nexus 5 General] Lownita:
So stock dalvik was even better than optimizied dalvik :confused:
[Nexus 5 General] Dungeon47:
I'm confused, too. I'll run more tests when I can.
[Nexus 5 General] aavvaallooss:
Flashify, maybe?
[Nexus 5 General] Lownita:
I don't know for sure, but I believe that flasify relies on either cwm or twrp to flash .zip files. Don't think that unsigned files could be flashed with stock recovery.
[Nexus 5 General] aavvaallooss:
Maybe you're right
[Nexus 5 General] atishey23:
Correct me if I'm wrong,

I have to flash "dalvik.zip" and "bionic.zip" when I'm running dalvik runtime?

And I have to flash only "bionic.zip" when I'm running ART runtime?
[Nexus 5 General] cellsafemode:
Stock ROM is optimized. It is obviously not optimized the same way as other manufacturers like Motorola, but it also is hardly aosp.... which gets no love.

So then the question at hand is which is optimized better, stock nexus 5 or moto x? From what I saw benchmarked, the motox optimizations don't play well with nexus 5 in some operations, and do marginally better in others but the negatives outnumber the positives.

In weighted benchmarks this will get skewed and perhaps rightly so. In reality they are probably so similar running that it would be impossible to tell the difference.

The main thing motox optimized was graphics and the bulk of that work is not in DVM or bionic... that and their custom hardware. Most of these companies fish for qcom opts in the same place everyone does... Code aurora.
[Nexus 5 General] aavvaallooss:
Correct
[Nexus 5 General] :
Hi,

You can flash both Dalvik and Bionic patches if you want, it's just that with ART runtime only the Bionic files will be used. Then if you decide to switch to Dalvik runtime again you have already the Dalvik files... :D

I tested and there is no bootloop or weird issues.

:)

EDIT: Some use a bench app to demonstrate that there is no improvement and others used other bench apps to demonstrate that there is an improvement... Even if it's not 100% reliable and accurate we're going round in circles... :D :laugh:

:)
[Nexus 5 General] G-DannY:
Reverted back to stock after 2 weeks with both optimizations: stock libraries feels a lot smoother

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 General] oberbrunner:
On stock, rooted+ART: bionic patch made it worse

On my N5 (stock, rooted with ART), applying the bionic patch made my Quadrant scores go down significantly, and I didn't notice any speedup. Reverted back.
[Nexus 5 General] Lownita:
I made the same observation. I think for overall smoothness it is ART> stock dalvik> rest. Although difference between first two is negligible.

Tapatalked from my Nexus 5
[Nexus 5 General] cazs:
Feels pretty smooth so far today, although of course I will keep testing :)

Running Cataclysm Rom with ElementalX kernel and dalvik+bionic.
[Nexus 5 General] Prezlamen:
stock

i ve tried all combinations...but stock always feels smoother. i ll never understand why are those benchmark results are so low on stock libs
[Nexus 5 General] jphilippon:
It's not why are the stock ones so low, the better question is why are the optimized ones so high? It's because the optimizations improve Java performance and the main benchmark applications use Java.

sent from my Nexus 5
[Nexus 5 General] bog3nator:
Will the revert to stock zip files work on the n7 also?
[Nexus 5 General] metayoshi:
Actually, the question IS why are the stock ones so low. On a Dalvik-heavy benchmark like Quadrant, you can see the Nexus 5 getting somewhere on the order of 8000 or 9000 with the stock Dalvik lib. This is almost as low as the 2012 era-LG Optimus G at ~7000. Other Snapdragon 800 handsets, such as the Galaxy Note 3, LG G2, and Sony Xperia Z Ultra, are getting somewhere on the order of 18,000-20,000 on Quadrant, so using the optimized Dalvik lib is actually putting the Nexus 5 at the same level as what a Snapdragon 800 should be pulling. The thing with Android now, however, is that more apps are less and less dependent on the Dalvik lib, so you actually don't see that big of a performance hit unless you're using apps that are Dalvik heavy like the outdated Quadrant benchmark, so some people see a difference, and some people don't.
[Nexus 5 General] :
Hi,

Why the scores are so low, because they are not included (the libs and binary files) in the Nexus, why? Maybe this:

These patches do not improve only Quadrant (outdated it's right) but Antutu also (and others), not outdated...

Here, I speak only in benches, not the improvement or not in general UI. And if the improvement is only in benches, well, why not?

And if people seems to have an improvement in general UI, well it's even better, each user will make its own opinion by testing, some don't care about benches, others yes, so...

Theses patches are part of the Nexus for me, like test, mods, tweaks, etc... like we flash a custom rom or a custom kernel or anything else :good:

:)
[Nexus 5 General] cellsafemode:
I hate running popular benchmarks due to all the cheating manufacturers and developers have been using lately. But the idea that stock rom is not optimized is annoying.

This is stock ROM, not over clocked, not chilled. Not under volted.