LightBlog

mardi 21 avril 2020

Xiaomi India clarifies that bootloader unlocking does not void warranty

Xiaomi and its sub-brand Redmi have always been preferred for the excellent value their phones offer. But that is not the only reason why the community at XDA-Developers is fond of the brand. The other reason power users and developers have been inclined towards Xiaomi’s smartphones is that the company has allowed users to unlock their phone’s bootloader without invalidating the phone’s warranty. This policy has attracted a lot of users to partake in modifying or replacing the pre-loaded software on their Xiaomi and Redmi devices.

A recent tweet from Redmi India, however, took us by surprise as it stated that unlocking the bootloader on Redmi – and presumably, Xiaomi – phones will now void the phone’s warranty.

Does unlocking bootloader void warranty of your Xiaomi or Redmi phone?

Tweet from Redmi India (now deleted)

A few YouTube videos also popped up on the topic, seemingly affirming through other customer support mediums that simply unlocking the bootloader of the device will violate the warranty clause. While the tweet was deleted shortly after we took note, it did sow the seeds of doubt and confusion. Thus, we decided to reach out to Xiaomi India in order to set the record straight on the matter.

Does unlocking the bootloader of your Xiaomi or Redmi phone void your warranty?

As per the official response we have received from Xiaomi India, the mere act of unlocking the bootloader does not void the warranty of your Xiaomi or Redmi phone. However, if you do manage to hard brick your phone once/after you have unlocked the bootloader, then you no longer have a warranty that can be claimed for the phone.

Unlocking of the bootloader is made available to make sure that MIUI developer ROMs can be tested by users and will be covered under warranty.

Bootloader unlocking does not inherently void your hardware warranty. But a case where the unlocking results in a brick which cannot be fixed via software, the warranty will be void.

Xiaomi India spokesperson

As the statement explicitly says, the warranty remains intact so long as a software fix can work on the bootloader unlocked phone. By extension, if you hard brick your device and it needs a hardware fix to be brought back to life, perhaps in the form of EDL pin-shorting or worse, a motherboard replacement, you will be out of luck and warranty. If any software fixes are needed, Xiaomi India will charge you a nominal amount (currently ₹150 plus taxes) under the general maintenance clause in the official warranty, in order to revert your phone back to the stable ROM available for the phone in that region.

This policy is applicable to Xiaomi phones in India under both the Mi and Redmi sub-brand. Other regions could possibly have variations to this policy. And before you ask, POCO is excluded from the scope of this article and this policy entirely as it operates as an independent unit and has its own separate policy.

After deleting the tweet, Xiaomi also updated their statement with a fresh response:

Thus, as per our understanding of the situation, if you have any manufacturing defect in the form of faulty hardware that is otherwise covered under the company’s warranty clauses, you will be allowed to avail warranty regardless of your bootloader status. However, if the non-functional hardware is a result of your own doing (maybe you flashed the wrong file to the wrong partition and hard-bricked your phone), then you are out of luck.

When is your warranty void?

The condition in which you might end up losing your warranty due to an unlocked bootloader is when you set out to further modify the software and end up with a hard bricked phone. A hard brick is a state when the phone cannot boot and it is impossible to flash the stock firmware to restore the phone. This could be the case when you’re stuck on the EDL Mode (Emergency Download Mode) on Xiaomi or Redmi devices with Qualcomm Snapdragon chipsets or the Download Mode on Xiaomi or Redmi devices with MediaTek chipsets.

Qualcomm’s EDL Mode, as well as its MediaTek counterpart, is a special boot-mode that can be used to recover or modify a phone by sidestepping the standard bootloader. Accessing this mode isn’t easy for average users as it requires a special cable or short-circuiting JTAG pins on a phone’s logic board. Usually, this process is used as a last resort when standard fixes don’t work and is thus, not advised without the proper know-how. While its utility is to revive a dead phone, there have also been instances of unauthorized resellers installing malware on a phone by going the EDL route, prompting Xiaomi to block users from accessing this mode.

Does unlocking bootloader void warranty of your Xiaomi or Redmi phone?

Error message on flashing through Xiaomi’s modified SP Flash Tool

