ZTE Makes the Notification Bell Optional in the Latest Axon 7 Update

ZTE released a very impressive smartphone this year that focused on build quality and audio performance while keeping the pricepoint very competitive. Many were wondering if they would be able to afford regular updates on the device and worried that it might only receive an update or two before being forgotten for the next phone release. However, as we've noted in a past article, selling a smartphone at a competitive price doesn't mean an OEM has to skimp out on the software updates.

We've watched as the ZTE Axon 7 and the OnePlus 3 have both received multiple software updates that include tweaks, improvements and new features since they've been released. Some will likely feel that ZTE and OnePlus can do better, but for a $400 smartphone with the build quality and specs they offer, we feel they are doing an impressive job in the update department. To this end, ZTE has just announced a new OTA update for the Axon 7 that brings some improvements and a highly requested feature to the phone.

The upcoming OTA update for the Axon 7 will be labeled A2017U Build 29 (MR3) and it comes to customers a little less than a month and a half since ZTE's previous OTA update. The company says this update should reach all Axon 7 devices before the end of tonight, and to be sure to manually check for the update if you haven't received the notification alert about it yet.

One big gripe that many people had with the Axon 7 was that you had to tap a notification bell on the lock screen just to see your notifications. Thankfully, this new update makes that feature completely optional and is a highly welcomed change to the software. ZTE tells us this OTA update also comes with the following changes:

• New application management policy to enhance battery life
• Optimized video camera focus on moving objects
• Resolved .FLAC file playback issue
• Visual Voicemail optimized for dual SIM
• Updated fix for Mute Call issue
• Other general enhancements

Source: ZTE

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

Samsung is Investing in Bezel-less, Edge-to-Edge Screen Technology

While some companies, including Samsung, are investing in foldable display technology, others are opting for a full screen display product. We recently watched Xiaomi make headlines with their Mi MIX concept phone. A smartphone that reportedly sports a 91.3% screen-to-body ratio. This type of technology is still in its infancy, and has already shown to be very fragile compared to smartphones with a bit of a bezel.

However, it seems like Xiaomi isn't the only company who wants to impress the world with a bezel-less, edge-to-edge display. Last week, Samsung was at the iMiD 2016 display exhibition in Seoul and a few of their engineers talked about the future of Samsung Display. The company would not confirm whether or not the upcoming Galaxy S8 would feature this type of tech, but Park Won-sang, a principal engineer at Samsung Display, did confirm the company was investing a considerable amount of money and manpower into the technology.

Won-sang said their goal is to hit above 90% in the screen-to-body ratio department. It's unknown if they will be able to topple Xiaomi's new Mi MIX smartphone, so we'll just have to wait and see what Samsung can produce. He did confirm that Samsung Display is targeting to roll out these types of displays sometime next year though. However, he did not give us a time frame for a release date or specifics on which phone Samsung would use it in.

Won-sang said their ultimate goal is to have something with a 99% screen-to-body ratio. He showed off some concept images during his presentation that showed a phone that looked similar to the Galaxy S7 Edge, and we were told that the display technology would allow for almost all sensors to be embedded under the display itself. Other than being impressive to hold and use, Samsung believes this would also help to improve immersion when used in a Gear VR type headset.

Source: The Investor

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

It’s still possible to enable the AOSP Lock Screen on HTC Devices

Over the years, the lock screen has evolved with the changing design language of Google's Android. Starting with Android 5.0 Lollipop, the lock screen developed a Material Design flavor and implemented rich notification support. But apart from Motorola, OnePlus, and a couple of other outliers, most OEMs have opted to use their own lock screen implementation in lieu of the AOSP one. HTC is no exception in that regard. However, a peculiarity with the way HTC chose to implement their lock screen has allowed end-users to disable the stock HTC lock screen. Years later, it appears that the trick still works. Here's how it works and how it's done.

---

Disable the HTC Lockscreen using ADB

Usually, the lock screen is contained within the framework-res.apk, which is pre-installed as a system app and cannot be modified without root. Furthermore, disabling the app would prove to be a very, very bad idea as it would almost certainly result in a bootloop. HTC, though, does not actually pack their custom lock screen within framework-res, and instead pre-installs their lock screen app on all of their devices. Fortunately for us, this means we can disable this package without causing any issues with the system!

To do so, you'll need to connect to your device via ADB and send a simple command. First, make sure you have the ADB binaries downloaded onto your computer. We recommend grabbing Minimal ADB & Fastboot from our forums. Next, install the necessary HTC drivers for your device. Finally, once you've got ADB and the drivers set up, open a command prompt and issue the following commands:

  adb shell  pm hide com.htc.lockscreen  

