OnePlus 8 Pro may go on sale in India with its Color Filter Camera disabled

The Color Filter camera on the OnePlus 8 Pro has been in the news for a fair few reasons. At first, most reviews wrote off the 5MP color filter camera and its existence as a gimmick, one with very limited use cases that a lot of users would quickly forget. Then, some users found that the color filter camera can actually see through very thin plastic objects and very thin clothing. OnePlus then mentioned in a Weibo post that they would be disabling the camera through a software update, with a clarification coming later that this would only be for the Chinese market. Surprisingly, an OTA went out to global units which ended up disabling the camera, only for OnePlus to come out and clarify that this was an accidental rollout and that the change was reverted shortly thereafter.

OnePlus 8 Pro XDA Forums

As it turns out, customers who purchase the OnePlus 8 Pro in India might not get to witness the color filter camera, not initially at least. We have evidence that suggests that the mode will be disabled on the Indian units as well.

OnePlus 8 Pro XDA Review — Never Settle on Hardware

In OnePlus Camera 4.0.267, which is to be found within OxygenOS 10.5.10 that has rolled out for the OnePlus 8 Pro in India, we spotted a few things. One, this update adds video filters and prepares to add a “Smart Scene Enhancement” toggle. In addition to this, we also discovered that the property “InfraredCameraBuilder.ModelsToDisableInfraredCamera” was modified to include model names “IN2020” and “IN2021“. IN2020 refers to the Chinese OnePlus 8 Pro, while IN2021 is the Indian OnePlus 8 Pro.

We decompiled the app and discovered that this camera app update now checks the system property ro.product.model. If this property matches either IN2021 or IN2021, then the color filter camera and the Photochrom mode is disabled.

We do not have access to an Indian OnePlus 8 Pro to test this out. But, we could replicate the same by changing the value of ro.product.model to IN2021 on a rooted OnePlus 8 Pro Global variant.

We can confirm that enabling this property will disable the color filter camera on the camera app update.

What does this mean for customers in India?

The OnePlus 8 Pro has launched in India, but it has not gone on open sale in the country yet, as the company had to deal with production issues because of COVID-19. There is no date announced yet for the first sale of the device, so no consumers actually have the device in their hands yet.

It is likely that OnePlus could preload this software update on retail units, which means that consumers will not have access to the color filter camera out-of-the-box (note that other cameras and modes will remain functional). Even if they do not preload the update, most users will accept the OTA updates on their phones anyway, especially since the update does have other meaningful additions, meaning the mode will be disabled through an update shortly after unboxing.

Our internal sources suggest that this disabling of the color filter camera is a temporary measure and that OnePlus is already working on an update that will “fix” and re-enable the camera, with an expected rollout ETA of end of June 2020.

We’ve reached out to OnePlus India for comments or statements on the same. We will update our article when we hear back from them.

The post OnePlus 8 Pro may go on sale in India with its Color Filter Camera disabled appeared first on xda-developers.

from xda-developers https://ift.tt/3dsNELk
via IFTTT

[Update: Launched in India] Samsung Galaxy A31 launched with 48MP quad rear cameras, 5000mAh battery, MediaTek Helio P65

Update 1 (06/04/2020 @ 06:59 AM ET): Samsung has launched the Galaxy A31 in India. Scroll to the bottom for more information. The article as published on March 24, 2020, is preserved below.

Last year, Samsung incorporated the J series into the Galaxy A series. The realigned Galaxy A series now comprises a wider variety of mid-range and sub-premium devices and caters to users who prize a smartphone’s looks and camera features over its performance. After launching several devices in the series – ranging from Galaxy A10 to Galaxy A90 5G – and even bringing mid-cycle upgrades to several of these devices in 2019, Samsung has already started launching the second generation of Galaxy A series devices. The latest one in the series is the Galaxy A31, which comes with a 48MP quad cameras, MediaTek Helio P65, 5000mAh battery, and Samsung Pay.

The Samsung Galaxy A31 is the fifth A series phone this year. Samsung started the year by unveiling the Galaxy A51 and the Galaxy A71, followed by the Galaxy A11 and the Galaxy A41 launching earlier this month. In terms of design, the Samsung Galaxy A31 aligns with the “Prism Crush” design on the other phones in the bunch. On the back, it features a quad camera with setup in an L-shaped orientation, which seems to be Samsung’s design mantra for 2020.

