Nexus Player pricing slashed down from $99 to $79
Released in October of 2014, and Google I/O 2015 happening later this week, Google has cut the price of the first Android TV box, the Nexus Player, from $99 to $79. We aren’t entirely sure whether this is just a coincidence or if this is a sign of things to come later this week. As with everything surrounding the weeks leading up and following Google I/O, it will be fun to watch.
You can grab the Nexus Player for $79 with free shipping today. So take advantage of this deal because there’s no telling when it will end, plus everything is good with free shipping. With the reduced pricing, are you planning to pull the trigger on the Nexus Player? Let us know in the comments below.
The post Nexus Player pricing slashed down from $99 to $79 appeared first on AndroidGuys.
What’s on tap for Google at I/O 2015
We’re coming down to the wire now: Google I/O 2015 is just a few days away, and we’ll be liveblogging and reporting from the ground as soon as the festivities begin. Don’t let its reputation as a developer bonanza fool you, though. There’s going to be no shortage of workshops and code review sessions, but I/O is also where Google takes time to update its vision of the future for the people who will ultimately help build it. Of course, it’s not all starry-eyed speeches and technical breakdowns — this is, after all, the sort of show that featured a live streaming Google Hangout with four dudes who jumped out of a zeppelin. We can’t account for whatever crazy, spectacular bits the folks in Mountain View might be working on, but we do have a taste of what to expect when the show starts in earnest this Thursday.
Android M cometh

Ah, yes, and the meat and potatoes of any Google I/O. It shouldn’t come as a surprise that Google has moved to a mostly annual release schedule for big Android updates (something VP of Android Engineering Hiroshi Lockheimer brought up again in an interview with Fast Company), which means we’ll get our first concrete sense of what Android M is like on Thursday morning. So far, the (rumored) changelog looks pretty promising. A recent Buzzfeed report suggests you’ll be able to get more mileage out of your fingerprints, for one — better support for biometric security has apparently been baked right into the OS, allowing users to log into apps with just a touch. This heightened focus on security and authentication also bodes well for some Android Pay announcements, too. First announced at MWC 2015, Google’s Android Pay platform aims to make it easier for app creators and stores to charge you for their wares via your Android phone. Senior vice president Sundar Pichai was awfully light on Pay details in Spain (maybe it was the never-ending lure of jamón), but that shouldn’t be the case in San Francisco.
Throw in some enhanced privacy controls that’ll let users more easily define what apps get to access what information and you’ve got yourself pretty thoughtful update. Beyond that, Android Police claims Android M’s development has seen Google trying to improve RAM management and battery life so your phone runs smoother and lasts longer on a single charge. Lollipop’s Project Volta was a crucial step in this direction, but really, we’ll take all the performance improvements we can get.

Google stepped out of its comfort zone by releasing a developer preview for Lollipop (née Android L) last year, and we strongly suspect they’ll do the same this year too. It’s basically a given that we’d be able to install whatever preview we’re given on the Nexus 6, but rumors of two new Nexus phones launching in 2015 have us hoping for a glimpse of some new hardware. The most recent spate of rumors suggest that we’ll get a pocket-friendly Nexus 5 sequel from LG with a 5.2-inch screen and a Snapdragon 808 chipset – same as in the mostly great LG G4 – as well as a 5.7-inch powerhouse from Huawei. No, really. LG’s a logical choice considering its close working relationship with the folks in Mountain View and Huawei has upped its Android game dramatically with devices like the P8 and Huawei Watch, but these things will almost certainly get their limelight at a standalone launch event.
The war for your wrist

Honestly, we’re not expecting a ton of movement on the Wear front this week. After all, the platform just got a substantial upgrade a few weeks back, bringing WiFi support and some love-’em-or-hate-’em navigation gestures to your fancy wrist-computers. Wear’s functionality might not see much in the way of upgrades, but I/O would be a great place for Google to announce iOS compatibility for its fleet of Android Wear watches. The feature’s been inching from rumor territory toward reality for months now — it was apparently almost done back in April — and we’ll be crossing our fingers all through the keynote for it.
Prepare to have your “socks blown off”

