This wallpaper triggers a rare bug causing Android devices to bootloop

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, the developers behind the popular LineageOS custom ROM have also come up with a unique solution to the problem. You can check out the patch description over on the LineageOS Gerrit by following 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.

The post 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

Taskbar 6.0 enables a Samsung DeX-like desktop mode experience on some Android 10+ devices

Android 10 has been out for nearly 9 months now, but one of its best features, desktop mode, is still widely unknown. That’s because it’s technically hidden in Android 10, requiring a development flag to be enabled as well as support built-in to the stock launcher app. Thankfully, the developer of Taskbar has figured out a way to make Android 10’s desktop mode far more useful, bringing a Samsung DeX-like experience to some devices.

For some background, Android 10 added a “Secondary Launcher” activity to Launcher3, the AOSP launcher app that Google’s Pixel Launcher and many other OEM launcher apps are derived from. When an Android device with support for display output is hooked up to an external display, this Secondary Launcher activity is shown on the external display. However, because this Secondary Launcher is extremely barebones, it’s not useful to use as a productivity tool. Third-party app developers figured out that it’s possible for their own launcher apps to replace the stock launcher on the external display, and that’s exactly what XDA Senior Member farmerbb has implemented in Taskbar 6.0.

Taskbar is an open-source Android app that puts a floating start menu and recent apps tray on top of any screen. Since it supports launching Android apps in freeform multi-window, it even comes pre-installed on Bliss OS, a popular Android port for x86 PCs. Back in early November, farmerbb released a fork of the open-source Lawnchair launcher with Taskbar integrated into it. This gave us an early look at what Android 10’s hidden desktop mode could look like with some development effort, but there were some glaring issues that needed fixing. The desktop mode user experience needed fixing so that freeform multi-window behavior worked as you would expect, the setup process needed to be cleaned up so you could control the DPI/UI without needing another app, and a better solution had to be found so that you wouldn’t have to change your default launcher. Now, farmerbb has updated Taskbar to version 6.0 to address all of these issues.

Desktop Mode with Taskbar 6.0

Setting up Taskbar’s desktop mode is quite easy:

1. In Developer Options, turn on “enable freeform windows” and “force desktop mode” and then reboot your device. (The latter may be unavailable on some OEM software like ZenUI/ROG UI, but don’t worry if it’s not there.)
2. Install Taskbar 6.0 (older versions won’t work) from Google Play.
3. Open Taskbar’s settings and go to “Desktop Mode.” Enable it and grant the app permission to “display over other apps” as this is required for the app’s floating start menu to appear. Then, set the app as your default home app. Don’t worry, though, as the next prompt will ask you to set your preferred/primary launcher app, so Taskbar won’t be hijacking your home screen. (Note that on some devices, changing the default launcher will disable Android 10’s full-screen navigation gestures.)
4. Next, I highly recommend you follow the instructions to “enable additional settings” for desktop mode. This will allow you to lower the DPI so UI elements aren’t enormous on the external display, to hide the navigation bar, and to even dim the phone’s screen to save battery life while it’s connected to the external display. You’ll have to set up ADB access on your PC and run the following command:

   adb shell pm grant com.farmerbb.taskbar android.permission.WRITE_SECURE_SETTINGS

   (If you are using Taskbar’s “Donate” version, replace “com.farmerbb.taskbar” with “com.farmerbb.taskbar.paid” in the above command.)

5. Finally, check to make sure that “usage access” has been enabled for Taskbar. Doing so will allow the app to show a row of your recently used applications in the start menu.
6. Now, simply connect your phone to your external display using a USB Type-C to Type-C cable (if your external display supports Type-C input) or via a USB Type-C to HDMI adapter.

Once connected, you can use the start menu to launch apps, search for apps, add app icons to the home screen, open some system menus, and more. You can tap the icon next to the start menu to add/show widgets. You can launch multiple instances of windows, and in some cases like Google Chrome, have multiple tabs.

There are loads of other options and changes in Taskbar 6.0, so I recommend you read the full changelog available here.

