Processing Android Tablet Adventures

ak_eric

Re: Processing Android Tablet Adventures

2 years ago

While I don't have access to a tablet myself, a few users of one of my apps have reported it working well on a Galaxy Tab and Archos 32 Internet Tablet.

And as a general shout-out, you've been a great Processing resource Mr. Shiffman ;) I've learned a lot from your examples.

Jesse Sco..

Re: Processing Android Tablet Adventures

2 years ago

Awesome. Next on my list... keep us posted! (pun intended)

ben.fry

Re: Processing Android Tablet Adventures

2 years ago

As long as you leave out a size() command that asks for a tiny window, it should be taking over the whole screen.

If it's not, then I may need to add another setting to mark the app as "ready to use enormous screens", because it may be stuck in some sort of compatibility mode for phone-only apps. (If that's the case, and someone wants to track down this magic setting in the sprawling android dev docs, it'd be super helpful.)

shiffman

Re: Re: Processing Android Tablet Adventures

2 years ago

leaving out size didn't work on the xoom. I'll see if I can track down anything more!

jimthree

Re: Processing Android Tablet Adventures

2 years ago

Is there any news on this? I've just got a xoom and very keen to start getting my sketches on there.

Jim

peterkirn

Re: Processing Android Tablet Adventures

2 years ago

Hmmm - this is worth investigating, Dan, as I think XOOM handles its screen resolution differently in order to accommodate HDMI output (which should also be really interesting). Probably the place to start would be to skip size and try manually passing in resolution, which could also mean a way to investigate how non-mirrored output would work...

Might have to drop by and try it out with you, especially as I'm pondering grabbing a XOOM myself. Querying resolution directly is possible - not desirable, but could be used to work backwards to what may be causing the app to fail.

shiffman

Re: Processing Android Tablet Adventures

2 years ago

Happy to report that with processing 1.5, if I just leave out size(), it runs in beautiful full screen on the motorola zoom! Or if you need to, you can say size(1280,800) for full screen resolution.

http://www.flickr.com/photos/shiffman/5631006137/

Hooray!

peterkirn

Re: Processing Android Tablet Adventures

2 years ago

Hey Dan, have you tried video output yet? Should just work with mirroring based on what I've heard from at least one other Xoom dev...

jimthree

Re: Processing Android Tablet Adventures

2 years ago

Hey folks,

I've managed to get a 3D sketch running on my xoom!

The camera moves from left to right, and then back again. There are two grids, one above and one below, each made up of about 200 lines, so the sketch is rendering about 400 lines in total. I'd say performance is ok, but it's not amazing, It doesn't feel like it's really using the hardware, it's probably running about 15-20FPS.

I've not seen any difference between using " size(1280, 800, A3D)" and " size(screenWidth, screenHeight, A3D)". This is a bit of a shame, because I know that you can make apps run in a fullscreen mode where the status bar "virtual-softkeys" are reduced to dots, and the rest of the icons are removed.

However, I'm thrilled to have got this far and I'm going to carry on an see what sensor stuff I can do next.

Code is below, if anyone can see anything that would obviously speed things up, let me know :)

Jim

PVector campos, target_p;
Grid topGrid, bottomGrid;
int direction = 0;
void setup()
{
size(screenWidth, screenHeight, A3D);
bottomGrid = new Grid(10,101,255,-50.0);
topGrid = new Grid(10,101,255,50.0);
campos = new PVector(600,0,0);
target_p = new PVector(0, 0, 0);
}
void draw()
{
background(0);
lights();
smooth();
if (campos.y > 200) direction = 1;
if (campos.y < -200) direction = 0;
if (direction == 0) campos.y++;
else campos.y--;
camera(campos.x, campos.y, campos.z, campos.x-1, campos.y, campos.z, 0, 0, -1);
topGrid.display();
bottomGrid.display();
}
class Grid
{
float spacing;
int gridSize;
int gridStroke;
float zpos;
Grid(float c_spacing, int c_gridSize, int c_gridStroke, float c_zpos)
{
spacing = c_spacing;
gridSize = c_gridSize;
gridStroke = c_gridStroke;
zpos = c_zpos;
}
void display()
{
for (int i = 0; i < gridSize; i++)
{
stroke(gridStroke-150);
if (i%5 == 0) stroke(gridStroke-100);
if (i == 0) stroke(gridStroke);
line(-(gridSize*(spacing/2)), (i*spacing)-((gridSize/2)*spacing), zpos, (gridSize*(spacing/2)), (i*spacing)-((gridSize/2)*spacing), zpos);
line((i*spacing)-((gridSize/2)*spacing),-(gridSize*(spacing/2)), zpos, (i*spacing)-((gridSize/2)*spacing),(gridSize*(spacing/2)), zpos);
}
stroke(0);
}
}

