Develop Bugs

HOX Screen Flicker on 4.0.4

Im having a screen flickering, where it looks a bit like interference on some images, it happened very slightly over the last few weeks but i didnt think anything of it. Since rooting & installing ARHD I have it more often – Im not sure if its increased or im noticing it more now.
Also ive read alot on XDA about similar probs being software – but there is always a chance its hardware – having only had the phone a month i dont want to have a faulty unit that cant be fixed!
But now my phone is unlocked will i be able to take it for warranty? if i flashed RUU & re-locked bootloader?
Its not bad atm, but im worried it may get worse

the flicker was/is kernel related
try flash another kernel - i was getting some flicker after rooting etc, but am using franco r18 kernel now and haven't seen any so far

lawrence750 said:
the flicker was/is kernel related
try flash another kernel - i was getting some flicker after rooting etc, but am using franco r18 kernel now and haven't seen any so far
Click to expand...
Click to collapse
Oh that would be good if it's definitely a software fix, its odd that others don't complain from ARHD, is the problem you had, colored lines across the images, or actual back light related, as ive seen this confused?
Sent from my HTC One X using xda app-developers app
Sent from my HTC One X using xda app-developers app

its not the graphical corruption that everyone somehow thinks is flicker definitely backlight flicker.
i think the reason some don't get it is just the variations in hardware if i'm honest.
the kernel is supposed to 'calibrate' the screen, and after 1-2 weeks on auto brightness the flicker should have completely gone. alternatively use max brightness for a few hours.
the 1.29 (the second 1.29) OTA was supposed to fix this, so it's strange that some are seeing this again with 2.17 ...

lawrence750 said:
its not the graphical corruption that everyone somehow thinks is flicker definitely backlight flicker.
i think the reason some don't get it is just the variations in hardware if i'm honest.
the kernel is supposed to 'calibrate' the screen, and after 1-2 weeks on auto brightness the flicker should have completely gone. alternatively use max brightness for a few hours.
the 1.29 (the second 1.29) OTA was supposed to fix this, so it's strange that some are seeing this again with 2.17 ...
Click to expand...
Click to collapse
Ill try it for a few weeks, :fingers-crossed:.. I just ran the fone on full brightness for 20mins and the phone got real hot - like 53d, that also doesn't seem normal. Might need to try a different ROM.

fonetalk said:
Ill try it for a few weeks, :fingers-crossed:.. I just ran the fone on full brightness for 20mins and the phone got real hot - like 53d, that also doesn't seem normal. Might need to try a different ROM.
Click to expand...
Click to collapse
all i can say, is that afaik arhd is close to stock, and i know the heat was improved in 2.17 - but faux/franco kernel both pretty good with heat. i'm using viper rom, the tweaks just make it something else! it's really good imo.
normally doesn't go above 40c battery temp even when charging. before on old versions i had it overheating when just browsing the web whilst charging, haven't had an overheat message for ages now.
try franco kernel first - i did see some flickering on fauxs kernel when using it.

Updated prob remains
lawrence750 said:
all i can say, is that afaik arhd is close to stock, and i know the heat was improved in 2.17 - but faux/franco kernel both pretty good with heat. i'm using viper rom, the tweaks just make it something else! it's really good imo.
normally doesn't go above 40c battery temp even when charging. before on old versions i had it overheating when just browsing the web whilst charging, haven't had an overheat message for ages now.
try franco kernel first - i did see some flickering on fauxs kernel when using it.
Click to expand...
Click to collapse
I flashed Viper ROM tonight, Great ROM btw so far.
Unfortunately it still has the screen problem, first day i know.
Here is a photo of what it looks like atm:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

fonetalk said:
I flashed Viper ROM tonight, Great ROM btw so far.
Unfortunately it still has the screen problem, first day i know.
Here is a photo of what it looks like atm:
Click to expand...
Click to collapse
hold on, i'm not sure what im looking at in the picture, do you mean the orange bits? can't tell if its the photo itself thats blurred or if thats the effect you're having with the screen
when i talk of flicker, i mean backlight flicker, as in one of those office lightbulbs, that when they're about to die, they start to flicker, like a strobe light effect. is this what you're getting, or something different?

