He said that when the service centre was alerted about the repeated issue, he was told to wait for one-two months for a software fix. While most users were facing problems while typing on their units, one user also complained that his Redmi Note 10 had become very slow.Ī user who claims to have got his unit replaced after repeated problems said that the new unit also had the same touch issues. Picking up the trash is the metaphor for taking care of problems.
Several Redmi Note 10 Pro and Redmi Note 10 users have complained about issues with their phone's touch response, while others have claimed that their handsets become unresponsive sporadically. Sustained A performance, even with a modest level of effort, gets rewarded. The Redmi Note 10 range is priced in India starting at Rs 11,999.īuyers of the Redmi Note 10 range have been tweeting to complain about several issues with their handsets. Redmi India has acknowledged the issues but said that less than 0.001 percent of users were affected, adding that it was working on a solution. These issues are reportedly cropping up in all three models. Early adopters are now reporting of touchscreen issues, slowing of handsets, and occasional screen flickering.
The smartphone series was launched in India just last month and the range includes three phones - Redmi Note 10 Pro Max, Redmi Note 10 Pro, and Redmi Note 10.
Redmi Note 10 series buyers are complaining online about a number of issues with their smartphones. In the case of the box sample we’ve been using throughout the previous guides, adding will-change for transforms and opacity looks like this. For most cases, then, any element in your app’s current view that you intend to animate should have will-change enabled for whichever properties you plan to change. The general rule of thumb is that if the animation might be triggered in the next 200ms, either by a user’s interaction or because of your application’s state, then having will-change on animating elements is a good idea. Don't overuse will-change, however, because doing so can cause the browser to waste resources, which in turn causes even more performance issues.
This allows the browser to put the most appropriate optimizations in place ahead of when you make the change. Use the will-change to ensure the browser knows that you intend to change an element’s property.
You can find a full guide on creating High Performance Animations on HTML5 Rocks. For most modern browsers, this means limiting animations to opacity or transform, both of which the browser can highly optimize it doesn’t matter if the animation is handled by JavaScript or CSS.įor a full list of the work triggered by individual CSS properties, see CSS Triggers. Where you can, you should avoid animating properties that trigger layout or paint. Whenever layout is triggered, the page or part of it will normally need to be painted, which is typically even more expensive than the layout operation itself.
This process is called layout (or reflow in Gecko-based browsers like Firefox), and can be expensive if your page has a lot of elements. For example, animating the width and height of an element changes its geometry and may cause other elements on the page to move or change size.