Friday, December 23, 2016

DxOMark Reviews the Dual Cameras of the LG V20

As we get to the end of the year, some review publications are starting to highlight some devices that they weren't able to get to upon release. Many have been waiting for DxOMark to review the dual camera system of the LG V20, and yesterday that review was officially published. The device earned a respectable overall score of an 85, which puts it right alongside the Huawei Mate 9 in their eyes.

DxOMark felt the sensors preserved a good amount of detail when the subject was in very bright light. They saw good noise reduction in low-light environments, and the autofocus was fast and generally accurate when they tested it. However, they found some irregularities with the focus, there was a slight pink colorcast when outside, and some highlights were overexposed in high-contrast scenes.

During the review, DxOMark felt the camera's video performance is where the LG V20 is weak. They gave its video performance an overall score of 82 as they saw some motion blur even all lighting conditions. There were slight autofocus oscillations visible in the preview, there was a visible focus drop during tracking, and limited dynamic range when shooting video in bright light. They did say it had good target exposure though, and appreciated the noise reduction in bright light and again they felt it preserved detail in bright light situations.

Overall, DxOMark was impressed with the camera of the LG V20, but felt a little let down since they ranked the LG G5 right above it with an overall score of an 86. If LG had just focused more on the video performance of the camera, then it would have received a higher score.

Source: DxOMark



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

SuperSU v2.79 SR1 is Available, Focuses on SELinux Changes for Nougat

Yesterday, Chainfire announced the first update after version 2.78 of SuperSU was made stable. As we've mentioned before, the SR updates are basically a different name for beta versions of SuperSU. The name change was put into place as an attempt at reducing the number of people trying to upload beta releases to non-Google Play app stores since it would continue to carry the same version number.

Most changes here are with SELinux on Android 7.x Nougat, although there are a lot of other changes with this new update. Chainfire says this version will now use it's own 'u:r:supersu:s0' context to run in. So instead of reusing the 'u:r:init:s0' context, this change can prevent a few conflicts from occurring. However, we're warned that this change could make some root applications (and even some firmwares entirely) to suddenly stop working.

SuperSU v2.79 SR1 no longer modifies file_contexts[.bin] as well. Chainfire noticed that this modification caused some issues on select firmwares. They've been unable to identify the reason for the conflict though, but noticed that the modifications were causing it. Some people reported that SuperSU was slow to grant root access to some applications on boot when a device had a bunch of application installed. This mainly happened with Nougat, and we're told it shouldn't be much of an issue anymore.

You can download the flashable zip for v2.79 SR1 right here, and we encourage you to check out the XDA forum thread for the beta version of SuperSU in case you run across any issues with the new version. The full changelog for this update can be found below.

  • Expand Samsung detection
  • GUI: reworked portions to work with 'supersu' context on 7.0+
  • GUI: fix binary update notice when superuser disabled by user in some cases
  • su: reworked portions to work with 'supersu' context on 7.0+
  • su/GUI: improve responsiveness when device busy on 7.0+
  • sukernel: fix cpio restore failure with very short filenames
  • sukernel: no longer patches file_contexts(.bin)
  • sukernel: revert force seclabel (no longer needed with 'supersu' context)
  • supolicy: add "create", "auditallow", "auditdeny" policy commands
  • supolicy: support "*" for permission/range parameter of "allow", "deny", "auditallow", "auditdeny", "allowxperm" policy commands
  • supolicy: –live/–file no longer apply default patches if custom patches are supplied
  • supolicy: –sdk=X option added (required for 7.0+)
  • supolicy: reworked all SELinux rules for 7.0+, run as 'supersu' context
  • ZIP: Separate slotselect and system_root logic
  • ZIP: Adjust system/system_root device and mount-point detection
  • ZIP: Fix minor errors in documentation
  • ZIP/frp: Explicitly label /su

Source: +Chainfire



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

Thursday, December 22, 2016

2016 in Review: What was the Best Flagship Smartphone of 2016?

As we enter the final days of the year, it's time to get your opinion on all the events, news, releases and controversies that we witnessed so far in 2016.

This year saw some great releases by OEMs big and small. Some smartphones took a gamble to differentiate themselves from the crowd, while some played it safe and improved on conventional expectations.

The competition was fierce, but a winner has to be chosen. So, today's question to you is,

What was the best Flagship smartphone released in 2016? Why does this smartphone deserve to be called the very best? What features attracted your interest towards this phone? What were your needs and expectations, and how were they fulfilled?

Let us know in the comments below!



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

Google will launch two flagship smartwatches with Android Wear 2.0 next year

In an exclusive interview with The Verge, Jeff Chang, product manager of Android Wear at Google, states that the company will launch two new flagship smartwatches in the first quarter of 2017. Furthermore, these two smartwatches will be the first devices to run Android Wear 2.0.