Ever since Xiaomi took the decision to block the EDL mode back in 2018, fixing phones through the EDL mode required an Authorized Mi Account alongside the MSMDownload Tool for Qualcomm Snapdragon devices or SP Flash Tool for MediaTek devices. However, an Authorized Mi account is exclusively available with official Xiaomi service center partners. Thus, users with hard bricked devices have no other option but to take their phones to the service center for repairs. And if they do so, their warranty will be deemed void. We understand the security concern behind needing Authorized Mi Accounts, but our opinion is that Xiaomi could use a better alternative than Authorized Mi Accounts for unbricking its devices.

It is, however, worth noting that this warranty clause has been the company’s stance on hard bricks over unlocked bootloaders since forever. The policy for nulling the warranty should not be mistaken as new, as this has always been the case and the community is largely aware and respectful of the same. Xiaomi also keenly exercises control over bootloader unlocking through the Mi Flash Tool and ties the unlock action and the IMEI to the user’s Mi Account—so they do have a way to determine if the bootloader is unlocked or not, even on a dead phone.

Our advice: Exercise caution

Xiaomi is generous for allowing users to unlock their bootloaders without any impact on the warranty. Many OEMs allow users to unlock their bootloaders, but the mere act of unlocking also voids the warranty from that point forward—so you will be stuck even if you have a genuine factory-origin hardware manufacturing defect. Many others simply do not allow bootloader unlocking at all, so you have zero choices in such a scenario. Bootloader unlocking is often the first step to installing a custom ROM or other system-level mods, so having this choice is important for power users like us. Xiaomi is, thus, one of the better OEMs out there in this regard.

It is also rightful on Xiaomi’s part to not to want to bear the cost of a customer’s misadventures and ill-informed experiments. Bootloader unlocking leaves the phone open to a plethora of security issues, and hence, is advisable for experienced users only. You should only venture forward if you understand what you are doing. If you’re fiddling with your Xiaomi or Redmi devices, or any other device for that matter, please do so only after understanding the risks.

The post Xiaomi India clarifies that bootloader unlocking does not void warranty appeared first on xda-developers.



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

Realme X2 Pro Custom Developments: LineageOS 17.1, Official TWRP, AOSiP, and more

Realme’s first true flagship, the Realme X2 Pro (our review) packs in a Snapdragon 855+ chipset, a high refresh rate 90Hz display, and an impressive quad-camera array. While redefining the benchmark of affordable flagships, the company didn’t forget to publish the kernel source code and the official bootloader unlock utility for the device in an effort to boost the aftermarket development scene. The stable version of Android 10-based Realme UI also landed on various regional variants of the phone across the globe at the beginning of this month. In case you are not satisfied with Realme’s custom skin and want to give vanilla Android a try, here are some custom ROMs that you can flash right now.

Realme X2 Pro XDA Forums ||| Buy Realme X2 Pro from Flipkart

Unofficial LineageOS 17.1

XDA Recognized Developer karthick mostwanted is currently maintaining the unofficial build of LineageOS 17.1 for the Realme X2 Pro. The ROM has SELinux in permissive mode and VoLTE activation requires flashing a separate zip, but otherwise, it’s quite stable to be a daily driver while featuring a plethora of device-specific feature control, such as DC dimming and Game mode. Do note that you have to downgrade to ColorOS 6.1 firmware before flashing this ROM.

Download unofficial LineageOS 17.1 for the Realme X2 Pro

Unofficial AOSiP 10

If you’re looking for an AOSP-based ROM that offers some useful UI/UX customizations on top of stock Android, you can also opt for the unofficial AOSiP 10 ROM by XDA Senior Member 4j17h.  From status bar customization to lock screen personalization options, you can tune various aspects of this ROM. Similar to the LineageOS 17.1 build, AOSiP 10 for this particular phone is still not compatible with Realme UI modem and bootloader, thus a downgrade is absolutely necessary before flashing.

Download unofficial AOSiP 10 for the Realme X2 Pro

Official/unofficial TWRP

A custom recovery like TWRP is the primary prerequisite of flashing all these custom ROMs. Fortunately, the TWRP project has had official support for this device since December 2019. The maintainer, XDA Senior Member mauronofrio, is also offering bleeding edge unofficial builds of TWRP with experimental features in the forum thread linked below.

Download TWRP for the Realme X2 Pro: Official || Unofficial

The post Realme X2 Pro Custom Developments: LineageOS 17.1, Official TWRP, AOSiP, and more appeared first on xda-developers.



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

[Update: Chrome Flag] Google Chrome could be getting its own Live Caption feature

