yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] NeoS:
I hope you're kidding, right?

Anyways, great to see Chainfire and NuShrike here. At least you guys still care a bit about this stuff. (a bit, but better than not at all)

NS, as I said earlier, it's a real shame some dumbasses shunned your great work you've done in the past. I hope you'll someday enrich us again with your help.
[Nexus One Android Development] Dany0:
Okay guys you should definitely check out this phone:

http://www.engadget.com/2010/08/19/exclusive-dell-thunder-prototype-preview-video/

It, again, uses same CPU, and hopefully same GPU. And the benchmark results are GINORMOUS! So maybe once... we actually may give not just a minor shot of speed with custom drivers, but a GINORMOUS shot of speed!

:eek:
[Nexus One Android Development] storm99999:
Same GPU... Heck, the roms for those are way more likely to be using a more modern kernel, as it's slated for a 2.2 release. I hope we can get the source (and it's not screwed up beyond repair like the ACER's) because it should make porting very easy.

This reminds me, sometime later today, I'm going to check the progress on the staging kernel by resynching my source repo. Maybe it's buildable.
[Nexus One Android Development] Dany0:
Thanks dude! :D
[Nexus One Android Development] wrinklefree:
This should get interesting. Subscribed!
[Nexus One Android Development] roteplex:
N1 on par with Droid X

The test units that were reviewed date back to april, so we rest assured that they have the same Adreno GPUs in our N1s.

-Note though, these Thunders are running outdated software and are still buggy, so when the final units arrive pumping froyo, I think we can see FPS at about 42 FPS for Neocore (from 37) and 22 FPS (from 19) for Nenamark based on the performance increase on the N1, and these scores TIE with the currently released Droid X/ Droid 2, which means our N1 GPUs can still play the compete game with the latest and greatest.

The SGX540 is still on another level (OMAP4s will also be using these), but well get Snapdragon 2 shortly, with a new powerful GPU.

Now all thats left is to find a way to port over the drivers.:mad:
[Nexus One Android Development] NeoS:
Hmm. I can't seem to get GLbenchmark running on my Nexus on Froyo. It worked on Eclair though. When i start the tests, it just crashes to desktop.

Anything i'm doing wrong here?
[Nexus One Android Development] Dany0:
Yup same problem, it works just don't select them all at once, just run them one by one.
[Nexus One Android Development] tolis626:
Hey guys,did anyone check AdamG's OpenDesire rom at the Desire forums?It says something about having a new gpu driver...Maybe it's a good idea to contact AdamG?I would test to see if there is any difference,but I have no rooted Desire,only stock!
[Nexus One Android Development] fstluxe:
Indeed With Big performance boost!! neocore 32.3 FPS Nenamark 21.2 FPS!! His Rom = Amazing..
[Nexus One Android Development] babijoee:
Well it seems that cyanogen nightly builds has incorporated some GPU updates aswell. I"m running on latest experimental 22.8.10 no modified kernel or OC

Kernel version:

nenamark = 15.7 highest i've ever achieved. But 21fps is wow.

Neocore: 31.3 first run