lawrence750 said:
hold on, i'm not sure what im looking at in the picture, do you mean the orange bits? can't tell if its the photo itself thats blurred or if thats the effect you're having with the screen
when i talk of flicker, i mean backlight flicker, as in one of those office lightbulbs, that when they're about to die, they start to flicker, like a strobe light effect. is this what you're getting, or something different?
Click to expand...
Click to collapse
I thought that you may have meant that. The flicker im talkin about is the green/yellow lines down the image - some people have called it banding.
So far no change in ROMs has fixed it.
There is alot of talk that it is Software related, i'm just worried there is confusion between what i have and the back lighting issue... Id like to know if its hardware.

fonetalk said:
I thought that you may have meant that. The flicker im talkin about is the green/yellow lines down the image - some people have called it banding.
So far no change in ROMs has fixed it.
There is alot of talk that it is Software related, i'm just worried there is confusion between what i have and the back lighting issue... Id like to know if its hardware.
Click to expand...
Click to collapse
ok i see now what you mean in the picture, the bit just slightly left from the middle?
and is that corruption even on the htc startup screens/bootloader etc?

Yeah just the vertical thin greenish lines, it only effects about 2% of complex rich colored images with varying severity, the example being the worst. And most of three time is only when I'm touching the screen.
So not a massive problem atm, but I just want to know if three a fix and it won't get worst.
Sent from my HTC One X using xda app-developers app

fonetalk said:
Yeah just the vertical thin greenish lines, it only effects about 2% of complex rich colored images with varying severity, the example being the worst. And most of three time is only when I'm touching the screen.
So not a massive problem atm, but I just want to know if three a fix and it won't get worst.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
to be honest, after the re flashing etc etc, it sounds like it could well be hardware, maybe a bad connection to the screen. its hard to say.
feel free to put up a link to the image and i'll test on mine, but i don't expect to see any issues of course.
it's probably worth having a chat with htc about it, they'll probably say to send it for repair imo

lawrence750 said:
to be honest, after the re flashing etc etc, it sounds like it could well be hardware, maybe a bad connection to the screen. its hard to say.
feel free to put up a link to the image and i'll test on mine, but i don't expect to see any issues of course.
it's probably worth having a chat with htc about it, they'll probably say to send it for repair imo
Click to expand...
Click to collapse
yeah, thats what i was worried about - now that the phones unlocked they will probly wont accept under warranty even though its hardware.
You reckon if i relock bootloader & RUU original ROM they would take it under warranty??
Here is the worst offending image, its just album art off spotify. there are heaps of other images that produce similar effects - but not as bad, and it usually settles within a second.

fonetalk said:
yeah, thats what i was worried about - now that the phones unlocked they will probly wont accept under warranty even though its hardware.
You reckon if i relock bootloader & RUU original ROM they would take it under warranty??
Here is the worst offending image, its just album art off spotify. there are heaps of other images that produce similar effects - but not as bad, and it usually settles within a second.
Click to expand...
Click to collapse
Are you from uk? If not, start looking up the consumer laws relevant to where you live, lemme know as well ill see what I can find
Re locking and all that hardly makes a difference imo, it might help for the luck factor in hoping the technician won't notice, but if they want to look, they'll see it straight away because of the re locked bit
Anyway if you're from uk its a lot easier because the onus is on Htc to prove you caused the fault (if the problem has occurred within 6 months of purchase)
Sent from my HTC One X using xda app-developers app
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
Also if you're under volting or over clocking revert to normal values and check if problem still happens
Sent from my HTC One X using xda app-developers app

lawrence750 said:
Are you from uk? If not, start looking up the consumer laws relevant to where you live, lemme know as well ill see what I can find
Re locking and all that hardly makes a difference imo, it might help for the luck factor in hoping the technician won't notice, but if they want to look, they'll see it straight away because of the re locked bit
Anyway if you're from uk its a lot easier because the onus is on Htc to prove you caused the fault (if the problem has occurred within 6 months of purchase)
Sent from my HTC One X using xda app-developers app
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
Also if you're under volting or over clocking revert to normal values and check if problem still happens
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Im from Australia, I really dont think I will take it in unless it gets worse..
Kind of sux concidering its only a month old, but its really not bad atm.
Im not willing to get charged a repair fee for it unless it occurs more frequently.
My next step is to try a jelly bean ROM as it will be a totally different kernel, just in case :fingers-crossed:

