yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Dany0:
Yes, and I found one book:

http://www.amazon.com/OpenGL-ES-2-0-Programming-Guide/dp/0321502795

But it's expensive and I can't find it in Czech Republic, what the... Also some other books, but for iPhone:

http://www.amazon.com/iPhone-Apps-Blender-SIO2-Open-Source/dp/0470574925/ref=pd_sim_b_7

http://www.amazon.com/iPhone-Progra...plications/dp/0596804822/ref=pd_bxgy_b_text_b

http://www.amazon.com/Beginning-iPhone-Games-Development-Cabrera/dp/1430225998/ref=pd_bxgy_b_text_c

http://www.amazon.com/iPhone-Game-Programming-All-One/dp/1435454782/ref=pd_sim_b_5

So if you find those as ebok, tell me ;)

Oh wait there is one in Czech Republic, great!

http://www.reading.cz/koupit/OpenGL...54350/?lista=prehled&zprava=hlidaci_pes#lista

and they make e-previews! Even better.
[Nexus One Android Development] tolis626:
Any news with the Gingerbread stuff guys?Or have you done anything with what you've been working on Dany0? :)
[Nexus One Android Development] Dany0:
The answer is easy:

No, I don't have money and I can't buy any of these books, the material on the internet is either outdated or misleading, and since I have no material to work with...

We wait for Nexus S to be released, when it's released the AOSP(source code) will be out, and then I/we can work on this.

But something I have found is that it's really easy to convert glES2.0 to glES1.1 - and that would be a huge performance boost in games like asphalt or brothers in arms 2. Though I think forbidding to render transparent textures would be more effective and easier to do.

edit:

oh yeah the AOSP is out! But I don't have enough HDD space to compile it =/
[Nexus One Android Development] tolis626:
:eek:

That must be a big source code!Or a small HDD! ;)

Anyway,we can all thank you for your effort pal!If someone could pick it up now that Gingerbread's out it would be cool! :)
[Nexus One Android Development] Dany0:
My effort? I've done nothing :D storm is the guy who compiled few kernels.

And yes, the small is the HDD. The source is 2gb(kinda big taking the fact it compiles into what, 60 megs? and oxygen is even smaller lol), and they say you need 6gb free to compile it. Counting I don't have any prequisities(except python and an old version of eclipse) on my pc installed, and I have 6,33gb free... no I will not risk it again. The last time I had 10 megs free xp didn't start.
[Nexus One Android Development] m0narx:
Hi, I have found a strange thing...

If I replace my file \system\lib\egl\libGLESv1_CM_andreno200.so on HTC Desire with same file from HTC Desire HD.... Qudrant shows 35fps on 2D test (with original only 18), but 3D isn't work at all...
[Nexus One Android Development] Dany0:
How much RAM do you have left after? Could be that Desire HD has more RAM they've made it to share more of it with the adreno. And Adreno 200 doesn't have a few things from 205 so... this might be the problem.
[Nexus One Android Development] Dany0:
I'll be trying to look at it again if I s-off properly :D But first really need to finally buy that **** tablet...
[Nexus One Android Development] Dany0:
s-offed. waiting for the tablet man to arrive :D
[Nexus One Android Development] Dany0:
Okay tablet arrived, then my stupid parents broke it and it doesn't charge. And they don't to pay the send back to china... Grr

So how's it going over here? Anyone still interested? There is still a lot of room for improvment!!
[Nexus One Android Development] @rj*n:
The people are interested but the development has been almost nil here and I'm a simple XDA-er who can't read codes so can't help much here :$

How about now mate? Can you try compiling now again?
[Nexus One Android Development] Dany0:
just bumping in case someone's going to get interested.
[Nexus One Android Development] storm99999:
Alright, I got it to compile with the new framebuffer, but it wouldn't boot. Anyone know how to check what went wrong?

Edit: Finally, I know how to figure out how to debug a crash, and the problem is:

[ 10.552703] irq clk setup
[ 10.552856] can't get mdp_clk error:-2!
[ 10.552978] irq clk setup done
[ 10.553192] mdp: probe of mdp.0 failed with error -2
[ 10.553375] can't find mddi_clk
[ 10.553497] Unable to handle kernel NULL pointer dereference at virtual address 0000004c

Edit2: found the bug, it concerns all implementations of getting the clock in certain files, they use clk_get(NULL, "mdp_clk") instead of clk_get(&pdev->dev, "mdp_clk") as implemented everywhere else. Too bad &pdev isn't initialized in these points...

Edit3: Oh crap... the problem is that it needs the clocks whenever the driver is initialized. The problem is that the driver cannot be initialized with &pdev active. Either we disable any clock calls or find a way to fake a &pdev.

Edit4: Disabled that, now the issue is the 3rd line there, insofar that probe of mdp.0 failed with error -2. There is no error -2, all positive values are defined, but if it was 2, that's file not found.

Edit5: Figured that out, here's what's up. I have the driver implemented, but when the kernel tries to probe the mdp driver, it tries to set the clock. In the old driver, this works without fail, but in this driver, it doesn't, so it returns the pointer in error, this pointer refers to nothing, code fails. Once we get beyond this, it should boot without fail. I rechecked just now, the mdp_clk is accessed using the same method in the other older framebuffer more or less. There's a new IRQ locking mechanism, but that's all. The only thing that could be wrong is that either it's not supposed to be called with the NULL (see edit2) and &pdev is wrong somehow, or something is preventing the clk call. I really have no idea what's going on, I'll try again tomorrow.

If anyone's interested in checking in on the code, if you've followed what I've done, it's in drivers/video/msm/mdp.c in mdp_probe(), else it'll be in any .35 kernel under drivers/staging/msm/mdp.c
[Nexus One Android Development] tolis626:
Any progress guys?

Also,will a hypothetical success of this improve the video recording capabilities of our devices or does that concern only the CPU?
[Nexus One Android Development] NeoS:
Clock issues... We've had those on the Winmo MSM project too. Seemed like there was an incompatible Core.dll file, which, of course, is the core of the system. I don't know Android kernel development, so I'm afraid I can't help you out there.

I do however like to know what the difference is between our N1 and the Acer, so we all know what we can get out of this project. (hint to joe ;))

And good luck storm, you're doing great so far, seeing your logs. I know alot of devs jumping in on this would really appreciate that.