If the command returns 'hidden: true' then it was successful in hiding the lock screen package. Now, simply reboot your device and you should see the stock AOSP lock screen! As a bonus, by re-enabling the AOSP lock screen, you will apparently gain the ability to double tap the power button to launch the camera.

We hope you enjoy this mini customization tutorial. Do note that we've personally tested this on an unrooted HTC 10 with the September security patches, but this should work on most other HTC devices. Try it out for yourself! If we come across anything we think you might find interesting, we'll be sure to let you guys know in a future article.

 

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

Honor 8 Root TWRP and Xposed

In this video, TK show us how to root the FRD-L04 and the FRD-L09 versions of the Honor 8. To root, we will flash TWRP and install SuperSU.

Before we get started with the root tutorial, you will need to unlock the bootloader on your phone. See this video to learn how to unlock the bootloader on the Honor 8.

Requirements:

1. Unlocked Bootloader

2. Download TWRP and SuperSU

3. Make sure USB Debugging is turned on, in the developer's options.

4. Download and install the correct drivers and ADB tools.

5. Watch the video once and then watch it again to make sure you get the flow or the work.

Once you have setup the device with your PC for ADB and fastboot connections we are ready to start.

Installing TWRP

1. Connect your device to your PC and make sure to grant authentication to your PC over ADB. (You should be able to see your device when you type [ADB devices] in the Command Prompt)

2. Type [adb reboot bootloader] and wait for the device to reboot into fastboot mode

3. Type [fastboot devices] to confirm you have a connection to your device

4. Make sure to save the downloaded recovery .img in the same folder as your are running Adb/fastboot tools, and then type [fastboot flash recovery TWRP image.IMG] ( replace .img with the exact name of the downloaded file)

5. When complete reboot normally

6. When the device comes back up, open up ADB and type [adb reboot recovery]

7. Your device should reboot into TWRP

8. Do not change to "read/write" keep in read only mode and do a backup

9. Once backup is complete then enable "read/write" by going to "mount" and disabling the option for read only

Rooting the device

1. While connected in recovery mode transfer the Supersu2.78 stable to your device and install it. After installed, reboot

2. After rooting your device may restart 2 to 3 times. This is normal so just be patient.

3. System will reboot and you should have root. Test root access with your favorite root app ( I like XDA labs)

Xposed installation

1. Install the xposed installer 3.11 apk.

2. Reboot into recovery via [adb reboot recovery], or your favorite APM app on the play store

3. Install the version 86 sdk23 arm64 binaries zip and reboot

4. First boot will take about 6 minutes

5. After rebooting go back into recovery and do another backup now that Xposed is installed

6. Now you can start checking out modules. Do one at a time and always perform a backup before installing an Xposed module

If you followed the instructions carefully, you should be all set to go!

 

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

Google “Evaluating” Firmware Update to Add Fingerprint Gesture Support to Nexus 6P and 5X

The Google Pixel and the Google Pixel XL have been stealing the show in the latter half of 2016 so far. Google deciding to turn on the heat in the premium smartphone segment certainly surprised many users, as many expected Google to remain closer to the Nexus roots. But the Pixels have proved to be different enough to earn their branding.

There is one thing that is similar in the Google Pixel duo and the Nexus duo released last year — the fingerprint scanner. Specifically, the sensor used in the Pixel and Pixel XL for fingerprint scans is the OneTouch FPC1025, which is the same as the sensor used in the LG Nexus 5X and the Huawei Nexus 6P. While the fingerprint response on all the four phones come very close competitively, there is one key factor which differentiates the Pixel and Pixel XL from the Nexus 6P and the Nexus 5X despite this particular hardware similarity: support for fingerprint gestures.

On the Pixels, a quick swipe down on the rear-placed fingerprint scanner pulls down the notification shade. While it might not seem very groundbreaking (after all, the Huawei Honor 5X had it before the Pixel on the same hardware sensor), the Pixel exclusivity of what appears to be a software addition on the surface angered a lot of Nexus users. Perhaps rightfully so, as the Nexus 6P and the Nexus 5X are still under support from Google, and locking them out of features which they would otherwise be capable of seems like the kind of move expected from other OEMs, and not from Google.

Kernel developer at Google for Pixel and Nexus device, Nick Desaulniers, commented on Reddit on the issue:

Bullhead [Nexus 5X] and angler [Nexus 6P] use similar hardware but older versions of firmware that don't have gesture support. Updating the firmware used and HAL and some other stuff will take some effort. Doable.

