LightBlog

mardi 2 juin 2020

Samsung rolls out home screen widgets for the Galaxy Buds and Buds+

The Galaxy Buds and Galaxy Buds+ plugins for the Samsung Galaxy Wearable app are reportedly getting an update that brings new home screen widgets to help users easily control the TWS earbuds. As per a recent post on Reddit, there are two new widgets for each pair of wireless earbuds. The first widget shows the current battery level of both the earbuds and the charging case, while the second widget allows you to easily turn on the Ambient Sound mode and lock the touchpad.

As you can see in the attached image, both the new widgets have two different themes —  white and black — and the Widget settings also give you the option to manually set the opacity of the widgets. Additionally, the Widget settings also include a toggle that will automatically match the widget’s theme with the system theme. This means that whenever you switch on the One UI dark mode on your Samsung device, the widget will automatically switch to the black theme and vice-versa.

In case you haven’t received the new update yet, you can follow the Play Store link below and download the latest Galaxy Buds or Galaxy Buds+ plugin on your device. Max Weinbach from our team has already received the update on his device and has shared the screenshot included in the featured image. As a few comments on the original Reddit thread point out, the update isn’t available for all users right now and you might have to wait for some time before the update finally arrives for your device.

Galaxy Buds Plugin (Free, Google Play) →

Galaxy Buds+ Plugin (Free, Google Play) →


Source: Reddit

The post Samsung rolls out home screen widgets for the Galaxy Buds and Buds+ appeared first on xda-developers.



from xda-developers https://ift.tt/30094eQ
via IFTTT

[Update: Possibly this month] Brave Browser Android dev says the team would like to add extension support in 2020

Update 1 (06/02/2020 @ 02:30 AM ET): Brave Browser might finally add extension support this month. Scroll to the bottom for more information. The article as published on December 17, 2019, is preserved below.

When it comes to web browsers, Android offers users a variety of different options. Along with Google Chrome, Android users have access to a plethora of great third-party browsers like Kiwi, Vivaldi, and Brave. These browsers offer some amazing features like native ad-blocking, Chrome extension support, cryptojacking protection, and more. But what helps Brave stand out is that it gives you the option to support your favorite websites (like XDA) by watching ads. For this reason alone, Brave ranks among the best third-party browser apps out there. However, its lack of extension support forces several users to rely on other browsers as well. But this might change in the near future.

In a recent comment on Reddit, a developer from Brave Browser’s Android team has revealed that the browser might get extension support next year. The comment was posted in response to a query submitted by a user and in response, the developer wrote, “We would like to add extensions support on Q1-Q2 2020”. While this still doesn’t confirm that the browser will get extension support in the first half of next year, it does reveal that the team is willing to work towards adding the feature. According to the official Brave Browser FAQ, the company didn’t add extensions support in the browser as it introduces API and performance limits while also raising security concerns. Nonetheless, it’s great to see that the team is willing to work on bringing a highly requested feature to the browser.

Source: Reddit


Update: Brave Browser could get extensions support on Android as early as this month

Developers working on Brave Browser have a working prototype of the browser with extension support. They are targeting a release as early as the end of this month.

The post [Update: Possibly this month] Brave Browser Android dev says the team would like to add extension support in 2020 appeared first on xda-developers.



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

Nubia Play may launch internationally as the Red Magic 5G Lite

Shortly after the launch of the flagship Red Magic 5G in March this year, Nubia unveiled a new mid-range gaming smartphone called the Nubia Play 5G in China. Powered by Qualcomm’s Snapdragon 765G chip, the Nubia Play 5G featured a 6.65-inch FHD+ Super AMOLED display with an impressive 144Hz refresh rate and 240Hz touch sampling rate. The device also packed in up to 8GB of LPDDR4z RAM and up to 256GB of UFS 2.1 storage, along with a massive 5,100mAh battery featuring 30W fast charging support.

The Nubia Play 5G went on sale in China at a starting price of CNY 2,399 (~$340) on April 24th, but the company has still not revealed any official information about its international release. However, thanks to a recent tweet from leakster Sudhanshu Ambhore (@Sudhanshu1414), we now know that the device will soon be launched internationally as the Red Magic 5G Lite. The tweet cites certification listings of the device spotted on the Global Certification Forum (GCF) and Eurasian Economic Commission (EEC), which confirm that Nubia will be launching the mid-range Nubia Play 5G as a “Lite” variant of its flagship Red Magic 5G.

Since the device has already received certification for an international release, we expect Nubia to officially launch the Red Magic 5G Lite in the next couple of weeks. Based on the device’s pricing in Nubia’s home market, we suspect that the Red Magic 5G Lite might be launched at a starting price of around $350-400 internationally.

Nubia Red Magic 5G Lite specifications

Specification Nubia Red Magic 5G Lite
Dimensions and Weight
  • 171.7 x 78.5 x 9.1 mm
  • 21og
Display
  • 6.65″ FHD+ (2340 x 1080) Super AMOLED;
  • Notchless display with thin top bezel
  • 144Hz refresh rate
  • 240Hz Touch Response Rate
  • 4096 auto brightness adjustment levels
