Google is considering building its own phone. But why?
Google is discussing internally about building its own smartphone, according to The Information, which cites people working at Google.
The recently promoted head of Android, Hiroshi Lockheimer, is said to be part of the talks, but other details are scarce. It’s not clear who is the proponent of the idea or when a decision will be made.
It’s possible that The Information caught wind of one of the many ideas that are thrown around inside Google on a daily basis. But given the report from last week about Google’s work on standardizing phone components, it’s likely that the “Google phone” is more than idle talk.
Why?
Why would Google want to make its own smartphone? Presumably, to exert more control over a sprawling, occasionally unruly ecosystem, and to address the biggest issues holding Android back right now: fragmentation, poor update support, and security vulnerabilities. But Google already has deep control, if not complete, over the Nexus smartphones. So how would a true Google phone help advance these goals?
The Google phone could be a platform for showcasing and promoting the standardized components Google is reportedly working on.
According to The Information’s report from last week, Google is looking at improving camera capabilities so phones can capture information from the environment, that Google can use to create new, valuable features; adding more memory to processors to improve performance; improving sensor hubs that can survey the world at all times without draining a lot of power; and adding new sensors.
Sure, Google could work with chipmakers like Qualcomm and MediaTek to put these features on their roadmaps, and just hope that Android OEMs will pick them up. The alternative is to create a compelling smartphone that really showcases Google’s advanced features, and sell it directly to consumers. That could pressure Android OEMs into adopting Google’s standardized hardware.
The Chromebook Pixel and the Pixel C Android tablet have set a precedent for this. Google used the former to lead the adoption of USB Type C, while the Pixel C appears to be designed with a more PC-friendly version of Android in mind.
Taking Android to the next level
The problem for Google is that we’ve hit a plateau in terms of what features Android can offer based on software alone. For more advanced features, like better voice control or machine vision, specialized hardware is needed. Google needs to make sure its wish-list of components and features is adopted by chipmakers and OEMs, so that most new phones and tablets can support these advanced features. The risk, if Google fails, is to have a divided Android ecosystem, with an elite tier of devices with advanced functionality, and everyone else.
Google needs to take initiative because the current Android ecosystem is so cutthroat. Samsung is still making a lot of money, but it’s mostly from components that it sells in high volume. Almost everyone else is feeling the heat: Qualcomm, LG, Motorola, even Xiaomi, not to mention HTC or Sony. These embattled companies can’t be expected to act in Google’s interest or even in the interest of the Android ecosystem. So, in a way, Google has to make its own phone. It has to take the lead.
Whenever people talk about Google’s Android business model, Apple comes up, and rightfully so. Apple has consistently huge profits, even if its market share is relatively low. More importantly, Apple can decide exactly what hardware and software to put in its devices this year, and next year, and the year after. Google doesn’t have that luxury, but if the rumors are correct, it’s trying to change that.
Let us know your thoughts. Do you see Google making its own phone from the ground up?
Chrome announces end to Windows XP support
Earlier this year, Google announced that it would be supporting older desktop OS’s for Chrome for the remainder of 2015, but not beyond the end of the year. Today, the tech supergiant announced that after April 2016, the company would no longer be offering any support for Windows XP, Windows Vista, and Mac OS X 10.6, 10.7, and 10.8. The browser will still function on these operating systems, but there will be no security updates or fixes of any kind after April.
If you’re still using one of the ancient operating systems, Chrome’s lack of support is the least of your problems. Google strongly encourages you to update your OS to a more recent version, and I do too. Windows XP turned 14 this year, meaning it was released when Boy Bands were king and Friends was still on air. If you’re running Windows XP still, do yourself a favor and get an update. You’ll get Chrome support, and you’ll also have an OS made in this decade.
Source: Chrome Blog
Come comment on this article: Chrome announces end to Windows XP support
Google may build their own phone that isn’t a Nexus
We recently reported on a story about Google trying to end fragmentation in Android. However, it now looks like Google may be going a little farther and making their own Google made phone.
If they make their own Google phone, not a new Nexus as that is made by other companies, they would be able to control literally everything just like Apple does. The chips, the software, and the hardware would all be made by Google.
Currently, this is just a rumour, but it would be awesome to have an Android phone that is totally made by Google as it would be the smoothest Android device ever. The only problem with this idea is the Nexus already receives updates quickly and is pretty smooth. Plus, a Google made phone would only make other manufactures who run Android look bad. They would always release the newest version of Android even later and considering Google wants manufactures to use Android, probably not a good idea. However, share your thoughts on if you want a Google made phone in the comments?
Source: The Information
Come comment on this article: Google may build their own phone that isn’t a Nexus
Google Maps now has offline navigation support
(adsbygoogle = window.adsbygoogle || []).push();
For the longest time, Google Maps has been capable of saving maps for offline use, but has always lacked one crucial piece of the puzzle – offline navigation support. This is particularly important for the frequent traveller who doesn’t necessarily have readily available access to data, but Google has finally come through for us all. Starting today, Google Maps now has offline navigation support and the update will start rolling out to all Android apps from today – iOS is “coming soon”.
To use the new functionality, you’ll need to download the map before you start your navigation – once downloaded, you’ll be able to use the map almost as if Google Maps was still connected to the Internet. The questions that come to my mind are how much storage this functionality requires and whether the re-routing part of the navigation is still going to work as well once the data connection is cut. All the same, it’s great to have this functionality and there are a lot of people that are going to be happy about this.
http://playboard.me/widgets/pb-app-box/1/pb_load_app_box.jsWhat do you think about Google Maps now having offline navigation support? Let us know your thoughts in the comments below.
Source: Google Blog via Droid-life
The post Google Maps now has offline navigation support appeared first on AndroidSPIN.
Chrome will stop supporting XP, Vista and early OS X this year
It seems like Google is looking to do a little spring cleaning. In an announcement on the official Google Chrome blog, the company noted that it will no longer support browsers on Windows XP, Vista and Mac OS X 10.6, 10.7 and 10.8 devices. Google had alluded to the discontinuation of support back in April and reasoned that these older — and in XP’s case, almost prehistoric — operating systems can no longer offer the crucial security updates the web browser needs to keep malware at bay. This means that older operating systems running Chrome browsers will still be fully operational, though they won’t be eligible for new updates and features.
Source: Google Chrome Blog
Nexus 6P cases present challenges for screenshot captures
If you purchased a Nexus 6P with plans to ensconce it in a case and you like to take screenshots, you better check the case to make sure you do not end up frustrated with the experience. Some users are reporting that the material and construction used for some cases, including the Nexus 6P Case and the Adopted model available through the Play Store, are making it extremely difficult to capture a screenshot.
The problem appears to be rooted in the materials used for the cases being on the flexible side. When combined with the fact that the power and volume down buttons are fairly close together and the case is all one piece, users are finding attempts to capture a screenshot result in the volume up button being depressed as well. This triggers a bug report instead of a screenshot.
As you are shopping for cases for a new Nexus 6P, you may want to look for cases that are constructed of a sturdier plastic. The other item to look for may be buttons that are separate pieces from the rest of the case so that button presses are independent of the case material.
Anyone out there having trouble with screenshots on a Nexus 6P?
via: Android Police
Come comment on this article: Nexus 6P cases present challenges for screenshot captures
Apple Music is live on Android devices today
Apple Music launches in beta form today on Android, cementing it as the second Apple program to hit Google’s mobile platform (following the “move to iOS” app). Apple offers a three-month trial to Android users, as it does to Apple customers. Since the Android version is still in beta, it’s missing a few features and upgrades: Apple promises music videos are on their way and the sign-up process will be optimized for Android. To sign up for a family membership, you’ll need a Mac or iOS device for now. Apple Music on Android requires version 4.3 or better, and it’s a 29M download. After the trial period, Apple Music is a $10-per-month service. We gave the iOS version a spin when it launched on June 30th and found it to be heavy on features but a little disjointed. Apple announced the Android version of Music back in June, alongside a promised launch on Apple TV this fall.
Via: TechCrunch
Source: Google
Offline maps and navigation function is officially rolling out to Google Maps
Back at Google I/O this year, the ability to search for a city or specific area on Google Maps and download it for offline use was demonstrated, and it now appears to be rolling out to the masses.
Basically, while you still have access to the internet, you can search for a city or even country and tap the ‘Download’ option on the resulting card, or you can navigate to the ‘Offline Areas’ section of Google Maps and press the ‘+’ button to begin downloading the map of your choice. Once the chosen area is downloaded, Google Maps will switch automatically between online and offline modes as need be, so when you lose internet access it will switch seamlessly into offline mode, and vice versa. As you can see from the GIF above, it really is a simple process.
While in offline mode, access to live traffic conditions will naturally be unachievable. Google says that maps will only be downloaded to the device when on a Wi-Fi connection. The updated Google Maps app is in the process of rolling out, so it may be a couple of hours before it reaches your device.
Source: Google
Come comment on this article: Offline maps and navigation function is officially rolling out to Google Maps
Nitpicking the Nexus 5X: Gosh the grievances!
Now that the LG Nexus 5X has hit the hands of some of the more hardcore haves, I thought it would be a good time to sound off on some of the sour spots. Make no mistake, the device is a fantastic product and a worthy upgrade from the original Nexus 5. Still, I tend to test out a lot of phones for evaluative purposes and suffice to say there have been a number of issues I’ve had with the 5X in the days I’ve spent with it so far. Some of these are device-specific, some are OS-related, however, given that the two are one-and-the-same, both will be addressed in this piece.
Also, I feel it pertinent to mention that this is not intended to be a thorough review of the hardware by any means. Those interested in a more objective, in-depth look at the device and all it has to offer should check out our official review here. With that said, let’s get this train started.
The “Misunderstandings”
Call it strange, but unless I’m specifically required to know relevant information for purposes of a post or debate, I tend to shy away from full-disclosure when it comes to IT products. Basic specs are fine, but I want to know the ins and outs for myself, kind of a pseudo sense of discovery. With that said – and especially regarding the 5X as opposed to the 6P – my prior knowledge of the spec sheet was limited so as to be potentially surprised. Indeed I was, but in both good – and bad – ways.
To this end, the first formal section will address those “darling discoveries” I have encountered:
Sour about the speaker
Before I had my hands on a 5X, I was under the impression the prominently visible dual “grill” setup along the top and bottom bezels were for stereo speakers. Nope. Sound comes only from the bottom vent, and the sound quality is really lacking for 2015, especially with companies like ZTE making it a sound priority.
YouTube videos for example, are harder to enjoy due to this problem, and I really wish LG could have put a better sound system in the hardware. At the very least, at this point in time if companies are going to make it look like there are front-facing stereo speakers, they ought to actually do it.
This is not to say the Nexus 5X is horrible, but in all honesty I’ve heard better sound coming from rear facing speakers than the one pointed flat at my face on this device. Oh well, that’s what headphones are for perhaps.
Bravo about the build
Some of the other aspects of the 5X are, in my humble opinion, fantastic. I happen to love the design, even the camera protrusion on the back. It hearkens back to the days of the HTC One X, of which I have fond recollection. At least on a personal level, I feel the 5X looks more modern than the original Nexus 5.
Additionally the screen is excellent. Shortly before the 5X arrived I stared in total disbelief at the spec: it’s “TFT”. And yet, the screen is – as far as non-AMOLED goes – bright, vibrant, and colorful. It is perhaps a testament to LG’s own display prowess.
…but those buttons…
On the other hand, I have nothing positive to say about the flimsy power and volume buttons along the right side of the phone. They are every bit as bad as those on last year’s Nexus 9. In the case of said tablet, the issue was gradually resolved with later builds, and seemed to be better – on the whole – with the white variant.
LG still makes some internally produced hardware with buttons along the side, one of which I used just last month, released in Japan as the LG Spray. This device had the same tactile, responsive buttons that LG used to make on all their phones, thus I begin to wonder if this is something Google-related given the HTC Nexus 9.
Could LG fix this with later production runs, as it did with the Nexus 4’s sliding siding? Sure. But it’s not going to do diddly squat for me, or the potentially hundreds of thousands of early adopters who potentially are less than pleased with the issue. Sure the Nexus Imprint negates the need to use the power button, but that’s hardly justification. Speaking of which…
I can’t quite place my finger on it…
The Nexus Imprint sensor is cool, without a doubt. Rather than requiring a prior press to turn on 5X’s screen (or a pressurized push), a single print does double duty and will both power on the device and immediately unlock it.
This works wonders, especially given the aforementioned build quality blues regarding the power button. You simply place, and presto.
The problem is that…any time the device is turned off and something presses against Imprint, the sensor will try to read it. Wrong. It makes handling the device somewhat troublesome because of the two quick haptic feedback responses that occur for bad scans.
At least for me, it’s like I’m always accidentally touching the Imprint sensor by “accident” and constantly get the vibratory feedback error. Likewise depending on the finger(s) registered, you may inadvertently turn wake up and unlock the display simply by mistake.
It kind of makes me wish the sensor was on the front of the device, a la Samsung, though obviously nothing can be done about this now.
The force returns in full
Related to this is the problem of the 5X’s forceful feedback. In all my years and experience, I don’t think I’ve ever encountered a device with haptic feedback this strong. Indeed many have said that the actual audible vibration from the part itself is stronger than the sensation itself.
And it is loud. Even on a semi-crowded Tokyo subway with people talking next to me, I could still hear the mechanical “noise” emitted by the build as I typed this very sentence.
This brings up two specific issues for concern:
1. If haptic feedback is this strong, will the internals wear out over time due to too much use?
2. Why isn’t there a way to manually adjust the haptic feedback intensity in the Usability settings option? Given that high intensity might be best for people who have certain disabilities, it seems fundamentally relevant.
Mushy Marshmallows
Concluding this list, I am also not particularly happy with the fact that the home screen now has 5 columns instead of just 4. The icons seem almost too small, despite the fact that their text labels are permanently enlarged. This is a stark contrast to the Google Now Launcher’s typical presentation wherein it usually has gigantic icons.
I am also somewhat surprised that the font size on the 5X is so small. Even when set to Large, it looks small. Extra Large, which is usually comically gigantic, is basically what I’d consider to be just “large” standard.
And on a final note, I’m not too keen on the new font. What was wrong with Roboto…
Wrap up
And there you have it, my general grievances about the Nexus 5X. Is it a good phone? Yes. Is it a worthy sequel to its predecessor? Definitely. Is it the best product it could be? No, not really. Given that rumors persist that the 5X had 3GB of RAM until the last minute, I am inclined to lean towards the belief that it was once much more, but stripped of its superiority due to possible competition with the 6P.
Still, assuming you want a Nexus, one must be happy with what they have, as that’s all we’re going to get, this year at least. With that said, I’d like to ask for your thoughts. Are any of you sporting the Nexus 5X? Do you have similar feelings or is everything perfect as far as you’re concerned? Leave a comment below, or yell at me on Google Plus!
// <![CDATA[
(function ()
var opst = document.createElement('script');
var os_host = document.location.protocol == "https:" ? "https:" : "http:";
opst.type = 'text/javascript';
opst.async = true;
opst.src = os_host + '//' + 'www.opinionstage.com/polls/2308141/embed.js';
(document.getElementsByTagName('head')[0] ());
// ]]>
Google Maps adds offline turn-by-turn navigation, search, and more
During this year’s Google I/O we learned that fully featured offline navigation would be making its way to Google Maps before 2015 was over. Now Google is making good on its promise, as they have announced that offline navigation and search is rolling out!
While it was possible to use Google Maps offline in a limited fashion before, the newly upgraded offline functionality gives you the power to select entire cities, counties, or even countries to download. Once downloaded, you’ll have the ability to get turn-by-turn navigations, search for locations, and more.
Whereas before you could simply view an area of the map offline, now you can get turn-by-turn driving directions, search for specific destinations, and find useful information about places, like hours of operation, contact information or ratings.
While offline functionality is exceptionally important for those with limited data or for those in countries where data speeds are slower, this is also a welcome addition for those who find themselves travelling country roads, small towns, and other areas where data connections might be spotty. As someone who has family in a neighboring city and has to pass a dead spot that lasts about twenty minutes every time I visit them, I certainly am very excited about getting access to fully-featured offline maps! Of course, in usual Google fashion, you can expect the functionality to start rolling out gradually.
What does everyone think, do you see yourself using this regularly? Or are the data connections in your area strong enough that it is really a non-issue? Let us know your thoughts in the comments.
AIVAnet 