googlevoice
Latest
Tokyo's Shibuya gets a big-screen Google voice search terminal
Arguably, the whole convenience of Google's search and map skills (and by association, the voice-guided version) is the fact it's on your smartphone -- which is right in your pocket. However, In a bid to explain to Tokyo-ites that there's more to the eminently tech-friendly Shibuya outside of That Starbucks and the scramble-crossing, Google's erected a temporary structure right outside the station. Not only can you make voice search requests for the nearest tech store or... french patisserie, it'll display a map and directions on a huge 138-inch screen -- which you can then take a photo of, presumably, with your smartphone.
Google Voice Search can now handle multiple languages with ease
It's not unusual for people who speak several languages to forget particular terms, and that can be pretty frustrating when you're trying to look up stuff through Google Voice Search. Thankfully, the latest Voice Search update for Android gives you the power to choose up to five languages as your default instead of just one, making random lapses in memory a bit less annoying. This change, spotted by Android Police (and which the Google Search team first revealed on Reddit in July), allows you to do voice queries in different tongues without having to dive into the settings page each time. The app now even understands a query even if it's spoken in more than one language -- the bad news is you're still stuck with English as the sole default if you use the OK, Google command. If that's not a dealbreaker, just sit tight and wait for the update to arrive on your phone, if it hasn't yet.
Google Voice offers web-based calls through Hangouts, no G+ profile needed
The rumor is that eventually we're going to see Google Voice merged completely into Hangouts, and that's getting even closer to becoming reality. You can now make phone calls via Hangouts directly from the Google Voice website, no Google+ necessary. As Mountain View's Alex Wiesen notes on G+, the new feature is listed as an option in the "phone to call with" drop-down box. It seems a bit minor, sure, especially when you consider that Hangouts is already how you make phone calls from within Gmail -- but any updates for the oft-neglected service are welcome, right?
Google Voice plans to make transcriptions better with your help
What's the silliest Google Voice transcription you've gotten? That question might have come up during a meet-up with tech-loving friends before -- after all, you're not the only user who's ever received garbled voicemail-to-text messages. In fact, even Google Tech Lead Manager Alex Wiesen admits they can be "unintentionally hilarious," to the point that the company's now asking for your help to make transcriptions better. Now, when you log into Google Voice on the web, you'll be given the choice to share your voicemail messages (anonymously, thank goodness) to be analyzed for accuracy by automated systems. While you can already submit individual messages for analysis, you'll automatically be sending the system all your messages, all the time, if you decide to participate in this project. Don't worry, though: you can always disable it through Google Voice's settings page in case you change your mind later on.
Patch GrowlVoice using Keyboard Maestro to prolong its life
Google recently made some changes to the way Google Voice responds to some requests, and GrowlVoice stopped working. Update (2014-05-10): There is now a much easier way to do this now. See http://github.com/szhu/fix-growlvoice for instructions on patching this which does not require Keyboard Maestro. Background: As I understand it, there has never been an official API for Google Voice, so developers have had to figure things out on their own and build a workable solution without the tools they really need. Google has announced plans to integrate Google Voice into Google Hangouts, and the recent change which broke GrowlVoice was part of that. Could GrowlVoice be patched to fix this? Probably, but how long will it be until Google changes something else? And how long will it take Apple to approve the update for the Mac App Store? With no official API for Google Voice, and Google Voice's entire future uncertain, I don't think I'd want to try keeping the app working either if I was the developer. However, just as clever developers found a way to make Google Voice work without an official API, someone else has figured out how to make Google Voice's current setup work with GrowlVoice, to extend its life, at least until Google changes something else. Elliot Kroo (@ellkro) came up with an ingenious solution to patch the information that comes from Google Voice so that GrowlVoice can understand it. His instructions can be found at: https://gist.github.com/kroo/11205755. A big-time hat-tip and thank you to Terry McCall (@hagure) for telling me about Elliot's instructions! Unfortunately, even after you download the necessary files, this fix requires that you run a Terminal command every time GrowlVoice launches. You can probably already guess what I thought when I heard that: "Wait... you have to do something every time something else happens? Can I automate that?" Spoiler alert: yes. How? Say it with me: Keyboard Maestro. Here are the (non-automated) steps involved Before we can automate it, we have to know what steps to take to make it work manually. Download the files described in the 'gist' Launch GrowlVoice Wait for an alert panel that looks like this: Press OK Run command OK, now that we know the steps, we can automate them. How to do this in Keyboard Maestro Create a new macro which will run the following commands every time GrowlVoice launches: "Pause Until" there is a button "OK" Press "OK" button Run Terminal commands Now, that last step is a little tricky because one of those commands has to be run with elevated "permissions" which can be done, but requires some extra work. There are two ways to accomplish this: with AppleScript or with sudo. (N.B: Step 3 will also download the necessary files if they are not already installed.) AppleScript This way is a little easier, because you don't have to get into the Terminal. However, you have to enter your administrator password every time GrowlVoice launches: sudo Requires that you add an entry to your /etc/sudoers file via visudo But once the initial configuration is done, everything else can be automated, meaning that you do not have to enter your password each time GrowlVoice launches. This is the line you need to add to /etc/sudoers: %admin ALL=NOPASSWD: /Users/luomat/Dropbox/etc/fix-growlvoice/cycript However, you need to change /Users/luomat/Dropbox/etc/fix-growlvoice/ to the correct path on your Mac. If you aren't sure what any of that means, use the AppleScript version. Download Download and install one of these into Keyboard Maestro: Fix-GrowlVoice-with-AppleScript Fix-GrowlVoice-with-sudo Whichever one you use, you will have to edit the line in the shell script section: DIR="$HOME/Dropbox/etc/fix-growlvoice/" change that to be wherever you want the files to be kept. (If you use the sudo version, $DIR should be the folder where the cycript command is found.) Regardless of which version you choose, the first time you run it, the necessary files (as referenced in the "gist" above) will be downloaded and installed the directory you set as $DIR. It's not a fix, it's a patch If GrowlVoice's developer doesn't update the app, this patch will only work until Google changes something else, and it will have to be run each time the app launches. It might not be the most elegant solution ever, but it's better than not having GrowlVoice at all. Again my thanks to Elliot Kroo (@ellkro) and Terry McCall (@hagure). Some days I really love the Internet.
How to port your Google Voice number to your iPhone
Earlier this week, I saw this post from @GrowlVoice: As of today, Google has officially shut off GrowlVoice's access to Google Voice as part of their integration of Google Voice into Hangouts. Google has also shut off 3rd-party access to Google Voice VoIP, and it seems that the writing is on the wall for Google Voice as a standalone product in any form. I have a Google Voice number that I really like and wanted to keep, so I decided I wanted to port it out of Google Voice and onto my Verizon iPhone. I wasn't even sure this was possible since Google Voice isn't really a cell phone provider like Sprint, AT&T, and Verizon, but Dan Moren of Macworld was kind enough to point me in the right direction to an encouragingly titled page at Google: Port your number out of Google Voice. In sum, on the Google side of things, there are two steps to porting your number out of Google Voice: Go to https://www.google.com/voice/unlock and follow the few steps there to say that you want to unlock your Google Voice number. Pay Google $3 as "a one time fee to port your number away from Google Voice" unless you are using a number that you ported into Google Voice. I did both of those steps and then decided to call Verizon. There may be a way to do this without having to talk to Verizon customer support, but since it was an unusual situation, I thought I'd be better off talking to another human being. Verizon has about eleventy-milion phone numbers for various technical/customer support issues. The number I called was 800–922–0204. When prompted, I pressed 3 for tech support. At the next prompt I said "Porting a number" and then "Porting to Verizon wireless" when it asked what kind of port I wanted. Lastly I was asked if I wanted to add a line to my account or replace an existing account, so I said "replace" since I was going to replace my current iPhone number. After that I was on hold for 5–10 minutes before being connected with "Jason" at Verizon Wireless. I explained what I wanted to do, making it clear that I wanted to move a number to Verizon, not the other way around. There were five pieces of information that Jason needed: The name of the account holder on the Google Voice account. The "billing address" for the Google Voice account. I wasn't sure what to use for that, so we just used the same billing address that was already associated with my Verizon account. The phone number that I wanted to port to Verizon. My "account number" with the carrier which currently held the number I wanted to port over. We used my Google Voice phone number. A password, if any. At first Jason thought this meant he was going to need my Google Account password, but it turned out there was an option for "No Password" so we used that. Once the whole thing went through, the system said that it would take 4–24 hours before it would take effect, and I would have to power cycle my iPhone for the new number to be recognized. (That turned out to be incorrect. Read on.) Jason said that in his experience it usually only takes about 2 hours, but it could take longer, and if it hadn't happened in 24 hours, give him a call back. After I hung up the phone, I realized that there were a few sites which used my current iPhone number to send me SMS login verifications for Two-Factor Authentication systems, most notably Paypal and Twitter. (Most others use the Google Authenticator, which I use with Authy.) For Twitter, I had to go to https://twitter.com/settings/security and choose "Don't verify login requests" and then to https://twitter.com/settings/devices and choose "Delete My Phone." Once the number was ported, those were the two URLs I needed to re-add my iPhone. For PayPal, I had to go to https://www.paypal.com/cgi-bin/customerprofileweb?cmd=%5fsecurity%2dtoken and "Deactivate" my "PayPal Security Key" and after the number was ported, I had to go to https://www.paypal.com/us/cgi-bin/webscr?cmd=_register-security-key-mobile to enable my Security Key with my new iPhone number. Then it was just a matter of waiting. I went back to https://www.google.com/voice/unlock and say that my Google Voice number was now listed as "Unlocked (Approved [1])" and they added: "You have a Google Voice number that has been unlocked. You can now initiate porting with your new provider. We will notify you by email once the number has been ported away." (Spoiler Alert: I never received an email from them.) Still later, I went back to that page and it said: "Google Voice has successfully approved your request, but the carrier to whom you are porting hasn't completed their necessary action. If you are still having issues and your number doesn't successfully port in 2–3 business days, please contact your new carrier for support, as Google Voice is unable to take any additional action." Waiting Two hours passed, four hours passed, 24 hours, 36 hours, and nothing. However, this morning when I sat down at my Mac, there was an alert panel from iMessage, asking if I wanted to use my Google Voice number for iMessage. I clicked yes, and then checked my iPhone by going into the Phone app, and inside the Phone app I tapped on the "Contacts" tab, and scrolled all the way to the top. It still showed my old iPhone number, even after restarting it. I tried to send an SMS (not a blue-colored iMessage, but a green-colored SMS) and it failed to send. I tried making a phone call, and was greeted by an automated message that they could not authenticate my iPhone. I tried rebooting again, but still nothing. I thought about going to Settings » General » Reset » "Reset Network Settings" but I knew that would also remove all my saved Wi-Fi passwords, so I decided to wait a few more hours and try again. In the meantime, iMessage and FaceTime both showed my Google Voice number as associated with my iCloud account, and I could use Verizon's 3G and LTE data networks, I just couldn't make any calls or send any SMS messages. Eventually I called Verizon (#8899, as the automated message suggested). After about 20 minutes on hold I was finally connected with someone, explained what had been going on, and she said "You aren't on that phone now, are you?" Well, of course I was, because I don't think calling #8899 from my landline was going to get me to Verizon Wireless tech support. She asked if there was another number where she could call me back, and I gave her my number, but asked: "If I wasn't on my iPhone right now, what would you have me do?" "Reset your network settings," she said. She wrote down my landline phone number and promised to call me back in about 10 minutes. I reset the network settings, my iPhone rebooted, the Verizon logo showed up, the LTE logo appeared, I went into the Phone app, looked up my own number and -- my old phone number was still there. I was in the car and had my iPhone on the windshield mount, but there wasn't anywhere I could pull over, so I just left it unlocked on the screen showing my old phone number. About two minutes later, the number changed right before my eyes. One second it was the old number, and then it was the new number. Success! Finally I could make calls, send/receive regular SMS messages, and everything else. Summary of Steps If I was starting over from the beginning, here's what I would do: Go through my texts for the past month or so and look to see what (if anything) is using my iPhone number for SMS instead of my Google Voice number. Temporarily disable any two-factor authentication systems which rely on SMS. Go to https://www.google.com/voice/unlock and pay Google $3 to unlock my Google Voice number. Call Verizon (800–922–0204 worked for me) and navigate the phone options for "Tech Support" and then "Port a phone number" and then "Port to Verizon" Verizon will need your name (as it appears in Google account), your Google Voice number is the number you want to port and your "account number" and there is no password for porting a number out. Accept that you may have to wait 2–3 days, and be on the lookout for iMessage or FaceTime to tell you that your Google Voice number has been associated with your account. Don't bother just rebooting your iPhone to see if that does it, bite the bullet and choose "Reset Network Settings." Tip: Whenever I am somewhere that has a Wi-Fi password, I always save the network name [SSID] and the password in 1Password, so if I do have to reset my network settings, I will still have the Wi-Fi passwords for the various networks that I use. Once the port has been completed, be sure to reenable any two-factor authentication systems which use SMS. Although these instructions were for a Verizon iPhone, I would assume that the process is similar for AT&T or Sprint, with the obvious exception of who you'd call to initiate the port from your carrier.
Google Voice now supports MMS messages from T-Mobile users
Your friends on Sprint aren't the only ones that can flood your Google Voice number with MMS messages anymore -- now, even your T-Mobile pals can, too. Google's Nikhyl Singhal recently mentioned that Mountain View's been working on Voice MMS integration, so it's no surprise that another telcom's followed so quickly after The Now Network. Unfortunately, the process is nowhere near seamless: you don't actually get images, clips or whatever MMS file people send on your Voice account. Instead you get an SMS notification that a multimedia message was sent to your Gmail as an attachment. There's no word on whether the feature will follow for users on Verizon, AT&T and other carriers, but for now, you can always introduce friends and family to third-party messaging apps.
Google says it's cracking down on third-party Google Voice apps, expanding SMS support in Hangouts early next year
Google didn't have much to say about Google Voice integration in its Hangouts app when it announced the latest version earlier this week, but the company's Nikhyl Singhal has filled in a few more details on his Google+ page today. Singhal notes that while the update (and its SMS support) only works with Google Voice numbers if you have the service enabled on your Sprint phone, it's "working to support SMS messages for all Google Voice phone numbers by early next year." He further goes on to say that the company is also working to offer Google Voice phone numbers outside the US and support MMS, but he's not going so far as to offer a timeline there, saying "we need to work with carriers and this can take some time." Beyond that, Singhal also confirmed that Google will now be more heavily enforcing its Terms of Service and cracking down on third-party apps that offer unauthorized calling and SMS services through Google Voice. Those app makers will apparently have until May 15, 2014 to transition their users to another service. As for the new Hangouts app itself, while it's available on the new Nexus 5, other Android users will still have to wait a bit longer for the update to show up in the Play Store.
Google Hangouts for iOS adds voice calling, Google Voice integration
Google has updated its Hangouts app with a number of VoIP features. The new version 1.3 allows iPhone, iPad and iPod touch users in the US and Canada to call US and Canadian phone numbers for free right from the app. Users can also call phone numbers in other countries for a cost. The update also adds more VoIP features in the way of allowing a Google Voice user to make phone calls to Google Voice numbers and receive phone calls to their Google Voice number. The move could make traditional phone carriers nervous as both features only require a data connection and mean that a subscriber isn't using their plan's minutes. Check out the release notes below to see all the features of the latest update. What's New in Version 1.3.0 See which of your friends is using Hangouts, and who can be reached right now Call phone numbers from your iPhone, iPad, or iPod Touch (free to the US and Canada) Make and receive calls using your Google Voice number Send and receive animated GIFs that play inline Hangouts will temporarily turn down your music (instead of stopping it) when you receive an incoming message Hangouts is a free download.
Google Hangouts for iOS can call US & Canada for free, receive Google Voice calls
The Google Hangouts app for iOS is getting a major update this evening that gives it all new calling features on Apple's mobile hardware. Users can call phone numbers directly from the app itself, with no charge for any calls to US & Canadian numbers (international calls work too, for a fee). If they have a Google Voice account it's even more useful since it can both make and receive calls now, with outgoing calls showing your GV number and incoming calls popping up in the Hangouts app itself. Also new, are the better visible indicators of who is reachable right now that recently popped up in the Android version, inline animated GIF support and now incoming calls don't stop user's music -- they just pause it. We're already expecting Hangouts to take a step to the forefront in Android 4.4 KitKat -- check the app's placement in yesterday's Nexus 5 leak for a peek -- and this update will probably make things easier for users that cross back and forth between platforms.
Google Voice update adds short code support, warns you when you text 911
An update to Google Voice today brings a useful, if not earth-shattering, new feature: support for SMS short codes. If your primary phone number is the one associated with your Google Voice account, this means you'll finally be able to use these codes for online banking and other services without your message showing up as sent from your carrier number. Today's update also adds a warning message whenever you type the 911 short code -- a handy safeguard, if you ask us. Nab the Android app update via the source link below.
Outbound calls from desktop Gmail are back, with free calling to the US and Canada
Today Google has brought back the ability to make phone calls from desktop Gmail, Google+ and via its Chrome extension, and also announced that calls to the US and Canada are free (from countries where Hangouts calling is available. The feature disappeared when Google introduced its new Hangouts setup, but a post on the Gmail blog claims that now it's better than ever. According to the company, "Hangouts is designed to be the future of Google Voice," with making and receiving calls just the beginning. For now, users can enjoy new features like adding multiple phone numbers and video participants to the same call, and using sound effects from the Google Effects app. Current Hangouts users should see a new phone icon in Gmail, or a "call a phone" menu item in Google+ and the Chrome extension.
CyanogenMod tweak lets Google Voice SMS work through other apps
Many Android-based Google Voice users don't like having to use the official Google Voice app for text messaging, especially when its performance can be flaky. They now have some choice courtesy of experimental code from ClockworkMod's Koushik Dutta. His test release lets those running CyanogenMod nightlies send and receive Google Voice SMS through any suitable Android app as long as Google's software is present. The project should be helpful, although there's no question that there's some risk involved -- it's a beta that requires an unstable custom ROM, after all. If that's no deterrent, though, you can get Dutta's code and instructions from the source links.
Hangouts upgrade disables outbound Google Voice calls in desktop Gmail, company promises it will return 'soon'
Anyone who's tried out the new Hangouts feature in Gmail in place of the traditional Google Talk option got a bit of surprise when they went to make an outbound call from their computer. That feature gets disabled when the new Hangouts replacement is switched on, leaving folks looking to make calls with no other option than to revert to the old Google Talk in Gmail or seek out another alternative. That's apparently just a temporary change, though, as Google's Nikhyl Singhal has now confirmed that both outbound and inbound calls will "soon be available." Unfortunately, he's not getting any more specific than that for the time being. He did, however, reiterate that "Hangouts is designed to be the future of Google Voice," and that "making / receiving phone calls is just the beginning," further adding that "future versions of Hangouts will integrate Google Voice more seamlessly."
Gmail phone calls remain free of charge in 2013 for US and Canada
It may be an expected holiday gift, but it's still a nice one: Google's VoIP service in Gmail will remain free of charge for calls within the United States and Canada in 2013. A note on the Gmail Blog announced as much today; the news ushers in a thrilling third year of free Google Voice service for US and Canadian customers, right through the standard Gmail interface. Of course, we prefer the retro-inspired phone booth that Google showed off back in 2010 when the service was first announced, but free is free. Now, what to get for the megacorporation that has everything. We're thinking ... Furby? Probably a Furby.
Google Voice app updated for iOS 6, iPhone 5
Two months after the release of iOS 6 and the iPhone 5, Google has issued an update for Google Voice to bring full support for both to the popular VoIP app. While it was usable on iOS 6 prior to today, and ran bordered on the latest iPhone, Google Voice now makes use of the iPhone 5's full 4-inch display. Version 1.4.3 of the app also contains unspecified bug fixes and performance boosts, so while iPhone 5 owners will obviously see the biggest benefits, iPad and iPod touch users will still have reason to update. Users of legacy devices will want to note, however, that the new version requires iOS 4.3 or higher in order to run.
Google Voice update cures Android 4.2 compatibility woes
Google Voice callers who lean heavily on the Android app got an unwelcome side dish of predictable app crashes if they upgraded to Android 4.2 very quickly. Thankfully, the developers in Mountain View have been quick to get us back to the main course: a newly available update patches the relevant bug and lets us get back to messaging as usual. Anyone who held off on a firmware upgrade (or a Nexus purchase) for fear that they'd miss an important call has just been given the all-clear signal.
D'oh: Google Voice force-closing text messages for Android 4.2 users
The growing pains associated with being an early adopter can sometimes be brutal, as Android's latest software bump doesn't appear to jibe too well with one of Google's most popular in-house apps. Prior to the Nexus 4's official release, word of a Google Voice texting bug began to circulate, but was written off as pre-release jitters. However, it appears that the issue is expanding beyond the search giant's newborn smartphone, as owners of the HSPA+ Galaxy Nexus loaded with Android 4.2 (Jelly Bean) are also experiencing crashes when attempting to compose a text message within Google Voice. While the app still works for phone calls, text messages are completely off limits. Hopefully, this issue can be fixed with an app update as opposed to a new Android software version altogether. In the meantime, if you're a heavy Google Voice user with Android 4.2 in your crosshairs, we suggest that you hold fire and wait until Google officially sorts things out.
Google Voice brings greater control over anonymous and unknown callers
Think about it for a moment: do you recall a single instance when you were actually glad that you answered a telephone call from a blocked number? Unless that bill collector turned out to be your future spouse, the answer is likely no. Now, Google Voice users will find an extra perk in the online settings that should take the edge off of receiving calls from unknown sources. You'll now find the ability to screen anonymous callers, whereby the system will prompt the individual to state their name, and only then will your phone ring. From there, you'll have the option of answering the call, sending it to voicemail, or even listening in as the caller leaves a voice message -- kinda like back in the days of answering machines. Similarly, you'll also find the ability to apply this same screening process to callers who aren't in your address book. As proof that Google isn't a total grouch, it's also thrown in a new option that allows you to customize a warm greeting for those contacts who are, in fact, in your address book. After all, it never hurts to show some love.
Slick Google Voice integration may not be Sprint exclusive for long
Despite it's rocky start, we wouldn't blame you for being a little jealous of Sprint's tight integration with Google Voice. Well, the relationship between the two might not be exclusive for much longer. Vincent Paquet, Product Manager for Google Voice, told CNET in an interview that the web giant is actively talking to other carriers about forming a similar bond. Paquet didn't name any names unfortunately, but we're hoping one of the other major national providers here in the US is on the short list of potential corporate polygamist partners. If we're lucky, getting your Verizon phone to play nice with Google Voice's voicemail inbox will soon be a lot simpler. Or, at least it'll be easier to send those stubborn exes straight to voicemail.