Display Output on Android – Sadly Still Limited

Who might this be useful for? Samsung, Huawei/Honor, and LG offer their own desktop mode experiences, so there’s you won’t find much use out of Taskbar’s desktop mode if you own a smartphone from one of those brands. ASUS, OnePlus, Essential, Google, and Xiaomi don’t offer their own desktop mode experiences, so if you’re on at least Android 10 on a device from one of these brands, then you may find Taskbar’s desktop mode feature to be useful. If you want a desktop mode experience to be more productive, then I recommend you use a Bluetooth keyboard and mouse. If you have a portable external monitor/laptop chassis like the NexDock 2, then you’ll have an even better experience with Taskbar.

Keep in mind that in order to actually make use of this feature, your smartphone must support display output. Qualcomm’s latest Snapdragon 800 and 700 series chipsets natively support DisplayPort Alternate Mode over a USB 3.1 Type-C port, but some vendors (like Google) have disabled this functionality on their smartphones. If your device doesn’t support DisplayPort Alternate Mode, then you may have luck using a DisplayLink-certified adapter and the DisplayLink Presenter app to mirror the phone’s display. Screen mirroring using a DisplayLink adapter isn’t as ideal as native desktop mode through a standard connector, but it’s better than not having any display output at all! Fortunately, Taskbar can still be used if you’re just mirroring your phone’s display so long as the app is set as the default launcher, but you’ll have to use the developer’s SecondScreen app to change the resolution and density.

The biggest downside to desktop mode on Android right now is the limited app support. Even though Samsung and Huawei have both offered desktop mode experiences for years and sell millions of smartphones a year, there’s not a lot of demand from users to support desktop mode. That means that a lot of Android apps out there aren’t optimized for larger screens. Google wants to change that because broader Android app support for larger screens will benefit Chromebooks as well, but sadly, there’s still a long way to go before most Android apps support larger screens. Thus, while using Taskbar, you may notice that some apps refuse to run or just look terrible, and there’s not much you can do to fix that.

Download Taskbar 6.0

If you have one of the following smartphones, I recommend giving this app a try:

• ASUS ROG Phone II
• Essential Phone
• OnePlus 7
• OnePlus 7 Pro
• OnePlus 7T
• OnePlus 7T Pro
• OnePlus 8
• OnePlus 8 Pro
• OPPO Reno 10X Zoom

You can download Taskbar 6.0 from the Google Play Store link below or compile the app from its source code on GitHub. The app is totally free to use, but there’s a $1.99 donate version in case you want to support farmerbb’s development efforts.

Taskbar Forum Thread on XDA ||| Taskbar Source Code on GitHub

Taskbar - PC-style productivity for Android (Free, Google Play) →

Taskbar (Donate Version) ($1.99, Google Play) →

The post Taskbar 6.0 enables a Samsung DeX-like desktop mode experience on some Android 10+ devices appeared first on xda-developers.

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

LineageOS 17.1 adds support for new OnePlus, Samsung, Xiaomi, and other devices following server hack

LineageOS is the most popular AOSP-based custom ROM out there. Its origin can be traced back to CyanogenMod, which was itself not only the most well-known custom ROM many years ago but also the reason the OnePlus One was so well-received by the community. Over the years, the team behind LineageOS has kept the project updated with new versions of Android for dozens of Android devices. The latest version, LineageOS 17.1, is based on Android 10 and supports a long list of devices. Now, the custom ROM team has added official support for their latest release for a lot of devices from OnePlus, Samsung, Xiaomi, and more. Newly added devices include the Essential Phone, Moto X (2014), Samsung Galaxy A5 (2016), Xiaomi Redmi Note 5 Pro, and more.

The LineageOS team recently decided to cease the development of LineageOS 15.1 and jump to version 17.1 rather than 17.0 after they decided to rebase on top of the updated AOSP release corresponding to the Pixel 4/4 XL launch. With the update, the team also announced Lineage Recovery as the default option to install LineageOS on officially supported phones. 17.1 also added a new ThemePicker, a partial screenshot feature, and a lot more.

