rosjava / android_core Goto Github PK

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original author: [email protected] (May 16, 2011 20:10:58)

I'm not knowledgeable enough about the android properties files, but it seems that the ant dist is grabbing damonkohler's instead of mine. My android sdk is installed in ~/

I am running ubuntu 11.04 64bit

What steps will reproduce the problem?

1. ant dist
   2.
   3.

What is the expected output? What do you see instead?

a successful build I would suppose

What version of the product are you using? On what operating system?

most recent

Please provide any additional information below.

k3nt@k3nt-m:~/workspace/rosjava$ ant dist
Buildfile: /home/k3nt/workspace/rosjava/build.xml

dist:

dist.dependencies:

depend.ws-commons-util:

init:

compile:

jar:
[echo] No JAR to buid for ws-commons-util.

dist:

default:

depend.apache-xmlrpc:

init:

compile:

jar:
[echo] No JAR to buid for apache-xmlrpc.

dist:

default:

depend.java:

init:

check-msg-gen-skip:

msg-gen:

check-srv-gen-skip:

srv-gen:

compile:

jar:

dist:

default:

dist.dependencies:

depend.ws-commons-util:

init:

compile:

jar:
[echo] No JAR to buid for ws-commons-util.

dist:

default:

depend.apache-xmlrpc:

init:

compile:

jar:
[echo] No JAR to buid for apache-xmlrpc.

dist:

default:

depend.java:

init:

check-msg-gen-skip:

msg-gen:

check-srv-gen-skip:

srv-gen:

compile:

jar:

dist:

default:

depend.android:

compile:

BUILD FAILED
/home/k3nt/workspace/rosjava/build.xml:5: The following error occurred while executing this line:
/home/k3nt/workspace/rosjava/build-common.xml:16: The following error occurred while executing this line:
/home/k3nt/workspace/rosjava/dependencies.xml:20: The following error occurred while executing this line:
/home/k3nt/workspace/rosjava/android/build.xml:6: The following error occurred while executing this line:
/home/k3nt/workspace/rosjava/android/library/build.xml:37: Cannot find /Users/damonkohler/android-sdk-mac_x86/tools/ant/pre_setup.xml imported from /home/k3nt/workspace/rosjava/android/library/build.xml

Total time: 1 second

Original issue: http://code.google.com/p/rosjava/issues/detail?id=1

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original author: [email protected] (June 16, 2011 00:11:26)

What steps will reproduce the problem?

1. Create a ROSJAVA node on an android device
2. Connect to a remote master (I had this running on Ubuntu 10.04 with Diamondback)
3. run "rosnode info <node name>" from ROS Master side

What is the expected output? What do you see instead?
List of publications, Subscriptions, and Services followed by an attempt to contact node and return a PID.

Instead a list of publications, subscriptions, and services is shown followed by:
"ERROR: remote call failed: Cannot retrieve PID on this platform."

What version of the product are you using? On what operating system?
ROSJAVA version: cb4300c0e727 Android: 2.2.1

Please provide any additional information below.
It seems that this error is associated with the node slave api, which is causing my application to crash when attempting to subscribe to topics.

Original issue: http://code.google.com/p/rosjava/issues/detail?id=10

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original author: [email protected] (July 21, 2011 00:15:52)

The attached patch refactors the generation of the eclipse .classpath and .project. It creates a generate_eclipse_project.py and generate_eclipse_classpath.py that correctly make an Android eclipse project when <android> is exported from the manifest.

Original issue: http://code.google.com/p/rosjava/issues/detail?id=24

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original author: [email protected] (August 31, 2011 05:26:23)

What steps will reproduce the problem?

1. Run the android_tutorial_camera project on an Android phone.
2. Record the /camera/image_raw topic using rosbag.
3. Play back the bag file.

What is the expected output? What do you see instead?
The expected output is that the CompressedImage messages are recorded and the image data will be visible upon playback.

Instead, the data field of the CompressedImage is empty in all recorded messages.

What version of the product are you using? On what operating system?
Using latest version of rosjava source compiled against electric.

Please provide any additional information below.
The images are viewable using image_view at the time of being recorded, however the bag file does not actually contain the image data. It appears that something is causing rosbag to record corrupted CompressedImage messages because running "rosbag check <bagfile>" causes very strange behavior, e.g. spawning many rospack processes and causing many strange errors to be output.

Perhaps rosjava does not properly implement something that prevents rosbag from properly recording the uint8[] data field in CompressedImage.

Attached is a sample bag file. Note that the topic recorded is not "/camera/image_raw", but "/camera/image/compressed" as I changed the published topic to properly conform to the expected topic names as mentioned in Issue #22.