We should definintely look into their kernel work.
[Nexus One Android Development] Dany0:
LOL I wonder who created that driver, because he's a genius! :D
[Nexus One Android Development] storm99999:
Well, I quickly perused the thread, if anyone wants to build it for the N1, all you need to do is sync his repo and build the kernel. I'd do it meself if I wasn't 6 hours overdue for sleep and needed to wake up in 4 hours (and my computer wasn't in hibernation/self assembly mode). Check the thread, second post:

http://xdaforums.com/showthread.php?t=712615

Ignore which selection you want for lunch, select passion, then cross-compile a kernel as a person usually does.

It's 50/50 it's self contained, but I aught to PM him to make sure.

Edit: Oh hey, my computer quit self-assembling. Maybe sleep isn't that good an idea.

Edit2: His repos are jacked up for me right now, so I'm not going to build from source. However, since the n1 and desire are pretty much identical, I'm going to try to flash his kernel. I'll let you all know.

Edit3: No, it doesn't boot. Well, I guess I'll have to get his kernel source, but it's just unavailable right now.

Edit4: Found it! http://github.com/xdabravoteam/cm-kernel It's a direct fork off of cyanogen's, so any work I do is mostly pointless. Any improvements will be here in a week or two at most.
[Nexus One Android Development] Dany0:
Wow dude have a rest sometimes :o
[Nexus One Android Development] storm99999:
Alright, is 15 fps good in the newest nenamark (the one with butterflies and weird music)? Cause I just got that with the kernel. Of note, though, if that isn't good is the kernel option that "Provides access to registers needed by the userspace OpenGL|ES library." I couldn't find the library inside of the rom over there though, but that was exactly what I've been looking for. Also, the difference between the two values could just be that his rom's overclocked 30%.

Edit: yup! I forgot I was using an OC source, so I pumped it to 1267mhz and I just got 21! I think something somewhere is wacky as his 1.3 OC only got 14, but the 1.0 OC got 15.

Edit2: I think there is some strange things a-happening. Once I got the 21, no matter what the SetCPU settings, as long as the max was above 1Ghz, I got 21. So, I guess I got stuff to upload. :)

http://dl.dropbox.com/u/9780975/zImage

It's in zimage format, so:

adb reboot bootloader

fastboot boot zImage

It's not meant for frequent use, or even passive use. It's probably broken to all hell and the top clock is 1.3Ghz, which very well could fry your phone. Keep that in mind, and have fun. I got some sleep to have.

Edit3: Even at 245/245 in SetCPU, I'm getting better frames than 1Ghz yesterday, 13.6. Hah!

Probably last edit: ok, launcherpro runs stutter free down to 445 MHz. The same cannot be said of the browser, but still... I'll do a code comparison to see what is the difference between kernel codes when I get the chance.

Last edit: This kernel may not be special in any way. Using a different frequency scaler than userspace cut my frames down to 14.
[Nexus One Android Development] Dany0:
no it is not, I've got 17FPS in Pinky's Desire(stock driver, no OC), 17,2FPS in DeFrost 2.9a @1,3Ghz and 20,8FPS with OpenDesire @ 1,075Ghz (crashes if I go over this mhz or performance mode)

YOU'RE AWESOME!

Nice! Just one question, can I use it on OpenDesire? (e.g. NOT on nexus one?)
[Nexus One Android Development] storm99999:
Huh. My source is OpenDesire based, (but incompatible as I built it for the n1) so you should be clocking identically. Did you try switching cpu governers to userspace or were you not using the latest build? (the one where you apply everything then a patch?)

I don't know why my quickly hacked together kernel is running so well if you already were doing that.

