So I'm following the Corona instructions to install the Android SDK, and it just feels like we're following completely different instructions:
- There's no "install" on OSX. It's just big folder with \eclipse\ and \tools\ folders. (I moved that into Applications as a guess; is that the "sensible location"?)
- platform-tools is installed by default, according to what the SDK manager tells me. (And despite what Google's own documentation says, there is no "Android SDK" file to run on OSX. Just "android"
- "adb" doesn't do anything. In platform-tools, there is an adb object, but running it spawns a terminal window that called "adb; exit;", displaying help information followed by [PROCESS COMPLETE] and the end of the usefulness of that terminal window.
- A path is not added. As you might expect from just moving the SDK into a folder and running the manager, there is no path added. And neither the Corona instructions nor Android instructions offer any idea how one would add a path in OSX so that adb can be called anywhere.
- You can't actually run the command line as displayed. For one, you can't just type the name of a command to run it in terminal; adb requires typing "open" first. And if you do that, none of the arguments are allowed.
- ddms does not display most Corona print messages. In desperation, I tried running ddms (also in platform-tools, it's a not bad little GUI for android debug output) And it will occasionally display a print statement. But in my case it's only displaying one, across the entire program. 99% do not appear.
- You can't use adb output anyway without enabling developer mode. I'm not expecting Corona to explain this one but it should be mentioned to at least google how to do it for your device. (In the Note 3, for instance, you need to tap on the build number 7 times, and then enable USB debugging.)
General criticism aside - I'll help rewrite the page if you'd like - any ideas how to actually get adb working on OSX? (I'm out of ideas.)