I would really like to know if anyone else can reproduce this issue.

Original issue: http://code.google.com/p/rosjava/issues/detail?id=29

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original author: [email protected] (June 16, 2011 10:18:39)

What steps will reproduce the problem?

1. Start tutorials/image_transport
2. Setup an arbitrary ROS_MASTER_URI
3. Press OK -> Crash

What is the expected output? What do you see instead?

A connection to my ros core.

What version of the product are you using? On what operating system?

Android 2.3.3 on HTC Desire Z.

Please provide any additional information below.

W/Bundle (15937): Key ROS_MASTER_URI expected String but value was a java.net.URI. The default value <null> was returned.
W/Bundle (15937): Attempt to cast generated internal exception:
W/Bundle (15937): java.lang.ClassCastException: java.net.URI
W/Bundle (15937): at android.os.Bundle.getString(Bundle.java:1040)
W/Bundle (15937): at android.content.Intent.getStringExtra(Intent.java:3415)
W/Bundle (15937): at org.ros.tutorials.image_transport.MainActivity.onActivityResult(MainActivity.java:86)
W/Bundle (15937): at android.app.Activity.dispatchActivityResult(Activity.java:3908)
W/Bundle (15937): at android.app.ActivityThread.deliverResults(ActivityThread.java:2649)
W/Bundle (15937): at android.app.ActivityThread.handleSendResult(ActivityThread.java:2695)
W/Bundle (15937): at android.app.ActivityThread.access$2000(ActivityThread.java:123)
W/Bundle (15937): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:969)
W/Bundle (15937): at android.os.Handler.dispatchMessage(Handler.java:99)
W/Bundle (15937): at android.os.Looper.loop(Looper.java:123)
W/Bundle (15937): at android.app.ActivityThread.main(ActivityThread.java:3835)
W/Bundle (15937): at java.lang.reflect.Method.invokeNative(Native Method)
W/Bundle (15937): at java.lang.reflect.Method.invoke(Method.java:507)
W/Bundle (15937): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
W/Bundle (15937): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
W/Bundle (15937): at dalvik.system.NativeStart.main(Native Method)
D/AndroidRuntime(15937): Shutting down VM
W/dalvikvm(15937): threadid=1: thread exiting with uncaught exception (group=0x40015560)
E/AndroidRuntime(15937): FATAL EXCEPTION: main
E/AndroidRuntime(15937): java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=0, result=-1, data=Intent { (has extras) }} to activity {org.ros.tutorials.image_transport/org.ros.tutorials.image_transport.MainActivity}: java.lang.NullPointerException
E/AndroidRuntime(15937): at android.app.ActivityThread.deliverResults(ActivityThread.java:2653)
E/AndroidRuntime(15937): at android.app.ActivityThread.handleSendResult(ActivityThread.java:2695)
E/AndroidRuntime(15937): at android.app.ActivityThread.access$2000(ActivityThread.java:123)
E/AndroidRuntime(15937): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:969)
E/AndroidRuntime(15937): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(15937): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(15937): at android.app.ActivityThread.main(ActivityThread.java:3835)
E/AndroidRuntime(15937): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(15937): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime(15937): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime(15937): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime(15937): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(15937): Caused by: java.lang.NullPointerException
E/AndroidRuntime(15937): at java.net.URI.parseURI(URI.java:296)
E/AndroidRuntime(15937): at java.net.URI.<init>(URI.java:72)
E/AndroidRuntime(15937): at org.ros.tutorials.image_transport.MainActivity.onActivityResult(MainActivity.java:86)
E/AndroidRuntime(15937): at android.app.Activity.dispatchActivityResult(Activity.java:3908)
E/AndroidRuntime(15937): at android.app.ActivityThread.deliverResults(ActivityThread.java:2649)
E/AndroidRuntime(15937): ... 11 more
W/ActivityManager( 1318): Force finishing activity org.ros.tutorials.image_transport/.MainActivity
W/ActivityManager( 1318): Activity pause timeout for HistoryRecord{4056fad0 org.ros.tutorials.image_transport/.MainActivity}
I/Process (15937): Sending signal. PID: 15937 SIG: 9
I/ActivityManager( 1318): Process org.ros.tutorials.image_transport (pid 15937) has died.

Original issue: http://code.google.com/p/rosjava/issues/detail?id=12

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original author: [email protected] (July 08, 2011 20:57:02)

