Monday, September 30, 2019

Remap the S Pen button on the Samsung Galaxy Note 10 with sideActions

Android users love to stretch the functionality of every aspect of their phones. This is why the modding community is so active. People want complete control over their device. If there’s a button on a phone programmed to do something, we want it to do something else. The developer of the popular bxActions app is back with a similar tool for the Galaxy Note 10 and the S Pen.

Galaxy Note 10 Forums ||| Galaxy Note 10+ Forums

sideActions is an app that allows Galaxy Note 10 (and 10+) users to remap the power button on the S Pen. The developer says this is the first time the power button on the S Pen has ever been remapped. The power button can be mapped to any action or app you like. It can even be used to navigate the phone (map the button to the Back button).

Setting up sideActions is pretty easy. All you need to do is hook up the Galaxy Note 10 to a computer and run a simple ADB command. After that, it can be remapped to your heart’s content. Download the app for free from the Play Store below. Here’s a list of features and actions:

FEATURES:

  • Double and long press supported!
  • Remap the Power Button / side key on Galaxy Note 10!
  • Remap the S Pen button!
  • Launch Google Assistant with the Power Button
  • Remap the Volume buttons!
  • Per app remapping
  • Turn on the flashlight with the Power Button
  • Disable the Power Button
  • Skip tracks with the volume buttons
  • High performance! No lags!
  • No annoying ads

ACTIONS:

  • Turn on flashlight
  • Take a screenshot
  • Mute phone
  • Answer phone calls
  • Launch Google Assistant
  • Launch camera or any other app
  • Switch to last app
  • Disable the Power Button
  • 35+ actions
Galaxy Note 10 remap S Pen button

Power Button Remapper for Note10 - sideActions (Free+, Google Play) →

If you have any feedback to offer, you can leave a comment on the support thread linked below.

Read more in the Galaxy Note 10 Forum thread

The post Remap the S Pen button on the Samsung Galaxy Note 10 with sideActions appeared first on xda-developers.

Google confirms Car Crash Detection is coming to Pixel smartphones

Back in May, we discovered changes to the Emergency Information app that hinted at Google adding automatic car crash detection to Pixel smartphones. We haven’t heard any new information about this feature since then, and it hasn’t appeared in any of the numerous Pixel 4 leaks this past month. However, Google updated the built-in Emergency Information app on Pixel smartphones today, rebranding it as Personal Safety. The Play Store’s app description confirms that car crash detection will be made available for Pixel devices in the United States.

Here’s the updated description on Google Play:

Personal Safety is an app for Pixel phones that helps you stay safe and connected to first responders and your emergency contacts.

  • If your phone detects that you’ve been in a car crash, it can help reach 911 for you. Car crash detection is available in the United States.
  • Enter medical information and choose your emergency contacts. By default, this info is available when your phone is locked to help first responders.
  • With emergency sharing, you can quickly share a short message and your current location with all of your emergency contacts.

Google says that your phone will automatically dial 911 if it detects you’re in a car crash, using your location and sensor readings from the accelerometer and microphone to detect when a car crash has occurred. When your phone thinks you’re in a car crash, it’ll vibrate and play a sound at maximum volume, asking you if you need help. If you don’t respond, Pixel will automatically dial 911 and provide your location.

Another new feature mentioned in the changelog is the ability to quickly share your emergency status with your contacts. You can send your location and a custom message about your current situation to multiple contacts.

I downloaded the update on my Pixel 2 XL, but I don’t see the car crash detection or emergency status sharing feature shown in the screenshots submitted to the Play Store. I also don’t see an announcement on the official Google blog, but it’s possible that Google is preparing an announcement shortly. We’ll be analyzing this APK to find out as much as we can about the update because there’s no real way to actually test the car crash detection feature ourselves.

I did notice that the app has been slightly redesigned and now includes settings to show or hide your emergency info from the lock screen. Here are some screenshots:

Google recently announced another U.S.-only emergency feature that lets you send important information to emergency responders without having to actually talk. We’re hoping the company makes these features available for Pixel owners in other countries, but Google is known to take its time in rolling out features globally.

You can download the latest version of the app from the Play Store link below. We’ll update this article if we learn more about the rollout of these new features, but do let us know if you see any of these new features on your own Pixel device.

Personal Safety app on Google Play

The post Google confirms Car Crash Detection is coming to Pixel smartphones appeared first on xda-developers.

Navigation Gestures 1.18.4 released to stable with new features and bug fixes

It’s been a while since the last stable update of Navigation Gestures (1.15.10), and even longer since we’ve posted about an update. We’re here to change that. This post marks the release of Navigation Gestures 1.18.4 to stable. You might be wondering: what happened to 1.16 and 1.17? Well, we can assure you we know how to count. You may not have seen these versions on the stable channel, but we’ve been hard at work releasing betas.

In those betas, we decided to concentrate more on stability instead of new features. While there are a couple of new options, most of the changes since 1.15.10 are to improve performance, prevent crashes, and fix bugs. Think of it like Google’s Project Marble, but hopefully more effective.

Release Highlights

  • Performance should be noticeably improved on older and lower-end devices.
  • Navigation Gestures is less likely to be killed in the background.
  • We’ve added an option to put the pill on top of the software navigation bar, so it has a dedicated space.

Hopefully, 1.18.4 will provide a much better experience. If you still run into any issues, make sure to report them at support.xda-developers.com. To make things easier for everyone, please include your device model, app version, and Android version if you make a report.