Just about anything Google’s Advanced Technologies and Products division does makes headlines, and the outfit’s getting a primo slot on I/O day 2 to spill its secrets. Expect at least a brief update on Project Ara as the modular phone makers inch ever closer to a test launch in Puerto Rico; if we’re lucky, we might even get a firm date for when those Ara-friendly food trucks take to the streets. We might not see many (or any) new Android Wear watches at I/O, but the ATAP team promises to show off a few new wearables on Friday, and if the tongue-in-cheek panel description is anything to go off, at least one of them is meant to get strapped to your lower extremities. In an age where smartwatches dominate the wearable conversation, is it finally time for a smart ankle watch? Erm, we’ll see. Also on deck is a new immersive Spotlight Story directed by Justin Lin (of Fast and Furious fame), that’s slated to debut “in full 360 with 3D soundsphere”.
Speaking of 3D…
Cardboard and Beyond

Last year, the I/O swag bag came with a curious slab of cardboard that looked like it fell out of an IKEA box. That was Google Cardboard, an experiment in cheapo VR experiences that just might get fleshed out further this year. The Wall Street Journal reported earlier this year that the company is actively working to turn Android into a virtual reality operating system of sorts, and the I/O stage would be a fine place to put some speculation to rest. Let’s put pricey consumer VR headsets like those from Oculus and HTC aside — what better way to initiate the masses into alternate realms than with some awfully inexpensive gear?
Thing is (as Gizmodo points out), Cardboard might not actually be made of cardboard anymore, and Google might push past the low-cost tidbits of virtual reality we’ve seen so far. Yeah, yeah, that’s nice and vague, there’s no denying Google’s dedicated to digging into alternate views to reality. Remember Project Tango, which put 3D-sensing cameras into tablets to give developers a taste of bringing software experiences into the world immediately around us? And its hefty investment in Magic Leap, a company that wants desperately to blur the line between the real world and ones powered by silicon? Regardless of what actually gets outed on-stage, expect this to be the year Google starts taking VR really seriously.
Connecting all the things

Google has a thing for not letting old, improperly executed ideas die. Google TV might have sunken into obscurity ages ago, but Android TV picked up where it left off… and is struggling to find its footing. The Nexus Player was left us wanting when we first played with it and few OEMs have thrown their support behind the platform as a whole despite the neat tricks it brings to the table. There’s no way Google won’t spend time digging into the future of Android TV on-stage, and it’s got at least one shiny, mostly new gadget to point to: NVIDIA’s Shield TV. The sleek set-top box was first outed at the 2015 Game Developers’ Conference, where it promised to blend Google’s search chops and broad app ecosystem with NVIDIA’s own graphics cards (for game streaming from your local Steam box) and cloud service (for game streaming from a server far, far away). Google’s got plenty of workshops slated for Cast-friendly apps, too, underscoring just how important devices like the Chromecast are to its plans in the living room. We wouldn’t hold our breath for new Chromecast hardware, but we’re more than happy to be proven wrong on that one.