You can find the new LineageOS nightly builds for each of the following devices by tapping on “Get the builds here” on their respective Wiki pages. All of the devices listed here except for the Samsung Galaxy Grand 2 Duos are supported by LineageOS 17.1. The newly added Grand 2 Duos is supported by LineageOS 16 based on Android 9 Pie.

Device + XDA Forum Link	Code-name + Wiki Page	Maintainer(s)
Essential Phone	mata	haggertk, intervigil, npjohnson, rashed
Motorola Moto X (2014)	victara	jro1979, linckandrea, npjohnson
OnePlus 2	oneplus2	OzzysCmAcc, aviraxp
OnePlus 7	guacamoleb (mirror)*	AshwinRC
Samsung Galaxy A3 (2016)	a3xelte	danwood76, Stricted
Samsung Galaxy A5 (2016)	a5xelte	danwood76, Stricted
Samsung Galaxy Grand 2 Duos	ms013g (mirror)*	djchittoor
Samsung Galaxy S5 Neo	s5neolte	danwood76, Stricted
Wileyfox Swift	crackling	115ek
Xiaomi Mi A2	jasmine_sprout (mirror)*	mikeioannina
Xiaomi Mi 6X	wayne (mirror)*	Isaac Chen
Xiaomi Mi Note 3	jason	dianlujitao
Xiaomi Redmi 2	wt88047	nicknitewolf
Xiaomi Redmi 7	onclite (mirror)*	Dhina17
Xiaomi Redmi Note 5 Pro	whyred (mirror)*	srfarias, SebaUbuntu
Xiaomi Redmi Note 6 Pro	twolip (mirror)*	DD3Boh
Xiaomi Redmi Note 7	lavender (mirror)*	erfanoabdi

*Some of the download pages for newly added devices return a code 500 “Internal Server Error.” Until this bug is fixed, you can download the official builds from the official LineageOS download mirror. For those devices that require it, the download mirror for LineageOS Recovery can be found here.

Be sure to read the installation instructions for each of the devices as well as the other documentation linked such as for Lineage Recovery. Also, be sure to take a backup of your data before you start with the installation process.

Why the delay?

If you’re wondering why LineageOS has had a delay in getting new builds up, the answer is because LineageOS suffered a hack in early May. According to a statement published by the team on May 3rd, an attacker “used a CVE in our saltstack master to gain access to our infrastructure.” Salt is an open-source framework to manage servers that is used by loads of open-source projects like LineageOS. On April 30th, Cybersecurity firm F-Secure publicly disclosed a vulnerability in Salt that could be used to bypass authorization. Attackers quickly targeted Salt installations that were unpatched, resulting in dozens of servers being hacked.

The LineageOS team identified the attack and then quickly took down its servers. The team confirms that their build signing keys are unaffected (so third-parties can’t sign and distribute official LineageOS builds), the currently uploaded builds themselves are unaffected, and the project’s source code is unaffected.

Around 8PM PST on May 2nd, 2020 an attacker used a CVE in our saltstack master to gain access to our infrastructure.

We are able to verify that:
– Signing keys are unaffected.
– Builds are unaffected.
– Source code is unaffected.

See https://t.co/85fvp6Gj2h for more info.

— LineageOS (@LineageAndroid) May 3, 2020

The post LineageOS 17.1 adds support for new OnePlus, Samsung, Xiaomi, and other devices following server hack appeared first on xda-developers.

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

[Update: Delayed] Google will launch the Android 11 Beta on June 3rd, releases Developer Preview 4 today

Update 1 (05/30/2020 @ 01:07 AM ET): Google has announced that the launch and event scheduled for June 3, 2020, has been postponed. Scroll to the bottom for more information. The article as published on May 6, 2020, is preserved below.