andres

Re: Processing Android Tablet Adventures

2 years ago

Line drawing actually needs to be re-implemented on both A3D and OPENGL2. For the time being, I recommend using a PShape3D object in LINES mode for better performance.

jimthree

Re: Processing Android Tablet Adventures

2 years ago

... Actually, I take that back, the performance isn't that bad at all. I've increased the speed at which the camera moves and added " println(frameRate);" into the draw loop. The emulator chugs along at 4fps, but the xoom is cruising at around 36fps.

Jim

Edit: Thanks Andres, I'll go look at the PShape3D call now :)

jimthree

Re: Processing Android Tablet Adventures

2 years ago

Hi Andres

I've changed my grid drawing class to use (what I think is) Pshape3D, but it's not working for me. It doesn't give any errors, but doesn't render anything on the screen.

I won't paste the whole sketch again, as it's largely unchanged from the version I have in my previous post, except that I'm declaring " PShape gridlines;" at the top of the sketch. I understand that I don't need to load the openGL libs in android, but I don't know if this includes the openGL2 libs. If I add " import processing.opengl2.*;" to the top, then the compiler complains that it can't find the package.

the new grid.dispalyGL() method looks like this, can you see any problems with the Pshape calls?

thanks

Jim

void displayGL()
{
//mergeShapes(true);
gridlines = beginRecord();
for (int i = 0; i < gridSize; i++)
{
stroke(gridStroke-150);
if (i%5 == 0) stroke(gridStroke-100);
if (i == 0) stroke(gridStroke);
beginShape(LINES);
vertex(-(gridSize*(spacing/2)), (i*spacing)-((gridSize/2)*spacing), zpos);
vertex((gridSize*(spacing/2)), (i*spacing)-((gridSize/2)*spacing), zpos);
endShape();
beginShape(LINES);
vertex((i*spacing)-((gridSize/2)*spacing),-(gridSize*(spacing/2)), zpos);
vertex((i*spacing)-((gridSize/2)*spacing),(gridSize*(spacing/2)), zpos);
endShape();
}
endRecord();
stroke(0);
}

jimthree

Re: Processing Android Tablet Adventures

2 years ago

Hey Folks.

I don't want to take over this thread, but I've had a lot of fun today with processing and my Xoom, and I thought I'd share some more code.

I apologise right now, the code is a bit of a mess, I've been so excited that I've not been very tidy! The code is based on the sketch I wrote and posted above, which displays two grids in 3D.

The camera in the 3D scene now moves in relation to the accelerometer, you tilt the device to move around the scene. it's not great, but it certainly works! There is also debug code in there, which is commented out for now which will list all the sensors available on your device.

I've spent most of the time I've had today getting bluetooth working, and it does! The sketch can now connect to another device (probably your Desktop or Laptop) and if it's already paired, it will open a SPP port and send the Accelerometer values along with the frame rate. I don't think it's very robust, and there is no GUI for the selection of the device you want to connect to. The sketch will list all the paired devices, but you have to add the MAC address of the intended device into the 'BTserver' string.

ToDo...

- I still can't get Andres suggestion for Pshape3D working...

- I want to try and get "lights-out" mode working for true full-screen

- I need to improve the BT implementation and robustness.

- I want to use the TYPE_LINEAR_ACCELERATION sensor, but that seems to throw errors.