Now, here’s everything that’s new:

New Navigation Gestures Features

  • Overlay Navigation Bar
    • While it can be nice to have the extra space gained by hiding the navigation bar, it’s possible for the pill to interfere with app elements near the bottom of the screen. If you have this problem, try out the new “Overlay NavBar” option in the Experimental Settings. It will place the pill on top of the software navigation bar and blackout the navigation buttons.
    • If you’d like to keep your navigation buttons, you can deactivate the “Blackout” option.
    • Make sure to turn off “Hide Navigation Bar” before enabling this.
    • This option only works for devices that have a software navigation bar.
Overlay NavBar navigation gestures Overlay NavBar No Blackout navigation gestures
  • Per-App Pill Color
    • Since we released this app, we’ve been getting requests for an option to automatically color the pill based on what’s behind it. Unfortunately, we can’t do exactly that. However, we’ve added a new Experimental Setting called “Per-App Pill Color” which lets you set the color of the pill on a per-app basis. Any apps not selected will use the color set in Appearance.
Per-App Pill Color Options Per-App Pill Color Example
  • Accessibility Button Action (Root)
    • The release of Android Oreo brought an accessibility button to the navigation bar. Unfortunately, Android doesn’t allow normal apps to invoke this action. If you have root access, though, you’ll see two new actions: one to open the chosen accessibility interface, and another to select which one to show.
  • Keep Alive
    • We’ve done a lot to make sure Navigation Gestures isn’t killed by Android, but some devices have incredibly aggressive battery management. If you’ve been noticing that Navigation Gestures is killed on your device a lot, the new “Keep Alive” option may help. Found in the Compatibility settings, enabling it will start a foreground Service, which should keep the app alive.
  • Restart App
    • Sometimes the app gets unstable. We know it; you know it. We’re working on making it better, but it’s never going to be perfect. If you find yourself running into problems with Navigation Gestures, open the app and tap the “Problems?” button. Scroll down and tap the first option in the “Something else?” category to restart the app.
    • When restoring settings from a backup, Navigation Gestures will also prompt you to restart the app.

Bug Fixes

  • Crash Fixes
    • Since the last stable release, 1.15.10, we’ve been working hard to fix as many crashes as possible. If everything has gone to plan, you should notice fewer (or even no) crashes using 1.18.4.
  • “Don’t Hide NavBar on Lock Screen” and “Don’t Show on Lock Screen” Fixes
    • On some devices (notably those running EMUI 3.x), there is a weird issue where Navigation Gestures thinks the device is always on the lock screen. This version should fix this issue, although we don’t have any EMUI 3.x devices to test with.
  • Performance Improvements
    • We’re not Snapchat, so we’re actually going to explain a little bit of what our performance improvements are.
      • On older and lower-end devices, animations should be smoother.
      • On all devices, battery usage should be lower.
  • Navigation Bar Height on Android 10
    • With Android 10’s new gestures, it’s possible to change the navigation bar height to be much shorter. Navigation Gestures 1.18.4 is now able to detect the change in the navigation bar height, so it can properly hide the navigation bar.
  • Switch Keyboard Action on Android 10
    • If you’ve got a device running Android 10, you may have noticed that this action was broken on 1.15.10. We’ve fixed it in 1.18.4, so it should work properly again. We also added a notice that the action requires you grant Navigation Gestures the WRITE_SECURE_SETTINGS permission if you haven’t already.

Navigation Gestures - Swipe Gesture Controls! (Free, Google Play) →

Navigation Gestures Premium Add-On ($1.49, Google Play) →

The post Navigation Gestures 1.18.4 released to stable with new features and bug fixes appeared first on xda-developers.

Nintendo 3DS emulation is now viable on Android with an unofficial Citra port

Many months ago, we talked about an unofficial Citra port which allowed you to play Nintendo 3DS games on your Android smartphone. While that specific build saw few updates, there’s a new build that just got released by the developer of Dolphin MMJ, and it runs a whole lot better than before. On high-end devices, games like Pokemon X/Y and Persona Q are very playable, with very few visual bugs and minimal lag. It’s obviously not perfect yet, but it’s certainly on its way. I ran some tests to see what games work and don’t work, and the results may surprise you. To use the Citra for Android emulator, you will need a smartphone with top of the line specifications at the moment. A Snapdragon 855 is basically a requirement to even get playable framerates.

Note: This is an unofficial build. We are not testing for raw performance at the moment as it wouldn’t be fair to any of the developers involved in the project, as it may give off a false assumption that 3DS games are unplayable on current-gen Android smartphones. It’s may be possible to emulate 3DS games flawlessly in the future with more optimization. On the contrary, it may never be.

Citra for Android is still unofficial

So, first things first, this is still an unofficial port. It’s not officially endorsed by the developers of Citra, and until recently, was actually plagued with ethical concerns over its violation of the GPL. That has been rectified since its published source code to GitHub, but it’s something to keep in mind as well to the legitimacy of it all. It works, but if you’d rather wait for an official release from the Citra developers (which has apparently been in the works for a long time now) then you can wait for that. If you want to start using it now though, it’s extremely simple to use and navigate. There are a lot more features than that older port allowed as well, including actually useful features such as internal resolution scaling, emulation regions, and more. You can check out the screenshots below to see all of that.

Fire Emblem: Awakening

