SPV C100 display spec - HTC Oxygen

Hi,
does anyone have detailed display specs for Oxygen? I need this for adapting frame buffer display driver for kernel.
I'll need: pixel clock, horizontal synchronization pulse width, horizontal front porch, horizontal back porch, vertical synchronization pulse width, vertical front porch, vertical back porch, ac-bias pin frequency.
thanks
Marek

Related

[Q] Calibrate Vertical G-Sensor

My Samsung Tab just fall in the floor and now it loose the rotate functionality.
After going to setting's -> horizontal calibrate. I've managed to make it rotate but only landscape.
1 - Is it possible to have only the vertical sensor broken ?
2 - Is there a way to calibrate way vertical, as the only option availabe is horizontal ?
All the level/bublle app's show's horizontal rotation but no vertical.
Many thanks (sorry my english)
Just a side note! I can play modern warefare 3 with gyroscope just fine i and can see 3d gallery just fine to, what the hell?

[Q] Calibrate Vertical G-Sensor

My Samsung Tab just fall in the floor and now it loose the rotate functionality.
After going to setting's -> horizontal calibrate. I've managed to make it rotate but only landscape.
1 - Is it possible to have only the vertical sensor broken ?
2 - Is there a way to calibrate way vertical, as the only option availabe is horizontal ?
All the level/bublle app's show's horizontal rotation but no vertical.
Many thanks (sorry my english)

Accelerometer off by 26° on X axis

Hi,
I just bought a chinese tablet BS109 from Aliexpress, for the price the tablet is really an excellent value.
However, I have a big annoyance with it:
The G-Sensor is off by 26° on X axis (and 7° on Y axis).
However, it seems accurate (gives the same values for the same position). It's just like if the component would have been bent on the motherboard.
I don't need accuracy on the G-Sensor, but this has 2 nasty effects:
- When in landscape mode, it won't switch to portrait mode without flipping it right by at least 25°
- It's impossible to keep a portrait mode when lying on a table. (Except by locking to portrait mode). It will return to landscape mode as soon as the tablet approach the horizontal lying position.
The "recalibration" tools did not help. (GPS Status or Clinometer for instance)
There is no settings menu for this sensor.
My questions:
- How can we fix such a huge miscalibration?
- Can a calibration fix such a difference?
- Should I consider a Hardware problem? In this case, could it be that the sensor is not properly placed on the motherboard, and that we could fix it by opening the tablet?
Thanks,

Strange behaviour with black when scrolling

Has someone experienced "dancing blacks" with vertical or horizontal scrolling, specially in low bright settings?.(40 or below)
I have purchased an EU ver. Of V30 and i experience this behaviour every time i do scrolling with photos, desktop icons with black contour (like netflix) webpages with black línes or blocks... Or everything containing black colour.
When i move the photo, scroll across website... The part that contains black colour seems to dance on screen, it's hard to describe but it's something like jelly effect, the black part of the object, photo... seems slower and doesn't scroll accordingly. I went to a local store to check it on another unit and discard a faulty one and i saw the same effect.
Regards
That's the feature of all oled displays, nothing you can do with it except changing the brightness to the level it doesn't show any signs of this "violet trails"
i have that behavior too on my H930DS. no solution yet.
The phone regulates it's brightness through PWM, so that you don't have the same issue like on the g flex where the whole display got blurry and grayish when you turned the brightness down. Because the display shuts itself on and off many times per second (222 times according to a German review page), you see that when you are sensitive. Just set the display brightness higher, then you should be fine.

General Getting correct white balance on S23U screen in vivid mode