On the front, there’s a 6.4-inch Full HD+ Super AMOLED Infinity-U display, which is an upgrade over the HD+ Super AMOLED display we saw on the Galaxy A30s. Just like the Galaxy A30s, the Galaxy A31 also comes with an in-display fingerprint scanner. The front-facing camera has also been upgraded from 16MP to 20MP.

The quad-camera setup on the back appears identical to the Galaxy A51. It includes a 48MP primary camera, an 8MP wide-angle camera, and two 5MP cameras for macro photography and depth-sensing.

In terms of performance, the Samsung Galaxy A31 is equipped with a MediaTek P65 SoC and comes in 4GB and 6GB RAM variants. The two RAM variants feature 64GB and 128GB storages, respectively. The phone also supports Samsung Pay but the availability of NFC or MST will vary as per the country. Onboard, there’s a 5,000mAh battery that supports 15W fast charging.

In terms of software, the Galaxy A31 is expected to come pre-loaded with One UI 2.0 based on Android 10.

Samsung has not revealed the price or the date of availability for the Galaxy A31 and the same will vary as per your country. It is available in black, blue, red, and white colors.

Samsung Galaxy A31: Specifications

Specification	Samsung Galaxy A31
Dimensions and Weight	73.1 x 159.3 x 8.6 mm 185g
Display	6.4-inch FHD+ Super AMOLED Infinity-U
SoC	MediaTek Helio P65 12nm process 2 x Cortex A75 @ 2.0GHz 6 x Cortex A55 @ 1.7GHz
RAM and Storage	4GB + 64GB 6GB + 128GB Expandable through microSD card slot
Battery & Charging	5,000 mAh battery 15W fast charging
Rear Camera	48MP, f/2.0 8MP ultra wide-angle, f/2.2 5MP depth sensor, f/2.4 5MP macro, f/2.4
Front Camera	20MP, f/2.2
Other Features	Samsung Pay

Update: Samsung Galaxy A31 launched in India for ₹21,999 (~$291)

Samsung has launched the Galaxy A31 in India, for a price of ₹21,999 (~$291) for the 6GB RAM + 128GB storage variant. The phone will be available in blue, black, and white color variants. You can buy the phone across offline retail stores, Samsung Opera House, Samsung.com and leading online portals such as Amazon.in.

Buy the Samsung Galaxy A31 from Amazon.in

The post [Update: Launched in India] Samsung Galaxy A31 launched with 48MP quad rear cameras, 5000mAh battery, MediaTek Helio P65 appeared first on xda-developers.

from xda-developers https://ift.tt/2UvpMP3
via IFTTT

Netflix adds the ASUS ZenFone 6, ASUS ROG Phone II, and TCL 10 series to its list of HD certified devices

In order to stream videos in HD resolution from popular streaming apps like Netflix and Amazon Prime Video, your smartphone needs to have Widewine L1 certification. However, despite Widevine L1 certification, some devices aren’t able to stream HD content on Netflix because the platform also has to manually whitelist devices to enable HD playback support. Over the last few months, Netflix has whitelisted several Samsung Galaxy devices for HD and HDR10 support, and most recently, the company added the OPPO Reno3, a few Sony Xperia phones, and the Xiaomi Mi Note 10 Lite to its HD/HDR supported list. Now, according to a recent report from Android Police, the company has added the ASUS ZenFone 6 (ASUS 6Z in India), ROG Phone II, and the TCL 10 series to the list.

New HD-compatible devices:

• ASUS ROG Phone II
• ASUS ZenFone 6
• TCL 10L
• TCL 10 Pro

New HDR10-compatible devices:

• ASUS ROG Phone II
• TCL 10L
• TCL 10 Pro

Interestingly, the ASUS ROG Phone II has previously been listed on Netflix’s list of HD and HDR10 certified devices but was removed alongside the premature listing of the Google Pixel 4. Despite being recently added to the list, we can confirm that both the ZenFone 6 and ROG Phone II have supported HD and HDR10 playback on Netflix for several months now.

This leads us to believe that Netflix takes its own sweet time to add new devices to the list, even if they already support HD/HDR10 playback on the platform. Which is why we recommend that you don’t believe the list at face value and check if your device supports the Widevine L1 certification using an app like DRM Info. Once you confirm that your device features Widevine L1 support, you can try playing videos in HD or HDR10 on Netflix to see if your device has been whitelisted by the platform.

---

Via: Android Police

Source: Netflix Help Center

The post Netflix adds the ASUS ZenFone 6, ASUS ROG Phone II, and TCL 10 series to its list of HD certified devices appeared first on xda-developers.

from xda-developers https://ift.tt/2U8LB7o
via IFTTT

