LightBlog

jeudi 4 juin 2020

[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.

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.

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:

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

mercredi 3 juin 2020

Facebook Messenger’s chat heads switch to Android 11’s bubble notifications API

Google introduced the new Bubbles API with Android 10 Beta 2 back in April last year. The API was initially offered as an opt-in feature for developers, with Google urging them to test the API in their apps so that the supported apps were ready when the feature finally rolled out in a future Android release. As expected, the feature was enabled by default in the Android 11 Developer Preview 1 that was released earlier this year. In the leaked Android 11 Beta, the Bubbles feature is now available in Notification settings (and not in Developer Options), however, developers still have to enable support for showing notifications in a Bubble. Up until now, we’ve only seen the feature in action in an APK teardown of the Google Messages app. But the latest update for Facebook Messenger also switches the app over the Bubbles API.

For the unaware, Facebook Messenger has long had a feature for floating notification bubbles called “Chat Heads”. The feature made use of Android’s System Alert Window API, but in Facebook Messenger version 268.0.0.3.118 the app is switching over to the new Bubbles API if the device is running Android 11. This feature works on our tipster’s Pixel 4XL running Android 11 Beta 1 and our Editor-in-Chief Mishaal Rahman‘s Pixel 3a XL, running Android 11 DP4.

Facebook Messenger Android 11 Bubbles Facebook Messenger Android 11 Bubbles Facebook Messenger Android 11 Bubbles

As you can see in the attached screenshots, the feature shows up as a new option called Bubbles in the Facebook Messenger settings. Once enabled, it gives you the option to choose if you wish to see Bubbles for all conversations, selected conversations, or no conversations from within the Messenger notification settings. While the feature is making use of the newer API, it still looks pretty much the same as the older Messenger Chat Heads. Whenever you receive a new message, it shows up as a chat bubble clinging to a side on your device’s home screen. Tapping on the bubble opens up the conversation in a floating window where you can quickly reply to messages.

You can move the bubble from one side to the other by tapping and holding the bubble and then dragging it to the other side. You also get the option to have multiple conversations in a single bubble by tapping on the plus icon at the top and adding a new contact. To dismiss a bubble, you can tap and hold on it and then drag it to the X icon that appears close to the bottom of the display.


Thanks to Hani Mohamed Bioud for the tip and screenshots!

The post Facebook Messenger’s chat heads switch to Android 11’s bubble notifications API appeared first on xda-developers.



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

ZTE quietly announced a 4G version of the Axon 11 with the MediaTek Helio P70 processor

Back in March, ZTE launched the Axon 11 as a mid-range 5G smartphone. It featured the Snapdragon 765G processor and a very affordable price for a 5G-equipped smartphone. ZTE also launched the Axon 11 SE in China with a MediaTek Dimensity 800. The company is back with another version of the Axon 11, this time without 5G.

The 4G version of the ZTE Axon 11 appears to be essentially the same device with one key difference. Instead of the Snapdragon 765G processor, the 4G-only variant has the MediaTek Helio P70 chip. Besides the fact that it doesn’t have 5G support, the Axon 11 4G has the same design, same four cameras, same battery size, etc. However, owing to the fact that the 4G variant has the weaker Helio P70 processor, this device likely doesn’t have a 90Hz refresh rate display or the same storage and RAM capacities. We also don’t know if the 4G version supports wireless charging like the 5G model, but the 4G model won’t support Qualcomm Quick Charge 4+ since it uses a MediaTek chipset. We’ll have to wait for the full specification sheet to be sure of all of these details, though.

ZTE very quietly announced this 4G-only Axon 11 on its official website but did not share pricing or availability details. The 5G model was already an affordable device, so the lack of 5G should make it even more affordable. Stay tuned for more details.

Specification ZTE Axon 11 4G
Dimensions & Weight 159.2 x 73.4 x 7.9mm, 168g
Display
  • 6.47-inch curved 3D AMOLED display
  • 19.5:9 FHD+ (2340×1080), 100,000:1 contrast
  • Waterdrop notch
SoC MediaTek Helio P70
RAM and Storage Unknown
Battery and Charging
  • 4,000 mAh
Ports
  • USB Type-C
  • No headphone jack
Rear Cameras
  • 64MP, f/1.89
  • 8MP, 120° wide-angle
  • 2MP macro
  • 2MP depth
Front Camera 20MP, f/2.0
Connectivity Dual SIM

FDD: B1/3/5/7/8/20/28/32

TDD: B38

UMTS: B1/5/8

GSM: B2/3/5/8

Security Under-display fingerprint scanner
Android Version MiFavor 10 based on Android 10
Colors Black

Source: ZTE

This article was updated at 5:21 PM EST to reflect that the display refresh rate, RAM, storage, and whether or not the device supports wireless charging are unknown.

The post ZTE quietly announced a 4G version of the Axon 11 with the MediaTek Helio P70 processor appeared first on xda-developers.



from xda-developers https://ift.tt/306n3ji
via IFTTT

OnePlus 8 and 8 Pro get new OxygenOS updates with tons of system, camera, and network optimizations

OnePlus is back with another round of OxygenOS updates for the OnePlus 8 series. The latest update has a pretty lengthy changelog, including numerous optimizations and fixes for the camera, system, and network. OnePlus is also including the May 2020 Android security patches with this update.

OnePlus 8 XDA Forums ||| OnePlus 8 Pro XDA Forums

The changelog includes some overlap with the OxyegnOS update that rolled out last month to the OnePlus 8 and 8 Pro. Some of the most noteworthy additions are found in the camera section of the changelog. There’s a new auto ultra-wide-angle lens feature when shooting at close range to improve the picture quality of edges (Pro only). They also added support for encoding videos in the H.265 (HEVC) video codec to reduce video storage size. Check the full changelog below and find download links at the bottom of the page.

Changelog

System

  • Optimized the touch and interaction experience
  • Optimized the expanded screenshot user experience for some scenes
  • Optimized the power consumption performance of the system, battery life extended to be longer than ever
  • Optimized the wireless charging stability, providing better user experience (OnePlus 8 Pro only)
  • Optimized the pocket mode to reduce mistouches
  • Optimized the unlocking animation, making the unlock transition smoother
  • Updated Android Security Patch to 2020.05
  • Updated GMS package to 2020.03

Message

  • Added the “Delete” button in the notification bar of incoming messages
  • Added keyword whitelist option in SMS blocking settings, the messages with the specified keywords will not be blocked

Camera

  • Newly added H.265 HEVC codec to reduce video storage size seamlessly, capture and shoot more without compromising on quality
  • Added auto ultra-wide-angle lens feature when shooting at close range to improve picture quality of edges (OnePlus 8 Pro only)
  • Optimized the click animation for camera shutter, boosting the smoothness of photo-taking experience
  • Improved the shooting experience with camera and improved stability

Network

  • Improved the stability of communication
  • Improved the performance and stability of Wi-Fi transfers
  • Optimized network latency for online games and improved the smoothness

Game Space

  • Added Epic Games in Game Space. With one-step installation, check out Fortnite and many other Epic Games, all from Game Space

Downloads

Once again, thanks to XDA Senior Member Some_Random_Username for providing the download links!

The post OnePlus 8 and 8 Pro get new OxygenOS updates with tons of system, camera, and network optimizations appeared first on xda-developers.



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

Microsoft’s new Chromium-based Edge browser rolls out to all Windows 10 users via Windows Update

Microsoft released the stable version of its Chromium-based Edge browser to the public earlier this year. Like any other browser (not including Internet Explorer), users had to go out of their way to download and try the new browser. As expected, Microsoft is now pushing the browser to Windows 10 devices via a Windows Update.

Since the beginning, Microsoft has said the Chromium-based Edge browser would replace the pre-installed Edge browser. From this point forward, Chromium Edge is the default Windows 10 browser. Microsoft support articles KB4541301, KB4541302, and KB4559309 inform users and administrators that the old Edge browser is being replaced with the new Chromium-based browser. The updates will be available for Windows 10 v1803 and later systems up to Windows 10 v2004.

Installing Chromium Edge via the Windows Update will replace the old Edge browser. However, unlike manually installing, it can’t be removed to restore the old Edge browser. There are a few different updates rolling out depending on your Windows 10 version. Microsoft also makes recommendations for which update you should be on before installing the Windows Update. As of right now, the update is not available through the Microsoft Update Catalog website.

  • KB4541301 — for Windows 10 version 1803 and 1809 (Microsoft recommends the November 12, 2019 updates KB4525237 and KB4523205)
  • KB4541302 – for Windows 10 version 1903 and 1909 (Microsoft recommends the October 8, 2019 update KB4517389)
  • KB4559309 — for all Windows 10 versions from Windows 10 version 1803 to 2004.

Microsoft will probably never live down Internet Explorer, but Chromium Edge is a very solid browser. If you haven’t tried it out yet you really should. It can rival Google Chrome in many ways and it’s only getting better. There is also an Android app.


Source: gHacks

The post Microsoft’s new Chromium-based Edge browser rolls out to all Windows 10 users via Windows Update appeared first on xda-developers.



from xda-developers https://ift.tt/36XT4vg
via IFTTT

Samsung may continue its Ultra branding with the Galaxy Note 20 series

As we get closer to the rumored launch date of Samsung’s next Galaxy Note smartphones, we’re learning more information about all of the devices in the series. For most of its history, the Samsung Galaxy Note series has only been sold in a single size, though last year was the first time that Samsung sold 2 different Galaxy Note devices in the Galaxy Note 10 and Note 10+. With the Galaxy S20 series this year, Samsung dropped the more affordable “e” variant and introduced an ultra-premium “Ultra” variant. While we still expect there to be only two Galaxy Note 20 smartphones this year, it seems that Samsung may apply the “Ultra” branding for higher-end Note 20, effectively replacing the + model.

In a new listing on the Bluetooth Launch Studio, the website where the Bluetooth SIG lists all Bluetooth-certified devices, a device with model name SM-N986U appeared with the design name “Samsung Galaxy Note20 Ultra.” The model number listed is the long-rumored model name of the upcoming Galaxy Note 20+. Assuming this new listing is accurate, that device may not be called the Note 20+ but rather the Galaxy Note 20 Ultra. This is in line with the branding from the Galaxy S20 series.

In my view, this branding change makes sense. The rumored specifications and leaked CAD renders of the Galaxy Note 20 “+” model were very similar to the S20 Ultra. The upcoming Galaxy Note 20 Ultra will likely be using the 108MP Samsung ISOCELL Bright HM1 main sensor (like the S20 Ultra) along with a 12MP ultrawide sensor. The telephoto camera is rumored to be changed to a 13MP periscope camera with a maximum digital zoom level of 50x in contrast to the 48MP ultrawide sensor and maximum 100x digital zoom of the S20 Ultra. The Galaxy Note 20 Ultra will also have a similar 6.9″ WQHD+ AMOLED display with 120Hz refresh rate support, but the Note 20 Ultra is rumored to support running at both 120Hz refresh rate and WQHD+ resolution at the same time. It seems like Samsung is serious about using this Ultra branding on its most expensive and “Ultra” flagships.

I’m hopeful that Samsung isn’t giving up on their premium Ultra branding despite prior reports to the contrary. The Ultra branding has quickly become recognized after how hard Samsung pushed it with the S20 series, so I’m hoping the new Note 20 “Ultra” will also feature boundary-breaking tech.


Source: Bluetooth Launch Studio ||| Via: @_the_tech_guy

Featured image credits: @OnLeaks/Pigtou

The post Samsung may continue its Ultra branding with the Galaxy Note 20 series appeared first on xda-developers.



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