I'm starting to wonder whether Arc is really having it's display set to show 16M colour!! The reason for this is the, I notice gradient/unpolished in few places; example in the "Tweetcast" application.
It;s the application not the screen
Of course it does:
{
"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"
}
What you see is related to that app
I can't be sure, i was counting them but the phone rang and distracted me at 14,283,102. So now i'm having to start again.
1.... 2.... 3.... 4....
Thanks everyone for the reply and everyone pointing to the application!
Is there any application that can be used to test this? (Just to make sure that I don't have a faulty screen)
What you have to bear in mind is that an image is only as good as its weakest link. Artifacts and errors can be introduced by the camera, the compression scheme (if you see banding in any jpeg image, it could easily be caused by compression algorithms), the screen driver software (IIRC, android v1.5 only supported 64k colours, regardless of screen quality) and, finally, the screen itself.
A good test for computer LCD monitors is here: http://www.lagom.nl/lcd-test/. Even though it's designed for PC monitors some of the tests are valid for mobile phone screens (but note that in lot of the tests a mobile phone web browser will perform page scaling and will shrink/expand the images, messing up the results).
However, the Gradient (banding) test should give valid results at any zoom level. If your display is 16M colours, you should get a totally smooth gradient (it does on mine, it's actually better than my computer monitor). Make sure the screen is clean, mine was covered in smeary fingerprints which didnt help at all
daveybaby said:
What you have to bear in mind is that an image is only as good as its weakest link. Artifacts and errors can be introduced by the camera, the compression scheme (if you see banding in any jpeg image, it could easily be caused by compression algorithms), the screen driver software (IIRC, android v1.5 only supported 64k colours, regardless of screen quality) and, finally, the screen itself.
A good test for computer LCD monitors is here: http://www.lagom.nl/lcd-test/. Even though it's designed for PC monitors some of the tests are valid for mobile phone screens (but note that in lot of the tests a mobile phone web browser will perform page scaling and will shrink/expand the images, messing up the results).
However, the Gradient (banding) test should give valid results at any zoom level. If your display is 16M colours, you should get a totally smooth gradient (it does on mine, it's actually better than my computer monitor). Make sure the screen is clean, mine was covered in smeary fingerprints which didnt help at all
Click to expand...
Click to collapse
Arc beat my Streak easily which beat my Dell laptop easily..lol
Well, since everyone says it could be related to application and not the screen or driver itself, I'm convinced. Let me start using and see whether how many applications are like this and might update this topic lately.
Thanks everyone for your replies.
Related
Hello,
I've just got my replacement phone (the previous one had mechanical problems) and the display seems a bit strange with this new device.
There are visible banding effects in color gradients, (web pages, pictures) I know the Lcd has only 65K colors, but I don't remember those bands being so strong on my previous device.
Could you fellow G1 owners check this on your device please? I am in Hungary, Europe and I don't know any other G1 owners here (you know it's not available here, actually mine is an ADP1).
It's easy to check, the effect is very visible on http://www.google.com/news (Google international news mobile site) in the Android browser. It's slightly visible in the dark blue title bar, more in the light blue bar below and very strongly in the "Sections" bar far below.
Please check it and tell me what you have found...
Thanks,
Peter
I see the same issues with google/news. I think it has to do with google's site and/or the g1's browser. Here's a few high quality jpeg gradients Black-White, RainBow and Blue-Red. Unfortunately google compresses them and they look like junk online. So, here's a .zip of the three gradients your can download right to your phone and view with Astro, or extract to pc etc. They should look fairly smooth on the g1, better on pc tho..
use there gradients for w/e you choose.
Hello sonikamd,
Thanks for your help! Interestingly your test pictures look better (smoother) in the standard picture viewer app than in Astro's viewer. Can you confirm that?
Also how old is your device? It looks like that mine (the replacement device) is very old, it's serial number is lower than what I have sent back (purchased in december).
Thanks,
Peter
Just one last quick question: on the incoming call screen there are strange lines appear, do anyone see those on the G1 or it is just me?
Click on the picture to see 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"
}
No, I am not crazy - I am a graphics artist and really sensitive to things like that.
Thanks,
p
nope... [filling characters]
Hi lilithpro,
Thanks for the image, however you won't see the effect on a screencapture (like you attached). I made the pic in Photoshop (from a captured emulator screen) to show the effect - I exaggerated the effect in the pic a little.
You should check your device's lcd during an incoming call to see it. I think it is something to do with the lcd panel. Today I managed to check an other G1 and it showed that effect, too.
So it seems it is not my ADP1's problem.
look at the picture..
{
"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"
}
Understand?
on the phone its looks ok..
i dont have this bug on the officle rom..
any solution?
Our Heros baaaad camera? =)
no i think he means the 'cubes' on the picture, you can see it better when it is a bit smaller, http://hero.host-il.co.il/IMAG0001.jpg, click on that link and not make it bigger(so it fits in your webbrowser screen)
Dude exactly the same problem that I have with all 2.1 roms... I already reported:
http://forum.xda-developers.com/showthread.php?p=6148051#post6148051
take a look at the next posts too... i think it's a driver/software problem, because with 1.6 i don't have the problem...
there must be a solution, any chance if we somehow replace the camera app from a 1.6 build ?
edit:
seems somebody is working on a fix... http://forum.xda-developers.com/showthread.php?t=662436
incomer said:
no i think he means the 'cubes' on the picture, you can see it better when it is a bit smaller, http://hero.host-il.co.il/IMAG0001.jpg, click on that link and not make it bigger(so it fits in your webbrowser screen)
Click to expand...
Click to collapse
Exactly .. These strange cubes..
any Solutions?
while they may be working on a fix, the issue will be fixed when we have an official rom and therefore official camera drivers in the kernel.
This thread had me puzzled for a while as I couldn't see the effect, until I followed some of the links & found a photo of someone's pc screen.
What you're seeing is a moiré pattern. It doesn't reflect a bug in the image creation software. If anything's faulty is the software you're using to view scaled images; it's making a crap job of scaling the image using an inadequate sampling technique, probably point sampling.
The reason you are only seeing it with certain image sources is probably down to dithering. Moiré patterns appear when an image is sampled which contains a very fine repeating pattern. In this case it could well be something as innocent as the camera driver using an ordered dither to improve the image. OTOH it is possible the driver is introducing an erroneous fine repeating pattern of tonal variations.
Either way, you won't see any issues if you use decent software to view or process your images. For example, I couldn't see any issues when viewing images in Chrome or XNView. Windows built in software is a different matter, no surprise.
Yeah, same here. I could not see the effect being described in post one on my MacBook no matter how long or how scaled the image was in my browser.
I do however see it on the link posted above of the computer screen. I have to agree that it is not an issue with the camera or the phone software itself..
It is a software issue of the phone...
How come older pics taken with Android 1.6 builds are being scaled OK?
http://www.youtube.com/watch?v=7-62tRHLcHk
Have a look at this video if you have time - about a hour.
It tells you why the X10's screen refresh rate is only 30 frames per second, and shows that SE's opengl driver seems to be well written too.
yep, it was quite obvious, it's also a great video for anyone willing to write games for Android (or any handled device using OpenGL)
On the other hand i don't think the driver is that good, i've already found some really annoying issues on the OpenGL extensions I used : out of the two extensions I tried including the widely used draw_texture OpenGL extension, both aren't using the correct screen resolution and are either scaled or cropped to fit a 800x480 screen resolution.
You can easily reproduce this by trying to draw a 2D texture on screen using glDrawTexfOES() you'll see that the texture looks scaled and the coordinates are wrong because it's trying to fit a 800x480 screen but the X10 is using a 854x480 resolution... so it just chops off the 54 remaining pixels and scale it to fit the screen, and that sucks badly since you can't trust the reported screen resolution and you have to hack a path for the X10 in case you want to use that extension.
The same thing happens if you try to use the GL_OES_framebuffer_object extension, when you bind a buffer you'll only only get 800x480 pixels out of it... and the worse part is that it's not even scaled to fit the screen, so it actually crops the 54 remaining pixels and don't render anything there, so this one is definitely unusable unless you want a big black bar on the right of your screen
Of course, those extensions are surely not -needed- to make an OpenGL game, (the first one is just a fast way to draw a 2D texture on screen, and the second one is an advanced feature that's not supported by default on OGL 1.0 and 1.1 (hence why it's an extension heh))
But it's still a shame to have such issues on such a high end device, it's like the driver wasn't meant for this screen resolution and they just hacked it into the X10, Hopefully this will get fixed when we get Android 2.1 and OpenGL 2.0
Interesting to see the Droid does better than the Snapdragon phones by quite a bit.
{
"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"
}
AFAIK there is no Android phone with an eInk display.
eInk Display swap:
I wonder if there's a device out there with a modem that would be a good candidate to replace the screen with an eInk, or at least, sunlight readable display?
The last time I looked into this the graphics driver itself would probably need replacing too, making it much more difficult than a simple screen swap. Also I was unable to get find a donor phone with a screen size to match off the shelf eink displays and also sourcing an eink display was difficult too. I need to learn more about how displays work and how I can search to get a phone and screen to match. Any ideas on this?
Kindle:
Perhaps I need to come at it from a different angle? The old kindle is eink and Android... and it has 3G... but it's hard to hack with... it wouldn't be easy to turn into a proper phone. That I will have to investigate. Any other ideas?
NookTouch:
The NookTouch would be a lot of work to turn into a phone but it's technically possible. You could go hostmode, usb hub for mic/speaker/headset and add a USB modem but that's going to be messy. To do this neatly you'd be cutting up the Nook and would at least want a low profile way of connecting into the USB port. Plus charging might then become difficult, especially if trying to do the induction charging hack. I think other avenues are better to try.
I don't think that the old kindle is android based, and besides it wouldn't be ideal as it's not touch-screen
or you could go down the 50/50 route and follow this guide:
I use a matte screen protector and using an app like Cool Reader (since I'm on Android). I change the background to a moderate to light grey and the font to a dark grey about 25% -30% lighter than black. Turn down the screen brightness to about 75% outside and 45% in doors. Then change the font by adding fonts to the system fonts to a more soothing type face like "antipasto". Increase line spacing to about 125%-150% and margins to no more than 10pt on all sides.
See the above image for what this looks like. It isn't exactly like E-Ink, but it is nicer than staring at a bright white screen. This trick should work with any app that lets you tweak the text and background colors, on iOS or Android.
{
"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"
}
source: http://lifehacker.com/5937104/diy-e+ink-contact-shortcuts-and-dropbox-slideshows/gallery/1
I have major display problems on any CM based ROM with crazy jumping and unreadable screens.
I have tracked the problem to the display of white lines. A screen shot is OK, so its hardware - either the Adreno200 GPU or my screen.
Problem Description:
Lines (pixel lines that is) containing a significant amount of white randomly do not display. As a result the display "scrunches up" with a gap from the bottom. Any background to the app, and sometimes the desktop will display in the gap at the bottom as it has not been written over.
Note the "bottom" in this context is the button end of the phone, thus rotating the phone leads to different screen areas being affected.
Affects all the CM ROMS I have tried, with the latest CM10.x ones being the worst. There was no issue with the stock LG ROM.
Images:
1.
{
"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"
}
Coloured triangles produced by "OpenGL Demos" app are OK
2.
White Triangles loose lines and scrunge up. I used the Demo prog as the code is the same, just a color change!
3.
Screen shot, so not a software issue. What they should look like!
5.
Google Play. Unusable. Note hte white background is OK. It just seems to be items that are layered onto the screen.
Apps with black backgrounds and grey/coloured text are fine.
What have I tried?
I have tried messing with OpenGL HW settings with no effect.
I have messed with screen brightness.
I have tried various ROMS.
I tried moving processing from the GPU to the CPU, but that completely messed the display, and I had to re-install the ROM
I haven't tried altering the refresh rate from 60hz, but cannot find if this is possible. I think its a refresh problem, but not sure. Its almost as if the white lines are sent faster than the screen can handle and they are missed during the display phase.
The other theory is that the GPU does some special acceleration cleverness for white areas the screen can't handle.
Any ideas?
Any Adreno200 settings I could try?
Any bridges nearby I could jump off?
p.s. Photos taken from the Optimus Nexus Me port here:
http://forum.xda-developers.com/show....php?t=2397696 not that it matters which ROM it is.
Obviously, it's not "soft" problem, it's a "hard" one, replace the screen.
LeoPosas said:
Obviously, it's not "soft" problem, it's a "hard" one, replace the screen.
Click to expand...
Click to collapse
That was kind of where I was heading, but I was concerned that an aftermarket screen would have the same problem. This screen was fine with the stock ROM, so was hoping for a magic setting change.
Thanks for the response. Really wanted to run your Zoe ROM, but that was worse.
To be honest, I wouldn't replace the screen on this phone anymore. It isn't worth it anymore.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app