OnePlus Camera 4.0.267 on the OnePlus 8 series adds video filters and prepares to add a “Smart Scene Enhancement” toggle

OnePlus recently rolled out a major OxygenOS update for the OnePlus 8 (review) and OnePlus 8 Pro (review). As per the official changelog, the update added several new features to the OnePlus Camera app, including support for H.265 HEVC codec for videos, a new auto ultra-wide-angle lens feature, optimizations for the click animation, and improvements for camera stability. What the changelog didn’t mention, however, is that the update also included a new set of “video filters” for the video mode in the camera app.

An APK teardown can often predict features that may arrive in a future update of an application, but it is possible that any of the features we mention here may not make it in a future release. This is because these features are currently unimplemented in the live build and may be pulled at any time by the developers in a future build.

The OnePlus Camera app version 4.0.267 recently rolled out for the OnePlus 8 and OnePlus 8 Pro in India with the OxygenOS 10.5.8/10.5.10 update. The app brings a new set of video filters — Vivid, Night, Vintage, B&W, and Yummy — that you can use while recording videos on the device.

The filters are supported on all video resolution except for the 4K 60Hz setting and can be accessed by tapping on the filter icon in the top right corner of the app.

<string name="settings_key_is_smart_scene_enhancement_enabled">IsSmartSceneEnhancementEnabled</string>
<string name="settings_smart_scene_enhancement_description">Auto enhance image based on scene detection</string>
<string name="settings_smart_scene_enhancement_title">Smart scene enhancement</string>
<string name="settings_smart_scene_enhancement_toast">Scene enhancement icon will pop up when triggered</string>

Additionally, a teardown of the OnePlus Camera app reveals that the company is preparing to add a new “Smart Scene Enhancement” toggle in the camera settings. While the Smart Scene Enhancement feature is already active in the current version of the camera app, it’s invisible to the user and cannot be disabled. The newly added strings of code suggest that a future update for the app will bring a new indicator in the viewfinder that will show users when the smart scene enhancement feature is active and a new toggle in the app settings that will let users disable the feature completely.

---

Thanks to PNF Software for providing us a license to use JEB Decompiler, a professional-grade reverse engineering tool for Android applications.

The post OnePlus Camera 4.0.267 on the OnePlus 8 series adds video filters and prepares to add a “Smart Scene Enhancement” toggle appeared first on xda-developers.

from xda-developers https://ift.tt/2XttUlb
via IFTTT

Realme X3 with Qualcomm Snapdragon 855+, 120Hz display gets listed on Google Play and India’s BIS

After weeks of leaks and teasers, Realme finally launched the Realme X3 SuperZoom in Europe late last month. Priced at €499, Snapdragon 855+ powered flagship killer features a 120Hz high refresh rate FHD+ display, up to 12GB of RAM, and up to 256GB of onboard storage. However, one of the most interesting aspects of the X3 SuperZoom is its 8MP telephoto camera that supports 5x optical zoom and up to 60x digital zoom. While the device is currently only available in China and Europe, recent teasers from Realme suggest that it will soon be launched in India as well. However, we now believe that the company will be launching two more devices as part of the X3 series in the Indian market — Realme X3 and Realme X3 Pro.

Along with the Realme X3 SuperZoom, the company will also be launching the Realme X3 in India as listings of the device have now appeared on the Google Play Console’s Device Catalog and the Bureau of Indian Standards (BIS). The BIS listing confirms that there are 3 devices in the X3 series with the model numbers RMX2018, RMX 2085, and RMX2086. Over on the Google Play Console’s Device Catalog, devices with the model number RMX2081L1 and RMX2085L1 were added alongside the RMX2086L1. All three devices are listed with the marketing name Realme X3, but we know from our review unit that RMX2086 is the X3 SuperZoom. This leads us to believe that RMX2081 may be the regular X3, while RMX2085 may be the X3 Pro.

The Realme X3 and X3 Pro will presumably lack the X3 SuperZoom’s periscopic telephoto camera. However, both devices will feature the same Qualcomm Snapdragon 855+ chip. The X3 and X3 Pro will have 8GB of RAM, unlike the X3 SuperZoom’s 12GB, and both the devices may feature the same 120Hz panel, since “oppo.display.screen.120hz.support” is listed as a support system feature for both devices on the Google Play Console. As of now, we have no further information about the specifications of these devices but we expect to learn more from Realme in the days leading up to the launch.

---

Source: BIS

Featured image: Realme X3 SuperZoom

