January 29, 2012 in C++, Java, JNI, NDK, OpenGL, Tutorials, Tutorials
If you want to use FreeType in your native C/C++ Android app, you’ll need to cross-compile it. The Android system uses FreeType internally but it doesn’t expose it to native apps.
Here is the full tutorial on howto use it in your project.
[Latest version of these instructions can be found at the OpenGL Wikibook]
January 29, 2012 in Applications, Firmware
Well i got the job to root the samsung Galaxy Tab 10.1 (gsm model sold at orange) , In Romania is sold as GT-P7500
Sweet device , it looks like what i want for my next Xmas or sooner 
Warning to recognize the device as storage at step Completing the Root you need to install Samsung Kies or the usb driver for samsung (and reboot)
Update: seems that with all my will the windows/ubuntu couldn’t recognize the device as storage so i have shared root file zip Samsung_Galaxy_Tab_10.1_root.zip on my one account and then have downloaded to the sdcard as in the tutorial the http://ur1.ca/7xnj3
ps:Finally i can type to the screen without misspelling the word , I love the screen size and the speed (dual core)
Only the browser is a little bit lagging compared with my Lubuntu desktop experience , I wait for a real chrome on android devices to speed up the browsing experience
January 27, 2012 in C++, Java, JNI, NDK, OpenGL, Tutorials
I got myself a second-hand Samsung Galaxy S at last, and started hacking on it!
The very first thing I wanted to try was porting the OpenGL wikibook C++ samples, that we wrote with OpenGL ES 2 in mind.
I started writing a minimal GLUT-compatible wrapper to run the samples as-is, using the Android NDK, and I’m making progress The Android NDK is getting nicer with Android 2.3, though it still feels less supported than Java apps (e.g. the resize events seem buggy and the keycodes header is incomplete…). Nonetheless, it’s nice to be able to write C++ portable apps.
You can see how to use the wrapper, and how it works internally, at:
http://en.wikibooks.org/wiki/OpenGL_Programming/Installation/Android
One of the limitations is that GLES2 is not a true subset of OpenGL 2.1, in particular:
I needed to pre-process these differences away, checking on GL_ES_VERSION_2_0 in the C++ source code to define a GLES2 macro in the shaders:
#ifdef GLES2 varying lowp vec4 f_color; # else varying vec4 f_color; #endif
Is there a better way?
ED: see the article comments for some good tips
January 26, 2012 in WebGL
In November, we announced that we were the first phone manufacturer in the world to support WebGL in the native Android web browser on Xperia™ phones. As a next step, we are now very excited to release our WebGL implementation for our coming Xperia™ phones running Android™ 4.0 (Ice Cream Sandwich) and above as open source. Read more after the jump, as Anders Edenbrandt, Senior Software Architect, explains more!
January 24, 2012 in JNI, NDK, OpenGL, Tutorials, Uncategorized
I eventually got myself a Galaxy S and started implementing this GLUT
wrapper idea!http://en.wikibooks.org/wiki/
OpenGL_Programming/ Installation/Android It currently works for tutorials up to “teapot“.
I’d greatly appreciate your feedback
Regards,
January 24, 2012 in News
by The Admin
January 24, 2012 in Site
Because of some issues with the site theme, unfortunately we had to revert to a default theme until we will fix the issues.
Sorry for the inconvenience.
January 4, 2012 in Uncategorized
I found Japanese tips on building 4.0.x and following them now i could create the daily iso for asus laptop and eeepc ,
soon i will publish the iso and usb images daily
The only thing i forgot is that now lunch is needed after build setup env is done
. build/envsetup.sh make clean make installclean lunch asus_laptop-eng make-j12 iso_img
wait and then burn the iso and boot on a asus laptop
January 4, 2012 in Uncategorized
The Android-x86 project is glad to announce a new test build 20120101 for public testing. This is a test release for android-x86 4.0. Live CD ISOs are available from our sites, as usual
January 1, 2012 in Uncategorized
Jean-Baptiste Queru reflects on the ups and downs of the Android Open Source Project in 2011.
Well, the work year is over for me as today was my last day in the office before the new year.
This closes my 3rd whole year working on the Android Open-Source Project (my involvement in 2008 had been quite minor). It’s been an interesting year for AOSP, full of contrasts.
On the positive side:
-I finally managed to distribute some proprietary hardware-related binaries for the very first time. This is an issue that I had been working on since before the G1 even shipped, and it finally became reality. For me personally, that’s really a huge deal, because it really makes it practical to take the AOSP code, modify it, install it on a phone in a way that actually works, and to distribute the resulting image. This enables community builds of AOSP in ways that were not possible before, thanks to a license that allows redistribution.
-I also finally managed to distribute some factory images for the very first time. Just like for the proprietary binaries, this is the result of 3 years of work. The main benefit is obvious: play with an AOSP build for while, and then get your device back to its factory state, over and over and over. It also has some other nice advantages, e.g. it allows AOSP users to stay up-to-date with the latest bootloader and baseband firmware.
-For the first time, AOSP supports a non-Nexus non-ADP device, which also happens to be a tablet (Xoom), and supports a development board (PandaBoard). We also added support for Intel CPUs, including emulator support. Those show well that AOSP is important for companies other than Google.
-We also got some proprietary binaries submitted directly in AOSP instead of being separate downloads, e.g. the touchscreen firmware for Galaxy Nexus and the Wifi/Bluetooth firmware for PandaBoard.
-We reached the point where AOSP is running on 11 different targets (8 different devices from 4 different families, plus 3 virtualized or emulated systems).
-IceCreamSandwich was a massive release, which added over 220,000 changes over Gingerbread. As usual since Froyo, the full source history is available, so that people can easily study how the code evolved, or research when, why and by whom a given line of code was written.
-With IceCreamSandwich, we now have a fully Open-Source NFC stack and a fully Open-Source sensor processing chain. In Galaxy Nexus, we also have a wifi/bluetooth chip that can work without requiring any proprietary firmware.
-I tagged 26 device releases in 2011, compared to 12 releases in 2010.
-I fine-tuned the process that we use when releasing GPL source files, so that it’s now much easier to build the GPL source code independently from full platform releases.
-We Open-Sourced the source.android.com site itself, thanks to the work on the intern who took care of that in the beginning of the year.
-Last but not least, the AOSP team grew, and that allows us to split the workload: +Conley Owens takes care of the long-term engineering while I manage the day-to-day execution. Conley gets credit for implementing the auto-verifier that we had running on Gerrit for a while, for dealing with many build issues that appear on various environments, and also for a lot of other work that’s not visible yet but that’ll make things even better in the future. All that happens under the watchful eye of+Dan Morrill who occasionally stops by to say hi, and with a lot of help from Google’s main Open-Source team.
“Not releasing the Honeycomb source code was catastrophic for the AOSP community. I had never before received so many angry emails, so many threats, to the point where I had to take several weeks off at some point to get away from it. Even today, there’s a lot of bitterness left on all sides. From start to finish, Honeycomb probably cost AOSP anywhere from 6 to 12 months.”
Recent Comments