Scott Geeks Out

These components/categories need to be reckoned with in order to add a peripheral to WearScript:

build.gradle

init.js

WearScript.java

add a new <your>DataProvider

DataManager

add a new <your>Manager

ManagerManager

add new <your>DataEvent(s)

add any new dependencies into the file tree.

In this particular instance, these are the files that changed:

build.gradle init.js init.js.min WearScript.java MyoDataProvider.java MyoAccelerometerDataEvent.java MyoGyroDataEvent.java MyoOrientationDataEvent.java MyoPairEvent.java MyoTrainEvent.java DataManager.java ManagerManager.java MyoManager.java

Now you need to go to /etc/paths to define them.

There are so many pitfalls, it's hard to count them. Two major parts here.

Assuming you're able to get the device into fastboot and recognized by `fastboot devices`, here's what to do.

If your device isn't booting and you need to get it into fastboot mode

Flashing the image

Here's what worked for me on OS X just now, documenting just the right thing to do, and none of the million other things I tried. I was updating to XE12, so I downloaded `glass_1-img-947604.zip` from the Glass Developer site. Unzip that into a directory of the same name. Then from your current directory, which now contains a directory called `glass_1-img-947604`, run

export ANDROID_PRODUCT_OUT=glass_1-img-947604 && fastboot flashall -w

For me the output was http://pastebin.com/hNiXs1mj

Getting the device into fastboot mode

I probably don't need to tell you here that the standard way to get into fastboot mode is to run `adb reboot bootloader`. If, however, you're in a state where you can't turn adb on because the system is not booting at all, this doesn't help you. So you need the hardware technique for getting into fastboot.

Start from the device being off, unplugged, and not totally dead. If it's not responding to the power button, you can hold it down for 10-15 seconds until it turns off.

Press and hold the camera button.

Keeping the camera button pressed, give the power button a single press.

Within two seconds the power light will come on. Keep the camera button pressed for another 2 seconds, then release.

The power light will stay on for something like 5 to 10 seconds, and then it will go off and enter a mode where it flashes briefly every 3 seconds or so. It's now in fastboot mode.

Plug it into your computer, and if that is setup right, Glass will now show up in `fastboot devices`. 

You need the Recon version of adb. As documented here http://goo.gl/c7dzzZ, you get it from /ReconApps/Developers *on the device*. Kind of like a bike that has its own little toolkit built in.

It's really easy to get started with the SDK. It's a jar file and in Android Studio you just need to drag it into your project and then select "Add as Library" from the right-click menu.

From inside the folder containing all the m4a’s

find . -iname “*.m4a” | while read file; do faad -o - “$file” | lame —preset insane - “${file%m4a}mp3”; done

I was able to get lame and faad from brew. Note that the package containing faad is called faad2. Using while read keeps you safe if there are spaces in the filenames (as there typically are in iTunes filenames).

I had given up long ago, but performed a Google search now, just for kicks. Turns out fn+left arrow is home and fn+right arrow is end. Awesome! Another corollary is that fn-up is page-up and fn-down page-down.

So useful! An item appears in the Notification Shade starting something like 90min before an alarm is set to go off. It can be used to "Dismiss Now". I find this particularly useful for repeating alarms, where "dismissing early" would otherwise require either (1) turning the alarm off and risking that you'll forget to turn it back on for the future, (2) changing the time of the alarms to be before the current time -- which is cumbersome, and screws up the time your alarm is set at. 

Examples:

You wake up before your morning alarm. If you leave it, it will go off while you're in the shower, so you must use one of the two strategies I mentioned above. Of course, you are probably in the habit of setting your alarm before you go to sleep. But hey, one less thing to do.

I was doing some local WearScript development, and was pulling my hair out because I couldn't get the application to load changes I'd make to javascript files used by the page. Of course any changes I made to the scripts embedded in the html would be changed, but the script includes just wouldn't change. For a little while in order to make progress I just renamed the script every revision. That's obviously a horrible thing to do, so I eventually found a better solution.

webview.clearCache(true)

This clears the resource cache of all WebViews associated with the current application.

Now when I use adb to push new versions of javascript files, they get reloaded immediately! The disadvantages of this should be pretty obvious: if there's something big that's not changing, there's no point in reloading it every time. But when the hell am I going to be loading something big in WearScript? The resource cache is dwarfed by the bandwidth used for photos and videos in other applications, so I figure the advantages pretty much outweigh the disadvantages. This may affect offline access, but that deserves its own separate treatment anyway

http://developer.android.com/reference/android/webkit/WebView.html