Android NDK hits Release 3, brings OpenGL ES 2.0 access to devs
By Chris Ziegler 
posted March 8th 2010 6:17PM
posted March 8th 2010 6:17PM
We know from a brief spat of iPhone 3GS controversy that OpenGL ES 2.0 brings a new level of immersive realism to 3D gaming on mobile devices, so Android developers (and users, for that matter) should be delighted to hear that a new release of the official Native Development Kit exposes its capabilities to anyone targeting Android 2.0 or higher. As a refresher, the so-called NDK is a bolt-on to the standard Android SDK that gives folks the ability to write and compile critical pieces of functionality in native code, closer to the processor without that pesky Java virtual machine standing in the way -- in other words, it's exactly what gamers and game devs need to make Android a serious gaming platform, and better access to badass 3D capabilities are a fun little piece of the puzzle. The latest NDK's available for download now -- so seriously, hurry up and go wow us with your revolutionary first-person shooter. Git!
Called it. Figured this would be announced at GDC, but I guess they decided to jump the gun by a few hours. At any rate, it'll be great to be able to use the native support, rather than having to hackishly load the shared object file from my Nexus One every time.
Android ftw!
"in other words, it's exactly what gamers and game devs need to make Android a serious gaming platform"
It adds physical buttons to the hardware?
@Extinction
Uh oh, iPhone haters are seriously conflicted now...
@Extinction
There are physical buttons on some Android phones. But no dedicated gaming buttons are the reason why Android, the iPhone and similar won't be the proper place for actual in-depth games. Doesn't mean they can't support touchscreen casual games.
@TheGM The Cliq is the closet thing to having a game controller than any other Android phone(besides that one Ophone).
@TheGM
How about actual in-depth touchscreen games? Physical buttons allow accurate and well-timed input, but those aren't the only ways to add "depth" to a game. Good games don't have to be a dexterity test.
Hey Chris,
I know this is a little off-topic, but it's Android-related.
When you (or one of Engadget's finest) do the HTC Desire review, can you guys check on the multi-touch? I wanted to see if the issue with the N1 was resolved in this handset before I decided to buy it around April.
Thank you in advance.
@Wiizer I think the issue you're talking about was chalked up to a bug in the software. There's a video here talking about a different app that measures it correctly: http://www.androidcentral.com/throwing-fuel-nexus-one-and-moto-droid-multitouch-fire
@Serus That video is flawed, since the second multitouch demonstration application shows a symmetrical box instead of two actual points. The detected points actually swap corners of the box, but you can't tell from the second app.
There is a software hack to fix 50% of this problem, but it's not enabled yet (the framework basically normalizes the points it's feeding apps if they "skip" too far). Touch points getting stuck after crossing remains an issue.
@Wiizer I am pretty sure that it will still be present on the Desire.
@coolbho3000
Well, unless you have info to back that up, I'd like to hear that from Engadget myself.
After all, they're the gadget gurus.
@Wiizer
The issue is with the screen the Nexus One uses, which is Synaptic's ClearPad2000.
@thevoiceless
The reason I ask is because of this sentence at TechRadar:
http://www.techradar.com/news/phone-and-communications/mobile-phones/hands-on-htc-desire-review-670596?src=rss&attr=all&artc_pg=1
"It's a little on the large side thanks to packing a 3.7-inch OLED screen, but HTC has had a look at the few foibles the Nexus One has and sorted them out on the Desire."
@Wiizer I really don't see HTC changing the part they use for the Desire. It's a very, very similar piece of hardware to the Nexus One, and there's nothing on the Desire or Sense UI that would require precise multitouch gestures beyond pinch. HTC has no reason to change it, and changing the part would require costs to redesign and retrofit the new touch screen controller for the Desire. This is my gut feeling as an Android developer, however.
Yeah this will help the devs out :) I'm downloading to
2009 says hi.
@Titanium Man
dick.
@Titanium Man Yeah, tell that to all the (majority) iPhone 3G users, which are still stuck in 2007 (can't use 2.0 anyway).
The openness of Android plus killer gaming = WIN
@AlienSix only for Android > 2.0 though. It is amazing phones are still selling with Android 1.5. There are going to be a lot of upset people out there.
@jarobusa
Just like those who buy computers that only have enough resources to run Windows 95 are pissed that they can't run Crysis 2. C'mon, give me a break.
@Invader Par they are selling 1.5 phones today. Look at the Sprint Hero for instance. The average user will have no idea their brand new phone cant run the latest games.
@jarobusa Well here is to defragmentation of Android helping the cause
@Invader Par Thats computers made years sometimes a decade apart not phones released in the same year. That is a horrible comparison. If you ignore the fragmentation like google wants you to do then you will be spending a bunch of money.
@AlienSix
Open is officially a meaningless word here on Engadget.
@jarobusa
I wouldn't say the Hero is the best example here since that phone actually came out when 1.5 was new. A better example is probably the X10. Google really should really set a limit to how far back manufacturers are allowed to go with the OS versions to help this issue out a little bit.
@jarobusa Even though you can get a 'new' hero it doesn't have the hardware acceleration you would need for the highly graphical end of 2.1
@jarobusa
yes you can buy Android OS devices that may not be able to run the latest games.
you can also buy Windows based PC's like netbooks/laptops that can't run the latest games.
whether the game will actually start or not doesn't change the fact that the hardware isn't suitable, that's what researching your needs and the available options is about.
customers going into computer shops and asking if the netbook will run Crysis are the same as the people that should be checking if their Android 1.5 device can run their needed apps.
if the customer doesn't know what they want the device to for, then how is that the fault and responsibility of the device-maker and shop that sells it?
you're the customer, you know what you want the tool for, let the shop people know your needs and they will get you something sufficient. or do the research yourself and get what you know you need to get the job done.
buying something without knowing what you need it for like a trendy hipster and then complaining it doesn't do what you want is not the fault of the seller.
Can't wait :) I'm running Android full-on on my winmo phone and love it, and my plan ends in September so I can't wait to switch, and better yet the Supersonic will be out by then! :D
does this mean we finally get Halo 3 on my nexus one?
@creepin Only if you follow this recipe to exactly:
Take 1 nexus 1 add it to a blender. Next pour in 1 pint of nitroglycerin, making sure to add it gently so you don't blow your kitchen up. Now take two feathers on an Arch Angel and finely dice, adding the results to the blender. Next take one prayer from an apple hating engadget staff member and wrap in pure unobtanium leaf of no more than a Jame Cameron plot depth, and add it to the blender as well.
Now mod your blender for remote activation via iTunes and trek to the temple of gadgets in the foothills of the flamewars and switch your blender on.
If you have followed the recipe correctly, the full 1080p glory of Halo 3 should now be residing on your nexus 1 with your 360 controller attached for good measure.
If you have not, start rebuilding your house!
@creepin Ywah cause Microsoft is during to make apps for a google android phone. Cmon think about it
Catching up to WebOS.
Google Android's future is looking bigger and brighter everyday...
Now just keep AT&T out of the picture so that we don't have to witness another AT&T/Backflip fiasco.
Android is too fragmented......
@namyboyz44 Not really, you don't know what you're talking about.
@Luffy
Sorry dude. Android is the new Windows Mobile.
@Wesscoast All Android phones released in the US will be upgraded to 2.1. When the older fragmented versions of Android are more capable than the iPhone.
Nice try though.
@Luffy
Uh yes I do. Think of android as a PC. full of potential but since hardware is so fragmented games has to be very scalable which mean harder to develop and get full potential. Then you have playstation 3 and xbox which is one hardware and developers can utilize the full potential.
@TheGM
Even if all android phones upgrades to 2.1 there will still be a huuuge fragmentation. An example can be a game can be made for Window XP but that doesnt mean you meet hardware system requirements. I love Android, I just dont see it as a gaming powerhouse...WebOS is much newer then android yet has 3d games galore. think about it..
@namyboyz44 The Pixi won't be able to access all the game the Pre can. The 3G also has doesn't support 2.0 like the 3GS does. Android has tons of 3D games, many of which run on the G1, even if it doesn't run as well as the Droid or Nexus One. HomeRun battle is an example of a heavy 3D game that's on multiple phones including Android and the iPhone. It does work with the G1, but obviously runs smoother on the Droid and Nexus One in comparison.
@TheGM
Yes your exactly right. That is why android is even more fragmented then the Iphone and WebOS. With android you would have to test compatibility with the hero, eris, droid, nexus one, samsung moment, etc.... Android is well capable of 3d games. But developing for the Iphone and then scaling for 2.0 in 3gs will be easier then scaling for a bunch of different hardware. This is why Nexus one was built to have a stable system on Android. Hopefully it works out as i plan on buying one when it releases on Verizon.
So if the whole point of Java VM is to foster hardware abstraction and increase compatibility, and this Developer Kit is to allow you to write "closer to the processor," does that mean that every Android phone is going to need it's own version of a game written for it's specific hardware???
Are we going to be seeing 1/2 dozen versions of the same game??
@Hazdaz not if they write directly to the OpenGL library. The library will handle to different hardware.
@Hazdaz As jarobusa said: No. OpenGL ES 2.0 uses a standard interface. You don't need to mess around with the specific hardware in each phone.
@MarcusMaximus I don't think you got what he was asking. Yes, the programming interface will be the same across each phone, but when you compile to native code the code produced may be different for each phone depending on the processor used on the phone.
Driod does
But can it run.. ZIIING... I'll be here all week.. tip your server..
What about the limited storage issue with android? We're not gonna have much game to play with.