Speaking of old ideas, reports of a service to succeed the ill-fated Android @Home project have been swirling like crazy. The Information reported last week that Google’s so-called “Brillo” software is meant to power seriously low-power devices (with as little as 32MB of RAM) and act as a sort of backbone for Internet of Things device makers to lean on. By providing the foundation for these early creators to build on, Google has a solid shot at creating a common platform with the potential to explode as homes and the things in them grow inexorably more connected. If we’re really lucky, Google will make it easy for companies to bake its first-rate voice input and search features into their wares too, though we’ll have to wait a few days before we find out.
Then there’s Android Auto. Google pushed the in-car experience way hard at last year’s I/O, and since then we’ve seen it pop up in after-market head units from Pioneer and straight into new rides like the 2015 Hyundai Sonata. To say Android Auto is still in its early days is putting it pretty mildly — it doesn’t yet have the finesse and app support to make a seamless, obvious choice for most drivers — but expect Google to shed some light on how it’s doing and where else it’s going.
…And everything else
Some really important bits — like the future of Chrome, Chrome OS and how they’ll intersect — will certainly get their time on-stage, but the scuttlebutt surrounding them in the days and leading up to the show is usually pretty hushed. Expect to see Google push its flat, friendly Material Design even harder, too, as it’s long been said the look would eventually permeate the rest of its web properties. Remember, this is all just a taste of what Google’s got in store for us all this week. For more (you know you want it), just park it right there and keep your eyes peeled for all our dispatches from San Francisco starting this Thursday.
Filed under: Mobile
Google exec confirms Android M will be released this year