Well, for everyone else, if you're using a current CM nightly, changing the governer to userspace (Edit: check set on boot as this isn't the default for most kernels. It explains all my problems.) gives a jump to 21. The only actually neat thing of that kernel I put up though is that it can run to 1.3 Ghz. I am, for one, quite surprised my phone could run on that.
[Nexus One Android Development] Dany0:
Well I am not a fan of adb so I am not pushing it right now(100% next time, when there'll be normal patch for clockworkmod ;) )

But thanks for the advice, it looks like it doesn't crash with userspace @ 1,267Ghz(it does on 1,3Ghz). And just got 20,9FPS at nenamark, great!

Oh wait... okay not, just crashed w/ userspace @ 1267Mhz..

EDIT:

Lasted longer with conservative... trying now at 1,1Ghz...

EDIT2:

It's clearly opendesire's problem, I could do 1,3Ghz stress test for 8min 20s without error, and was not unstable.
[Nexus One Android Development] storm99999:
Did you try it at 1Ghz? It seems CPU clock speed has little to do with GPU benchmarks above ~500Mhz from my testing.
[Nexus One Android Development] chrs2021:
wifi - driver

hey storm, can you upload the wifi driver for the zImage?? :p
[Nexus One Android Development] uoY_redruM:
Dude, Storm, your getting your N1 to top out at 1300MHz without crash?! With WMs kernels, I couldn't get 1267 to run...it was an instant crash. 1228 use to work with his old kernels perfectly, but the new ones don't run on my phone anymore.

If that's the case, you mind uploading one as a .zip that can just be flashed? My driver files are all ****ed and I can't get adb to work anymore on my computer. I've tried troubleshooting many different ways and cannot get it to work anymore.
[Nexus One Android Development] storm99999:
I'll get to that an a few hours, once I'm free. Edit: eventually. I'll probably pack it up in a user friendly way too, once I figure out how to do this.

I was frankly surprised about it too, but I've never had my phone crash from an overclock and AVS always undervolted to the absolute minimum the phone could give it. I must have an incredibly stable specimen of a processor, but I did note how terrible battery life was using it. I think AdamG overvolts it at such a high level.

I don't have much time to maintain a kernel, especially when I don't know the inner workings too well, but if interest is high, I could spend the time. I'll just git clone that repo and use Cyanogen configuration settings.

Anyways, way back on topic, how has changing the kernel's cpu throttle affected 3D performance? Any success stories? Lastly, I'm going to look into extracting a working source from the Liquid E fora. If it works as I think it should work, porting the new driver is far easier than I thought, but as always, I could be wrong.
[Nexus One Android Development] Dany0:
Neocore 31,8FPS DeFrost 3.0b @ 1,267Ghz
[Nexus One Android Development] elmerendeiro:
Holy sh...
[Nexus One Android Development] Dany0:
I wonder if I could go over 34FPS if someone would make a stable 1384MHZ kernel.

Anyone?
[Nexus One Android Development] ax0r:
wow bro, 1384 mhz. thats some crazy ****
[Nexus One Android Development] skorpioneMM:
My N1 also support the 1267 MHz kernel without 0 issues and no freezes, i got lucky :)
[Nexus One Android Development] Dany0:
So where's storm? What's the progress with the acer driver portage?
[Nexus One Android Development] madj42:
Be patient. It's only been two days since he last posted and it's probably not something that can be whipped up in a couple of days. He does have a life (well I'd hope) outside of this. :D
[Nexus One Android Development] storm99999:
Sorry all, I'm really busy right now. School just started and I'm taking the maximum number of classes they'll let me. I don't exactly have much free time on the weekdays anymore. Does anyone know if there is any AOSP development on the Liquid E? Do those roms have the same performance? I may need the source for a few core libraries in this project, as I suspect a coming issue.
[Nexus One Android Development] Dany0:
No those GPU+ drivers make OCing much more unstable and the speed boost is not that big as it should.

Wait.. School? What school?
[Nexus One Android Development] storm99999:
Alright, I busted open a rom, and it distinctly has absolutely no distinguishing features. They have the same libs, the same file sizes, the same names, everything. There appears to be no big binary blob that should be particularly adept at OpenGL.

Of note, it is a AOSP CM rom, but it is described as being based on the Liquid E official roms. This hints at it being outside of the rom again, or they removed the driver and replaced it with the current N1 driver.

I'll poke at others later on.

Oh, and school, yeah, I go to UNM, member of the Chemical and Nuclear Engineering department. Fun times.
[Nexus One Android Development] Dany0:
Haha well, good luck.
[Nexus One Android Development] dogiedogie:
While we are on the subject of clock speeds again, why are mainstream Desires all capable of .267 yet most N1s only .113?
[Nexus One Android Development] Dany0:
They all are capable the same. 50% do max 1267, and 50% 1384 and maybe even more.

The problem is voltage. Just most of the roms are undervolted, and some devices might not do very well even on stock volatage. Simply overvolt your device to 1350mv and it can do 1384 easily. But too big voltage might damage the device! Too low as well.
[Nexus One Android Development] dogiedogie:
Cheers. Just seems the Desire forums are FULL of them, where as I cant see any publicly on the N1 forums. Id love to have the option in set cpu to attempt speeds like that, at those 'higher' voltages.
[Nexus One Android Development] babijoee:
Just flashed the new 3d drivers from the leaked G2 rom and i'm sure storm99999 has already. doesn't work. screen is on but logcat says broken display. so i'm guessing as storm99999 has also suggested we need a new fb for these drivers to work.
[Nexus One Android Development] storm99999:
Um... What?! There's drivers in that mess? Where? I must've not been paying attention. Anyways, the problem is that the G2 most probably isn't using the same gpu. If it were, then all that we would need to do is get a 2.6.34.5 kernel, enable the option, hook the libs into initramfs and it'll boot. Someone finished the new framebuffer for us already.

Edit: Also the prevalance of overclocked kernels is partially peer pressure. Cyanogen won't use them as, rightfully, he fears they'd toast the device. CM is the biggest game here, so kernels tend to follow in those footsteps. That, and more of us paid full price for our device, so we have more value placed on it. There shouldn't be a binning difference between the chips. If anyone wants me to, I can tend an AdamG port for here, 1.3 Ghz max, update once in a while, and they sync with CM (daily I think), but I wouldn't clock it to 1.3 myself except for ego on linpack.
[Nexus One Android Development] dogiedogie:
I'm still looking for my 'forever' build, so ta anyway.
[Nexus One Android Development] fuinhu:
G2 uses a different GPU, Adreno 205 i guess, let's try to figure out something
[Nexus One Android Development] Dany0:
Nope it has Adreno 200.
[Nexus One Android Development] storm99999:
Well, that's interesting. I'll put it on my queue of projects to try out.

They massively improved 3D performance on the MSM7x30 chips compared to the QSD8x50, and it's all on the same silicon?

Edit: Wikipedia says no,but it's worth trying.
[Nexus One Android Development] Dany0:
I don't know about the graphics boost in MSM but I am sure the Adreno has some space for improvement, and not just a bit. At least at the power of Droid X, and maybe even a bit more. I was even thinking of some app to tweak global graphics quality.
[Nexus One Android Development] Androith:
IloMilo 3D Game running on Qualcomm's MSM7x30 (Adreno 205 GPU)

[YOUTUBE]SIkb_kDbrRE[/YOUTUBE]

Adreno 200 is outdated. Life goes on
[Nexus One Android Development] Dany0:
Actually... Adreno 205 was BEFORE Adreno 200, which, AFAIK, Adreno 200 was selected in the snapdragon CPU to lower the power consumption @ 1Ghz.
[Nexus One Android Development] Jack_R1:
Wrong.

http://smartphonebenchmarks.com/for...no-205-and-how-does-it-compare-to-other-gpus/

Some errors in this article, though. QSD8x50A and MSM8x55 aren't dual-core.
[Nexus One Android Development] tolis626:
Did you see the part about the Adreno 220?WOW!Just WOW! :D
[Nexus One Android Development] NeoS:
Did you see that wallpaper before the guy started the game in that vid? Awesome!
[Nexus One Android Development] Dany0:
I don't know how about you but I saw numbers Adreno 200, 210 and 220 in 2008, AFAIK I saw the 205 planned a little earlier, just when they bought imagino(well ATI/AMD stocks)
[Nexus One Android Development] mortzz:
http://www.youtube.com/watch?v=x8aKB77c1Hs

Edit: I have no idea how to embed YouTube videos on this site :(
[Nexus One Android Development] Jack_R1:
The name "Adreno" appeared only in 2009 after Qualcomm acquired AMD's ATI mobile graphics, so you couldn't have seen those names and numbers in 2008 in any possible way, because they didn't exist.

http://en.wikipedia.org/wiki/Imageon#Renaming_to_Adreno

But it's completely off topic. The only thing I wanted to bring in this thread is a couple of questions - 1) Are 200 and 205 compatible? 2) Is the current 200 driver we have lacking OpenGL ES 2.0 support? 3) Might the new driver be backwards-compatible with 200?
[Nexus One Android Development] Dany0:
Huh that is really odd...

---

oh no it is from 2008:

http://www.youtube.com/watch?v=A_daMQJ1jck

So to answer your questions:

1.) Bloody yes. Why do you think they are not? How could it not be? Impossible even in my worst nightmares!

2.) Eh.. you'd not be allowed to run nenamark if not

