Just noticed today, in darkness the proximity sensor is visible as a faint, but distinct, red light on the phone when its active. Anyone else noticed this? Maybe mine has a faulty sensor.
If you activate the sensor, by making a call in darkness (or opening a text message, if you have direct call on) and looking above the sensor, do others have this visible light?
I've seen other people mention other models using near-IR as opposed to actual IR for the sensor, but I haven't seen anyone mention it for the S3 (which is surprising considering how popular it already is) which makes me think it could be just mine.
I am pretty sure it's not a fault, mine does it too.
Sent from my GT-I9300 using XDA
Proximity sensor uses infrared which is the same light your tv remote uses.
You can't see infrared but due to technical reasons there are always a few light particles emitted / reflected as visible dark-red light.
It's the same as with ultraviolet (darklight); you can't see UV but it still glows faintly dark-purplish.
Cool thanks. I thought so. Very relieved all the same.
It was more worrying when it seemed to be there all the time when the screen was on (I had a message open at the time!)... It didn't even occur to me it might be the proximity sensor, since I forgot about direct call which was obviously activating it.
Anyone know if there some advantage to visible ones? I've seen ones before that aren't. Are visible ones more sensitive? Or cheaper?
d4fseeker said:
Proximity sensor uses infrared which is the same light your tv remote uses.
You can't see infrared but due to technical reasons there are always a few light particles emitted / reflected as visible dark-red light.
It's the same as with ultraviolet (darklight); you can't see UV but it still glows faintly dark-purplish.
Click to expand...
Click to collapse
I know remotes etc. emit very small amounts of visible light (I remember my fascination at 12 when I found this out ). But this is a lot stronger than I've ever seen on a remote. Were it as weak as a remote, I probably wouldn't have even noticed.
Hmm, usually non-visible IR should be less expensive since the wavelength is longer, however due to manufacturing it could still be slightly visible.
Near-IR could be more accurate since under direct sunlight you'll have tons of IR-light so the sensor could mistake it for your ear reflecting the light in certain conditions. Slight changes in the specutrum might prevent this from happening.
Does it really bother you? Because the proximity sensor is only on when you're on the phone in which case I usually keep it on my ear or in my pocket =)
[Edit]
Also, IR remotes should be quite a bit less light-intensive. They only need to pulse a light which the receiver captures while this one needs to illuminate your ear so the receptor can decide how far it is.
Compare it to holding a tealight candle to show others that you're there vs using a torchlight to illuminate the path for thm.
My proximity sensor is lit up all the time. Even when the screen is off. I only just noticed it now and did a search on Google. Does it sounds like it might be faulty? It wouldn't have any need to keep it on all the time and it would drain a small amount of power right?
Jaisah said:
My proximity sensor is lit up all the time. Even when the screen is off. I only just noticed it now and did a search on Google. Does it sounds like it might be faulty? It wouldn't have any need to keep it on all the time and it would drain a small amount of power right?
Click to expand...
Click to collapse
Do you have have the latest version of Viber installed? If so try uninstalling it
Sent from my GT-I9300 using xda premium
do you have viber? if yes, then that's the one causing it.. the latest update has this bug..
Sent from my GT-I9300 using xda premium
Oh, you're right. I force stopped Viber and the light went away straight away. Soooo, I kinda wanna keep Viber, will it damage the proximity sensor if it stays lit? Will it effect my battery life significantly?
i dont know if it will cause damage.. but it will cause battery drain.. but not that much.. if you charge your phone at least once a day, then you should be fine.. and besides, a lot of people have already reported it to the devs, so im sure they will fix it in no time..
Sent from my GT-I9300 using xda premium
Related
Do you like the light Sensor on Nexus?
I didn't like it.
It's a very good feature, but it works strange.
It is slow in dimming and took already not enough light to the display.
Nexusdisplay is dark dark dark...
Does anybody know, how to tweak this sensor?
Or am I the only one who dislike it very much?
I just set my brightness manually. Done deal.
Perfect.
In the Night I'll put my sunglasses on or at a sunny day I take my nexus blind...
Wherefor is the sensor if it don't work proper?
There must be some settings for...
I think the light sensor works great but it would be even better if we can customize it a little bit. Something like scale up the screen brightness for each level of external light.
Or something like auto lock when it is totally dark (you put it into your pocket?).....but that would cause trouble if you want to use your phone in the theater
I think the light sensor is terrible. I have tried everything but it still seems very finicky on when it will work properly. I regularly go from low light to sunny outdoors and having the feature would properly would be awesome, especially since it worked fine on my last 2 phones and they arent even close to being a superphone.
Trying to make it transition smoother is something I've been meaning to try. The settings for this are in the source tree at frameworks/base/core/res/res/values/config.xml (I override this in my passion vendor overlay). You can tweak the values and rebuild framework-res to try it out.
oh cyanogen, You Are GOD!
Where we can find it?
I've searched the whole framework.
ha he meant the source tree for framework provided by google. not in the framework-res inside of the zip of the rom you are using.
two things I noticed about it:
1 It dims and brightens too quick, it should take an average light level over a longer time period
2 Our fluorescent lights in the office at work seem to confuse it, so that could mean that the lens is too focussed and if you hit one of the lights it goes too bright, miss and it goes too dim as you move around and/or the wavelength of the lights confuse it - though this problem may be more bearable if #1 above is fixed.
I gave up using the sensor. I use the power strip. the 3 settings work great for me.
Ssantos6981 said:
I gave up using the sensor. I use the power strip. the 3 settings work great for me.
Click to expand...
Click to collapse
Yea I mean why should it work? We only paid $530 for it ;/
spyz88 said:
Yea I mean why should it work? We only paid $530 for it ;/
Click to expand...
Click to collapse
Yes, these words are soooo true! They're absolut true.
And: It's not HTCs first device with such a sensor. It's not the first android Handset with such an sensor.
I can't understand, why they did such a thing!
@spyz88: I'll pray your words every time if i see this dumb dimming and flickering.
I too have noticed this problem, and have such, turned it off. Disappointing, yeah.
I hope someone can come up with some good idea/settings, to fix this like google should be doing already :/....
Thanks people
spyz88 said:
Yea I mean why should it work? We only paid $530 for it ;/
Click to expand...
Click to collapse
You can pay £30,000 for a car and things still don't work properly.
Nature of the beast I'm afraid.
OK, we can put our heads down in the sand or we can try to make us happier with it.
Does anybody tells google/htc that this is crap?
Probably we can make it on our own.
yeah it doesn't work very well. Maybe sensitivity needs to be lowered somehow
I hate to say this because I always talk crap about the iphone, but the iphone does have a better way to auto dim the screen with the sensor.
I thought I had a problem because from the get go I installed a screen protector that lays over the sensor, but now I see that other people have the same issue.
It is funny because I can have the phone in one place, but if I change the angle the screen will dim or brighten.
the worst thing is , it comes in the way of reading constantly on your phone , and after two to three cycles of dim/bright , you would eventually give up and disable it. disappointing .
but i think the problem is it samples ambient light with long interval , and then average it in a way that is always behind what it should be
This has bothered me as well and I've been looking for an easy way to fix it.
It seems that the light sensor (or its driver?) is to sensitive or inaccurate. The reported LUX value can fluctuate a lot in constant surrounding light. There is also the possibility that one waves a hand in front of the sensor which can produce undesired brightness changes etc.
My idea:
PowerManagerService.java (frameworks/base/services/java/com/android/server) listens for light sensor changes with a SensorEventListener. Either directly or after (config_lightSensorWarmupTime) a method called lightSensorChangedLocked is called with the sensor value as parameter. This method sets the brightness.
Here we can add some low pass filtering to the sensor value before calling lightSensorChangedLocked. Maybe a simple average of the last 5 values or so will suffice? Maybe take time into consideration as well. Say average 5 or all values received in the last 20 seconds or so. There sure are room for improvements of my suggestions.
My message is that the issue is perfectly fixable and PowerManagerService.java is the file to fix it in.
Hello,it seems there is no Q&A forum for this device, so here is my doubt:
Although the tech manual for the xperia S from the sony website report a proximity sensor, I fail to find one on my phone.
There seems to be a black oval spot on the glass next to the light sensor as if some sort of sticker can be removed to install the sensor.
The light sensor seems to work, since I've seen the screen go darker and brighter, but when I'm in a call and put the phone in my ear the screen wont shut off like in my old SGS nor will it turn on when I move the phone away from my face.
are your phones like mine? or is mine a defective unit?
I guess ur device has something wrong with it.
By the way; did u place a screen protector?? Coz if u did that may be the problem!
I think the light and proximity sensor are the same.
There is something wrong with your phone,maybe you should try to flash a new firmware.
Sent from my LT26i using Tapatalk 2
grained said:
Hello,it seems there is no Q&A forum for this device, so here is my doubt:
Although the tech manual for the xperia S from the sony website report a proximity sensor, I fail to find one on my phone.
There seems to be a black oval spot on the glass next to the light sensor as if some sort of sticker can be removed to install the sensor.
The light sensor seems to work, since I've seen the screen go darker and brighter, but when I'm in a call and put the phone in my ear the screen wont shut off like in my old SGS nor will it turn on when I move the phone away from my face.
are your phones like mine? or is mine a defective unit?
Click to expand...
Click to collapse
Hi,
Mine works fine...
Do this:
1>Go to dialpad and type *#*#7378423#*#* (*#*#SERVICE#*#*)
2>A menu pops up in that u will see service tests select that
3>Then scroll down and select Proximity Switch
4>Initially it will display as OFF. Now u place your finger or hand on the Proximity Sensor, then the value of Proximity Switch on the screen will change to ON.
If this is working then the sensor is just fine u need to update the firmware else u need to go and replace the piece IMO though.
Thank you all for the feedback.
I used the service menu to check the sensors ...
indeed the proximity sensor is always off, even when I put my finger on it, it seems someone forgot to remove the black paint from behind the glass, but I will update it anyway to make sure before returning it.
grained said:
Thank you all for the feedback.
I used the service menu to check the sensors ...
indeed the proximity sensor is always off, even when I put my finger on it, it seems someone forgot to remove the black paint from behind the glass, but I will update it anyway to make sure before returning it.
Click to expand...
Click to collapse
sensor is IR, so darkened window is normal for it. but if it have always closed windows - than its status must be always ON. so, most likely you have faulty sensor (or bug in firmware)
goodwin_c said:
sensor is IR, so darkened window is normal for it. but if it have always closed windows - than its status must be always ON. so, most likely you have faulty sensor (or bug in firmware)
Click to expand...
Click to collapse
Hi,
Exactly it should be showing status as ON if it's covered replace the piece as soon as possible
shoz_on4u said:
Hi,
Exactly it should be showing status as ON if it's covered replace the piece as soon as possible
Click to expand...
Click to collapse
If it was covered by the glass/ cover it would show OFF because the glass doesn't radiate heat like your body does.
Sent from the Delta Quadrant using a transwarp conduit.
Pezo said:
If it was covered by the glass/ cover it would show OFF because the glass doesn't radiate heat like your body does.
Sent from the Delta Quadrant using a transwarp conduit.
Click to expand...
Click to collapse
Proximity sensor on phones does not react to heat. It have simple IR transmitter, which emits a beam, and IR sensor, which react on reflected beam.
goodwin_c said:
Proximity sensor on phones does not react to heat. It have simple IR transmitter, which emits a beam, and IR sensor, which react on reflected beam.
Click to expand...
Click to collapse
You are right, just tested it and it seems to be a reflective sensor.
thanks for the tips, it was indeed a faulty sensor and they gave me a new phone right away .
I hope I don't get any more problems like a yellow tint :X (knock on wood with fingers crossed)
I woke up to find this red light on the top left of my screen looking at me. If that light wasn't on i would have not never seen it.
Looking under a bright light there appears to be an LED there. It's use I have no clue. It's not in the users guide. Maybe its there to tell if DHS is monitoring you.
Sent from my EVO using Tapatalk 2
My thoughts exactly
Is that right next to the proximity sensor or is that the proximity sensor?
Sent from my EVO using xda premium
Nope the proximity sensor is right next to it. Could it be a roaming led?
Sent from my EVO using Tapatalk 2
Hmmm. It's not a roaming led cause I'm roaming right now and it's not on. Weird.
Sent from my EVO using xda premium
drummerb said:
I woke up to find this red light on the top left of my screen looking at me. If that light wasn't on i would have not never seen it.
Click to expand...
Click to collapse
Government's electronic spies. They are to monitor your activities. This phone was kept in customs remember?
It's part of the proximity sensor, the led is an ir diode. The led beams ir light toward your head and the sensor picks up the reflectance of the signal bouncing back off. See the attached diagram.
Sent from my EVO using Tapatalk 2
UltimatePG said:
It's part of the proximity sensor, the led is an ir diode. The led beams ir light toward your head and the sensor picks up the reflectance of the signal bouncing back off. See the attached diagram.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
So its some sort of cover for mind control? Or to prevent the apple signals to penetrate our head
Sent from my EVO using Tapatalk 2
UltimatePG said:
It's part of the proximity sensor, the led is an ir diode. The led beams ir light toward your head and the sensor picks up the reflectance of the signal bouncing back off. See the attached diagram.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
IR LED's should not emit visible light. Just saying. The Op's is looks illuminated in the photo. But yes it is the emitter for the proximity sensor. Could be a dual LED package. Would have to see if there is a parts list available, then look up the part to see.
kf2m said:
IR LED's should not emit visible light. Just saying. The Op's is looks illuminated in the photo. But yes it is the emitter for the proximity sensor. Could be a dual LED package. Would have to see if there is a parts list available, then look up the part to see.
Click to expand...
Click to collapse
He's illuminating the diode casing externally with visible light.
Edit: Also, CCD sensors in cameras are able to pick up IR signal as well. Record a video of any irLED on a remote control while pushing the buttons, you'll see it light up on camera.
I noticed the same light on my phone when the front cam is activated for the Face Unlock, it could be an IR emitter to help the front cam in low-light scenarios...
But it was totally dark in the room.
I'll resurrect this. I just woke up this morning and saw this same VERY DIM red light in that spot. It's visible light, not catching light from something else. I'm running down my first charge. It was dead when I bought it (had to put it on charger for 5 minutes just to get it to power on to activate at the store) and then I charged it to 100% overnight, took it off yesterday and left it all day and all night, I'm now at 13%. I figured it would be a power notification, but it's certainly not useful for notifying of anything at this brightness.
When I try to take a pic of it it shows up very brightly illuminated just like in the OP's photo, FWIW. I'm not convinced that it isn't some sort of notification light that just isn't active yet (I never saw the cyan/amber light on my OG Evo until I installed Deck's AOSP over a year into the contract and it started lighting up for notifications). Curious as to what this one is for.
SilverZero said:
I'll resurrect this. I just woke up this morning and saw this same VERY DIM red light in that spot. It's visible light, not catching light from something else. I'm running down my first charge. It was dead when I bought it (had to put it on charger for 5 minutes just to get it to power on to activate at the store) and then I charged it to 100% overnight, took it off yesterday and left it all day and all night, I'm now at 13%. I figured it would be a power notification, but it's certainly not useful for notifying of anything at this brightness.
When I try to take a pic of it it shows up very brightly illuminated just like in the OP's photo, FWIW. I'm not convinced that it isn't some sort of notification light that just isn't active yet (I never saw the cyan/amber light on my OG Evo until I installed Deck's AOSP over a year into the contract and it started lighting up for notifications). Curious as to what this one is for.
Click to expand...
Click to collapse
To put this to rest, some irLED diodes have a spectra that tail off in the visible region (around 750-800nm) with a peak at around 850nm (for Gallium Arsenide LED's). The visible portion of the emitted light would appear red (650 nm to 750 nm) and will appear dim due to the low emission at this wavelength range.
And again, a powered irLED will appear very bright when taking a picture of it with a digital camera due to sensitivity of CCD's toward infrared light.
Attached is a spectrum of two types of irLEDs, one emitting at a peak of 850nm.
Just be careful that it doesn't start saying things like "I am putting myself to the fullest possible use, which is all I think that any conscious entity can ever hope to do"
Sent from my EVO using Tapatalk 2
UltimatePG said:
To put this to rest, some irLED diodes have a spectra that tail off in the visible region (around 750-800nm) with a peak at around 850nm (for Gallium Arsenide LED's). The visible portion of the emitted light would appear red (650 nm to 750 nm) and will appear dim due to the low emission at this wavelength range.
And again, a powered irLED will appear very bright when taking a picture of it with a digital camera due to sensitivity of CCD's toward infrared light.
Attached is a spectrum of two types of irLEDs, one emitting at a peak of 850nm.
Click to expand...
Click to collapse
See, now that makes sense.
SilverZero said:
See, now that makes sense.
Click to expand...
Click to collapse
+1
So drummer you hit things with sticks? Have a Roland TD-12 here.
There seems to be a number of people raising certain hardware issue problems. I don't know about you, however I don't seem to have any issues at all here.
Current Issues
Light Bleed
Back Cover Flex
Warped Back
No issues here!
Vote in the poll!
Would be nice to know which possible batch you got yours from.
Did you order it on launch day or have you ordered it since it's come back into stock?
Which country have you ordered it from?
Have you had to RMA ones before?
I have no issues at all. There is a minor amount of light bleed around the bottom edge (landscape with camera at top)but this is no issue as it only affects the nav bar, and is totally invisible when set to lowest brightness setting where I tend to use the tablet . I love this thing.
If I turn the brightness up full, I have the weeniest bit of light bleed on the bottom right corner but you have to look hard to see it.
Everything else is fine
Possible Touchscreen/Multi-Touch issue?
Still awaiting for others to leave some feedback Only takes about a minute or two to test
Some of these are not a hardware issue but a chassis issue. Hardware is the components inside the tablet.
I ordered on the 13th and no issues to report.
Murmur95 said:
Some of these are not a hardware issue but a chassis issue. Hardware is the components inside the tablet.
Click to expand...
Click to collapse
Minor technicality.
Minor light bleed, non factor. Extremely pleased with this tab!
Minor light bleed in lower right like everyone else, which I wouldn't have noticed if not for reading the forums!
My LED is not working, our art last I can't make it work. Doesn't really bother me as in my previous tablet (a BlackBerry playbook) I turned out off anyway.
Sent from my Nexus 10 using XDA Premium HD app
Nothing at all there could possibly be light bleed, but I have not dine a test, I am just using it and in terms if uses, there is nothing noticeable
Murmur95 said:
Some of these are not a hardware issue but a chassis issue. Hardware is the components inside the tablet.
Click to expand...
Click to collapse
So far as I'm concerned, hardware is anything physical, so to me the chassis falls under this. Hardware is physical components, software is well, software.
Part of the 2nd batch (restocked 11/20).
Only minor light bleed.
Alright I ordered another one due to some light bleed that is visible on almost all automatic brightness levels. I sure hope I don't get one that's worse. charging cable I got doesn't work either so that also pushed me to RMA it.
Sometimes when holding the Nexus 10 with one hand on either side, I frightening notice the side speakers slightly detach. I only noticed this three times before I promptly adjusted the way I hold it till I get a case with sufficient protection.
Sent from my Nexus 10 using XDA Premium HD app
Light bleed. And not a hardware issue but a lot of freezing....
Sent from my Nexus 10 using Tapatalk HD
I haven't seen anyone else mention this anywhere, but the backlight makes a really annoying high-pitched whine whenever it's turned on, and the pitch/tone changes with brightness. From what I've read it could be a choke coil squealing but I didn't think something like this would have them large enough to make noise.
ChrisK15 said:
I haven't seen anyone else mention this anywhere, but the backlight makes a really annoying high-pitched whine whenever it's turned on, and the pitch/tone changes with brightness. From what I've read it could be a choke coil squealing but I didn't think something like this would have them large enough to make noise.
Click to expand...
Click to collapse
I maxed out my brightness and I couldn't hear a thing, however I did notice that my plasma makes a high pitched whine.
Multi touch all good here when using the app that was posted; tried several different touches to be sure.
Light bleed in the bottom right, pretty minor though. Everything else is solid & working though.
As for the back strip flexing, The clips that keep it secured are tiny, so it doesn't surprise me that that is an issue for some... makes me wonder how things will go once the covers that swap out the back strip are released...
Sent from my Nexus 10 using xda premium
Light bleed, but the most annoying one is that the front and back camera both are not working. Doesnt anyone else have this problem?
Pasmaaaan said:
Light bleed, but the most annoying one is that the front and back camera both are not working. Doesnt anyone else have this problem?
Click to expand...
Click to collapse
I get this issue sometimes on my Galaxy Nexus when 3rd party camera apps or apps that use the light are in use. The camera on my n10 works okay at least.
I guess I got extremely lucky. Ordered the minute it first become available (Tuesday, delivered Friday) and zero issues.
No reboots, freezes, laggieness, light bleed, back flex, dust, etc..... nothing, everything has been great.
Not usually this lucky....so I am extremely pleased
I'm experiencing either a defect or an unfortunate feature on this tablet. I just took delivery of a new one, and while viewing any solid colors besides grey on the screen everything is fine (also no dead pixels), but I'm noticing what appears to be slight backlight flickering/pulsing whenever grey or light blue is shown on the screen. It seems to be PWM (pulse width modulation) of the leds, but I can't be certain it's a defect or just the unfortunate way these tablets' led screens are designed. It's a very subtle but consistent and annoying pulse, but it's definitely there. Can anyone confirm that PWM is what's going on with these tablets or if this is a defective screen. The screen doesn't pulse at all on any other colors solid or only partially filling the screen or otherwise.
I haven't noticed anything on mine, though I tend to keep the backlight fairly low (17%).
One thought though which is why I'm saying anything, I remember on the nexus 7 there was an issue with one of the friction pins not connecting to the back of the case's antenna fully sometimes, which would cause the radio/wifi to suck extra power resulting in backlight pulses... have you tried turning on airplane mode (disable the cellular) with wifi off to see if that makes a difference? Though it would be odd if it only affected the one colour... I suppose it could be your ambient light source too, does it do it in sunlight?
joeblowma said:
I haven't noticed anything on mine, though I tend to keep the backlight fairly low (17%).
One thought though which is why I'm saying anything, I remember on the nexus 7 there was an issue with one of the friction pins not connecting to the back of the case's antenna fully sometimes, which would cause the radio/wifi to suck extra power resulting in backlight pulses... have you tried turning on airplane mode (disable the cellular) with wifi off to see if that makes a difference? Though it would be odd if it only affected the one colour... I suppose it could be your ambient light source too, does it do it in sunlight?
Click to expand...
Click to collapse
Good idea! Unfortunately, killing the antennas doesn't affect it. And there's no ambient light sensor on the g pad x, so that's out as well I'm so disappointed because there are not dead pixels and only very little light bleed in the corners too.
I didn't mean ambient light sensor would be the cause, more that perhaps you have bulb/s that cycle at a specific rate at a certain colour range that would cause a subtle flicker, I always found those big long roof fixture fluorescent tube lights bad for this sort of thing... I notice some "out of the corner of my eye" subtle flickering on my PC LCD when I have the one CFL on, but not when I have the other LED lamp going instead for example. I just tried a LCD screen tester with various solid colours (cyan, blue) and the only 'flickering' I'm seeing is if I actually move the screen, this panel has some waviness in it that is visible when the screen is off and you angle it just right under a light which seems to pop out on these blues with the backlight turned up - but only when the screen is physically moving. Definitely not a perfect panel, but for me nothing like what you are talking about.
I'm outta ideas though, unless you are running a custom firmware and it does something different than what my stock does.
GL
edit:/ just read that RFD post from the other thread, and I definitely notice a flicker when in nova's app drawer. It seems to occur only right after I move the tablet and only noticeable at higher backlight settings, if I set it down flat and don't move it, it doesn't do it. Perhaps related to the gyro sensor? Something not isolated fully/properly would be my guess. With the wifi turned on, it also does it along with the activity up/down arrows on the logo... now that I've seen it I wonder if its going to bother me on lower brightness levels now :silly:
joeblowma said:
edit:/ just read that RFD post from the other thread, and I definitely notice a flicker when in nova's app drawer. It seems to occur only right after I move the tablet and only noticeable at higher backlight settings, if I set it down flat and don't move it, it doesn't do it. Perhaps related to the gyro sensor? Something not isolated fully/properly would be my guess. With the wifi turned on, it also does it along with the activity up/down arrows on the logo... now that I've seen it I wonder if its going to bother me on lower brightness levels now :silly:
Click to expand...
Click to collapse
Thanks for checking. I tried the airplane mode setting, and I swear that fixed it. But then it came back after a few more toggles of data/wifi. Given that you're seeing it too and that others have reported seeing it as well in the RFD thread, I'm thinking it isn't a defect but rather poor design. There's little chance it would be this widespread and only on the exact same color combo for everyone. I think most people just never notice it since you're rarely just looking at a solid or mostly solid grey screen. I wonder if there's a way to disable the gyro on a stock/non-rooted gpad like mine? For me, it does it regardless of brightness level.
I've seen this on different devices too, so it's not just a G Pad X thing. I wanna say I've seen it on my Nexus 5 back in the day, but I've had many devices so it's hard to remember. But yep, noticed it happens on "grey" colors. It's much less noticeable with the brightness lowered. Never really bothered me so never posted about it.
emilyrugburn said:
I've seen this on different devices too, so it's not just a G Pad X thing. I wanna say I've seen it on my Nexus 5 back in the day, but I've had many devices so it's hard to remember. But yep, noticed it happens on "grey" colors. It's much less noticeable with the brightness lowered. Never really bothered me so never posted about it.
Click to expand...
Click to collapse
My guess is it's the led pulse width modulation. It affects some screens more than others, but is an issue with led implementation on lcd screens in general. I'm leaning towards keeping the tablet as I'm 99% convinced that another unit would exhibit the exact same behavior. Glad to hear it isn't a defect, but sad that they did not manufacturer a better screen.
Jottle said:
My guess is it's the led pulse width modulation. It affects some screens more than others, but is an issue with led implementation on lcd screens in general. I'm leaning towards keeping the tablet as I'm 99% convinced that another unit would exhibit the exact same behavior. Glad to hear it isn't a defect, but sad that they did not manufacturer a better screen.
Click to expand...
Click to collapse
I don't want to clutter this thread any further, but I'm going into a B&M t-mo store to see if I can test this out on a display device to confirm how widespread this issue is.
Quick update on the flicker issue. It's a problem with all the units, or perhaps just poor design. I did a warranty exchange, and the replacement unit had the exact same issue. Oh well. Just time wasted I guess.
I have the same exact issue with the one i got my mom. Fortunately it doesn't bother her too much but it definitely seems to be a design flaw as we also returned it with the return unit having the same issue
Welcome to the world of flicker.
What you are seeing is very common and an unfortunate side effect of cheap reference designs and a don't care attitude.
There are many new standards for flicker but I doubt they'll be implemented. Flicker pwm needs to be in the 10khz range to be indistinguishable to constant current drives.