Update 1 (4/21/2020 @ 6:20 PM EST): An option to toggle Live Captions is now available in the latest Chromium builds. Although the feature does not work yet, it should soon start working with more code commits and eventually make its way to a stable Google Chrome build.

Back at Google I/O last year, the company announced a new tool in Android 10 called Live Caption. As the name suggests, the tool is designed to automatically provide captions for audio that’s playing on your device. It works with videos, podcasts, audio messages, and other supported media, making it a great accessibility tool for the hearing impaired. On top of that, the tool can also be used to help improve the video watching experience in loud environments. Now, according to a commit spotted on the Chromium Gerrit (via ChromeUnboxed), it seems like the Google Chrome team is working to bring the feature to the browser.

The commit in question is for the SODA (Speech On-Device API) service which is crucial to get live captions to work on the browser.  The description of the commit reads, “This CL creates a sandboxed service that hosts the Speech On-Device API (SODA). It contains the components required to launch the service from the renderer process, but the implementation of the service itself is stubbed out. The design document for the feature is located at: go/chrome-live-captions.” SODA is a first-party product made by Google’s Speech team that transcribes audio into text. The name of the design doc references “Live Caption,” and several methods and constants in one of the Chromium commits also hint at this.

In one of the comments, a Googler explicitly compares this feature to the one on Android and says, “I think we should use “Live Captions” when using a name for the feature to match what’s done on Android.” However, Google wants SODA to be used for more than just Live Captions, based on a comment from another Googler who states, “Based on our discussion with the ChromeOS team, it sounds like they have other speech recognition scenarios they may want to build in the future. The benefit of naming this SODA is that other features can use this component, though it could be seen as a leaky abstraction.”

Google has currently released no information about the upcoming feature but based on the aforementioned information we can safely assume that it will work much like Android 10’s Live Caption feature once released. As of now though, the feature is still in its early stages of development and it will be quite a while before it makes it to a stable release of Google Chrome.


Update 1: Google Chrome Flag

When this article was first published back in mid-February, we only saw hints that Live Caption functionality would make its way to desktop Chrome. Now, a commit has been merged that brings a Google Chrome flag to the mix. This flag is intended to test the feature in Canary builds by adding an easily controllable toggle in Chrome’s settings. The toggle can be enabled by first enabling the flag at chrome://flags#enable-accessibility-live-captions and then enabling the “Live Captions” toggle in Chrome’s Accessibility settings. The captions UI can then be customized in Windows 10 settings. The captions box can also be moved around on the screen. Currently, the captions box only displays a single static string, so it isn’t currently working. We will monitor this feature and report back when it starts working, though.

The post [Update: Chrome Flag] Google Chrome could be getting its own Live Caption feature appeared first on xda-developers.



from xda-developers https://ift.tt/39tu2nP
via IFTTT

Google is rolling out “Hey Google” sensitivity controls for Google Assistant devices

While Google Assistant-enabled smart speakers and smart displays can be really useful for simple tasks like setting an alarm, checking the weather, or controlling your smart home devices, they still have a long way to go when it comes to nailing speech recognition. I’m sure many of you have faced issues getting your Google Assistant devices to recognize your voice from time-to-time. Having to yell “Hey Google” multiple times to start a voice command can be really annoying. Likewise, it can be equally as annoying when your smart speaker starts listening even though you haven’t actually spoken the hotword. A one-size-fits-all hotword sensitivity threshold clearly isn’t working, so that’s why Google is finally starting to roll out “Hey Google” sensitivity controls.

Back in September, Google announced new privacy-centric features for Google Assistant. One of the most exciting new features they announced is new sensitivity options for the “OK/Hey Google” voice command. Google did not announce when the feature would go live, but in the latest version of the Google Home app (version 2.21.1.10), we managed to surface the new “Hey Google” sensitivity option under Device settings for Google Assistant-enabled smart speakers and smart displays. Tapping this option opens the Google App with the option to control the hotword sensitivity. Users can pick from “Least Sensitive,” “Default,” or “Most Sensitive.” Only the primary account can change the setting for a particular smart speaker or smart display.

Hey Google hotword sensitivity in Google Home app Hey Google hotword sensitivity in Google App

A Google spokesperson told The Verge that this “Hey Google” hotword sensitivity feature is starting to “roll out gradually,” which likely means it’ll arrive as a server-side update for most users. Keep an eye out for the “Hey Google” sensitivity option to appear under “Device settings” in the Google Home app in the coming days and weeks. You can download the latest versions of Google Home and the Google App from the Google Play Store links below.

