LightBlog

lundi 21 novembre 2016

Verizon Begins Rolling Out Nougat to the Moto Z Droid & Moto Z Droid Force

Many were wondering how Lenovo would change the way Motorola handles their smartphone business once the acquisition had been completed. Lenovo said they had plants to utilize Motorola connections to enter the US smartphone market, while at the same time introducing Motorola smartphones to countries they have never been sold in.

This all sounds great, but there were still some who were paranoid about the whole situation.

Some were worried that Lenovo would force Motorola to start using their own custom UI skin, and there were others who felt Motorola wouldn't be able to push out updates as quickly as they had in the past. So far, the fans of stock Android have had nothing to fear, but the update cycle has been a bit of a mixed bag. It seemed like the Droid Turbo 2 wasn't ever going to receive the update to Marshmallow, and this led to many thinking the same would happen to the Nougat update for the Moto Z Droid and the Moto Z Droid Force.

Thankfully that isn't the case, as multiple people are starting to see their Motorola and Verizon flagship updated to Android 7.0 Nougat. The build number for the new Moto Z Droid update is NCL25.86-11, the install time for the update is said to be up to 20 minutes, and currently weighs in at 1.58GB in size. This OTA update from Verizon and Motorola includes the typical Nougat features (like split-screen mode and quick app switching), along with the November 1st, 2016 Android security patches.

This new update also brings official support for Google's Daydream VR platform as well. Besides the Pixel and Pixel XL, the Axon 7, Moto Z Droid and Moto Z Droid Force are currently the only smartphones with support for Daydream. We're also seeing this update include support for the Camera2 API as well. So certain applications will be able to manually control various aspects of the camera hardware.

Source: Android Police



from xda-developers http://ift.tt/2fUAB8c
via IFTTT

Photos Reveal an Unannounced Xiaomi Mi MIX in White

At the end of last month, Xiaomi held a launch event for a trio of new products. At this event, they announced the Xiaomi Mi Note 2, Mi VR, and a concept phone that they are calling the Xiaomi Mi MIX. While many people were excited to see the Mi Note 2 and the Mi VR announced, it was actually the Mi MIX smartphone that stole the show.

Since launch, a number of people have been able to get their hands on the device and some are calling it "the smartphone of the future".

What made the Mi MIX stand out from the other products Xiaomi launched, as well as most of the smartphone market today, is the way they designed the bezels. Now, the design of the Xiaomi Mi MIX isn't entirely new. Sharp has been tinkering with this type of design in smartphones since late 2014 (most notably with the Sharp Aquos Crystal). We even saw Dell use a similar design (albeit with slightly bigger top and side bezels) with their Venue 8 7000 tablet.

Xiaomi has only officially announced one version of this Mi MIX concept phone. The company has even said they are unable to do a wider release for it because the ceramic body limits them to producing 10,000 units per month. Still, that hasn't stopped the rumor mill from spinning around this highly sought after smartphone. Last week there were rumors about a mini variant spotted in some low quality photos, but now there could also be a new color in the works.

4 photos show what could be a white color variant of the Xiaomi Mi MIX. Thanks to the newly leaked photos, we get a good look at the front, back and left side of the phone. As with all unannounced devices, this might not ever see an official release, but it's nice to see what Xiaomi is working on behind the scenes.

mimix-white-04 mi-mix-white-03 mi-mix-white-02 mimix-white-05

Source: GizmoChina



from xda-developers http://ift.tt/2geqUC8
via IFTTT

ZTE Announces the Axon 7 Enhanced with Force Touch, 6GB RAM and 128GB Storage

Competing very strongly in the affordable flagship category are the OnePlus 3 and the ZTE Axon 7. But the matchup here seems to be changing, with OnePlus discontinuing sales of the OnePlus 3 and producing the OnePlus 3T instead. ZTE has decided that they too should shake things up a little.  And so we meet the new ZTE Axon 7 Enhanced.

As the name would imply, the Axon 7 Enhanced is everything that the Axon 7 was, and then some. This new Axon 7 flagship inherits the metallic unibody construction along with the iconic front speaker setup. The display specs remain the same with the screen being 5.5″ AMOLED QHD display, but you now get added functionality in the form of Force Touch opening up its own use cases.

axon-7-gold

On the inside, the Axon 7 Enhanced continues on using the Qualcomm Snapdragon 820 SoC, and since the 820 continues to be a very solid performer, there is not a whole lot to complain about here. For RAM and storage, the Axon 7 Enhanced bumps up the spec to 6GB of RAM and 128GB of internal storage from the previous 4GB + 64GB combo. You can still make use of the SIM2 slot for microSD expansion to add another 128GB of storage. The rest of the device is the same as the Axon 7, including the 20MP rear camera, the premium HiFi Audio experience, the USB 3.0 Type-C 1.0 connector and the non-removable 3,250 mAh battery with Quick Charge 3.0 support. Unfortunately, the phone still ships with just Android 6.0.1 Marshmallow, and with ZTE's skin on top.