It wasn’t too long ago that we first heard whispers of the next version of Android, thanks to an error on the official Google I/O 2015 schedule. We have a strong suspicion that Google will introduce Android M at this year’s developer conference, but we haven’t actually received any confirmed information regarding the next release. However, thanks to a recent interview with a Google exec, it’s now confirmed that Android M will be released to the public before the year’s end.
Read more: What will Android M bring?
In an interview with Fast Company, Android’s Vice President of Engineering Hiroshi Lockheimer spills some details regarding Android M, and what Google’s plan is for future releases:
As we’ve grown as a platform, we realize that to some extent predictability is important for the whole industry: developers, manufacturers, operators, and consumers, frankly. So we’ve landed with sort of a yearly cadence of big releases, so, for instance, one year we release J, the next year we release K, and then the year after that L, and then this year we’ll launch M, and so you can predict what will happen next year.
This certainly isn’t any groundbreaking news, as we were already assuming that Google would release Android M the same way it released Android L – launching a developer preview at Google I/O, then releasing the final build to the public before the end of the year, likely with some new hardware. Even so, the interview does provide some helpful information, since we now know that Google is planning for yearly release cycles for bigger versions of Android. Lockheimer didn’t make any more comments on Android M in the interview.
We’ve already heard that the next version of Android may feature native fingerprint authentication and new voice controls, but what else do you hope Android M will bring? Let us know in the comments below!
LG and Huawei rumored with Nexus smartphones for 2015
It has been back and forth, but it may finally be set who is making the next Google Nexus device… or Nexus devices. Rumors are still swirling around and this time more than ever. Rumor has it there will be a 5.2 inch LG made Nexus and a 5.7 inch Huawei Nexus. The new information has the LG device code named Angler and the Huawei made device code named Bullhead. Fish aliases have always been a Google staple, that is why we think this latest stream of info is worth the time.
The LG Angler will feature a 5.2 inch display, most likely QHD being backed by a Snapdragon 808 processor and a 2,700 mAh battery. LG was quite pleased with the performance of the Snapdragon 808 on their flagship, the G4, so it’s understandable that they would lean this way for a Google device. It seems that the Nexus (2015) that everyone is beggine for will indeed be a reality.
The Huawei Bullhead will sport a 5.7 inch QHD display panel, backed by a massive 3.500 mAh battery. Current plans have Bullhead being powered by the Snapdragon 810 processor, which may or may not change. It all depends on if they can tune it to not overheat without throttling performance. Bullhead is essentially the successor to Nexus 6 and will keep Google in the phablet game.
Both devices are expected to be announced in October, which has become a norm for Google. That means it would most likely be a late October or early November release for the majority of the world. Prices are unknown, but it is assumed the LG Angler will be in the $400 price range whereas the Huawei Bullhead will be around $600.
The post LG and Huawei rumored with Nexus smartphones for 2015 appeared first on AndroidGuys.
LG and Huawei are reportedly making Google’s Nexus phones this year
If you were disappointed that your only choice for a new, official Google phone last year was the gargantuan Nexus 6, you’ll be glad to hear that 2015 could be very different. Android Police sources have elaborated on previous rumors with word that both LG and Huawei are working on Nexus handsets this year. The LG device, nicknamed Angler, would have a 5.2-inch screen and might borrow the G4’s six-core Snapdragon 808 processor — effectively, it’d be a modernized Nexus 5. Huawei’s phone, Bullhead, would pack a bigger 5.7-inch display and could step up to a Snapdragon 810 chip. Think of it as a not-so-ungainly Nexus 6.
Some of the specs of both devices are up in the air, so it’s not clear just how sophisticated they’ll be. They should show up around the typical Nexus release window for October, however, which suggests that they’ll both be poster children for Android M. Just don’t expect a new tablet. AP‘s tipsters don’t believe there’s a revised Nexus slate in the works, which could leave the Nexus 9 soldiering on for another year.
Filed under: Cellphones, Mobile, Google, LG
Source: Android Police
Microsoft bringing digital assistant Cortana to Android and iOS
Microsoft is announcing that Phone Companion will be bringing Cortana to iOS and Android. The Redmond-based company plans on releasing separate apps for each mobile operating system, moving away from the digital assistant’s exclusivity to Microsoft products.
Cortana won’t be available on Android and iOS just yet, as Microsoft is only offering a sneak peak at the new apps today. But, we’ll see an official Android release come late June and an iOS release set for later this year.
Microsoft is attempting to make Cortana as seamless as possible on all mobile operating systems–you should be able to give it the same requests, whether you’re on Android or iOS. However, Microsoft does note that it won’t be nearly as powerful as it is on Windows because of the various integrations. Despite that, you will still be able to get notifications for all of your favorite content–sports, flights, weather, and more.
You can check out the full breakdown in the video below.
Click here to view the embedded video.
It’ll be interesting to see what Google brings to I/O this year in terms of Google Now, as this is a big shift from Microsoft. The real problem company’s are going to face is getting people to actively use these digital assistants. As of right now, people outside of the tech crowd aren’t “sold” that they need a digital assistant.
What do you think of Microsoft making Cortana cross-platform? It’s certainly one of the better moves Microsoft has made for its software. Let us know in the comments.
source: Windows Blog
Come comment on this article: Microsoft bringing digital assistant Cortana to Android and iOS
Google rumoured to be concentrating on Battery Life and RAM optimisations in Android M
It isn’t long to go until its May 28th, the opening day of Google I/O 2015, and that means that we are getting closer to finding out what Android M will bring, and the surprises Google has in store for us.
Until then though, we have a new rumour to consider courtesy of AndroidPolice, who have heard that Google will (once again) be focusing on battery life and RAM usage in Android M (or Macadamia Nut Cookie or MNC). This is hardly a new focus, as Google has previously attempted to tackle battery life issues with Project Volta in the Android 5.0 Lollipop edition. Still, no one will ever say no to getting more efficient use of their smartphones battery life.
Google has apparently told its teams to concentrate on reducing location check-ins, cutting off-charger activities and optimising RAM usage. Google’s own Play Services app often heads the list of guilty parties when it comes to battery usage, so hopefully it will receive a check-up along the way as well.
The other part of the rumour is that Google plan to release a developer build of Android M, just like they did with Lollipop before it. Android M is alleged scheduled for a final release sometime in August. This date should be taken as a provisional date, rather than being set in stone due to possible delays in developing this latest version of Android.
Source: AndroidPolice
Come comment on this article: Google rumoured to be concentrating on Battery Life and RAM optimisations in Android M
Taking a spin in the first car with Android Auto
Get ready for Android Auto to hit the masses. Until now, the only way to get the Google-powered car interface was to install an aftermarket unit from Pioneer, and even those have only been around since March (Parrot is also citing support for Android Auto in its head units, but its availability has not been announced). But that changes today, as Android Auto is now finally available in actual cars that you can buy. That is, if you want to buy a Hyundai. The Korean automaker is the first car company to have Android Auto integrated in its production vehicles, starting with the 2015 Sonata with Navigation models. I recently spent a week with a 2015 Hyundai Sonata Sport 2.0T, and while I think Android Auto still has some growing up to do, I was overall very pleased.
First, a brief primer on Android Auto. It’s essentially a driver-friendly Android interface for your car. “We lock out the phone to make you look at the car screen. It’s a lot safer,” says Andrew Brenner, the lead product manager for Android Auto. Brenner is also the first person Google hired to lead the project two years ago. “The first thing we did [when we started the project] was to put cameras in the cars of Googlers and observe them,” says Brenner. “What we saw shocked us and made us a little scared!” The team found that research participants frequently used their phones while driving, which Brenner says is unfortunately not uncommon. According to a study by the National Highway Traffic Safety Administration, approximately 660,000 drivers are “using cellphones or manipulating electronic devices while driving,” and apparently that number hasn’t changed much since 2010.
People don’t just use their phones for navigation either. Google found that drivers frequently used their devices for calls, messages, music and even things they really shouldn’t be doing, like reading tweets. “Our digital life is so important these days. … People don’t want to leave their connectivity and link to the outside world when they get in the car,” explains Brenner. It became immediately obvious that distracted driving was the main thing that Brenner and his team needed to solve. They started working with auto manufacturers — Hyundai being one of them — to develop an ecosystem that would allow an Android phone to integrate with the car’s existing controls. With some cars, you might navigate the interface with knobs and buttons, while on others, you just use the touchscreen.
The Sonata I tested falls into the latter category, with a touchscreen dominating the center console. It comes with Hyundai’s own navigation and entertainment interface, with SiriusXM, its own GPS navigation system and an SD card preloaded with maps. But if you wanted to use Android Auto instead, now you can. Do note, however, that Android Auto only works with a Lollipop-powered Android phone (that’s Android 5.0 and up). Fortunately, I happened to have a HTC One M9 on hand that meets that requirement.
http://www.engadget.com/embed-5min/?sid=577&playList=518846951&responsive=false
I plugged the phone into the car’s center console via a USB cable, which then prompted it to download and install the Android Auto app. After I did that, I noticed a new “Android Auto” button appear on the screen. I tapped it and voila — that Hyundai interface was gone. In its place was the Android Auto interface, which is so much cleaner and tidier than Hyundai’s own cluttered UI that I couldn’t help but smile when I first saw it. Interestingly, however, it wasn’t a complete takeover. For example, I could still hear SiriusXM while I was fiddling with the Android Auto interface and similarly, I could keep streaming Google Play Music while over on the Hyundai side.
Now, the Android Auto interface isn’t an exact replica of your phone — you won’t see all your apps on here. That’s because it’s meant to surface apps and features that are relevant when you’re on the road. The first thing that you see when you launch Android Auto, for starters, is an overview screen that’s essentially a car-friendly version of Google Now. “It filters through only the cards that are relevant when driving,” says Brenner. In my case, I often saw the currently playing track, recently missed calls, the local weather and directions to either go home or to the office. It also showed me directions to locations of upcoming appointments. I had booked a ticket to a local production of Book of Mormon, for example, and Android Auto instinctively knew to offer me directions to the theater. Creepy, but useful.
Along the bottom of the screen is a universal nav bar that leads to maps and navigation, the phone dialer, music apps and an app tray. In Hyundai’s case, the latter simply leads back to the default car menu. Aside from these features, Android Auto also supports basic Google voice actions. So, for example, you can say things like, “What’s my next appointment?” or, “What’s the weather today?” and Android Auto will respond with the appropriate answers just like your phone would.

