How can you specify the target API Level

david.bou..

Re: How can you specify the target API Level

2 years ago

The only method I found so far requires modifying the source for the Processing IDE -- it appears that the API level is hard-coded in the file AndroidBuild.java (in processing/app/src/processing/mode/android/)

On line 37, change this line to match your desired sdkVersion:

static final String sdkVersion = "10";

Then re-build by going into the app/ folder and running "ant". I was able to access the GL20 API that way, so I presume the same will be true for the ADK stuff.

d.

almost_sc..

Re: Re: How can you specify the target API Level

2 years ago

Great Thanks!

So I'm on osx & I followed the instructions here: http://code.google.com/p/processing/wiki/BuildInstructions to download svn and get the source. I then modified AndroidBuild.java as you suggested and rebuilt using ant. I got this message:

MyPath/processing-read-only/processing/app/build.xml:77: Please build the core library first and make sure it sits in ../core/core.jar

So I went into /processing-read-only/processing/core and ran ant and built core/core.jar

I then went back and app/ and ran ant again, building /app/pde.jar:

build:

[jar] Building jar: /Users/alan/processing-read-only/processing/app/pde.jar

BUILD SUCCESSFUL

But, now what? How do I run this modified version?

I've never really complied and run java source before.

Thank you so much for your help so far.

david.bou..

Re: How can you specify the target API Level

2 years ago

Glad you got the build to work!

Once you've built it, the Processing.app should be in processing/build/macosx/work.

d.

almost_sc..

Re: Re: How can you specify the target API Level

2 years ago

Thanks for your continued help!

So, yes, I discovered the app in build/macosx/work but only after I ran ant in processin/build directly.

And, the application did run in standard mode just fine. However, when I tried to launch the same piece of code in Android mode (running on a device) I got this error:

java.io.FileNotFoundException: /Users/alan/processing-read-only/processing/build/macosx/work/Processing.app/Contents/Resources/Java/modes/android/android-core.zip (No such file or directory)

at java.io.FileInputStream.open(Native Method)

at java.io.FileInputStream.<init>(FileInputStream.java:106)

at processing.app.Base.copyFile(Base.java:2237)

at processing.mode.android.AndroidBuild.createProject(AndroidBuild.java:152)

at processing.mode.android.AndroidBuild.build(AndroidBuild.java:80)

at processing.mode.android.AndroidMode.handleRunDevice(AndroidMode.java:173)

at processing.mode.android.AndroidEditor$13.run(AndroidEditor.java:358)

So I went back to my build outputs and found this error (I saw the app apear so I thought the build was successful):

/Users/alan/processing-read-only/processing/build/build.xml:28: The following error occurred while executing this line:

/Users/alan/processing-read-only/processing/build/build.xml:338: The following error occurred while executing this line:

/Users/alan/processing-read-only/processing/build/build.xml:164: android-core.zip was not built, but is required for dist. Install the Android tools, set ANDROID_SDK, and try again.

When I try run ant in processing/android/core I get this:

Buildfile: /Users/alan/processing-read-only/processing/android/core/build.xml

sdk_chatter:

[echo] ANDROID_SDK not set, skipping build of android-core.zip

actual_build:

build:

BUILD SUCCESSFUL

Now I've searched all the code and can't seem to find where ANDROID_SDK is set. I know I have the SDK installed properly because I've got Android apps working in Eclipse.

I even when ahead and got subclipse installed to see if doing this in eclipse helped. And I get the same errors.

I've put the SDK tools in my path via my .bash_profile :

PATH="/Documents/android-sdk-mac_x86/tools"

export PATH

But I'm jammed up again with this ANDROID_SDK variable.

Any ideas?

Thanks again for your help. I owe you a beer!

almost_sc..

Re: How can you specify the target API Level

2 years ago

Well, I solved the ANDROID_SDK problem by pulling up the properties for the various .xml files and setting ANDROID_SDK to the path for my sdk.

After this I was able to recompile and run Proessing without a problem in both standard and Android mode.

I also altered AndroidBuild.java and processing/android/core/build.xml to use api Level 10.

However, when I try to import android.hardware.usb I still get the same error:

compile:

[javac] /Users/alan/Documents/android-sdk-mac_x86/tools/ant/main_rules.xml:384: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds

[javac] Compiling 2 source files to /var/folders/+J/+JfHtdmFGhG1G8wnOA64A++++TI/-Tmp-/android2798083215887787701.pde/bin/classes

[javac] /var/folders/+J/+JfHtdmFGhG1G8wnOA64A++++TI/-Tmp-/android2798083215887787701.pde/src/processing/android/test/test1/Test1.java:6: cannot find symbol

