yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] SupremeBeaver:
the project has been abandoned apparently.
[Nexus One Android Development] Dany0:
No, storm is just at school and other guys just did not do anything.
[Nexus One Android Development] hotweiss:
Why not give the guys at MIUI a shout? They seem to have a lot of skill:

http://miui.com/index.php

Some Chinese writing abilities are a must though :)
[Nexus One Android Development] Dany0:
all you need is google translator! lol :)
[Nexus One Android Development] NeoS:
Seeing that Angry Birds skyrocketed in the Android Market with over 2 million downloads in 2 days, gaming on Android is now officially booming! This means (hopefully) that the GPU's will get more attention. And maybe even for existing devices.
[Nexus One Android Development] rodigezstyle:
i wish i could help so much...
[Nexus One Android Development] dreamhunterr:
According to Phandroid:

Maybe some improvements have been made on this are...fingers crossed :)

Of course the news itself isn't that believable (lol @ the picture). However, since the Nexus is still the developer phone, there's no reason why one can't dream.

Source
[Nexus One Android Development] babijoee:
All we can do is wait i guess. I havent much time to poke around and have a look at this stage. And as pointed out the nexus is google's baby so it'll still be getting the attention is needs
[Nexus One Android Development] storm99999:
Looks like nothing has changed in the staging driver since the kernel.org head added it several months ago.

However, here's the issue: CodeAurora has been modifying the driver to the point that it is almost worthwhile to try again with it. However, I expect that once it works with our devices well to the point we would want it, there will be about a week between when it is finalized and the source head gets a patch. At that point, every rom and kernel that syncs with android.git.kernel.org will have it.

In other words, it would be cool to try it out, but as seen with the last driver upgrade, Cyanogen had his hands on it before we even figured it out. With how things are set up, we may be lucky and the driver is only in staging by fluke, but most likely none of us can expedite the process without working with CodeAurora directly with docs.

When time opens up sufficiently, I'll resync my code and retry with the current CA driver, but I think I'm putting my hat up with this project.
[Nexus One Android Development] Dany0:
Storm, you are the man that makes me wanna drop all my hate and learn C programming language.
[Nexus One Android Development] charnsingh_online:
I am getting 23fps on nenamark and 32 fps on neocore. I think thats hellot of improvement since stock. Thats in CM6. The drivers keep getting better and better. I remember stock nenamark neared 16 fps
[Nexus One Android Development] tltester:
Tell me please, are you overclocking/using any other technique for fps improvement?

I'm asking this because I'm getting a 15.5 with nenamark. That's with Enomther's theofficial 2.13.2.

Comparing to me you are getting about 50% improvement. That's a lot, really :)

Is this a CM6 production version's driver? 6.1 nightly one? Something using your own personal magic?

If this is just a new driver, I think Enomther may be happy to hear about this and incorporate it in his own bakery :)
[Nexus One Android Development] charnsingh_online:
They are in cm6. I think its in the stable version. Told enomther bout them!
[Nexus One Android Development] Dany0:
Does anyone wanna contact the MIUI guys plox?
[Nexus One Android Development] Dany0:
Trei tage!
[Nexus One Android Development] Dany0:
Lalalala
[Nexus One Android Development] babijoee:
@Dany0 thanks for trying to keep this thread alive but honestly i dont think anyone is actually working on this. Haven't heard from storm in awhile aswell
[Nexus One Android Development] Dany0:
Who cares? I start liking to bump this thing :)
[Nexus One Android Development] mik101:
Pretty sure storms in school. Be patient.... he probably has very little free time if he wants to do very well.

Overall I think unless CM or MIUI take it on in whole then we might be asking for a little much though.
[Nexus One Android Development] Dany0:
Agree, I think it's time to contact both of them. CM shouldn't be a problem, since I've never heard it would be such a proble to contact him... though I think I already did and he never answered... bastard =)

But I can't access the MIUI forums.

a.) I can't understand chinese Hans

b.) google translator fails my attempt to reigster

c.) I'm a bit... let's face it, lazy about that.

Soo... anyone?
[Nexus One Android Development] YoMarK:
I'm on Rod's MUIMOD v1.5 and also getting 23fps in nenamark with CPU governor set to performance and OC-ed to 1113Mhz.