edit: and no, this won't change the videorecording capabilities. It's the GPU (aka videocard in pc's) that will be used fully. Consider this:

You have a brand new Windows 7 pc and want to play a new game like Starcraft 2 for example. If there are no GPU drivers installed on the system, the game won't run, or run very slow, with artifacts and all that. Now, If you install the latest videocard drivers, the game runs perfectly and the PC's CPU offloads most task to the GPU, which makes it alot faster.

That's what this project does for the Nexus: install the correct videocard driver. ;)

edit2: I saw the glbenchmark from the first post. There are very minor improvements over the Nexus, GPU wise. Are you sure the Liquid has a fully working driver babiijoee?
[Nexus One Android Development] storm99999:
I kept such detailed logs as I kinda expected to hit a wall like I did, completely burn out, and find something else to occupy my mind. If I saved anyone ten minutes, my writing all that out will have been worth it.
[Nexus One Android Development] babijoee:
well its more optimized than our n1. we shall hopefully see one day
[Nexus One Android Development] tolis626:
Well,as irrelevant as I may be,I know what a good driver will do for us.I just wondered if it could help because,as you said,the CPU offloads some things to the GPU.And nowadays,graphics cards have video encoding/decoding capabilities.So I just though,hell,why not?
[Nexus One Android Development] fstluxe:
any news here?
[Nexus One Android Development] babijoee:
well iR hasn't got back to me yet and storm99999 is occupied with his other project which is still awesome. hopefully google/htc will give us a little push push in the right direction when gingerbread is ready.
[Nexus One Android Development] Dany0:
soooo dead thread?
[Nexus One Android Development] HairyMerkin:
Give it time..
[Nexus One Android Development] patelkedar91:
I hope this goes somewhere. I really want to improve the Adreno GPU. I feel as if this can be possible to finally have no worries with graphics on my Evo.
[Nexus One Android Development] storm99999:
What we're waiting on is the msm-fb-staging driver. It has support for the newer driver, but it is not done. You see, the one on the Acer Liquid E does not compile, and it is in much of the same state of un-done-ness as the linux-mainline kernel. In the mainline, there is a to-do list, the most prominent of which is to add support to the old FB implementation.

What happens is that the entire system appears to be rewritten to support the incomplete framebuffer in the Acer, but we would have to reverse engineer it to do the same. I'll wait until the kernel team finishes this. Then, porting will be easier, much easier. It'll take time.
[Nexus One Android Development] patelkedar91:
Thanks for the update.
[Nexus One Android Development] Dany0:
Ok just a quick question. If there is Liquid E driver successfully compiled, what'd you focus on, optimizing the original quallcomm driver or continuing with the Liquid E driver?
[Nexus One Android Development] storm99999:
We have no idea where the performance is to be had. The Liquid E driver has a new framebuffer and a new main driver, and either could be the performance bump we are looking for. However, if it's the latter, I'd suggest we focus only on the Liquid E, there is no easy way to optimize a driver we don't have the code for.
[Nexus One Android Development] Dany0:
okay thanks for response
[Nexus One Android Development] roteplex:
Acer Liquid Benches

GLBenchmark HD ES 1.1 CPU Skinning :	1766 Frames

GLBenchmark HD ES 1.1 GPU Skinning :	1680 Frames

GLBenchmark Pro ES 1.1 CPU Skinning :	606 Frames

GLBenchmark Pro ES 1.1 GPU Skinning :	256 Frames

CPU Performance

CPU Performance: Float :	2932

CPU Performance: Integer :	15491

Nexus One Benches

GLBenchmark HD ES 1.1 CPU Skinning :	1518 Frames

GLBenchmark HD ES 1.1 GPU Skinning :	1279 Frames

GLBenchmark Pro ES 1.1 CPU Skinning :	514 Frames

GLBenchmark Pro ES 1.1 GPU Skinning :	178 Frames

CPU Performance

CPU Performance: Float :	3527

CPU Performance: Integer :	22805

Cmon, even at 768Mhz, Liquid is much faster, atleast in the graphics area. Why does HTC neglect graphics so much, a problem since the titan days. Hmmmm........
[Nexus One Android Development] babijoee:
they definitely need a better GPU driver development/kernel team
[Nexus One Android Development] Dany0:
Whenever Cyanogen touched something it turned to be awesome, we should invite him IMHO.
[Nexus One Android Development] patelkedar91:
Couldn't this account for some of the improved graphics (not all)?

NexusOne is 854x480

Acer liquid is 800X480

I just thought about that.

Though why not just bug HTC for drivers? They're pretty responsive.
[Nexus One Android Development] B3astofthe3ast:
They are both 800x480.
[Nexus One Android Development] Dany0:
N1/Desire has 800x480 not 854x480. 854x480 is in some motorolas

ohkay

nice idea, someone should try
[Nexus One Android Development] patelkedar91:
Oh okay, my mistake. I don't know how I forgot.

Anyway, some Acer Liquid A1 users have noticed that graphics benchmarks are higher.

Again, all my support... which is just me screaming from the sidelines.
[Nexus One Android Development] Dany0:
The biggest advantage of the Liquid A1 as you call it is that it uses Android 1.6.

It's much faster, don't forget the fact that it's older, and since 2.0 Android got MUCH more sophisticated.

With 2.2 it'll be just half the boost. But it's worth it. And it feels better IMHO
[Nexus One Android Development] :
you guys should check out this thread, and maybe speak with the author

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

although its for winmo it may be able to help since it is for the hd2 which is also a snapdragon device.
[Nexus One Android Development] NeoS:
Chainfire is definitely the person to talk to if you want to improve 3D drivers. Also, NuShrike, but I haven't seen him on the boards since some ignorant people cast him away. :mad:

I've been doing 3D drivers on Winmo for a while now, but I know zilch compared to these guys.
[Nexus One Android Development] Dany0:
I'm contacting these guys.
[Nexus One Android Development] Chainfire:
I have no clue, would have to look at this indepth. But I don't have any Snapdragon Android devices, just MSM7Ks and Hummingbirds.

Also, I'll be out of touch for two weeks.

EDIT: Also, driver scores seem to be pretty on-par with WM/HD2+Turbo3D ...
[Nexus One Android Development] Dany0:
I thought you have HD2. Aren't there Android ROMs for it? BTW thx for visiting. ;)
[Nexus One Android Development] elmerendeiro:
thanks for visiting chainfire!
[Nexus One Android Development] Dany0:
Hmm where's NuShrike? \=
[Nexus One Android Development] Chainfire:
Some idiots chased him off. Think he's currently working on symbian stuff..
[Nexus One Android Development] Dany0:
Lol what? How can someone chase someone off a forum? LMAO
[Nexus One Android Development] NuShrike:
Check out my signature. Also doesn't help that Clove Technology ripped me off and still owes me $5xx.xx for a phone. They literally/physically still have my RMA since Dec 2009, and Brit courts isn't making it easy to recover it. Lots of expensive doc filing.

Meantime, did some WinMo/Qt work for personal gfx app project. Qt def is Nokia-focused now and starving off WinMo with contribution neglect. Job searched. Testing mattc Froyo.

I'll look here but I figured Android finally got decent support to not fix Qualcomm plumbing again. :-)
[Nexus One Android Development] storm99999:
It's not so much Qualcomm's poor support, it's that Qualcomm had a "good" driver for a while that everyone uses, but a month or so ago had a "great" driver that they haven't even properly ported the framebuffer to old devices.

A few others and I have compiled the framebuffer and the new drivers, but once SurfaceFlinger starts up, there appears to be nothing to correctly hook onto and the phone crashes. In addition, there's a large mess surrounding the binary-only driver, like where it is and how to load it into the kernel. I'll get back to work on that, as I think I know where it is.
[Nexus One Android Development] Dany0:
Wow man, that's... wow.

Regarding that e-shop that ripped you off. Might be you'd want to contact few hackers, you know it's not just a myth. An hour search can lead you to any dark/white hacker IRC. You can make an agreement, dark hackers may make them go bankrupt(bad guys beat bad guys... well still better then Hollywood ;)) and send you your money back, but that may lead to problems. Or you can contact a white hacker team, they might erase the site and instead add there a bugging warning that this site tries to steal your money ;) Or DDoS their mail or... uh well, something? Well from what I can tell, I've seen a lot cases like this. Give them a warning and they'll piss their pants. It's legal(for you) and harmless.

EDIT:

Thanks storm! You're a great :)
[Nexus One Android Development] android.activate:
Dany0,

You could very well be one FBI test subjects. !! ;-)
[Nexus One Android Development] Dany0:
LOL FBI? Okay dude, just to pull you to the right way: FBI has an IT department. 98% of the people are complete BFUs that once read a book about microsoft office. 2% are proffesional russian hackers that are so skilled that if microsoft would hire them, they could fire everyone else.

Those guys are so stressed already, they won't look for some douch talking about everything knows. Also I am not in the USA so...

Eat my shorts; FBI :o
[Nexus One Android Development] babijoee:
hrmmm i haven't heard about this great driver :p hopefully it will get ported soon enough :) anways gl on your hunch :p
[Nexus One Android Development] Dany0:
Can anyone ask qualcomm/HTC about the drivers? Thanks.