Related
Hi Galaxy S II users and developers!
I'm working since months on Galaxy S II Super AMOLED+ screen calibration and rendering customization.
As it takes a lot of time to get something really usable, I decided to publish dev snapshots as a free application on android market.
This project takes so much time because I reverse-engineer all the mDNIe image converter registers one by one. Same for the ld9040 Super AMOLED+ controller.
Then I measure the potential effect of settings found, transform it into comprehensive settings etc.
I also back-up all this by measurements made with a calibrator.
Most of this reverse-engineering will be published as GPL source code.
I don't provide any kind of support for the dev snapshots but I'm sure you'll be interested discussing screen stuff here.
Icon chose is self-explanatory: unstable software!
I have ambitious plans for this application. It may become more powerful than anything you saw before affecting screen rendering on any mobile device
I've installed the Market version but can't see differences between the Native and Samsung mode.
Same as with the earlier version you distributed on Twitter. I've read there you said it worked only on your SGS2. I guess it has been fixed now but still, no changes for me.
EDIT: I see a change now between the 2 modes, my screen mode was set to Movie, not Standard. And I remember having seen in the app you change the Standard mode settings only. Maybe worth adding it to the 1st post?
I was also using the movie mode but sometimes the screen will became a little bit greenish.
I'm so happy with the screen Turner now especially with light blue!
Sent from my GT-I9100 using XDA App
exciting only things i hate after switching to sgs2 (from i9000) was color calibration (and banding issue) and a bit sound quality which can be increased even though its not that much difference..
@supercurio do you have something in mind about color banding or its just calibration?
Nice start supercurio!! Happy to know you have started working All the best
thanks for the early feedback:
@snark_be as its really dev snapshots, I won't document it as virtually anything can change from one day to another.
Thats why sharing your observation with other curious experimental testers is so valuable
As someone stated before, I got good result against light blue colours...
Sent from my GT-I9100 using xda premium
pan466 said:
exciting only things i hate after switching to sgs2 (from i9000) was color calibration (and banding issue) and a bit sound quality which can be increased even though its not that much difference..
@supercurio do you have something in mind about color banding or its just calibration?
Click to expand...
Click to collapse
Color banding: mostly done already.
Disabling artificial sharpening on everything make any banding very hard to notice.
Still, some apps are runing in 16-bit mode without dithering on MALI GPU instead of 32bit as you can see in Angry Birds RIO introduction animation.
Samsung settings apply sharpening even on dithered images. Result is not good, as expected.
The gradient pattern in today's app show that.
Gradient itself is a screen screenshot of Samsung browser rendering, for an accurate simulation.
The app will be declined for power-users, allowing full control over all the settings.
Sharpening, color saturation or tones: its all a matter of user preferences.
For Calibration I'll work on linear domain, directly tuning AMOLED hardware and not mDNIe effect.
Its what allows the best precision and avoid ending with 7 or 6bit usable per channel, but due to how is supposed to work factory calibration it's also the only way to fix color calibration issues, that makes some screen very different from others in terms of white balance, especially in low brightness modes.
hi
i tried tune it but it doesnt work.
When you look at letters ex web you see bluring letters. I discovered i had the same problem on windows 7 but switch of smooth edges of screen font and font are sharp crisp. Take a look http://forum.xda-developers.com/showthread.php?p=15554743#post15554743.
supercurio said:
Disabling artificial sharpening on everything make any banding very hard to notice.
Click to expand...
Click to collapse
But it makes the text look fuzzier. Maybe I need time to get used to it.
snark_be said:
But it makes the text look fuzzier. Maybe I need time to get used to it.
Click to expand...
Click to collapse
Yes, everyone eyes gets lazy when used to a sharpened result.
Immediate comparison makes the normal rendering looks blurry even if it's not − brain trick!
kamartonus said:
hi
i tried tune it but it doesnt work.
When you look at letters ex web you see bluring letters. I discovered i had the same problem on windows 7 but switch of smooth edges of screen font and font are sharp crisp. Take a look http://forum.xda-developers.com/showthread.php?p=15554743#post15554743.
Click to expand...
Click to collapse
Maybe you just don't like Android font hinting.
Personally I prefer stronger hinting like freetype "Best Contrast" one available on Linux desktops.
Issue with this kind of string hinting is that it doesn't play well with arbitrary font size.
Shapes become 1px or 2px wide but nothing in between, probably why Android uses an intermediate hinting, that eventually works better on higher density screens.
does this only work on stock based rom? are you planning to get this working on cm based rom as well?
awesome-member said:
does this only work on stock based rom? are you planning to get this working on cm based rom as well?
Click to expand...
Click to collapse
It will work on CM based ROM when they'll re-add mDNIe support in their kernel.
mDNIe feature doesn't depend on kernel patches as Samsung nicely allowed customization in their own driver.
Of course this official driver must be enabled (CM) and not destroyed in its functionality (hardcore's patches)
I discussed it with Unhelpful and codeworks a few days ago and will contribute if needed.
Edit : seems to work, even though difference barely is noticeable, I guess it'll improve with updates
this may be a solution of fixing the left side yellow tinted screen just like mine
WOW~~supercurio you are come back again~welcome! just installed it from market~
native mode seem look soft and warm ..i like it..
samsung mode look dazzling and cold..
but i think it's a long way to go...
but i am very happy..you are back...
because i love your voodoo lagfix voodoo color voodoo sound for SGS..
also hope you can bring some things for SGS2~~
Says this device is not supported, running CyanogenMOD7 ver 31
Incredible difference. I really hated the sharpening Samsung do. Cannot thank you more for your hard time put into this.
This has potential to be a major breakthrough for SGS2 phones. Modifying our displays to fit everyone's needs is a much needed addon.
Thanks Supercurio!
Hi, I am still fairly new around here (and to the custom ROM scene) and I have been lurking around for some time. So far, I haven't had the need to ask any questions as they have all been answered in other threads, but here's one that I am curious about; it's one that I have noticed in a few custom ROMs I have tried so far.
[Q]: What is the mDNIe scenario and what does it do?
It is located under the Advanced portion of the Settings menu. I've ticked a few of them, but it doesn't seem like it does anything.
KunoMochi said:
Hi, I am still fairly new around here (and to the custom ROM scene) and I have been lurking around for some time. So far, I haven't had the need to ask any questions as they have all been answered in other threads, but here's one that I am curious about; it's one that I have noticed in a few custom ROMs I have tried so far.
[Q]: What is the mDNIe scenario and what does it do?
It is located under the Advanced portion of the Settings menu. I've ticked a few of them, but it doesn't seem like it does anything.
Click to expand...
Click to collapse
smhtc said:
mDNIe stands for mobile Digital Natural Image engine.
In stock galaxy S2 rom (at least my i9100 international), under Settings ->Display -> Screen mode, it shows a sample image and three preset profiles - Dynamic, Standard, and Movie. These adjust the brightness, sharpness, contrast on different screens/ in apps like camera.
Custom roms can always have custom settings for these display-related parameters of a phone.
I am not android developer, so I cannot tell you how to turn it on, but I think stock rom has mDNIe enabled by default.
Click to expand...
Click to collapse
I also wondered about this option on CM10.1, but from reading the quote (from another post) above, I conclude that they are just different settings to tune the displaly of the phone. The differences between each scenario are so small that I can't really notice them, so I just leave it on the preset UI mode.
klin1344 said:
I also wondered about this option on CM10.1, but from reading the quote (from another post) above, I conclude that they are just different settings to tune the displaly of the phone. The differences between each scenario are so small that I can't really notice them, so I just leave it on the preset UI mode.
Click to expand...
Click to collapse
Yeah, I dug little into it myself and read that they were some presets for color management. I was kind of curious if they were working properly on the ROM I am currently running and if it would have any impact on battery life as well, but if it's as minute a change as you say, then it's probably not worth investigating, at least not for the time being.
Thanks for the reply and the info, by the way. I guess it's more for display clarity if anyone were to have problems with the viewing screen. I'd give your post a "Thanks" if I haven't already met my thanking limit of the day already. lol I'll be sure to give you one when I get the chance to.
Can this be related to the Galaxy S4 auto-dimming problem? If I set the background mode to STANDARD instead of AUTO, it will probably not dim?
This is not the normal 'lag' but a wierd frame drop issue when scrolling in an otherwise smooth experience.
This doesn't seem to be app specific or kernel specific either. It happens in even the settings app and I've tried pretty much all kernels and different settings but this issue seems to persist. This does not happen in Custom Roms, I tried really hard to replicate it.
I've reported it to Oneplus via the feedback app with logs, but have little hope for a reply from them. I'm just taking a shot at here if anyone else noticed this or maybe even found the reason for it. I checked logs but couldn't find anything specific.
Screenshots attached with 'Profile GPU Rendering' On when the stutter happens.
(Issue since 4.7.6 to now OB4)
Logs of when the stutter happens attached.
Yes am also facing the same.
venky716 said:
This is not the normal 'lag' but a wierd frame drop issue when scrolling in an otherwise smooth experience.
This doesn't seem to be app specific or kernel specific either. It happens in even the settings app and I've tried pretty much all kernels and different settings but this issue seems to persist. This does not happen in Custom Roms, I tried really hard to replicate it.
I've reported it to Oneplus via the feedback app with logs, but have little hope for a reply from them. I'm just taking a shot at here if anyone else noticed this or maybe even found the reason for it. I checked logs but couldn't find anything specific.
Screenshots attached with 'Profile GPU Rendering' On when the stutter happens.
(Issue since 4.7.6 to now OB4)
Click to expand...
Click to collapse
adi105 said:
Click to expand...
Click to collapse
Amazing contribution.
Same issue on OB4. Seems to happen after 3-4 after a reboot
Same things, on custom rom though..
MarcoReckless said:
Same things, on custom rom though..
Click to expand...
Click to collapse
Extensively used CNP and Omni, even intentionally tried to replicate this but couldn't. Seems it's restricted to just OxygenOS.
When Ivrun stock oos, I always use renderkernel. It is the smoothest I've ever seen on this phone. Not sure how to read the GPU bars but it never exceeds above the navbar area. It usually stays right in the bottom half of the navbar.
Give render kernel a try and you really wont be disappointed.
swapavi said:
When Ivrun stock oos, I always use renderkernel. It is the smoothest I've ever seen on this phone. Not sure how to read the GPU bars but it never exceeds above the navbar area. It usually stays right in the bottom half of the navbar.
Give render kernel a try and you really wont be disappointed.
Click to expand...
Click to collapse
Using render right now and yes it is by far the smoothest kernel. But this issue still persists. The only common factor is OxygenOS, I'd assume it to be a hardware or screen protector issue but it does not happen with custom ROMs.
After talking to @joshuous this is what he suspects could be the reason for the issue. Thanks again for explaining.
"The issue was mainly because the graphics buffer could not be dequeued (to allocate free buffers for graphics)
But that was as deep as I could trace
I haven't yet figured out a way to trace further
Maybe OOS screwed up somewhere trying to allocate too many buffers to graphics but not freeing them in time for more frames to be rendered"
There is no likely solution as of yet, will post if and when.
I experienced the same issue for the first time on OB4 and it persists from time to time. Solution: Reboot
Ok so as a temporary fix I found enabling 'Disable HW Overlays' from developer options helps a lot.
This maybe similar to a fix for YouTube lag found on Nexus 6.
https://www.xda-developers.com/fix-youtube-lag-on-the-nexus-6/
Hi, occasionally I have a similar problem where I experience intermittent lags or heavy frame drops during scrolling. My setup is OOS 9.0.3, stock kernel, unrooted.
Turning on "disable HW overlays" definitely helps a lot, but in my case just turning the screen off and on seems to get rid of the quirk at least until I turn the screen off.
Also there was a thread on XDA apparently talking about the same kind of lags, and the OP there said to have solved it by tinkering with some custom kernel to crank up the CPU frequency whenever s/he touches the screen. I didn't try it myself though.
same on op6/6t
on latest stable oxygenOS all ok...
but betas and older stable same lag after fast third scroll/tap... kernel cannot fix it, it's rom issue (
Same issue on oneplus 7T! But no one talks about It, it's absurd. Didn't find any solution, I'm getting crazy because is always so visible
Inviato dal mio HD1903 utilizzando Tapatalk
Hello! I flashed Icecold kernel on my redmi note 5 plus, its super fast! but my touch screen suddenly acts up, its not major, like when im typing on my keyboard the letters sometimes gets doubled without my intention, or inside a game, when im using too much skill or touches the game exits and goes to home or recent apps.
So im asking is it possible that the kernel is affecting my touch screen? if it is what should i do? or is it my touch screen digitizer? Thank you for the help and answers!
I was using Icecold Kernel 5.1 before and I was experiencing it. Now I am on KangarooX Kernel and so far, I haven't experienced the double tap on keyboard.
RSBluee said:
I was using Icecold Kernel 5.1 before and I was experiencing it. Now I am on KangarooX Kernel and so far, I haven't experienced the double tap on keyboard.
Click to expand...
Click to collapse
is kangarooX fast?
Wrong forum
jaedstermedina said:
is kangarooX fast?
Click to expand...
Click to collapse
It is actually smooth but the battery life is better on Icecold Kernel.
jaedstermedina said:
Hello! I flashed Icecold kernel on my redmi note 5 plus, its super fast! but my touch screen suddenly acts up, its not major, like when im typing on my keyboard the letters sometimes gets doubled without my intention, or inside a game, when im using too much skill or touches the game exits and goes to home or recent apps.
So im asking is it possible that the kernel is affecting my touch screen? if it is what should i do? or is it my touch screen digitizer? Thank you for the help and answers!
Click to expand...
Click to collapse
Because this kernel is for Note 5 Pro (whyred) not Plus (vince), so it's normal that something will break, i was suprised that it actually boots lol.
Hi All,
I decided to do a mini review, in case someone is on the fence with buying the device, or just wants to read a different perspective than what you can find on Youtube about the 9 Pro.
This first post will be a general overview, focusing on changes coming from the 8 Pro. The second will be more development-related, and a deeper dive into the device itself.
The 9 Pro vs the 8 Pro
Coming from the 8 Pro, here are the biggest changes that stick out:
- The screen itself is much higher quality. I used to have black crush as well as a green tint at lower brightness levels on the 8 Pro, but the 9 Pro is free of these issues. Screen gets darker when it's pitch black and no longer burns my eyes out.
- The camera is much better (as advertised). I'm finally able to take photos of my kids running/jumping around and the image is no longer blurred.
- Google Dialer and Google Messages are default. FINALLY. I love the Google Dialer and it's great to see this as the default app on the 9 Pro.
- Battery life is definitely improved vs the 8 Pro, I would say somewhere between 10-20% better.
Setup
It took about an hour to setup from scratch. Yes, I know there is a Oneplus Switch app, but that would rob me from experiencing the setup itself, and I need that. In the past I also had issues with the Oneplus Switch, iPhone backups, etc., so I just prefer to set everything up myself.
Near stock Android experience, with just the right additions. I can tweak to exactly how I like it.
For those who are like me, and want to turn off vibration for everything (since I find it annoying). Go into USB debugging mode, and do:
Code:
adb shell
Code:
appops set android VIBRATE ignore
This disables all standard Android vibrations. If you are finnicky and want to be more granular, or do away with vibrations coming from a certain app:
Microsoft Teams - which I use quite a lot - seems to ignore every single setting I have in notifications, but you can disable app-specific vibrations with:
Code:
appops set com.microsoft.teams VIBRATE ignore
Just substitute "com.microsoft.teams" with the package name you want to turn vibrations off for...
I always disable Sleep Optimization under Battery settings, but keep Adaptive Battery and Enable App Power Consumption enabled.
The screen I always have on QHD+ and 120Hz, and disable power savings in the display setting.
The display
Adaptive refresh rate (LTPO) rocks. This is probably why I'm seeing better battery life. The overall feel of the device is just much smoother than on the 8 Pro (and I was using my own custom kernel on that). Colors are beautiful, the screen doesn't have any tint even on lower brightness, so it's great.
Performance
My primary usage is: emails, WhatsApp, Microsoft Teams, phone calls, camera, photos. I do tons of multitasking, listen to music in the meantime, etc., and not a glitch, no lag.
Multitasking
Snappy, no reloading of apps, everything stays in memory (and I have 8Gb version). Switching on a "regular" work-day between emails, calendar, Teams, Spotify, etc. is so seamless, it's an incredible experience.
Everything stays in memory (it does get cleared overnight to help with idle drain, but I'm good with that).
Camera
OK, it's camera time! It's now been 3 weeks with the phone, let's talk about the camera. Mainly comparing with the 8 Pro.
Camera - general
This rocks. I'm finding that 80-90% of the shots I do turn out great. It's better than the 8 Pro, where I would say 60-75% of the shots turned out great.
Camera - everyday shots
Excellent colors, sharp images, even though I keep the settings on 12 megapixels to ensure better handling of light.
Camera - videos
Just perfect. I'm now defaulting to 4k 60fps HEVC videos, and they all turn out great. No complaints here. Stabilization of videos is perfect as well.
Camera - low light
Low light shots got a massive boost with the 9 Pro. Much better handling, less noise, better colors overall.
That sums it up (for now), do let me know if you have any questions!
And now for a deeper dive...
Let's start with what has changed in the kernel/source code!
- Linux 5.4.y branch! This is incredible, having such a recent LTS kernel on my device. My build system (Manjaro Linux) is also using the 5.4.y branch, whcih is awesome. Of course, the Oneplus is using a more dated, 5.4.61+ tag, while Manjaro is at 5.4.113 currently, but still. Very nice
- ThinLTO and CFI are enabled and working by default. Very nice.
- Compiled with Clang 11 branch, so it catches more errors and warnings, and most of the warnings also seem to be fixed. A very big plus here.
- There is still a ton of unneeded stuff turned on in the kernel, but then again that is stock CAF, trying to cover all bases.
Of course, having both ThinLTO and CFI enabled by default on stock kernel has its disadvantages, namely kernel development. Modules can be force loaded from the vendor partition, but then the kernel breaks due to symbol mismatches - which I am now observing with Omega kernel as well, seeing random reboots when the screen turns off.
In the latest source drop from OOS 11.2.4.4, the Oneplus kernel developers actually removed a massive dmesg hog, which is probably a first. Kudos to Oneplus.
thanks for the detailed review, this will definitely help some with the purchase decision.
looking now forward to the first Omega Kernel alpha
Mar-cel said:
thanks for the detailed review, this will definitely help some with the purchase decision.
looking now forward to the first Omega Kernel alpha
Click to expand...
Click to collapse
We're past alpha, already at beta. One more bug to iron out actually before it's stable...
AFAIK LTPO still doesn't work on 11.2.4.4 or am I wrong?
DashDashCZ said:
AFAIK LTPO still doesn't work on 11.2.4.4 or am I wrong?
Click to expand...
Click to collapse
How do you know?
r4p70r said:
How do you know?
Click to expand...
Click to collapse
I myself haven't researched it but many people on oneplus forums claim they have and that it isn't working as advertised during launch event. It is known that LTPO wasn't working at first on the Oppo find X3 pro when it was released and that they fixed it later with a software update so people assume it's the same with op9pro.
DashDashCZ said:
AFAIK LTPO still doesn't work on 11.2.4.4 or am I wrong?
Click to expand...
Click to collapse
It's working fine. Android's built-in FPS counter is not able to handle it.
DashDashCZ said:
I myself haven't researched it but many people on oneplus forums claim they have and that it isn't working as advertised during launch event. It is known that LTPO wasn't working at first on the Oppo find X3 pro when it was released and that they fixed it later with a software update so people assume it's the same with op9pro.
Click to expand...
Click to collapse
That's what I thought at the beginning. I checked it with the FPS counter from the developer options. There you could only occasionally see that it went down to 60hz. On reddit I came across a post in which someone wrote that it is not visible with the fps counter but you can see via entries in logcat that the Hz goes down. I found entries there for switching to 11hz and 1hz. The one on reddit said he would only have found entries up to a minimum of 4hz. So I suppose that works as promised.
r4p70r said:
That's what I thought at the beginning. I checked it with the FPS counter from the developer options. There you could only occasionally see that it went down to 60hz. On reddit I came across a post in which someone wrote that it is not visible with the fps counter but you can see via entries in logcat that the Hz goes down. I found entries there for switching to 11hz and 1hz. The one on reddit said he would only have found entries up to a minimum of 4hz. So I suppose that works as promised.
Click to expand...
Click to collapse
Indeed it's working fine. I imagine the switch mechanism will be tweaked in the future for more fluidity and smoothness.
@kristofpetho hey man! Sent you a message on Telegram. Just a heads up!
Updated 2nd post with some source code-specific stuff. I will expand it once I get the kernel fully running.
Seeing this kernel is basically all I've ran on OnePlus 8 pro, I'm thinking I might get the 9 pro now, but honestly, this has been one of the only good reasons (so far) for me personally to make the jump. Thank you very much for sharing and thanks for the review
So. Finally. Custom kernel is stable. Release tomorrow if there are no errors in the next 24 hours.
kristofpetho said:
So. Finally. Custom kernel is stable. Release tomorrow if there are no errors in the next 24 hours.
Click to expand...
Click to collapse
How to install with no TWRP?
r4p70r said:
How to install with no TWRP?
Click to expand...
Click to collapse
Kernel manager ( EX,...FKM)
kristofpetho said:
So. Finally. Custom kernel is stable. Release tomorrow if there are no errors in the next 24 hours.
Click to expand...
Click to collapse
I’m assuming you’ll make a post on here?
Is it tomorrow yet?
Shooter7889 said:
Is it tomorrow yet?
Click to expand...
Click to collapse
It was tomorrow a couple of hours ago. Thread '[KERNEL] [OOS] Omega Kernel OOS11 [May 2, 2021]' https://forum.xda-developers.com/t/kernel-oos-omega-kernel-oos11-may-2-2021.4271027/
cultofluna said:
Kernel manager ( EX,...FKM)
Click to expand...
Click to collapse
Does fkm work? It had many issues with op8