The post Realme X3 with Qualcomm Snapdragon 855+, 120Hz display gets listed on Google Play and India’s BIS appeared first on xda-developers.

from xda-developers https://ift.tt/2A37Rsy
via IFTTT

[Update: Specifications] HTC’s upcoming Desire 20 Pro leaks with a hole-punch display and quad rear cameras

Update 1 (06/04/2020 @ 03:40 AM ET): Specifications of the upcoming HTC Desire 20 Pro have surfaced on Google Play Console’s Device Catalog. Scroll to the bottom for more information. The article has published on April 30, 2020, is preserved as below.

Oh, HTC. The company that was once at the forefront of Android innovation, as well as the company that kickstarted Android phones in general (by launching the very first commercial Android phone 12 years ago), is now, for the most part, forgotten. After enduring a tough time, the company has exited the smartphone marketplace for the most part: we haven’t seen an HTC flagship since the HTC U12+, and right now, the company has focused on launching the occasional mid-range phone (often licensing their name to another company) or launching devices for a very niche market (remember that cryptocurrency phone?). Surprisingly, HTC now has another release in the pipeline: the upcoming HTC Desire 20 Pro.

Our first close look of the device comes from Evan Blass’ Patreon page, where he shared a rough render of the device. Meanwhile, XDA Recognized Contributor LlabTooFeR also shared the purported name of this phone as well as a rough depiction of it, which matches what Blass shared.

I thought HTC is dead… But HTC Desire 20 Pro is in the pipeline… Design is kind of a mix One Plus 8 on the front and Mi10 on the back… Yea, 3.5mm audio jack is there, lol

— LlabTooFeR (@LlabTooFeR) April 25, 2020

The HTC Desire lineup has always been about midrange phones and lower-end ones, and judging by the looks of it, the HTC Desire 20 Pro will be no different. It does integrate some newer smartphone design features: the phone will sport a hole-punch display, with the front-facing camera cornered to the left side of the display. The back also features a corner-aligned camera setup with what looks like a quad rear camera setup. We do have a rear-mounted fingerprint sensor, though, which has also lately become a characterizing feature in lower-end devices: most higher-end ones now go with in-display ones.

We have no clue on what this device will pack spec-wise, but since it’s a Desire smartphone and the phone looks fairly mid-range, we’re not really expecting anything amazing or mind-blowing here. There is an alleged GeekBench listing for the device, and it shows not-so-impressive performance, but it does indicate that it runs on an octa-core Snapdragon processor clocked at 1.8 GHz. It is possible that HTC might surprise us, though, but it’s highly unlikely. We also don’t know when HTC is planning to release this device or if it’s going to release it at all.

---

Update: Specifications of the HTC Desire 20 Pro

The HTC Desire 20 Pro has just been added to Google Play Console’s Device Catalog. With the codename “htc_bymdugl” and model name “HTC 2Q9J10000”, the HTC Desire 20 Pro will come with the Qualcomm Snapdragon 665 SoC, 6GB of RAM, and a display with a 2340×1080 resolution. The phone will run Android 10, unsurprisingly.

While the listing states specifications which we believe to be correct, it still includes an old render of the HTC u11+, so we do not have any new graphics to share at this stage.

The post [Update: Specifications] HTC’s upcoming Desire 20 Pro leaks with a hole-punch display and quad rear cameras appeared first on xda-developers.

from xda-developers https://ift.tt/3bQQCZd
via IFTTT

[Update: New Explanation, Google Response] This wallpaper triggers a rare bug causing Android devices to bootloop

Update 1 (06/04/2020 @ 03:12 AM ET): Explanations have emerged on the cursed wallpaper bug, alongside a response from Google. Scroll to the bottom for more information. The article as published on June 1, 2020, is preserved below.

Imagine you’re scouring the internet for cool wallpapers and you come across a picturesque landscape. It has everything; a lush green forest, a pristine lake with a tiny island, snow-capped mountains in the background, and a thick cloud cover with sunlight seeping in through the gaps. You immediately download the image, set it as your phone’s wallpaper, and boom! Your Android phone gets stuck in a bootloop. Sounds unlikely, doesn’t it? Well, it’s true for this particular wallpaper.

WARNING！！！
Never set this picture as wallpaper, especially for Samsung mobile phone users!
It will cause your phone to crash!
Don’t try it!
If someone sends you this picture, please ignore it. pic.twitter.com/rVbozJdhkL

— Ice universe (@UniverseIce) May 31, 2020

