LightBlog

lundi 1 juin 2020

Google Chrome’s bottom tab “Duet” experiment has likely been killed off

In a bid to make Chrome easier to use on large screen devices, Google replaced Chrome Home with the Chrome Duplex split toolbar UI early in 2018. The new UI, which was later renamed Chrome Duet in order to avoid confusion with Google Duplex, moved some UI elements closer to the bottom of the display in order to make them easily accessible on modern devices. The latest update for the feature arrived late last year when Google started testing a new Duet-friendly UI for tab groups. However, it now seems like Google’s Duet experiment wasn’t successful as the company has done away with it in the latest Chrome beta release.

As per a recent report from Android Police, the Chrome 84 beta release has removed the two feature flags for Duet: #enable-duet-tabstrip-integration and @enable-chrome-duet. The flags can still be seen in the flags list in Chrome 84 if you enable #temporary-unexpire-flags-m82 and #temporary-unexpire-flags-m83, but enabling them doesn’t make any difference. The unexpire flags also have a description that reads, “These flags will be removed soon,” which suggests that Chrome Duet has been completely shelved by the company.

Google Chrome Duet on Chrome 83

For the unaware, Chrome Duet in its current form adds a toolbar to the bottom of the screen that includes a few shortcut buttons. While the address bar remains at the top of the screen, it can be opened by tapping the search icon in the bottom bar. These features make Chrome slightly easier to use on large devices. However, with the latest Chrome beta update, users won’t be able to enable these features in the browser. It’s quite possible that Google might, once again, release a new UI layout for the purpose with a new flag. But for now, we have no information regarding any such upcoming changes.

Source: Reddit

Via: Android Police

The post Google Chrome’s bottom tab “Duet” experiment has likely been killed off appeared first on xda-developers.



from xda-developers https://ift.tt/36Nuc9A
via IFTTT
Publié par à Aucun commentaire:
Libellés : ,

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
Publié par à Aucun commentaire:
Libellés : ,

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
Publié par à Aucun commentaire:
Libellés : ,

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
Publié par à Aucun commentaire:
Libellés : ,

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
Publié par à Aucun commentaire:
Libellés : ,

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
Publié par à Aucun commentaire:
Libellés : ,

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
Publié par à Aucun commentaire:
Libellés : ,
Inscription à : Articles (Atom)