fonetalk said:
Im from Australia, I really dont think I will take it in unless it gets worse..
Kind of sux concidering its only a month old, but its really not bad atm.
Im not willing to get charged a repair fee for it unless it occurs more frequently.
My next step is to try a jelly bean ROM as it will be a totally different kernel, just in case :fingers-crossed:
Click to expand...
Click to collapse
Does it happen on stock rom? Sorry can't remember if you said it does or not
Let us know if jb helps
Sent from my HTC One X using xda app-developers app

LG G3 Severe annoyances

Hi all, this is my first post here, just thought I would share my experiences with the LG G3 (D855)
...probably the worst phone I have ever owned, so far I have had the Nexus one, Nexus S, Galaxy Nexus, Nexus 4 and a Nexus 5. My nexus 5 got destroyed at work, so took this as an opportunity to upgrade, but didn't want the Nexus 6 due to its size.
Now, where to start with the G3...
Signal- it is unbelievably bad, going from the Nexus where signal was nearly full in my room to barely getting any now. It is impossible to make calls or browse the net with the phone unless connected to the WiFi, I could download on H+ at about 1.2 mB a second, where as the G3 will barely refresh Facebook. My phone gets used at work quite a bit, but the signal isn't the strongest- however, all phones worked there to make call, apart from this one
Keyboard- Who the hell designs a keyboard without the comma on the front of it without having to go into a menu? This is where you tell me to install another one, but seriously?
Battery- yes I can understand it is a big screen etc, but for 3000 mAh it a atrocious.
Airplane mode- yes I know what it does, why the hell does it tell me every time I select it.
McAfee- we have a play store, I am not a chump and don't download from unknown sources, give the option to remove it.
Vibrate- yes it is harsh, but I work in a noisy environment, I need a strong vibrate function, however, one thing I DO NOT NEED is for it to vibrate in my ear when someone texts/whatsapps me during a call. This makes hearing the other person impossible, they can even hear it on the other end of the phone. I see no way of dulling the vibrate but only when in a call?
-Camera lag
-OS lag (Severe)
Yes, they have wowed their customers with a qhd display, but seriously, they need to start spending money on where it matters like antenna research. After a quick Google, it turns out to be a huge problem with this phone. Not just mine personally.
I am returning this phone after 18 hours of having it. Sorry LG, but they have lost me as a customer.
Dave

Looking for your previous phones I still think this "lag" is a placebo.
Came from a GNex and I must say that LG G3 does NOT lags.

Thank you for your judgment on how I percieve lag, my last phone was a Nexus 5 with CM, it did NOT have lag. This phone does.
UPDATE
Ok, after doing some more reading up, I decided to give the phone a bit more of a chance. I was headed on a 60 mile drive with my brother to see my family this Christmas. Before I left, I gave it a factory reset just to make sure I started with a clean slate.
Anyway headed on my way, 85% battery, I sent a friend a whatsapp message that would sit there ready to send and then go when I got signal. 40 miles traveled, checking very often here and there and it still hadn't sent. The battery had dropped to 25% in this time. Rather than waste any more time or battery in the hope that it would eventually get signal, I put airplane mode on. Guess what, I know what airplane mode does, because it told me AGAIN.
Now, I know this journey well, I know where I get signal and where I don't. All previous phones would have worked numerous places where the G3 didn't.
Oddly, instead of getting signal in some of the places around home where it should definately get it, the phone just constantly displayed roaming and wouldn't allow data. This happens with the Three network from time to time, but always happens in certain places where the network isnt available and allows voice calls only, not at home where there IS reception.
UPDATE
Just discovered that the stock charger cannot supply enough current to use the phone at the same time as charging. This phone is just brilliant...