Google Home (Free, Google Play) →

Google (Free, Google Play) →

The post Google is rolling out “Hey Google” sensitivity controls for Google Assistant devices appeared first on xda-developers.



from xda-developers https://ift.tt/34W82RF
via IFTTT

Epic Games gives in and finally puts Fortnite on the Google Play Store

Fortnite is an incredibly popular battle royale game that’s available on PC, game consoles, and mobile devices, but unlike most other Android games, Fortnite hasn’t been available on the Google Play Store. The game first launched for Android devices in August of 2018 as a 3-day Samsung Galaxy Apps store exclusive after which the game became available for everyone through Epic Games’ website. Epic Games decided to forego the Play Store to avoid giving Google a 30% cut on revenue, but now, the company has decided to give in and release the game on Google Play.

This shift comes 20 months after launching the Android client outside of the Google Play Store. In the past, Epic Games’ CEO Tim Sweeney has heavily criticized both Google and Apple for their revenue cuts. When Epic Games first launched Fortnite outside of Google Play, Tim Sweeney justified the decision as follows:

“The 30 percent store tax is a high cost in a world where game developers’ 70 percent must cover all the cost of developing, operating, and supporting their games…There’s a rationale for this on console where there’s enormous investment in hardware, often sold below cost, and marketing campaigns in broad partnership with publishers…30 percent is disproportionate to the cost of the services these stores perform, such as payment processing, download bandwidth, and customer service.” – Tim Sweeney, CEO of Epic Games, speaking to The Verge in 2018

Earlier this year, we learned that Epic Games had requested that Google exempt them from a 30% revenue cut, but this petition was denied by Google. It seems that Epic Games has now reversed course, offering up Fortnite on the Play Store without reducing or eliminating Google’s revenue cut. In a statement, Epic Games told The Verge and Polygon that the company “[came] to a basic realization…[that] Google puts software downloadable outside of Google Play at a disadvantage, through technical and business measures such as scary, repetitive security pop-ups for downloaded and updated software, restrictive manufacturer and carrier agreements and dealings, Google public relations characterizing third party software sources as malware, and new efforts such as Google Play Protect to outright block software obtained outside the Google Play Store.” While we haven’t seen evidence that Google has directly targeted Epic Games and Fortnite, Epic Games feels that the cards are stacked against them in the Android ecosystem. For what it’s worth, Epic Games still hopes that Google will reconsider its revenue cut, stating that “we hope that Google will revise its policies and business dealings in the near future, so that all developers are free to reach and engage in commerce with customers on Android and in the Play Store through open services, including payment services, that can compete on a level playing field.”

Here’s the company’s full statement:

After 18 months of operating Fortnite on Android outside of the Google Play Store, we’ve come to a basic realization:

Google puts software downloadable outside of Google Play at a disadvantage, through technical and business measures such as scary, repetitive security pop-ups for downloaded and updated software, restrictive manufacturer and carrier agreements and dealings, Google public relations characterizing third party software sources as malware, and new efforts such as Google Play Protect to outright block software obtained outside the Google Play store.

Because of this, we’ve launched Fortnite for Android on the Google Play Store. We’ll continue to operate the Epic Games App and Fortnite outside of Google Play, too.

We hope that Google will revise its policies and business dealings in the near future, so that all developers are free to reach and engage in commerce with customers on Android and in the Play Store through open services, including payment services, that can compete on a level playing field.

Fortnite Mobile is available today on the Google Play Store. You can download the game through the below link. The game can still be downloaded through the Epic Games website, but it’s unclear if this will remain unchanged or if Epic Games will redirect users to the Play Store listing. It’s also unclear what Epic Games plans to do with the Epic Games Store app for Android which still only lists Epic’s own Battle Breakers title.

Fortnite (Free+, Google Play) →

The post Epic Games gives in and finally puts Fortnite on the Google Play Store appeared first on xda-developers.



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

Google Duo adds AV1 support to improve video calls, Moment screenshot captures, and saving messages

Millions of people are stuck at home due to shelter-in-place or stay-at-home orders, making it impossible for many people to see their friends and family face-to-face. Fortunately, we live in an age where it’s possible to see each other virtually using a video calling app. Google Duo is a popular video and audio calling application because it’s part of Google’s core mobile services on top of being a great, easy-to-use application. Now, it’s getting even better with the addition of new features, both user-facing and at the back end.