With default CPU governor and no OC it's about 17fps. Changing CPU governor makes a big difference.
[Nexus One Android Development] Dany0:
OK Guys, Leedroid has already ported GPU+ drivers to his Sense rom. It's time to optimize it.
[Nexus One Android Development] charnsingh_online:
I think the GPU+ thing he is saying is already in CM, i saw his gpu commits were from CM
[Nexus One Android Development] :
Please could you explain what gpu+ is, i googled it but i couldn't find anything on the subject. BTW your sig is hilarious.
[Nexus One Android Development] storm99999:
GPU+ was just the name given to a newer-ish driver for the Adreno 200. It was first ported into Cyanogen and it's spread out to anyone who syncs with them. I think it changes memory mapping or somesuch of kgsl. I never really bothered doing a diff.

It's not the newest version of the Adreno 200 driver, I've been on and off working on getting that one in, but this version is an 80% speed bump and for the time, it's good enough.
[Nexus One Android Development] charnsingh_online:
Testing new gpu drivers, they are unstable but provide around 60% performance increase, wait for them to be stable n optimized!
[Nexus One Android Development] charnsingh_online:
It seems slower to me in nenamark but its better in quadrant and neocore , quadrant score 422 in 3d and neocore is 34fps

Edit

duh they perform better in nenamark too, around 24-25 fps
[Nexus One Android Development] blunden:
How unstable are they and in what apps have you noticed it?
[Nexus One Android Development] tolis626:
Hey hey,what drivers gives such results?I run AuraxTSense with GPU+ on my Desire and with perfrormance governor @1190MHz I get 32 at Neocore and 21 at Nenamark.What driver are you talking about?
[Nexus One Android Development] charnsingh_online:
these are not GPU+ drivers, these are after GPU+. The latest one currently in development. Unstable like sometimes graphics would totally stop and sometimes they would lag but rare like 1 in 20 runs.
[Nexus One Android Development] tolis626:
And will these be available for Sense roms also or will I have to give up on Sense?See,I love Sense,but I love performance even more! :D :cool:
[Nexus One Android Development] LaurensBER:
Awesome!

Any link to more informations? Commits or something like that?
[Nexus One Android Development] charnsingh_online:
Expect a lot with gingerbread update in terms of hardware optimization, i beleive there will be a new radio, better DSP(video encoding and decoding) drivers and better GPU drivers. There will be a lot lot more thats coming with gingerbread
[Nexus One Android Development] babijoee:
Awesome Christmas present from google :)

Making our N1 still no1
[Nexus One Android Development] blunden:
Would you mind uploading your boot.img and wlan.ko for the latest build?

My build errors out with a non-obvious error. I guess I could try intersectRaven's latest kernels by I'd like to avoid his extra changes.
[Nexus One Android Development] charnsingh_online:
wait like 10 minutes, compiling one, will upload soon

edit here it is, not tested as just compiled and i am calibrating battery on my phone.

#include std.h

#include cyanogend.h

wlan.ko - http://www.megaupload.com/?d=HXIKDTDL

zImage - http://www.megaupload.com/?d=58FEDZUU

#blamewes
[Nexus One Android Development] blunden:
Thanks a lot man!

Are you using the config from the nightlies btw?
[Nexus One Android Development] charnsingh_online:
the config is in the kernel source. cyanogen_mahimahi_defconfig, no need to pull configs from phone. make ARCH=arm cyanogen_mahimahi_defconfig

make ARCH=arm oldconfig
[Nexus One Android Development] blunden:
Ah, ok.

Strange thing is that I don't see any improvement in Nenamark1 after fastboot booting the zImage.

EDIT: The error I got when compiling (about the function declaration) disappeared when using the correct config. :) Had a feeling that might be an issue but the error message threw me off. However I still wonder why I don't see any performance difference in the benchmark where you got massive improvements.
[Nexus One Android Development] charnsingh_online:
I got 23.1fps normally on nenamark whereas >24 when i did something secret. Secrets not to be told!
[Nexus One Android Development] blunden:
Well, I still can't get better than 16.7 fps with sound off. I got 16.6 fps with the old kernel something important must be different. Sure, I'm lacking the wlan.ko module currently but I don't see why that would matter and fastboot booting it shouldn't affect it either as far as I know.
[Nexus One Android Development] maxisma:
​

WTF? Why?! O.o
[Nexus One Android Development] blunden:
What are your results when running this kernel? Did you try it?
[Nexus One Android Development] tolis626:
Change your CPU governor to performance in SetCPU.
[Nexus One Android Development] blunden:
Thanks. That got me up to 21 fps. 22 fps with some CPU overclock. Too bad it can't get the same results when using other than performance though. I would have expected some kind of boost at least.