SoC Qualcomm Snapdragon 765G:
  • 1x Kryo 475 (ARM Cortex-A76-based) Prime core @ 2.4GHz
  • 1x Kryo 475 (ARM Cortex-A76-based) Performance core @ 2.2GHz
  • 6x (ARM Cortex-A55-based) Efficiency cores @ 1.8GHz

Adreno 620 GPU

RAM and Storage
  • 6GB LPDDR4X + 128GB UFS 2.1
  • 8GB + 128GB
  • 8GB + 256GB
Battery & Charging
  • 5,100 mAh battery
  • 30W fast charging via USB PD
Rear Camera Photo:
  • Primary: 48MP Sony IMX582, f/1.79
  • Secondary: 8MP wide-angle
  • Tertiary: 2MP Super Macro
  • Quaternary: 2MP Depth Sensor
Front Camera 12MP selfie shooter
Other Features
  • 3.5mm headphone jack
  • Bluetooth 5.1
  • Dual-frequency GPS
  • 5G SA/NSA
  • Pressure Sensitive capacitive buttons on side frame
  • In-Display Fingerprint Scanner
Android Version Nubia UI 8.0 based on Android 10

Source: GCF, EEC

The post Nubia Play may launch internationally as the Red Magic 5G Lite appeared first on xda-developers.



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

lundi 1 juin 2020

Unofficial LineageOS 17.1 brings Android 10 to the Realme 1

As most of you should already know, the Realme brand has its roots in OPPO, which is itself owned by BBK Electronics. The Realme 1, the first smartphone under the Realme brand from before the company spun off from OPPO, ran ColorOS, a customized Android software designed by none other than OPPO itself. To differentiate their devices from their parent company, Realme introduced a new interface called “Realme UI” which is built on top of Android 10. However, the OEM has no plans to deliver the Realme UI/Android 10 update to the Realme 1, although the phone is still getting regular security updates on its Android 9 Pie-based ColorOS 6 firmware.

Realme 1 XDA Forums

As expected, though, XDA’s aftermarket development community has come to the rescue. XDA Senior Member Invincible-Venom has compiled an unofficial version of LineageOS 17.1 for the Realme 1 which brings a close-to-stock Android 10 experience to owners of this phone. The availability of the kernel source code as well as the existence of an official bootloader unlocking method certainly helped the developer in this venture. Apart from a few quirks such as broken USB tethering and SELinux set to permissive (which is a major security issue we hope to see resolved soon), the current builds can be used as a daily driver.

realme_1_unofficial_lineageos_17.1It is worth mentioning that this particular build of LineageOS is a source-built ROM and not a Generic System Image (GSI), though arguably many custom ROMs these days have roots in GSI. Both the CPH1859 and the CPH1861 variants of the Realme 1 are supported by the developer. You need to flash the latest version of the stock firmware (CPH1861EX_11_C.49) and use the TWRP compiled the same developer before installing this ROM. There are some known incompatibility issues with Magisk, so users are advised to stick with Magisk versions 20.1 or 20.3.

Unofficial LineageOS 17.1 for the Realme 1: Download ||| XDA Discussion Thread

The associated device tree and the vendor tree are available on GitHub. A built-in OTA updater was initially planned as well, but the developer has abandoned it for the time being. Now that a somewhat-stable version of LineageOS 17.1 for the Realme 1 is here, we hope to see the fruits of this effort available to the community in the near future.

The post Unofficial LineageOS 17.1 brings Android 10 to the Realme 1 appeared first on xda-developers.



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

At least 3 Chromium-based browsers may enable extensions support thanks to Kiwi Browser

One of the advantages of open source software is the ability to allow forks of the main projects to exist. These forks can then take a different form to gain different features. If things go right, these changes and bug fixes can also make their way back upstream to the original project and then passed on to all other projects downstream that rely on it. Such is the beauty of open-source, and we are likely to see an example play out in a noticeable manner on our phones very soon. The code submitted upstream by the developer of the recently open-sourced Kiwi Browser will now make it easier for Chromium forks to enable extension support on mobile.

The Chromium browser is an open-source project that serves as the basis for a lot of web browsers, including Google Chrome, Microsoft Edge, Vivaldi, Brave, and Kiwi too. Most of these Chromium-based browsers offer a handful of additional features over the base, but there are some that radically change the experience. Kiwi Browser by XDA Senior Member arnaud42 falls in the latter category, with features like a built-in content blocker, dark mode, background video playback, AMP skipper, and the fact that it was one of the first Chromium-based browsers for Android that supported Chrome, the other being Yandex Browser. Earlier this year, Kiwi Browser went open-source, allowing other Chromium projects to include the code that enables extension support into their own projects. At the time of the announcement, the developer had mentioned that they were already working with other browser developers to help them integrate some of Kiwi’s Browser functionality.

As spotted by Dinsan Francis, arnaud42 had started a bug report on the Chromium Gerrit in order to make it easier for Chromium-based projects to enable extensions. The code proposed in the bug report would make it easier for Chromium forks to enable extensions if they want to, without affecting Google Chrome for Android. The submitted code has not been merged yet into Chromium, and to clarify, there is no evidence to suggest that Google will be enabling extension support for Chrome for Android. But still, there are “at least three variants of Kiwi” that are being worked on with extensions support.

