hi guys
been reading some posts about color banding and some say its due to the color depth of the screen (16 or 24 bit)
is the screen 16bit throughout or only for certain applications,whats the story behind this? it will be a shame if a gorgeous super amoled + is hindered by a 16bit color representation
I think the general consensus is it's running at 16bit becasue the phone was shipped before the drivers were complete. Like earlier phones, it's expected to be fixed via an update.
BarryH_GEG said:
I think the general consensus is it's running at 16bit becasue the phone was shipped before the drivers were complete. Like earlier phones, it's expected to be fixed via an update.
Click to expand...
Click to collapse
Or is the panel 16 bit, and they'll need to improve dithering?
I'm not sure the SAMOLED panel is actually capable of 24 bit. Anyone have any definitive info?
GSMArena says that the screen is 16bit
4.3" 16M-color Super AMOLED Plus capacitive touchscreen of WVGA (480 x 800 pixel) resolution
kersh said:
GSMArena says that the screen is 16bit
4.3" 16M-color Super AMOLED Plus capacitive touchscreen of WVGA (480 x 800 pixel) resolution
Click to expand...
Click to collapse
Is'nt 16M supposed to be 32bit?
Just to clear out this rumor.
The phone is 16M (24bit). The drivers are supporting 24bit, they are not crippled due to early release or anything.
Some applications, specially the browser, are showing some banding, specially for gray shades. Thats been like that since the Galaxy S. It's probably some trick to "accelerate" graphics.
But if you open the same website on opera or firefox for android, you will see they render it in full 24bit and most of the banding goes away.
Android 2.3.3 is capable of 32bits.
uskr said:
Just to clear out this rumor.
The phone is 16M (24bit). The drivers are supporting 24bit, they are not crippled due to early release or anything.
Some applications, specially the browser, are showing some banding, specially for gray shades. Thats been like that since the Galaxy S. It's probably some trick to "accelerate" graphics.
But if you open the same website on opera or firefox for android, you will see they render it in full 24bit and most of the banding goes away.
Click to expand...
Click to collapse
Thanks uskr
But it's not just the browser. If you dig up some of the "banding" posts you'll see it effected games and wallpaper also. The NS had the same problem until Samsung/Google issued an update.
uskr said:
Just to clear out this rumor.
The phone is 16M (24bit). The drivers are supporting 24bit, they are not crippled due to early release or anything.
Some applications, specially the browser, are showing some banding, specially for gray shades. Thats been like that since the Galaxy S. It's probably some trick to "accelerate" graphics.
Click to expand...
Click to collapse
Unfortunately it looks like it's the other way around : Most apps display banding (games, xda etc...) but the Samsung browser and gallery only have banding when you're using GPU acceleration to resize/scroll.
So I think either the display is always in 16bits, and the Samsung browser and gallery use dithering to hide the banding ; Or the display is 16bits when hardware acceleration is used and 24 bits otherwise.
Any news on this issue?
I hate to see this on the angry birds entry screens and in the image gallery backgound.
It's so anoying ... Super Amoled+ shouldn't be a super screen ?
this problem killing me
i prefared gs2 only cuz if the screen
i dont know if the problem with all devices or some some
but im sure its not hardware issue cuz when i take screen shot and check the pic on the computer , its also 16bit
Hi,
have you tried unchecking
Settings -> Display -> Automatic Display Performance
And changing to
Settings -> Display -> Background Effect -> Dynamic???
Might help!
Bye briko78
briko78 said:
Hi,
have you tried unchecking
Settings -> Display -> Automatic Display Performance
And changing to
Settings -> Display -> Background Effect -> Dynamic???
Might help!
Bye briko78
Click to expand...
Click to collapse
thanks , but it doesn't help
Just to clear out this rumor.
The phone is 16M (24bit). The drivers are supporting 24bit, they are not crippled due to early release or anything.
Some applications, specially the browser, are showing some banding, specially for gray shades. Thats been like that since the Galaxy S. It's probably some trick to "accelerate" graphics.
But if you open the same website on opera or firefox for android, you will see they render it in full 24bit and most of the banding goes away.
Click to expand...
Click to collapse
I doubt this.
Tried opera and Aurora and saw the same problem, although I haven't been able to find a gradient-displaying website just now.
However, pictures/gradients look like they were displayed on my old notebook when the graphics failed. 16bit.
It does not at all display 16 million colors. Hoping for an update...
Sent from my GT-I9100 using XDA App
Anybody with Beautiful Widgets, go to live wallpapers and choose live weather without actually selecting it. The sun goes up and down giving a sample of the wallpaper. As the sky changes check out the banding.
This issue I would like to see fully fixed soon because it looks so bad I'm thinking on selling the phone till it's solved... don't understand why so few people talk about it.
You can go to http://www.lagom.nl/lcd-test/ for a gradient check.
I see banding as well on mine using the stock browser but it's not there on Dolphin Browser.
Could this be why the Galaxy S2 score such much better than the HTC Sensation? Because of crippled graphics quality? (i also have noticed the heave banding in all sorts of applications)
MALmen64 said:
(i also have noticed the heave banding in all sorts of applications)
Click to expand...
Click to collapse
I also see it in de OS...
Like for example, when you plug your phone in and turn the phone off. You can see a battery icon that you are charging your phone...
This icon is ugly! Banding!!!
And this is made by Samsung itself... Wtf. Can you check it?
Also they keypad has some banding as some of the bars do also have minor banding, or is it just me?
Related
I am trying to decide which phone to buy: Touch Pro , Touch HD, or others. I like the bigger screen on this one but I read somewhere that it is only 16bit color (65k colors). Is that true or was the review mistaken? It seems strange sicne that wouldn't be enough for good quality pictures and video.
rogerbacon50 said:
I am trying to decide which phone to buy: Touch Pro , Touch HD, or others. I like the bigger screen on this one but I read somewhere that it is only 16bit color (65k colors). Is that true or was the review mistaken? It seems strange sicne that wouldn't be enough for good quality pictures and video.
Click to expand...
Click to collapse
More than enough for any human, 65k like any other good ppc.
I think I saw in the specs that it's an 18-bit screen.
I also read that WM only supports up to 16-bit colour.
16-bit isn't enough for all purposes, especially photos with smooth gradients such as blue skies. Of course 18-bit would still give some banding.
OK, I did some mroe reading and the screens are 18 bit (both Touch pro and Touch hd) but the software is set for 16 bit because its easier on the processor. The 65k colors will be enough. I had thought my iPAQ was more but its the same. I jsut wanted to make sure I could run my AnywhereMap software on the Touch HD.
I heard that the Touch HD can't do 3G on US networks. Is that true and, if so, is there a hack to get around it?
"I heard that the Touch HD can't do 3G on US networks. Is that true and, if so, is there a hack to get around it?"
no htc device ever supported a hack to change the hardware supported frequencies so
doubt blackstone will be different
about the colour nr
then i'd say on such a small screen
16bit should be enough very large screens
one can see the diff with large colour changes on surfaces
but small pda screens one would have to be close
to touching ones eye with the screen to see and then
be being blinded by the backlight would make it impossible anyway
Looks like it CAN do US 3G afterall.
http://www.intomobile.com/2008/12/19/htc-touch-hd-is-compatible-with-us-3g-frequencies-surprise.html
rogerbacon50 said:
Looks like it CAN do US 3G afterall.
http://www.intomobile.com/2008/12/19/htc-touch-hd-is-compatible-with-us-3g-frequencies-surprise.html
Click to expand...
Click to collapse
Nope. It can't.
It's also pointed out in the fourth reader comment at that same URL. The author just missed a very crucial "or" in the specs. I would assume the service manual states what the hardware could be configured to do. It seems that the current hardware is set up for only the first half of that "or".
I'm using the Touch HD on AT&T in the US. No 3G.
i have searched this forum n didnt find the thing i was looking for thts why im starting a new thread....
all windows mobile devices have 65k colors n not 16 million. Is this a hardware related limitation or software (winmo) n driver related or both?
if its only software n driver related than why is microsoft not updating its drivers pack in winmo 6.5? or why is tht limitation not overcome in the neo graphics drivers pack.....
if any moderator decides to close this thread please do answer my query before closing. thanks...
It's related to the HTC hardware (chipset+screen)
kroukes2000 said:
It's related to the HTC hardware (chipset+screen)
Click to expand...
Click to collapse
than why is htc still sticking to 65k screens while is competitors r using 16M colors... apple android n webos all have 16M colors while we r stuck on 65k screens
hispeedworm said:
than why is htc still sticking to 65k screens while is competitors r using 16M colors... apple android n webos all have 16M colors while we r stuck on 65k screens
Click to expand...
Click to collapse
Erm lots of reasons:
1) Cost
2) Performance
3) Not needed
Cost is obvious, who knows what deal HTC have with the screen manufacturer.
Performance... why be shifting 24 bits of data around when you can make do with 16? this means having 24 bit images (IF you want to make the most of the capabilities) although resource files could stay at 16 bit, perfectly fine for buttons and icons etc (actually 8 bit enough for basic resources)
Not needed... this is like saying 12mp camera on a phone... so what? it's not like it's improving quality at all.
800x600 resolution cannot render 24 million colours in the first place, BUT it could manage 480K given this, 65K is probably fine. I'm not sure if the palette is 16bit or 24bit though (and this is important): if the palette is 24 bit, but the screen 16 bit, then it's not too bad at all. If the palette is just 16 bit then 95% of users could never tell the difference, but rare specific photos with a prevalence for smooth shading in one colour might show a slight difference.
It's winmo's limitation.
Sasimi said:
It's winmo's limitation.
Click to expand...
Click to collapse
^ this.
WinMo 6.1 and 6.5 can handle a max of 65.000 colors.
[email protected] said:
^ this.
WinMo 6.1 and 6.5 can handle a max of 65.000 colors.
Click to expand...
Click to collapse
This is just plain wrong... 6.5 has native 24 bit support, and even without it, it's still possible to use 24 bit screens AND render in 24bit (although not for the native components in 6.1 which are limited to 16bit)
Ok as far as I'm aware all Windows Mobile OS up to WM 6.1 is limited to 65k colour!
I'm not sure if WM 6.5 can display 24 bit colour but I do know that WM 7 will handle colour upto 24 bit!!
Also not sure if some of you are aware that most of the recent windows mobile devices from HTC,LG and Samsung actualy have display that are able to display colour from 256k to 16 million but they are locked down to 65k because the limitation of the OS!
ok, than why just 65k in win 6.5 than?
because WM 6.5 it can
its not about WM
there are samsungs running wm 6.1 with 256k...
MOD EDIT
Moved to general discussion as not related to rom development
I've read somewhere that 65k is a WM limitation (also mentioned above). As for our devices, I've read they have 262k displays but only function in 65k mode because of the OS limitation. Maybe that's the case with some competitor devices too, but they apply more aggressive marketing...
IAmSmoke said:
I've read somewhere that 65k is a WM limitation (also mentioned above). As for our devices, I've read they have 262k displays but only function in 65k mode because of the OS limitation. Maybe that's the case with some competitor devices too, but they apply more aggressive marketing...
Click to expand...
Click to collapse
I agree with above post 100%!!! HD has 256K screen but WM uses only 65K of it!! and the other devices which use Wm and say theyre 256K color -- theyre using only 65k of them
BTW - you cant actually tell a difference from a 65k or 16mil colr screen unless you put them side by side, but in everyday use my HD has a ideak screen with 65k, my nokia had 16mil but I mostly used black white and red on it!!!
Kristaps-K9-Lv said:
BTW - you cant actually tell a difference from a 65k or 16mil colr screen unless you put them side by side, but in everyday use my HD has a ideak screen with 65k, my nokia had 16mil but I mostly used black white and red on it!!!
Click to expand...
Click to collapse
That's not true. Simply try a blackshaded background, like the original manilla 2,6 one. It's very easy to spot the pixels as it's something like: Grey, grey-black, black.
And not like on a 16mil screen, grey, grey-grey-greyish black etc. In other words, the ''steps'' taken are too large. A 16 million screen will definately look better.
The difference between a 262k and 16million screen however, is really difficult to discern
Sasimi said:
That's not true. Simply try a blackshaded background, like the original manilla 2,6 one. It's very easy to spot the pixels as it's something like: Grey, grey-black, black.
And not like on a 16mil screen, grey, grey-grey-greyish black etc. In other words, the ''steps'' taken are too large. A 16 million screen will definately look better.
The difference between a 262k and 16million screen however, is really difficult to discern
Click to expand...
Click to collapse
I meant in everyday use -- could you spot those dots on Blackstones WVGA screen??
who cares as long as it works!!
You're all kinda wrong.
It is, in this case, WinMo that is the limiting factor but it is not a limitation of WinMo, it is a limitation of this particular implementation.
As detailed in this article, dating back slightly more than 4 years now, the OS itself would be capable of displaying more than 65k colours if MS's OEM partners wanted to implement it - but they don't.
Intially that was due to limited resources available on mobile devices but, nowadays, it's almost certainly due to the fact that the 256k screens that they use being cheaper than 16m ones.
In the case of the HD and other current HTC handsets, there'd be no point implementing 16m colour support given that the hardware is limited to 256k so to answer the OP's question both the OS and the hardware prevent the HD from supporting 16m colours but, as detailed above, technically it would be possible if only HTC were prepared to put any effort in.
Furthermore, some people claim that it is possible to display more than 65k colours whilst running WinMo (see here) but I cannot help feeling that this cannot be correct.
even most lcd for computers are not true 24bit screens
I have question about Color Depth of the screen. We know that HD2 with WM have a 65K colors. If wm have limitation 65K colors , Android can use 16M colors. If hardware (display and controller) support 16M, I think -HD2 can display Hi 16M color depth.
no i dont think it does... when you drop down the notification bar, the notification items backround looks like poo... but when i took a screenshot and loaded it on my computer it looks smooth compared to the one on the phone
No Good
May be have hardware limitation.
expsvetly said:
May be have hardware limitation.
Click to expand...
Click to collapse
I believe we are stopped by hardware . I doubt HTC would fork out extra (however little it is) for a screen which cant be used.
AFAIK it's not a software limitation on winmo's part, but drivers released by manufacturers. Hopefully the devs will be able to port over/ reverse engineer a display driver.
HD2 screen is limited to 64k by hardware restrictions and NOT software so 16M colour depth will not be possible in Android on HD2.
Mark.
The ego 4G also has this hardware limitations
Sent from my Desire HD using XDA App
Why did they even fathom the thought of that limitation? In some of the movies I watch, it is very noticeable.
rr5678 said:
Why did they even fathom the thought of that limitation? In some of the movies I watch, it is very noticeable.
Click to expand...
Click to collapse
I guess they never realised we would 1 day be running android on a WinMo device which only supports 64k colour lol
Mark.
i always thought it was drivers and software. think we need product code or something off the screen and do some digging. even cheap nokias are 16m
If you didn't know the phone was restricted in color, would you really notice?
polo735 said:
If you didn't know the phone was restricted in color, would you really notice?
Click to expand...
Click to collapse
Yes because some things look like 2 tons of poop
rr5678 said:
Yes because some things look like 2 tons of poop
Click to expand...
Click to collapse
LOL Better than 3 tons, I guess!
this device has a 1024x800 screen resolution, will this cause many of apps n games cant work with this device? i love it but i scared i will lost my favorite apps
From my experience with several 1024x600 devices, most apps will look perfect, some will look weird, and almost none will not run at all.
An example of looking weird would be Google Reader, which only shows an article in a small portion of the screen, even though the feeds and labels lists are full screen.
Its poor programming. I and the company I work for make sure our software will run and look as best as possible on a variety of screen sizes larger than what is presently available. The emulator makes it simple to test and there really is no excuse for this.
Galaxy Tab::Tapatalk
BTW, it is 1280x800, not 1024
According to one site, here r the screen specs:
1920x1080 (1080p HD) (24 fps), 1280x720 (720p HD) - sorry these are camera specs
http://www.phonearena.com/phones/Samsung-Galaxy-Tab-10.1_id5212
Sent from my HTC EVO using XDA App
Not to mention...developers will continue cranking out apps for Tablets. I imagine lots of current apps will be upgraded as well, there are devs already doing this as we speak.
Hi,
Have you ever noticed that when you scroll for exemple internet pages there is a little deformation of the image ? Like the text were warping, and especialy in portrait mod.
Take a look at this video: https://www.youtube.com/watch?v=-4-tKflikYY&feature=youtube_gdata_player
Do you know if it's hardware or software problem ?
I was wondering the same thing. It's due to how LCDs refresh, top to bottom, line by line. Given the fact that our display is so dense with pixels, and the GPU isn't extremely powerful (it's a tablet after all), this is bound to happen.
It also happens on iPads, so don't think it's exclusive to the N10.
Sent from my Nexus 4 using xda app-developers app
I noticed this too back when I had my N10. It was very pronounced when scrolling in portrait mode. I thought it was another flaw until I had to go back to the HP Touchpad (running android) and noticed it too. But it was very hard to see on the Touchpad. Like stated before, its because it is pushing all those pixels.
It's not really disturbing but, i don't know if it could ever be fixed or we just have to deal with it...
I had a little freak out about this when I first got my N10. I had it on my galaxy tab 7+ and thought it was just an issue with that tablet, turns out its the refresh point of the screen and some people are really sensitive to it.
Anyone know if phone screens refresh top to bottom in portrait mode while tab screens refresh top to bottom in landscape mode?
Sent from my Nexus 10 using Tapatalk HD
I always thought that would be part of the butter project?
Has to do with the combination of a very high resolution screen with a gpu that is not strong enough or optimized to power it. You didnt see this issue at all in the ipad 2 but did see it (albeit slightly) in the ipad 3 due to the huge increase in screen resolution from the ipad 2. The issue is also not in the ipad 4 at all, the increase in gpu performance stopped it from happening. The issue is pretty prevalent in our nexus 10s and I definitely notice it but its not as jarring after awhile.
are google going to "optimise" this then? it is rather annoying
That's pretty weird. I've been using my Nexus 10 since early December, and never saw or experienced anything like this. The youtube video also looks pretty strange to me -- I don't have any of the lag in scrolling that is apparent in that video. In the video it appears that something is really eating up cycles in either the CPU, GPU or both. My own N10 appears to be much faster -- no lag or delay like the video shows, and none of the deforming or skewing that shows on the video either.
What are you guys looking at that "deforms" when you scroll? Do you developer options enabled that might affect video performance, e.g., Transition animation scale modified, Animator duration scale, Disable HW overlays? Having trouble reconciling my own experience with the youtube video and what I'm reading in this thread. I can't duplicate any of it on my end, regardless of the website or document I'm browsing or scrolling over...
Nitemare3219 said:
I was wondering the same thing. It's due to how LCDs refresh, top to bottom, line by line. Given the fact that our display is so dense with pixels, and the GPU isn't extremely powerful (it's a tablet after all), this is bound to happen.
It also happens on iPads, so don't think it's exclusive to the N10.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Its not so much because of the GPU. Its the screen limited by the 60hz refresh rate. This can be seen on a desktop if the monitor is in portrait mode and you can find a page that with scroll @ 60fps.