Showing posts with label google. Show all posts
Showing posts with label google. Show all posts

Tuesday 5 April 2016

Google may employ LG for another Nexus phone


Another Nexus built by LG? Yes please. Photo: LG
Photo: LG Nexus

Google may employ LG for another Nexus phone

LG’s Nexus smartphones — the Nexus 4 and the Nexus 5 — were arguably two of the best Google devices to date. In fact, they were so good that Google has asked LG to build another one, according to a report from South Korea.

eToday reports Google engineers have been spotted at LG’s headquarter, where they took a tour of the facilities responsible for building the company’s displays, cameras, and wireless charging components — as well as LG’s research and development facility.
The reason for the visit? A smartphone with the codename “N000,” which will launch as the Nexus 7, according to sources familiar with the matter.

Yes, that’s the name of Google’s 7-inch Nexus tablet, which makes the whole thing a little confusing. But while Nexus tablets are named based on their size, Nexus smartphones have long been named purely by the order in which they are released.

But of course, this is purely speculation for now. A new Nexus smartphone is more than six months away, and it’s never a good idea to rely on rumors this premature.

I must say, though, I certainly wouldn’t mind another Nexus made by LG. I adored the Nexus 4 and the Nexus 5, and while they weren’t perfect smartphones, they were certainly excellent products for the price.

Google may employ LG for another Nexus phone


By SourceeToday ViaPhandroid

Google is giving away $80 worth of freebies to Chromecast owners

Chromecast Featured ready to cast

Google is giving away $80 worth of freebies to Chromecast owners



Google continues to make the case for everyone on the planet to own a Chromecast. Their latest promotion puts $80 worth of freebies up for grabs just for owning a Chromecast. That’s over twice the amount it costs to buy a Chromecast, which is exactly what you need to do to get these deals.

Buy a Chromecast any time between today (March 20th) and April 19th to qualify for the rewards. The rewards include a three-month subscription to Google Play Music All Access, one month of Qello Concerts, three months of DramaFever, three-month of Sesame Street GO, and a free movie rental from Google Play Movies. It continues to pay to own a Chromecast.

chromecast-deals
[via Engadget]

Google is giving away $80 worth of freebies to Chromecast owners

Tesla App designers prefer Android Wear over Apple Watch

Apple_Watch_Android_Wear_Tesla_ELEKSlabs_9

Tesla App designers prefer Android Wear over Apple Watch


Apple may be trying to attack a niche portion of the wearable market by creating a more “premium” option, but premium hardware doesn’t always equate to blissful software. The developers of the Tesla app for the Apple Watch found that out in their latest project.

According to them, Google approached Tesla to create an app for Android Wear after seeing they’d done one for the Apple Watch. They accepted Google’s challenge, and more than just create a beautiful app for which to control your Tesla smart car, they laid out a wealth of impressions about the development experience and differences between the two platforms.

Here’s a spoiler for you: they like Android Wear. A lot. Their love for it comes from the fact that it’s a much more open platform to work with compared to Apple Watch. Where Apple limits developers on API access and low-level device integration, Tesla found it refreshing that Android Wear gave them nearly everything they needed.
Apple_Watch_Android_Wear_Tesla_ELEKSlabs_1

Perhaps their most favorite thing was being able to experiment with unique user interface tricks — apparently things are quite restricted in that regard on iOS. They also wondered how the Apple Watch could only manage 18 hours of battery life on such a limited platform compared to 2 days on many of the smart watches that run Android Wear.

Things weren’t all peachy for the Tesla team on Android Wear. Here are a few complaints they had:
  • Voice activation is too slow of a process. Their suggestion to Google is to allow developers control over the command after the initial “OK Google” to cut down on the 2-3 second pauses needed between each part of the command.
  • While better than the Apple Watch, battery life could still be improved. They love Pebble in that regard.
  • Thin documentation — not a knock on the platform itself, but certainly something that can mar the development experience.
But even with all that, they believe Google has done a fine job with Android Wear and can’t wait to see where it goes from here on out. Be sure to read their full thoughts on Android Wear development and what went into the new Tesla app over at Eleks Lab.

Tesla App designers prefer Android Wear over Apple Watch

Google is making surgical robots with Johnson Johnson

Google is making surgical robots with Johnson & Johnson

Google is making surgical robots with Johnson & Johnson


It looks like your medical surgeon might one day be, or at least be assisted by, a Google robot.
Google has partnered with a lot of companies in recent years on various different projects, but it's latest partnership is a bit of surprise. Medical and pharmaceutical company Johnson & Johnson has just announced it is advancing surgical robotics in collaboration with Google.