3.) Of bloody course

I'm getting british, duh
[Nexus One Android Development] storm99999:
1. No idea.

2. No, we have "slow" GLES 2.0 support.

3. It is difficult to know until we get the Linux source on one of these devices. Running the G2 kernel is pointless as it has completely different memory maps and board data so the system dies. With that being said, everything I've read leads me to believe that the Adreno 205 and the 200 are compatible architectures but with the 205 having "more" of basically anything.

On another unrelated note, I've still not tracked down the LiquidE driver. It has to be somewhere.
[Nexus One Android Development] Dany0:
You mean the bad driver?

didn't someone post a link on the older overclocking thread?
[Nexus One Android Development] storm99999:
"Bad", or current. Either or.

That was for the kernel implementation. It's now implemented in kernels outside of staging, so it's a matter of flipping a switch. Heck, the kernel I posted earlier in the thread had the feature enabled, just nothing to take advantage of it. What we need is the closed source part which still alludes me.
[Nexus One Android Development] babijoee:
LiquidE driver for userland?

I've think i've got that and the normal liquid drivers from userland. Not in kernel :p

If you need anything else pm me and i'll see if i can provide it :)
[Nexus One Android Development] storm99999:
Yes, the userland. I couldn't find them for the life of me, where were they?
[Nexus One Android Development] babijoee:
Can't remember i just remember searching for them everywhere and finally found it. i'll pm it to you
[Nexus One Android Development] storm99999:
Thanks. I already have a kernel with disabled kernelland drivers and enabled userland ones to test it with. I'm not sure if I need to weave it into the initramfs though. We'll see what we have to work with.

