Hi all, i have experienced something strange with my Z5P. When i take a walk on bright sunny day, the screen got bright for about 2-3 minutes, but then it would go down to the dimmest state without any info. I tried to push it up manually but it won't do. so i decided to pocket it for a while and when i'm in shade, i turn it on again and it goes back to normal.. So my question is, is this normal due to 4K display? Or is it a bug in Marshmallow? Because it really makes me hard to read at outdoor after a while. The screen surface sure is hot though.. Anybody have the same experience?
I am still on Lollipop and have the same issue
hansip87 said:
Hi all, i have experienced something strange with my Z5P. When i take a walk on bright sunny day, the screen got bright for about 2-3 minutes, but then it would go down to the dimmest state without any info. I tried to push it up manually but it won't do. so i decided to pocket it for a while and when i'm in shade, i turn it on again and it goes back to normal.. So my question is, is this normal due to 4K display? Or is it a bug in Marshmallow? Because it really makes me hard to read at outdoor after a while. The screen surface sure is hot though.. Anybody have the same experience?
Click to expand...
Click to collapse
I think this was happening in the other z series like the z1 too. But I think this because the phone would heat up and thus, the phone tries to cool down by doing that. I think there was a fix in the z1 phones but I'm not sure.
Sent from my Sony E6883 using XDA Labs
Ashray_Vk said:
I think this was happening in the other z series like the z1 too. But I think this because the phone would heat up and thus, the phone tries to cool down by doing that. I think there was a fix in the z1 phones but I'm not sure.
Sent from my Sony E6883 using XDA Labs
Click to expand...
Click to collapse
Hmm well my first XZU doesn't have any issue like that, but then again it's a big screen though.. So it's a shame if such issue happens due to heat..
Same thing has been happening to me too. Very very disappointed.
How can we fix it?
thihaz said:
Same thing has been happening to me too. Very very disappointed.
How can we fix it?
Click to expand...
Click to collapse
Don't go out into the bright sunlight! Stay in the shade. Having said that, I'm in the sun right now and I have no problems...
Sent from my SGP311 using XDA Free mobile app
guhvanoh said:
Don't go out into the bright sunlight! Stay in the shade. Having said that, I'm in the sun right now and I have no problems...
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
I only go into bright sunlight during lunch time when i enjoy the movie while having my meal.
The display is almost black. My previous phones LG G4, ZUK Z1, Moto X Style, even Note 4 or 3 has no issues.
I paid SGD835 for the phone and it sucks.
Enjoy man since you don't have that problem.
Still no fix for this annoying issue?
thihaz said:
I only go into bright sunlight during lunch time when i enjoy the movie while having my meal.
The display is almost black. My previous phones LG G4, ZUK Z1, Moto X Style, even Note 4 or 3 has no issues.
I paid SGD835 for the phone and it sucks.
Enjoy man since you don't have that problem.
Click to expand...
Click to collapse
All phones from any manufactures with snapdragon 810 have an overheating problem (you can thank Qualcomm for that)...since the Z5p uses that SoC as well, this is a protection implemented by Sony so the processor doesn't fry your phone, your phone will get hot already watching a movie as you do under normal conditions, the situation will get even more steamy in full sun (on a hot day, it's fine when it's cooler outside)...the screen brightness is reduced to cool down the phone when it becomes too hot...
With that said there is a way change the value of the minium screen brightness (if you're rooted) to a higher number... If you search there is a thread about this in the Z5p forum already where someone posted where to find what to change...never tried myself by the way as you permanently change that value to some higher so it will be too bright the rest of the time and frankly I think that it will do more harm than good anyway...
Just let your phone cool down and you're good to go again...
-DM- said:
All phones from any manufactures with snapdragon 810 have an overheating problem (you can thank Qualcomm for that)...since the Z5p uses that SoC as well, this is a protection implemented by Sony so the processor doesn't fry your phone, your phone will get hot already watching a movie as you do under normal conditions, the situation will get even more steamy in full sun (on a hot day, it's fine when it's cooler outside)...the screen brightness is reduced to cool down the phone when it becomes too hot...
With that said there is a way change the value of the minium screen brightness (if you're rooted) to a higher number... If you search there is a thread about this in the Z5p forum already where someone posted where to find what to change...never tried myself by the way as you permanently change that value to some higher so it will be too bright the rest of the time and frankly I think that it will do more harm than good anyway...
Just let your phone cool down and you're good to go again...
Click to expand...
Click to collapse
Thanks for the tip.
Because of those pros and cons, sony lacks behind. Sadly I am already using iphone 7 plus and there is no such a problem on camera and display.
Still keep my Z Ultra for fun though
thihaz said:
Thanks for the tip.
Because of those pros and cons, sony lacks behind. Sadly I am already using iphone 7 plus and there is no such a problem on camera and display.
Still keep my Z Ultra for fun though
Click to expand...
Click to collapse
Whatever floats your boat
If anyone have issue with this(Eveyone should), I have file that let you use 100% of screen brightness, of cause it's adjustable.
Basically let you have full control without Thermal limit kicks in.
Only thing is that the file can not be modified without ROOT...
Let me know
It's call thermal-engine.conf, all you have to do is change all the numbers under "backlight" to 255(Max value).
It works great, I've been using it as is for more than one year.
It's located Root/system/etc/thermal-engine.conf
-DM- said:
Whatever floats your boat
Click to expand...
Click to collapse
Had the same problem, at least think so since I was never able to recover by cooling the Z5 so I am not sure.
Then, I installed Lux Auto Brightness.
The last 72 hours are much better and I was in the sun though not sure if the phone was overheating.
In settings I set Min brightness to 40%, linked ambient light of 0 lux to 60% brightness and let the app do its thing.
So far so good.
Let me know what you think.
barrr said:
Had the same problem, at least think so since I was never able to recover by cooling the Z5 so I am not sure.
Then, I installed Lux Auto Brightness.
The last 72 hours are much better and I was in the sun though not sure if the phone was overheating.
In settings I set Min brightness to 40%, linked ambient light of 0 lux to 60% brightness and let the app do its thing.
So far so good.
Let me know what you think.
Click to expand...
Click to collapse
never tried Lux Auto Brightness...I'll give it a try, but the screen dimming only happens to me on rare occasions while outside under a hot sun, I'll install that app and see next time around when I meet those conditions
Related
When i select auto-brightness it takes my phone to the lowest possible setting regardless of the environment lighting and it stays there
wondering if i should take the phone back if it's just my phone...anyone else experience this?
Hmm mine seems t I slwsys be low by the I like it like thst.. Have not had a chance to take it outside yet due to the hurricane
Sent from my SPH-L900 using xda app-developers app
thanks for the feedback...i compared it side by side to my gs3 and my gs3 works as it should...my Note 2 goes all the way down to the lowest setting..
BTW im in north east MD...the eye past directly over us here ..we are about 1 hour and 20 minutes from AC new Jersey...
Mine also appears to be a bit on the low side. It is not at the lowest, but auto never appears to hit the highest brightness. When i am in sunlight, i have to untick auto and move the slider to max in order to comfortably read the screen. Hopefully it will get fixed.
JD
I've always thought Samsung's auto brightness sucked regardless of phone. The note 2 is no exception.
Try some apps in the play store, they work better.
Sent from my SPH-L900 using xda premium
shook187 said:
I've always thought Samsung's auto brightness sucked regardless of phone. The note 2 is no exception.
Try some apps in the play store, they work better.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
SGIII didn't have any issue with brightness at all. At least for me.
Galaxy Nexus is absolutely horrible on the other hand. And I'm too lazy to play with AOKP adjustments so I have to do it manually everytime.
My Note II does appear a little darker than it should but I thought it might be only my perception. I'll take closer look at it.
meccadon123 said:
When i select auto-brightness it takes my phone to the lowest possible setting regardless of the environment lighting and it stays there
wondering if i should take the phone back if it's just my phone...anyone else experience this?
Click to expand...
Click to collapse
I thought I had the same thing. My phones brightness is all the way down with the auto box checked. I did however uncheck it and then the brightness dropped way down. I chalked it up to auto taking over and misrepresenting what the level of the brightness was on the screen. Dont know if you are seeing that or if you are seeing a true glitch.
i thanked all for your feed back...its obviously not just my phone...again my GS3 works very well...my note 2 not at all...I wonder if samsung set this up like this on purpose to save battery..either way auto-brightness is unusable for me...
Hi all,
I just gotten this phone today. I noticed the auto brightness transistion is not smooth but rather jerky and on my set it will brighten the screen and then lower the brightness quite often even though the lighting in the room did not change. Just wondering if I got a lemon set.
Newbie123 said:
Hi all,
I just gotten this phone today. I noticed the auto brightness transistion is not smooth but rather jerky and on my set it will brighten the screen and then lower the brightness quite often even though the lighting in the room did not change. Just wondering if I got a lemon set.
Click to expand...
Click to collapse
I see the same thing. I hope it's not defective.
Mine does the same thing. Ended up turning the feature off, and leaving the brightness at about 50%
mine to i think it's a software issue
andygold said:
Mine does the same thing. Ended up turning the feature off, and leaving the brightness at about 50%
Click to expand...
Click to collapse
Exactly What I did. I used to have the face recognition to keep screen on and that was really annoying with the screen dimming every 15 seconds but with the brightness. Set at 50 I can still see the screen pretty well in sunlight.
Sent from my LG-E980 using Tapatalk 4 Beta
thedudex said:
Exactly What I did. I used to have the face recognition to keep screen on and that was really annoying with the screen dimming every 15 seconds but with the brightness. Set at 50 I can still see the screen pretty well in sunlight.
Sent from my LG-E980 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Coming from 2.5 months of HTC One, I just got this phone yesterday! Awesome phone amid some lags here and there at times. I hope that the next update of Android 4.2.2 will iron out those issue.
Yes, Since Android 4.1, the Autobrightness is kind of "too extreme" to be practical especially the dimming of backlight in low light. I have also set it to 52% manual.
Has anyone noticed any burn-in problems yet? I've seen reports of the problem for some other watches (LG), but so far nothing specific here for the Huawei.
It's so far so good for me, but I've been extremely nervous about this issue. I avoid faces with things like thick tic marks or logos in ambient mode. I know about Wear's built-in "protection," but I don't have a lot of confidence in it. Am I being unreasonable?
improvius said:
Has anyone noticed any burn-in problems yet? I've seen reports of the problem for some other watches (LG), but so far nothing specific here for the Huawei.
It's so far so good for me, but I've been extremely nervous about this issue. I avoid faces with things like thick tic marks or logos in ambient mode. I know about Wear's built-in "protection," but I don't have a lot of confidence in it. Am I being unreasonable?
Click to expand...
Click to collapse
I had the GWR and didn't have any issues with that at all. That said I turn the screen off at night during charging so maybe that helps. I'll keep an eye on the Huawei, but I'm hopeful that it will be fine.
dunjamon said:
I had the GWR and didn't have any issues with that at all. That said I turn the screen off at night during charging so maybe that helps. I'll keep an eye on the Huawei, but I'm hopeful that it will be fine.
Click to expand...
Click to collapse
I had the GWR for almost a year too. Always used watchfaces that are 'always on' (so no dimmed mode without background) and always had the charging animation on by night. Never experienced any burn-in.
I just powered mine on for the first time last night. I played with it for a few hours, then put it in the charger for the night and this morning it has burn-in!! How could it happen so fast??
mszach said:
I just powered mine on for the first time last night. I played with it for a few hours, then put it in the charger for the night and this morning it has burn-in!! How could it happen so fast??
Click to expand...
Click to collapse
Whoa! What got burned in? The little charging icon?
improvius said:
Whoa! What got burned in? The little charging icon?
Click to expand...
Click to collapse
The outline of the watch face. If I change the watchface and swipe left, you can see the outline of the other face as the background instead of white.
mszach said:
The outline of the watch face. If I change the watchface and swipe left, you can see the outline of the other face as the background instead of white.
Click to expand...
Click to collapse
hell no, wtf!!
it is very bad, sorry for that, were you using this watchface long time ago? what is the watch face look like in ambient mode? maybe the watch got really hot, and screen on while charging. i started to worry about the screen quality of this watch.
Edit:
i have seen this is your first day, i think maybe a faulty screen
Yeah, I'm wondering if your watch just froze in full display mode overnight.
mszach said:
The outline of the watch face. If I change the watchface and swipe left, you can see the outline of the other face as the background instead of white.
Click to expand...
Click to collapse
That deserves an RMA and you deserve a new replacement watch.
I sometimes get lag on mine, im not sure if it's actual lag or whether im doing something wrong but as someone mentioned if the watch went full brightness and is charging then the heat might have done it?
I returned it yesterday to best buy. Lucky me though. . they had cyber Monday deals and it was on sale for $50 less! !
I noticed that when the minute hands on mine move (ie every minute) that the whole screen kind of does a refresh. I'm using a custom watch face called InstaWeather, and in the settings there's an option to help with screen burn. I wonder if this is it? So every minute, every pixel would have been off/on or on/off?
dieselboy said:
I noticed that when the minute hands on mine move (ie every minute) that the whole screen kind of does a refresh. I'm using a custom watch face called InstaWeather, and in the settings there's an option to help with screen burn. I wonder if this is it? So every minute, every pixel would have been off/on or on/off?
Click to expand...
Click to collapse
yes, this is an android wear burn in protection buy moving a few pixels in all directions, works very good if you don't have large objects in the ambient mode, and won't help much if you have.
improvius said:
Has anyone noticed any burn-in problems yet? I've seen reports of the problem for some other watches (LG), but so far nothing specific here for the Huawei.
It's so far so good for me, but I've been extremely nervous about this issue. I avoid faces with things like thick tic marks or logos in ambient mode. I know about Wear's built-in "protection," but I don't have a lot of confidence in it. Am I being unreasonable?
Click to expand...
Click to collapse
In my opinion, yes, you are being overly worried. First the technologies itself has improved and we see less burn-in even when we set screens on to test such a thing. Second, the ability to move(write) a watch face or screen is not some huge leap, in fact it's really super easy to add to an OS to simply move the screen pin outs when in any long display mode. Beyond all that, app makers, watch face builders, now have the old data and make sure they write to avoid any long same display visual mode.
Easy to add to an app, when write same display, write 2 pixels, change.
Then after all that we have face on mode and ambient mode, which in my daily use changes my watch face enough that I would never get burn in. Agree that I am a heavy user of the watch, I tend to have to change twice a day. Perhaps someone that used the watch much less would have more of a concern?
I have the same problem
http://cl.ly/183c0O2m0m2q/amoled_vypaleny.jpg
Huawei Watch - after four days of use.
dj.kure said:
I have the same problem
http://cl.ly/183c0O2m0m2q/amoled_vypaleny.jpg
Huawei Watch - after four days of use.
Click to expand...
Click to collapse
****. What kind of messed up face watch/app did u use?
rusty.gh said:
In my opinion, yes, you are being overly worried. First the technologies itself has improved and we see less burn-in even when we set screens on to test such a thing. Second, the ability to move(write) a watch face or screen is not some huge leap, in fact it's really super easy to add to an OS to simply move the screen pin outs when in any long display mode. Beyond all that, app makers, watch face builders, now have the old data and make sure they write to avoid any long same display visual mode.
Easy to add to an app, when write same display, write 2 pixels, change.
Then after all that we have face on mode and ambient mode, which in my daily use changes my watch face enough that I would never get burn in. Agree that I am a heavy user of the watch, I tend to have to change twice a day. Perhaps someone that used the watch much less would have more of a concern?
Click to expand...
Click to collapse
Wrong. You must not understand what screen burn in is. No new technology has come out that will stop screen burn in. The software that moves the pixels over only works if the object is 1 pixel wide other wise it doesn't work screen burn in will still happen. And they do not have it where the same pixels won't be used otherwise in ambient mode it would jump around not wiggle.
dj.kure said:
I have the same problem
http://cl.ly/183c0O2m0m2q/amoled_vypaleny.jpg
Huawei Watch - after four days of use.
Click to expand...
Click to collapse
Reset the watch. It may not be burn in. I saw a bug like this from using too high Def of an image on a watch face. It got stuck in the cache even after I changed watch faces. I reset the watch and haven't had any issues since
Lepa79 said:
****. What kind of messed up face watch/app did u use?
Click to expand...
Click to collapse
Default watchface "Explorer".
---------- Post added at 11:08 AM ---------- Previous post was at 11:06 AM ----------
ShrekOpher said:
Reset the watch. It may not be burn in. I saw a bug like this from using too high Def of an image on a watch face. It got stuck in the cache even after I changed watch faces. I reset the watch and haven't had any issues since
Click to expand...
Click to collapse
Do you mean "Factory reset"? I did it, but nothing has changed.
ac16313 said:
Wrong. You must not understand what screen burn in is. No new technology has come out that will stop screen burn in. The software that moves the pixels over only works if the object is 1 pixel wide other wise it doesn't work screen burn in will still happen. And they do not have it where the same pixels won't be used otherwise in ambient mode it would jump around not wiggle.
Click to expand...
Click to collapse
Fare enough, just my opinion, & you have yours. Too bad you had to start by saying wrong.
Samsung has made changes to light output and color to reduce burn in, and we all know there is some type of display movement now to also reduce burn in, so it's odd you claim there has been nothing.
Anywho, I don't get burn in so yea, maybe with your attitude if you do, you deserve it?
rusty.gh said:
Fare enough, just my opinion, & you have yours. Too bad you had to start by saying wrong.
Samsung has made changes to light output and color to reduce burn in, and we all know there is some type of display movement now to also reduce burn in, so it's odd you claim there has been nothing.
Anywho, I don't get burn in so yea, maybe with your attitude if you do, you deserve it?
Click to expand...
Click to collapse
I'm not going to start it by saying you're right, am I? Samsung didn't make changes to anything in light output the only thing that's changed is adaptive screen color which is meant to adapt the screen contrast to show what's on screen in the best possible colors. There is no new technology that will stop burn in. You must not have understood me. The image wiggle is a software attempt to stop screen burn in from happening but it won't stop it just slow it down. Screen burn in will continue to be a thing until the panels we use change technology. I didn't say that nothing has been made to prevent it.
And if you sense attitude in a straightforward response that's on you. I'll let karma deal with that comment. I personally don't get screen burn in and I've had a SAMOLED device since the Samsung Epic. I just understand how to prevent it. But just because I've never had it I won't tell people that they're overly concerned about screen burn in.
Just installed P and now previous brightness level of 63 it's so dim? I have to have it almost on 90% brightness now, why have they messed with this, it was fine as it was
Ady1976 said:
Just installed P and now previous brightness level of 63 it's so dim? I have to have it almost on 90% brightness now, why have they messed with this, it was fine as it was
Click to expand...
Click to collapse
Same for me. WTF Google?
The actual brightness is the same, they just changed how the slider works. The first half moved it fast, last half moved it slower. Now the slider is more uniform.
https://www.androidpolice.com/2018/...c-brightness-slider-introduced-android-p-dp3/
Sent from my Pixel 2 XL using Tapatalk
It's definitely not smooth across the entire range, all my brightness is almost all the last 10% and actually a pain to set properly, it's worse for me.
That's more accurate because in bright indoor lighting or outside it's going to be towards the end of the scale. Dim indoor lighting I'm currently at 43%. And in pitch black it goes to 0%. I pretty much never touch my slider anymore after a couple adjustments. Don't get caught up on the percentages. I would be willing to bet that with Oreo at 40% and Pie at 90% the lumens output of the screen was the same.
Ady1976 said:
It's definitely not smooth across the entire range, all my brightness is almost all the last 10% and actually a pain to set properly, it's worse for me.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
That's more accurate because in bright indoor lighting or outside it's going to be towards the end of the scale. Dim indoor lighting I'm currently at 43%. And in pitch black it goes to 0%. I pretty much never touch my slider anymore after a couple adjustments. Don't get caught up on the percentages. I would be willing to bet that with Oreo at 40% and Pie at 90% the lumens output of the screen was the same.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yeah I don't touch mine once it is setup generally but it's definitely not even throughout the scale, only gets really bright from like 85% onwards, just seems odd the real brightness is so high up, makes for fine tuning a bit difficult.
The screen has been rated a minimum of 1.78 nits and a maximum of 496 so if it truly is linear now, 50% is something like only 247 which isn't that bright at all.
Ady1976 said:
Yeah I don't touch mine once it is setup generally but it's definitely not even throughout the scale, only gets really bright from like 85% onwards, just seems odd the real brightness is so high up, makes for fine tuning a bit difficult.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Hi
So much for AI on adaptive brightness, it's rubbish, and why do Google try to fix things that aren't broken, who needs AI for adjusting a backlight? Seems nothing more than just being able to market the phone as having AI! Never had an issue on Oreo, had it set at 25% with adaptive brightness and it was always the correct brightness wherever I was, which shouldn't be difficult given it's got a sensor to read the light levels.
Now since Pie, last night I turned my phone on in the dark and was blinded by a bright display (Oreo it would have been at it's lowest level in the dark), so turned the brightness down, turned it again later and the same thing, way too bright, and again this morning in a fairly dark room the same thing, far too bright, so I turn it down again. How long will it take to learn? The old method it was tamed immediately, now I'm constantly fiddling with the brightness, how is that progress!
Is there an option to go back to the old method?
Wish I hadn't bothered upgrading, just another year with an Android update with changes for changes sake.
Regards
Phil
PhilipL said:
Seems nothing more than just being able to market the phone as having AI!
Click to expand...
Click to collapse
Totally agree on this. Adaptive battery and adaptive battery are almost non-sense. Only something cool to brand the item.
And Pixel Visual Core is just something super-expensive to make Whatsapp, Facebook and Twitter cameras use HDR+. I'd rather pay something less and not having this feature that is probably expensive (or modifies the perception of the Pixel 2 as super-new and mega futuristic). Also, I've got the feeling they won't use it for Pixel 3 or 4.
Moto X1 was the last to use more CPUs to optimize the phone, before Qualcomm introduced more chips.
Hi
For any one having this issue please report this from your device at Settings > System > About Phone, the more people that flag it the more likely it will get fixed.
For me, I hate these updates that break simple basic functionality and overall add nothing extra to what we had with Oreo. Google really need to test these things properly and stop trying to fix things that simply are not broken!
Regards
Phil
PhilipL said:
Hi
For any one having this issue please report this from your device at Settings > System > About Phone, the more people that flag it the more likely it will get fixed.
For me, I hate these updates that break simple basic functionality and overall add nothing extra to what we had with Oreo. Google really need to test these things properly and stop trying to fix things that simply are not broken!
Regards
Phil
Click to expand...
Click to collapse
Already reported, i shouldn't have to have my phone on 90% to be the same as what it was on 63%
Hello everyone,
I got my device some time ago and wanted to highlight the things that rarely ever get mentioned by your average youtuber.
-) Yes, vibration motor noise is there.
But it feels really intentional, not like it is broken.
For me personally I don't mind it really, just wanted to share it since this is dicussed in this forum.
I don't have the "crackling" that has been mentioned, it feels more like when you set the alarm on an iPhone and rotate the hours/minutes wheel - satisfying.
-) Screen PWM'ing
The display is great, gets decently bright especially when viewing HDR content on YT.
Also the 120Hz is definitely a game changer, you can trust me on that.
What I however noticed coming from my F1 is the PWM.
Feels like they do 240-280Hz PWMing the brightness.
I feel like it is causing me headaches and sore eyes, but might just be the exhaustion after coming home from office work on Thursday's
Will see how it develops - my F1 has also PWM, but at around 4000Hz (!) which is definitely not noticeable.
Anyone of you have noticed the PWM? I might be an isolated case, even all high-end Samsungs's have 240Hz and no one complains ...
If you know a hack to enable DC dimming just shoot me a PM please
Hope I don't have to send it back because of this, would be really a shame.
-) Green tilt
Yes, I have noticed some green tilt at the upper half of the screen.
Only happens at really low brightnesses and with certain silver/grey'ish colors in dark mode with reading mode on.
But it is really minor, you really have to focus to make out a slight green shift.
That is no issue for me really, but wanted to highlight it because of the ongoing discussin.
Actually that was all.
The rest is great so far.
Extremely fast, premium build, nice AOD, battery is good so far, camera is more than enough for me and the sound quality is excellent.
If you want to me to test/check out something just let me know, as long as it doesn't involve ADB
Motor noise?
djuroue1 said:
Motor noise?
Click to expand...
Click to collapse
The vibration motor for the haptic feedback.
GeForce66 said:
The vibration motor for the haptic feedback.
Click to expand...
Click to collapse
Ah ok.I didnt hear that.
About Dc dimming:
I have read that they had problems with it, so it might not come to the stable version but it can be enabled in the developer version.
darkb7 said:
About Dc dimming:
I have read that they had problems with it, so it might not come to the stable version but it can be enabled in the developer version.
Click to expand...
Click to collapse
Any link you can share with me? Maybe there is a chance I can give it a try.
GeForce66 said:
Any link you can share with me? Maybe there is a chance I can give it a try.
Click to expand...
Click to collapse
It was stated about the K40 on Weibo by a Xiaomi official, but since it is the same phone as Poco F3 I guess the situation is no different.
Here is a link: https://en.xiaomitoday.it/redmi-k40-poco-f3-dc-dimming.html
Yeah so I have packed it up again and will send it back to Amazon.
Unfortunately the PWM does not go along with my eyes/brain.
But other than that, great device - can definitely recommend, just make sure you are not sensitive to PWM.
When does PWM kick in according to the brightness settings?
From what I have seen as soon as you are below 100%
PWM?
_j3roen said:
PWM?
Click to expand...
Click to collapse
This should explain very well: https://www.oled-info.com/pulse-width-modulation-pwm-oled-displays
Can you please help me.. I don't know if my eyes are sensitive to pwm or not as I've always used an ips and I don't have the option of returning the phone, I used to get a headache behind my eyes while using my old pc for a long time, so does it relate to it or did you have the same problem?
Well yes, it could be - or you just were in front of the screen too long in general.
For me only my eyes start to burn when i have work in front of the pc all day, but no pain behind the eyes. This only happens with PWM'd OLEDs it seems.
What monitor have you been using with your pc?
GeForce66 said:
Well yes, it could be - or you just were in front of the screen too long in general.
For me only my eyes start to burn when i have work in front of the pc all day, but no pain behind the eyes. This only happens with PWM'd OLEDs it seems.
What monitor have you been using with your pc?
Click to expand...
Click to collapse
samsung monitor b1930n, I used to get the pain after playing for long time. I then switched to a laptop (lenovo z50-70) and the frequency of the pain decreased a lot
I couldn't really find much information. If you have the chance just point a camera at the screen when set to medium/low brightness, if you see the flicker then your screen uses PWM.
To anyone wondering about PWM in the future, notebookcheck measured it at 490Hz. This should be fine for almost anyone.
My current phone Mi 9T has 240 and I did not even know it, so I'm good. Had me scared for a bit with the headaches and whatnot
This is a great phone and I am actually impressed by its display. It's so clear to the point that I enjoyed watching cricket matches on this phone. Great sounds as well, especially for the fact that it's not expensive.
Need assistance !
I'm planning to buy this phone since I'm done with my mi 10T .
Mi 10T having 1 issue which is the only reason i will let it go . The earpiece
has the ultrasonic technology which is annoying and unstable causing a lot of calling issues since there's no a proximity sensor . Even the WhatsApp voice notes having the same issues .
I have looked around for newer phone which i think poco F3 might be the one!
I have tried to look around if xiaomi still using that stupid technology init ! But no luck.
If ur facing proximity sensor issues please confirm since my birthday is coming on sept 18th and I will gify my self a new
Thanks
If you want to change because of the proximity sensor, give the F3 a wide berth. Whether the problem can ever be solved via software is written in the stars - and it is cloudy, very cloudy... I don't think Xiaomi will ever fix this issue.