This title was the first that our Editor-in-Chief, Mishaal Rahman, tested on Citra. He tested it on the ASUS ROG Phone II which launched just recently, with the game more or less completely playable. Some parts may suffer frustrating slowdowns, but for a first port, it’s nothing short of amazing. Fire Emblem: Awakening probably fared the best in our tests, as its problems were kept to a minimum. You can check out the video of which Mishaal recorded down below to get a feel for how the game runs on the ASUS ROG Phone II.

Animal Crossing: New Leaf

One of my favorite titles from the Nintendo 3DS, I was excited at the prospect of playing this game on my smartphone. Sadly it wasn’t meant to be, as the frame rates are basically unplayable. It runs at 50% speed most of the time when in the overworld, and even lags quite a bit during the opening intro sequence with Rover. It runs well though, and if you can bear the horrible framerates, it does appear to be functional. I’m super excited for the future of this title in particular, as playing it on a smartphone would be incredible. It’s worth noting that the screen flashing is because of the screen recorder, as disabling it also stops the flickering. This happens on both the OPPO Reno 10x Zoom and the OnePlus 7 Pro, though Mishaal Rahman didn’t see it happen on the ASUS ROG Phone II.

Pokemon X

One of the best-selling titles from the Nintendo 3DS, fans of the Pokemon series will be clamoring to see if it runs on Android. I’ve seen people using emulators solely to play Pokemon games, so I would be surprised if people were any different with Pokemon X. Just like other Pokemon games, Pokemon X is one of the least intensive games on the system, and runs surprisingly well. Again, the flickering appears to be caused by my screen recorder as it goes away once I stop the recording. It’s a surprisingly playable game, though it’s worth mentioning that there’s no music yet due to the audio’s file format. The game also allows you to actually complete the intro sequence, a problem which plagued the last Citra for Android port that we tested a few months back.

How to download Citra for Android

You can download Citra for Android from Github, but keep in mind it’s certainly not in its best state yet. It has a number of issues and the performance is poor in most games, though it might be worth checking out anyway! You can download it below. Note that Citra can only play decrypted files, which you can get by decrypting the games using your hacked Nintendo 3DS.

Citra for Nintendo 3DS

The post Nintendo 3DS emulation is now viable on Android with an unofficial Citra port appeared first on xda-developers.

Unofficial LineageOS 14.1 brings Android 7.1 Nougat to the 7th gen Amazon Fire HD 10

The beauty of the XDA development community is how passionate it can be. We are constantly impressed by some of the feats pulled off by developers in our community, allowing users to break free from the burdens imposed by some OEMs to make their device truly theirs. Amazon has become one of the most restrictive OEMs in this regard. Their Fire devices don’t really run Android in the traditional sense, rather, their devices run Amazon’s heavily customized Fire OS. It might be based on Android, but it barely resembles it. The OS in the 7th gen Amazon Fire HD 10 is actually based on Android 5.1 Lollipop, which is a very old version of Android that’s starting to become deprecated by some developers.

If you have one of these tablets, all hope isn’t lost: a developer has managed to put together an unofficial LineageOS 14.1 build based on Android 7.1 Nougat. Now granted, this is still a very old version of Android, with Android 7.1 having been released around late 2016 to early 2017. Nonetheless, this is still a very impressive development. Not only is the tablet stuck on Lollipop, but the low-end MediaTek MT8173 on it isn’t exactly developer-friendly at all. The software in this tablet predates the Project Treble times by several years, so you can’t just flash a GSI on it.

Being able to run Android Nougat on the tablet should open a lot of doors for Fire HD 10 users. There are a number of bugs to take note of such as a nonfunctional camera and issues with wired headphones and OMX. Still, if you want to try out the build for the Fire HD 10, you can head over to the XDA thread linked below to find the instructions and download links. You’ll need to unlock the bootloader first, and we have instructions for how to do that here.

Unofficial LineageOS 14.1 for the 7th gen. Amazon Fire HD 10

The post Unofficial LineageOS 14.1 brings Android 7.1 Nougat to the 7th gen Amazon Fire HD 10 appeared first on xda-developers.

Congress scrutinizes Google over use of private DNS in Chrome

DNS over HTTPS is a new-ish concept that was first introduced and proposed by the Internet Engineering Task Force (IETF) back in October 2018, roughly a year ago. For starters, it allows for performing DNS resolutions over the HTTPS protocol, providing great advantages for both privacy and security. This new protocol was supported, among other companies, by Google, and the company is currently working into implementing DNS over HTTPS on Google Chrome and is planning to start testing the feature on Chrome 78, rolling it out to a small number of users.

But this new protocol is, however, not sitting well with ISPs as it effectively blocks them from having any insight into their users’ traffic. Now, Congress seems to be scrutinizing Google over its implementation of DoH, according to a Wall Street Journal report. According to this report, the House Judiciary Committee has sent a letter to Alphabet Inc. asking for information regarding its “decision regarding whether to adopt or promote the adoption” of DNS over HTTPS, as well as information on whether they were planning on using data processed through this protocol for commercial purposes. The Justice Department has also expressed that they were aware of concerns regarding this protocol and has confirmed that they’ve received complaints, likely from ISPs.

In response to this, Google has declared that they were supporting this feature to maximize and ensure the privacy and security of users online, as well as dismissed claims that they were trying to force users into passing their data through their own encrypted DNS servers. The company has declared in an emailed statement that “Google has no plans to centralize or change people’s DNS providers to Google by default” and that “any claim that we are trying to become the centralized encrypted DNS provider is inaccurate.”

