1. if you haven't already, create an AVD (android virtual device)
android create avd -n (name) -t (targetID) [-(option) (value)]
android list targets
2. list available AVDs
3. starting your AVD
for more information goto:
ANDROID: Starting the Android emulator
here's how to start your android emulator via command prompt:
1. if you haven't already, create an AVD (android virtual device)
where the target id (ie. 4 for android 1.6) can be obtained via:
android list targets
2. list available AVDs
\ android list avds
3. starting your AVD
\emulator -avd
for more information goto:
1. if you haven't already, create an AVD (android virtual device)
android list targets
2. list available AVDs
3. starting your AVD
for more information goto:
ANDROID: Installation errors
This is a part 2 to the previous post on installation.
During installation I received the following failure:
Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
You can turn on Logcat to debug the installation failure:
adb logcat
My Logcat yielded the following errors:
E/PackageParser( 74): Package com.website.mclass has no certificates at entry assets/; ignoring!
To solve this issue, you need to sign the apk file before installing. Here's how:
jarsigner -verbose -keystore (directory)\debug.keystore .apk androiddebugkey
The default passphrase is android
To verify the certification, you can again use jarsigner:
jarsigner -verify -verbose -certs (directory)\(filename).apk
The last command line printout should now read:
jar verified.
During installation I received the following failure:
Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
You can turn on Logcat to debug the installation failure:
adb logcat
My Logcat yielded the following errors:
E/PackageParser( 74): Package com.website.mclass has no certificates at entry assets/
To solve this issue, you need to sign the apk file before installing. Here's how:
jarsigner -verbose -keystore
The default passphrase is android
To verify the certification, you can again use jarsigner:
jarsigner -verify -verbose -certs (directory)
The last command line printout should now read:
jar verified.
ANDROID: Installing application
There are 2 ways to install a pre-built applications:
1. command prompt
adb install(directory)\(filename).apk
2. SD card
A. install the apk to the phone SD card
B. insert SD card to phone
C. goto Android Marketplace, search for Apps Installer application
D. open and click Install
E. open Apps Installer
F. select the application you want to install
G. click on install
1. command prompt
adb install
2. SD card
A. install the apk to the phone SD card
B. insert SD card to phone
C. goto Android Marketplace, search for Apps Installer application
D. open and click Install
E. open Apps Installer
F. select the application you want to install
G. click on install
ANDROID: adb shell commands
For the times you want to log onto the unix command prompt of the device itself, you want to use the following command:
adb shell
this will convert the prompt into:
#
now you can start using unix commands as usual:
ps = list all processes
kill = kill specific process
adb shell
this will convert the prompt into:
#
now you can start using unix commands as usual:
ps = list all processes
kill
OpenGL + OpenVG
Here's my findings on the 2 technologies:
Imagination Technologies:
AMD:
So... Theoretically the 2 technologies can only be combined if the following is satisfied: A single emulator/device, that supports BOTH OpenVG and OpenGL, sharing the same EGL libraries. In other words, the EGL must have support for BOTH OpenVG and OpenGL ES 2.0. The EGL is the key.
Imagination Technologies:
--------------------------------------------The two technologies are individually packaged, so there is no support for combining these 2 technologies at this time by imgtec.
| OpenVG emulator | OpenGL ES 2.0 emulator |
--------------------------------------------
AMD:
--------------------------AMD does not have a OpenVG emulator
| OpenGL ES 2.0 emulator |
--------------------------
So... Theoretically the 2 technologies can only be combined if the following is satisfied: A single emulator/device, that supports BOTH OpenVG and OpenGL, sharing the same EGL libraries. In other words, the EGL must have support for BOTH OpenVG and OpenGL ES 2.0. The EGL is the key.
-----------------------------------
| GL ES 2.0 | VG |
| ----------- |
| | | |
| | E G L | |
-----------------------------------
OpenGL: What is EGL
Taken from Khronos: http://www.khronos.org/egl/
EGL™ is an interface between Khronos rendering APIs such as OpenGL ES or OpenVG and the underlying native platform window system. It handles graphics context management, surface/buffer binding, and rendering synchronization and enables high-performance, accelerated, mixed-mode 2D and 3D rendering using other Khronos APIs.
EGL™ is an interface between Khronos rendering APIs such as OpenGL ES or OpenVG and the underlying native platform window system. It handles graphics context management, surface/buffer binding, and rendering synchronization and enables high-performance, accelerated, mixed-mode 2D and 3D rendering using other Khronos APIs.
OpenGL: Toggling the DepthMask
glDepthMask(GL_TRUE/GL_FALSE);
Sometimes in blending, you will want to inter-mix opaque & translucent objects.
Here's the 2 obvious scenarios:
1. If the opaque object is in front of translucent object, we don't need to blend
2. If the translucent object is in front of the opaque object, we need to blend
There's a easy way to ensure the blending always works as expected. This is to render the opaque object FIRST with the writable depth buffer. And then render the translucent object with a read-only depth buffer. This can be done by using glDepthMask.
This way the renderer will automatically compare the translucent object's depth position with that of the read-only opaque object depth position. Blending is done only when needed, and buffer remains unchanged.
Sometimes in blending, you will want to inter-mix opaque & translucent objects.
Here's the 2 obvious scenarios:
1. If the opaque object is in front of translucent object, we don't need to blend
2. If the translucent object is in front of the opaque object, we need to blend
There's a easy way to ensure the blending always works as expected. This is to render the opaque object FIRST with the writable depth buffer. And then render the translucent object with a read-only depth buffer. This can be done by using glDepthMask.
This way the renderer will automatically compare the translucent object's depth position with that of the read-only opaque object depth position. Blending is done only when needed, and buffer remains unchanged.
OpenGL: Blending Formula
Taken from the Red Book:
Let the source and destination blending factors be (Sr, Sg, Sb, Sa) and (Dr, Dg, Db, Da), respectively, and the RGBA values of the source and destination be indicated with a subscript of s or d. Then the final, blended RGBA values are given by
Let the source and destination blending factors be (Sr, Sg, Sb, Sa) and (Dr, Dg, Db, Da), respectively, and the RGBA values of the source and destination be indicated with a subscript of s or d. Then the final, blended RGBA values are given by
(RsSr+RdDr, GsSg+GdDg, BsSb+BdDb, AsSa+AdDa)
Expanded:
red = Red(src)*Red(srcBlendFactor) +
Red(dest)*Red(destBlendFactor)
green = Green(src)*Green(srcBlendFactor) +
Green(dest)*Green(destBlendFactor)
blue = Blue(src)*Blue(srcBlendFactor) +
Blue(dest)*Blue(destBlendFactor)
alpha = Alpha(src)*Alpha(srcBlendFactor) +
Alpha(dest)*Alpha(destBlendFactor)
OpenGL: Rendering Pipelines
Here's 2 flow-charts explaining the 2 types of rendering pipelines.
Here are some typical uses for the programmable function pipeline:
Done within the Vertex stage:
- vertex displacement mapping
- morphing
- particle systems
Done within the Pixel stage:
- per pixel lighting
- toon shading (I'm guessing this is cell-shading)
- parallax mapping
- bump mapping
- custom texture filtering
- color kernel applications
Here are some typical uses for the programmable function pipeline:
Done within the Vertex stage:
- vertex displacement mapping
- morphing
- particle systems
Done within the Pixel stage:
- per pixel lighting
- toon shading (I'm guessing this is cell-shading)
- parallax mapping
- bump mapping
- custom texture filtering
- color kernel applications
Win32: Setting up OpenVG
I'm completely new to the OpenVG sphere, so this is the very basic of basics. How to run the openVG RI from Khronos site...
First, I downloaded the RI from the site at: http://www.khronos.org/files/openvg_1_0_ri
Unzip the package, and attempt to run the bin\wind32\tiger.exe file
If you got a MSVCRTD.dll is missing, this is because you aren't using Visual Studio 6 (or some other prehistoric version).
I don't recommend this, but you CAN find MSVCRTD.dll online, and throw it into your System32 directory. I found the dll inside some symbian directory... threw it in my System32 directory, and the tiger popped up like a charm... after 2 minutes of loading...
The second, and preferred method, is to recompile the project using your version of Visual Studio (mine is V9). Well I got stumped again when I tried compiling. The application couldn't find GL\glext.h
To solve this download the glext.h from: http://www.opengl.org/resources/faq/technical/extensions.htm
Throw this file inside the VC/include/GL folder (create the GL directory if it doesn't already exist).
The full path of said directory is at (for Visual Studio V9):
C:\Program Files\Microsoft Visual Studio 9.0\VC\include\GL
Inside this directory I now have the following:
- glut.h
- glext.h
- glxext.h
- wglext.h
If you also need glut.h, you should refer to an earlier post I wrote about setting up GLUT on your system.
First, I downloaded the RI from the site at: http://www.khronos.org/files/openvg_1_0_ri
Unzip the package, and attempt to run the bin\wind32\tiger.exe file
If you got a MSVCRTD.dll is missing, this is because you aren't using Visual Studio 6 (or some other prehistoric version).
I don't recommend this, but you CAN find MSVCRTD.dll online, and throw it into your System32 directory. I found the dll inside some symbian directory... threw it in my System32 directory, and the tiger popped up like a charm... after 2 minutes of loading...
The second, and preferred method, is to recompile the project using your version of Visual Studio (mine is V9). Well I got stumped again when I tried compiling. The application couldn't find GL\glext.h
To solve this download the glext.h from: http://www.opengl.org/resources/faq/technical/extensions.htm
Throw this file inside the VC/include/GL folder (create the GL directory if it doesn't already exist).
The full path of said directory is at (for Visual Studio V9):
C:\Program Files\Microsoft Visual Studio 9.0\VC\include\GL
Inside this directory I now have the following:
- glut.h
- glext.h
- glxext.h
- wglext.h
If you also need glut.h, you should refer to an earlier post I wrote about setting up GLUT on your system.
3D: Shaders
did some research on shaders:
FROM: http://en.wikipedia.org/wiki/Shader
A shader is a set of software instructions, which is used to calculate rendering effects on GPU. Shaders can program the GPU's programmable rendering pipeline (as opposed to Fixed Function Pipeline, or FFP). Shaders replaces the FFP.
Shaders help determine the traits of a vertex or pixel. There are 3 types of shaders:
1. Vertex shaders: these are run once per vertex. manipulates position, color and tex-coordinates of vertices.
2. Geometry shaders: can add or remove vertices from a mesh (caused by plane-clipping, etc).
3. Pixel/fragment shaders: determines trait of a single pixel (color, z, alpha). typically used in scene lighting, bump-mapping, color toning.
Programming shaders can be done in the following 3D languages: OpenGL, DirectX.
1. DirectX for ATI uses HLSL (high level shader language)
2. DirectX for NVidia uses Cg (C for graphics, very similar to HLSL)
3. OpenGL uses GLSL (OpenGL Shading Language)
FROM: http://en.wikipedia.org/wiki/Shader
A shader is a set of software instructions, which is used to calculate rendering effects on GPU. Shaders can program the GPU's programmable rendering pipeline (as opposed to Fixed Function Pipeline, or FFP). Shaders replaces the FFP.
Shaders help determine the traits of a vertex or pixel. There are 3 types of shaders:
1. Vertex shaders: these are run once per vertex. manipulates position, color and tex-coordinates of vertices.
2. Geometry shaders: can add or remove vertices from a mesh (caused by plane-clipping, etc).
3. Pixel/fragment shaders: determines trait of a single pixel (color, z, alpha). typically used in scene lighting, bump-mapping, color toning.
Programming shaders can be done in the following 3D languages: OpenGL, DirectX.
1. DirectX for ATI uses HLSL (high level shader language)
2. DirectX for NVidia uses Cg (C for graphics, very similar to HLSL)
3. OpenGL uses GLSL (OpenGL Shading Language)
IPHONE: User-defined constructor/destructor
This is actually the second time I've come across this issue. Unfortunately I did not post the solution last time, so I had to go look it up again...
The WARNING:
type 'SomeClassType' has a user-defined constructor
tyep 'SomeClassType' has a user-defined destructor
The SOLUTION:
convert object declarations into pointer declarations. for example:
change to:
Of course, this also means you will have to manually control the instantiation & destruction of the object with new & free.
The WARNING:
type 'SomeClassType' has a user-defined constructor
tyep 'SomeClassType' has a user-defined destructor
The SOLUTION:
convert object declarations into pointer declarations. for example:
@interface myclass {
@private
SomeClassType myInstance;
}change to:
@interface myclass {
@private
SomeClassType* myInstancePtr;
}Of course, this also means you will have to manually control the instantiation & destruction of the object with new & free.
ANDROID: logcat on device
Here's another gripe. When you have both the emulator & device running, the adb logcat doesn't know which to listen to, and as a result outputs NOTHING.
to solve you'd simply close the emulator or device, whichever you aren't currently using.
also, as an added bonus, I found out how to cue up logcat via command prompt:
adb logcat -s DEVICE_NAME
to solve you'd simply close the emulator or device, whichever you aren't currently using.
also, as an added bonus, I found out how to cue up logcat via command prompt:
adb logcat -s DEVICE_NAME
ANDROID: Cannot create linked resource...
Here's the second error today. While attempting to import the Android project, or attempting to create a new Android project, I kept getting the error:
Cannot create linked resource '/.org.eclipse.jdt.core.external.folders/.link0'. The parent resource is not accessible.
Solution:
Unfortunately, this means it's time to ditch your workspace and create a new one... save your preferences (esp your key bindings), and move your Eclipse workspace to a new location. This should fix the issue.
Other solutions I've found online:
- Reinstalling Eclipse (overkill)
- Reinstalling Android SDK (probably won't help)
- eclipse.exe -clean (doesn't clean the workspace)
Nevertheless, you should try the -clean method, just in case it works for you.
Cannot create linked resource '/.org.eclipse.jdt.core.external.folders/.link0'. The parent resource is not accessible.
Solution:
Unfortunately, this means it's time to ditch your workspace and create a new one... save your preferences (esp your key bindings), and move your Eclipse workspace to a new location. This should fix the issue.
Other solutions I've found online:
- Reinstalling Eclipse (overkill)
- Reinstalling Android SDK (probably won't help)
- eclipse.exe -clean (doesn't clean the workspace)
Nevertheless, you should try the -clean method, just in case it works for you.
ANDROID: Could not find *.apk!
SEVERAL very annoying errors popped up today as I was dev-ing for Android. This post describes & solves the first of these errors.
Description of Error:
While attempting to build the android project the following message will pop up in the Console
[2009-11-02 16:28:51 - AndroidGL]Android Launch!
[2009-11-02 16:28:51 - AndroidGL]adb is running normally.
[2009-11-02 16:28:51 - AndroidGL]Could not find ********.apk!
Solution:
Make sure your project imported the Android 1.6 library correctly. That is, under your project, you should see 'Android 1.6', which expands and displays 'android.jar'.
If it says Referenced Libraries > android.jar, you will need to fix this by manually altering the .classpath for the project.
Open .classpath for the project and type the following:
The important line is the 3rd classpathentry, which is the actual link to the Android SDK libraries.
Description of Error:
While attempting to build the android project the following message will pop up in the Console
[2009-11-02 16:28:51 - AndroidGL]Android Launch!
[2009-11-02 16:28:51 - AndroidGL]adb is running normally.
[2009-11-02 16:28:51 - AndroidGL]Could not find ********.apk!
Solution:
Make sure your project imported the Android 1.6 library correctly. That is, under your project, you should see 'Android 1.6', which expands and displays 'android.jar'.
If it says Referenced Libraries > android.jar, you will need to fix this by manually altering the .classpath for the project.
Open .classpath for the project and type the following:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<kind="src" path="src">
<kind="src" path="gen">
<kind="con" path="com.android.ide.eclipse.adt.
ANDROID_FRAMEWORK">
<kind="output" path="bin">
</classpath>
The important line is the 3rd classpathentry, which is the actual link to the Android SDK libraries.
glFrustum vs PerspectiveFovRH
I was a bit stumped when I stumbled into PowerVR's iPhone SDK for OGL ES 1.1. namely, I wasn't sure what PerspectiveFovRH was for... I messed around with the numbers a little, and discovered the relationship between PerspectiveFovRH and the usual glFrustum method:
glFrustum(frustumLeft, frustumRight, frustumBottom, frustumTop, frustumNear, frustumFar)
is the same as:
float fovy = 2 * atanf( (frustumTop - frustumBottom) / (2 * frustumNear) );
PerspectiveFovRH(fovy, 320/480, frustumNear, frustumFar, OGL, false);
glFrustum(frustumLeft, frustumRight, frustumBottom, frustumTop, frustumNear, frustumFar)
is the same as:
float fovy = 2 * atanf( (frustumTop - frustumBottom) / (2 * frustumNear) );
PerspectiveFovRH(fovy, 320/480, frustumNear, frustumFar, OGL, false);
COCOA: OpenGL View
I tried to render a box in OpenGL, and for some strange reason, the depth test wasn't working at all. Finally I googled the problem, and found out it was caused by the Interface Builder... this is why I avoid IB when developing...
Here's what the screen-capture looked like, even though I had enabled GL_DEPTH_TEST
basically you have to set the depth bit of the OpenGLView to be > 0 bit (which is default!?). While I was at it, I also changed the color to 32bit.
Here's what the screen-capture looked like, even though I had enabled GL_DEPTH_TEST
basically you have to set the depth bit of the OpenGLView to be > 0 bit (which is default!?). While I was at it, I also changed the color to 32bit.
Win32: Setting up OpenGL's GLUT
it's been a very long time since my previous posts. i had to recently install opengl on my windows xp environment, and found there were actually very little documentation on this subject. so here's a tutorial to getting things started in opengl & glut.
CHECK FOR OpenGL:
1. when you install visual studios, you should already have the following libraries and DLLs:
- OpenGL32.lib (in C:\Program Files\Microsoft SDKs\Windows\v6.0A\Lib, etc)
- GLU32.lib (in C:\Program Files\Microsoft SDKs\Windows\v6.0A\Lib, etc)
2. make sure you see the following dll's in C:\Windows\System32
- OpenGL32.dll
- GLU32.dll
BUILD & INSTALL GLUT:
1. goto http://www.opengl.org/resources/libraries/glut/glut_downloads.php
- i downloaded 3.7.6 from http://www.xmission.com/~nate/glut.html
- download glut-3.7.6-src.zip
2. unzip glut-3.7.6/ directory onto the desktop
3. open glut.dsw
4. build the glut32 project
if you have visual studios 6, you should be fine. however, if you have visual studio 9.0 like me, you'll end up with an error during file copy, so you have to do some manual copying and pasting...
1. inside the [[DESKTOP]]/glut-3.7.6/ directory navigate to:
- [[DESKTOP]]/glut-3.7.6/lib/glut/Debug
2. copy glut32.dll into C:\Windows\System32
3. Copy glut32.lib into C:\Program Files\Microsoft Visual Studio 9.0\VC\lib
4. Copy [[DESKTOP]]/glut-3.7.6/include/GL/glut.h to C:\Program Files\Microsoft Visual Studio 9.0\VC\include\GL\glut.h
after this you should be able to start compiling the samples from the OpenGL red book.
CHECK FOR OpenGL:
1. when you install visual studios, you should already have the following libraries and DLLs:
- OpenGL32.lib (in C:\Program Files\Microsoft SDKs\Windows\v6.0A\Lib, etc)
- GLU32.lib (in C:\Program Files\Microsoft SDKs\Windows\v6.0A\Lib, etc)
2. make sure you see the following dll's in C:\Windows\System32
- OpenGL32.dll
- GLU32.dll
BUILD & INSTALL GLUT:
1. goto http://www.opengl.org/resources/libraries/glut/glut_downloads.php
- i downloaded 3.7.6 from http://www.xmission.com/~nate/glut.html
- download glut-3.7.6-src.zip
2. unzip glut-3.7.6/ directory onto the desktop
3. open glut.dsw
4. build the glut32 project
if you have visual studios 6, you should be fine. however, if you have visual studio 9.0 like me, you'll end up with an error during file copy, so you have to do some manual copying and pasting...
1. inside the [[DESKTOP]]/glut-3.7.6/ directory navigate to:
- [[DESKTOP]]/glut-3.7.6/lib/glut/Debug
2. copy glut32.dll into C:\Windows\System32
3. Copy glut32.lib into C:\Program Files\Microsoft Visual Studio 9.0\VC\lib
4. Copy [[DESKTOP]]/glut-3.7.6/include/GL/glut.h to C:\Program Files\Microsoft Visual Studio 9.0\VC\include\GL\glut.h
after this you should be able to start compiling the samples from the OpenGL red book.
WINDOWS: Registry
To add something to the RIGHT CLICK context menu, we can change the registry.
In my particular instance, I am looking to add a QUICK COMMAND that will run the JAD file in MPowerPlayer.
1. Goto: My Computer > HKEY_CLASSES_ROOT > jadfile
2. Expand jadfile > shell, and add a key "Run with MPowerPlayer"
3. Add a key under "Run with MPowerPlayer" called "command"
4. On the right, double click (Default), add the following data: java -jar C:\\mpowerplayer\\player.jar "%1"
That's all. Now right click on the JAD file and you should see your new command "Run with MPowerPlayer.
NOTE: you will want to change the directory location of mpowerplayer\player.jar to match your own.
Here's the entire structure after you are done (added 'Edit' command for comparison):
My Computer
----L HKEY_CLASSES_ROOT
---------L jadfile
--------------L shell
------------------L Run with MPowerPlayer
-----------------------L command = java -jar ... (see above)
------------------L Edit
-----------------------L command = notepad.exe "%1"
In my particular instance, I am looking to add a QUICK COMMAND that will run the JAD file in MPowerPlayer.
1. Goto: My Computer > HKEY_CLASSES_ROOT > jadfile
2. Expand jadfile > shell, and add a key "Run with MPowerPlayer"
3. Add a key under "Run with MPowerPlayer" called "command"
4. On the right, double click (Default), add the following data: java -jar C:\\mpowerplayer\\player.jar "%1"
That's all. Now right click on the JAD file and you should see your new command "Run with MPowerPlayer.
NOTE: you will want to change the directory location of mpowerplayer\player.jar to match your own.
Here's the entire structure after you are done (added 'Edit' command for comparison):
My Computer
----L HKEY_CLASSES_ROOT
---------L jadfile
--------------L shell
------------------L Run with MPowerPlayer
-----------------------L command = java -jar ... (see above)
------------------L Edit
-----------------------L command = notepad.exe "%1"
Subscribe to:
Posts (Atom)