Indeed, Android Auto is very voice-driven. In the case of the Sonata, I pressed and held down the voice-command button on the steering wheel to activate the microphone (though simply tapping the microphone on the screen would work too). From there you can say all kinds of commands, like “How did the Warriors do last night?” and, “Find me some coffee.” In the first case, you’ll hear a voice telling you the scores, while the latter command will bring up a list of nearby coffee shops. Tap a spot you want to go to, and Android Auto will navigate you there.
In my experience, voice controls worked great. Unlike a lot of car systems where you have to go through a tree of commands to do anything, I could just speak naturally. In my own 2012 Ford Focus, for example, I have to say, “Destination, Street Address,” before detailing exactly where I want to go. With Android Auto, I could just say, “Take me to In-N-Out,” and it’ll just show me the way to the closest In-N-Out. I could also say commands like, “Call Roberto,” or, “Text Michael,” for calls and text messages and “Play [insert name of artist or song]” for music. In fact, I can even specify the exact app. With music, for example, the default is Google Play Music, but Android Auto works with other music services like Spotify, TuneIn and iHeartRadio. So I could say, “Play Vampire Weekend on Spotify,” and it’ll know to switch over to the different app to play the song.
The look of Android Auto is also designed to be very car-friendly. The fonts are nice and big and the UI is meant to be easy to navigate. Google Maps on Android Auto, for example, has fewer location labels than its mobile counterpart. When I get an incoming text message, I see a notification pop up on the screen showing who sent it, but not the actual message itself. Instead, I have to press the voice button to prompt Android Auto to read it to me. The menu system of each app is also simplified and standardized, while maintaining a few individual characteristics. So, for instance, both Google Play Music and Spotify have the same play/pause and track controls, but the former is orange while the latter is green. The apps also have different menu options depending on their features.