Developer Advocate at Google, Ian Lake, spoke to AndroidPolice on the issue, commenting:

Same hardware doesn't mean same capabilities, alas.

What this meant that although the hardware was the same, the firmware used on the newer Pixels allowed them to build on fingerprint gesture support. But since this was a firmware update and not hardware limitation, this does mean that there is scope of bringing in newer functionality via an upcoming update.

Google did not deny such a possibility. In a statement given to AndroidPolice, Google's PR machinery commented that Google is "evaluating" a firmware update for the Nexus 5X and 6P to add support for the fingerprint scanner gestures. To be fair and realistic, they did not confirm that gesture support is coming to the devices either. But their acknowledgement of the issue and keeping an open mind towards bringing it to older hardware gives us hope. Perhaps all is not lost for Nexus, after all.

If you are looking to add fingerprint gestures to your Nexus 6P and the Nexus 5X, but can't really wait for Google to come to a decision, you can try out Fingerprint Quick Action app to emulate the same functionality on your device.

What are your thoughts on the issue? Would you like to see Fingerprint Sensor Gesture Support being added to Android as a stock feature? Let us know in the comments below!

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

Motorola Moto MAXX/Droid Turbo Gets Unofficial Android 7.0 Nougat Update

Owners of the Motorola Moto MAXX/Turbo/Verizon Droid Turbo can now enjoy the taste of Android 7.0 Nougat thanks to crDroid Android ROM. Check it out!

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

First Google Tango Phone, the Lenovo Phab 2 Pro, Now Available in the USA for $499

A few months ago, Lenovo introduced its first smartphone with Google's Tango, the Lenovo Phab 2 Pro. This device was to be the first smartphone developed to showcase the technological innovations that grew out of Google's ambitious augmented reality (AR) project, formerly known as Project Tango. The Phab 2 Pro was scheduled to go on sale in mid September 2016, but after a little delay, it's finally here!

Even without all of its Tango tricks, the Lenovo Phab 2 Pro sports some fairly decent specifications for its price. The front is dominated by a large 6.4″ QHD IPS display — a size necessary because the phone needs to incorporate a lot of additional sensors, though we might see smaller devices once more companies decide to invest in Tango. The Phab 2 Pro is powered by the Qualcomm Snapdragon 652 SoC, which might disappoint those of you expecting the latest and greatest Snapdragon 821, but the 652 is respectable in its own right. Couple that with 4GBs of RAM, 64GBs of internal storage and expandability up to 256GB via a microSD card slot through the hybrid dual-SIM tray, and you've got a pretty beefy device. Furthermore, the battery capacity of 4,050 mAh is certainly welcome keeping in mind the strain the display, Tango-related sensors, and the cameras will place on the device.

 

The main camera on the rear is a 16MP shooter with PDAF. Additional sensors on the back help it with motion tracking, depth sensing and 3D mapping. The front is a 8MP shooter with f/2.2 aperture.

The Lenovo Phab 2 Pro is the first device to support Google Tango, but more devices are expected in 2017 that will help build up the AR ecosystem. It is the first commercially available Tango device for the average consumer though, and with it being sold at an affordable price, the Phab 2 Pro seems primed for success. Assuming, of course, that the device is decently marketed to consumers.

So what about Tango makes this device so special? First of all, Phab 2 Pro utilizes its dual rear camera sensors along with a bunch of other sensors to create a 3D map of our physical surroundings. This 3D mapping is then displayed on the screen, supplemented by other elements and points of interaction that is filled in via software – thus creating an Augmented Reality experience on a smartphone. The uses of AR on a smartphone are limited as of now, albeit the possibilities are mostly left up to the imagination of developers. Currently, only a limited number of apps and games make use of the AR capabilities of the Lenovo Phab 2 Pro. Though with the crazy success of Pokémon GO, we can expect to see a lot more interest in AR now that the technology will be more widely available.

Google currently operates both Google Tango, its platform for Augmented Reality, and Google Daydream, its platform for Virtual Reality, under separate organizational heads. There is a chance that we might see a merge down the line, with phones coming in that might support both Tango and Daydream out of the box.

The Lenovo Phab 2 Pro is available in the USA from today from Lenovo's official webstore or in select Lowe's retail stores. The phone will cost you $499.99, and shipping is expected to be within 4-5 weeks. At launch right now, only the Gunmetal Grey color is available, with the Champagne Gold color variant "coming soon".

---

Would you be purchasing the Lenovo Phab 2 Pro? Would you like to see other smartphones with Google Tango? Let us know in the comments below!

Check out XDA's Lenovo Phab 2 Pro Forums!

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