DavidVanstone said:
Hi all, this is my first post here, just thought I would share my experiences with the LG G3 (D855)
Keyboard- Who the hell designs a keyboard without the comma on the front of it without having to go into a menu? This is where you tell me to install another one, but seriously?
-OS lag (Severe)
Dave
Click to expand...
Click to collapse
I understand you are about to return it already, this is more for people who is experiencing your issues.
The 2 issues above can be solved:
-Keyboard: it is configurable. Settings-> Language and input-> Lg Keyboard-> Keyboard height and layout-> Bottom row keys.
-OS lag: I got the phone 2 days ago and I was quite pissed off about the touch panel lag. The issue was the Touch zoom in my case. Go to Settings-> General-> Accessibility and disable Touch zoom.
DavidVanstone said:
UPDATE
Just discovered that the stock charger cannot supply enough current to use the phone at the same time as charging. This phone is just brilliant...
Click to expand...
Click to collapse
I am not sure what do you mean here. I used the phone for a couple of hours yesterday from 0% battery to ~30% while charging.
I hope this helps.
R.

Ok thank you, installed the google keyboard for now, used to it so feel at hone
I can live with all the issues (as I would most probably ROM it if I kept it anyway) but cannot abide the very very poor signal and the charging. It is currently on charge and has dropped 2% in the time I have written this. Screen brightness is on its lowest.
Have raised an RMA, just waiting to hear back. It is such a shame, it has its good points, love the screen, volume isn't as bad as most make out. Just a lot of other issues (mainly software) that seriously need to be addressed.

Did i just read you complaining about LAG comparing the LG OS with a nexus 5 that was on ****ing CYANOGEN?!
Well just install CYANOGEN on your G3 and be done with it....

Pacote-san said:
Did i just read you complaining about LAG comparing the LG OS with a nexus 5 that was on ****ing CYANOGEN?!
Well just install CYANOGEN on your G3 and be done with it....
Click to expand...
Click to collapse
And that will cure my hardware signal issues will it? I think not.

UPDATE
Tried three different chargers tonight, none of which make any difference to its inability to be charging while being used. It just keeps slowly running out.

Yeah I just upgraded from a Nokia Lumia 1020 today, and I have to admit...I am unimpressed. This thing is, on paper, WAY more powerful, so why the hell is it so. goddamn. LAGGY?

The lag, I can live with, as said, if I was keeping it I woukd probably ROM it anyway.
The thing is there are a lot of issues that need to be addressed, and with us all being techy types we could sort most of the issues with some modding, but here is my question, what does the average end user do with the problems? Accept them? Talk to LG and get told that the phone should vibrate like that when getting a notification during a call? Get told that the signal issues are because of the carrier. Get told that the reason their batteriy is going flat is because of apps they have installed? When after all this it is a combination of bad software and hardware that lets this phone down, no one else's fault.
UPDATE
Battery full notification, during writing this, every time I paused for a few seconds the phone vibrated, left a notification and bleeped to tell me the battery was full- this gets highly ***king annoying after a while, can this be turned off?!
Oh, here is the graph of the battery during my drive yesterday that I explained about. The drop is when the phone was looking for signal duringn the journey.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can see at the -5 and -3 hour mark where I put the phone on charge, a small spike in the graph, then immediately while being used, the level continued to drop with it still plugged in.

Yeah, the average user is pretty much ****ed. Thing is, there is NO excuse for it. If Microsoft, the former king of bloat, can make a smooth, fast, stable operating system that flies even on low end hardware, why can't Google make it fly on high end hardware? Why can't LG?
I will keep experimenting with Roms, but right now it's very likely I'll return this and go back to a Windows phone.
Sent from my LG-D850 using XDA Free mobile app

jasongw said:
Yeah, the average user is pretty much ****ed. Thing is, there is NO excuse for it. If Microsoft, the former king of bloat, can make a smooth, fast, stable operating system that flies even on low end hardware, why can't Google make it fly on high end hardware? Why can't LG?
I will keep experimenting with Roms, but right now it's very likely I'll return this and go back to a Windows phone.
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
It is such a shame, the phone does have some good bits going for it, but I am definately returning mine, the RMA has been raised with Ebuyer, just waiting to hear back.
I would have rommed it, but seeing as it's going back I couldn't be doing with the hassle of doing it and putting it back to stock again. Also, not being able to utilise the 4k and other camera features in aosp. Maybe someone can sort that, but either way, a phone not being able to get signal is a big problem for me and for some reason this issue seems to be getting more and more common nowadays (why is this?).
A quick question, which smartphones ACTUALLY have good signal? Once this one has gone, I'll be looking for another phone.