Still a nice kernel though.
[Nexus One Android Development] charnsingh_online:
http://m.plixi.com/p/55911314
[Nexus One Android Development] blunden:
Nice.

Btw. I have yet to have a single kernel panic using the kernel you linked. My kernels build now but won't boot for some reason and since I don't have a serial cable for it I can't see what's failing :(
[Nexus One Android Development] charnsingh_online:
U don't have kernel panic cuz I did some code cleaning up
[Nexus One Android Development] eug89:
Best I can get with nenamark is 22.6, 31.3 with neocore and 420 with quadrant @1113 and performance scaling.

BTW does this kernel also have your latest mods for 720p recording?
[Nexus One Android Development] blunden:
Oh, ok. Nice. What's your github?

How come I can't even get my own kernel booting though?

EDIT: Never mind. I found it. Nothing relating to your modified kernel code though. :( Ah well, I just wait. :)
[Nexus One Android Development] charnsingh_online:
Yeah it has all my latest mods for 720p
[Nexus One Android Development] blunden:
I get and FC when the Camera app tries to save a recorded 720p video. Have you made any changes to Camera.apk compared to the CM nightlies?
[Nexus One Android Development] Dany0:
I love how the thread I was bumping for so long pointed out to be so well :)
[Nexus One Android Development] storm99999:
I'm glad something turned out. It's amazing, what's the GPU speed from stock, some 55% slower than it is now? We're nearing in on some of the graphical heavyweights.
[Nexus One Android Development] there_are_four_lights:
Are any of these findings/changes implemented in cm nightlies? Is there anything flashable available for public consumption?
[Nexus One Android Development] mik101:
WOW. I honestly didn't expect this much progress after seeing this thread get bumped for so long.

