Related
Hi there.
Wondering if it's just me, but do most wallpapers seem to look really bad? I just put some hi res wallpapers I use on my laptop on my phone, but they all look terrible when set and don't get why. I have very few wallpapers that actually look good on my phone.
edit: Thinking about it, will they only look good if they're the same resolution size as my screen?
If you are using gallery to set them , and your pictures are high res , gallery most likely is messing up. Try setting wallpaper with "QuickPic" from maket and let us know if its better.
I9100 screen resolution is 480*800, so a wallpaper at that resolution will certainly look better. But as it has 8 homescreens you can also use 960*800 wallpaper, which will be a scrollable one, besides you can put a HD wallpaper too, you just have resize it by dragging the orange lines to the corners perfectly.
Regards.
You must mean the color banding you see. The SGS2's stock firmware has a 16-bit screen driver. The guys from Cyanogen hinted at making it 32-bit, making the screen look beautiful, but it'll take a long while.
Somewhere I think Samsung downclocked everything there is on the SGS2. Because now it all of a sudden charges faster than before, it's faster. And I wouldn't look up if they overclocked it to 1.5 ghz. I bet they have something up their sleeves for the 16-bit screen.
When I read what I just typed, I actually think that won't happen.. Mehh
[Q]How does TW hold up at higher LCD Density?
any notifications pane or dialer issues?
You mean lower?
Sent from my GT-I9300 using Tapatalk 2
Yeah, I meant lower. It looks like it borks it. I'm stuck at samsung boot screen.
junglizste said:
Yeah, I meant lower. It looks like it borks it. I'm stuck at samsung boot screen.
Click to expand...
Click to collapse
i couldnt get LCD Density Modder to apply a new density, crashes when trying to save it
Yeah I heard of someone using a lower density that got it to boot but it looked ugly with some settings I believe
Sent from my GT-I9300 using Tapatalk 2
used rom toolbox. set it for 220. stuck at samsung boot screen.
cleared cache
still stuck.
re-flashing the root-rom fixes it.
all setting and data intact.
Anyone succeed with changing ppi yet? Here we are, screen the size of a planet... and the email size shows what... 12 characters across??? Duh...
So - it's driving me nuts after running slimics on my SGS at 182ppi and I'm sure stock sgs3 is in the 240 range like most others seem to be.... but the LCD modder pro that I bought isn't good with ICS roms and wasn't sure if someone has already changed their build.prop for a better ppi/dpi (never get those straight...)?
Ozark_8125 said:
...I'm sure stock sgs3 is in the 240 range like most others seem to be...
Click to expand...
Click to collapse
The SGSIII ppi is 306
Ozark_8125 said:
ppi/dpi (never get those straight...)?
Click to expand...
Click to collapse
dots per inch is something that is normally discussed with printers, scanners, etc.
pixels per inch is something that is discussed with displays
demarcmj said:
pixels per inch is something that is discussed with displays
Click to expand...
Click to collapse
Thanks for that - just seems counter-intuitive for some reason that when you lower the pixels per inch that your display gets smaller. I'd love to get a better ppi for the phone though, lots more use could be made out of that football field sized screen.
This phone does not deal too well with lower ppi settings. Used LCD Density Changer and got stuck at boot. Had to restore to CWM backup and tried again with different settings to no avail.
Used LCD Resolution to try lower resolutions without the reboot effect and it looks like crap. I could not get past the bloated numbers on my pin lock, let alone look at the monstrosity for the icons on the screen. My HTC EVO (+ dialer fix) does 161 without any issues and makes such good use of the smaller screen.
Was hoping to get something better with the larger screen in the S3. Hoping that someone finds the trick to this phone!
The one poster above used from toolbox, which is what I saw as a recommendation for ICS roms but looks like it failed for him.
Sent from my SCH-I800 using XDA Premium HD app
I used Rom Toolbox to change the LCD res on the same day I rooted. I went from 320 to the 200 I was on my SR, then to 220, to 260 and increasing back up as I thought it was way too small. At some point I couldn't get back to 320 anymore as the max on the slider is the current res. So I had to reflash the rooted img to reset it back.
I'm a little confused here. LCD panels should almost always be left at their native resolution. Why are we trying to adjust the pixels?
pdykstra said:
I'm a little confused here. LCD panels should almost always be left at their native resolution. Why are we trying to adjust the pixels?
Click to expand...
Click to collapse
This isn't adjusting the screen resolution, it's changing the reported DPI so apps draw their stuff smaller to fit on the "lower resolution" screen. The actual display resolution never changes.
The reason the lower DPI settings cause an increase in perceived screen space is because all the apps (system or otherwise) believe the display to be of a lower density, so they draw smaller text/buttons/images/etc to fit on (what they think is) a smaller screen. The display is still being driven at its native 1280x720.
Hey guys, as we know, the very first batch of any device likely will have some flaws. Hopefully this won't happen to the nexus 10. Anyway, Im a very picky consumer so I have to ensure my device is perfect. So I will list some of the things we need to check when the item arrives. feel free to give tips etc..
1/ Check the screen to see there are any dead pixels/ discolored area/ uneven white screen/ yellow or pink spots
2/ Light bleed
3/ any scratch on the body
4/Buttons are all good.
5/ Speakers
All I can think of so far..
also would want to check if the cameras, radios, ports, battery and other such components work properly, along with checking along the seams of the tablet to make sure it is solidly put together.
Microscope... check EVERY pixel.
I also have a few questions. It has to deal with the snap on cover if anyone got those (if they are out). When you unfold the cover does the screen light up like the iPad does with its smart cover. And also can the cover be used as a stand or does it just fall over? And how bad is the lag on Chrome compared to anyone who has used Safari on an iPad. Thanks. I'm hoping to switch from my ipad to the nexus 10!
Add couple more
1. Check GPS
2. Pixel check can be done with https://play.google.com/store/apps/details?id=com.ossibussoftware.deadpixeltest&hl=en
Will Google even replaces screens with a couple dead pixels?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
duarian said:
Will Google even replaces screens with a couple dead pixels?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Well in my case they'd be replacing the screen whether they intended to or not. If I had to, I'd just order a new one, then send the old one back in its place and say I changed my mind. And that just if they didn't want to exchange a clearly defective product. Up to them, but either way I'm going to make it right for myself in the end :good:
With 2560x1600 x3 sub-pixels (=12.288.000 pixels) you will very likely not get a sample without a single defective sub-pixel. Doesn't really matter either, a stuck sub-pixel at 300 DPI resolution is so small that it will be hard to find even if you "know" where it is.
My tab 10.1 and GS3 first batch were flawless. I expect a pretty close to perfect initial batch here as well. This isn't Asus or HTC.
Tomatoes8 said:
My tab 10.1 and GS3 first batch were flawless. I expect a pretty close to perfect initial batch here as well. This isn't Asus or HTC.
Click to expand...
Click to collapse
Bam !
Good point !
Samsung has an excellent track record!
Nothing is for sure but every samsung product ive ever had has been perfect!
From my Note 2
It's not only about the company behind the product, it's also about math/probability.
Hint: Try counting the sub-pixels on the Galaxy 10.1 or S3 and compare to the N10.
Tomatoes8 said:
My tab 10.1 and GS3 first batch were flawless. I expect a pretty close to perfect initial batch here as well. This isn't Asus or HTC.
Click to expand...
Click to collapse
not really...I guess it's a matter of luck. I bought my S3 in june and after 3 replacements, I got the satisfying one.
One thing concerns me the most is the screen. It's true that it's hard to get a screen without any dead pixels considering the huge amount of pixels. well, I really hope this won't happen since if I ever find out just one single dead pixel, it would turn me off really bad even if I normally can't see it. But you know, it is there... haha
rookiegenius said:
not really...I guess it's a matter of luck. I bought my S3 in june and after 3 replacements, I got the satisfying one.
One thing concerns me the most is the screen. It's true that it's hard to get a screen without any dead pixels considering the huge amount of pixels. well, I really hope this won't happen since if I ever find out just one single dead pixel, it would turn me off really bad even if I normally can't see it. But you know, it is there... haha
Click to expand...
Click to collapse
I forgot to include the legendary GS2 as another first batch flawless device. It might be about luck sometimes but generally you can deduce when it is safe to buy a first batch.
I use two methods that I feel pretty good about.
One, like I said, my GS2, tab 10.1, and GS3 were all flawless first batches for me. I realize that using just myself as a sample size is pretty shady statistically but if you look at the posts of complaints of the GS3 in May/June, they are far less than most devices.
Two, we know for a fact that Samsung is not only a manufacturer, but one of the if not the best manufacturer. Sure HTC and Apple are moving away from them, but it is not because of the quality. People trust their factories and manufacturing processes so unless the Nexus 10 uses some fancy new manufacturing process, Samsung already has the wisdom and experience and chances are, they won't need to make many changes to the manufacturing process like others might.
Valynor said:
It's not only about the company behind the product, it's also about math/probability.
Hint: Try counting the sub-pixels on the Galaxy 10.1 or S3 and compare to the N10.
Click to expand...
Click to collapse
I'm not so sure we should expect the majority of units to have dead pixels. I deal a lot with high resolution 2560x1600 computer monitors and very rarely do I encounter dead/stuck pixels. You're right that they would be harder to notice because of the high pixel density, but I'll use pixel checker and send it back if there's an issue. Just because it's a smaller screen doesn't mathematically necessitate pixel issues. The 13in retina macbook pro has almost the same pixel density and of the few I've tested, none have any pixel issues.
keenraven said:
I'm not so sure we should expect the majority of units to have dead pixels. I deal a lot with high resolution 2560x1600 computer monitors and very rarely do I encounter dead/stuck pixels. You're right that they would be harder to notice because of the high pixel density, but I'll use pixel checker and send it back if there's an issue. Just because it's a smaller screen doesn't mathematically necessitate pixel issues. The 13in retina macbook pro has almost the same pixel density and of the few I've tested, none have any pixel issues.
Click to expand...
Click to collapse
Are you really spending maybe 15-30 minutes (if that's enough) to check each display in a dark room with dark-adapted eyes?
I'm asking that because as an example my Nexus 7 has 1 stuck blue sub-pixel almost smack in the middle of the screen, I know where it is and I still need about 10-20 seconds in a dark room with a (mostly) black screen to find it again - in daylight it's just plainly impossible to locate it. On a Retina/N10/WQXGA display this will be even harder.
It's my personal opinion that a lot of the people posting here how their displays are perfect with zero errors just never see any of their stuck/dark sub-pixels. They're really that hard to find unless you have bad luck and get a completely broken pixel or a cluster of broken sub-pixels in close proximity.
Valynor said:
Are you really spending maybe 15-30 minutes (if that's enough) to check each display in a dark room with dark-adapted eyes?
I'm asking that because as an example my Nexus 7 has 1 stuck blue sub-pixel almost smack in the middle of the screen, I know where it is and I still need about 10-20 seconds in a dark room with a (mostly) black screen to find it again - in daylight it's just plainly impossible to locate it. On a Retina/N10/WQXGA display this will be even harder.
It's my personal opinion that a lot of the people posting here how their displays are perfect with zero errors just never see any of their stuck/dark sub-pixels. They're really that hard to find unless you have bad luck and get a completely broken pixel or a cluster of broken sub-pixels in close proximity.
Click to expand...
Click to collapse
first thing I do is go to my closet and turn the brightness all the way up... lol I can not live with dead pixels..
rookiegenius said:
first thing I do is go to my closet and turn the brightness all the way up... lol I can not live with dead pixels..
Click to expand...
Click to collapse
Whatever brings more happiness into your live ...
My personal view on sub-pixel errors is: if I have to search for them to see them ... I don't really care about them.
A full stuck/dark pixel (or anything that catches the eye) is a reason to send the device back though, no doubt about that.
rookiegenius said:
first thing I do is go to my closet and turn the brightness all the way up... lol I can not live with dead pixels..
Click to expand...
Click to collapse
I thought I was a bit wierd doing this to test for Light Bleed! lol I feel slightly better now!
rookiegenius said:
first thing I do is go to my closet and turn the brightness all the way up... lol I can not live with dead pixels..
Click to expand...
Click to collapse
I tend to do that anyway for light bleed... That's my worry. My Nexus 7 has pretty bad light bleed, and i'm okay with that because it's a cheap tablet, but I won't be happy if the Nexus 10 has bleed like that one. I can deal with a minor amount around the edges, but it's really annoying if it extends to the center of the screen, etc.
Valynor said:
With 2560x1600 x3 sub-pixels (=12.288.000 pixels) you will very likely not get a sample without a single defective sub-pixel. Doesn't really matter either, a stuck sub-pixel at 300 DPI resolution is so small that it will be hard to find even if you "know" where it is.
Click to expand...
Click to collapse
Not really true. My monitor is 2560x1440 and I promise you, there are no dead pixels. Granted it's 27", and the Nexus is only 10", it may be a little harder to see, but throw up solid color backgrounds and you will probably see it.
Hello all,
I'm relatively new to android, but I've been playing with RemixOS trying to see if it would be a suitable replacement for Android x86 on various devices.
Right now, I'm using RemixOS on a 55" 4k touch display, running at 3840x2160 resolution, with a dpi setting of 160 (to make the OS readable/touchable reliably).
Here's the issue: in the middle of the screen, touch is spot-on accurate, but the closer I get to the horizontal edges, it skews a bit, until it is about a full inch off near the absolute edge. Changing the screen resolution and dpi settings seems to have no effect on touch. It seems as though the OS thinks that the touch area is a couple of inches larger than it actually is.
Does anyone know a fix for this particular issue?
Thanks!
been bashing my head against this problem all day, and I've made a few steps in the right direction: namely, I see what the issue is, but I have no idea how to go about fixing it. When I do a dumpsys display, I see that the resolution that the system is reporting for the monitor is 4096x2160, but that's not what it actually is - it's 3840x2160. This explains the offset touch around the horizontal edges of the screen, but I have no idea how to force the resolution for both the video and touch down to the right resolution. I've tried wm, which does work to correct the video, but has no effect on touch, and i've tried setting the resolution as a boot parameter, which does basically the same as wm.
I hope that makes sense, my brain is mush after today.
halp.
Hi there.
My cousin dropped his phone and completely shattered the front glass. Phone still worked fine though. Went shopping for a replacement LCD+Touch glass part and finally found a shop which charged him about 60 bucks (this included service).
The display is not terrible, but it's definitely a no-brand spare, it's darker, has a blue-ish tint to it and on top of that, it seems to run on a lower resolution. It works fine for looking at memes on social media and stuff, but text and icons look jagged. The system effectively believes it's running untouched at 1080x1920 (checked via "wm size"), but the display itself is pushing less pixels than that.
He can live with that, though, so here comes my question point for discussion: Is there any practical way to measure the actual, physical resolution of this display?
I just thought it would be nice for Android to render everything at this display's native resolution. Jagged edges wont be gone, but I'm pretty sure using appropiate graphics assets and proper density is better than whatever downscaling is happening here.
Regards.
Get a magnifying glass and count the number of physical pixels.
All jokes aside, if you're rooted you can first try figure out what panel you have with "dmesg | grep panel" in terminal.
Other than that you should go back to the store your cousin got the screen repaired and demand an explanation from them and a refund.
Attached is the output I get on my own Z2 which has a OEM display. I didn't need root for this hehe. Lets see what it looks like on his phone next time I meet with him.
I really think requesting a refund is out of the question, it's been a few weeks since the repair took place and service technicians are a PITA to deal with 'round here.
Anyhow, what I'm worried about the most is software updates on the repaired Z2. Chinese knock-off parts are known to stop working or straight out break when treated with non-factory default firmware. It's sitting on 5.1 as we speak.
Update: The replacement display works after an upgrade to M build .291, the phone is now rooted and equiped with TWRP. I'll try to run
Code:
wm size 540x960
and
Code:
wm density 240
on it and see what happens. It could very well be a half-resolution panel, or a FWVGA one, we'll see.
UPDATE #2: The display looks worse after the fact. There's no saving it haha.
you buy a stock dislay from Sony or others?
Are they jagged or actually interlacing? I got a replacement that looked jagged but then I noticed they were actually interlacing which kind of looks like every other pixel is tearing slightly.
That gave it a jagged look. So it may be the right resolution, but just a faulty LCD. I was sent a new screen on request (ebay).
Either way you should get a replacement.
i got some low res display cheap from china. it was horrific resolution.. device also crashed ala bluescreen-of-death, especially when plying blossom blast or watching fb video. i ordered a display from eu on ebay, and now i'm happy again. and so is the device.
Same here and how to make things better
Flash kcal flashable mod and then use these settings R=255
Green=250 blue=245
Saturation =65
Value=135
Contrast =135
Ok turns out he broke the display again. This second replacement actually looks great, there's little difference when compared side-by-side with my Z2. Good thing he's no longer doomed to a bad display haha.
xRevengerZee said:
Flash kcal flashable mod and then use these settings R=255
Green=250 blue=245
Saturation =65
Value=135
Contrast =135
Click to expand...
Click to collapse
Not sure how this is supposed to help with resolution. Perhaps it would help with the blue tint, but the stock white balance does this as well.
Da Iceman said:
Are they jagged or actually interlacing? I got a replacement that looked jagged but then I noticed they were actually interlacing which kind of looks like every other pixel is tearing slightly.
That gave it a jagged look. So it may be the right resolution, but just a faulty LCD. I was sent a new screen on request (ebay).
Either way you should get a replacement.
Click to expand...
Click to collapse
Now that you mention it, that could explain the scanlines effect when looked up close.
rbrandser said:
i got some low res display cheap from china. it was horrific resolution.. device also crashed ala bluescreen-of-death, especially when plying blossom blast or watching fb video. i ordered a display from eu on ebay, and now i'm happy again. and so is the device.
Click to expand...
Click to collapse
Glad to know that. Who is this "eu"? Europe? Lol I'm out of touch here. Glad to know you got a fine display.
I REALLY hope to never ever need to go through display replacement lottery.
Compared to other devices, this Xperia is not hard to repair, and there are cheap spare parts, and quality parts available from a number of EUropean sellers.
Anyway, it's Friday, good to see this forum again, it's really a nice place.
Oh yeah, my daughter after terrorizing me for years finally made me buy her an iPhone, well... I'm waiting for replacement display nr5 for this 5s in a year now. Lol.
Pixelado said:
Hi there.
My cousin dropped his phone and completely shattered the front glass. Phone still worked fine though. Went shopping for a replacement LCD+Touch glass part and finally found a shop which charged him about 60 bucks (this included service).
The display is not terrible, but it's definitely a no-brand spare, it's darker, has a blue-ish tint to it and on top of that, it seems to run on a lower resolution. It works fine for looking at memes on social media and stuff, but text and icons look jagged. The system effectively believes it's running untouched at 1080x1920 (checked via "wm size"), but the display itself is pushing less pixels than that.
He can live with that, though, so here comes my question point for discussion: Is there any practical way to measure the actual, physical resolution of this display?
I just thought it would be nice for Android to render everything at this display's native resolution. Jagged edges wont be gone, but I'm pretty sure using appropiate graphics assets and proper density is better than whatever downscaling is happening here.
Regards.
Click to expand...
Click to collapse
Can you send me a link for the original replacement display?
napyaninja said:
Can you send me a link for the original replacement display?
Click to expand...
Click to collapse
Sorry, he bought his display from a brick and mortar store, I have no idea where they get their parts from