As a result we increase maintainability for downstream players who do support extensions or may be tempted to do so (example: Microsoft, and of course, Kiwi Browser, but there are at least 3 variants of Kiwi that are getting born right now, including with a very very large OEM)

We asked the developer to elaborate on the projects being referred, but they mentioned that they would be unable to name them. Irrespective of the exact variants, this presents itself as good news for consumers as they will soon have more browser alternatives with extension support, and in turn, would prompt others to also consider its implementation.

Interestingly, the Chromium Gerrit commit that would change the Chromium build process to make it easier to rebase Chromium with extensions enabled was submitted by a Samsung engineer. However, we do not think Samsung would be the “large OEM” mentioned by arnaud42 because the Samsung Internet browser already supports extensions, albeit in a limited capacity as you can only install approved extensions from the Galaxy Store. Samsung would still be interested in the code that arnaud42 submitted, because it would make it easier for them to rebase the Samsung Internet browser with newer Chromium versions, such as how they recently updated Samsung Internet from Chromium 71 to Chromium 79.

Kiwi Browser - Fast & Quiet (Free, Google Play) →

Kiwi Browser (Free, XDA Labs) →


Sources: Chromium Bug Tracker, Chromium Gerrit
Story Via: @_dinsan

The post At least 3 Chromium-based browsers may enable extensions support thanks to Kiwi Browser appeared first on xda-developers.



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

Xiaomi Redmi 9 is launching soon – Here’s what we know so far

Following the launch of the Redmi Note 9 series earlier this year, Xiaomi’s budget-friendly sub-brand is now prepping up to launch the entry-level Redmi 9 series. While Xiaomi hasn’t released any official information about the Redmi 9 series yet, we do have some key details about the upcoming devices, including live images, specifications, and pricing. Here’s everything we know about the Redmi 9 series so far:

Leaked live images

Live images of the upcoming Redmi 9 have surfaced online, revealing some key aspects of its design. The images in question were shared by leakster Sudhanshu Ambhore (@Sudhanshu1414), which reveal that the Redmi 9 will feature a vertically-oriented triple camera setup on the back with the fingerprint sensor right underneath.

The device will also feature a fourth sensor within a separate module with the LED flash. Both the primary and secondary camera modules are within a circular design element on the back, which looks to have a different finish compared to the rest of the back panel.

The images showcase two color variants of the device — purple and green — and also shed light on the camera specifications. As per the leakster, the Redmi 9 will feature a 13MP primary sensor, an 8MP wide-angle camera, a 5MP macro camera, and a 2MP depth sensor.

Redmi 9 leaked image Weibo

Additionally, another leaked image of the Redmi 9 has been shared on Chinese social media platform Weibo, which features the same camera module. However, the device itself is enclosed in a case in the third image, so we don’t get a clear look at its design.

Redmi 9 series certification listings

Along with the aforementioned live images, the Redmi 9 series has also been spotted in Bluetooth SIG and Wi-Fi Alliance certification listings. As per the listings, the devices in the Redmi 9 series will have the following model numbers:

  • M2004J19AG
  • M2004J19PI
  • M2004J19C
  • M2004J19I
  • M2004J19G

Even though the listings don’t reveal much about the specifications, they do confirm that the devices will run MIUI 11 based on Android 10 out of the box and that some variants of the Redmi 9 will include NFC support.

Leaked specifications

XDA Senior Member and noted Xiaomi tipster kacskrz tells us that the Redmi 9 goes by the code-name “lancelot”, with other variants also going by the code-names “galahad” and “shiva.” All of the three variants are based on MediaTek chipsets, with Sudhanshu claiming that the device will be powered by the MediaTek Helio G80 chipset.

In a separate tweet regarding the devices, he also reveals the rumored specifications of all the devices in the Redmi 9 series, along with their respective pricing. As per the tweet, the Redmi 9A will feature the MediaTek Helio G25 chip, coupled with 3GB RAM and 32GB storage. The device will feature a 5,000mAh battery and will be priced between €100-120.

The Redmi 9C, on the other hand, will be available in two variants — with and without NFC — and will be powered by the MediaTek Helio G35, coupled with 3GB RAM and 64GB storage. The device will also feature a 5,000mAh battery and will be priced between €130-150. And finally, the regular Redmi Note 9 will be powered by the MediaTek Helio G80, along with 4GB RAM and 64GB storage. The device will feature a 5,000mAh battery and will be priced between €160-180.

Several Geekbench listings for “lancelot” corroborate these specifications and further reveal that at least one model of the device will have 3GB of RAM. Kacskrz also revealed that he has spotted evidence of an EEA/RU firmware for “lancelot,” which means that the device might be launched internationally.


Source: Weibo, Geekbench, Bluetooth SIG, Wi-Fi Alliance

Featured image: Xiaomi Redmi 8A Dual

The post Xiaomi Redmi 9 is launching soon – Here’s what we know so far appeared first on xda-developers.



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

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.

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, 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