Google shows off the Android M’s Auto Backup for Apps function in video
One of the great things about flashing a custom Rom on your Android device is being able to backup and restore your apps via the custom recovery or by using an app such as Titanium Backup, it’s especially helpful if you’ve had to factory reset your device or if you’ve swapped over to a new device. Now it seems like un-rooted users will also be able to automatically backup and restore their apps thanks to a feature called ‘Auto Backup for Apps’ that is present in the latest Android M Preview.
Google’s Matthew Jav Williams takes us on a video run through of the Auto Backup for Apps feature, telling us that the apps user data will be automatically backed up and stored in Google Drive with a 25mb limit. The app backups will not count as part of your Google Drive quota. If you’ve installed apps on your device either from a third-party app store or by side-loading, don’t worry, they will also be backed up because the Auto Backup for Apps function isn’t directly tied to the Google Play Store.
Backups will occur when:
- It is night-time
- The device is charging
- The device is connected to WiFi
Developers can include this feature into their apps by re-building their apps with version 23 of the SDK, they can also choose to opt out of including the auto backup function as well as choosing not to back up sensitive data or device specific tokens. Matthew gives some coding examples in the video below which show how easy it is for developers to include the Auto Backup for Apps function.
Click here to view the embedded video.
Source: Google Developers Blog
Via: Phandroid
Come comment on this article: Google shows off the Android M’s Auto Backup for Apps function in video
OnePlus says the OnePlus 2 is “ahead of its time”
Today, OnePlus reflected on the creation of its original device while providing insight to the journey it has been creating the OnePlus 2. Last week, OnePlus said that the upcoming phone is going to be “the 2016 flagship killer” even though a reveal is coming next week. It turns out that the company really means what it says.
OnePlus says its next flagship will offer features that other devices will not see until the release Android M this fall. The company also mentioned that the OnePlus 2 has been designed with the future in mind rather than competing directly with today’s offerings.
“Contrary to what some of our followers on social media may have believed, our tagline is not a typo – the OnePlus 2 was not created to compete with the flagships from 2015. We’re more interested in looking further into the future.”
It has been over fifteen months since the OnePlus One was announced. The company believes in lengthier life cycles than just about anyone else in the mobile industry. This is what OnePlus could be aiming for with its OnePlus 2. It doesn’t want to be the company releasing a new device every six months. OnePlus wants one that is made to last.
Source: OnePlus
Come comment on this article: OnePlus says the OnePlus 2 is “ahead of its time”
Google Nexus 2015 rumor roundup

The second half of the year is going to bring us some amazing smartphones. Among the most anticipated announcements are those related to Google’s popular Nexus series. Rumors tend to start blazing through the internet very early on, and this year is not the exception.
It is no surprise to see the industry having such a high regard for the Nexus line-up. These are, after all, Google’s demonstration of where they want Android to go. Quality hardware, a pure Google experience and timely updates have always been the Nexus stamp, which has helped the brand gain a major follower base.
Where does Google want to take the most popular mobile operating system now? What will the upcoming Nexus device(s) be like? We have gathered plenty of (unofficial) details to share, so let’s dig right into the goods.
This article will continue to be updated as new information begins emerging. Bookmark this page and keep checking it if you want to stay in the loop! The article will also be pushed to the front of our home page whenever it’s edited.
Nexus 5 (2015) from LG?
The Nexus 6 offered performance and specs without compromises, but the phone wasn’t exactly for everyone, due to one main reason. Its massive 5.96-inch screen and gargantuan body will definitely make it an uncomfortable phone to bear, especially for those who have smaller hands. This forced Nexus fans to stick with an older-generation handset if they wanted to have a traditionally sized phone.

Google may be onto something this year. Recent rumors suggest there will be a couple Nexus phones launched this year. One of them would be manufactured by LG and reportedly resemble the phone maker’s Nexus 5. In fact, some believe the new phone could be a direct successor, a Nexus 5 (2015) if you will.
LG’s Nexus device is reportedly codenamed Bullhead and is rumored to come with a Snapdragon 808 processor, a 5.2-inch display and a 2700 mAh battery. So far this is all we know about this product, though.
More rumors revolve around a Huawei Nexus phone, so we will focus on that one for now.
Huawei Nexus