As we said before, Google plans to begin testing a rollout of DNS over HTTPS starting with Chrome 78, in anticipation of a wider rollout on a future Chrome version.


Source: The Wall Street Journal

The post Congress scrutinizes Google over use of private DNS in Chrome appeared first on xda-developers.

YouTube TV launches on Amazon Fire TV devices

Google and Amazon have become fierce competitors in the past few years, competing for dominance on a lot of things such as artificial intelligence, voice assistants, and the smart TV ecosystem. They’ve even tried to take on Google’s dominance in the smartphone marketplace. In the case of smart TVs, though, Google’s Android TV is challenged by Amazon’s Fire TV devices–while this space is currently dominated by Roku, Amazon still has a small, yet considerable lead over Google here. This fierce competition has also led to some services from one company not being available on the other company’s devices, but this has been slowly changing. Now, YouTube TV, Google’s live TV streaming service, is becoming available on some Fire TV devices.

Amazon took to their Fire TV blog to announce the news today. The YouTube TV app, in case you don’t know, allows users to get access to live TV and over 70 channels from cable networks and local networks such as FOX, CBS, and ABC, all without the hassle of cable boxes and contracts. You tune into YouTube TV using your Internet connection. YouTube TV is also available on other popular platforms such as Roku, Apple TV, and (obviously) Android TV, as well as consoles like the Xbox One. Now, it’s also available on Fire TV devices, allowing more users to access Google’s TV platform. The list of compatible devices includes:

  • Fire TV Stick (2nd Gen)
  • Fire TV Stick 4K
  • Fire TV Cube (1st/2nd Gen)
  • Toshiba, Insignia, Element, and Westinghouse Fire TV Edition Smart TVs
  • Fire TV (2nd Gen)
  • Fire TV (3rd Gen, Pendant Design)

If you want to check out YouTube TV on your Fire TV and download it, then be sure to hop into Amazon’s app store to download it to your device right now.


Source: Amazon | Via: 9to5Google

The post YouTube TV launches on Amazon Fire TV devices appeared first on xda-developers.

Google Play Store gets one-tap buttons to unsubscribe from betas, clear wishlists, and more

The Google Play Store, amongst all its features, allows developers to roll out multiple release channels for the same app. Users can easily opt into an app’s beta program and start testing unreleased versions of an app without much more hassle. There is also a number of other features you can easily opt-in to, such as adding apps to your wishlist, pre-registering for unreleased apps, and so on. But a very pesky thing about these opt-in features is how, if you want to opt-out of them, you would have to go the extra mile and remove them one by one, which sounds like a complicated and annoying task.

Well, luckily for you, you don’t have to do this anymore. As of the latest version of the Google Play Store, the app has added a new “Google Play preferences” section in the app’s Settings. This gives you four new buttons which will allow you to leave every beta program you’ve ever joined, wipe your wishlist clean, and unregister for both upcoming events and unreleased, upcoming apps you’ve pre-registered for. A reset button of sorts if you might call it like that. Whether there is a beta app bothering you or you just don’t want to receive any notifications, there are lots of scenarios where this may come in handy. As we said before, the functionality for opting out of these lists on a per-app basis has always existed, but it’s nice to have global buttons to clear these lists completely.

As the Google Play Store receives a massive overhaul of both the way the app looks and feels, features like these being introduced make perfect sense and are pretty useful for users. If you want to check it out, be sure to have the latest version of the Google Play Store installed–the Play Store updates by itself, so you don’t have to do much other than waiting.


Via: Android Police

The post Google Play Store gets one-tap buttons to unsubscribe from betas, clear wishlists, and more appeared first on xda-developers.

Samsung Galaxy Note 10 Display Analysis: The Most Vibrant and Brightest, but Not the Most Accurate

Samsung and Apple are the two back-to-back contenders for “best smartphone display”, and the title is sometimes thought to belong to the company who’s released the latest phone. However, since both companies source their displays from Samsung Display, many believe that it is Samsung’s smartphones that must have the better displays. This belief is flawed since Samsung Display is actually a separate company from Samsung Mobile, who assembles the Galaxy smartphones, and who are also asking client to Samsung Display. And just like any other client, the OEM is ultimately responsible for the color calibration qualities shipped on their phones’ displays, and the latest panels don’t necessarily mean the best-calibrated. In this review, we take an extensive look at panel qualities of the Samsung Galaxy Note 10 and how well it has been calibrated according to industry standards.

Samsung Galaxy Note 10 Display Specifications

The Note lineup has previously been thought of as giant phones with extra-large displays, but Samsung switched it up with the Galaxy Note 10 to be more in-line in size with their S-series phones. The regular Galaxy Note 10 is very similar in size to the Galaxy S10, only slightly larger — the display is about 0.2 inches wider and 0.1 inches taller. The front-facing camera is housed in a small cut-out circle at the top-center of the display, which was previously at the top-right on the S10. I personally think that it looks goofier in the middle than on the right, but it is actually more out-of-the-way when using the phone since nothing is usually in the middle of the status bar anyway, and it doesn’t shove the system icons awkwardly to the left.