While the ZTE Axon 7 retails for $399.98, the Axon 7 Enhanced will retail for $499.98. No word has been given for availability, but we can expect it to go on sale soon. Further, we haven't learned whether the original Axon 7 and Axon 7 mini are being discontinued — we hope not!

What are your thoughts on the ZTE Axon 7 Enhanced? Do you agree with the pricing strategy followed by ZTE? Let us know in the comments below!



from xda-developers http://ift.tt/2g9mriU
via IFTTT

dimanche 20 novembre 2016

Create a Context Aware Fingerprint Reader in Tasker

Fingerprint readers are fairly limited in their default state. Besides the obvious ability to unlock the phone or authorize some payments, there isn't much else you can do with the fingerprint reader on most Android phones. The feature always felt like a missed opportunity – until now!


Tasker-based, Context Aware Fingerprint Reader

Creating a customized fingerprint reader within Tasker is a fairly simple project. Tasker will  assign  multiple functionalities to the fingerprint reader depending on what you are doing or where you're located. In this example, I will show you how to instantly cast the current website to the big screen (in this case, my PC).  This way you will be able to add additional functions to the reader depending on windows opened or your location. Your imagination is your only limit.

How it works

Bear in mind that the Fingerprint Scanner Tools app is new and under active development. The Tasker support is currently limited to only executing tasks, however, that's all we're going to need. We are going to use variables within Tasker to assign more than one profile to the fingerprint scanner. When the fingerprint  is activated, Tasker will check what else you have been doing (or where you are) and will execute the correct profile accordingly.

Fingerprint scan

screenshot_20161120-173936 screenshot_20161120-173946

We need to get the reader to act as a universal trigger for our conditions. We will need to create a task, Scanned Finger, that will trigger other profiles for us. We can link this to a variable %FingerScanned. When the Fingerprint Scanner Tools app recognizes a fingerprint, it will launch our Scanned Finger task to temporarily set the value of %FingerScanned from 0 to 1 for 2 seconds. 2 seconds should be sufficient time for our other Tasker profiles to react to the variable change and respond to it. If you have any issues with Tasker responding to the variable change, try increasing the wait action to 3 seconds or longer. Open the Fingerprint scanner tools and assign this task. Next, we will create different profiles that are launched depending on the current context – whether or not a certain app is opened, what your current location is, etc.

Cast the current Chrome window

screenshot_20161120-173955 screenshot_20161120-175131

In this example, we will demonstrate how to cast the currently opened tab in Chrome. This profile will be triggered when the value is %FingerScanned is set to 1 (as per the task created previously) AND Tasker detects that the currently opened app is the Chrome browser. This requires you to enable the Accessibility service for Tasker, otherwise Tasker will not be able to detect when Chrome is opened. Furthermore, we will make use of AutoInput as well as Join by XDA Junior Member joaomgcd due to the extensive integration with Tasker.

First up, you'll need to create a profile with two contexts: first, a State context that is activated when %FingerScanned = 1; second, an App context that is activated when Chrome is opened. Next, you'll need to replicate the task as shown in the screenshot above, or as reproduced below. Once you're done, this task as set up will query the currently opened URL in Chrome and push it to your PC using Join. You can prompt a device selection if you wish, but for super fast sharing, I designated a single device for doing so.

I'm using the AutoInput UI Query to get the value of the URL in the browser. In most cases, the web address will start with www/http(s) or a combination thereof. To capture the URL we will need the following regex:

  ((?<=http:\/\/|https:\/\/|https:\/\/www.|http:\/\/www.|www.))?.*  

If you have any issues configuring the Query – use Variable Setup to return to Chrome and select the address bar. AutoInput will then help set up the URL capture automatically. I have set up a custom variable %address which will contain the URL address from the currently opened Chrome tab.

screenshot_20161120-175136 screenshot_20161120-175141

Before we can push the page to the computer, we need to check that the URL is formatted properly. Pushing a URL starting with www will not open the website automatically in your desktop browser. The easiest way to ensure we are sending a correctly formatted URL is to run a search/replace action. The default value for the %prefix variable will be "http://". We need this if a website does not support the https protocol. We will be looking for either http or https in the URL, and if %prefix is found it is set in the Join URL push. Look for https:// and select replace. Do not enter anything in the replace with field as we just want this to be removed from our address do the same for the http://. The last action is the Join Push.  Go to the URL and enter %prefix%address . This way the URL will be pushed correctly to  the PC and will open the website automatically.

If you're worried about security, many websites will automatically redirect you to their secure version if it exists, but if not you can use the HTTPS Everywhere extension to handle that for you.


Conclusion