Reports of a Huawei Nexus have been making the rounds for a while, and the good news is these reports come from multiple sources, including some highly reliable ones. So while LG’s Nexus is shrouded in mystery, we can be almost totally confident that Huawei and Google will launch a Nexus phone this year, and we also have a pretty good idea of what to expect. Here’s the rundown.
Design
We have seen or heard very few details on what this Huawei-made Nexus phone could look like, but we can tell you one thing – it will be large. Rumors suggest the phone’s screen will measure 5.7-inches, which just so happens to be the same screen size as the Samsung Galaxy Note 4.
According to @evleaks, the Huawei Nexus will feature a metallic construction and a fingerprint sensor. In other words, it’s rough outline may be pretty similar to the Mate series. In fact, there’s a good chance the Mate 9 (due this fall) will contain hints at what to expect from the Google-branded device.

If Huawei’s latest work is any testament, we should see a well-engineered phone with a solid build quality. The Chinese manufacturer is no rookie, and they can make some amazingly well-built gadgets. Let’s show you some examples.
Huawei devices in videos
.rvs_wrapper
width: 350px;
.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;
font-size: 24px !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 (min-width : 480px)
body #page .rvs_wrapper.cbc-latest-videos ul
width: 100% !important;
@media only screen and (max-width : 480px)
body #page .rvs_wrapper.cbc-latest-videos
width: 100%;
float: none !important;
overflow-x: auto;
overflow-y: hidden;
body #page .rvs_wrapper.cbc-latest-videos ul
overflow: auto;
max-height: none;
body .rvs_wrapper.cbc-latest-videos ul li
float: left !important;
clear: none !important;
Display
As we mentioned above, the upcoming Huawei Nexus smartphone should come with a sizable 5.7-inch panel. What we didn’t tell you was that, like the Nexus 6, the new Nexus should also feature a QHD resolution display (2560x1440p). This entails the panel will have a pixel density of 515 pixels per inch.
Pixels should be packed in a little tighter than in the Nexus 6, due to the slight size difference, but it’s likely not a very noticeable upgrade.

Specifications & hardware
The little evidence we have tells us this phone should be quite powerful. While the new LG Nexus is expected to go with the slightly sub-par (yet still capable) Snapdragon 808 chip, Huawei is not skimping out on performance one bit.
Most rumors state the new Huawei handset will come with a Snapdragon 810 chipset. Evan Blass (@evleaks) claims it will pack a Snapdragon 820 SoC. Regardless of the outcome, Huawei making a move to Qualcomm would represent a significant change, as they have stayed exclusive to their very own Kirin processors so far. Maybe this is one of the conditions for working with Google? After all, while Google is known to have worked with more exotic processors in the past (like Texas Instruments and Nvidia), the processor manufacturer has a huge role in ensuring support and timely updates through the lifetime of a device. Perhaps Huawei’s Kirin is just too risky for Google from this perspective?

Other hardware specifications continue to be a mystery, but Evan did say the phone should also come with a fingerprint reader, a first for Nexus devices. This would make total sense, as Google announced at Google IO that Android M is to integrate native support for fingerprint readers. This will enable users to make purchases on the Google Play Store, unlock devices, protect sensitive data and more.
There’s also a good chance the next Nexus will feature USB Type-C, which Google already adopted for the new Chromebook Pixel and hinted at for future Android smartphones. As for microSD, while Android M has gotten a bit friendlier to external storage, we would be very surprised if Google reversed its stance and included a microSD slot on a Nexus device.
Camera
The upcoming Nexus devices’ cameras may be the subject we have the least information on. We have heard some rumors say the LG Nexus successor will come with a dual-camera setup, similar to the in the HTC One series. In addition, some believe Huawei’s Nexus phone could be based on the Huawei Honor 6 Plus, which also happens to sport a couple cameras in the back.
Many would consider this a gimmick, as its most popular functions are to distinguish distance and allow for digitally applied bokeh effects (otherwise known as “blurry background”). While that may be a valid argument, I wouldn’t discard the possibility of Google adopting this dual-camera technique. The Mountain View-based company has been playing around with similar technology in Project Tango, and they do appear to be well-invested in the concept.