I just bought my G3 Monday, switched from an iPhone 6. The stock rom was slow.
Today rooted and installed Candy5. This phone is a beast. I haven't had one thing today phase this.
You can't compare CM to stock.
Works very well paired the Lg w110 watch.
Also this phone has much much better coverage then my iPhone and has the same that my Note 2 had.
Sent from my LG-D851 using XDA Free mobile app

Touch issues (only in corners), worse without navbar - w/ video!

hey guys,
the videos and the title speak for themself. rest of the screen is fine touch-wise, perhaps with a slight limitation at the left and right edge. since the latter could be software related, do you think that touch registration issues in a particular area (like left and right bottom corner) can be anything else than hardware.
https://youtu.be/Yy5xoOXfm8s
https://youtu.be/d6q90SkSFYc
its getting even more massive, when disabling the navigation bar with custom navigation bar from the playstore (root required). see here:
https://youtu.be/kyVwnlnNeFY
what do u guys think? anyone having the same issues? perhaps someone could test with root and no navbar?
contemplating on just rma-ing or going with a full return (and my old n6p) to wait out the issues and a potential hardware revision.
thanks everybody!

xflowy said:
hey guys,
the videos and the title speak for themself. rest of the screen is fine touch-wise, perhaps with a slight limitation at the left and right edge. since the latter could be software related, do you think that touch registration issues in a particular area (like left and right bottom corner) can be anything else than hardware.
https://youtu.be/Yy5xoOXfm8s
https://youtu.be/d6q90SkSFYc
its getting even more massive, when disabling the navigation bar with custom navigation bar from the playstore (root required). see here:
https://youtu.be/kyVwnlnNeFY
what do u guys think? anyone having the same issues? perhaps someone could test with root and no navbar?
contemplating on just rma-ing or going with a full return (and my old n6p) to wait out the issues and a potential hardware revision.
thanks everybody!
Click to expand...
Click to collapse
I've noticed a bit of this as well. I believe this is an issue recognized by Google and has something to do with software implementation to reduce ghost touches from the curved screen. If I recall, this was supposed to be addressed in the December security patch update. I'll see if I can find a source for this info.

mlin said:
I've noticed a bit of this as well. I believe this is an issue recognized by Google and has something to do with software implementation to reduce ghost touches from the curved screen. If I recall, this was supposed to be addressed in the December security patch update. I'll see if I can find a source for this info.
Click to expand...
Click to collapse
but only in the corners?
are u rooted?

This is the exact same problem I had with the essential phone. Mine doesn't have this problem.

xflowy said:
but only in the corners?
are u rooted?
Click to expand...
Click to collapse
I notice its worst near the edges of the screen. I am not rooted.

The touch response is much better on the new 8.1 beta 2.

gm007 said:
The touch response is much better on the new 8.1 beta 2.
Click to expand...
Click to collapse
This is good to know. I figure I'd ride it out until after the December security patch and/or 8.1 is released to determine if I need to RMA. It hasn't much interfered with my use with the exception of gaming on a couple of occasions.

mlin said:
This is good to know. I figure I'd ride it out until after the December security patch and/or 8.1 is released to determine if I need to RMA. It hasn't much interfered with my use with the exception of gaming on a couple of occasions.
Click to expand...
Click to collapse
yea going that route too. since then there would also be some time for quality control to be more efficient since i dont think i would have much luck with a new replacement device right now.
but an argument against the software related explanation would be, that some arent experiencing these touch screen issues. would a software update which adresses the issue for the owners with issues then provoke issues for those who havent had any at all since then?

xflowy said:
yea going that route too. since then there would also be some time for quality control to be more efficient since i dont think i would have much luck with a new replacement device right now.
but an argument against the software related explanation would be, that some arent experiencing these touch screen issues. would a software update which adresses the issue for the owners with issues then provoke issues for those who havent had any at all since then?
Click to expand...
Click to collapse
Both good points. I am almost past my 14 day return period, but I have no intentions of returning the device. If I do RMA, I would like to wait a little while so Google/LG can get some of this nonsense sorted out with later batches.