The panel is coined “Dynamic AMOLED” by Samsung, which they mainly attribute to its HDR10+ capability and its reduction in harmful blue light. This is the most Apple move Samsung has made in a while, in my opinion. The display has a native resolution of 2280×1080 pixels over its 6.3-inch display, or 401 pixels-per-inch. This pixel density is absolutely mediocre for a $950 phone, especially when Samsung’s “mid-range” S10e has a higher pixel density, and its S10 counterpart has a 1440p screen. The lower density is immediately noticeable to me when reading text, and 1080p videos definitely do not look as sharp as 1440p videos do on the S10. Samsung has been indecisive between rendering at 1080p or 1440p, as suggested by their 1080p render resolution on their 1440p panels. It would seem that Samsung would benefit from taking Apple’s approach of targetting a specific pixel density in-between, and custom-manufacture panels with resolutions for that pixel density for both sizes of their smartphones. Apple targets 458 pixels-per-inch for their OLED iPhones, which is between 1080p and 1440p for their respective sizes, and, in my opinion, is the sweet-spot between pixel density and power consumption without the need to downsample. However, I imagine that manufacturing panels at these specific resolutions is actually more costly than just using the mass-produced 1440p fabrication process.

Samsung boasts that their displays, starting from the S10, help against eye fatigue by reducing the amount of blue light within the “harmful range.” They achieve this by shifting the wavelength of their blue OLED a little further up the visible spectrum, and it is not a screen “filter” that some may have been lead to believe. Because adjusting the wavelength of a light source changes the color of its light, Samsung needed to have completely recalibrated their panels for the new OLED. At a glance, Samsung seems to have done a good job of color-matching it to their previous OLEDs as indicated by their similar (warm) white point, but I can’t help but wonder if it’s a reason for why they’re still calibrated so warm.

Methodology

Display Profiles & Color Gamut

Color gamut for Samsung Galaxy Note10

Color gamut for Samsung Galaxy Note10

The Galaxy Note 10 maintains the two standard color profiles, Natural and Vivid, for Android devices adopting Google’s color management system.

The Natural profile was the default display profile set on my US Snapdragon variant, and if Samsung is to follow the same trend as on the S10, it is the default profile for the US and Europe, while Vivid is the default for Asia. It is the color-accurate display profile, employing color management to render content in their intended color space, and defaults to targeting sRGB, the standard color space for the entire Internet, for non-contexted colors. The adoption of color management in Android apps is still very low, but Samsung’s Gallery app and Google Photos both support viewing wide-color images. As seen in the Color Gamut figure, the profile doesn’t seem to reach the full saturation for blue, and it is slightly warmer than standard.

The Vivid profile expands the color saturation of colors on the screen and modifies the white point to be colder, which can be further adjusted by the available color temperature slider. Its color gamut is about 54% larger, with 22% increased reds, 38% increased greens, and 28% increased blues relative to its Natural profile. And while the profile does expand saturation, its greens and blues are both shifted towards cyan. This may be undesirable to those that want to use a profile that just expands color saturation but not the originally intended hue of colors. The profile also does not support Android’s color management system, which is detrimental to content retaining the same relative artistic intent (if apps supported it). There are phones that provide both a color saturation-expanding profile and color management, like the OnePlus 7 Pro, which improves the viability of color saturation-expanding profiles.

Brightness: A

Section Description

Phone brightness reference chart

Phone brightness reference chart

When it comes to display brightness, Samsung’s mobile OLEDs have always typically been the brightest. Peak display brightness is a quality that pretty much all comes from the provided panel and its rated power efficacy. This is where Samsung shines (!) since their group affiliation with Samsung Display can nag them first-in-line for their latest schematics and panels. Apple’s iPhone 11 Pro phones, however, did not release too-long after, and also use the same-generation panels as the S10 and Note 10.

In its Natural profile, the Samsung Galaxy Note 10’s manual brightness ranges from 1.85 nits at its minimum up to 377 nits at its maximum. This is measured at 100% APL, which is a fullscreen white image and when OLEDs are typically the dimmest. At 100% APL, the power management of the display driver is at its maximum for its specific white level (if any), and no brightness boosting is applied. The Natural profile does not employ any brightness boosting, and it does not seem to have much brightness decay due to power management — in fact, the display brightness seems to slightly increase with higher APL, the inverse of what’s expected of OLED displays. However, as revealed later from our grayscale measurements, there actually is brightness decay with increased APL for lower color intensities, and Samsung must be applying some sort of boosting to keep 100%-intensity white brightness readings similar (and slightly higher).

For the Vivid profile, the manual brightness ranges from 1.85 nits to 380 nits at 100% APL. Unlike in the Natural profile, Samsung squeezes as much brightness as they can out of the Vivid profile, boosting up to 7% in brightness per 100 nits average display luminance. As a result, the Vivid profile can boost up to 420 nits at 50% APL, peaking at 480 nits at a low <1% APL.

Under intense ambient light, the Galaxy Note 10 enters high brightness mode in which the panel draws additional power, boosting up to about 790 nits for 100% APL for both display profiles. Additional boosting is also enabled for both profiles at lower content pixel levels under high ambient light (where this boosting is usually disabled for the Natural profile), further boosting up to 915 nits for 50% APL, and capping out at 1115 nits for a tiny lit region of the screen.

Color Accuracy & Balance: B

Section Description

Preface:

Smartphone displays are getting good. Really good. The displays on some of the latest smartphones seem to be acing tests in color accuracy. However, when they are pitted against reference-grade monitors, they may be far from it. ΔE values from low-breadth patterns don’t tell the whole story. Display assessments must be improved to better reflect the nuanced performance of a display and to be able to better distinguish the calibration characteristics between very good displays.