Johnson & Johnson's Ethicon medical device arm is sharing intellectual property and expertise with Google's Life Sciences team in order to develop a robotic-assisted surgical platform that will benefit surgeons, patients, and health care systems. The platform will not only integrate advanced technologies with the goal of improving health care, but it will also allow surgeons to have more control and accuracy during procedures.

"Robotic-assisted surgery is a type of minimally invasive surgery that uses technology to give surgeons greater control, access and accuracy during the surgical procedure while benefitting patients by minimising trauma and scarring, enabling accelerated post-surgical healing," explained Johnson & Johnson, while highlighting that it wants to develop new robotic tools and capabilities for surgeons and operating room professionals.

The idea is that these new robotic tools will feature cutting-edge medical device technology, robotic systems, imaging and data analytics, and when these aspects are combined, they'll be able to advance surgical care around the world.
This isn't the first time Google has experimented with medical-themed projects. It has a Google Fit health data service, for instance, and it backs the Calico life science company.

Google is making surgical robots with Johnson & Johnson


Tuesday 29 March 2016

Download Gapps of Android 6.0 Marshmallow Google apps CM13, 6.0, 6.0.1

Obtain operating gapps for android Marshmallow 6.0 Cm13 and different roms .If you're working on android Marshmallow 6.0/ 6.0.1 on any customized roms like Cm13 or AOSP in response to android Marshmallow with out gapps the android device is incomplete prior to in the event you now not set up those Google apps you'll now not get apps like Gmail, Google play retailer, Google play track, Google + and lots of different apps to.We by some means be able to get the % Gapps of android marshmallow 6.0.zip that's flashable via customized restoration.

See additionally: methods to use the android information restoration application to get better deleted information from android units.
 
Nowadays we can display you tips on how to set up GAPPS(Google apps) in android  Marshmallow 6.0.Those google apps package deal is appropriate with the entire roms for android.Those gaaps are compressed in a zipper report.

#Obtain Google apps 6.0 Bundle



Those gapps for android marshmallow 6.0 roms are equipped by way of Opengapps group.

1.Inventory Marshmallow Gapps (490 MB):

That is the really helpful bundle for contemporary units, contains all Google Apps that come usual at the recent Nexus tool.

Obtain Inventory Marshmallow Gapps



2.Complete Marshmallow Gapps (441 MB):

That is similar to inventory bundle, however does now not replaces the AOSP apps for Browser, Digital camera, E-mail, Gallery, Launcher, Keyboard, SMS app, Percent TTS and WebView

Obtain Complete Marshmallow Gapps

3.Mini Marshmallow Gapps (228 MB):

That is the smaller set of Google apps: the preferred apps, plus further capability that may be now not to be had from the Play Retailer.

    Obtain Mini Marshmallow Gapps
  
4.Micro Marshmallow Gapps (142 MB):

It is a restricted set of Google apps: Gmail, Calendar, Google now, plus additional capability that may be now not to be had
from the Play Retailer.

    Obtain Micro Marshmallow Gapps

 
5.Nano Marshmallow Gapps (ninety one MB):

That is some other minimum install, however contains the additional capability that may be now not to be had from the Play Retailer.

     Obtain Nano Marshmallow Gapps

6.% Marshmallow Gapps (sixty four MB):

That is as naked as it will probably get to get the Google Play capability.  

   ►Obtain % Marshmallow Gapps
 

#A few Different Gapps Supplied by way of XDA builders

 

1.Obtain Gapps 6.0 Mini for android Marshmallow 6.0

The percentmodel of PA Gapps for Android M 6.0 Marshmallow comes with minimal Google programs. Thosecome with Google device base, Google Play Retailer, Google Calendar Sync handiest, Google Play Services and products. This model of GApps is meant for the customers who don’t like everydifferent Google packagesand needthe fundamental ones simplest.

Measurement:fifty five.5 MB | Obtain |

2.Obtain Gapps 6.0 Mini Benzo Marshmallow Gapps

This model of Google GApps is meant for the customers who wish to use the minimalimaginable Google GApps having the “K Google” and “Google Seekoptions. Different GApps come with Google machine base, off-line speech information, Google Play Retailer, Google Calendar Sync and of-path, Google Play Services and products. Identify of the gapps benzo-gapps-M-20151011-signed-chroma-r3.zip

Dimension:107 mb | Obtain |

#The best way to flash Gapps in android Marshmallow by way of restoration