https://youtu.be/vAs1NH_GNhY
Fixed and working in 8.1 DP2

phamine said:
https://youtu.be/vAs1NH_GNhY
Fixed and working in 8.1 DP2
Click to expand...
Click to collapse
Had the same issue on my device, but running newest december build (9.0). have an exchange from Google on the way. The chat agent also said something about software, so I assume it didnt make it into the 9.0 december update.
Hopefully my replacement device does not have the same issue.

Question Screen problems (anomalies)?

Anyone with Mi 11 Lite experiencing screen "black crush" or gradient issues?
Seems prominent problem according to this thread, as you can see the pictures of the issue on the official support thread.
https://c.mi.com/thread-3654299-1-1.html

kirin432 said:
Anyone with Mi 11 Lite experiencing screen "black crush" or gradient issues?
Seems prominent problem according to this thread, as you can see the pictures of the issue on the official support thread.
https://c.mi.com/thread-3654299-1-1.html
Click to expand...
Click to collapse
Hello
I just received my Mi 11 Lite 4G today, not used a lot, but checking it with some total-black images it seems good.
But on the italian telegram community several people complain about your problem.
Probably a batch of defective screens?
I'll think about returning the phone, if I where in your situation

Luckily I didn't buy phone yet, because I've seen the same ongoing topics about screen problems. Russian's communities are also reporting vast number of affected units, seems everyone got their phones from the first batch, so it could really be a jinxed batch... But apparently Xiaomi said it's working on a software fix.
That's why I am holding off, I don't want to buy a phone and get one from the firsts batch that may be problem.

^^
Can you tell me production date of your phone. It should be on the box in MM.YYYY format. Because as I have read many people with screen anomalies seem to have batch 01.2021.

kirin432 said:
^^
Can you tell me production date of your phone. It should be on the box in MM.YYYY format. Because as I have read many people with screen anomalies seem to have batch 01.2021.
Click to expand...
Click to collapse
Yes, of course: mine is 2021.02
Seems i've been lucky

Lollauser said:
Hello
I just received my Mi 11 Lite 4G today, not used a lot, but checking it with some total-black images it seems good.
But on the italian telegram community several people complain about your problem.
Probably a batch of defective screens?
I'll think about returning the phone, if I where in your situation
Click to expand...
Click to collapse
Hi bro.. your Mi 11 Lite is fine? Which production date is your. At your box you will see it. Mine got problem also.. I also go to Mi Store in my country to check another Mi 11 Lite. Also got same problem.

He said his phone is 02.2021.
I've read many people had reported same problem as yours.

The mi 11 Lite thread on 4pda is reporting, on page 102, an update to12.08 that does something to improve the display.

berlin51 said:
The mi 11 Lite thread on 4pda is reporting, on page 102, an update to12.08 that does something to improve the display.
Click to expand...
Click to collapse
Which version (EEA, Global)?

EEA or Global....doesn't say, so far.
But it will probably be available on Mi Lite editions soon.

berlin51 said:
The mi 11 Lite thread on 4pda is reporting, on page 102, an update to12.08 that does something to improve the display.
Click to expand...
Click to collapse
The only thing they do is making less notification shade less transparent. But the Black crush is still there when you watch movie on low Light. If about half brightness then the black crush is gone.. not much improvement. On my fourth pic is Half brightness in light condtion. I dont know is this really software problem or hardware issue

Probably a software thing.
There were phones with black crush issues before and those were fixed like Samsung S9.

What is the best way to check if the problem is present?

Well the problem was most evident in dark mode when notification shade was pulled down. but they resolved that in new update by making the shade less transparent.
You can play some videos that have gradient black to grey transitions like this one which they used to point the problem. See if it has any gradient issues.
Only thing that is confusing for me is some people are claiming the don't have any problems whatsoever, and others believe that first batch of the phones maybe had problems with the panels themselves.
But the good thing is people are reporting not perfect but better situation with the screen since the last update, so at least Xiaomi is addressing the problem.