If the LG Nexus rumor winds up being true, we do hope the Korean manufacturer makes life good by implementing the LG G4’s camera. Nexus phones are not exactly known for having exceptional shooters (Nexus 6 was better), so it would definitely be a welcomed addition.
Getting back to the Huawei Nexus, camera info is completely absent. With the implementation of a superior Camera API in Lollipop, the conditions are set for a truly great camera experience, provided Google and Huawei won’t skimp on hardware. Unfortunately, that happened before, so it remains to be seen whether the Huawei Nexus will buck the trend.
Software
Nexus phones characterize themselves by staying true to the Pure Google experience; we have no doubt this will also be the case with the new Nexus phone(s). Furthermore, we also know the next-generation Nexus handsets should be the first to launch with Android M, Google’s new version of their mobile OS.
Improvements over Lollipop include granular permissions, custom Chrome tabs, battery improvements, USB-C compatibility, app state backup and native biometric support. You can see a detailed explanation of all Android M features in our announcement post, as well as our detailed “Diving into Android M” article series.

Pricing and release date
Most Nexus devices have been launched either in October or November. We expect 2015’s devices to follow suit, and previous rumors support these suspicions. Evan Blass’ sources previously stated they should ship in Q4, while The Information’s insiders suggest it will be in “the Fall”. Pricing-wise, some think the Huawei Nexus will be more upscale, due to the top specs and metal constructions, while LG’s Nexus could follow in the tracks of the popular Nexus 5. But there’s no guarantee that will be the case, at least for now.
Wrap up
2015 is looking to be a great year for Google. If most of this information proves to be true, the new Nexus products will be the phones to beat – especially Huawei’s. As we mentioned above: don’t forget to keep it tuned to Android Authority and this specific article, as it will continue to get updates as soon as new information emerges.
For now, let’s just hit the comments and share our thoughts on these rumors. What would you like to see in the new Nexus phones? Are you signing up for any of them? Many of you are probably happy a normal-sized Nexus phone is likely to hit the market again!
Tidbit in Developer Preview suggests Android M will be Android 5.2
<ins class="adsbygoogle"
style=”display:block”
data-ad-client=”ca-pub-8150504804865896″
data-ad-slot=”8461248232″
data-ad-format=”auto”>
(adsbygoogle = window.adsbygoogle || []).push();
Google likes to leave extremely subtle clues about its upcoming Android software builds, and the latest one is no different. It was been uncovered in the latest Android M Developer Preview (#2 for those who aren’t counting) that a new “demo mode” has been introduced, presumably for the purpose of showing off the new features of Android M. What’s interesting about this demo mode is that the time on the device resets to “5:20″ – and if Google’s previous teases are anything to go by, this is as good as a confirmation that Android M will be Android 5.2, not Android 6.0.
For those who aren’t aware, the previous teases we’re referring to are like the time Google started teasing Material Design in Android Lollipop and the clocks on its screenshots were set to 5:00 – this was also the case with Android 4.4 (Android KitKat), Android 4.2 (Android Jellybean), Android 4.0 (Android Ice Cream Sandwich) and Android 2.3 (Android Gingerbread). We’re honestly not surprised by this news at all as it looks like Android M will be an incremental, though still substantial, update over Android Lollipop, improving on some of the missteps in their biggest overhaul in recent memory.
What do you think about Android M being Android 5.2, not Android 6.0? Let us know your thoughts in the comments below.
Source: Technodify via Phone Arena
The post Tidbit in Developer Preview suggests Android M will be Android 5.2 appeared first on AndroidSPIN.
Google finally acknowledges the Lollipop battery drain associated with mobile radios
Over on the Android Developer Preview portal, Google has acknowledged an issue with battery life on Lollipop.
The problem occurs when a device running either 5.0 or 5.1 uses data. Internet apps will continue to drain the battery by keeping mobile data active unless they are forced to stop. On KitKat, apps stop doing so once they have completed their tasks. According to the user who reported it, this happens on Android M, as well. He or she also adds that the issue has been in the Android Issue Tracker since April, but Google has given it low priority.
A project member responded to the post with this:
Hi,
Thank you for reporting this issue. We have passed this on to the development team and will update this issue with more information as it becomes available.Status: Acknowledged
Owner: dnaga…@google.com
Labels: Defect-22287469
Personally, I’ve experienced this since my LG G3 updated to Lollipop some time ago. Battery life indeed was worse, as the personal anecdotes I had read had mentioned.
Still, Google realizes this complication, and hopefully, this means that Google will raise its priority and work to fix it, especially as Lollipop (and later, Android M) becomes the most used flavor of Android.
The post Google finally acknowledges the Lollipop battery drain associated with mobile radios appeared first on AndroidGuys.
Google finally acknowledges the Lollipop battery drain associated with mobile radios
Over on the Android Developer Preview portal, Google has acknowledged an issue with battery life on Lollipop.
The problem occurs when a device running either 5.0 or 5.1 uses data. Internet apps will continue to drain the battery by keeping mobile data active unless they are forced to stop. On KitKat, apps stop doing so once they have completed their tasks. According to the user who reported it, this happens on Android M, as well. He or she also adds that the issue has been in the Android Issue Tracker since April, but Google has given it low priority.
A project member responded to the post with this:
Hi,
Thank you for reporting this issue. We have passed this on to the development team and will update this issue with more information as it becomes available.Status: Acknowledged
Owner: dnaga…@google.com
Labels: Defect-22287469
Personally, I’ve experienced this since my LG G3 updated to Lollipop some time ago. Battery life indeed was worse, as the personal anecdotes I had read had mentioned.
Still, Google realizes this complication, and hopefully, this means that Google will raise its priority and work to fix it, especially as Lollipop (and later, Android M) becomes the most used flavor of Android.
The post Google finally acknowledges the Lollipop battery drain associated with mobile radios appeared first on AndroidGuys.
Google will finally add iPhone-like visual voicemail to Android
Android users on select networks will soon get native “visual voicemail,” a feature that iPhone users have enjoyed since forever. In case you’re wondering, that’s a way of checking and deleting voice mails via an app, rather than having to call a carrier number and go through them one by one. The feature was spied by Android Police on a support ticket for the upcoming Android M release and via Google+ user Danny Hollis. Hollis showed a screen cap of the new interface (below), and said it’s now implemented for T-Mobile in a preview build.
The only problem with the new feature is that it won’t work unless carriers support it, and for now, the only two that do are T-Mobile and Orange in France. Hollis also mentioned that “voicemail will not load on WiFi. Only on mobile data,” so you won’t get the service unless you have a cell signal. The support ticket revealed native voicemail-to-text transcriptions as well, but it’ll reportedly require carrier support, and none are doing so for now. That said, the app is still in a basic state, and features like transcription may be available when Android M arrives in the fall.

Filed under: Cellphones, Google
Via: Android Police
Source: Google (Android Preview)
Android M will have native visual voicemail support
According to a report from Android Police, Android M will finally bring visual voicemail to Android. Carriers will have to implement support for Google’s service in order for it to work. French carrier Orange and T-Mobile US are already planned to include support in the final Android M release.
The Android dialer now has a tab for voicemail and shows all available messages for playback. The visual voicemail features works for T-mobile at the moment and hopefully, more carriers will eventually be supported. Visual voicemail does make it a lot easier to manage and listen to your voicemails, and having this feature directly implemented in your phone app (instead of having a carrier’s app to the same job) makes it even more convenient.

Source: Android Dev Preview Issue Tracker
Via: The Next Web
Come comment on this article: Android M will have native visual voicemail support
HTC’s Mo Versi confims HTC One M8 will be getting Android M update
style=”display:block”
data-ad-client=”ca-pub-8150504804865896″
data-ad-slot=”8461248232″
data-ad-format=”auto”>
(adsbygoogle = window.adsbygoogle || []).push();
Given HTC‘s recent financial troubles and a knack for being unpredictable, you could have been forgiven for thinking that the future Android M updates could be in doubt for HTC’s older devices. HTC One M8 owners, at least, can breathe a sigh of relief as HTC’s VP of Product Management, Mo Versi, confirmed on Twitter today that the HTC One M8 will be getting Android M update.
@sonsonnetwork @HTCUSA Thanks Pierrette! Appreciate your support. Yes, the M8 will receive the M OS update.
— Mo Versi (@moversi) June 30, 2015
Naturally, no timeframe was given, though we’re going to go out on a limb and guess HTC won’t be promising a 90 day window this time – but for many, the promise itself is more than enough. The next question of course is when Android M is going to be released, which according to last year’s release should be sometime around the end of October or early November. Given this timeline, and even assuming a 90 day delivery, HTC One M8 owners shouldn’t expect an update before February, and of course plus a few months if you have a carrier variant – we’d love to be wrong though.
What do you think about the HTC One M8 getting Android M? Let us know your thoughts in the comments below.
Source: Twitter via Phone Arena
The post HTC’s Mo Versi confims HTC One M8 will be getting Android M update appeared first on AndroidSPIN.
Diving into Android M: Visual voicemail makes its way to the dialer app

We’re well on our way into checking out all of the goodies the second Android M developer preview brings to the table, and so far quite a few notable features are present in the update. Google has (re)revamped the app drawer, given us the ability to edit what shows up in the status bar, and much more.
You can find all of the changes present in both Android M previews by following the link below, which I definitely recommend you do if you’re interested in checking out what may or may not make it into the next version of Android. Also, if you happen to own a Nexus 5, 6 or 9, you can download the newest dev preview by heading to this link.
Want to dive even deeper? Check out our full “Diving into M” series by clicking here.
.rvs_wrapper
width: 350px;
.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;
font-size: 24px !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 (min-width : 480px)
body #page .rvs_wrapper.cbc-latest-videos ul
width: 100% !important;
@media only screen and (max-width : 480px)
body #page .rvs_wrapper.cbc-latest-videos
width: 100%;
float: none !important;
overflow-x: auto;
overflow-y: hidden;
body #page .rvs_wrapper.cbc-latest-videos ul
overflow: auto;
max-height: none;
body .rvs_wrapper.cbc-latest-videos ul li
float: left !important;
clear: none !important;
The Preview 2 build of Android M introduces a handy little feature that will probably make most of our lives much easier. You see, smartphones are great at doing a lot of things, but they’re also really bad at doing some things. As it stands now, listening to a voicemail on your Android device can be quite annoying. You need to call your voicemail, listen to the prompts, listen to the voicemail message, most likely delete it, then go about your day. The second Android M dev preview aims to make this process easier through the dialer application.
Visual voicemail, a handy feature that’s been available through Google Voice and third party apps for some time, now has its own tab in the new preview. The tab is located on the right side of the dialer app. You’ll be able to see a list of your voicemails, each separated by individual cards. Expanding each card will give you play, pause, volume and trash icons, as well as shortcuts that can be used for texting or calling that person back right away.

Right now, Google has only added support for this feature for Orange in France. Folks on T-Mobile will be able to use the feature when the final preview is released, though some users are already reporting that it’s working for them.
Keep in mind that just about everything listed in this post may change by the time Android M is actually released to the general public. If you’re running the second M preview, how is it working for you? Have you tested out the visual voicemail feature yet? If so, be sure to let us know about your experiences in the comment section below!








