Skip to main content

Android Voice Commands for Cyclists Listening to Podcasts or Music

Disclaimer: I do not recommend using earphones while on your bike, but there are times or roads where I think it's OK. Pull out your earphones when nearing potentially dangerous situations (like intersections). At least pause the audio.

These tips also apply to anyone unable to look at and touch their device, leaving voice commands their only option (useful for visually impaired people, people wearing thick gloves, etc).
First of all, you need an Android with a fairly new version of Google Now installed, like Lollipop.
You'll need a headset with a microphone button. I’ve got an iphone headset that works great with my old Moto G, excluding the volume control.
You need to make sure that a connected headset can bypass the device’s lock mechanism. It’s in:
        Settings -> Language & input -> Google voice typing -> Hands-free
Your audio playback software has to work with the Google Now commands. I’ve tried Google Music and BeyondPod successfully.
So, off we go! You’ll want to practice a bit before doing this on your bike: 
  1. Lock your phone and put it in your pocket with the headset connected.
  2. Hold down the mike button until you hear a bell like “ba-ding!”. 
  3. Let go of the button.
  4. Enter the voice command clearly (you don’t have to say “OK Google” first)
  5. Wait until you hear another cheery ding sound, followed by Google Now’s voice confirming your command.
If you hear “Bong bong bong bong…”, that means there’s no signal or something. Just try again later. If Google Now doesn't grok what you're trying to say, start over.
Here are the commands I’ve found useful on the bike so far:
  • Resume” - this will start audio playback in whatever state you did previously (I think). Also un-pause.
  • Pause” - self-explanatory. Note that tapping the mike button will also pause/resume, but I have found it to be a bit unreliable when resuming especially.
  • Skip to the next track” - self-explanatory, some variations in how you formulate it is OK I noticed.
  • Open beyondpod” - opens the app BeyondPod. This could be useful if I want to get out of Google Music.
  • Tell my wife on hangouts, I’m on my way home” - I always forget to tell my wife when I leave work on the bike, so this is handy. If you leave out the “on hangouts” bit, it will just send a text message. Not sure if other IMs are supported.
  • What time is it” - handy to see if I’m running late.
  • What’s the weather like tonight/tomorrow” - always good to know when cycling.
  • What’s my schedule today/tomorrow” - I haven’t tried this but could be useful.
  • Help” - this one will make Google Now explain some voice commands for you.
If you’re cycling with some speed, you’ll need to cup the mike with your hand to avoid overloading your command with noise from the wind. For the same reason, I try not doing phone-calls while on the bike.
Any useful commands that I’ve missed? 
There are various lists of possible voice commands online, but unfortunately most of them are just useful when you’re looking at the phone in your hand. More can be found here:

Popular posts from this blog

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do:

# install vcsh & myrepos via apt/brew/etc
vcsh clone https://github.com/tfnico/config-mr.git mr
mr update

Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files. No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed:

config-atom.git
    -> ~/.atom/*

config-mr.git
    -> ~/.mrconfig
    -> ~/.config/mr/*

config-tmuxinator.git  
    -> ~/.tmuxinator/*

config-vim.git
    -> ~/.vimrc
    -> ~/.vim/*

config-bin.git   
    -> ~/bin/*

config-git.git          
    -> ~/.gitconfig

config-tmux.git  
    -> ~/.tmux.conf    

config-zsh.git
    -> ~/.zshrc

How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for operating on many repositories at the same time.

I discovere…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s https://svn.company.com/repos/project-foo/

You'll get this .git/config:

[svn-remote "svn"]
        url = https://svn.company.com/repos/
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):
    remotes/trunk
    remotes/feat-bar

(Compared to regular remote branches, they look very odd because there is no remote name i…

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:
How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without the…

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well:

I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there.

It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences.

To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer science a…