AV1 Video Codec for Video Calls

Earlier this month, Google detailed how their WaveNetEQ machine learning model can improve audio quality in Duo. Today, Google has announced they’re enabling the use of the AV1 (AOMedia Video 1) video codec for video calls. This will improve video call quality and reliability, especially if you have a low bandwidth connection. AV1 is a royalty-free video codec that’s designed to replace H.264 as the codec of choice for online streaming and media consumption. Videos encoded in AV1 lose less detail during compression when compared to videos encoded in H.264. The one downside of the AV1 video codec is that no mobile processor, except for the MediaTek Dimensity 1000, supports hardware decoding for it. That means Google Duo video calls encoded in AV1 may be more performance-intensive to playback and hence drain more battery.

Side by side comparison of an incoming video call at 30kbps with Google’s new AV1 (AOMedia Video 1) video codec technology on the left.

It is unclear if AV1 will be used for all video calls or only for low bandwidth situations.

“Duo Moments”

Back in December, we spotted evidence that Google would allow users to capture a side-by-side screenshot of the video call as a “Moment.” This feature is now live in the latest Google Duo release. When a person captures a Duo moment, every participant in the video call will be notified and the image saved to each participants’ image library. To enable Moments, go to Settings > Call settings and turn on Duo moments. All video call participants must have the feature enabled to capture a Duo moment, though users can still take screenshots of the video call without having Duo moments enabled.

Saving Messages

Google Duo allows users to send personalized voice and video messages to contacts when the recipient isn’t able to answer a call. Google has expanded upon the Messages feature since its initial release by adding emoji reactions, AR effects, notes and doodles, and more. Soon, users will be able to save messages that are sent to them. Previously, messages would automatically expire after 24 hours.

We’ve recently learned the company is planning on rolling out closed captions for Messages, but they have not yet made an announcement about this feature.


In late March, Google increased the group call size limit to 12 participants. In the coming weeks, Google will increase this limit even further. We’ll update you when we spot new features or if Google makes any announcements. You can download the latest version of the Google Duo app from the Play Store link below.

Google Duo - High Quality Video Calls (Free, Google Play) →

The post Google Duo adds AV1 support to improve video calls, Moment screenshot captures, and saving messages appeared first on xda-developers.



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

T-Mobile expands its 5G network with Sprint’s mid-band spectrum, nationwide 5G coming for Sprint customers

T-Mobile and Sprint officially completed their merger at the beginning of this month. While some of the eventual benefits will take a while to be put in motion, others can be rolled out sooner. Today, T-Mobile is announcing a number of immediate changes, including expanding its network with Sprint’s spectrum.

First, T-Mobile is expanding its 5G network with the addition of Sprint’s 2.5GHz mid-band spectrum. This is now live in parts of Philadelphia and will be coming soon to parts of New York City. Once live in NYC, it will be the first city with low-band, mid-band, and mmWave 5G. Mid-band 5G, as you might expect, is in-between the low-band and mmWave frequencies in terms of coverage area and maximum speeds. T-Mobile boasts peak download speeds of 600Mbps with this 2.5GHz spectrum. The Sprint OnePlus 7 Pro 5G currently takes advantage of the mid-band frequencies for 5G connectivity, but soon more 5G-capable devices will benefit from this expanded network, including the upcoming OnePlus 8 5G.

Speaking of which, the second announcement from T-Mobile is that Sprint customers with the Samsung Galaxy S20 5G will get access to T-Mobile’s sub-6GHz (600MHz) low-band 5G network in more than 5,000 locations across the United States. Support for connecting to T-Mobile’s 5G network will be rolling out later this month. T-Mobile has also announced that they are expanding their low-band 5G network to Detroit, St. Louis, and Columbus, Ohio.

Today’s news isn’t only about 5G, though. Perhaps the most important news of the day is that Sprint customers can now roam on T-Mobile’s LTE network. This means that Sprint customers will immediately have more than double the LTE sites, providing much better coverage in some areas. If you’re a Sprint customer who previously had spotty LTE coverage, things could get a lot better now. These announcements are just the beginning of what’s in store for the carrier following the Sprint merger.


Source: T-Mobile

The post T-Mobile expands its 5G network with Sprint’s mid-band spectrum, nationwide 5G coming for Sprint customers appeared first on xda-developers.



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