We have moved on to a new objective color difference metric, ΔETP (ITU-R BT.2124), which is an overall better measure for color differences than ΔE00 that is used in my previous reviews and is still currently being used in many other sites’ display reviews. Those that are still using ΔE00 for color error reporting are encouraged to use ΔEITP, as will be detailed in a session from the Society of Motion Picture and Television Engineers (SMPTE) and Portrait Displays (owner of CalMan).

ΔETP values are roughly 3× the magnitude of ΔE00 values for the same color. The metric assumes the most critically-adapted viewing condition for the observer, and a measured ΔETP color difference value of 1.0 denotes a just-noticeable-difference for the color, and a value less than 1.0 signifies that the measured color is indistinguishable from perfect. For our reviews, a ΔETP value of less than 3.0 is an acceptable level of accuracy for a reference display (suggested from ITU-R BT.2124 Annex 4.2), and a ΔETP value greater than 8.0 is noticeable at a glance (tested empirically, and the value (8.0) also nicely lines up with roughly a 10% change in luminance, which is generally the change in percentage needed to notice a difference in brightness at a glance).

We also curated a more-exhaustive set of testing patterns to better assess total color accuracy covering more conditions. For these reasons, the ΔE values we present for this review cannot be directly compared to ΔE values reported in previous reviews since both the metric and the testing patterns differ, with our newer assessments reporting larger overall ΔE values. The methodology and test patterns are explained in a previous section.

sRGB color accuracy for Samsung Galaxy Note10 (Natural profile)
sRGB color accuracy for Samsung Galaxy Note10 (Natural Profile), 100% intensity sRGB color accuracy for Samsung Galaxy Note10 (Natural Profile), 64% intensity sRGB color accuracy for Samsung Galaxy Note10 (Natural Profile), 36% intensity sRGB color accuracy for Samsung Galaxy Note10 (Natural Profile), 16% intensity sRGB color accuracy for Samsung Galaxy Note10 (Natural Profile), 4% intensity

As is Samsung tradition, the white point is calibrated too warm, with a correlated color temperature of about 6215 K for 100% white. Considering that OLED displays are subject to metameric failure and appear warmer for the same color measurements than their transmissive LCD counterparts, measuring too warm puts the Galaxy displays even further from the industry-standard white point. An inaccurate, warm white point is a detriment to the whole color gamut of the Note 10, shifting all colors towards red and decreasing color accuracy. Some may suggest that this is due to Samsung’s adaptive white point that was part of their old Adaptive display profile, but that does not apply to the Natural profile (nor does it seem to exist in the Vivid profile), and the Note 10 was measured in a near-pitch-black room.

Given Samsung’s supposed supremacy in display color accuracy, our evaluation of the Galaxy Note 10’s color accuracy for sRGB in its Natural profile is actually slightly disappointing. The profile has an average color difference ΔETP of 4.5 for sRGB, with a standard deviation of 4.6 throughout its intensity range. This means that, on average, sRGB colors on the Samsung Galaxy Note 10 are imperfect and above reference tolerance, though many are unlikely to be noticed besides the outliers. The high standard deviation of 4.6 is due to those outliers with high errors, and this puts colors that are indistinguishable from perfect and color errors that are noticeable at a glance all within one standard deviation from the average.

The Samsung Galaxy Note 10 is most accurate at maximum current intensity, with an average color difference ΔETP of 3.4, yet it slightly undersaturates its reds and blues. As color intensity reduces, so does the color accuracy of the Galaxy Note 10. High-saturation reds become radically oversaturated, and at the lowest intensities, the whole gamut is oversaturated. For very-low 4% intensities the profile has an average color difference ΔETP of 10.3, which may appear unpleasant at minimum display brightness levels and with low-intensity scenes in general. The Note 10’s Natural profile has a very high maximum error of 30 for low-intensity, max-saturation sRGB red. The overall average does not include the ΔETP value for this very-low intensity since color accuracy at these luminance levels is not as important and are often off-mark on OLED displays.

Click here for a link to the smartphone color accuracy reference chart. Note that the measurements in this list use the old methodology, and the Note 10* is scaled accordingly.

P3 color accuracy for Samsung Galaxy Note 10 (Natural profile)
P3 color accuracy for Samsung Galaxy Note10 (Natural Profile), 100% intensity P3 color accuracy for Samsung Galaxy Note10 (Natural Profile), 64% intensity P3 color accuracy for Samsung Galaxy Note10 (Natural Profile), 36% intensity P3 color accuracy for Samsung Galaxy Note10 (Natural Profile), 16% intensity P3 color accuracy for Samsung Galaxy Note10 (Natural Profile), 4% intensity

Fortunately, the Galaxy Note 10 does slightly better reproducing P3 colors in its Natural profile than sRGB colors, although sRGB gamut accuracy is definitely more important. Saturation targets are tracked quite nicely for P3 colors, and there are no gross oversaturations at lower intensities. Blues, however, are still shifted in hue and slightly oversaturated at lower intensities, just like they are for sRGB colors. Samsung seems to have an issue with color mixing at lower intensities, and color primaries approach that of the display’s native gamut as current intensity is reduced. The Natural profile has an overall average ΔETP of 4.2 for P3 colors, with a much lower standard deviation of 2.9.

Drive balance charts for Samsung Galaxy Note 10
Drive balance chart for Note10, Natural profile Drive balance chart for Note10, Vivid profile

