2.configure ngrep to capture packet on lo
3.start live..
4.in emulator fetch web page from server with rtsp links
5.click on the links
6.analyze the ngrep capture
to check java version
1.java -version
2.which java
3.echo $JAVA_HOME
4.PATH=$JAVA_HOME\bin:$PATH
5.CLASSPATH=$JAVA_HOME\jre\lib\dt.jar;$JAVA_HOME\lib\dt.jar;%CLASSPATH%
6.
The following command will print the version of java you are currently using.
> java -version
The following command will print the home directory for the java executables for the version of java you are running. I assume that this is what you will want to correspond to JAVA_HOME. I'm not a developer so I am not 100% sure on this. This is typically /usr/bin/java.
> which java
I think it might be best practice to create a sym link between your current version and the more generic path. For example:
>ln -s /usr/java/jre1.x.x.x /usr/java/jre
This saved me a bit of aggravation when I upgraded java. The only item I had to change was the first sym link. My PATH variable etc. is preserved.
The following sym link should also be in place to direct you to the correct executables:
>ln -s /usr/java/jre/bin/java /usr/bin/java
In the event that "/usr/bin" is *not* in the PATH variable (unlikely), the following command may be used to add it.
>PATH=/usr/bin:$PATH then export PATH
only $JAVA_HOME, jre symbolic link is necessary to get java UP
My understanding is that this will only stay put for the duration of the session. Editing the PATH variable as it exists in /etc/profile is a more permanent method.
I'm not sure how to set the class path, but I hope the above helps
8.edit ~.bashrc,
9.android master repo compilation error
# git reset --hard 9a199257cfdaeec82aa1cc662436d3a47fb6f2ea
# cd -
refere to .txt in the home directory
11.emulator ppp and emulator
http://i-miss-erin.blogspot.com/2010/04/use-3g-modem-data-card-in-android.html
12.Android kernel source for emulator
http://stackoverflow.com/questions/1809774/android-kernel-compile-and-test-with-android-emulator
No comments:
Post a Comment