Edit: Fun fact, tying in to the last thread, there was actually a code required to modify the clocks. We had to send a start and an end signal, so manually changing what was sent really screwed it up. Still, we know there's no improvement to be had there.
[Nexus One Android Development] babijoee:
Just pushed the libEGL_adreno200.so and libGLESv2_adreno.so from liquid e and it works this time.. dunno why it didnt last time. Anyways from logcat i can see there are updates but we're not using them

I/nena ( 1189): [t/dt 61575 5758] WARNING: Unused attribute a_texCoord in program 39 index 0 location 0

I/nena ( 1189): [t/dt 61575 0] WARNING: Unused attribute a_vertex in program 39 index 1 location 1

I/nena ( 1189): [t/dt 61576 1] WARNING: Unused uniform u_anim in program 39 index 0 location 0

I/nena ( 1189): [t/dt 61576 0] WARNING: Unused uniform u_modelViewProjectionMatrix in program 39 index 1 location 1

I/nena ( 1189): [t/dt 61577 1] WARNING: Unused uniform u_screenRes in program 39 index 2 location 2

I/nena ( 1189): [t/dt 61577 0] WARNING: Unused uniform u_normTex in program 39 index 3 location 3

I/nena ( 1189): [t/dt 61577 0] WARNING: Unused uniform u_reflTex in program 39 index 4 location 4

Edit: now i tried running G2 drivers and they are working too

benchmarking atm best so far is 16.4 fps