The RGB drive balance for both the Natural profile and the Vivid profile remain consistent throughout its intensity range. The three color channels remain within 10% of its maximum intensity, so the color of white and gray does not noticeably drift too far. In regards to color shifting at varying APL, the Note 10’s panel behavior has increasing reds and blues and slightly-decreasing greens as display emission increases. This results in a panel that shifts toward magenta at higher APLs, becoming more severe the higher the display brightness.

Contrast & Tone Response: B

Section Description

Gamma scales for Samsung Galaxy Note 10

An average pixel level (APL) of 50% is a typical pixel level for many apps and their content. At 50% APL, the Note 10 has a higher gamma than the standard of 2.20, measuring at about 2.35 for both the Natural and Vivid profiles. This results in the Samsung Galaxy Note 10 usually displaying a picture with higher contrast than standard. For low APL, which correspond to dark scenes and dark-mode apps, the display gamma on both profiles is closer to the 2.20 standard, though it’s still slightly high. However, this is offset by low APL content usually being viewed in low/dark ambient lighting, at which a display gamma closer to 2.40 is usually desired. For low display brightness and low content APL, the Note 10 boosts its shadows, resulting in a gamma of about 2.06 for those super-dim conditions where the panel may have difficulties rendering dark shades. Nevertheless, the display gamma should ideally remain consistent and independent from content APL, and should only be modified by either a change in ambient lighting or by external tone mapping.

Both profiles have the same target transfer function, which is responsible for the display’s intended contrast and gamma. In reality, the actual gamma is different between the two profiles because the Vivid profile boosts its brightness with lower content APL, while the Natural profile does not. In theory, the brightness boost of the Vivid profile means that its display gamma and contrast should increase with display brightness relative to the Natural profile, which it does. However, when averaging the Galaxy Note 10’s gamma throughout its brightness range, the two profiles actually average out to be very similar to one another. This is a bit unusual since the Natural profile is meant to have nearly no variance in luminance with APL, yet the profile has a considerable discrepancy in contrast between low 1% APL and medium 50% APL. So while the Natural profile has no brightness boost, it is still subject to luminance decay from increased display emission, and low-intensity shades are affected the most. This results in the Natural profile’s increased display gamma at higher display emissions.

Overall, the gamma and contrast of the Natural profile aren’t too accurate and are also quite inconsistent. They vary significantly with brightness and APL, ranging from 2.06 for low-brightness at low-APL up to 2.47 for medium-brightness at 50% APL. Although the Vivid profile isn’t to be seriously evaluated for accuracy, a display profile should maintain a consistent gamma, if not following a color appearance model.

On the Exynos Galaxy S10 I previously reviewed, I noticed that its display strangely followed the sRGB transfer function instead of a straight gamma power. However, I then found that the Snapdragon variant normally followed a straight 2.20 gamma power and that the two panels had different calibrations. The Galaxy Note 10 I’m reviewing is a Snapdragon variant, and while I do not own an Exynos Note 10, I believe that Samsung may still be targeting the sRGB transfer function for certain variants. DisplayMate’s intensity scale for their Note 10+ precisely matches the intensity scale for my Exynos S10 and the sRGB transfer function, with the same reported gamma. My guess is that Samsung is now natively decoding RGB triplets with the sRGB transfer function for the Natural profile in the Exynos display pipeline.

With the Exynos S10, I thought that Samsung may have finally fixed their issues with black clipping. While the sRGB transfer function isn’t as punchy and doesn’t provide as much contrast as a straight gamma power, it did have the benefit of cheating around black crush by significantly lifting near-black shades. With the Snapdragon Galaxy Note 10, the panel still exhibits the same amount of black clipping as all previous Samsung Galaxy displays (apart from the cheating Exynos variants). Samsung continues to fail to render its first 5 steps of its 8-bit intensities, and there’s absolutely no reason for it at this point besides negligence.

High brightness mode on my previous Exynos S10 would also adjust the display gamma for high ambient lighting, significantly reducing the contrast and lightening screen colors to improve sunlight legibility and perceived color accuracy. It looks like this is no longer the case for the Samsung Galaxy Note 10, unless that feature is also unique to the Exynos variants. If it is, it would be a welcome addition to Snapdragon devices.

HDR Video Playback: D

With the release of the Galaxy S10, Samsung began to make a push for HDR10+, boasting its latest phones’ capabilities to both capture and playback videos in the new format. It’s actually quite remarkable that phones are now able to support it. But just how accurate can a smartphone reproduce HDR content? For our assessment, we will only be staging 8-bit colors and static metadata.

HDR PQ reproduction for Samsung Galaxy Note 10

The Samsung Galaxy Note 10 doesn’t seem to reproduce the absolute Perceptual Quantizer all that well, unfortunately. Shadows start off too dark, and it jumps up too high in brightness, overexposing the entire scene. The peak brightness of 1000 nits for 20% APL is great, however, and Samsung does correctly roll off into it instead of clipping like the Sony Xperia 1. The Note 10 also doesn’t do too well at reproducing HDR color, missing a large chunk of the red and orange hues within the HDR sRGB gamut. Orange, pink, and purple hues are completely off-mark in the HDR P3 gamut, likely from overshooting the base PQ curve. The color error for these reference colors are quite high, and they don’t even cover a significant portion of the total color volume of the BT2100 color space.

Final Thoughts