[javac] symbol : class usb

[javac] location: package android.hardware

[javac] import android.hardware.usb;

[javac] ^

[javac] /var/folders/+J/+JfHtdmFGhG1G8wnOA64A++++TI/-Tmp-/android2798083215887787701.pde/src/processing/android/test/test1/Test1.java:198: cannot find symbol

[javac] symbol : variable intent

[javac] location: class processing.android.test.test1.Test1

[javac] UsbAccessory accessory = UsbManager.getAccessory(intent);

[javac] ^

[javac] /var/folders/+J/+JfHtdmFGhG1G8wnOA64A++++TI/-Tmp-/android2798083215887787701.pde/src/processing/android/test/test1/Test1.java:208: cannot find symbol

[javac] symbol : variable mUsbManager

[javac] location: class processing.android.test.test1.Test1

[javac] mFileDescriptor = mUsbManager.openAccessory(mAccessory);

[javac] ^

[javac] 3 errors

BUILD FAILED

/Users/alan/Documents/android-sdk-mac_x86/tools/ant/main_rules.xml:384: Compile failed; see the compiler error output for details.

It appears that despite it's claim that it's using API Level: 10 it's not.

Thanks for all the help thus far. Any thoughts would be appreciated.

david.bou..

Re: How can you specify the target API Level

2 years ago

OK. This might be a silly question but is your device running Android 2.3.4 ?

david.bou..

Re: How can you specify the target API Level

2 years ago

OK, so I don't have access to either an ADK board or a 2.3.4 Android device, so I could only get as far as getting the code to compile.

There are actually a bunch of hoops to jump through:

1) Unless you are using a 3.1 device, you need to change the target to the Google API Add-on -- just level 10 is not enough (also make sure you download said add-on!) Right where you changed the API level, you can replace this line as well:

//static final String sdkTarget = "android-" + sdkVersion;
static final String sdkTarget = "Google Inc.:Google APIs:" + sdkVersion;

BTW, do know the names of available targets, you can use the command "android list targets"

2) You also need to modify your manifest file needs to include new tags: <use-feature>, <use-library>, <intent-filter> and <meta-data> tags. Mine looks like this:

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package=""
android:versionCode="1"
android:versionName="1.0">
<uses-sdk android:minSdkVersion="10" />
<uses-feature android:name="android.hardware.usb.accessory" />
<application android:label=""
android:icon="@drawable/icon"
android:debuggable="true">
<uses-library android:name="com.android.future.usb.accessory" />
<activity android:name="">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
<intent-filter>
<action android:name="android.hardware.usb.action.USB_ACCESSORY_ATTACHED" />
</intent-filter>
<meta-data android:name="android.hardware.usb.action.USB_ACCESSORY_ATTACHED" android:resource="@xml/accessory_filter" />
</activity>
</application>
</manifest>

3) Which takes us to problem number 3. The docs mention that the accessory needs to provide an XML resource for the <meta-data> tag ("accessory_filter") with some info about the accessory. This is the example from the docs for accessory_filter.xml:

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <usb-accessory model="DemoKit" manufacturer="Google" version="1.0"/>
</resources>

I don't know if this is required or not for the code to run. You can compile without it. But if you need to include the file, here's a way:

Processing copies everything from the "data" folder into the "assets" folder, however I don't know how to refer to files from /assets in the manifest file. The @xml tag refers to resources inside "res/xml". My temporary solution was to make a "xml" folder in my sketch, and extend AndroidBuild.java to copy the content of that folder in res/xml as it builds all the temporary files:

private void writeRes(File resFolder,
String className) throws SketchException {
// copy all the XML files in the "xml" folder to res/xml
File XMLFolder = mkdirs(resFolder, "xml");
final File sketchXMLFolder = new File(sketch.getFolder() + "/xml");
try {
Base.copyDir(sketchXMLFolder, XMLFolder);
}
catch (IOException e) {
e.printStackTrace();
}
// ... rest of the original code resumes here

4) Finally, the package to import is not android.hardware.usb but this one:

import com.android.future.usb.*;
void setup() {
}
void draw() {
}

Unless you have a Honeycomb device, in which case you'll want to import android.hardware.usb, target "android-12" and I change the Manifest file around a bit... Hopefully this takes you a bit further along. I can't really test any more until I get my hands on some ADK hardware... Which board did you get, btw?

d.

almost_sc..

Re: Re: How can you specify the target API Level

2 years ago

Thanks again for your help and input, I really value it.

The phone I am test all this on is a Nexus S running Android 2.3.4 and I have the full most recent version of the Android SDK including Level-10 and the add-on.