I have a phone of batch 2021.02 - no screen issues whatsoever. I'm on firmware MIUI Global 12.0.4 (latest) -> RKQEUXM 12.0.4

Its still there and mine was on march's production date. Lower the night setting reduced the pixelates but its still there. We do really need this to be fixed like asus rog and galaxy s9.

i am facing same issue while watching video, it's almost impossible to watch.
any ideas if it will be fixed in upcoming updates i am on 12.0.8

No other way around....
Seems EVERYONE with the phone has the same issues, so Xiaomi needs to fix it, I suppose with 12.5

screen balance seems to fix it but the downside is u lost the true blacks well i hope xiaomi fix this its obviously a software problem

And what about image retention? I've even read some people reporting true burn ins after short time.
Somehow I am afraid that Xiaomi put not so good panel on this device, that's low quality and the software fixes can only mask the issues but no truly solve it.

Question General 12.1 issues, am I the only one?

Edit: I changed the title of this thread to general 12.1 issues bc I've been noticing more stuff. The list so far is:
1. Vibration strength for notifications is ridiculously weak now
2. Lock screen as detailed below in this post
3. Heating up quite a bit listening to music. Am on wifi, using pixel buds A series
4. Battery drain. Been off charger since about 8:40am 100%, listening to music for just over an hour, now at 80%.
................................................................................
Another weird bug I noticed with 12.1 is that whenever my screen locks, it briefly shows "No notifications" in the middle of the screen before showing the fingerprint icon. This only seems to happen when I disabled the huge 2 line clock.
Just like with the weak notification vibrate strength thread I started, I'm asking if anyone else is seeing this too or if it's just me. Also, anyone on 13 DP2, do you see this?
Trying to work out if I should bite the bullet and do a factory reset or if these are just known things bc if I don't have to reset, I won't.
James

How do you change the huge clock?

I'm speculating a little, but since you say "This only seems to happen when I disabled the huge 2 line clock", I would suggest that a factory reset won't help.
Note, I'm not on the March update yet.

96carboard said:
How do you change the huge clock?
Click to expand...
Click to collapse
Go to settings>display>lock screen>double line clock toggle

roirraW edor ehT said:
I'm speculating a little, but since you say "This only seems to happen when I disabled the huge 2 line clock", I would suggest that a factory reset won't help.
Note, I'm not on the March update yet.
Click to expand...
Click to collapse
This is exactly why I'm asking haha. However, I think a factory reset is getting more and more plausible because now, I am listen to music at work as I usually do and my phone is getting real hot as well as battery draining quick. Unreal that google holds back this specific update to ensure no major bugs and this happens. I had no issues with the December update they actually pulled, no issues with Jan, and only a couple little dumb issues with Feb. Battery, vibration, heat, etc are all major issues. The lock screen thing, not so much but if others aren't having the issue, then I shouldn't be also. I am going to change the title of this thread to general 12.1 issues bc I'm getting off topic from the lock screen question.
James

It's true. The battery is worse than it was. Notification vibration is generally a nightmare. My phone is constantly on silent, so it's important for me to have a strong vibration.By the way, we've added a new fingerprint unlock animation.

jrg67 said:
1. Vibration strength for notifications is ridiculously weak now
Click to expand...
Click to collapse
I am one of those who rely on vibration at work, and I can absolutely confirm that its much weaker after the update that I took mid morning.

dacapho said:
I am one of those who rely on vibration at work, and I can absolutely confirm that its much weaker after the update that I took mid morning.
Click to expand...
Click to collapse
Definitely submit feedback on this through the settings. This is absolutely unacceptable that they totally killed vibration strength on just the 6 series, either by design or a bug.

Can't repeat the screen lock screen error, but this vibration thing is wild.

somethingsomethingroot said:
Can't repeat the screen lock screen error, but this vibration thing is wild.
Click to expand...
Click to collapse
Send feedback! Hopefully if a ton of people complain, Google will actually acknowledge this. Only other thing I can think of is the pixel community and a bug report

I thought I was going crazy because of the vibration. It is noticably weaker. I haven't seen any significant battery drain though. Sorry. Compared to some bugs, this isn't too bad.

