Skip to content

Posts tagged ‘Google’

12
May

Google and Lionsgate celebrate Mad Men’s last episode with an interactive web experience and free episode


MadMen_Final_Season

If you’ve been watching the TV program, Mad Men, then you probably already know that its last episode will air on Sunday, May 17th. To celebrate this, Google has teamed up with the show’s production company, Lionsgate, to showcase ‘The Mad Men Experience‘, an interactive website documenting the program’s characters, themes and storyline. You can relive some of your favourite moments from the program while taking in some of the behind-the-scenes action and interviews with the actors.

If you haven’t actually watched Mad Men before, Google is making it easy for you to get started by offering the very first episode of the first season free of charge on Google Play in the US, Uk, Australia and Canada. As you would expect, you can also purchase all the other episodes via the Play Store as well. All you have to do to get your hands on the first ever episode is either scan the QR code or just click the Play Store link below. To visit  ‘The Mad Men Experience’, just click the source link below.

qr code

Google Play Store Get it Here

 

Source: TheMadMenExperience

Come comment on this article: Google and Lionsgate celebrate Mad Men’s last episode with an interactive web experience and free episode

12
May

Google’s self-driving vehicles have only been involved in 11 accidents over 6 years


Google self driving carGoogle’s self-driving cars are a big focus point for the company, but drivers and manufacturers alike are keeping their eyes on the safety of those autonomous vehicles. Fortunately for everyone (except maybe insurance companies) Google’s self-driving car program hasn’t caused any accidents over the 6 years and 1.7 million miles since it took to the road.

That’s not to say that there haven’t been any accidents where a Google car was involved, but none of the 11 recorded accidents were Google’s fault. To top that off, all 11 accidents that the self-driving cars were involved in were minor, so no one was injured. That’s pretty impressive, and seems far safer than what most human drivers can typically pull off.

Google’s research has also given a little insight into when crashes are most likely to happen. Out of the 11 times one of their cars was hit, 8 times were on city streets, while only 3 accidents happened on the freeway. Dealing with things like stop signs, intersections, and typical distractions seem to be the biggest culprit of minor vehicle accidents, and Google notes that. Too many people are distracted on their phones or by other things in their vehicles, which leads to drivers not paying attention at four-way stops or trying to rush to beat a red light. Google has developed some interesting ways to tackle those problems, like forcing their car to take a second pause when a light turns green to avoid getting hit by someone speeding through a red light.

Google also captured some pretty ridiculous things some drivers do, like driving on the wrong side of the road (seriously), sharply cutting across lanes to make a turn, and veering into other lanes in the middle of a turn. Google’s cars typically handle those situations very cautiously and probably much better than most human drivers, which explains the extremely low accident rate.

At the end of the day, this information really sums up how dangerous the human element is to driving. It’s much easier for a computer to make calculated, safe decisions, especially in a high-speed environment, especially compared to how people drive. It’ll be very interesting to see how Google plans to take this program further in the next few years.

source: Medium

Come comment on this article: Google’s self-driving vehicles have only been involved in 11 accidents over 6 years

12
May

Want to Help Google Improve Chrome? There’s an Extension for That


Chrome User Experience SurveysEver ready to listen to user feedback and then ponder whether or not to include said feedback in subsequent product releases, Google announced today a new Chrome User Experience Surveys extension that collects user experience data on Chrome. So it’s not just a clever name.

The tiny extension will pop up sometimes at random, or more often, when something unusual happens to Chrome, like bugs or malware warnings. Google says a user will get a maximum of two notifications per day, capped at four per week, with the average user seeing a survey once a month. Surveys are roughly 2-3 minutes in length.

Keenly aware of user trepidation when it comes to data harvesting, the third question answered in Google’s announcement of the extension (after “What?” and “Where?”) pertains to the information Google will collect from the extension. The answer: nothing personal. The only data collected will be that directly related to the extension.

Chrome User Experience Survey Example