Great work. Is this going to be included in the prebuilt kernel for CM at any point? (if it isn't already).
[Nexus One Android Development] gravufo:
+1! I'd like to test out these great results in CM too ^^
[Nexus One Android Development] christiankk:
Where did you get them from?
[Nexus One Android Development] blunden:
Yes, this is great indeed. I wouldn't say we are nearing some of the newer GPUs though. They are still much faster in most cases. However it's nice to see that there are still things to be done to the drivers, that it's not just a hardware limitation.

When it's considered stable enough and has undergone a little more testing probably. If you have unlocked your bootloader you can fastboot flash the zImage charansingh posted earlier in this thread. It will build the boot.img for you. If you rooted using another method and have a locked bootloader you will have to insert the zImage in a CM boot.img and then build an update.zip for that.

Most likely considering charnsingh's kernel in the previous post is based on cm-kernel-exp (ie. CyanogenMod Kernel Experimental) on Cyanogen's github. It also includes several fixes and improvements and features from the Desire HD/Z kernel source from what I've seen.
[Nexus One Android Development] mohsin125:
Whoa! great to see progress :D....cant wait for a stable release! btw after the performance increase, is the performance close to the adreno 205?
[Nexus One Android Development] blunden:
No, not even close. :( It seems people with the G2 get around 31-34 fps and devices with even better GPUs can get closer to 45-50 fps in Nenamark1.

As I've said before I have yet to have a single kernel-panic with charnsingh's compiled kernel. My builds won't even boot though so I don't know what's wrong. With that said I would also like to see this be the official CM kernel. :)
[Nexus One Android Development] vivanshah:
i'm getting 21.7 fps on wildmonk's kernel. isn't that roughly the same as what you guys are getting with charansingh's?
[Nexus One Android Development] charnsingh_online:
Yeah wildmonks commited the drivers from CM repo. They are the new ones that are meant to improve shader performance etc.
[Nexus One Android Development] Dany0:
2.3 Gingerbread drivers should perform just as well, we'll just have to wait for those. Also HTC Desire will be getting Sense 2.0. If the delay of update is going to be like it is already, then I'd expect it to come with 2.3 just after Desire HD gets 2.3.
[Nexus One Android Development] HairyMerkin:
Yay, progress!
[Nexus One Android Development] Dany0:
Yay useless post! I am soo surprised!
[Nexus One Android Development] curiousGeorge:
I can't wait until something like this hits the HD2!

Then again, Android on the HD2 doesn't support 720p (hardware capture/encode or decode) or even B-frames in its video decoder...
[Nexus One Android Development] DarkReaper111:
You can already get 20fps in nenamark with MDJs Kernel.
[Nexus One Android Development] blunden:
Like most people he probably base his kernels on the CM kernel source which would explain it.
[Nexus One Android Development] vivanshah:
23fps with wildmonk's latest kernel, oced to 1113, set to performance in setcpu
[Nexus One Android Development] skend04:
I'm probably being a div or having a blonde moment, but how do i run these? Or are these in the latest CM nightlies.
[Nexus One Android Development] Dany0:
Reports say 25FPS @ nenamark w/ gingerbeard possible but with a little but!

:D
[Nexus One Android Development] blunden:
If you have an unlocked bootloader you can flash the zImage with 'fastboot flash zimage zImage' and have it automatically build the boot.img for you. If not you have to extract the boot.img from the CM nightlies, replace the zImage and rebuild it. After that you'll have to make an update.zip or can perhaps flash it with flash_image in recovery.

The wlan.ko belongs among your kernel modules. Something like /system/modules/ but I don't remember the exact path. It's fairly obvious from browsing around the filesystem though. :)
[Nexus One Android Development] mortzz:
I haven't done this in a while, but I'm getting "signature verify fail" in fastboot, and yes, it's unlocked.

Edit: Derp, I typed fastboot flash zImage.
[Nexus One Android Development] tolis626:
Guys,my Father's X10 mini pro(which I think has the same Adreno as our Snapdragon phones),after its Eclair update hits 48FPS at Neocore and 40 at Nenamark.Maybe we should also reduce our resolutions to 400x240(it has 320x240)! :p
[Nexus One Android Development] Dany0:
They have already made a phone with smaller resolution. A korea-exclusive LG Optimus had 640x400 resolution. It had higher scores but there is a problem you know... It's called compatibility.

And even though we will find a way how to do that, it'll end up the same as on WM.
[Nexus One Android Development] tolis626:
No dude,I was just joking!Did you seriously think I would ruin my screen's beauty with a smaller resolution just to see some performance improvement?Nah,no way!Chillax...! ;)
[Nexus One Android Development] gravufo:
Hey guys...I need some feedback:

I am currently running CM nightly 254 and kernel 2.6.35.8_AVS-950mV_BFS_AXI_720p_1152MHz_112010 from WM and I barely get 15.4 fps in Nenamark and 1500s (very rarely in the 1600s) in Quadrant...I'm really looking to improve this and I don't know how and/or what to do...

Can someone possibly help? :D
[Nexus One Android Development] vivanshah:
set your cpu governer in setcpu to performance.
[Nexus One Android Development] mkrmec:
why doesn't the performance on other governors not do the same as performance?

I mean if a benchmark is testing the limits of a device that means that the CPU/GPU should be at maximum even if the governor is not perfomance.

Logicaly On Demand should do the same as Perfomarnce in CPU/GPU tests because it should demand the MAX performance.
[Nexus One Android Development] gravufo:
I necessarily have to have setcpu? It's a paid app and I can't buy these yet (soon getting a credit card, but need to wait a month or two cause I'm not 18 yet)

And as the post above...as default, the cpu/gpu should automatically use full potential when system is demanding lots of power, such as 3D rendering and so on...why isn't this happening?
[Nexus One Android Development] teihoata:
setcpu is offered for free here on xda by the developer, have a search for it ;)

The market version is for donations
[Nexus One Android Development] gravufo:
Oh how great! Thanks so much :D
[Nexus One Android Development] tolis626:
It's at the G1 forums at the Themes & Apps section.Happy overclocking! ;)
[Nexus One Android Development] storm99999:
I don't know if I'm lucky or something, but I consistently get 21+ with the userspace governor, so unless there's a bug in that where it operates identically to performance, I'm getting the best of both worlds on my end.

Can anyone confirm?
[Nexus One Android Development] Dany0:
isn't userspace basically the same as performance? Oh and btw, I get huge improvment in FPS in quake2droid when setting to performance. Totally has to do something. And I'm running MIUI(no enhanced GPU+ drivers!)
[Nexus One Android Development] gravufo:
Found it and made myself some nice profiles...hope it can save me some battery while getting great (even better) performance :D

I got to 23 in Nenamark as well as 1800s in Quadrant!

Thanks so much :D
[Nexus One Android Development] tltester:
Yes, that's obvious. Just tried out performance vs on demand (enomther's 2.14.3) and got 22 vs 16 fps :)

What's more interesting is how much we can suck out of this beast WITH gpu+ drivers, WITHOUT overclock and WITH "on demand" governor. This may really show improvement / lack of it...
[Nexus One Android Development] Imperial.mack:
Bump