import android.content.Context;
import android.hardware.Sensor;
import android.hardware.SensorEvent;
import android.hardware.SensorManager;
import android.hardware.SensorEventListener;
import android.bluetooth.BluetoothAdapter;
import android.bluetooth.BluetoothDevice;
import android.bluetooth.BluetoothSocket;
import android.view.*;
import java.util.List;
//For Sensors
SensorManager mSensorManager;
MySensorEventListener accSensorEventListener;
Sensor acc_sensor;
float[] acc_values;
//For Debug
//Sensor mSensor;
//List<Sensor> sensors;
//For Bluetooth
String BTserver = "--------ADD YOUR MAC ADDRESS HERE!------------"; //desktop
BluetoothAdapter mBluetoothAdapter;
BluetoothDevice mBluetoothDevice;
BluetoothSocket mBluetoothSocket;
Set<BluetoothDevice> devices;
String spp_buffer;
//For GUI
String[] fontList;
PFont androidFont;
//For 3D Scene
PVector campos, target;
Grid topGrid, bottomGrid;
int direction = 0;
float speed = 3;
PShape gridlines;
void setup()
{
size(screenWidth, screenHeight, A3D);
bottomGrid = new Grid(10,101,255,-50.0);
topGrid = new Grid(10,101,255,50.0);
campos = new PVector(600,0,0);
target = new PVector(0, 0, 0);
// Setup Fonts:
fontList = PFont.list();
androidFont = createFont(fontList[0], 8, true);
textFont(androidFont);
// Debug info
/*
println(fontList);
sensors = new ArrayList<Sensor>();
sensors = mSensorManager.getSensorList(Sensor.TYPE_ALL);
println("Number of sensors found: " + sensors.size());
for (int i = 0; i < sensors.size(); i++)
{
println("----------------");
mSensor = (Sensor) sensors.get(i);
println("Sensor Name:" + mSensor.getName());
println("Sensor Max Range:" + mSensor.getMaximumRange());
println("Sensor Type:" + mSensor.getType());
}
*/
println("------------------------");
}
void draw()
{
background(0);
lights();
smooth();
text((round(frameRate)+"fps"),8,10);
text(("Accelerometer: " + round(acc_values[0]) + " " + round(acc_values[1]) + " " + round(acc_values[2])), 8, 20);
//move the camera accordinf to the values from the sensors
campos.y+=acc_values[0];
campos.z-=acc_values[1];
camera(campos.x, campos.y, campos.z, campos.x-1, campos.y, campos.z, 0, 0, -1);
//camera(campos.x, campos.y, campos.z, target.x, target.y, target.z, 0, 0, -1);
//Draw the grids
topGrid.display();
bottomGrid.display();
// populate the buffer with information (string) we want to send. terminate with a " " for a new line
spp_buffer = round(frameRate)+"fps "+"X:"+round(acc_values[0])+" Y:"+round(acc_values[1])+" Z:"+round(acc_values[2])+" ";
try
{
//use a printStream to wrap the OutputStream so that we can easily send strings rather than just bytes
PrintStream printStream = new PrintStream(mBluetoothSocket.getOutputStream());
//print the buffer
printStream.print(spp_buffer);
//flush the buffer
mBluetoothSocket.getOutputStream().flush();
} catch (IOException e)
{
println("Writing failed: "+e);
}
}
// sources
// -------
// http://www.akeric.com/blog/?p=1313
// http://developer.android.com/reference/android/hardware/SensorEvent.html
void onResume() {
super.onResume();
println("RESUMED! (Sketch Entered...)");
// Build our SensorManager:
mSensorManager = (SensorManager)getSystemService(Context.SENSOR_SERVICE);
// Build a SensorEventListener for each type of sensor:
accSensorEventListener = new MySensorEventListener();
// Get each of our Sensors:
acc_sensor = mSensorManager.getDefaultSensor(Sensor.TYPE_ACCELEROMETER);
// Register the SensorEventListeners with their Sensor, and their SensorManager:
mSensorManager.registerListener(accSensorEventListener, acc_sensor, SensorManager.SENSOR_DELAY_GAME);
/////////////////////////////////////////////////
//bluetooth
/////////////////////////////////////////////////
//create a bluetooth adaptor from the default adaptor
mBluetoothAdapter = BluetoothAdapter.getDefaultAdapter();
//has that worked?
if (mBluetoothAdapter == null)
{
println("--Bluetooth adaptor NOT found");
}
else
{
//get a some info about the adaptor
println("--Bluetooth adaptor found");
println("--bluetooth name: "+mBluetoothAdapter.getName());
println("--bluetooth address: "+mBluetoothAdapter.getAddress());
println("--bluetooth enanbled: "+mBluetoothAdapter.isEnabled());
// find out how many devices are paired. we put the returned data int a java 'set'
devices = mBluetoothAdapter.getBondedDevices();
println("--bluetooth found"+ devices.size() +" paired devices:"+ devices);
//just to proove we can find all the paired devices...
//convert the devices 'set' into an array so that we can perform string functions on it
Object[] deviceArray = devices.toArray();
//step through it and assign each device in turn to mBluetoothDevice and then print it's name
for (int i = 0; i < devices.size(); i++)
{
mBluetoothDevice = mBluetoothAdapter.getRemoteDevice(deviceArray[i].toString());
println("--bluetooth Paried device ["+i+"]: " + mBluetoothDevice.getName());
}
//but now we use the BT device that we've hardcoded into the sketch becuase I don't have a GUI for choosing one.
mBluetoothDevice = mBluetoothAdapter.getRemoteDevice(BTserver);
println("--bluetooth server hardcoded as: "+mBluetoothDevice.getName()+" ["+BTserver+"]");
//this is a specific UUID that is used for SPP
UUID SPP_UUID = UUID.fromString("00001101-0000-1000-8000-00805F9B34FB");
//create an RFCOMM BluetoothSocket - a socket through which we can pass serial data
try
{
mBluetoothSocket = mBluetoothDevice.createRfcommSocketToServiceRecord(SPP_UUID);
} catch (IOException e)
{
println("createRfcommSocketToServiceRecord failed: "+e);
}
//and then try and connect() to remote device.
try
{
mBluetoothSocket.connect();
} catch (IOException e)
{
println("connect() failed: "+e);
}
}
}
void onPause() {
// Unregister all of our SensorEventListeners upon exit:
mSensorManager.unregisterListener(accSensorEventListener);
println("PAUSED! (Sketch Exited...)");
super.onPause();
// I should close a load of bluetooth stuff here.
}
// Setup our SensorEventListener
class MySensorEventListener implements SensorEventListener {
void onSensorChanged(SensorEvent event) {
int eventType = event.sensor.getType();
if(eventType == Sensor.TYPE_ACCELEROMETER) {
acc_values = event.values;
}
}
void onAccuracyChanged(Sensor sensor, int accuracy) {
// do nuthin'...
}
}