Unlike Google’s awesome, if totally data-collection-obvious, Google Opinion Rewards app, which pays users a few dozen cents here and there for answering surveys, Chrome User Experience Surveys offer no remunerative benefits other than the satisfaction that comes from making everyone’s browsing experience just that much better.

Now aside from the fact that apparently Google requires an extension to fully ascertain the incredible resource drain that is Chrome on a Mac, this could be a useful and simple way for everyday users to help Google improve the world’s overwhelmingly dominant browser. (As an aside, remember when Chrome felt like this light little rebel browser up against the IE monolith?)

The feedback period only lasts 120 days, and Google dissuades you from uninstalling the extension before then. After 120 days, the extension will uninstall itself. Skynet once promised the same thing.

Source: Google

Come comment on this article: Want to Help Google Improve Chrome? There’s an Extension for That

12
May

Having trouble keeping your mobile data connection on your Nexus 6? You’re not alone


nexus 6 review aa (6 of 14)

If you’re the owner of a Nexus 6 and happen to be a subscriber to either T-Mobile’s or Sprint’s network, you might want to take note of a problem that’s been happening to quite a few owners of the handset. Multiple users around the web have been experiencing complete mobile data connection failure over the past week or so, with no viable explanation for the problems.

Nexus 6 data

Most users explain that the problem happens sporadically throughout the day, and that their phones will randomly show an exclamation point over the signal icon, no matter if they have full bars or not. When that exclamation point shows up, the phone’s data connection is completely gone, and the Nexus 6 then requires a soft reset to work again. Unfortunately most folks are saying that a soft reset only fixes the problem for a few minutes.

The majority of these users report that the problem persists no matter if they’re rooted or non-rooted, or if their phones are running Android 5.0 or 5.1. Most complaints over on Reddit and XDA are from T-Mobile and Sprint customers, though there are also a few Verizon users reporting issues.

Related Videos

.rvs_wrapper
width: 335px;

.rvs_wrapper.align_left
float: left;

.rvs_wrapper.align_right
float: right;

.rvs_wrapper.align_center,
.rvs_wrapper.align_none
width: 100%;

.rvs_wrapper.align_center
text-align: center;

.rvs_wrapper.align_center.cbc-latest-videos ul li
float: none;
display: inline-block;
vertical-align: top;

.rvs_wrapper.cbc-latest-videos:not(.align_none) ul li:nth-child(2n+1)
clear: both;

.rvs_title
font-weight: 600 !important;
margin: 0 !important;

.rvs_wrapper.align_right .rvs_title
padding-left: 20px;

.rvs_title a
font-family: ‘Roboto Condensed’;
color: #3a3a3a;

.rvs_wrapper.cbc-latest-videos ul
padding-top: 10px;

.rvs_wrapper.align_left.cbc-latest-videos ul li,
.rvs_wrapper.align_none.cbc-latest-videos ul li
padding: 0 15px 0 0;

.rvs_wrapper.align_right.cbc-latest-videos ul li
padding: 0 0 0 15px;
float: right;

.rvs_wrapper.align_center.cbc-latest-videos ul li
padding: 0 7px;

.rvs_wrapper.cbc-latest-videos ul li > a
font-weight: 400;

.rvs_wrapper.cbc-latest-videos ul li > a .yt-thumbnail
margin-bottom: 0;

@media only screen and (max-width : 480px)
.rvs_wrapper
width: 100%;
text-align: center;

#page .rvs_wrapper.cbc-latest-videos ul li
padding: 0 7px;
display: inline-block;
float: none;
vertical-align: top;

If you’ve been experiencing this problem, you can try performing a soft reset, pulling the SIM card, or even calling T-Mobile or Sprint to see what the representatives have to say. As of now, there seems to be no permanent fix for the issue. Has this happened to you on your Nexus 6? If so, be sure to let us know in the comment section!

605
12
May

Google to shut down editing in Map Maker following the peeing Android fiasco


android apple