As you can see, by assigning Fingerprint Scanner Tool's Tasker action to changing variables, we can assign multiple actions despite the limitations of a single Tasker task. I have reached out to the developer of Fingerprint Scanner Tools, Daniel Huber, and he states that more Tasker functionality is planned for the future. Now that you know how to use the fingerprint reader without bonding it to a single task, you can customize what contexts and what actions should be launched when a fingerprint is recognized.

Perhaps you can cast a YouTube  video with a single tap (no Chromecast needed). I might show this off in my next tutorial? If you want to see this, and other Tasker scripts, let us know your thoughts below!


Download/Import

As always, we will be providing ways to either download or manually import the work that we show off in these Tasker tutorials. You will have two options to add these scripts to your Tasker set-up.

First, you can download the entire Project by following the download link below. After downloading the Project XML file, you can import it by opening up Tasker then long-pressing on the Home icon at the bottom left. This will bring up the Tasker Project menu, which will allow you to import Projects located on the internal storage.

Download the Context Aware Fingerprint Reader Project

Alternatively, you can use the descriptions of the Profile/Task as contained in the two tabs below to guide you through the process of recreating this script on your own. We recommend this route if you want to learn how to get better at Tasker, so that you can make customizations or improvements to the script on your own.

  Profile: Cast Chrome          Application: Chrome          State: Variable Value [ %FingerScanned eq 1 ]  Enter: Chrome          A1: AutoInput UI Query [ Configuration:Only Visible: true  Only Clickable: false  App Package: com.android.chrome  Check Screen State: false  Text: ((?<=http:\/\/|https:\/\/|https:\/\/www.|http:\/\/www.|www.))?.*  Regex: true  Variables: address Timeout (Seconds):20 ]           A2: Variable Set [ Name:%prefix To:http:// Do Maths:Off Append:Off ]           A3: Variable Search Replace [ Variable:%address Search:https:// Ignore Case:On Multi-Line:Off One Match Only:On Store Matches In:%prefix Replace Matches:On Replace With: ]           A4: Variable Search Replace [ Variable:%address Search:http:// Ignore Case:On Multi-Line:Off One Match Only:On Store Matches In:%prefix Replace Matches:On Replace With: ]           A5: Join Send Push [ Configuration:Device: Chrome@Home              Url: %prefix%address Timeout (Seconds):60 ]  

  Scanned Finger
A1: Variable Set [ Name:%FingerScanned To:1 Do Maths:Off Append:Off ]
A2: Wait [ MS:0 Seconds:2 Minutes:0 Hours:0 Days:0 ]
A3: Variable Set [ Name:%FingerScanned To:0 Do Maths:Off Append:Off ]

Requirements:
Android version: 6.0+
Apps: Join (or AutoRemote), Fingerprint scanner tools (Tasker support needs to be unlocked)
Plugin: AutoInput
Hardware: Fingerprint Reader



from xda-developers http://ift.tt/2fhRMCe
via IFTTT

Life of an Android Enthusiast in a Third World Country

In this video, Rawad tells us what it's like to be an Android enthusiast while living in Lebanon. When you have unreliable power, slow internet speeds, and no access to the latest phones, suddenly your daily Android-related activities are very different. What happens when you're on a nightlies ROM? How do you charge your phone during one of the frequent power outages?

Check out the video to see Rawad's take on things. And if you have any other questions about the topic, let him know in the comments section!



from xda-developers http://ift.tt/2g7FDO3
via IFTTT

samedi 19 novembre 2016

Which Current or Upcoming Processor Would You Want in Your 2017 Device?

Details regarding new processors are starting to surface as the Snapdragon 835 became official and it'll be built on Samsung's 10nm process. Not to long ago, we also saw the release of the Huawei Mate 9 with the Kirin 960, which we tested in preparation for our review, and news of a 10nm MediaTek chip.

We also hear reports of Xiaomi building its own custom silicon, we know that there is a better Exynos processor coming in the future, and it's even rumored Google might make its own chip at some point as well. Given what we know about all of these different options, the strengths of each producer and the track records of each line-up, we ask you:

Which processor would you want on your next smartphone, and why? Do you trust the company making it and its track record? Are you looking for specific features, or just raw performance? What about battery efficiency and fast charging solutions? Would you go for a developer-unfriendly chipset if it meant better speed and battery life?

Let us know in the comments below!



from xda-developers http://ift.tt/2fGdoIW
via IFTTT

CM13 Beta ROM on the Honor 8

Today we are going to look at a CM13 beta ROM on the Honor 8. There are a few things you'll need to get ready to flash this ROM. If you haven't yet, check out these videos first:

How to Unlock Bootloader on Honor 8 

How to Root Honor 8 and Install TWRP and Xposed 

Check out the official thread to follow development on this particular ROM. As noted in the video, make sure you have the updated TWRP from the XDA thread, before trying to flash this ROM.

Check out the video to see TK give a quick tour of the ROM and go over some of the stuff that works and some of the stuff that doesn't work.



from xda-developers http://ift.tt/2gvhAxB
via IFTTT