We learned of the existence of these two smartwatches earlier this year and even caught a glimpse of what the smartwatches could look like, but this is the first time we have official confirmation from Google. We now also have some additional information about the smartwatches thanks to Mr. Chang.

According to Mr. Chang, these new devices will not carry the Pixel branding, but will instead be OEM branded. What this tells us is that these two Google devices are going to made in close conjunction with their OEM partners, much like the now-defunct Nexus program. Mr. Chang reports that Google collaborated with the manufacturer on both the hardware design and software integration for the two smartwatches, and that their partners have had prior experience in making Android Wear smartwatches.


Android Wear 2.0 Release Timeline

After the release of these two smartwatches, Mr. Chang states that older Android Wear smartwatches will begin receiving their updates to Android Wear 2.0. As we've covered previously, the update to Android Wear 2.0 brings a plethora of changes including Google Assistant integration, a standalone app store, in-app billing, better two-factor authentication sign-in support, new gestures, and more. Although not every existing Android Wear smartwatch will be upgraded, most recent models are expected to make the cut. Mr. Chang states that although certain features such as Android Pay require NFC, the company will not make NFC a requirement to receive Android Wear 2.0.


Devices Expected to Receive Android Wear 2.0. Via The Verge.

  • Moto 360 Gen 2
  • Moto 360 Sport
  • LG Watch Urbane 2nd Edition LTE
  • LG Watch Urbane
  • LG G Watch R
  • Polar M600
  • Casio Smart Outdoor Watch
  • Nixon Mission
  • Tag Heuer Connected
  • Fossil Q Wander
  • Fossil Q Marshal
  • Fossil Q Founder
  • Michael Kors Access Bradshaw Smartwatch
  • Michael Kors Access Dylan Smartwatch
  • Huawei Watch
  • Huawei Watch Ladies
  • Asus ZenWatch 2
  • Asus ZenWatch 3

As we approach January, Google will release the fifth and final Android Wear 2.0 Developer Preview, which should include support for Android Pay and Google Assistant. In addition, the final Developer Preview will finally bring support for iOS, which has been confirmed to be compatible with the Android Pay feature.

In the future, Mr. Chang teases that several OEMs are planning on releasing their own Android Wear 2.0 devices, with some announcing them at CES next month. Given the news this year that the likes of Motorola, LG, and Huawei passed on releasing an upgraded model of their smartwatch, we may see some of these OEMs release a new smartwatch sporting Android Wear 2.0.


Source: The Verge



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

Best Apps of 2016

Google has has released their picks for the best apps of 2016. This list features several different categories containing the best apps in each category. For this video, I'll take a look at the best app from each section. So check out the video to see the best apps of 2016 in action.

image

Best self improvement app: Memrise

image-1

Most beautiful app: Adobe Illustrator Draw

image-2

Most share-worthy app: Adobe Photoshop Fix

image-3

Best Local App: Letgo

image-4

Most entertaining app: Violin: Magical Bow

image-5

Best app of 2016: Prisma

 

2016 was a great year for new and exciting apps from the Play store.. If you don't see your favorite app on this list, let us know in the comments what it is!



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

Guide for Full ADB Root, System RW, and DM-Verity Off on the Sprint LG G5

XDA Senior Member Honestly Annoying has created a guide to walk you through getting ADB Root, System RW & DM Verity Off on the Sprint LG G5. The process can be done on Windows, macOS or Linux, but it will only work on the ZV4 build.



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

OnePlus 2 OTA Update Brings OxygenOS 3.5.5 to the Device

OnePlus has announced they are starting to roll out a new OTA update to the OnePlus 2. This new update will bring your device up to version 3.5.5 of OxygenOS, and it comes with a lot of new features and changes. The company warns users that updating to 3.5.5 can cause issues with things like WiFi and network connectivity, as well as the fingerprint sensor if the person tries to downgrade back to version 3.1.0.

It is possible to downgrade to 3.1.0 without issue, but you'll need to use a special 3.1.0 downgrading version and flashing tool. Doing this will wipe all of the data from your phone. The main changes with this update are the new features that OnePlus has added. We're told that this update enables VoLTE functionality for select carriers but doesn't go into detail about which carriers and that it also comes with an App Lock feature.

They've added a Battery Saving Mode, a Gaming Mode, and put in some new options for the Alert Slider within the settings. The update comes with a redesigned volume adjustment bar, adds in some optimizations for their Shelf feature, and comes with an updated user interface for the clock application. We're also told that the Clock, Calculator, and Messages applications will be replaced with stock OnePlus apps unless you have updated the corresponding Google apps.

If this is the case for you, and you want to continue using Google's apps, then you can download them from the Play Store. This new OTA update brings new UI changes to OxygenOS as a whole, they've increased the stability, fixed a number of bugs, and included December's security patches too. OnePlus also warns that this update will reset "many" of the phone's settings (like device name, ring tones, accent colors, etc).

So you'll want to go back through your settings and adjust these options if you notice something is different from before.

Source: OnePlus



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