Just a few weeks ago, a “clever” Google Maps user submitted an image of the Android mascot urinating on an Apple logo in Google Maps, forcing Google to apologize for the mishap. Most folks out there thought this stunt was childish and inappropriate, and apparently Google Maps has seen an escalated number of spam submissions, thanks to the auto-approval process in Map Maker. Because this rate has been growing so quickly, Google has suspended auto-approval and user moderation across the globe in Map Maker, at least until the company figures out how to more intelligently prevent these types of incidents.

Pavithra Kanakarajan, Product Manager at Google Map Maker, explains:

As some of you know already, we have been experiencing escalated attacks to spam Google Maps over the past few months. The most recent incident was particularly troubling and unfortunate – a strong user in our community chose to go and create a large scale prank on the Map. As a consequence, we suspended auto-approval and user moderation across the globe, till we figured out ways to add more intelligent mechanisms to prevent such incidents.

All of our edits are currently going through a manual review process.

Editing in Map Maker will be disabled starting Tuesday, May 12th, 2015 (tomorrow).

Of course, Google shutting down the auto-approval process is meant to make the program more professional and accurate. We’re not sure when a fix will be published, but we’ll be sure to let you know when the improved tool will return back online.

1.5K
11
May

Android 5.1.1 OTA update and factory image now available to download and flash for the Nexus 9 Wi-Fi


android_lollipop_tweet

Google has finally pushed the Android 5.1.1 update to Nexus 9 Wi-Fi devices. The factory image was already posted and now we have the link to the official over-the-air update as well.

Flashing the OTA is probably your easiest method since you don’t have to lose your data. However, you need to make sure you are on Android 5.0.2 (version LRX22L) before you can do it. Android 5.0.2 was already pushed about a week or so ago, so if you won’t have it, you will need to flash that OTA update first. You can also opt for flashing the factory image, but you will lose your data if your Nexus 9 doesn’t have an unlocked bootloader.

Whichever route you decide to go with, make sure to hit up our extensive guides. Click here for flashing the factory image or here for flashing the OTA update. If you already know what you’re doing, just hit up the links below.

OTA update links

Nexus 9 (volantis) From LRXxx2 to LRX22L (5.0.2)

Nexus 9 (volantis) From LRX22L to LMY47X (5.1.1)

Factory Image link

Nexus 9 (volantis) 5.1.1

 

Come comment on this article: Android 5.1.1 OTA update and factory image now available to download and flash for the Nexus 9 Wi-Fi

11
May

Self-driving cars involved minor accidents, but don’t blame the tech


Google Self-Driving Car

Since California began issuing permits for self-driving car tests on public roads last fall, four out of nearly 50 vehicles had minor accidents. According to an Associated Press report, three of the four were Google’s Lexus SUVs outfitted with Delphi’s autonomous technology. The fourth was a test vehicle owned by Delphi. In half of the fender benders, the cars were in control when the accident occurred, and all of them happened at speeds of under 10 MPH. Most importantly, all four cases resulted in minor damage and no injuries. Due to the state’s privacy laws, the report doesn’t indicate any further details — like if they happened while backing out of a parking space, for example.

In a blog post today, Google’s self-driving project head Chris Urmson explained that in its six years, the project has seen 11 accidents — all of them with light damage and no injuries. What’s more, Urmson notes none of the accidents were caused by the self-driving technology that has piloted nearly a million miles. “If you spend enough time on the road, accidents will happen whether you’re in a car or a self-driving car,” Urmson said. As you may recall, Florida, Michigan and Nevada also license companies to test self-driving cars on publish highways. Thus far, no accidents have been reported in those states.

[Image credit: Mark Wilson/Getty Images]

Filed under: Transportation, Google

Comments

Via: Autoblog

Source: CNBC

11
May

Some Nexus 6 users complaining of mobile data issues


google_nexus_6_front

The Nexus 6 has been one of the least controversial devices to launch in quite a while. Although its size might not be for everybody, one would say that the device has been less prone to issues or bugs compared to older Nexus devices.