1.After downloading the appropirate Gapps package dealReproduction it for your in you android (do not extarct it)

2.Now reboot you software into restoration.

3.Now chooseSet up Zip from SD card choice.

4.Now navigate and make a selection Gapps zip documentthe place you stored it in advance.

5.Now Flash the report in you android telephone.

6.After flashing Restart you instrument and it is going to take time in first get started up so be affected person,

7.You might have now effectivelyput in all Google Apps on Android M 6.0 Marshmallow customized ROM or CM 13 ROM.

Sunday 29 March 2015

Android Wear App for iPhone and iPad compatibility may Launch Soon

android-wear-app-ios-iphone
As you may be aware, you need an Android smartphone to use an Android Wear smartwatch, but if you carry an Apple iPhone or iPad, you’ll soon be able to use the same Android Wear smartwatch, without relying on unofficial third-party app support.

Google is reportedly going to release its a new iOS app over to the App Store that will allow iPhone and iPad users to pair Android Wear devices such as Moto 360 and LG G Watch with their Apple products, French outlet 01net claimed.


Android Wear App for iPhone and iPad compatibility may Launch Soon



OFFICIAL ANDROID WEAR APP FOR iOS
Google’s new move to go cross-platform with an iOS app would expand support for the wearable platform beyond Android devices and target the potential market of tens of Millions of Apple users that may not be interested in purchasing an Apple Watch. As well as, with lower prices and strong design, a fair amount of Android Wear smartwatch demand would likely be there.

The search engine giant is possibly planning to launch the Android Wear app for iOS at Google’s annual developer conference in late May 2015, although the company may push the agenda depending upon the sales of the Apple Watch, which will be launched in the coming weeks.

UNOFFICIAL iOS APP SUPPORTS ANDROID WEAR
Recently, iOS app developer Ali Almahdi have also made an app that connects iOS to Android Wear device, same what Google is planning to officially launch.

In a video submitted to The Hacker News, Almahdi demonstrated the hack on how custom developed iOS app allows his Moto 360 Android Wear smartwatch to sync directly with his iPhone device, without having Jailbreak or root access.

GOOGLE TO CLUB WITH APPLE?
Right now, I can’t say if Google really be able to convince Apple into approving an Android Wear app for iOS as well as Apple users into using it, but if this happens, it would be highly profitable for both Google and its Android partners.

However, much details aren't available yet. But, it would definitely require additional efforts, as it wouldn't be an Android-to-Android connection any more, rather it’s an Android-to-iOS connection.

In case, Apple denied approving the Google’s proposal, the search engine giant could partner-up with Microsoft to widespread its Android wearable market. Another Gadget report suggests that Microsoft’s upcoming rumored smartwatch might be compatible with both iOS and Android devices.


Android Wear App for iPhone and iPad compatibility may Launch Soon


Saturday 21 March 2015

Android 5.1 factory image for the Nexus Player

nexus-player-artsy-2

Android 5.1 factory image for the Nexus Player



We talk a lot about Android 5.1 for phones and tablets, but what about Google’s first Android TV product? Looks like the Nexus Player is finally set to get it as the company has posted the factory image over at their website.

We aren’t sure if there are any big changes specific to TV, but we’ll certainly be looking to load this up onto our unit and check. In the meantime you can grab the factory image and flash the file through fastboot if you aren’t interested in waiting for a network OTA process.

You’ll be on version LMY47D and it figures to cost you little more than 442MB of bandwidth. Grab it from Google’s site right here to load it up and give it a go.

Android 5.1 factory image for the Nexus Player

Google in talks with LG to build this year’s Nexus smartphone, not Huawei


Nexus 5 back 1
Details about how the Nexus 6 was conceived is still shrouded in mystery. With rumors last year that Google would effectively be killing off the Nexus line in favor of multiple high-end devices — all running stock Android — sold in carrier stores, Google seemingly made a U-turn. This was after the Android Silver project head made his sudden departure from the company altogether.
Now, as we look ahead to the next Nexus, early rumors began swirling that Chinese smartphone maker Huawei would take up the mantle, something we’ll admit we never saw coming. But before you got your hopes up (or down), a new report has emerged, suggesting that it could be none other than LG.
Apparently, Google engineers were spotted visiting LG headquarters in South Korea, where they took a tour of a few LG facilities responsible for building LG’s displays, OIS cameras, wireless charging parts, as well as LG’s own R&D facilities. Carrying the codename “N000,” (those are zeroes, by the way, not the letter “o”) the device — said to be a smartphone — could launch as the “ Nexus 7.” Um… what?
Going by Google’s current naming convention, the number following a Nexus name has always denoted screen size — not generation. It’d be odd if Google suddenly switched gears confusing consumers in the process. So, that either means Google is looking to LG for a 7-inch tablet followup, or they’re launching a 7-inch smartphone (or not using the 7 name at all). If LG is making another tablet (and not a smartphone), then it’s still entirely possible for Huawei could be working on the actual smartphone. Confused yet? So are we.
As you can already tell, we’re getting a little bit ahead of ourselves here. In any case, LG is a major Android partner and has released quite a few Nexus devices to date, even more if you count their Google Play tablet. If rumors of an LG-made Nexus 2015 smartphone are true, would you guys be disappointed or overjoyed?
[eToday]