I verified this (as you suggested) with "android list targets":

id: 15 or "Google Inc.:Google APIs:10"

Name: Google APIs

Type: Add-On

Vendor: Google Inc.

Revision: 2

Description: Android + Google APIs

Based on Android 2.3.3 (API level 10)

Libraries:

* com.android.future.usb.accessory (usb.jar)

API for USB Accessories

* com.google.android.maps (maps.jar)

API for Google Maps

Skins: WVGA854, WQVGA400, HVGA, WQVGA432, WVGA800 (default), QVGA

I'm using one of the official Google ADK boards.

I know that I have everything I need to get the ADK board working, and I've gotten the demo code on the development page to work, as well as some basic Android code I've written.

My success with all that was what made me push off into getting it to work with Processing.

I had already made the changes (that you pointed out) to the manifest.xml file by altering Manifest.Java. I was leaving all that other stuff out of the discussion to keep it focused on my core problem of importing.

I had hoped to avoid having to create the @xml/accessory_filter by having the application enumerate the accessories. But thanks to your addition to writeRes() this looks like it could be a great option. Really, since I've just been having trouble getting the right library imported I was going to worry about this later.

You are correct, that I should be using com.android.future.usb.*

So, I made your suggested change to AndroidBuild.java (to account for the add-on), double checked my Manifest.java (and verified it was creating a clean manifest.xml file with all the additions), and added your extension to writeRes().

I also changed android.core.build.xml, line 18 from:

bootclasspath="${env.ANDROID_SDK}/platforms/android-7/android.jar"

to:

bootclasspath="${env.ANDROID_SDK}/platforms/android-10/android.jar"

Really, I'm not sure if this is the right thing to do.

My processing code, however, still does not compile:

import com.android.future.usb.*;
UsbAccessory mAccessory;
UsbManager mUsbManager;
UsbAccessory[] accessoryList;
FileInputStream mInputStream;
FileOutputStream mOutputStream;
float w, h;
String[] fontList;
PFont androidFont;
void onResume() {
super.onResume();
println("RESUMED! (Sketch Entered...)");
////////For Intent Filtered Accessories//////////////
UsbManager mUsbManager = UsbManager.getInstance(this);
UsbAccessory mAccessory = mUsbManager.getAccessory(intent);
////////////For enumerated Accessories//////////////
//UsbManager mUsbManager = (UsbManager) getSystemService(Context.USB_SERVICE);
//UsbAccessory[] accessoryList = mUsbManager.getAcccessoryList();
//UsbAccessory mAccessory=accessoryList[0];
}
void onPause() {
println("PAUSED! (Sketch Exited...)");
super.onPause();
}
private void openAccessory() {
mFileDescriptor = mUsbManager.openAccessory(mAccessory);
if (mFileDescriptor != null) {
FileDescriptor fd = mFileDescriptor.getFileDescriptor();
mInputStream = new FileInputStream(fd);
mOutputStream = new FileOutputStream(fd);
Thread thread = new Thread(null, this, "AccessoryThread");
thread.start();
}
}
void setup() {
size(screenWidth, screenHeight, A2D);
w = screenWidth;
h = screenHeight;
orientation(PORTRAIT);
fontList = PFont.list();
androidFont = createFont(fontList[0], 16, true);
textFont(androidFont);
}
void draw() {
fill(0);
rect(0, 0, w, h);
fill(255);
text("I LIVE", 10, 20);
}

The error output I get is:

No library found for com.android.future.usb

Android SDK Tools Revision 11

Project Target: Google APIs

Vendor: Google Inc.

Platform Version: 2.3.3

API level: 10

------------------

Resolving library dependencies:

No library dependencies.

------------------

Importing rules file: tools/ant/main_rules.xml

-debug-obfuscation-check:

-set-debug-mode:

-compile-tested-if-test:

-pre-build:

-dirs:

[echo] Creating output directories if needed...

[mkdir] Created dir: /var/folders/+J/+JfHtdmFGhG1G8wnOA64A++++TI/-Tmp-/android1921908255940324121.pde/bin

[mkdir] Created dir: /var/folders/+J/+JfHtdmFGhG1G8wnOA64A++++TI/-Tmp-/android1921908255940324121.pde/gen

[mkdir] Created dir: /var/folders/+J/+JfHtdmFGhG1G8wnOA64A++++TI/-Tmp-/android1921908255940324121.pde/bin/classes

-aidl:

[echo] Compiling aidl files into Java classes...

-renderscript:

[echo] Compiling RenderScript files into Java classes and RenderScript bytecode...

-resource-src:

[echo] Generating R.java / Manifest.java from the resources...

-pre-compile:

compile:

[javac] /Users/alan/Documents/android-sdk-mac_x86/tools/ant/main_rules.xml:384: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds

[javac] Compiling 2 source files to /var/folders/+J/+JfHtdmFGhG1G8wnOA64A++++TI/-Tmp-/android1921908255940324121.pde/bin/classes

[javac] /var/folders/+J/+JfHtdmFGhG1G8wnOA64A++++TI/-Tmp-/android1921908255940324121.pde/src/processing/android/test/test1/Test1.java:34: cannot find symbol

[javac] symbol : variable intent

[javac] location: class processing.android.test.test1.Test1

[javac] UsbAccessory mAccessory = mUsbManager.getAccessory(intent);

[javac] ^

[javac] /var/folders/+J/+JfHtdmFGhG1G8wnOA64A++++TI/-Tmp-/android1921908255940324121.pde/src/processing/android/test/test1/Test1.java:48: cannot find symbol

[javac] symbol : variable mFileDescriptor

[javac] location: class processing.android.test.test1.Test1

[javac] mFileDescriptor = mUsbManager.openAccessory(mAccessory);

[javac] ^

[javac] /var/folders/+J/+JfHtdmFGhG1G8wnOA64A++++TI/-Tmp-/android1921908255940324121.pde/src/processing/android/test/test1/Test1.java:49: cannot find symbol

[javac] symbol : variable mFileDescriptor

[javac] location: class processing.android.test.test1.Test1

[javac] if (mFileDescriptor != null) {

[javac] ^

[javac] /var/folders/+J/+JfHtdmFGhG1G8wnOA64A++++TI/-Tmp-/android1921908255940324121.pde/src/processing/android/test/test1/Test1.java:50: cannot find symbol

[javac] symbol : variable mFileDescriptor

[javac] location: class processing.android.test.test1.Test1

[javac] FileDescriptor fd = mFileDescriptor.getFileDescriptor();

[javac] ^

[javac] 4 errors

So, I've still got the same stupid problem, (now in a new flavor) of being unable to import the library that supports the accessory mode methods.

I'll keep hacking away at this, but if you have any other suggestions or advice, I'd be grateful to hear it.

Thanks for your help so far!

david.bou..

Re: How can you specify the target API Level

2 years ago

Oh, then it looks like you are in good shape! Notice that the errors not longer refer to the import statement! These are just a few basic problems with your code:

- the variable "intent" doesn't exist when you try to use it. Try this:

Intent intent = getIntent();
UsbAccessory mAccessory = mUsbManager.getAccessory(intent);

- mFileDescriptor isn't given a type either. Should be:

ParcelFileDescriptor mFileDescriptor = mUsbManager.openAccessory(mAccessory);

You'll need to import both of these classes as well:

import android.os.ParcelFileDescriptor;
import android.content.Intent;

Your code compiles for me with these changes. Now, I have no idea if this works or not, having no device to try it with!

BTW I didn't have to change android.core.build.xml.

Good luck!
d.

almost_sc..

Re: Re: How can you specify the target API Level

2 years ago

Yes! Thanks, again, so very much! It complies and runs on the phone now.

I had assumed that the error with the intent var was because it was not loading the android libs properly.

I suppose the message "No library found for com.android.future.usb" is not fatal and did not mean that it wasn't loading.

It makes complete sense that I need to define intent. I'm still trying to get my head around all the Android stuff.

Now the next step is to see if I can actually connect and comunicate with the ADK. I'm sure I'll have more problems with that ;) But it's nice to keep thing moving along.

I'll let you know how it goes.

At some point I'd like to write this all up more concisely for other people, do you have a specific way you'd like to be credited? (a web page or name or something?)

Thanks again!

david.bou..

Re: How can you specify the target API Level

2 years ago

No problem!

A write up would be great! The wiki might be a good place for this..

I updated my user profile /w website information.
d.

jonrose08

Re: How can you specify the target API Level

2 years ago

Sounds like this was resolved but I thought I would throw in my two cents. Although Processing is not intended to be run in eclipse, specifying the target API/SDK level is a zero hassle process. If you already are dealing with getting the source etc and having to modify that, this really wouldn't be a hassle.

For me, I use subversion in eclipse (as suggested on the wiki) to download the processing-core source for android. I then create a new Android project, as if I was going to write any other non processing android app in eclipse. The eclipse new project wizard lets you specify all the api target info there with a couple clicks. I have used this to run stuff on my girlfriends evo running 2.2 and then I also use this with my Xoom in Honeycomb 3.1.