That however could be changing with some users complaining about the handset’s mobile data connectivity. It is being said that some users are seeing a ‘!’ mark next to the signal bar, with no mobile network available. This usually happens when there’s not enough network coverage in your area, but this seems to be happening even when there’s plenty of coverage, thus causing concern among users.

The XDA forums are currently piling up with complaints about this issue, but we haven’t heard anything from Google as of yet. Some users apparently tried to soft-reset their device which seemed to have fixed the issue for a while, but unfortunately, it didn’t last long. When the users contacted T-Mobile and Sprint customer support, they were told to reset APN settings to default and/or to reset the APN protocols to iPv4/iPv6.

Are you facing any of the aforementioned issues? Sound off below.

Source: XDA
Via: Android Authority

Come comment on this article: Some Nexus 6 users complaining of mobile data issues

11
May

Google is temporarily shutting down Map Maker


Google_Maps_Bugdroid_Pissing_Apple_Logo

A couple of weeks ago, we wrote about a discovery on Google Maps that many believed was an Easter Egg hidden and planted by the search engine giant. Just in case you missed it, Facebook user Ahmad Babar posted a picture from a location just north of Rawalpindi, Pakistan, in which a Droid could be seen urinating on the Apple logo.

As soon as Google became aware of the uncouth artwork, it removed it from the Map. In an exclusive statement sent to The Washington Post, Google blamed the appearance of the graphic on an unidentified individual who was manipulating Map Maker to create audacious designs.

It would appear that Google is still having a bit of trouble filtering all of the bad edits, though, as earlier today it announced that it would be temporarily shutting down the Map Maker service until a more reliable moderation system could be created.

The full statement can be seen below:

As some of you know already, we have been experiencing escalated attacks to spam Google Maps over the past few months. The most recent incident was particularly troubling and unfortunate – a strong user in our community chose to go and create a large scale prank on the Map. As a consequence, we suspended auto-approval and user moderation across the globe, till we figured out ways to add more intelligent mechanisms to prevent such incidents.

All of our edits are currently going through a manual review process.

We have been analyzing the problem and have made several changes. However, it is becoming clear that fixing some of this is actually going to take longer than a few days. As you can imagine, turning automated and user moderation off has the direct implication of very large backlogs of edits requiring manual review. This in turn means your edits will take a long time to get published.

Given the current state of the system, we have come to the conclusion that it is not fair to any of our users to let them continue to spend time editing. Every edit you make is essentially going to a backlog that is growing very fast. We believe that it is more fair to only say that if we do not have the capacity to review edits at roughly the rate they come in, we have to take a pause.

We have hence decided to temporarily disable editing across all countries starting Tuesday, May 12, 2015, till we have our moderation system back in action. This will be a temporary situation and one that we hope to come out of as soon as possible.

While this is a very difficult, short term decision, we think this will help us get to a better state faster. More importantly, we believe it is simply the right thing to do to all of you, our valued users who continue to edit with the hope that your changes might go live as fast as you’ve been used to.

Come comment on this article: Google is temporarily shutting down Map Maker

11
May

Google suspends Map Maker service after digital vandalism


Google is suspending Map Maker, the service that allows anyone to contribute to Google Maps, following a prank submission that showed the Android mascot urinating on an Apple logo. When the mapping mischief was first discovered, most of us had a good chuckle and wondered who was responsible. Inevitably, Google took it down and later confirmed that it was a user-created edit, which raised questions about Map Maker’s review policies.

The service uses a mixture of “Google Reviewers” and trusted users to moderate Map Maker contributions, but clearly the setup has some flaws. As such, Google has already suspended auto-approval and user moderation, instead relying on manual checks from its in-house team. The company says it’s quickly accrued a huge backlog of user-contributed edits, so while it develops a new moderation system, it’s suspending public submissions entirely. It’ll come into effect from May 12th and while Google says it’s “a temporary situation,” it’s also admitted that it’ll take more than a few days to fix.

Filed under: Internet, Google

Comments

Source: Google Product Forums