Hello,
bought my new Galaxy Note II recently.
Apart from the loosse USB-Connector problem, it has also problems with the light sensor.
Well, at this point I don't know if it's an general Software/Hardware Problem of the Note II or just my Phone which is faulty.
So, could you please read out your light sensor data with AndroSensor or similar tools and tell me the behavior in dark areas and in full lighted areas?
My problem is that the value spazzes out between 0 and 23 or 0, 40 and 35000 sometimes.
Rgrds
Sub
Related
Hey Guys,
got my new Note II yesterday, but already having 2 problems.
The biggest is the light sensor; the Screen keeps adjusting it's Brightness like hell.
Read out the Sensor data, which is going from 0 to 13 lux when I cover the Sensor with my hand.
Do you experience the same?
Also my USB wire plug is very loose. Also normal?
try turning off auto brightness...
and yes USB wire IS a bit loose
Jamal Ahmed said:
try turning off auto brightness...
and yes USB wire IS a bit loose
Click to expand...
Click to collapse
Well, just bought it brand new, I think this shouldn't be on a 600€ device
Does your Light Sensor Value also jump around in same light conditions?
Low-Light mine goes from 0-28, normal it goes from 400~ to 80.000 sometimes, which results in frequent readjustment in brightness.
Thats very irritating for me, cause I use it everytime
Would be nice if someone could give me his values/behavior of the sensor with AndroSensor or so.
Will return this device then
substancer said:
Well, just bought it brand new, I think this shouldn't be on a 600€ device
Does your Light Sensor Value also jump around in same light conditions?
Low-Light mine goes from 0-28, normal it goes from 400~ to 80.000 sometimes, which results in frequent readjustment in brightness.
Thats very irritating for me, cause I use it everytime
Would be nice if someone could give me his values/behavior of the sensor with AndroSensor or so.
Will return this device then
Click to expand...
Click to collapse
I just got my GT-N7100 and am having the same problems. Very irritating. Need this to work for better battery life. Tried a program from Play Store called Lux, but it works the same, maybe a little better. But Lux is showing the sensor readings varying all the time even when the ambient light hasn't changed at all, thus the brightness fluctuations. I am rooted, but on Stock ROM. Wonder if a custom ROM would fix it, or if it's a defective sensor.
Anyone else experiencing this?
580guy said:
I just got my GT-N7100 and am having the same problems. Very irritating. Need this to work for better battery life. Tried a program from Play Store called Lux, but it works the same, maybe a little better. But Lux is showing the sensor readings varying all the time even when the ambient light hasn't changed at all, thus the brightness fluctuations. I am rooted, but on Stock ROM. Wonder if a custom ROM would fix it, or if it's a defective sensor.
Anyone else experiencing this?
Click to expand...
Click to collapse
The default auto-brightness should not be updating so fast that it flickers You might want to get it checked out. Or if you use a 3rd party app, reduce the time interval of the update.
And do note, there is a difference say, with your back towards the sun, you face the phone towards you, or towards the floor. So when you are on the move, expect values to change.
Stock auto brightness is woeful in my opinion. It was the same one my Gnex so I have used Luxbon both with good results. Takes a bit of tweaking but brilliant when set up.
Sent from my GT-N7100 using Tapatalk 2
I'm not an expert at light sensors, but look at this:
http://www.youtube.com/watch?v=P9Os3HyCR5Q
I'm moving phone, holding camera still.
It looks like light sensor problem on galaxy note 2.
Can you check yours GN2?
Use code *#0*# and enter sensor test.
promi said:
I'm not an expert at light sensors, but look at this:
http://www.youtube.com/watch?v=P9Os3HyCR5Q
I'm moving phone, holding camera still.
It looks like light sensor problem on galaxy note 2.
Can you check yours GN2?
Use code *#0*# and enter sensor test.
Click to expand...
Click to collapse
I'm not in the brightest room but I have 2 60W light bulbs above me and my sensor has 0 when the phone is towards me and 20 lux when it is towards the roof. And yes it's stable with the values.
It would be great if somebody can test it, thanks in advance.
How to test:
put a camera in front of the screen and play around with the shutter speed and the brightiness of the screen. When lines appears on the screen, its not good => pwm, without lines => good :good:
edit: i had links for pwm explanation, but not enough posts, sorry..
The question is about pulse width modulation, which I'm reading occurs when both of the following are true:
- you are using an LED light source with variable brightness
- you are using a camera with a rolling shutter
http://provideocoalition.com/aadams/story/pulse_width_modulation_is_not_your_friend/
The camera on the note 8 does not have an LED flash, so I think the poster either now knows that it won't be an issue, or is curious as to whether display brightness on the screen is controlled by pulse width modulation or a different technique.
In the latter case, I don't know, and since this is stuff that can't be seen by the eye nor in the viewfinder, but mostly in photo editing suites per the article I link to, I'm not sure why it's an issue here.
Hi roustabout
I think we dont speak about the same topic.
What I mean is the flickering of the display. A good example is found on youtube: Nexus 7: no PWM on LCD
A lot of LCD use this technology to dim, but its not proper dimming, just switch on / switch off the the lcd very quickly.
Some people have problem with this flickering but dont know that theres a problem, so for example dry eyes, getting tired very fast when working on the computer..
I think more the 95% of the usual monitors use this technique.
I hope this helps.
no, we're talking about the same thing:
'curious as to whether display brightness on the screen is controlled by pulse width modulation or a different technique.'
The article I found thinks it's not visible; what you've read or experienced suggests it's problematic.
What I can say is the first-gen ipad was very hard on my eyes; the note 8 is not like that, but not as good as e-ink. Much more fun than e-ink, though!
I'm now on my 5th Samsung Galaxy Note 2 replacement from T-Mobile...
The reason for the replacements is; on every one I've had the earphone jack goes out within 6 weeks of every day use. And it's always the right channel that goes out.
But that's beside the point...
On the back of every replacement I get (under the battery) is the white sticker with bar code, IMEI ect. as well as "STA 13.0X" where "X" is a number that has been increasing from 2 to 8 on my latest replacement. (i.e. STA 13.02, STA 13.04, STA 13.08 etc.)
Are these different hardware revisions or something...?
Another thing I've noticed with these phones (starting from a Verizon Note II I had for a few days before returning it and switching to T-Mobile) is that some light sensors work WAY better than others. On the Verizon model it worked perfectly, scaling the screen brightness appropriately depending on ambient lighting. On my first T-Mobile version it was horrible in indoor lighting conditions. It would be too dim in anything but very bright ambient lighting. I don't think it was a software/kernel issue either because I downloaded an app that monitors the sensor and tells you what level of light it was sensing and on the T-Mobile version the sensor would jump all over the place and appeared to be obviously malfunctioning.
Since the 1st T-Mobile replacement about 50% of the phones I've received have had sensor issues and the other 50% have been fine...
My questions are these:
Has anyone experienced similar issues with either their sensor or headphone jack?
Does anyone have any insight into what the STA number signifies?
If this number signifies hardware revisions does anyone have any insight as to what is changing from revision to revision?
Thanks!
There are different revisions and locations of manufacture. For instance my phone is noticeable thinner and lighter then my wife's. I've noticed hers seems to function smoother, buttons have a firmer ckick and yes her sensors seen to work better.
Mine is a newer build then hers which leads me to believe that Samsung went with a cheaper manufacturer for their new supplier.
I noticed this on my Verizon as well before I switched to tmobile
Sent from my SGH-T889 using xda app-developers app
Hi Folks.
I searched the forum for related issues but only found one other user who never got a response. I recently took it upon myself to replace the usb/charging board and mic on my stock sph-l900 note II running 4.4.2. Prior to the repair the display was perfect. Anyhow i replaced the board and when I powered up the phone the display seems to have lost the ability to display black. The Note II launch screen looks brown, so brown i would call it woodgrain. I double checked all connections and messed with every every display setting, none of which solved the problem. The touchscreen still works, the phone runs everything beuatifully, but the display gamma is too high by at least .6 everywhere on the screen.
Is this a matter of dust between the digitizer and screen? IS this even a problem anyone is remotely aware of? I have a cheap replacement glass but that was not an endeavor I wanted to attempt. Any ideas what to attempt short of replacing the screen? Any ideas at all?
Ok, here is the problem I am facing.
I recently changed the display to my G6 Play, and everything works fine except proximity sensor. When I try to make calls my screen goes black. I set up the power button to terminate the call but that's a very simple workaround. I can live with that but its very annoying. I checked the rubber shaped like an 8 figure around the light sensor and proximity, it seems properly aligned but I don't have enough experience to say that I am 100% sure. I have no case or screen guard on my phone also. I have tried with all kind of third apps to disable the proximity sensor. No joy. I know for sure since I have used an app for sensor testing that the proximity sensor is draining voltage aprox 0,32 mA so I think it is working. But the value is 0 so it is in a covered state. Now I am thinking since my phone dropped on the floor and cracked almost near the sensor where the impact zone was, that the sensor may be damaged. The current can flow but the hardware inside may be affected due to shock.
So again I guess it would be an elegant solution just to disable it with software. Is is possible and how?
Same problem here
Hello, I have the same problem... Did you managed yo disable the sensor?
Thanks you