Google announced the first Android 11 Developer Preview back in February. The first Developer Preview was released earlier than we expected because Google wanted to give developers more time to adapt to their apps to the new APIs and platform behaviors. Since DP 1, two more Developer Preview builds have been rolled out to the Pixel 2 onward. If it weren’t for the COVID-19 pandemic, Google would have released the first Android 11 Beta at Google I/O event, which was scheduled for May 12th-14th. This delay has impacted the Android 11 release timeline, and the tech giant has now announced that they are pushing back the release of the first Android 11 Beta. The first beta will now be revealed at an online event on June 3rd, 2020. To make up for the new gap between DP3 and Beta 1, Google is releasing Android 11 Developer Preview 4.

Google has aptly titled next month’s online event “#Android 11: The Beta Launch Show.” During this event, Google will release Android 11 Beta 1 which will contain the final SDK and NDK APIs. Google will also open up Play Store submissions for apps targeting the new Android version. Citing this change in plan, Google has also released an updated timeline for the release schedule.

Older Beta timeline

Updated Beta timeline

While Google had initially charted its plan to release only three Android 11 Developer Previews, it is releasing the Developer Preview 4 to fill up the gap caused by the delay in the release of Beta 1. Starting today, the DP4 builds for the Google Pixel 2/2 XL, Pixel 3/3 XL, Pixel 3a/3a XL, and Pixel 4/4 XL will be available for download. You can flash these builds manually to try out the upcoming Android version or wait for an OTA if you’re already enrolled in the Beta program.

Since Android 11 Beta 1 has been pushed back by about a month, Beta 2 will now be released in July instead of June. As with the previous schedule, Beta 2 will be the “Platform Stability” release. Google introduced this milestone with Android 11 to signify the finalization of internal and external APIs, app-facing behaviors, and non-SDK graylisting. According to official communication from Google, Android 11 Beta 3 will be released in August 2020, and this will be the “Release candidate” build. The Final Release is still expected to be available in Q3, which means it shouldn’t be pushed back to October or months after that.

While the exact date for Beta 2 onwards was not released, Flame Group – a company that consults with OEMs and ODMs to help them receive GMS certifications for devices – mentioned in a blog post that the “Final Release Candidate,” which is most likely Beta 2, will be released on July 6th. While Beta 3 is intended to be the Release candidate build, it appears that Flame Group is referring to Beta 2 when it talks about the “Final Release candidate.” Furthermore, the blog post states that Google will publish the Android 11 source code to the AOSP git repository on September 8th, 2020. Our source corroborates the information laid out in this blog post, as it is apparently information that Google shared with its partner OEMs.

Android 11 News on XDA

Android 11: The Beta Launch Show to substitute Google I/O 2020?

At the Android 11: The Beta Launch Show, Google will also be hosting a series of online talks and webinars for topics that were initially supposed to be covered at Google I/O 2020. The talks ranging “from Jetpack Compose to Android Studio and Google Play” will be held following the post-show Q&A session after the announcement launch. You can register yourself to get notified of the event on this page.

---

Update: Google postpones Android 11 Beta Launch Show

Google has announced that the Android 11 Beta Launch Show has been postponed.

We are excited to tell you more about Android 11, but now is not the time to celebrate. We are postponing the June 3rd event and beta release. We’ll be back with more on Android 11, soon.

— Android Developers (@AndroidDev) May 30, 2020

The next date has not been announced yet.

The post [Update: Delayed] Google will launch the Android 11 Beta on June 3rd, releases Developer Preview 4 today appeared first on xda-developers.

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

Samsung Access program quietly launches for the Galaxy S20 with Premium Care and Microsoft 365 included

A few years ago, Apple launched its iPhone Upgrade Program. Apple’s program offered a great deal where every year you could pay a low monthly fee to have the option to upgrade your iPhone while continuing those monthly payments. Carriers and other device makers emulated this idea but started to add their own offers to improve upon it. Samsung, of course, was one of the companies that emulated that idea with the Samsung Upgrade Program. Now, Samsung has quietly launched a new program called “Samsung Access” that provides even more benefits at a lower cost.

