I would be grateful if people could post their results in this topic after following the instructions.
Okay i posted about this before in the small eui topic but i don't think anyone saw it and it's a general issue that affects everyone so i want to bring it to people's attention.
This phone seems to give a lot of black crush. I have used the stock EUI fw and the small eui CFW and both have it. Black crush is where dark regions of images just turn to solid black so that you cannot see anything below a certain darkness - as you can imagine this is a large issue.
Instructions for the test:
Go here: www.lagom.nl/lcd-test/black.php
You should be able to see all of the squares, 1 - 255
However for me, at highest, retina burning brightness, I can only see down to 7 or so and at a comfortable brightness, only 11 or 12. At lowest brightness I can only see as low as 25 or 20!
Report back how far you can see (at different phone brightness levels including minimum) and also please list what firmware you are using. I wonder if this is an EUI issue or a hardware issue.
Click to expand...
Click to collapse
This is with the screen set to Natural like it should be (the other LE ECO, Vivid etc modes are way over saturated and you actually get colour crush), and even in the other modes it is just like this too.
Because there are these colour modes, i think there must be a way to fix this somehow in eui based fw?
It seems like LE ECO is doing something to mess up the black level and crush all the blacks to make the screen look all contrasty deliberately.
(on a side note, the small eui cfw referred to a change: "Disabled LeEco gamma curve (oversaturation in the daylight)" although i'm not sure exactly the technicalities of it, it didn't seem to help with this issue as on both smalleui and stock x829 it is the same).
One thing i did notice was that on the stock 829 FW, when you first turn the phone on, it DOESN'T have the issue. However when the phone first sleeps it then changes back to the colour mode with the black crush issue (so if it times out to standby or you press the power button etc then you get the problem back).
To me, that seems like the phone is only starting the code the runs the black crush on the first lock screen / standby opportunity.
It wonder if KCAL support could be added to the EUI based CFW? Or if Le Eco's own colour controls (whatever they used to do the colour mode settings) could be user configured. Maybe it is these colour controls that are causing the issue in the first place?
I would be grateful if people could test this and also bring it to the attention of cfw developers (especially eui based).
Thanks
Related
I think, for internet reading this is a good test and producing the results we might expect, but for more general purposes this test is flawed. http://blog.laptopmag.com/android-b...d-handsets-trail/comment-page-1#comment-50669
Method:
"
First, we download My Settings and Advanced Task Killer, two free apps that are useful regardless.
Then, we open My Settings, and do the following:
Turn screen brightness to 40%, and turn off auto brightness.
Turn off Wi-Fi, Bluetooth, GPS location, cell location, and auto sync.
Deactivate screen timeout; that is, make sure the screen stays on indefinitely.
In the Web browser, we turn off Flash support and plug-ins.
We placed the phone in an area that was receiving at least 4 bars of service."
I'm not trying to overly just support the device because I have it, I think many of us knew we wouldn't have great performance when reading black text on white background. So, this only tests on LCD's strength and AMOLED's weakness. Next, the SAMOLED specifically is way to bright to be reading indoors at this % brightness, LCD maybe not quite as much so it'd be best to have like either most common setting (you'd actually need to have devices report this for something accurate, not going to happen), auto brightness would've even been better even though you have manufactures (I think) being able to have too much control over 'perceived' best practice. They removed plug-ins, something I think the Streak might struggle with next to the mighty decoding ability of the hummingbird.
Also, one important thing to note is, they didn't make note of the fact that the Galaxy phones have independent brightness control within the internet browser, perhaps this was set too high/low, I'm not sure how it plays relative to the general brightness (e.g. does it add to the setting to make it even brighter within the browser? Does it override the setting for the browser?). Them not acknowledging this setting gives me some pause, even though it could come at the cost of the battery life even more.
Last and most important, we do more than just browse the internet on our phones. We do need things like video tests, white text on black backgrounds, gaming, audio and other tests run.
In the end, this'll confirm what some users have complained about when it comes to their battery life.
Hey guys. I'm sorry for being a newbie but I'm new to this section and couldn't find the issue in a few other threads that I searched through.
I was really happy with my Nexus 7 until the 4.2 update that introduced several issues.
The most apparent is the autobrightness one. On 4.1 it was a little dim but stable - I could easily read at night and during the day time and it seemed to adjust perfectly in a totally non-annoying manner.
Now, however whenever I read something it keeps flashing - going from 0% to 50%+ in a second and then back after a short period time despite the fact that the lighting conditions do NOT change. It happens even when I'm in a totally dark room and holding the tablet in the very same position without moving it.
Last night I placed it on my desk to watch a movie with no artificial light sources around whatsoever and the brightness would go up or down every 10 seconds or so.
Sometimes I had a feeling that it depends a little on what's currently being displayed as it happens A LOT when playing a movie and it changed more often when a scene would change (for example it got a little BRIGHTER when it was displaying bright images already, thus hurting my eyes).
I usually use my tablet when it's dark already so I find it really almost impossible to read with autobrightness on because books with white background just begin glowing spontaneously in my eyes and then after a few seconds it dims so I have to adjust again and before I do it begins glowing hard again.
Now I know that I can always set it manually but the thing is that I really liked it the way it was in 4.1 - it was perfect at night and also perfect during daytime without me having to change it manually a couple of times a day. I would totally love a feature to be able to correct the autobrightness (Sort of like in Iphones or older Samsung Androids) but what I had on 4.1 was good enough.
Do you guys have this issue as well?
I have a couple of other issues that did not occur on the previous OS version and the tablet is a little bit less responsive (not UI but in apps) so I wouldn't mind going back to 4.1 actually if there's a way.
Yes i have this
Same problem here. Google screwed up auto brightness with their shoddy update. Very frustrating.
Sent from my Galaxy Nexus using xda premium
My C60 has the issue.
This is why I use Lux for autobrightness. I can't use a device without it now.
Why Yoga tablet 2 screen looks so blurred and sharpened at the same time
Have you been wondering why your screen on the 10" Yoga tablet 2 with KitKat doesn't look really crisp even with some obvious sharpening applied? Here is why!
Lenovo screwed up twice!
1. Blur filter is applied. (KitKat ONLY) The BIOS/bootloader defines wrong display resolution. The Intel graphics driver (i915) gets confused and switches on panel fitting which includes a blur filter (fuzzy filter). Normally this is used if the display resolution is different from the frame buffer resolution to scale the image. Here the device just scales 1:1 and applies the filter. Luckily the driver is open source and it turns out there is a way to overwrite this feature No longer true for Lollipop. Thanks Lenovo
2. Sharpen filter is applied. (KitKat and Lollipop) The panel is not programmed correctly. When disabling the CABC feature (/sys/lcd_panel/cabc_onoff) the sharpening effect is gone. But CABC should have nothing to do with sharpen. Unfortunately the specs of the display (AUO B101UAN01.E) are not public so I cannot verify if the correct MIPI DSI commands are sent to the panel.
So our display is softened then sharpened again! What a waste!
Both workarounds are only temporary. After each screen off/screen on sequence the old values are restored by the system. So we need an app which sets the values after the screen is switched on. Or a new kernel. Or Lenovo cares to fix it in a future release
Fix (Root partially required)
I wrote an app which can disable CABC / sharpness filter (requires ROOT) and can disable the blur filter (KitKat, no root required) . Of course I am not held responsible if you brick or burn your tablet. I tested this on my 1050F with rooted firmware S000143_150105.
1. Copy app to device and install
2. Start app and select your setting
3. The settings may apply only after switching screen off and on again.
Source on Github:
http://github.com/Matshias/yoga2sharpness
Bugs / issues
- may not work directly after reboot, only after screen on/off
- fullscreen video may switch on CABC/sharpness filter again
Any suggestions? I'd be really happy if you could test and report
Cheers!
Matt
Update Jan 21
make more reliable and add complete source
Update Jan 26
Reliable implementation as app which automates this process.
Update Jan 30
new version 1.1 (please uninstall old version!):
- add option to start at boot and enable/disable applying the settings at screen on for manual operation
- add little delay after screen on for more reliable operation
- app should be harder to kill by the system
Update Feb 2
new version 1.1.1:
- Fix occasional reboot issue when using the setting on display on. Turns out Android sends screen on broadcasts sometimes even if the display is off. This causes a crash if the filter settings are applied.
Update Feb 11
new version 1.1.2 (please uninstall old version):
- hopefully ultimately fix reboot issues by using different method to start on boot
Update Apr 30
tested with new firmware S000198_150422. Same as before. Lenovo has not fixed the issue, but the app works like before
Update June 3
New version 1.1.3:
- fix full screen video playback re-enabling CABC/sharpness filter. As for CABC itself root is required.
Update June 17
Update for Lollipop version 1.2.0:
- blur filter disable no longer needed
- sharpness filter is still present. If root becomes available for Lollipop this should work there too
Update June 19
Fix for rooted Lollipop - version 1.2.1:
- the mechanism for sharpness filter disable from 1.2.0 didn't work, probably due to SE Linux restrictions
Matshias, you are a legend!
I bought a Yoga 2 10" a couple of weeks ago and the odd blurred and sharpened effect ruins what is otherwise a great little tablet. I'd always suspected it was some kind of odd scaling issue, but I haven't had time or sufficient Android knowledge (or root access on my device) to properly investigate it, beyond making up some test images with alternate 1 pixel wide black/white lines - which were rendering as grey on the Yoga 2.
I had a support ticket raised with Lenovo about the issue, so I've referred them to this post and one on the Lenovo Community forums.
Thanks for your hard work, hopefully Lenovo will implement the fix in a software update soon!
Cheers,
Richard
Thank you!
matshias: Thank you.
The blur filter disable makes a HUGE difference. I really appreciate you taking the time to post your results, hopefully Lenovo will take note and implement a permanent fix.
workes
Hi!
I have just started using your app with the latest firmware on a 1050L.
0) Unrooted device
1) installed your app and applied the non-root part of the fix - worked after screen on/off
2) rooted device with temporary cwm solution from this parent thread (- which worked as well)
3) applied the root-required part of the fix from your app - works as well
Thank you for this!
Great great great! Like the others here I was looking for a solution to this Problem since I bought the tablet.
I am really satisfied with your APP, now everything is way sharper.
BUT: When I test the screens resolution with a screen test APP, only the horizontal ( long sides) resolution seems to be right now. The vertical resolution (short sides) is still just grey, when testing single pixel lines.
Do you have the same Problem, what could cause this?
fanatictentacle said:
Great great great! Like the others here I was looking for a solution to this Problem since I bought the tablet.
I am really satisfied with your APP, now everything is way sharper.
BUT: When I test the screens resolution with a screen test APP, only the horizontal ( long sides) resolution seems to be right now. The vertical resolution (short sides) is still just grey, when testing single pixel lines.
Do you have the same Problem, what could cause this?
Click to expand...
Click to collapse
I see the same if the sharpness filter/CABC is still switched on. If you have root then try disabling the sharpness filter as well and then the screen test look fine. Obviously the sharpness filter in the panel is not uniform in all directions and seems to prefer horizontal resolution (in landscape mode).
Thanks again for the advice!
I just had to enable root, really cant look at that horrid screen anymore! But now it really looks as sharp as an 240ppi Display should look like!
problem
After installing the app I have problems.
In 10 minutes my tablet rebooted 3 times . Android not asked to reboot.
It was crash of sistem. My system is rooted.
After uninstalling I had no problems.
Regurds
Yosef said:
After installing the app I have problems.
In 10 minutes my tablet rebooted 3 times . Android not asked to reboot.
It was crash of sistem. My system is rooted.
After uninstalling I had no problems.
Regurds
Click to expand...
Click to collapse
Did you use the start on boot feature? This might cause it. I uploaded new version 1.1.2 which should fix that problem. Let me know if it works for you.
this is a fantastic fix, one that Lenovo should have implemented themselves
actually when i just got the tablet over christmas, it was running older firmware in which the blur filter was actually not enabled. yes i now realize the text was "over sharp" but it was clear, and what i expected for the price (i.e. not double the price for a galaxy tab S) but i was fine with the sharpness, it looked good, and the tablet otherwise suits my needs perfectly, and gotta love that built in stand. i didn't even know what people meant about the image quality, considering the mid-range target audience of the tablet.
anyway, i recently got the OTA firmware update to the current S000143_150105 and that's when it messed everything up. it enabled the blur filter, and it looked HORRIBLE. i tried to accept it because at 1 ft from the tablet, the text actually looked all right, perhaps even a slight improvement because it was slightly softer. but the blur filter is applied to EVERYTHING, so all the images and everything on the screen was blurred....it was like looking at an HD monitor with a state of the art GeForce video card but using the standard windows video drivers...everything stretched and totally blurry.
this is a great fix, i don't have my tablet rooted and don't want to take the potential battery hit to disable the sharpening filter (since i think it looks good just with the blur filter disabled). it might be in my head though, but i feel like the system is a little more sluggish...maybe due to the update, maybe because of this (great) app...i wish lenovo would fix this, seems easy enough. sours me to an otherwise great tablet for the price.
speaking of battery, i noticed in the last day after installing the fix that my tablet powered off sometime during the day, and when i restarted, the battery had drained about 30%. and it continued to drain faster than before. i previously got well over 10 hours of usage time playing movies and web browsing, in addition to up to several days of standby....today i had to charge it within 24 hours and only got about 7 hours use time and 13 hours standby...any chance it's related to the fix, or has anyone experienced it after the firmware update?
@digitalatlas: Thanks for testing the app.
Regarding your observations, I don't think sluggishness can be attributed to the app. After all it doesn't do much. Only when the screen is switched on or you manually start the app it changes the kernel setting. So it really shouldn't have any impact on performance.
The battery life should also not be affected by the app itself. It does not have any background tasks other than the kernel setting mentioned above and it shouldn't wake up the device as well. Although I saw occasionally that my app gets informed that the screen was switched on even though the screen was not switched on. That caused some reboot issues. But that was fixed with version 1.1.1 and 1.1.2 and I didn't see a reboot since I use 1.1.2. Also there are reports of hangs/reboots by other users unrelated to my app. Anyways it might be the case that changing the kernel setting has some other effect on the hardware, kernel and battery life. According to Intel documentation the filter is not meant to be switched on or off while the display is active. However, it is the only time it is possible to change it in our system. So to be sure we have to test and disable/uninstall the app and see if the battery life improves.
Hopefully Lenovo fixes this with an upcoming update!
Thanks!
Just got this tablet in the mail today and was disappointed by its display. So grateful for your fix, its like night and day with the blur gone. Guess I have a good reason to root now to get rid of the sharpness too. Mind me asking what method you used to root for this firmware?
Falv said:
Just got this tablet in the mail today and was disappointed by its display. So grateful for your fix, its like night and day with the blur gone. Guess I have a good reason to root now to get rid of the sharpness too. Mind me asking what method you used to root for this firmware?
Click to expand...
Click to collapse
I used the temporary CWM method [GUIDE] CWM & Root Lenovo Yoga 2 (8/10/13)
It is easy enough and works fine, but keep in mind that there might be issues with OTAs.
I'll keep track of the battery over the next little while, hopefully it was just an aberration that first charge. I'm getting better results with this second charge since the update and your fix.
Could you or someone post a picture shoeing the effect of turning the sharpening filter off? Might help some of us decide it rooting is in fact worthwhile. Thanks!
digitalatlas said:
I'll keep track of the battery over the next little while, hopefully it was just an aberration that first charge. I'm getting better results with this second charge since the update and your fix.
Could you or someone post a picture shoeing the effect of turning the sharpening filter off? Might help some of us decide it rooting is in fact worthwhile. Thanks!
Click to expand...
Click to collapse
I tried taking pictures but it doesn't really show the effect. Instead I made two screenshots and recreated the filter with GIMP. It should be very close to what the panel does.
Does anybody have any info from Lenovo? I think that this is preposterous! How can someone do that and have it go through testing? Unless there were no tests at all.
Buying Lenovo was a mistake.
v1.2 tested on my new 1050F. Awesome. I was disapointed by the screen but now it's perfect. Thank you so much to have done this patch!
+1
AMAZING PICTURE QUALITY!!.
Without blur picture is good, but witchout blur and sharpness image quality is FU…NG AWSOME!!
THANKS!!!!!
saupiquet said:
v1.2 tested on my new 1050F. Awesome. I was disapointed by the screen but now it's perfect. Thank you so much to have done this patch!
Click to expand...
Click to collapse
+1
Great app, thank you
Are you all running this with rooted devices? Mine is not yet rooted but notice a big difference with this app. How much better is it if I was to root the device? Thank you so much for this fix. I recieved my tablet today and was very disappointed with the display.
This is afix to screen burn issue some of our devices have
Download bluescreen filter and change the opacity 5 %
Thus you temporarily fixed the screen burn.
https://www.youtube.com/watch?v=kOFQ1-ewMOY
watch the video .
Comment in case of queries :good:
If rooted ..Just download a kernel management app...Ex kernel manager or kernel auditor (misspelt)..Go to Color management and reduce all 3 rgb to 200 and set apply on boot...This way you'll face no extra distorted Colors .
ad_anu143 said:
If rooted ..Just download a kernel management app...Ex kernel manager or kernel auditor (misspelt)..Go to Color management and reduce all 3 rgb to 200 and set apply on boot...This way you'll face no extra distorted Colors .
Click to expand...
Click to collapse
This method requires no root .
Nothing gets "burned" in the screen, it's called "screen retention" because it disappears in time.
My XT1644 started to have it. I had applied the last OTA (14-4) and it was still there. Then my phone locked-up in a boot loop and I decided to go back to 14. Well... no more screen retention now!
I used Sfilter Lite, it consumed less baterry and worked well, nowdays I'm rooted and got my colors fixed with XKernel Manager.
---------- Post added at 04:43 PM ---------- Previous post was at 04:42 PM ----------
SoNic67 said:
Nothing gets "burned" in the screen, it's called "screen retention" because it disappears in time.
My XT1644 started to have it. I had applied the last OTA (14-4) and it was still there. Then my phone locked-up in a boot loop and I decided to go back to 14. Well... no more screen retention now!
Click to expand...
Click to collapse
are you saying it has to do with the android version?
It might have to be related with the actual firmware that they are pushing. I was kind of pissed when I noticed the retention, because before I never had it, but now is completely gone.
I have rooted it with ElementalX every time and adjusting the RGB levels didn't help, retention was still there.
Now, I don't even have a Kernel Manager installed anymore. And retention it's gone ¯\_(ツ)_/¯
SoNic67 said:
It might have to be related with the actual firmware that they are pushing. I was kind of pissed when I noticed the retention, because before I never had it, but now is completely gone.
I have rooted it with ElementalX every time and adjusting the RGB levels didn't help, retention was still there.
Now, I don't even have a Kernel Manager installed anymore. And retention it's gone ¯\_(ツ)_/¯
Click to expand...
Click to collapse
I hope the " screen retention" you were talking about is a hardware issue. I dont think software updates or downgrades can fix them.
Only changing the LCD panel can permenently fix them.
I can be wrong btw.
I could see the hour, battery symbol and cell strength indicator when pulling down the top drawer, retained and faded on the grey area. Now they are not there anymore.
If I was taking a screenshot, the retention was not in the screenshot, so it wasn't kept in the video memory. Probably it was in the LCD controller somehow.
Don't know what to say maybe the firmware adjusted the RGB values to less than 256 (what we can do also with the custom kernel).
Which version are you on exactly?
SoNic67 said:
I could see the hour, battery symbol and cell strength indicator when pulling down the top drawer, retained and faded on the grey area. Now they are not there anymore.
If I was taking a screenshot, the retention was not in the screenshot, so it wasn't kept in the video memory. Probably it was in the LCD controller somehow.
Don't know what to say maybe the firmware adjusted the RGB values to less than 256 (what we can do also with the custom kernel).
Click to expand...
Click to collapse
I agree with this. Its not a hardware side issue, because, different screen instances show different image retentions... Its annoying as f*ck, but at least its not hardware... They probably need to update the LCD firmware...
Hardware Issue!!!
It's an hardware issue!!! I had the same problem with my Moto G4 Plus. I unlocked the bootloader to try the ex kernel manager method but didn't work then i took it to the service centre and they changed the lcd panel. And now no screen burn issue!!!
There is a method which I remember one Xdian used to tackle screen burning issue...go to colour calibration in Live display option and put all the values to 95%..
Done
I often have to be very persistent in training the phone for brightness in the auto mode. Especially in the evening, when the brightness slider is to the left of the middle. I set the desired brightness, but it is not fixed. You have to do it 10 times or more, and after a minute the brightness again lives its own life. Has anyone come across this on customs ROMs? Everything was great on stock.
Bookworm Yevgen said:
I often have to be very persistent in training the phone for brightness in the auto mode. Especially in the evening, when the brightness slider is to the left of the middle. I set the desired brightness, but it is not fixed. You have to do it 10 times or more, and after a minute the brightness again lives its own life. Has anyone come across this on customs ROMs? Everything was great on stock.
Click to expand...
Click to collapse
Turn off auto brightness Its Simple
(I dont understood your issue propperly...)
ai.Sanaul said:
Turn off auto brightness Its Simple
(I dont understood your issue propperly...)
Click to expand...
Click to collapse
Maybe you don't know auto-brightness can be trained due to users preferences. At least it works on stock.
Or don't you use auto-brightness at all?
I am accustomed to auto-brightness at any time of a day and I like to use it. I don't want to change it mannualy after each changes of circumstances.
However on the custom ROM the process isn't so easy. I just have doubts if it will be successful at all.
Bookworm Yevgen said:
Maybe you don't know auto-brightness can be trained due to users preferences. At least it works on stock.
Or don't you use auto-brightness at all?
I am accustomed to auto-brightness at any time of a day and I like to use it. I don't want to change it mannualy after each changes of circumstances.
However on the custom ROM the process isn't so easy. I just have doubts if it will be successful at all.
Click to expand...
Click to collapse
i,m on Samsung J2 Pro 2018(i use most) with Super Amoled screen and my phone dosent supports auto brightness but i've seen in Redmi 9 Power (second phone i have) that it works according to light around you and cant be trained at all... i think you been talking about another concept, sorry... Tell me about it more if you can so i can learen about it.
ai.Sanaul said:
i,m on Samsung J2 Pro 2018(i use most) with Super Amoled screen and my phone dosent supports auto brightness but i've seen in Redmi 9 Power (second phone i have) that it works according to light around you and cant be trained at all... i think you been talking about another concept, sorry... Tell me about it more if you can so i can learen about it.
Click to expand...
Click to collapse
There is nothing special to say more here. Just in the auto-brightness mode, the user sets the slider to the desired level at any time. This is repeated a certain number of times and after that the phone remembers the new settings and, depending on this, the new auto-brightness algorithm works. The learning process for brightness is endless. You can adjust it anytime to your preference. In any case, it worked fine on stock and the phone memorized new settings very quickly.
Bookworm Yevgen said:
There is nothing special to say more here. Just in the auto-brightness mode, the user sets the slider to the desired level at any time. This is repeated a certain number of times and after that the phone remembers the new settings and, depending on this, the new auto-brightness algorithm works. The learning process for brightness is endless. You can adjust it anytime to your preference. In any case, it worked fine on stock and the phone memorized new settings very quickly.
Click to expand...
Click to collapse
oh! its a cool thing. Thanks
I tried A11, A12, A13 ROMs, and after that I'm on A10 stock again. I think that's the best way for me to keep my nerve sells. Now the autobrigness doesn't even need additional training.