Even though the Galaxy Note 10 is only meant to be a minuscule update to the Galaxy S10, I’m a little disappointed in the direction (or lack thereof) that Samsung seems to be heading. The resolution downgrade to 1080p on the “base” Note 10, for example, is uncalled for. There are many people, including me, that can absolutely resolve the Note 10’s 401 pixels-per-inch. OnePlus had constantly been under fire for maintaining the same 401 pixels-per-inch in their displays, and Samsung should not be held sanctuary. That pixel density hovers within most people’s visual acuity at typical smartphone-viewing distances, and it needs to clear it a good-leap further to comfortably appear perfectly sharp for more people.

Color accuracy and its intricacies are a very niche matter. Most people don’t necessarily care for perfect color reproduction, which is why I tend to weigh it lower in my overall grade. But those that genuinely do care for color accuracy need to know the full extent of its calibration qualities. This is where the Note 10 — and Samsung’s calibrations in general — doesn’t perform as great as most outlets lead them on to be. DisplayMate is generally to be acknowledged for that since Samsung seems to time-after-time ace DisplayMate’s color accuracy tests. Most don’t question it, because it does require a lot of knowledge of the subject to understand what you’re looking at when you’re reading color accuracy measurements. One of the issues is that DisplayMate only measures 41 colors on the display at its maximum brightness. This is not enough measurements at enough display conditions to form a metric that accurately describes the general accuracy of a display. Because, as shown in my measurements, the color accuracy of the Samsung Galaxy Note 10 rapidly deteriorates at lower color intensities. Many intricate details about the panel calibration are left out, including black clipping, drive variance, and properly-averaged gamma (since gamma also changes with total emission). All of these are very important characteristics of a reference monitor, and a display review should bring light to these issues.

Given the ever-rising ubiquity of smartphones and their utility, there should really be more independent testing of smartphone displays that can hold them to these higher standards.

But for those that don’t care about color accuracy, it’s just another brighter panel, with no other improvements, and a reduction in pixels. However, other panels are getting just as bright, and many displays are also already rather accurate, with quite a number of them being more accurate than the Galaxy Note 10. Then there are those that are now including higher refresh rate panels, which provide an actually-noticeable umph to the smartphone display experience — an umph that hasn’t been felt (or seen) in newer display feature additions in a while. And these factors, in my modest judgment, now blur the line that props up the Galaxy lineup as a leader in smartphone displays. Which is fine, because it is a result of the latest smartphone displays just becoming that good, and they need this additional scrutiny to be able to differentiate them.

Good

  • Brightest OLED on the market
  • Very vibrant Vivid profile

Bad

  • 1080p/401 PPI panel on a $950 device is mediocre
  • White point in Natural profile too warm
  • Low-intensity colors are oversaturated
  • HDR10 playback needs improvement
  • No improvements in black clipping

XDA DISPLAY GRADE

B

Specification Samsung Galaxy Note 10
Type “Dynamic AMOLED”

PenTile Diamond Pixel

Manufacturer Samsung Display Co.
Size 5.7 inches by 2.7 inches

6.3-inch diagonal

15.4 square inches

Resolution 2280×1080 pixels

19:9 pixel aspect ratio

Pixel Density 284 red subpixels per inch

401 green subpixels per inch

284 blue subpixels per inch

Distance for Pixel Acuity Distances for just-resolvable pixels with 20/20 vision. Typical smartphone viewing distance is about 12 inches <12.1 inches for full-color image

<8.6 inches for achromatic image

Angular Shift Measured at a 30-degree incline -25% for brightness shift

ΔETP = 7.8 for color shift

Click here for chart

Black Clipping Threshold Signal levels to be clipped black <2.0%
Specification Natural Vivid
Brightness
100% APL:
790 nits (auto) / 377 nits (manual)
50% APL:
915 nits (auto) / 376 nits (manual)
1% APL:
1115 nits (auto) / 375 nits (manual)

0.6% increase in luminance per 100 nits
100% APL:
781 nits (auto) / 380 nits (manual)
50% APL:
905 nits (auto) / 420 nits (manual)
1% APL:
1107 nits (auto) / 478 nits (manual)

Boosts up to 6.9% in luminance per 100 nits
Gamma Standard is a straight gamma of 2.20
2.07–2.46
Average 2.34
High variance
2.06–2.47
Average 2.36
High variance
White Point Standard is 6504 K
6215 K
ΔETP = 3.1
6703 K
ΔETP = 2.3
Color DifferenceΔETP values above 10 are apparent
ΔETP values below 3.0 appear accurate
ΔETP values below 1.0 are indistinguishable from perfect
sRGB:
Average ΔETP = 4.5 ± 4.6
Maximum ΔETP = 30
50% color accuracy
Maximum errors are high
P3:
Average ΔE = 4.2 ± 2.9
Maximum ΔETP = 17
41% color accuracy
Maximum errors are high
54% larger gamut than Natural profile
+22% red saturation, hue-shifted 1.1  degrees (ΔETP⊥ = 5.2) towards orange
+38% green saturation, hue-shifted 5.1 degrees (ΔETP⊥ = 13.6) towards cyan
+25% blue saturation, hue-shifted 5.7 degrees (ΔETP⊥ = 18.8) towards cyan

Samsung Galaxy Note 10 Forums ||| Samsung Galaxy Note 10+ Forums

The post Samsung Galaxy Note 10 Display Analysis: The Most Vibrant and Brightest, but Not the Most Accurate appeared first on xda-developers.