Samsung Access, which we spotted earlier today on Samsung.com, is a bit different than the previous Samsung Upgrade Program in terms of benefits. Both Samsung Access and the previous Samsung Upgrade Program have you finance a new phone through monthly payments and later allow you to trade in the phone for the value that’s left. For example, if you had the Samsung Galaxy S10 for a year and paid $30 a month for 12 months ($360 total), you would have owed $540 left on the balance on the device. If you wanted to upgrade to the Samsung Galaxy S20 after it launched, you would send back the Galaxy S10 to Samsung so they could void the $540 and allow you to start a new contract for a new monthly fee for the new device.

Samsung Access works the same way for upgrading. If you wanted to keep the device instead of upgrading, you are able to pay off the full balance or just not upgrade and continue your financing which takes 36 months or 3 years.

If you are like me and like to upgrade a lot, that’s also a possibility with Samsung Access. You are able to upgrade your phone for no fee every 9 months. If you wanted to upgrade earlier in the cycle, say for example from the latest Galaxy Note to Galaxy S series or vice versa, you can do so if you pay a $100 fee. In the long run, you would likely save money using this service instead of buying and trading in phones every time a new one launches.

Samsung Access – Other Benefits

What makes Samsung Access better than the Samsung Upgrade Program are the other parts that are included in the monthly subscription. Samsung Access includes both Microsoft 365, which itself includes 1TB of OneDrive storage, and Samsung Premium Care. Microsoft 365 gives you full access to the Microsoft Office suite, including Outlook, Word, Excel, Powerpoint, Skype, and Teams. The 1TB of OneDrive storage, which is included in a Microsoft 365 subscription, is especially useful on Samsung phones. You are able to link your Samsung and Microsoft accounts to use the 1TB of storage for photo backups in the Samsung Gallery app or Samsung Cloud storage for backups. The other benefit, Premium Care, is Samsung’s insurance program. If you break your phone, you are able to get it replaced or repaired for a $99 deductible up to three times in a 12 month period.

Samsung Access is available for the Samsung Galaxy S20 series only. When financing the Galaxy S20 series, it costs $37 a month for the Galaxy S20, $42 a month for the Galaxy S20+, and $48 a month for the Galaxy S20 Ultra. In my view, this is actually a great deal. If you were to sign up for Samsung Financing, Premium Care, and Microsoft 365 separately, it would cost you an extra $9 per month. That might not seem like much, but over the 36 months of the contract, you would save $324. That’s ignoring the money you can save from the upgrade program. If you want to cancel, you are also able to return the phone for free after 3 months. If you want to cancel before those 3 months, though, you will owe a $100 fee.

These programs are actually really good for those early adopters who love to upgrade (like me). It makes upgrading easy and painless along with not having to worry about accidental damage since it’s covered under Premium Care. All around, this is a pretty great upgrade deal. For a visual overview of what’s offered in Samsung Access, check out the video below that Samsung uploaded to their YouTube channel today. Otherwise, hit up the Samsung Access page and read the FAQs to get all the nitty-gritty details.

Samsung Access for Mobile ||| Samsung Access FAQs

Oh, and Samsung Access is also available for Samsung TVs, in case you’re interested.

The post Samsung Access program quietly launches for the Galaxy S20 with Premium Care and Microsoft 365 included appeared first on xda-developers.

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

The Samsung Galaxy A71s 5G UW may launch on Verizon with support for the carrier’s Ultrawide Band network

Flagship smartphones have become really expensive this year, with many at or beyond the $1,000 mark. The Qualcomm Snapdragon 865 is apparently a really expensive chip because it doesn’t come with a modem and also 5G is just really complex. Fortunately, there’s the cheaper (but less powerful) Qualcomm Snapdragon 765 which includes an integrated 5G modem. We earlier found evidence that the U.S.-bound Galaxy A71 5G will feature this chipset when it lands on Verizon. There was some doubt about whether the Verizon model will support the carrier’s Ultrawide Band network when it launches, but now, we’ve spotted evidence that the device will indeed support Verizon’s mmWave network.