I also noticed a much weaker vibration strength after the update. I did a search in Settings for vibration and got a "vibration & haptics" settings. All sliders were on the left. Once I pulled them back to the middle, vibration strength seems to be normal again (as far as I remember).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jrg67 said:
This is exactly why I'm asking haha. However, I think a factory reset is getting more and more plausible because now, I am listen to music at work as I usually do and my phone is getting real hot as well as battery draining quick. Unreal that google holds back this specific update to ensure no major bugs and this happens. I had no issues with the December update they actually pulled, no issues with Jan, and only a couple little dumb issues with Feb. Battery, vibration, heat, etc are all major issues. The lock screen thing, not so much but if others aren't having the issue, then I shouldn't be also. I am going to change the title of this thread to general 12.1 issues bc I'm getting off topic from the lock screen question.
James
Click to expand...
Click to collapse
I never had an issue, even with the December update that was pulled.
I'm beginning to wonder about different production runs of this device.
I missed out on the opening day, nothing but 500 errors trying to order the phone.
I got my 256G jobbie on the next restock and received it in December.
(I originally was going for the 512G but I didn't want to wait until sometime in 2022.)
I couldn't order until November 9, and received my device in th second week of December.
So I hear and read about complaints, and I had none.
Even today, with my phone is on my desk, vibration is just fine.
It gets my attention and I didn't notice a thing.

bleez99 said:
I never had an issue, even with the December update that was pulled.
I'm beginning to wonder about different production runs of this device.
I missed out on the opening day, nothing but 500 errors trying to order the phone.
I got my 256G jobbie on the next restock and received it in December.
(I originally was going for the 512G but I didn't want to wait until sometime in 2022.)
I couldn't order until November 9, and received my device in th second week of December.
So I hear and read about complaints, and I had none.
Even today, with my phone is on my desk, vibration is just fine.
It gets my attention and I didn't notice a thing.
Click to expand...
Click to collapse
I never had a major issue until this 12.1 update as well. This is so weird. I was able to order my phone on announcement day and received it on launch day in October. Phone has literally been as close to perfect as it could be (again just a few minor annoyances but nothing major).
This is making the case for a wipe even stronger. Ugh. Has anyone that has experienced these issues perform a wipe and had it fix these things, especially the weak vibration?
When you say your vibration is fine, I am assuming you updated to 12.1 and the vibration is the same as it was on the Feb 12.0 release and earlier?

jrg67 said:
I never had a major issue until this 12.1 update as well. This is so weird. I was able to order my phone on announcement day and received it on launch day in October. Phone has literally been as close to perfect as it could be (again just a few minor annoyances but nothing major).
This is making the case for a wipe even stronger. Ugh. Has anyone that has experienced these issues perform a wipe and had it fix these things, especially the weak vibration?
When you say your vibration is fine, I am assuming you updated to 12.1 and the vibration is the same as it was on the Feb 12.0 release and earlier?
Click to expand...
Click to collapse
Yes. I haven't noticed a difference, it's still just as strong as it was before March.

stbxxl said:
I also noticed a much weaker vibration strength after the update. I did a search in Settings for vibration and got a "vibration & haptics" settings. All sliders were on the left. Once I pulled them back to the middle, vibration strength seems to be normal again (as far as I remember).
View attachment 5568471
Click to expand...
Click to collapse
Mine are all maxed out. I even put them down to off, restarted the phone both soft and hard (holding the power button what seems like an hour to perform) and moved them all back up to max. No difference.

Vibration hasn't changed for me, still wants to shake the house down.
Not got any of the other issues you have listed either fortunately, not that it helps you though

jrg67 said:
Send feedback! Hopefully if a ton of people complain, Google will actually acknowledge this. Only other thing I can think of is the pixel community and a bug report
Click to expand...
Click to collapse
Been reading that this has been going on since the beta, which makes it sound like a choice.

somethingsomethingroot said:
Been reading that this has been going on since the beta, which makes it sound like a choice.
Click to expand...
Click to collapse
Yes but there is some hope, some say their vibration hasn't changed. Anyone factory reset with weak vibration and the reset fixed it?

I haven't really noticed any change in my vibration strength, for whatever that's worth.