The wallpaper was recently shared on Twitter by renowned Samsung leakster Ice Universe, who claimed that the wallpaper “will cause your phone to crash!” Despite their warning, several users downloaded the wallpaper to check if it actually did do anything on their phone and they were met with the following results:

@UniverseIce This is an android issue sadly is affecting also google pixels as well pic.twitter.com/HZTtogLfwB

— Sebastian (@seb3153) May 31, 2020

This is the most fucking bug I’ve ever seen. I even tried in safe mode but still no help. Had to reset app data. Shitsung do something pic.twitter.com/ASeHfNNGYI

— Dawood (@pegasaie) May 31, 2020

Huh, tested this in an emulator. Crashes SystemUI. Checked for any odd issue with the image’s header, didn’t notice anything off from my limited knowledge of JPEG. It also ends properly. pic.twitter.com/s2m0q0WNqo

— Jason Ashley (@testsubjectname) May 31, 2020

According to Davide Bianco, lead developer of the AOSP-based custom ROM “POSP”, this particular wallpaper causes some Android devices to crash as it makes use of the RGB color space, instead of the sRGB color space that is supported natively on Android. Bianco has submitted a patch to AOSP that reportedly fixes the issue and the description of the patch states that “The issue occurs when the user tries to set as wallpaper an image that is not sRGB. What happens is that variable y value is higher than the histogram bounds, making SysUI crash. One possible fix is to limit y value to be always less than 256.” Along with Bianco, two developers, XDA Senior Member BadDaemon and XDA Recognized Developer luca020400, from the popular LineageOS custom ROM team have also come up with a unique solution to the problem. You can check out the patch descriptions over on the LineageOS Gerrit by following this link and this link.

We strongly recommend against using this image as your wallpaper under any circumstances. In case you have already used it and your device is stuck in a bootloop, please check the instructions below on how you may be able to recover your device.

A report from 9to5Google on the matter further reveals that the issue is limited to devices running Android 10 or older and it doesn’t affect devices running the Android 11 Developer Preview. This is due to the fact that on Android 11, the system converts the color space if it’s not supported, but on Android 10 it does not. Which means that this isn’t an issue with this particular image and could be caused by other images using the RGB color space.

Do note that while the issue doesn’t affect all Android devices, we strongly recommend against trying the wallpaper on your phone. In case you try it anyway, you might be able to recover your device by either resetting it completely or by entering safe mode and changing the wallpaper. But since some users over on Twitter weren’t able to recover their devices using the aforementioned methods, it would be best if you don’t use the exact image as your wallpaper. If you really like the wallpaper, just take a screenshot of the image and use that as your wallpaper instead.

---

Update: Explanation and Response from Google

Expanding on the causes of the bug as explained by XDA Senior Member BadDaemon and XDA Recognized Developer luca020400, the “cursed” wallpaper is encoded in a special color space which is called “Google/Skia/E3CADAB7BD3DE5E3436874D2A9DEE126” — this is the full name of the color space, and Skia refers to the 2D graphics library made by Google. In contrast, most other wallpaper images are encoded in a color space called “sRGB”.

In Android versions 10 and older, all images are converted to sRGB unless otherwise specified by the developers. There’s a rare bug that can occur when converting the image to sRGB, wherein the code that calculates the “luminance” value of each pixel manages to exceed the maximum limit of 255.

Luminance is calculated using the following formula:

Luminance = .2126f * r + .7152f * g + .0722f * b

Here “r”, “g”, and “b” are red, green, and blue color values represented in an 8-bit value from 0 to 255.

The problem with this calculation is that it always rounds the final value up. The “cursed” wallpaper has the following RGB values: 255, 255, 243, which when plugged into the above equation looks like:

Luminance = .2126 * (255) + .7152 * (255) + .0722 * (243)
Luminance = 256

This value causes SystemUI, and basically the whole OS, to crash because it exceeds the maximum value. It’s a bug that’s so incredibly specific because it involves a combination of a rounding error and color space conversion error.

This bug does not affect Android 11 because the image’s “Skia” color space is not converted to sRGB by default. Thus, this color space conversion error and the rounding error does not occur on Android 11.

However, Romain Guy from the Android Toolkit team at Google believes that the root cause of this issue is only in the way that luminance is calculated and not in any color space conversion issues. Google is conducting its own testing, so we will likely see what they come up with soon.

The post [Update: New Explanation, Google Response] This wallpaper triggers a rare bug causing Android devices to bootloop appeared first on xda-developers.

from xda-developers https://ift.tt/2TY96QH
via IFTTT