And the Grid class is:

class Grid
{
float spacing;
int gridSize;
int gridStroke;
float zpos;
Grid(float c_spacing, int c_gridSize, int c_gridStroke, float c_zpos)
{
spacing = c_spacing;
gridSize = c_gridSize;
gridStroke = c_gridStroke;
zpos = c_zpos;
}
void display()
{
for (int i = 0; i < gridSize; i++)
{
stroke(gridStroke-150);
if (i%5 == 0) stroke(gridStroke-100);
if (i == 0) stroke(gridStroke);
line(-(gridSize*(spacing/2)), (i*spacing)-((gridSize/2)*spacing), zpos, (gridSize*(spacing/2)), (i*spacing)-((gridSize/2)*spacing), zpos);
line((i*spacing)-((gridSize/2)*spacing),-(gridSize*(spacing/2)), zpos, (i*spacing)-((gridSize/2)*spacing),(gridSize*(spacing/2)), zpos);
}
stroke(0);
}
void displayGL()
{
//mergeShapes(true);
gridlines = beginRecord();
for (int i = 0; i < gridSize; i++)
{
stroke(gridStroke-150);
if (i%5 == 0) stroke(gridStroke-100);
if (i == 0) stroke(gridStroke);
beginShape(LINES);
vertex(-(gridSize*(spacing/2)), (i*spacing)-((gridSize/2)*spacing), zpos);
vertex((gridSize*(spacing/2)), (i*spacing)-((gridSize/2)*spacing), zpos);
endShape();
beginShape(LINES);
vertex((i*spacing)-((gridSize/2)*spacing),-(gridSize*(spacing/2)), zpos);
vertex((i*spacing)-((gridSize/2)*spacing),(gridSize*(spacing/2)), zpos);
endShape();
}
endRecord();
stroke(0);
}

I promise I'll post the code somewhere else and link to it next time! I hope this helps people, but to be honest, there is nothing more fun than working it out for yourself!

Jim

local_guru

Re: Processing Android Tablet Adventures

2 years ago

Im using a Archos 101 running android 2.2

and it works like a charm with processing - after some fiddling around with the udev-rules it even starts the
sketches with "run on machine"

I wrote a small android-monome clone yesterday to test the use of external libraries and sending
osc-events

http://www.local-guru.net/blog/2011/04/28/android-monome-clone-in-processing