Mac won't detect phone

Android Processing

ak_eric

in Android Processing • 2 years ago

Recently got a new mac. First mac... ever. So, I'm a complete mac noob. I still managed to get all the appropriate Processing\Android software installed, but I can't get Processing to detect the phone.

I have the Phone's usb development set to "usb debugging" like on my PC. The first time I plugged it into the mac the mac tried to connect to it as a modem (I think that's what it was trying to do?). Then every time after that when I plug it in the phone says "connected", but the mac makes no sign of detecting it. DDMS doesn't see it either

If I instead change the usb settings to "mass storage" and mount the drive, the mac can see it for file transfer, but not for any kind of development (just like on the pc).

So I downloaded this nifty app called adbWireless which lets me connect via adb wirelessly. This works really good in fact: I can connect wirelessly (no more usb needed) and the phone is detected by the DDMS. So I know I'm hooked up.

But when I try to "present" in Processing, I still get the "Waiting for device to become available" message. No love.

Really bummed. Anyone have any ideas?

Replies(12)

andres

Re: Mac won't detect phone

2 years ago

Strange. I don't remember doing anything special to get the phones detected from my Mac.

Sometimes the USB connection can get buggy, in cases like this a reboot (of the phone) usually solves the problem.

Jesse Sco..

Re: Mac won't detect phone

2 years ago

I've had the same issue, and a reboot fixed it.

ak_eric

Re: Mac won't detect phone

2 years ago

Thanks guys. I'd rebooted in the past with no change, but this morning ddms did detect the phone via usb so that's good.

Still doesn't work though (still waiting for device to become available). But I think I'm narrowing it down. I get a bunch of errors when I try to present a sketch (that worked fine on the pc). Starts with this:

AndroidEnvironment.listDevices() did this to me

java.io.IOException: Cannot run program "adb": error=2, No such file or directory

at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)

at java.lang.Runtime.exec(Runtime.java:593)

at java.lang.Runtime.exec(Runtime.java:466)

at processing.app.exec.ProcessHelper.execute(ProcessHelper.java:65)

at processing.app.tools.android.AndroidSDK.runADB(Unknown Source)

at processing.app.tools.android.AndroidEnvironment.listDevices(Unknown Source)

at processing.app.tools.android.AndroidEnvironment.refresh(Unknown Source)

at processing.app.tools.android.AndroidEnvironment.find(Unknown Source)

at processing.app.tools.android.AndroidEnvironment.blockingGetHardware(Unknown Source)

at processing.app.tools.android.AndroidEnvironment.access$200(Unknown Source)

at processing.app.tools.android.AndroidEnvironment$3.call(Unknown Source)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

at java.lang.Thread.run(Thread.java:680)

Caused by: java.io.IOException: error=2, No such file or directory

at java.lang.UNIXProcess.forkAndExec(Native Method)

at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)

at java.lang.ProcessImpl.start(ProcessImpl.java:91)

at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)

... 16 more

Looks like it can't run adb? But I can run adb from a shell no problem. If I print my env the dir where adb lives is in it. Any more thoughts? Appreciate it

andres

Re: Mac won't detect phone

2 years ago

Maybe you have to add this line:

export PATH=${PATH}:<full path to your android sdk folder>/tools

to your .bash_profile file (located in the user folder).

ak_eric

Re: Mac won't detect phone

2 years ago

Thanks andres, I think we posted at the same time :) I had done that, see post below:

----

Ok, so it looks like that the PATH that Processing sees is different from what a shell sees:

// simple sketch to print the env vars in Processing:

import java.util.Map;

Map<String, String> env = System.getenv();

for (String envName : env.keySet()) {

println(envName + "=" + env.get(envName) );

}

Processing PATH, before turning on 'android mode' (made a little sketch that prints this):

PATH=/usr/bin:/bin:/usr/sbin:/sbin

Processing PATH after turning on (and off) 'android mode':

PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/Users/ak_eric/Documents/android-sdk/tools:/usr/bin:/bin:/usr/sbin:/sbin

Mac Shell PATH: (picking up my edits in .bash_profile)

PATH=/Library/Frameworks/Python.framework/Versions/2.6/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/Users/ak_eric/Documents/android-sdk/tools: /Users/ak_eric/Documents/android-sdk/platform-tools

adb lives in the /android-sdk/platform-tools, and that's why the shell sees it.

I cracked open Processing's preferences.txt file, and found this line:

android.sdk.path=/Users/ak_eric/Documents/android-sdk

If I delete that line, Processing says it can't find the android sdk. So it seems pretty obvious that Processing isn't seeing the path that the shell sees.

Which raises the question: how can I change the PATH that Processing sees? And why is it different from the shell?

andres

Re: Mac won't detect phone

2 years ago

What version of Processing are you using? I ask this because with the pre-release 0192 (plus Android SDK 8), everything works smoothly. However, if I try to run the binaries I compile myself from the trunk, I get exactly the same error you posted earlier ("AndroidEnvironment.listDevices() did this to me...", etc). But I haven't updated my local copy of the trunk for two weeks or so, maybe I'm missing some important changes/fixes...

ak_eric

Re: Mac won't detect phone

2 years ago

I'm using 0191: This is what I had installed on my PC. And correct me if I'm wrong here: The wiki says that 0192 only works with SDK 8: My phone is only rooted to 2.1, which is SKD 7 (right?). I had concerns of installing a new sdk into the system and not having it be compatible with the phone itself. Is that correct?

I'm such a mac noob I'm sure I'm missing a lot here :-S But it sure seems like the stuff I put in my .bash_profile isn't being seen by Processing at all (I tried .bashrc and that failed as well, not that I know what I'm doing...). Is there some lower-level location to store env vars on the mac? I did a closer inspection of the path printed via "env" in a shell, and my code posted above to query the env in Processing, and they are two different things. I can add new vars to my .bash_profile, and they won't show up in Processing. I'm missing some secret piece of mac knowledge :P Thanks for the help.

ben.fry

Re: Mac won't detect phone

2 years ago

You have to use 0192, which fixes these issues.

You're mixing the SDK "Tools" version 8 and the Android Platform, version 7 (Android 2.1) or 8 (Android 2.2). It's incredibly confusing, but the Tools (the developer tools download) must be version 8. And then you need to install Android Platform version 7 (at least) which is what works with Processing (and what's installed on your phone, if it's Android 2.1). It's unfortunate that they use identical numbering for both.

onato.com

Re: Mac won't detect phone

2 years ago

Processing will take the path from the shell when you open it from there i.e.

open /Applications/Processing.app

ben.fry

Re: Re: Mac won't detect phone

2 years ago

That's true in other cases, but not relevant to the issue here. Especially because the PATH is manipulated by Android Mode in Processing.

ak_eric

Re: Mac won't detect phone

2 years ago

Thanks Ben & Andres: So, I installed 0192, and now it 'just works'. Yes, those version are a bit confusing, I was sure to think it would break things. But I'm good to go, really appreciate you guys! I'm back on the Mac bandwagon again :P

aljones15

Re: Mac won't detect phone

2 years ago

The problem appears to be that adb has moved from tools to platform_tools in the android_sdk folder.
copy adb from platform_tools to the tools directory and it should work.

Google placed the following warning in the tools section:

The adb tool has moved to platform-tools/

If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"

Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.

Top Reply