In some regulatory documents that were recently published, we spotted the marketing name of the device corresponding to model name SM-A716V. SM-A716V, if you’ll recall, is the model name we spotted last week on the Bluetooth SIG that appeared alongside the product name “Galaxy-A71-5g US VERIZON.” Today’s regulatory filing indicates this device may actually be marketed on Verizon as the Samsung Galaxy A71s 5G UW.

This name is important for a few reasons. First, it tells us that Verizon may carry the phone under the “Galaxy A71s 5G” branding which has yet to be announced. However, we expect the phone overall to be very similar to the other U.S. Galaxy A71 5G models. The “UW” part of the name tells us the phone will support connecting to Verizon’s Ultrawide Band network which operates in mmWave frequencies. Verizon has appended the “UW” branding to the name of several 5G devices they carry such as the OnePlus 8 5G UW, Galaxy S20 5G UW, LG V60 5G ThinQ UW, and more.

As we reported last week, the United States version of the Samsung Galaxy A71 5G should use the Qualcomm Snapdragon 765 chipset. The 765, 765G, and 768G are the only chipsets from Qualcomm with integrated 5G modems. That modem is the Snapdragon X52, and like the Snapdragon X55 modem paired with Snapdragon 865 devices, the X52 supports both mmWave and sub-6GHz 5G networks. While we’ve seen other Snapdragon 765-powered devices with support for sub-6GHz 5G, the Galaxy A71s 5G UW would be the first Snapdragon 765 device to support mmWave 5G. It would also be the first mid-range smartphone to support Verizon’s 5G network if you exclude the Moto Z3 and Moto Z4 which required a $350 Moto Mod.

While Verizon’s mmWave network has proven to be very fast, the coverage isn’t great. You would need an uninterrupted direct line of sight with the broadcast antenna. Verizon has claimed to be launching a low-band 5G network later this year but the carrier hasn’t given any specific locations yet. The Galaxy A71s 5G UW should support the current mmWave network and the upcoming low-band network when it launches.

Keep in mind that although the information in this article comes from an official regulatory filing from Samsung, there’s a possibility that there’s an error in the filing. We will have to wait for the official launch from Verizon for more information about the phone and network compatibility.

Featured image: Samsung Galaxy A71 in pink

The post The Samsung Galaxy A71s 5G UW may launch on Verizon with support for the carrier’s Ultrawide Band network appeared first on xda-developers.

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

OnePlus 8 series camera updates will bring color filters to portrait mode, improved white balance, and more

The OnePlus 8 has been in the news recently for its camera, but not in the way you might expect. People discovered that the OnePlus 8 Pro’s camera could use the Photochrom filter to see through certain things, including thin clothing. OnePlus made the decision to disable the feature and rework it. But that’s just one part of the OnePlus 8 series’ camera capability, and the company is continuing to work on it.

OnePlus 8 XDA Forums || OnePlus 8 Pro XDA Forums

Last week, the folks at OnePlus had an online Open Ears Forum about the OnePlus 8’s camera technology. During the meeting, some new features for the OnePlus 8 series were floated to users for feedback. Those features haven’t been revealed yet, but the company has shared some actions they will be taking based on feedback:

• Continue improving white balance consistency across all lenses
• Reduce the haloing seen on some HDR portrait shots
• Improve UX for AE lock
• Add more color filters and bring them to portrait mode
• Show visual cue when tripod mode is triggered
• Keep optimizing post-processing strategy

These things seem like pretty basic camera functions, but they’re also things that generally can always use improvement in smartphone cameras. White balance consistency across lenses is especially important in the day and age of multi-camera devices. The visual cue for tripod mode is also a welcomed addition as there’s no way to manually enable it.

We have no idea when these changes will come to the OnePlus 8 series. We’ll keep an eye out for these changes in a future OxygenOS update.

Thanks for XDA Senior Member Some_Random_Username for the tip!

---

Source: OnePlus

The post OnePlus 8 series camera updates will bring color filters to portrait mode, improved white balance, and more appeared first on xda-developers.

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