Showing posts with label why. Show all posts
Showing posts with label why. Show all posts

Friday, October 21, 2016

Thinking Out Loud Why Can’t Google OnHub Become Google’s Amazon Echo or “Chirp”

Thinking Out Loud Why Can’t Google OnHub Become Google’s Amazon Echo or “Chirp”


There has been a lot of talk recently about Google making an Amazon Echo-like device that may or may not be shown off at Google I/O. But what if the devices already exist and can be purchased today? Confused? I’m talking about Google OnHub routers, of course, devices that have been shrouded in mystery since launching within the past year. It seems that a software update is all that would be needed for these devices to instantly become the Amazon Echo competitor the media can’t stop talking about. Let me explain. 

As a recap, Google released two devices recently under a new OnHub brand. We still don’t really know what OnHub is other than a line of products that Google is calling a “better, faster router,” for the time being. Of course, the devices have branding on them that reads “built for Google On,” because they are likely supposed to be a part of a bigger “Google On” ecosystem than just routers that hasn’t arrived yet.

These first two OnHub products are indeed WiFi routers, though, but they have the potential to be so much more, which Google keeps admitting to but won’t quite deliver on. In fact, the listings for each product (one made by ASUS and another by TP-LINK) say that they “keep getting better,” because they include “next-generation technologies, and, over time, will support a growing number of smart devices.” Except, we’re almost a year into this OnHub thing and there aren’t any other smart devices that play with them. Well, I wouldn’t be shocked if Nest’s products can, Google just isn’t telling us that they do.

These are routers with dual-core processors that are Weave (Google’s IoT communications layer), 802.15.4, and Bluetooth Smart ready. They have speakers, quite large ones actually. They also have ambient lights, proximity sensors, and designs that are just begging you to put them in the open, on a shelf, so that you not only improve wireless performance, but they look pretty in the process (like an Amazon Echo). The only thing I’m not sure about is whether or not they have microphones, since iFixit didn’t note one in their teardown of the TP-LINK router and neither specs list for the OnHub devices call for one.

google onhub-2

But you are seeing the vision here, right? Google already has two devices that are setup to be an Amazon Echo. They have all of the technologies inside them for Google’s future smart home products (and current Nest products) to talk to one another, speakers for talking back to you, and pretty designs so that you’ll leave them in the open. We’re just waiting for Google to turn all of that fun on and make it a reality.

With talk of Google potentially showing off a project under codename “Chirp” at Google I/O next week, but no product supposed to be there with it, you have to wonder if that can be taken as a play on words. Because if “Chirp,” which is thought to be the smarts (or the Alexa) to Google’s home hub, all it needs is to be loaded on OnHub hardware.

Related Stories

  • Report: Google’s Amazon Echo-Like Device is Codenamed Chirp, Possible Google I/O Tease to Take Place
  • Google Announces the ASUS OnHub WiFi Router, Priced at $220
  • Google’s OnHub WiFi Router App Hits Google Play
  • This Could be What the LG Nexus 5 (2015) Will Look Like

Thinking Out Loud: Why Can’t Google OnHub Become Google’s Amazon Echo or “Chirp” is a post from: Droid Life



from Droid Life http://ift.tt/225TzKA

Get or watch

Friday, October 14, 2016

FCC and FTC Want to Figure Out Why Security Updates Take so Long to Get to You

FCC and FTC Want to Figure Out Why Security Updates Take so Long to Get to You


Because security is always of the utmost importance, but maybe even more so today on mobile because we all have a smartphone and use it for everything we do, the FCC wants to figure out why it’s taking carriers and manufacturers such a long time to get you updates, namely security patches. Yesterday, through a press release, the FCC announced that it is partnering with the FTC to open an inquiry into mobile device security updates. The basic idea here is that they want carriers and manufacturers to tell them their process for updating, to see what can be improved. 

The announcement from the FCC name-drops Stagefright as an example, a vulnerability that really had the potential to be a disaster for many people, but has since been patched a number of times by Google. Stagefright was such a big deal during much of last year that companies like Google, Samsung, and LG all promised monthly security patches to try and protect users going forward. Unfortunately, not everyone got on board with the monthly schedule and there could be millions of vulnerable people still to date with older devices that are no longer supported by OEMs or carriers.

The FCC sent letters carriers with questions about the processes for “reviewing and releasing security updates for mobile devices.” They want to know things like, if the carrier faces issues or hurdles in releasing updates, if there are hurdles getting users to install new updates, if carriers know if updates have been installed, and if security vulnerabilities in mobile devices pose threats to their networks. They also want to know all of the parties involved in getting an update ready and pushed out, how this process works differently from one operating system to the next, and when do carriers cut off security patch support for devices.

I can’t help but applaud the FCC for probing carriers over security updates, but will say that many of them have become quite good at getting out the monthly patches that start with Google and then carry on through companies like Samsung, LG and HTC. Thankfully, the FTC says that it is going after eight phone manufacturers (Apple, Blackberry, Google, HTC, LG, Microsoft, Motorola Mobility, and Samsung) to find out similar information. That’s a good thing, because there are certainly a couple that need to get with the program.

All parties have 45 days to respond to the FCC and FTC, so it could be a while before we know anything, including findings, thoughts, and if there are going to be recommendations for improving the entire process.

Via:  FCC (PDF) | FTC (PDF)

Related Stories

  • How Many Android Applications Does Google Check Every Day for Malware?
  • Here is the Android 5.1 Update Changelog for the Moto X (1st Gen)
  • Android 6.0 Marshmallow Rolls Out Next Week to Nexus 5, 6, 7 (2013), 9, and Player
  • Going Forward, Nexus Devices Will See Monthly Security Updates – First Up are the Nexus 4, 5, 6, 7, 9, and 10

FCC and FTC Want to Figure Out Why Security Updates Take so Long to Get to You is a post from: Droid Life



from Droid Life http://ift.tt/1UQ6kaV

Get or watch