I tried the qualcomm optimized kitkat dalvik and bionic libraries, on cm 11 and mokee 44.2, and they install flowlessly. On mokee i saw an antutu benchmark increase of about 400 points, not so much on cm 11, but still even on cm11 I feel the system is much more responsive. So give it a try if you want, I haven't run into any issues yet.
satwantrana said:
I tried the qualcomm optimized kitkat dalvik and bionic libraries, on cm 11 and mokee 44.2, and they install flowlessly. On mokee i saw an antutu benchmark increase of about 400 points, not so much on cm 11, but still even on cm11 I feel the system is much more responsive. So give it a try if you want, I haven't run into any issues yet.
Click to expand...
Click to collapse
Well it is given that this affects only Qualcomm based devices, while ours isn't. Most likely it is the placebo effect at work.
Sent from my Nexus 7 using Tapatalk
satwantrana said:
I tried the qualcomm optimized kitkat dalvik and bionic libraries, on cm 11 and mokee 44.2, and they install flowlessly. On mokee i saw an antutu benchmark increase of about 400 points, not so much on cm 11, but still even on cm11 I feel the system is much more responsive. So give it a try if you want, I haven't run into any issues yet.
Click to expand...
Click to collapse
:silly:
Please note, however, that this only is of benefit to Qualcomm-powered devices. Naturally, CAF’s optimizations will not have any beneficial effect on non-Qualcomm hardware.
Click to expand...
Click to collapse
Defy isn't Qualcomm
hotdog125 said:
Well it is given that this affects only Qualcomm based devices, while ours isn't. Most likely it is the placebo effect at work.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes our Defy has as Chip from Texas Instruments (TI) the OMAP 3630
Related
Interesting link here guys wonder if One x can get some of this.
http://liliputing.com/2012/06/android-is-about-to-get-a-lot-faster-thanks-to-linaro.html
shankly1985 said:
Interesting link here guys wonder if One x can get some of this.
http://liliputing.com/2012/06/android-is-about-to-get-a-lot-faster-thanks-to-linaro.html
Click to expand...
Click to collapse
I'm impressed.
shankly1985 said:
Interesting link here guys wonder if One x can get some of this.
http://liliputing.com/2012/06/android-is-about-to-get-a-lot-faster-thanks-to-linaro.html
Click to expand...
Click to collapse
Wow, bring it on!
What i would be interested in is whether battery consumption is therefor increased or if it remains the same? Either way, i hope this gets the attention it deserves. It doubles the fps, this is crazy!
nvidia is not involved in this project according to linaro website
the dev in the video mentioned they were only developing for ARM processors.. .. looks like the wait begins
AndrewJ41 said:
the dev in the video mentioned they were only developing for ARM processors.. .. looks like the wait begins
Click to expand...
Click to collapse
99,99% of all Android devices are ARM. Intel has just ported it to x86 but there has never been a worlwide release of an Intel-Android phone yet, so it makes a lot of sense to keep it on ARM. Needless to say that the HOX is ARM-based too. No need for sad faces...
basically if u use custom rom which is based on AOSP, AOKP & CM9 your in luck because these developers can use this now,
while sense have to wait for htc to update... thus us <---- right?
personally i dont see if happening anytime soon
Not happening on tegra just because Nvidia is a bad company and will not release any source for their drivers and so therefore there's no way to port the timizations over.
thunder07 said:
basically if u use custom rom which is based on AOSP, AOKP & CM9 your in luck because these developers can use this now,
while sense have to wait for htc to update... thus us <---- right?
personally i dont see if happening anytime soon
Click to expand...
Click to collapse
Wouldn't google have to implement this into their source or can this be done via kernel update from htc ?.
shadehh said:
What i would be interested in is whether battery consumption is therefor increased or if it remains the same? Either way, i hope this gets the attention it deserves. It doubles the fps, this is crazy!
Click to expand...
Click to collapse
I would guess less battery usage. It goes faster because the code is better optimised and therefore fewer instructions to achieve the same goal.
Hunt3r.j2 said:
Not happening on tegra just because Nvidia is a bad company and will not release any source for their drivers and so therefore there's no way to port the timizations over.
Click to expand...
Click to collapse
I don't think the ABI is affected by these changes, so it should be possible to build the kernel and still use the prebuilt nVidia binary drivers.
Hunt3r.j2 said:
Not happening on tegra just because Nvidia is a bad company and will not release any source for their drivers and so therefore there's no way to port the timizations over.
Click to expand...
Click to collapse
Aren't this changes made to the google code?
Linaro has been applied to CM9 Domination ROM [JUN14-Build3] today On any CM9 build I tried before this all I could acheive on quadrant was around 4300 now im hitting 5000+ with this build.
http://forum.xda-developers.com/showthread.php?t=1692415
13pointseven said:
Linaro has been applied to CM9 Domination ROM [JUN14-Build3] today On any CM9 build I tried before this all I could acheive on quadrant was around 4300 now im hitting 5000+ with this build.
http://forum.xda-developers.com/showthread.php?t=1692415
Click to expand...
Click to collapse
I'm getting 5000 with stock ROM
Sent from my HTC One X using xda premium
13pointseven said:
Linaro has been applied to CM9 Domination ROM [JUN14-Build3] today On any CM9 build I tried before this all I could acheive on quadrant was around 4300 now im hitting 5000+ with this build.
http://forum.xda-developers.com/showthread.php?t=1692415
Click to expand...
Click to collapse
as you can see in the users feedback opf this ROM lots of GPU acceleration issues
on the linaro website FAQ
its actually said they dont support Nvidia processors since NV didnt join the program
anyway ill keep my eyes on that ROM
To be fair I think nvidia will keep a close eye on this and work that has worth they will use internally, so its not all bad. It does however mean a long wait until users see anything from it though
Hunt3r.j2 said:
Not happening on tegra just because Nvidia is a bad company and will not release any source for their drivers and so therefore there's no way to port the timizations over.
Click to expand...
Click to collapse
Most likely nvidia would like to release the source but can't because of non disclosure agreements with 3rd parties. Anyway acoording to the video most optimization is to the cpu so even on sense we could soon see some of the optimizations on custom roms.
Also a while ago I build custum RPM packages on Mandriva, when building on Mandriva by default it uses strict aliasing and many packages refused to build but adapting the code to compile was relatively easy, even for someone like me with little to no experience in coding.
This would do really, really great on the one x.
How hard is it to port the toolchain to tegra3?
Sent from my HTC One X using XDA
oOzzy` said:
This would do really, really great on the one x.
How hard is it to port the toolchain to tegra3?
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
To get a issue free port I would say it needs Nvidia to do this.
Sent from my HTC One X using xda premium
I have some questions concerning Linaro optimizations. I can't find a ROM ready to run on my Galaxy Nexus so I made my own using Linaro's images (system, userdata and boot) and the result isn't spectacular:
1. no cellular connectivity
2. some graphical glitches -- red bands that surround the display at times
Has anyone made a ROM from their images/source that actually works as it should? I tried their latest AOSP Blob, 71, by the way. Is the 12.08 release better in this regard?
I'm sporting the Android 4.1.1 JRO03R + Linaro kernel ROM from Galaxy Nexus Android Development and I'm getting mixed results:
1. In Antutu I'm getting a maximum of ~6400 points and minimum of ~5400 points while the phone was pretty hot.
2. Quadrant remains relatively consistent during testing, with ~2280 points
3. Velamo (latest) I get ~1300 in HTML5 and ~390 in Metal -- just for reference, I did not test it in CM10 or any other ROM before
The difference between the two benchmarks in weird considering that with CM10 + Franco's latest kernel I get:
1. ~6500 points in Antutu
2. ~2900 points in Quadrant
Any idea why the Antutu scores are so close, while Quadrant is not? It seems odd that one benchmark posts a great improvement over stock that is similar to another ROM while another is quite similar. Benchmarks are not necessarily an indicative of actual performance or feel, but nonetheless provide a reference point and I'm curious about the difference in growth.
Quadrant is a horrible benchmark, never care what it says.
Sent from my Galaxy Nexus using Tapatalk 2
It might be so, but the biggest issue I'm having is with Linaro, not Quadrant.
F_T_B said:
I have some questions concerning Linaro optimizations. I can't find a ROM ready to run on my Galaxy Nexus so I made my own using Linaro's images (system, userdata and boot) and the result isn't spectacular:
1. no cellular connectivity
2. some graphical glitches -- red bands that surround the display at times
Click to expand...
Click to collapse
1- missing gsm binary
2- thats no graphical glitch, that's a feature of android itself when either userdebug or eng variants are built.
suggestion: try to build from their source.
sent from my i9250
Vzw has a linaro release, they are always faster but have some odd quirks. On the incredible it made it tons faster unfortunately this also resulted with random reboots and battery drainage and other odd quirks. I did try the linaro build and only really noticed battery drainage and graphical glitches.
Sent from my Galaxy Nexus using Tapatalk 2
bk201doesntexist said:
1- missing gsm binary
2- thats no graphical glitch, that's a feature of android itself when either userdebug or eng variants are built.
suggestion: try to build from their source.
sent from my i9250
Click to expand...
Click to collapse
1. Thanks, I was guessing towards that but I thought their instructions also covered that. Pretty weird that they don't considering I managed to add the VGA driver by using their scripts.
2. Did not know that, thanks.
I'll see whether it's worth it or not when I'll have the chance. Much appreciated.
Within two days since the release of CM10.1 with hybrid ION/PMEM allocation, I happen to see more and more people asking for the explanation of that ION thing we are all talking about.
In fact, all you need to do is a Google search because lately there's been quite a bit of discussions about Android "ION". What exactly is ION? Is it just some fancy name or is there more to it?
Let's talk about some history of Android first.
Since the very beginning, vendors of Android devices like HTC, Samsung or Motorola all use different System on a Chip (SoC) solutions from Qualcomm (MSM/Snapdragon), Nvidia (Tegra) and TI (OMAP). Each SoC has its own kernel drivers for managing memory buffers (chunks of scratchpad memory) used by Graphic Processing Unit (GPU), Audio processing, and Camera Stills and Video processing.
Every vendor had their own version of memory management, such as PMEM for Qualcomm, NVMAP for Nvidia and CMEM for TI - private memory not shared with anyone else. Each Android graphics, audio and camera libraries had to be customized to work with each of the SoC's own flavour of memory management, which makes it a nightmare for the Android Maintainers to maintain the fragmentation and compatibility issues abound. However, this was the case for all pre-Ice Cream Sandwich OS like Froyo, Gingerbread or even Honeycomb.
For Android 4.0 (aka Ice Cream Sandwich), Google was finally fed up with the private memory manager structure and decreed that all newer devices with Android 4.0 native should use the new, so called "ION" memory manager.
So what is exactly the Android ION?
In a simple words, Android ION removes ARM specific dependencies. The ION memory manager provides a common structure for how memory will be managed and used by GPU, Audio and Camera drivers.
Common functions are:
- Memory allocation / de-allocation
- Direct Memory Access Pools
user-space (Android libraries)
- memory passing to/from kernel space
With these common functions and structures defined, kernel drivers from each SoC manufacturer needed to rewrite their drivers to be compatible with Ice Cream Sandwich.
Once the drivers adopted to the new common structure, the graphics, audio and camera libraries can now be more generic and could care less about the nitty-gritty details of how different SoC vendors' drivers worked.
It was painful at first, but it was a necessary move for Google to impose to all the SoC vendors.
Now looking back, this new ION manager enabled manufactures and third party Android projects (like Cyanogen-mod) to quickly bring up newer Android releases for various devices and also reduce the "hidden" Android fragmentation.
Thanks Google for a powerful Search Tool and the author of this:
Original Article
Sent from my GT-I8150 using Tapatalk
A very good explaination in terms of general basic stuff as my head would be spinning around if you explain it into 'high level wizard' stuff.Hehehe.Thank You.
Sent from my GT-I8150 using Tapatalk
Clearly described. Thank you
Sent from my GT-I9500 using Tapatalk 4 Beta
Very clearly explanation! Thanks
Thanks for the explanation sir, at last, i know what is ION :highfive:
Thanks for the explanation! Been looking for one LOLS! So does it mean ION is better than PMEM?
Sent from my eeepc using xda app-developers app
What's the advantage of ION?
Sent from my GT-I8150 using XDA Premium 4 mobile app
TiTAN-O-One said:
Thanks for the explanation! Been looking for one LOLS! So does it mean ION is better than PMEM?
Sent from my eeepc using xda app-developers app
Click to expand...
Click to collapse
I'm not a dev, but in my understanding the biggest hurdle for porting ROMS is device drivers. It is relatively easy to port a ROM from the AriesVe to the Ancora, because they are made by the same manufacturer, have the same system-on-a-chip manufacturer (Qualcomm) and have a similar stock kernel based.
But porting a ROM from, let's say a HTC One is highly impossible, because it uses a different system-on-a-chip exclusive to HTC phones and its stock kernel is based on it. And even though Android is based on Linux, each of the phone manufacturers have slightly different ways of organizing system files that set the various system options. So a kernel patch that works on one device probably won't work on another. (kernel level features such as GPU overclocking, two-way call recording etc. rely on these system setting files).
Even among phones made by the same company, you may have hardware differences such as different camera technologies, different screen resolutions, etc. that make porting harder.
That's why CyanogenMod, AOKP and MIUI are so valuable and appreciated, because they organize porting of a ROM that, as far as the kernel and GUI are concerned, vary little between devices. However those projects still have to rely on what manufacturers choose to release as open source to develop hardware device drivers to port the ROM to each device.
And then you have the problem of, what level of Android is officially supported by the manufacturer? Our Galaxy W, for example, is still waiting for an official ICS release it may never get, which means running JB/KK as it is meant to be run is that much harder. It's hard enough , where we doesnt have official ICS/JB/KK kernel source.
That's why I give lots of kudos to people who take custom ROMs like Aokp,CM(Mega Kudos to Arco) Paranoid Android and the like that were developed for other devices and port them to the Ancora.We're talking crazy wizard-level stuff like memory management, camera, hardware graphics optimization (Project Butter).
#copypaste ;p
Sent from my GT-I8150 using Tapatalk
BIG thanks for this amazing explanation *thumbsup*
ahaiqali said:
What's the advantage of ION?
Sent from my GT-I8150 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The main advantage for us is the possibility to update Adreno drivers, get rid of some bugs and feel smooth with some sort of better performance.
TiTAN-O-One said:
Thanks for the explanation! Been looking for one LOLS! So does it mean ION is better than PMEM?
Sent from my eeepc using xda app-developers app
Click to expand...
Click to collapse
Surely ION management is better. If it wasn't, it would have already been left out since ICS times by all the manufacturers.
Sent from my Nokia 1100.
LeroViten said:
Surely ION management is better. If it wasn't, it would have already been left out since ICS times by all the manufacturers.
Sent from my Nokia 1100.
Click to expand...
Click to collapse
agree with you.. last time i use CM10.1 that still PMEM, i gave up to stay with it because it is really poor performance when the phone stay up longer... now with ION i feel happy when using this CM10.1 with ION.. well since ICS until KITKAT all should use ION to fully optimize the memory management itself.. if someone could build ION for ICS.. haha.. that would be awesome...
hurtsky said:
agree with you.. last time i use CM10.1 that still PMEM, i gave up to stay with it because it is really poor performance when the phone stay up longer... now with ION i feel happy when using this CM10.1 with ION.. well since ICS until KITKAT all should use ION to fully optimize the memory management itself.. if someone could build ION for ICS.. haha.. that would be awesome...
Click to expand...
Click to collapse
Mates, @hurtsky & @LeroViten
Just want to ask , so for now ONLY cm10.1 b2 custom ROM is compatible with ION kernel? Both ROM and kernel must support ION? Thnx
dec0der said:
Mates, @hurtsky & @LeroViten
Just want to ask , so for now ONLY cm10.1 b2 custom ROM is compatible with ION kernel? Both ROM and kernel must support ION? Thnx
Click to expand...
Click to collapse
Yes
poji94 said:
Yes
Click to expand...
Click to collapse
*sighs
sorry before i noob are "ION" give more life battery to custom rom?
ades47 said:
sorry before i noob are "ION" give more life battery to custom rom?
Click to expand...
Click to collapse
Surely not. It has nothing to do about our battery life. We all have different usage statistics and the variety of apps installed. So we all have different battery stats too. For me one with a heavy usage is more than enough. And two days as a calling and messaging device - is brilliant.
But no... ION has no influence on battery life...
thanks for the topic... best explanation i've read
Maido Ari...
Thank You For The Explanation
LeroViten said:
Surely not. It has nothing to do about our battery life. We all have different usage statistics and the variety of apps installed. So we all have different battery stats too. For me one with a heavy usage is more than enough. And two days as a calling and messaging device - is brilliant.
But no... ION has no influence on battery life...
Click to expand...
Click to collapse
i expecting ION can do better in battery life since bbm to android my galaxy w 100% battery drain in 3 hours and i install greenify
Does the PA rom for the Nexus 5 have the optimizations from the Moto X included?
IIMaxII said:
Does the PA rom for the Nexus 5 have the optimizations from the Moto X included?
Click to expand...
Click to collapse
There are bionic optimization... no dalvik
IIMaxII said:
Does the PA rom for the Nexus 5 have the optimizations from the Moto X included?
Click to expand...
Click to collapse
Dave Kessler from Team Vanir on the subject of the Moto X Dalvik/Bionic patches floating around XDA at the moment:
They aren't compatible with your device unless the rest of the rom was compiled from the same source. If you like memory alignment segmentation faults continue to use them.
They are a bunch of snake oil bull**** anyways. On my nexus 5 they increased quadrant scores from ~10,000 to ~20,000. HUGE red flags here lol. Don't you think any device that uses them would have gotten a lot more press just because they were using them if they actually did something? it's easy to insert hacks to increase benchmark scores and it's something we've chosen to not do. We even removed the ones from the linaro source we rebased.
Click to expand...
Click to collapse
https://plus.google.com/104097621805582709171/posts/JJsTYxXEgZF
Just another perspective. Don't get too hung up on the inclusion of these patches in whatever ROM you're using. CM have included their own bionic optimisations and PA have done the same.
How many of you are running stock? Would you like a custom kernel with optimizations, governors, schedulers and overclocking/undervolting? Would anyone use it if I released one? If so, what governors and schedulers would you like to see?
Thanks!
Personally, I love running stock. I would definitely like to see a kernel that focuses on battery saving.
Please release the kernel. This phone needs some overclock
I'm going to wait until Nougat source is released to build a stock kernel since I was accepted into the Beta.
A custom kernel for Nougat would push me even closer to the already close edge that is my wallet.
This phone seriously looks attractive for the ~$160 asking price on Newegg/Amazon. Coming from a Nexus 5/Spare GS4, I'm used to really poor battery life and average performance.
I'm currently eyeing the Moto G4 and the Robin. The Robin is much more powerful, but doesn't have a replaceable battery and has a much smaller battery (technically the G4's battery isn't replaceable but it can be done fairly easily). There's also this business with Razer, which isn't too big of an issue as I normally stick with custom ROMs (and stock is getting quite a few updates in the future).
Both are in the high ~$160-200 range. Any input? If the Robin's battery is somehow replaceable that would be amazing, and I'd like an OEM supplier.
negusp said:
A custom kernel for Nougat would push me even closer to the already close edge that is my wallet.
This phone seriously looks attractive for the ~$160 asking price on Newegg/Amazon. Coming from a Nexus 5/Spare GS4, I'm used to really poor battery life and average performance.
I'm currently eyeing the Moto G4 and the Robin. The Robin is much more powerful, but doesn't have a replaceable battery and has a much smaller battery (technically the G4's battery isn't replaceable but it can be done fairly easily). There's also this business with Razer, which isn't too big of an issue as I normally stick with custom ROMs (and stock is getting quite a few updates in the future).
Both are in the high ~$160-200 range. Any input? If the Robin's battery is somehow replaceable that would be amazing, and I'd like an OEM supplier.
Click to expand...
Click to collapse
It would also be amazing to see some voltage control to control the beast of an 808.
There will be a custom kernel available in the near future for AOSP/Omni on the Robin. It is currently being tested ? and so far it's showing quite a bit of promise.
Some features it'll include are efficient hotplugging, optimized CPU governors, a new I/O scheduler and much more.. Based on Electron Kernel for the Nexus 6p by @frap129
nexbit robin has volte support any one test ??????
variravitejareddy said:
nexbit robin has volte support any one test ??????
Click to expand...
Click to collapse
I know for T-Mobile US yes but idk for where you are at.
Saythis said:
There will be a custom kernel available in the near future for AOSP/Omni on the Robin. It is currently being tested and so far it's showing quite a bit of promise.
Some features it'll include are efficient hotplugging, optimized CPU governors, a new I/O scheduler and much more.. Based on Electron Kernel for the Nexus 6p by @frap129
Click to expand...
Click to collapse
If you need a tester, I would love to help.
Saythis said:
There will be a custom kernel available in the near future for AOSP/Omni on the Robin. It is currently being tested ? and so far it's showing quite a bit of promise.
Some features it'll include are efficient hotplugging, optimized CPU governors, a new I/O scheduler and much more.. Based on Electron Kernel for the Nexus 6p by @frap129
Click to expand...
Click to collapse
Any news on the electron kernel?
Saythis said:
There will be a custom kernel available in the near future for AOSP/Omni on the Robin. It is currently being tested ? and so far it's showing quite a bit of promise.
Some features it'll include are efficient hotplugging, optimized CPU governors, a new I/O scheduler and much more.. Based on Electron Kernel for the Nexus 6p by @frap129
Click to expand...
Click to collapse
Updates?
xBane_ said:
Updates?
Click to expand...
Click to collapse
Seems to be dead
Nope not dead. You can get weekly builds from here https://github.com/frap129/ether-weeklies
sykomaniac said:
Nope not dead. You can get weekly builds from here https://github.com/frap129/ether-weeklies
Click to expand...
Click to collapse
Is the kernel only compatible with Omni?
crian said:
Is the kernel only compatible with Omni?
Click to expand...
Click to collapse
The latest weekly build doesn't boot with Omni 7.1.2, so I'm not sure.
I believe the kernel is meant for Nextbit OS 7.0, not for custom roms. Not sure though.
Sent from my Robin using XDA
bmccoy11 said:
The latest weekly build doesn't boot with Omni 7.1.2, so I'm not sure.
Click to expand...
Click to collapse
So dirty flashing back to the latest Omni 7.1.1 build and then flashing the kernel should allow get the phone to boot?
Working on trying to get it to boot don't worry guys
sykomaniac said:
Working on trying to get it to boot don't worry guys
Click to expand...
Click to collapse
I tried going back to the latest 7.1.1 build and couldn't get it to boot, so I gave up. Can you give updates in the future?