That’s not to say I didn’t encounter a few bugs. Whenever I requested Android Auto to play a song, it struggled to show me the relevant track information on the screen — it would show “Getting your selection” instead of the name of the song. Additionally, the current Android Auto app library is still relatively small. While I appreciate that it supports WhatsApp and Skype as alternate messaging services, I wish that it could also support Twitter DM and Google’s own Hangouts, the two apps that I use the most. The same goes for music — I wish it supported Rdio and SoundCloud as well. Still, these are mostly teething problems, and I suspect Android Auto’s performance and app library will improve over time.
So if you’re Hyundai, why would you agree to offer Android Auto if you’ve already invested time and money in your own in-car solution? Cason Grover, Hyundai’s senior group manager for Cross-Carline Planning, says it’s all about freedom of choice. “Right now if you want onboard maps, you have to use this SD card. … That’s good technology right now, but over time, mapping will become more and more offboard,” he says, pointing to Google’s ability to have real-time traffic info. But when it comes to driving in areas where you might not get great data reception, automotive GPS will still be useful. Brenner says that Android Auto also isn’t meant to take over your car’s internal system like heating and seat suspension.
But it’s clear that carmakers like Hyundai see the benefit of partnering up with the likes of Google and Apple — Hyundai’s 2015 Sonatas with Navigation will also be compatible with Apple CarPlay down the road — if only to make their vehicles more appealing to smartphone-savvy consumers. “We’ve learned quickly that to offer everything that everybody wants is not feasible, more so with apps on the phone,” says Grover. “Google works with those developers, and those apps work with every Android Auto phone. All we have to do is work with Google to integrate it with the car.”