Sunday 15 March 2015

Android 5.1 update on your Nexus device, how Google manages updates

Android 5.1 update on your Nexus device, how Google manages updates


Waiting for the Android 5.1 update on your Nexus device? You’re not alone, here’s how Google manages updates
If you keep hitting “check for updates” on your Nexus device, you are just wasting your time, and stressing your fingers. We know, we don’t like to wait for the OTA update either.

Having your device constantly check for updates is about as effective as repeatedly hitting a floor button on an elevator – it’s not. As it happens, clearing Google Service Framework data doesn’t help either, in fact, it will actually hurt your chances of getting an update in a timely manner.

We dug through the interwebs to find some information about how Google manages Android updates, et voila, we found an explanation by Google’s own Dan Morrill, an Android Engineer, on Reddit. He shared these pearls of wisdom a little over a year ago when Android 4.4 KitKat started rolling out, but let’s rehash these things as they touch on both tactics for trying to get Android updates, and explain perfectly why they don’t work.

Taking the latter issue first, if you clear the Google Service Framework data, Google’s servers see this as factory reset, changing the primary ID for your device. Doesn’t sound like a big deal right? The problem is that it invalidates all the app tokens which, in turn, wreaks havoc over notifications. In short, you won’t brick your device, but you are not getting it to the front of the line trying to grab the newest OS update.


As for continuously “checking for updates,” it is not unlike knocking at the door when no one is home. The updates are pushed out in phases. The first phase lasts 24-48 hours, and will reach about 1% of devices initially. The engineers then examine error reports and how the devices are checking in.

If all is going well, then the second phase will push out to about 25% of the install base. Assuming there are no further problems (if any), then the following phase will reach 50%, and so-on over the next couple of weeks.

How does that translate to you the user? Well, if you hit “check for updates” during the first phase, basically you have a 1% chance of getting the update. If your device is not randomly selected to receive the “offer,” then you are on the sidelines until the next phase starts. In Morrill’s own words, “Once your device checks in and gets turned down, that’s it until the next batch. Mashing on the ‘check for updates’ button just causes yourdevice to check in again, and get automatically turned down again. Think about how that makes your device feel! WON’T SOMEONE PLEASE THINK OF THE PHONES?”

As you may expect, the next phase gives your device another shot at hitting pay dirt for the update, but again, once the device checks in, that is it for a given 24-hour period usually.

If it’s any consolation, the “offers” are random, updates are not handled on a first-come, first-served basis. While that means there is no “race” to get the update first, we kind of wish it was sometimes.
 

Android 5.1 update on your Nexus device, how Google manages updates


source: Dan Morill (1, 2) via Reddit


Google just acknowledges leaky memory, is fix coming to Android 5.1.1 or not ?

A memory leak that was originally discovered in Android 5.0.1, is still annoying and befuddling Nexus device users with Android 5.1. According to the Issue Tracker page on the AOSP website, Google has internally fixed the issue and plans to include it in an upcoming release. That most likely would be Android 5.1.1. 

The complaints are beginning to read the same. Apps, especially Google+, restart on their own. Some active apps disappear in the middle of using them, and free RAM drops in hours to about 750MB-800MB from 1.1GB-1.3GB. Most of the people who sent in a complaint appear to be using the Nexus 5, although other Nexus devices have been cited. Some complaints said that opening apps would increase the amount of RAM in use, but closing apps would not reduce that figure.

Issue 159738, "Memory leak still present on Android 5.1," was closed by Google on Friday. Now, it is just a matter of waiting for Android 5.1.1. Google will no doubt stamp this as "Rush" because no one wants to live with the craziness of a handset running with a memory leak.

Thanks for the tip Rodrigo!

source: AOSP