/*To get this running in eclipse, first of all, rosjava-android should *be set as a library using Properties->Android->Is Library (tick box) *and then include the project in any of the *rosjava_core/android/tutorials. You would also require all the *necessary jar files in the build path)

Due to some apparent XML RPC issues, I use a remote roscore host with *local nodes for all my work./

In RosCameraPreview,main()

Instead of

imagePublisher =
node.createPublisher(resolver.resolve("image_raw"), "sensor_msgs/CompressedImage");

it should be

imagePublisher =
node.createPublisher(resolver.resolve("image_raw/compressed"), "sensor_msgs/CompressedImage");

As image_view expects the compressed image to be published to image_raw/compressed or theora.

Original issue: http://code.google.com/p/rosjava/issues/detail?id=22

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original author: [email protected] (June 08, 2011 21:53:41)

What steps will reproduce the problem?

1. roscd rosjava/android/library
2. ./create_project.sh

What is the expected output? What do you see instead?

Expected output looks something like this:

Updated default.properties
Updated local.properties
File build.xml is too old and needs to be updated.
Updated file build.xml
Updated file proguard.cfg

Actual output is this:

Error: Target id '11' is not valid. Use 'android list targets' to get the target ids.

Here is the output of 'android list targets':

Available Android targets:
id: 1 or "android-3"
Name: Android 1.5
Type: Platform
API level: 3
Revision: 4
Skins: QVGA-P, HVGA-P, QVGA-L, HVGA-L, HVGA (default)
id: 2 or "android-4"
Name: Android 1.6
Type: Platform
API level: 4
Revision: 3
Skins: QVGA, HVGA, WVGA854, WVGA800 (default)
id: 3 or "android-7"
Name: Android 2.1-update1
Type: Platform
API level: 7
Revision: 2
Skins: QVGA, WQVGA400, HVGA, WVGA854, WQVGA432, WVGA800 (default)
id: 4 or "android-8"
Name: Android 2.2
Type: Platform
API level: 8
Revision: 2
Skins: QVGA, WQVGA400, HVGA, WVGA854, WQVGA432, WVGA800 (default)
id: 5 or "android-9"
Name: Android 2.3.1
Type: Platform
API level: 9
Revision: 2
Skins: QVGA, WQVGA400, HVGA, WVGA854, WQVGA432, WVGA800 (default)
id: 6 or "android-10"
Name: Android 2.3.3
Type: Platform
API level: 10
Revision: 1
Skins: QVGA, WQVGA400, HVGA, WVGA854, WQVGA432, WVGA800 (default)
id: 7 or "android-11"
Name: Android 3.0
Type: Platform
API level: 11
Revision: 1
Skins: WXGA (default)

Same problem happens in rosjava/android/tutorials/create_project.sh.

Original issue: http://code.google.com/p/rosjava/issues/detail?id=4

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original author: [email protected] (June 09, 2011 22:29:08)

What steps will reproduce the problem?

1. Install a fresh copy of rosjava according to the instructions.
2. Make rosjava build.
3. Start Eclipse, and import the following projects into your workspace:

• android (the rosjava android library)
• java (the rosjava library)
• Teleop (under tutorials)

1. Fix build build path problems in the packages until you've managed to get rid of the red crosses (some of the msg_gen/java and srv_gen/java folders have moved)
2. Once the 'android' and 'java' projects compile, try to compile Teleop.

What is the expected output?

• A successful compilation

What do you see instead?

• The following errors:

Description Resource Path Location Type
appManager cannot be resolved Teleop.java /Teleop/src/ros/android/teleop line 227 Java Problem
AppStatus cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 60 Java Problem
AppStatus cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 156 Java Problem
AppStatus cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 157 Java Problem
AppStatus cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 158 Java Problem
MapView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 54 Java Problem
MapView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 84 Java Problem
MapView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 84 Java Problem
MapView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 91 Java Problem
MapView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 103 Java Problem
MapView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 124 Java Problem
MapView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 128 Java Problem
MapView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 133 Java Problem
MapView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 141 Java Problem
MapView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 165 Java Problem
MapView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 222 Java Problem
RosAppActivity cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 51 Java Problem
RosAppActivity cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 70 Java Problem
RosAppActivity cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 166 Java Problem
RosAppActivity cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 213 Java Problem
RosAppActivity cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 220 Java Problem
RosAppActivity cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 256 Java Problem
RosInitException cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 206 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 53 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 79 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 79 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 97 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 104 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 125 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 129 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 132 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 142 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 152 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 153 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 154 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 193 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 193 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 195 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 196 Java Problem
SensorImageView cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 200 Java Problem
StartApp cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 228 Java Problem
StartApp cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 230 Java Problem
The import org.ros.exceptions cannot be resolved Teleop.java /Teleop/src/ros/android/teleop line 36 Java Problem
The import org.ros.message.app_manager cannot be resolved Teleop.java /Teleop/src/ros/android/teleop line 38 Java Problem
The import org.ros.service.app_manager cannot be resolved Teleop.java /Teleop/src/ros/android/teleop line 41 Java Problem
The import ros.android.activity cannot be resolved Teleop.java /Teleop/src/ros/android/teleop line 43 Java Problem
The import ros.android.views cannot be resolved Teleop.java /Teleop/src/ros/android/teleop line 44 Java Problem
The import ros.android.views cannot be resolved Teleop.java /Teleop/src/ros/android/teleop line 45 Java Problem
The import ros.android.views cannot be resolved Teleop.java /Teleop/src/ros/android/teleop line 46 Java Problem
The method createPublisher(String, Class<Twist>) is undefined for the type Namespace Teleop.java /Teleop/src/ros/android/teleop line 204 Java Problem
The method findViewById(int) is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 76 Java Problem
The method findViewById(int) is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 79 Java Problem
The method findViewById(int) is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 83 Java Problem
The method findViewById(int) is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 84 Java Problem
The method findViewById(int) is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 86 Java Problem
The method findViewById(int) is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 87 Java Problem
The method findViewById(int) is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 193 Java Problem
The method getAppNamespace(Node) is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 192 Java Problem
The method getMenuInflater() is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 248 Java Problem
The method getNode() is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 191 Java Problem
The method getWindow() is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 72 Java Problem
The method makeText(Context, CharSequence, int) in the type Toast is not applicable for the arguments (Teleop, String, int) Teleop.java /Teleop/src/ros/android/teleop line 214 Java Problem
The method makeText(Context, CharSequence, int) in the type Toast is not applicable for the arguments (Teleop, String, int) Teleop.java /Teleop/src/ros/android/teleop line 291 Java Problem
The method onCreate(Bundle) of type Teleop must override or implement a supertype method Teleop.java /Teleop/src/ros/android/teleop line 69 Java Problem
The method onCreateOptionsMenu(Menu) of type Teleop must override or implement a supertype method Teleop.java /Teleop/src/ros/android/teleop line 247 Java Problem
The method onNodeCreate(Node) of type Teleop must override or implement a supertype method Teleop.java /Teleop/src/ros/android/teleop line 218 Java Problem
The method onNodeDestroy(Node) of type Teleop must override or implement a supertype method Teleop.java /Teleop/src/ros/android/teleop line 146 Java Problem
The method onOptionsItemSelected(MenuItem) of type Teleop must override or implement a supertype method Teleop.java /Teleop/src/ros/android/teleop line 254 Java Problem
The method onResume() of type Teleop must override or implement a supertype method Teleop.java /Teleop/src/ros/android/teleop line 212 Java Problem
The method requestWindowFeature(int) is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 71 Java Problem
The method resolveName(String) is undefined for the type Namespace Teleop.java /Teleop/src/ros/android/teleop line 195 Java Problem
The method runOnUiThread(new Runnable(){}) is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 288 Java Problem
The method setContentView(int) is undefined for the type Teleop Teleop.java /Teleop/src/ros/android/teleop line 74 Java Problem
The type new ServiceResponseListener<Response>(){} must implement the inherited abstract method ServiceResponseListener<Response>.onSuccess(Response) Teleop.java /Teleop/src/ros/android/teleop line 228 Java Problem
TurtlebotDashboard cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 61 Java Problem
TurtlebotDashboard cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 83 Java Problem
TurtlebotDashboard cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 83 Java Problem
TurtlebotDashboard cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 164 Java Problem
TurtlebotDashboard cannot be resolved to a type Teleop.java /Teleop/src/ros/android/teleop line 221 Java Problem

What version of the product are you using? On what operating system?

• Mac OS X 10.6.7
• ROS Diamondback
• rosjava's current tip (544:89983389c982)
• Eclipse Helios

Please provide any additional information below.

• It looks like there has been a change in the way how the android apps used to work, and as a consequence, the app_manager doesn't appear to exist anymore. It seems that it existed some time ago though: http://code.google.com/p/rosjava/source/browse/android/library/src/ros/android/activity/AppManager.java?spec=svne32902286f84c56abade5cea87993a95d3982e35&amp;r=e32902286f84c56abade5cea87993a95d3982e35.
  It also looks like the various Turtlebot specific files as well as the MapView and a few other classes have been removed...

Original issue: http://code.google.com/p/rosjava/issues/detail?id=6

Skipping this issue number to maintain synchronization with Google Code issue IDs.