To drive home the point, Hyundai is also planning on rolling out cars with a new head unit called Display Audio. It has a center console touchscreen like the Navigation models except that it won’t come with embedded maps — you’ll have to supply your own. Not only does this make the cars a lot more affordable to the average consumer, but also it’s when third-party solutions like Android Auto and Apple CarPlay really come into their own.
“Right now only less than half of all Sonatas have support for Android Auto,” says Grover, explaining that’s because the Navigation models are mid- to high-level options. But once Hyundai rolls out those cars with Display Audio units, nearly all of Hyundai’s fleet will be Android Auto-ready. “Android Auto is focused on trying to have you use your phone in a much safer way,” says Brenner. “We want to give people the connected experience that they crave.”
If you’re ready to take the Android Auto plunge now, however, well you can always head on over to your closest Hyundai dealership to check out the new Sonatas with Navigation. If you’re already a current owner of a 2015 Sonata with Navigation, you’ll be able to take your car down to a dealer where you can update your car’s software with Android Auto. You could also add an aftermarket unit from the likes of Pioneer or Parrot if you’d rather not give up your existing car. And, of course, you could also just wait for more automakers like Honda, Ford and Audi to roll out their own Android Auto-compatible vehicles later this year.
Filed under: Transportation, Google
Two Nexus smartphones in 2015, rumours say, and no tablets on the horizon
<ins class="adsbygoogle"
style=”display:block”
data-ad-client=”ca-pub-8150504804865896″
data-ad-slot=”8461248232″
data-ad-format=”auto”>
(adsbygoogle = window.adsbygoogle || []).push();
We’ve been hearing conflicting rumours in the past few weeks regarding which manufacturer could be making Nexus smartphones this year. Huawei and LG are the two front runners, however, a rumour today has perhaps made the discussion a little easier – according to said rumour, there will be two Nexus smartphones in 2015 due out around October, one from Huawei, and one from LG. Now wasn’t that easy?
These devices are allegedly codenamed the LG “Angler” and Huawei “Bullhead“, and I’m sure we’re all hoping these devices don’t take inspiration from their namesake because both those fish are hideous. Joking aside, the LG device is expected to be a 5.2-inch device with a Snapdragon 808 processor and 2,700mAh battery and the Huawei a 5.7-inch device with Snapdragon 810 and 3,500mAh battery, which fits in with previous rumours which say that the Huawei device will be based on the yet-to-be-announced Ascend Mate 8. Another point worth noting from this rumours is that there will be no tablet to replace the Nexus 9 this year.
What do you think about having two Nexus smartphones in 2015? Let us know your thoughts in the comments below.
Source: Android Police via TalkAndroid
The post Two Nexus smartphones in 2015, rumours say, and no tablets on the horizon appeared first on AndroidSPIN.
Two Nexus phones in 2015, but no Nexus tablet according to rumor

As Google I/O draws near, just two days away now, the rumor and expectation mills are churning at full force. The latest expectation is that Google will bring two new Nexus phones to market this year, but no new tablet is on the immediate horizon.
These rumors sound fairly plausible, we have already heard that Huawei is building a Nexus phone, a 5.7-inch monster with code name Bullhead. I’ll leave you with the previous coverage for more details, but we expect to see the device later in the fall with the Snapdragon 810 SoC and a nice big 3,500mAh battery.

The new phone rumor is for another LG built Nexus device. Clocking in with a 5.2-inch display, the LG Angler looks like it may be fairly similar to the LG G4 with the Snapdragon 808 SoC. Speculation is early on this one though, specs are bound to change, and many components have not been chosen yet. With the general idea being that this LG phone is the proper successor to the Nexus 5, we do not expect top rung specs, just an overall solid experience.
Finally, do you like your Nexus 7 or Nexus 9? I hope so, since you may be stuck with it for another year before another Nexus tablet is introduced. We can always hope for a surprise, but at this point, there are no Nexus tablets in the rumor mill. Although the Nexus 7 has been removed from the Google Store, the Nexus 9 is still up for sale, offering you a solid Android tablet experience and the latest version of the Android OS (finally.)

I think I’ve mentioned this, these are purely rumor at this stage. We can’t help but send you over to Android Police where this new rumor of an LG Nexus phone comes from.
Stay tuned for more to come, we will be on the ground at Google I/O 2015, May 28-29, that’s Thursday and Friday in San Francisco. We hope you are as excited as we are to see the next chapters in the history of Nexus.
.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;
What do you think about a new smaller form factor Nexus phone? Is a 5.2-inch display the right size for you?









