ONLY TESTED ON NIGHTOWL ROM
[This kernel is actually bauner's kernel source from 11.07.2015 with the patch on top]
Also if you want to flash this, make a backup in a twrp compatible format since this kernel uses twrp.
If you don't then.....oh well I don't really care.
And most importantly:
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS. IT IS YOUR CHOICE TO USE THIS KERNEL OR NOT.
With that out of the way, here it is: A WORKING BLACK CRUSH/CLIPPING FIX
This kernel shows that the black clipping issue is NOT hardware related and can be fixed through software.
Actually it was already fixed in 2012 or even earlier.
There was a driver in the source but no one bothered to use it.
So I went ahead and put it into a kernel and fixed a few things here and there to get it working properly.
Actually the fix is just a simple value change in a single header file.
The currently attached kernel still uses the "other driver" method but the outcome is roughly the same anyways.
bugs:
--brightness settings
--colour calibration
--a lot more....
The brightness settings take too long (for me) to implement so I just left it there without it.
Also this can be worked around by using apps like Screen Filter which add a dark overlay on top of the screen.
The colour calibration is completely off. This one is actually is easy to fix but I don't know how it should look like so it is how it is for now.
As for now. You will see an orange hue in recovery and during boot. If you turn off the screen (once) everything becomes blueish.
The orange hue was an attempt to fix the blue. It seems like it is still too blue.
There is also a bad gamma calibration (or the lack of one at all). The image below shows what I mean.
{
"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"
}
We are at the first stage because I really don't know how the mdnie gamma (second stage) settings work. (However it still looks nice.)
Anyways this kernel does what it is supposed to do: show that black crush is not hardware related.
One would wonder as to why no one else tried to do this (especially since the fix was there since who knows when).
Hopefully someone will actually spend time on this and get it working properly.
For now it is what it is and no more.
Maybe I should also say that this kernel is not suitable for daily use but I assume most people figured this out.
The cause of black clipping
From what I found out, the following is responsible for the black clipping.
Code:
static int s6e8ax0_gamma_ctl(struct lcd_info *lcd)
{
s6e8ax0_write(lcd, lcd->gamma_table[lcd->bl], GAMMA_PARAM_SIZE);
/* Gamma Set Update */
s6e8ax0_write(lcd, SEQ_GAMMA_UPDATE, ARRAY_SIZE(SEQ_GAMMA_UPDATE));
return 0;
}
[file: s3cfb_s6e8aa0.c]
Getting rid of either s6e8ax0_write line also gets rid of brightness settings and adds the blue hue but fixes black clipping.
Also this one seems important.
Code:
static const unsigned char SEQ_GAMMA_UPDATE[] = {
0xF7, 0x03,
0x00
};
[file: s6e8aa0_param.h]
There doesn't seem to much to change with these 3 values (especially since 0xF7 shouldn't change).
Changing 0x03 to 0x00 has the same effect as deleting one of the s6e8ax0_write lines.
So basically it is just a few lines that completely mess up the display.
A "good" fix?
This is just my opinion etc etc....
A possible fix would be to set 0x03 to 0x00 and reimplement brightness settings in the rom instead of the driver.
This is based on the assumption that it is easier to do a black overlay in the rom while it would still have the same effect.
Then all that is left is a decent calibration and we would have a perfect display.
Source
Commit
These 2 are irrelevant, kind of...
Thank you for the great stuff. Will definitely check soonest possible.
Boot up screen tone is quite warm, and after boot its very cool(everything's bluish). But the important thing is it works properly, couldn't see any black clippings.
Nice job.
avincric said:
Boot up screen tone is quite warm, and after boot its very cool(everything's bluish). But the important thing is it works properly, couldn't see any black clippings.
Nice job.
Click to expand...
Click to collapse
Thanks for the feedback.
Regarding the blue hue:
It should "cooldown" after the first time you lock the screen (bug but hard t fix).
In recovery it stays warm all the time.
You can change the colour temperature under the display settings in the rom if the colours are too cold.
I forgot to add this in the OP.
ruleh said:
ONLY TESTED ON NIGHTOWL ROM
[This kernel is actually bauner's kernel source from 11.07.2015 with the patch on top]
Also if you want to flash this, make a backup in a twrp compatible format since this kernel uses twrp.
If you don't then.....oh well I don't really care.
And most importantly:
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS. IT IS YOUR CHOICE TO USE THIS KERNEL OR NOT.
....
Click to expand...
Click to collapse
I've tried this kernel but it only hides the effect and makes the colors even warmer.
Settler11 said:
I've tried this kernel but it only hides the effect and makes the colors even warmer.
Click to expand...
Click to collapse
Lock and unlock your screen to get rid of warm colours.
However this kernel is badly calibrated anyways so you won't see any decent improvement in your daily use (it actually makes it harder to seperate black tones).
ruleh said:
Lock and unlock your screen to get rid of warm colours.
However this kernel is badly calibrated anyways so you won't see any decent improvement in your daily use (it actually makes it harder to seperate black tones).
Click to expand...
Click to collapse
Doesn't work. Besides, I've restarted it. Also, I wasn't able to change the brightness after this update as well. So not so good, sorry.
Related
I got a Nexus One last week and have a question for other Nexus One owners: has anyone noticed any weird "bleeding" or "ghosting" on the screen (not sure what to call it)? In the browser, I have noticed that, for example, if there are colored pixels on one row of pixels, the entire row of pixels seems to be slightly discolored. If I rotate the phone and hold it in landscape mode, the same things happens but then it is vertical instead of horizontal (that is, still *rows* of pixels going across the short side, not the long side).
Here is a crappy picture I made with the most noticeable parts highlighted:
{
"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"
}
That was taken while I was viewing this page, in case you want to check yourself:
http://en.wikipedia.org/wiki/Google_maps
(normal, not mobile Wikipedia!)
Anyone else seeing something like this? Other than this, I LOVE the phone and would really hate to have to send it back.
Sure do
I never noticed it until i saw this. But sure enough when i opened the browser it had the same thing on the page that i was already on.
have the same prob and im positive everyone else does. Its a software problem as zooming in, everything is all sweet. So there will prob be some kind of fix in the future. Nothing bad enough to send in the phone.
It might be a software issue, but it shows up in every program it seems - if you look hard enough!
Hmm, HTC now wants me to send in the device. Anyone else see this? I don't want to send in the phone and just get another that has the same problem.
Try loading this and look at the background when you are zoomed all the way out:
http://herzeleid.com/n1/test.html
ive already told u. we all have this problem. if it bothers you that much send it in.
I tried really hard to look for this on my N1, but couldn't see it. I have better than 20/20 vision so that shouldn't be a problem
Anyways I looked long and hard in both portrait and landscape and couldn't see anything wrong.
u need to fully zoom out to see it. and like i said its a software issue.
I did zoom all the way out, no dice. Not using the stock browser though.
I live in Germany so I would really like to avoid sending the phone back if possible, since I would have to send it to a friend, etc.
If this is a software issue, I can deal with it since it can be fixed. It happens even outside of the browser though, so I don't think it is (only) a zoom issue. For example, I can see it in the Facebook program. On the Facebook home screen, there are 6 icons, with lines below them, and then text below that (see here if you don't know what I mean). I can see this discoloration between the lines. The "~" in the following diagram represents pixels that are not the same color as the pixels directly above or below:
Code:
(Icon) (Icon)
----------~~~~~~----------
News feed Friends
download dolphin browser and see if u still have the same problem
I see the same effect there.
i dont see it .. normal browser zoomed all the way out ... o well i guess im lucky
Confirmed; I see the same effect. Also on this live wallpaper:
The white stripes in this wallpaper will show the same thing. I'm going to guess that this is the case for all N1s.
Response from HTC:
After performing the test you recommended, I noticed a small difference similar to what you described. The difference I noticed was that there seemed to be a lighter colored line of pixels on the same row as where it says Advertising Programs, Business Solutions, and About Google--essentially what you mentioned. However, this line remained with that row when i scrolled the page up and down, and was also no longer present when the device was turned to landscape mode. It was not something I would describe as a bleeding, either, as this is the only row it happened in. However, I noticed many more lines when I checked the Google News page. When I adjusted the brightness to what I would consider a normal, high brightness, I had to look very closely to see the lines, but I could still faintly see them. When comparing it with the screenshot you included, it does appear to be the same type of issue. As such, I think you are right; it is apparently a limitation of the display. As for if anything can be done, the lines become much less noticeable if the brightness is turned up on the screen; there is unfortunately not anything else that can be done as it is a matter of the hardware. I do apologize for any inconvenience you may have experienced, and I thank you for pointing this out, being patient, and helping to test this theory with the test and the screenshot you provided.
Click to expand...
Click to collapse
(I told him to check www.google.com, the row with "Advertising", etc. is just the bottom row of links there.)
:/
Ahh yeah, I've my brightness turned down at the lowest (I find higher settings blinding--this is quite a screen). Turning it up does lessen the effect, but not make it disappear completely.
It was my understanding that is was just an issue/limitation of current AMOLED screens.
Just like an LCD screen looks bad when you view it from the wrong angle.
All N1s have the 'problem'.
GlenH said:
It was my understanding that is was just an issue/limitation of current AMOLED screens.
Just like an LCD screen looks bad when you view it from the wrong angle.
All N1s have the 'problem'.
Click to expand...
Click to collapse
My understanding too, there was another thread on here somewhere where someone said the same and seemed to know what he was talking about.
That said I cant see the problem on my screen, though that could be my eyesight though.
Its probably due to the unusual layout of the rgb pixels. I can now see it on Google home page in classic mode zoomed out.
No big deal. Perhaps their scaling algorithm was designed for an even RGB distribution, unlike AMOLED's. Its still readable, which is all I care about. Of course, I never really "read" a web page at that zoom level anyways.
Thank you for posting this on XDA. I have posted the same issue since day one on these sites.
nexusoneforum.net/forum/nexus-one-tech-issues-bug-reports/373-nexus-one-streaky-screen-issue-please-post-here-if-you-got.html
google.com/support/forum/p/android/thread?tid=774a196159681fa2&hl=en
The consensus from both forums is that it's the nature of the beast of an AMOLED screen. Which is disappointing. The screen is my only complaint about the phone. I have to keep it at 100% brightness not to see them. Which gives me about 2 hours of battery life.
I have an NC, rooted with autonooter, and everything seems to be working ok, but on lots(most) app's dialogs, including the nook popup UI, I will get get white on white text.
Has anyone else seen this or have a fix? It makes several apps a guessing guessing game and checkboxes have no descriptions so I haven't been able to check any of them.
Thanks!
i have the same problem!
me too! * Hoping for a quick fix!*
So, if its not a unique issue, are there people who have working rooted nooks that don't have the issue? I'm assuming that stock/unrooted NC's don't have the issue so is this some setting that needs tweaking when we open up the rest of the android OS?
hypoxichypoxic said:
So, if its not a unique issue, are there people who have working rooted nooks that don't have the issue? I'm assuming that stock/unrooted NC's don't have the issue so is this some setting that needs tweaking when we open up the rest of the android OS?
Click to expand...
Click to collapse
I assumed it was an issue with the rooting process.
Im having the same problem with the long-press pop-up menu in xScope. I had to use trial and error to memorize the location of each option.
Sent from my Nooted friend...
What applications are you seeing this in? I haven't noticed white on white text.
I have noticed that Tasker's action tab has light blue on dark blue that's really hard to read. I think that's the only one I've seen
How do you add a bookmark in xscope? Thanks
I've had this problem with the pop-up windows in XScope and RedditIsFun, although I feel like it must have happened at other times as well. It's always in a pop-up window.
I find the ADW settings screen very hard to read. It's white text on almost white background & I first thought that they were grayed out. Very annoying!
Cheers,
kev
I had it too. I saw it first in an email widget I got off the Market - de.invalidobject.mailwidget or something like that. White on white text on a popup.
Yes. Same here. It is very annoying to see Table of Content with white fonts on white background with my ezPDF Reader. And many pop up screens too.
I feel like the reason for this is because the apps are using the sam sort of theme that the books settings page uses.
The apps are set to be white on black but the book is set to be black on white so they get mixed up.
Sorry if that doesn't make sense it is rather late here.
Sent from my NOOKcolor using the xda app
I found this to be the case in the game Alchemy if you try to get info on items you've created. The popup shows hyperlinks in blue but all other text is white on white and unreadable.
hypoxichypoxic said:
So, if its not a unique issue, are there people who have working rooted nooks that don't have the issue? I'm assuming that stock/unrooted NC's don't have the issue so is this some setting that needs tweaking when we open up the rest of the android OS?
Click to expand...
Click to collapse
I seriously doubt this has anything to do with the nooting, vs just that the default text color is not appropriate for normal Android apps.
I suspect someone can find the way to fix it eventually.
it happens in lots of places
here are some screenshots of what i'm seeing, it seems to be system wide.
No text visible next to the checkbox for what I assume is something like 'set default'
{
"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"
}
In file manager context menu
and here is an example where you can almost see the white text on a settings page
It makes things kind of a guessing game, with possible bad consequences if you choose the wrong option
So, is there a way (setting/app/etc) to change the theme or text color globally or such?
thx!
What I do is I highlight an option which changes the background color of the item but I don't release so I can read what it is, bad part is I have to do it for all menus until I get used to which blank spot I can click. Hopefully we can get this fixed
likearaptor said:
What I do is I highlight an option which changes the background color of the item but I don't release so I can read what it is, bad part is I have to do it for all menus until I get used to which blank spot I can click. Hopefully we can get this fixed
Click to expand...
Click to collapse
Good workaround... I've been also having to use my phone as reference for apps that I use on both such as Tasker.
Such a pain in the arse, but I know help is around the corner. Someone out there with the knowhow is going to change the xml settings for font color soon and share with the rest of us.
likearaptor said:
What I do is I highlight an option which changes the background color of the item but I don't release so I can read what it is, bad part is I have to do it for all menus until I get used to which blank spot I can click. Hopefully we can get this fixed
Click to expand...
Click to collapse
that's what i've been doing. i'm guessing there may be a png we can edit in the system
I am hoping eventually we will have all kinds of custom themes and then all the menus will be black background like in typical android.
I have a serious issue with the color repdoruction of two galaxy s units.
I have bought two used SGS i9000 phones but they do not produce the same colors, and I have warrenty for only one of them!
I have installed Slim ICS 4.2 on both of them to eliminate any rom issues.
Please see the attached images. The thing is, also I dont know which one actually has the correct color? I would definetely prefer the one with the dark tone, but maybe the one with the grey tone has the correct color reproduction?
{
"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"
}
It should be very obvious they do not produce the same colors.
I have checked in the device settings that brightness is the same, and that there is no difference in DNIe and color reproduction setting.
Could there be a difference in the display types or what the hell is going on?
Are you sure that the other device is not Galaxy SL because it has LCD screen not amoled
Do you mean the one with the "light" or "dark" tone?
How can you see the difference between the LCD and Super Amoled screen?
I just checked the one with the "light" tone and it is definetely a GT-i9000 (checked under the battery).
The other one I dont have at hand atm, but im 99,999% sure it is also GT-i9000 (I recall i checked under the battery when purchased).
If both devices are i9000 then i reckon there are some color tweaking problems.
Have you checked the "Device Settings" in your settings? This opens up the AriesParts.apk (aka Galaxy S Settings). Have you tried to play around with the Gamma Bar?
abobobilly said:
If both devices are i9000 then i reckon there are some color tweaking problems.
Have you checked the "Device Settings" in your settings? This opens up the AriesParts.apk (aka Galaxy S Settings). Have you tried to play around with the Gamma Bar?
Click to expand...
Click to collapse
I have checked that both screen settings are exactly the same, i.e. as in default settings. In "color tuning" red,green and blue are set to 1.000 and red-,green-,blue gamma is set to 0.
But you are correct in tweaking the gamma bars can adjust the screen display to look more like the other (the dark one).
I just don't understand why they dont give the same output with the same settings.
Which one of the phones does your screen display look like?
mcmanuf said:
But you are correct in tweaking the gamma bars can adjust the screen display to look more like the other (the dark one).
Click to expand...
Click to collapse
The current screen condition I.e. Washed out colors made me think of one and one thing only. "Gamma"
It was very obvious that the Gamma was somehow increased beyond the default value, hence the washed out screen.
Just tweak it to make the colors look darker and you'll be fine.
mcmanuf said:
I just don't understand why they dont give the same output with the same settings.
Click to expand...
Click to collapse
Yea it even made me curious.
Did you check the colors on a Gingerbread firmware? (The stock one, not a modified one) Are they same i.e. washed out on that too?
So far, thats the first case i have seen like that. So i am sure its more related to some drivers problem and NOT with the phone itself.
mcmanuf said:
Which one of the phones does your screen display look like?
Click to expand...
Click to collapse
I am not sure.
But its certainly not washed out.
If i were to make a choice then i would say that mine looks like with Darker color tone.
Again, i can make it even more darker by tweaking the colors.
-------
Lastly, for my curiosity, kindly adjust the colors using Device Settings and reduce the Gamma. Post another picture after that. I would love to see some results
I actually reinstalled stock gingerbread and the colors seems to be correct here ???
Very strange indeed I must say!
@mcmanuf intresting URL:http://billedeupload.dk/images/m6qdL.jpg Process:C:\Program Files\Google\Chrome\Applicati... Infection:URL:Mal
looks like you got a similar problem, please check if pictures view normal for you and tell me how old the device displaying pictures wrong is to maybe confirm my point
http://forum.xda-developers.com/showthread.php?t=1784735
Beasy30 said:
Same problem here with my Galaxy S and my brother's Galaxy S
So what can I do? I prefer the dark one (my brother's Galaxy S)...
Click to expand...
Click to collapse
There must be something different in the displays and I dont think the drivers in AOSP supports both displays. Even though they are both AMOLED, there must be a driver difference between the two devices that I have and that you have.
Why would we otherwise have the correct colors in GB for both devices, but wrong colors in ICS?
darkcheater said:
looks like you got a similar problem, please check if pictures view normal for you and tell me how old the device displaying pictures wrong is to maybe confirm my point
http://forum.xda-developers.com/showthread.php?t=1784735
Click to expand...
Click to collapse
I know the one with the wrong colors was bought 25/7-2011. So it was also probably manufactured also much later than the first batches of SGS which were shipped june 2010, so they could have used other displays, although still AMOLED.
The device producing the correct colors is definitely older.
I don't really know how to check when the display was produced.. How can i check that?
And also how did you send it in for warrenty. You also said the colors looked fine in GB in your thread, so the warrenty center wouldn't approve if you came in with ICS on it?
I have the exakt same problem with my i9000. It's from 2011 aswell. Must be a new display, which is not playing very well with drivers in AOSP.
No matter how much you tweak the gamma values, you can't get it right. VC or CM color, doesn't matter. CM is a little better.
No solution yet?
Is there no way of pulling the correct drivers from GB and use them in 4.x.x rom, or something like that?
Hello
I had my Galaxy S screen replaced and it's different indeed, seems there are different Amoled displays.
My phone was bought in Feb 2011 and I have CyanogenMOD 9 installed with Semaphore kernel
No new modifications have been done to the firmware and yesterday I had a Samsung Service Centre install a new screen for me, screen was original and I saw all the process. Now my phone's screen seems to a bit darker, like if the contrast was different and the colors aren't fully right
So I guess it¡s true and there are different revisions of the screen that seem to look different on custom roms
I don't have the GB stock to test
Please bear with me if this seems like the dumbest post in the world.
Ok, so right up until a few weeks ago, i loved the split screen feature on my phone. It was as easy as hitting the square button on the bottom, choosing split screen on one app, app folds itself up creating a space below, and then selecting another app to share the screen with. Easy peezee. Could have a video playing in VLC while perusing rss feeds in Newsfold, either on top of one another in portrait mode or side by side in landscape etc. Even my long dead grandmama could do this.
Fast forward to one day last month, i download some usual pixel update prompted by phone, only to discover my oft used split screen is now no more, but now "split top". It doesn't split the screen like it used to do, and i can't figure out how this split top thing is supposed to work. Plus it always says "Pixel Launcher keeps stopping" after several attempts to use the split top function, which is indicating that Pixel Launcher has crashed. But i din't use Pixel Launcher or have it as my default, i've always used Nova Launcher.
Basically i was doing just fine until whatever this update (which i am assuming is 12L) that has ruined split screen for me.
Is there a way to go back to the old split screen way? Or, how the heck do you split screen with this "split top"? I searched around the web and can't seem to find a solution.
I'm really not enjoying my device or being as productive as i used to be.
Hello @LordLugard I just registered to reply here.
After wasting so much time trying to fix this bug on my end, and several factory resets where it didn't fail at the beginning but then it eventually did, I found the solution on another post of a different forum:
-Turn ON system animations.
That's it. That's how it got solved. If you turn them off, the new split screen doesn't work at all. I'm afraid this must be an Android 12.1 bug because I had the exact same bug in a Poco F2 Pro with Lineage 19.1 and Trebuchet as launcher, so it's not phone model specific, not ROM specific, and not even launcher specific.
I hope this helps someone
buggyupdate said:
Hello @LordLugard I just registered to reply here.
After wasting so much time trying to fix this bug on my end, and several factory resets where it didn't fail at the beginning but then it eventually did, I found the solution on another post of a different forum:
-Turn ON system animations.
That's it. That's how it got solved. If you turn them off, the new split screen doesn't work at all. I'm afraid this must be an Android 12.1 bug because I had the exact same bug in a Poco F2 Pro with Lineage 19.1 and Trebuchet as launcher, so it's not phone model specific, not ROM specific, and not even launcher specific.
I hope this helps someone
Click to expand...
Click to collapse
Thanks for the reply.
Where would you "Turn ON system animations"?
I have it in:
"Settings/Accessibility/Text And Display/Remove Animations"
I had this switch on (meaning no animations), what caused split screen to crash. Turning it off solved it.
Hmmm, doesn't work for me. Mine was already in the "OFF" position.
What the heck was ever wrong with the old simple way? It just worked.
{
"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"
}
Bummer, sorry that it didn't help. It just did for me.
I don't think so, but maybe you activated Developer options, and then changed the value of the animations scales?
Just to discard animation related settings.
I'm afraid I'm of no help beyond that
Well, what do you know...a bit of success.
Since time immemorial, i've always turned off animations in Developer Options to 0, as i do not care for all the fluffy visuals.
So on a whim i decided to tinker and set it to the lowest value, 0.5x, and that seems to work now. But the implementation is so much different than the old way, will take some getting used to. The old method was so much better.
Thanks for the input.
I'm glad it helped at the end!
I fully agree on everything, I don't want animations either, but we're stuck with them if we want split screen as long as they keep this bug...
Also not a fan of this new and worse split screen method. You press Home and both apps are gone.
Deleted member 12160633 said:
I'm glad it helped at the end!
I fully agree on everything, I don't want animations either, but we're stuck with them if we want split screen as long as they keep this bug...
Also not a fan of this new and worse split screen method. You press Home and both apps are gone.
Click to expand...
Click to collapse
1,000% this. I'll be returning my brand-new Pixel 6 and returning to my old phone which will never even be eligible for A12
Many Galaxy devices have a Serious issue.
You can't adjust brightness and your display is greenish and not usable.
After many years of hard work and researching.
I found the best and free method to fix this issue
The world first solution without replacing the display.
This will help you to get a 100% usable display.
I spent lot of hard time for this.
Today I will show how to fix this issue by flashing a custom ROM and some small stuff
- There is a way to use Samsung stock roms but it's not stable if anyone interested in that please let me know I will help -
{
"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"
}
First of all your device must be the Exynos model
1) Install TWRP
2) Make a EFS backup (very important)
3) Download and install (flash) any Aosp ROM,
(Evolution x ROM recommended)
4) Root your device (if ROM already have Root you're good to go)
5) Download Color changer pro & pwmfree Apk files (can't provide download links for color changer pro because it's a paid app you can find it somewhere on internet for free) Asop roms doesn't limit maximum brightness but Samsung roms does. So after flashing aosp ROM you can easily bypass display flickering issue by setting brightness to maximum amount easily by brightness slider top on notification panel.
6) (VERY IMPORTANT) install PWMfree and give notification permissions and display overly permissions.
- DON'T USE YOUR DEVICE AT MAXIMUM BRIGHTNESS WITHOUT USING THIS APP !
This app helps you to decrease amount of brightness by adding a black overly on your display it's working like your adjusting screen Brightness.
7) after installing color changer pro and open it you will ask Root permission and there will be a custom 1,2,3 tabs touch and hold to edit values my best adjustment is R: 239 , G:238 , B: 255 , S: 1.00
And it depends on your display and your choice just slowly play with it till you get the best results and make sure you save the values
Enable developer mode and set all animations to off this will help when screen is dimming while screen timeout.
"Every time you reboot your device it's adjusting the brightness auto and fix itself (pwmfree)
But after every reboot just open color changer pro and select your custom mode it's only need to set if you only reboots"
- There is a way to use Samsung stock roms but it's not stable if anyone interested in that please let me know I will help -
That's all your device is so much better than before
Thanks me later..
No need to install anything, its hardware issue not software issue.
Only reliable fix is to turn on AlwaysOn to always show, let it go to normal color after locking display and wake it with press on home button not a hardware button, works like a charm.
Without installing any third party apps with suspicious wakeups and logs.
No hard feelings tho.
milance92 said:
No need to install anything, its hardware issue not software issue.
Only reliable fix is to turn on AlwaysOn to always show, let it go to normal color after locking display and wake it with press on home button not a hardware button, works like a charm.
Without installing any third party apps with suspicious wakeups and logs.
No hard feelings tho.
Click to expand...
Click to collapse
brother every display is not the same
your display is not hardly damaged
And the issue is the display flex cable this method will work for same devices but not for all devices i have played with this for 4 years and you are correct if the display is not hardly damaged.
I can show you if there is a doubt about it because i tried your method long time ago its worked for Galaxy note 10+ but didnt worked for galaxy s9 plus & note 9 but worked for another note 8.
If your method didnt help this is the last method you can try other than rreplacing the display flex cable (our country there is no place to replace the flex only opinion is to replace the display)
GG