Can we ever get above 22-23 in nenamark? This is the only thing holding my nexus back from being perfect as I want to try some psx games but its too laggy :(

Sent from my Nexus One
[Nexus One Android Development] gravufo:
Wait til Gingerbread, they'll probably have more material to work on, since I suspect Google will try and optimize the graphics drivers too and maybe in ways that were not thought here...
[Nexus One Android Development] Imperial.mack:
I will wait, thankx lol

Sent from my Nexus One
[Nexus One Android Development] nlimperios:
How can i use the given zImage in my Htc Desire ?

I flash it but the phone hangs at the splash screen (probaply because

of different boot structure in the nexus).

Of course i made a nandroid backup and i restore my boot back to the

working state.
[Nexus One Android Development] Dany0:
It's kinda outdated, don't use it. You can just flash a CM6 based kernel instead. Or a gingerbeard rom
[Nexus One Android Development] redstar3894:
You wouldn't be able to even use it on the desire... the system board (while containing 99% of the same hardware) is configured completely differently... so it's not surprising it wouldn't boot... :rolleyes:

So we won't see updated graphics drivers until charansingh releases what he was working on or we get some kernel source from gingerbread... until then... we're all out of luck... :(
[Nexus One Android Development] charnsingh_online:
The drivers are already in cm source
[Nexus One Android Development] redstar3894:
Really? Were they merged in recently or is this older stuff?

Correct me if I'm wrong but I thought you had been working on some more updated stuff....guess not, sorry, my mistake :p

Sent from my Nexus One
[Nexus One Android Development] nlimperios:
Υου were mentioning 60% increase in performance.

I hardly saw a 10% increase.
[Nexus One Android Development] charnsingh_online:
THe performance varies in different tests differently, shader performance, etc varies. Like in quadrant tests there is about 60% increase in performance, nenamark is around 10%
[Nexus One Android Development] Dany0:
We'll see with the gingerbeard drivers.

I get usually more then 10% boost in nenamark, bit more, something between 15-20% boost.

Also in games, it's VERY easy to notice the extreme smoothness, people, it's totally going much higher then the 60 FPS limited by the frequency of the display. We should try this thing I suggested earlier:

http://xdaforums.com/showthread.php?t=755671
[Nexus One Android Development] storm99999:
Y'know, although texture resolution changes would be cool, wouldn't it be more universal and effective if we tried to change how a game rendered itself? On PCs, I know this is driver level stuff and we don't have much driver level control, but say we mapped, in pseudocode of course, RenderWithoutAA to RenderWithAA and force antialiasing on games.
[Nexus One Android Development] Dany0:
Dude, AA on 3,7" display? With 300+DPI? :D No dude, but one note: we'd add more spec maps and some bump maps just by copying the galaxy s texture files.
[Nexus One Android Development] storm99999:
I figured, but I thought that AA would be the easiest. The only other mod that my drivers currently provide is tesselation, but I think that's difficult if not impossible to externally add in OpenGLES.

Now, I do know that the difference between the, say, AMD normal hardware and FireGL stuff is the drivers. The FireGLs use higher quality rendering modes instead of faster ones. Also unlikely to implement.

To be honest, I'm just throwing out ideas to see if it catches the mind from someone who might know more than I.
[Nexus One Android Development] thanharts:
How can I try it ?? Plzzzz!!!
[Nexus One Android Development] Dany0:
I have an idea! Something like ENBSeries embedded some time ago - custom shaders!

Since glES2.0 is all about programmable shaders, we could add a simple enhancment. Like bloom or volumetric lighting. And tessalation is actually a method that accelerates the game(has to load less data to graphics ram, then if you would create the data with more detail already, but renders more, so saves bandwidth). Though it depends on implentation. And it's really easy to implent it as a shader, and I'd not wonder if it could handle it!

And I know a bit of shader programming, might try to learn glES2.0! :D
[Nexus One Android Development] tolis626:
Go Dany GO! :D
[Nexus One Android Development] Dany0:
Okay so playing Brothers in arms 2 I realised a really big problem with adreno that's been here for a while: Any particle or transparent texture result in HUGE FPS dropdown, so i think this is No.1 on the list now.

Anyone knows a book about glES 2.0? Thanks.
[Nexus One Android Development] storm99999:
So, adrenos struggle with transparent billboarding, or is it something else? As for the book, if you find one, let me know. I've been wanting to get into this for months.