The WannaCry ransomware worm has spread panic and destruction as it infects hundreds of thousands of systems around the world; a rate not seen since the Blaster and Sasser worms of 2003. WannaCry — also known as WannaCrypt, WannaCryptor, WanaCrypt0r, WCry, or WCrypt — leverages vulnerabilities that Microsoft patched in the March MS17-010 Security Bulletin, after taking the unprecedented step of canceling the February Patch Tuesday.
While collecting samples of WannaCry, I found a sample that predates the worm version. The sample was compiled on February 9th, and uploaded to VirusTotal on February 10th. While compile timestamps can be faked, the closeness to the upload date suggests that the compilation timestamp is legitimate.
The headline feature of the new Google Pixel phones is deep integration between the operating system and the Google Assistant AI. By default, the Google Assistant can be activated even when the phone is locked and the display is off, if the device hears the trusted voice say the hot word, “Ok Google”. This also has the effect of unlocking the device, meaning that anyone with a recording of the trusted voice saying “Ok Google” — or even someone with a similar voice — can easily unlock the device.
When I first switched my Nexus 6P to from T-Mobile to Verizon, I noticed that support for native visual voicemail in the Android dialer was missing. Worse, I was getting cryptic text messages instead of the usual basic voicemail notification.
A blog post from Matt Cutts describes this situation in detail. It turns out the text messages are somehow used in the background by Verizon’s proprietary visual voicemail application. That application is not available to Nexus devices on the Google Play store like the My Verizon app is. So the only solution to get regular voicemail notifications working on Nexus devices was to have a Verizon rep switch your line to basic voicemail. This option is different that basic visual voicemail, which is on your line by default.
In an age of texting and messaging apps, loosing visual voicemail might not seem like a big deal to most consumers, but I’ve found that the voicemail to text feature is extremely useful when I need to discreetly check voicemails from businesses and doctor’s offices while on the go or at work. It’s also indispensable for those who are hearing impaired. I wondered how Verizon and Google were going to do Visual Voicemail on the Pixel phones, since Verizon’s Visual Voicemail app is not on the list of installed Verizon apps. Now we know.
After upgrading my Nexus 6P on Verizon to the Android 7.1.1 beta, I discovered that Visual Voicemail in the native Android dialer works! You just need to make sure that that basic (free) or premium visual voicemail is active on your line. Voicemail-to-text works too, if you add Premium Visual Voicemail to your line. Unfortunately, there is no sign of Wi-Fi calling support (yet?). HD voice has always worked on the Nexus 6P.
Also, the Support tab in Settings is there, as seen on the Pixel phones.
This was one of the features that I thought was Pixel exclusive. It’s nice to see it included. Hopefully more features from the Pixel phones like the Google Assistant will make their way to Nexus devices over the next few months. That would go a long way towards soothing the outrage of many Nexus owners who feel left behind. It would certainly be in Google’s long-term interest to put the assistant in the hands of as many Android users as possible once it has full integration with third party services.
Update: Unfortunately, the day after this post was published, Google updated Google Support Services that remove the phones and chat support buttons for Nexus devices 🙁
You can get Android 7.1.1 on a Nexus device right now by signing up for the Android Beta. It’s actually very stable, and I think it’s snappier than 7.0.
My Google Pixel XL is due to arrive today. I’ll have a full review here next week.
When Google Chrome updated to 53.0.2785.101 on my Windows systems, I encountered an onslaught of alerts from EMET, which was killing chrome.exe processes for EAF+ violations as fast as Chrome kept trying to spawn them (each tab in Chrome is a separate process). Luckily, this problem is easily fixable.