Anyone who wants to adjust the white balance of vivid screen mode to 6500k - here are my settings, done with a laser spectrophotometer. Gamma is 2.207289 and delta E is 0.3
While every screen is a little different and ideally needs its own calibration, these settings should probably be better than the default settings. with all sliders cranked up to 100%.
With sRGB set on in the developer settings, you'll get a natural looking photo with very slightly more saturated colours than the equivalent photo displayed on a fully calibrated and profiled wide-gamut desktop monitor (it's worth noting that in natural screen mode, the match is very accurate when compared to my monitor and if you're wanting colour accuracy above all, then put it into natural mode)
In the screenshot below, there are four white dots to the right of the green slider position and one white dot to the left of the blue slider position. The red slider is at 100%.
{
"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"
}
dl12345 said:
Anyone who wants to adjust the white balance of vivid screen mode to 6500k - here are my settings, done with a laser spectrophotometer. Gamma is 2.207289 and delta E is 0.3
While every screen is a little different and ideally needs its own calibration, these settings should probably be better than the default settings. with all sliders cranked up to 100%.
With sRGB set on in the developer settings, you'll get a natural looking photo with very slightly more saturated colours than the equivalent photo displayed on a fully calibrated and profiled wide-gamut desktop monitor (it's worth noting that in natural screen mode, the match is very accurate when compared to my monitor and if you're wanting colour accuracy above all, then put it into natural mode with sRGB toggled on in developer settings)
In the screenshot below, there are four white dots to the right of the green slider position and one white dot to the left of the blue slider position. The red slider is at 100%.
View attachment 5834505
Click to expand...
Click to collapse
That looks identical to how my N10+ looks in natural mode @50% brightness.
Color/gamma calibration/accuracy are excellent on the N10+.
dl12345 said:
Anyone who wants to adjust the white balance of vivid screen mode to 6500k - here are my settings, done with a laser spectrophotometer. Gamma is 2.207289 and delta E is 0.3
While every screen is a little different and ideally needs its own calibration, these settings should probably be better than the default settings. with all sliders cranked up to 100%.
With sRGB set on in the developer settings, you'll get a natural looking photo with very slightly more saturated colours than the equivalent photo displayed on a fully calibrated and profiled wide-gamut desktop monitor (it's worth noting that in natural screen mode, the match is very accurate when compared to my monitor and if you're wanting colour accuracy above all, then put it into natural mode with sRGB toggled on in developer settings)
In the screenshot below, there are four white dots to the right of the green slider position and one white dot to the left of the blue slider position. The red slider is at 100%.
View attachment 5834505
Click to expand...
Click to collapse
Srgb option disappears when you switch to Natural.
erik2041999 said:
Srgb option disappears when you switch to Natural.
Click to expand...
Click to collapse
Yeah, it does. I'd imagine it's forced to on...
erik2041999 said:
Srgb option disappears when you switch to Natural.
Click to expand...
Click to collapse
Not needed... if correctly calibrated from the factory. Color/gamma calibrating by eye is impossible... it won't work.
If you use the phone a lot in the sun ( definitely not recommended!) the vivid setting will help compensate for the bright light color washout.
Noted, thank you and thank you.
dl12345 said:
Anyone who wants to adjust the white balance of vivid screen mode to 6500k - here are my settings, done with a laser spectrophotometer. Gamma is 2.207289 and delta E is 0.3
While every screen is a little different and ideally needs its own calibration, these settings should probably be better than the default settings. with all sliders cranked up to 100%.
With sRGB set on in the developer settings, you'll get a natural looking photo with very slightly more saturated colours than the equivalent photo displayed on a fully calibrated and profiled wide-gamut desktop monitor (it's worth noting that in natural screen mode, the match is very accurate when compared to my monitor and if you're wanting colour accuracy above all, then put it into natural mode with sRGB toggled on in developer settings)
In the screenshot below, there are four white dots to the right of the green slider position and one white dot to the left of the blue slider position. The red slider is at 100%.
View attachment 5834505
Click to expand...
Click to collapse
Cheers buddy, it's really help, like it now looks great.
Sorry if this is a silly question but where on the Cool/Warm scale do you have your marker, there are 5 dots there but these aren't shown on your screenshot above.
Thank you for these settings, much appreciated.
Guess this doesn't matter at all when using Eye comfort shield?
That cool/warm slider is a very blunt instrument, so it remains exactly in the middle with the settings I showed for the RGB sliders
Eye comfort shield messes with the white balance by reducing the blue component, so while you have it activated, you're right that this doesn't matter
dl12345 said:
That cool/warm slider is a very blunt instrument, so it remains exactly in the middle with the settings I showed for the RGB sliders
Click to expand...
Click to collapse
Great, thank you very much.
I found using the Eye Comfort Shield fixed the white balance AND restored the saturation level of the the S22 Ultra. I prefer cooler tones so I set it all the way to the left. By default, the S23 Ultra screen is less vibrant than the S22 Ultra so this works great.
Thanks for this.
If you get chance, can you check some different areas of the screen with a white background to check uniformity. Mine seems a bit brighter in certain areas. Just wondering if I've got a duff one or not.
blackhawk said:
That looks identical to how my N10+ looks in natural mode @50% brightness.
Color/gamma calibration/accuracy are excellent on the N10+.
Click to expand...
Click to collapse
No it's not. It's ok for 3 years ago but in terms of today it's average.
cledee said:
No it's not. It's ok for 3 years ago but in terms of today it's average.
Click to expand...
Click to collapse
The in depth test results on any variable refresh rate display will show the fallacy of your statement.
They are impossible to accurately calibrate across their many brightness/refresh ranges.
The brightest variable alone skews color calibration/accuracy which has a exponential effect on the gamma calibration.
This is one big reason I blew off the N20U was it's variable rate display. In terms overall color accuracy/calibration/viewing angle color shift the N10+ is one of the best smartphone displays ever produced. There are dozens of test parameters.
Samsung can't even get their basic display lamination technology right now let alone the much more difficult display color calibration. In Samsung's defense variable refresh rate displays are impossibly hard to color calibrate through their many brightness/refresh rate ranges. The differences are small but there. The higher brightness levels of these newer displays are making calibration even more difficult like it wasn't bad enough already.
This N10+ display has well over 8K hours on it and is still perfect. Zero detectable flaws or pixel fading; excellent longevity. Time will tell... ain't bragging but you see how chill I'm hanging.
dl12345 said:
Anyone who wants to adjust the white balance of vivid screen mode to 6500k - here are my settings, done with a laser spectrophotometer. Gamma is 2.207289 and delta E is 0.3
While every screen is a little different and ideally needs its own calibration, these settings should probably be better than the default settings. with all sliders cranked up to 100%.
With sRGB set on in the developer settings, you'll get a natural looking photo with very slightly more saturated colours than the equivalent photo displayed on a fully calibrated and profiled wide-gamut desktop monitor (it's worth noting that in natural screen mode, the match is very accurate when compared to my monitor and if you're wanting colour accuracy above all, then put it into natural mode)
In the screenshot below, there are four white dots to the right of the green slider position and one white dot to the left of the blue slider position. The red slider is at 100%.
View attachment 5834505
Click to expand...
Click to collapse
Hello, good day to you, could you please elaborate on that? I'm not knowledgeable enough but as I do understand is that vivid mode uses wider DCI-P3 color gamut (on some percentage) so why do you suggest to use sRGB in developer settings?Also you said that natural mode looks more accurate than vivid in comparison with your display (you didn't tell if it is wide gamut, but mentioned earlier "...fully calibrated and profiled wide-gamut desktop monitor...", so I assume you have exactly this one), as I get it , this can be true if your monitor has a sRGB emulation because other spaces should make same colors more vibrant, saturated. Again, I can not say it for a fact, just want to know whether I'm right or wrong, would be glad to read explanation on how actually things work, thanks in advance.
SLEStyler said:
Hello, good day to you, could you please elaborate on that? I'm not knowledgeable enough but as I do understand is that vivid mode uses wider DCI-P3 color gamut (on some percentage) so why do you suggest to use sRGB in developer settings?Also you said that natural mode looks more accurate than vivid in comparison with your display (you didn't tell if it is wide gamut, but mentioned earlier "...fully calibrated and profiled wide-gamut desktop monitor...", so I assume you have exactly this one), as I get it , this can be true if your monitor has a sRGB emulation because other spaces should make same colors more vibrant, saturated. Again, I can not say it for a fact, just want to know whether I'm right or wrong, would be glad to read explanation on how actually things work, thanks in advance.
Click to expand...
Click to collapse
Yes, my monitor is wide-gamut. I'm not 100% sure exactly what you're asking, although I'll try to give a short explanation on colour management. This info is not specific to phones. It's general colour management information. There are lots of resources on the net if you wish to learn more. Some of the info below is guesswork, since Samsung's colour management is a bit of a black box.
Android 13 is colour managed. That is to say, ostensibly it has all these components for a fully colour managed workflow, although many apps are still not colour managed.
On a properly calibrated and profiled desktop system, any photo should display using the same colours and look identical to the way the same image displays on a different fully calibrated and profiled monitor. For example, a calibrated and profiled AdobeRGB monitor should display an identical sRGB colourspace image to a properly calibrated and profiled sRGB monitor. This is how it should be.
Take, for example, the RGB value RGB(255,0,0). On a wide-gamut monitor, this maximal red value will be a deeper shade of red than on a smaller gamut sRGB monitor. So when no colour management is present, this would mean that instead of displaying the correct sRGB red primary colour, a wide-gamut monitor would display its version of the red primary, which is way more saturated (deeper) than the sRGB red primary. Colour management ensures that the sRGB red primary will map to the equivalent red hue in the wider monitor gamut and thus display correctly.
On the S23U, the display device profile shipped with the device appears to be non-standard and deliberately displays more saturated colours - I assume this is precisely what is intended by the "Vivid" setting in Display Settings. It looks almost as if no mapping is being applied between the image's sRGB colourspace and the wider display gamut, resulting in more saturated colours. Why Samsung chooses to do this, I don't know - it's probably because these cartoonish looking colours are seen as a desirable marketing feature. Without access to the source code or detailed technical documentation on Samsung's colour management implementation, it's just guesswork as to what they're doing. It's why the icons look more saturated in vivid mode: their sRGB colour value is being displayed in a wider-gamut space, resulting in a more saturated colour.
To partially fix this, setting sRGB on in Developer Settings is supposed to force the display's gamut to emulate sRGB when displaying pictures and so the image colours display as intended rather than in the over-saturated form that Samsung thinks consumers want (although it seems to be less than perfect in its emulation of sRGB to be honest, as it still looks a little more saturated than when using the Natural colour scheme). One would reasonably expect that pictures displayed when Picture Mode sRGB is on with Vivid mode to be the same as how it would look if you set the display mode to Natural, although it's not a 100% match (it's close). This Picture Mode setting is essentially a picture-specific sRGB mode as opposed to the system-wide natural display mode that forces the display gamut to emulate sRGB at all times.
This Picture Mode setting apparently has no effect when watching videos. It only affects pictures. As an aside, having watched several videos encoded in different colour spaces in the different S23U display modes, video colourspace mapping appears to work properly (ie. no over-saturation). Most Youtube content is encoded to REC.709 which has a similar gamut to sRGB (REC.2020 is used for HDR and is much wider gamut). I've watched a combination of REC.709 and REC.2020 videos on the S23U while running the same video on my desktop at the same time and the videos look identical on the S23U. In fact, video colour reproduction looks remarkably accurate.
dl12345 said:
Yes, my monitor is wide-gamut. I'm not 100% sure exactly what you're asking, although I'll try to give a short explanation on colour management. This info is not specific to phones. It's general colour management information. There are lots of resources on the net if you wish to learn more. Some of the info below is guesswork, since Samsung's colour management is a bit of a black box.
View attachment 5853577
Android 13 is colour managed. That is to say, ostensibly it has all these components for a fully colour managed workflow, although many apps are still not colour managed.
On a properly calibrated and profiled desktop system, any photo should display using the same colours and look identical to the way the same image displays on a different fully calibrated and profiled monitor. For example, a calibrated and profiled AdobeRGB monitor should display an identical sRGB colourspace image to a properly calibrated and profiled sRGB monitor. This is how it should be.
Take, for example, the RGB value RGB(255,0,0). On a wide-gamut monitor, this maximal red value will be a deeper shade of red than on a smaller gamut sRGB monitor. So when no colour management is present, this would mean that instead of displaying the correct sRGB red primary colour, a wide-gamut monitor would display its version of the red primary, which is way more saturated (deeper) than the sRGB red primary. Colour management ensures that the sRGB red primary will map to the equivalent red hue in the wider monitor gamut and thus display correctly.
On the S23U, the display device profile shipped with the device appears to be non-standard and deliberately displays more saturated colours - I assume this is precisely what is intended by the "Vivid" setting in Display Settings. It looks almost as if no mapping is being applied between the image's sRGB colourspace and the wider display gamut, resulting in more saturated colours. Why Samsung chooses to do this, I don't know - it's probably because these cartoonish looking colours are seen as a desirable marketing feature. Without access to the source code or detailed technical documentation on Samsung's colour management implementation, it's just guesswork as to what they're doing. It's why the icons look more saturated in vivid mode: their sRGB colour value is being displayed in a wider-gamut space, resulting in a more saturated colour.
To partially fix this, setting sRGB on in Developer Settings is supposed to force the display's gamut to emulate sRGB when displaying pictures and so the image colours display as intended rather than in the over-saturated form that Samsung thinks consumers want (although it seems to be less than perfect in its emulation of sRGB to be honest, as it still looks a little more saturated than when using the Natural colour scheme). One would reasonably expect that pictures displayed when Picture Mode sRGB is on with Vivid mode to be the same as how it would look if you set the display mode to Natural, although it's not a 100% match (it's close). This Picture Mode setting is essentially a picture-specific sRGB mode as opposed to the system-wide natural display mode that forces the display gamut to emulate sRGB at all times.
This Picture Mode setting apparently has no effect when watching videos. It only affects pictures. As an aside, having watched several videos encoded in different colour spaces in the different S23U display modes, video colourspace mapping appears to work properly (ie. no over-saturation). Most Youtube content is encoded to REC.709 which has a similar gamut to sRGB (REC.2020 is used for HDR and is much wider gamut). I've watched a combination of REC.709 and REC.2020 videos on the S23U while running the same video on my desktop at the same time and the videos look identical on the S23U. In fact, video colour reproduction looks remarkably accurate.
Click to expand...
Click to collapse
Natural mode should produce near faithful reproduction*. Vivid is intended for bright lighting conditions like outdoors to reduce the effect of color washout.
Using a standardized color chart makes set up and verifying work flow much easier.
*On the N10+ is this mode color accuracy is excellent cam>display, I verified it with a color chart shot 50% brightness (I think it was), natural mode, image shot with noon sun. I couldn't see any deviations on the N10+'s display... not bad for an Android.
However haven't verified that on a known color calibrated monitor. So there's that
I have big problems with the screen and cameras.
Compared to my previous phone S22 Ultra the s23 ultra has a worse screen - faded colors, turns green and blurs details in photo-video. Front camera - now captures less detail because it has less megapixels. The main camera shoots with a green tint. When s22 photos are as transparent as possible.
Am I the only one like this in the world? Or what?
1 photo - s23 left, s22 right
2 photo - s23 right, s22 left
3 photo - s23 top, s22 bottom
More photos here

Categories

Resources