G2 1.1 gles breaks screen :(
[Nexus One Android Development] storm99999:
Well, after all this time, I found a LiquidE source that actually is supposed to compile! It still doesn't yet, I need to find out where kzalloc and the like are defined as they're missing header definitions, but I'm working on it.

Edit: I got it to compile, it was just missing #include <linux/slab.h> at the top. Let's fire this bad boy up.

Edit2: Bah! It's the old driver. Now I'm going to go on a lead from inside a config file.
[Nexus One Android Development] babijoee:
good luck :) crossing fingers
[Nexus One Android Development] storm99999:
I sincerely think I'm working with CM based drivers. These all have identical performance to CM without the speed boost the userspace governor conveys. I get a soild 16 on nenamark.
[Nexus One Android Development] babijoee:
Could be possible, maybe people use CM drivers as it gives better performance..

Edit1: so its possible the improvements are hiding elsewhere?

Edit2: I have some acer drivers which dont have CM in it. Not sure if its E or S.

Want to give those a go?
[Nexus One Android Development] storm99999:
They probably are hiding elsewhere, and I think I found out where. When I first looked through the Acer source, I didn't know that the kgsl stuff was under drivers/char, which doesn't make sense to me. I'm trying to port that, of which they are CodeAurora work from 2010 instead of Google 2009 everyone uses. Too bad it bugs the hell out so far.

Edit: CodeAurora's git repo is broken right now... I found one of the files in my source is, to put it mildly, really broken. Half of the functions just say "return 0" instead of doing anything.

Edit2: I'm done for the night. I can't continue unless the codeaurora repo is working, and it's not tonight. I was very close too, all but kgsl_drm compiled.
[Nexus One Android Development] charnsingh_online:
I can easily get to 21 fps with cm kernel stock. Idk how u guys barely reach 15-16. I don't have my laptop with me so can't check
[Nexus One Android Development] babijoee:
What? i've never got that high. Even when OC i dont get that. Anyways i'm running on stock CM kernel aswell so you've obviously got something going on there

Edit: Okay decided to do full wipe and clean install of cm rc3 wow 32.1fps in neocore and 20.6fps in nenamark :)
[Nexus One Android Development] Dany0:
Hey guys just a quick note,

there's that korean LG phone called Optimus Z, which is something between the Nokia X6, iPhone, Nexus One, Droid X and HD2 but with a really good screen.

And it has improved drivers aswell(same CPU/GPU too), 1-2FPS boost no probs. I think they used a different "trick" to get better FPS, you might wanna check it out. But I don't think there are any codes laying around.
[Nexus One Android Development] NeoS:
Whait guys, are we talking Cyanogen Mod or the Common Lite profile for OpenGL es? I think we're confusing one with the other here...
[Nexus One Android Development] Dany0:
Yes they're talking about Cyanogen Mod new drivers.
[Nexus One Android Development] babijoee:
its displaying at 640x480, so that would give it a boost.

@neos2007 we think they might be cyanmod drivers as all results are equal. hopefully storm figures out where the actual performance increase comes from, I hope he's right with the kgsl stuff
[Nexus One Android Development] storm99999:
Yeah, the drivers are cm. After seeing so many kernels, you learn quickly which driver tree they are using. That particular one was a cm branch from about a month ago. Code Aurora is back up, so expect me to be posting updates in a few hours after class.
[Nexus One Android Development] Dany0:
Oh, woops then

Cool! Can't wait what comes from this :)
[Nexus One Android Development] storm99999:
Thank goodness for T3 lines. I'd snap if I had to download several GB of kernel source on anything slower.

Anyways, I have several plans of attack, so this may take a while.

Edit: It appears that the CodeAurora android enablement project has support for the HTC Passion in the dev files. Hopefully, I don't have to sync in a differing kernel.
[Nexus One Android Development] ax0r:
Storm I love you bring life to my graphics
[Nexus One Android Development] shiro836:
If I set the cpu governer to userspace i get 21fps in nenamark... I got 15-16fps with ondemand..