Related
Phone -> Keypad -> *#0*# -> Sensor -> put your device on a flat/steady surface and tell me if the numbers of the magnetic sensor are always changing rapidly, the azimuth is sometimes changing in increments of 1 vice versa.
The accelerometer is showing x: 0, y: 0 z: -240 or sometimes -216 (as long as i don't move it).
How does your device behave?...
accelero 0, 0, -216
Magnetic keeps changing constantly indeed.
azimuth keeps changing between 15-17
same
accelerometer x:0,y:0,z:-216
magnetic 2, x: (-6.0 --> -6.4), y: (-15.6-->-16), z: (-154-->-156)
azimuth: (145-->146)
My results of the accelerometer x:0,y:0,z:-216
but, 'z' value (-216) indicates that the accelerometer isn't working right, is it? It should be all "0" when it is on a flat surface, or??
the accelerometer Z axis is 0 when the device is upright, not flat down.
-216 is perfectly fine, considering that the device's back is not flat at all.
try moving the device when in test mode, you'll see the values change.
And in this opprotunity, i have to say the sensors in the SGS are amazingly responsive, even when compared to other same category phones.
For a more fun way to test all the sensors, install the Tricorder app from the market and play with all the scanning options.
Hi, I bought a cheap clear rubber case from eBay . I notice after I put the case on , I am unable to control the screen when I'm charging. Remove the case and it works again ? Anyone has seen something like that before ? Is this due the capacitive screen ? The case wrap over the edges of the screen though. Thanks !
For sure the rubber case is touching the screen so your HD2 can't recognize both your touches and also the rubber case touches, other than that I can't think of anything else that might have happend!
does the skin cover up the proximity sensor in the upper left ( you should see 2 circles O O when you hold the phone at a slight angle just to the left of the earpeice grille
I dont know if this is an issue with other handsets.
I installed proximity screen off application . The purpose was to have the phone turn the screen off when i close my flip case.
However i found something strange.
When the flip case is very close to the screen the proximity sensor does not seem to detect that there is something covering it.
Is this an issue with every one ?
Any solution
Please see the videos
As you can see from the videos when i bring the shield very close the proximity sensor does not seem to detect the sheild.
Edit : However if u use ur finger this is not seen
I've noticed the same behavior, it's quite annoying because it kills one of NoLed's best features (screen off using prox. sensor).
[deleted]
Still really annoying that the original flip cover won't work with the proximity sensor. A workaround might be a third party flip case. A diy modification of to the original one won't work since if I close it AND hold whatever object that alone is enough for a positive result over the flip cover, the sensor will still not register positive [because a minimal distance between an object and the glass surface is required, see below].
mine works even with a finger...
I've done it a few times accidently when i was trying to access the notification bar while on the phone
ph00ny said:
mine works even with a finger...
I've done it a few times accidently when i was trying to access the notification bar while on the phone
Click to expand...
Click to collapse
Thats the thing i was saying.
With finger i works great even if u touching the screen
Dial *#0*# and press sensor. If it vibrates, the proximity sensor is registering an object.
Maybe it comes in handy with testing.
It's working for me, thanks for the tip about the app!
edit:
Okay, I tested and found that indeed when you set the app to:
"Cover an hold to lock the screen" to say 5 seconds.
Close the flipcover.
It does not register.
However. If I set:
"Disable Accidental Lock" to .25 seconds.
Close the flipcover.
It works quite well.
Coming back to the sensor. It indeed does not register the flipcover when it's closed and touching the screen.
Weird thing is it does not register your hand anymore either.
Recreating issue:
Remove flipcover and lay it completely flat over the sensor.
Dial *#0*#.
Press "Sensor".
No registration.
Now hover your hand over where the proximity sensor is, and... How about that, no registration.
This indeed messes up NoLed's battery saving feature.
This can also be a problem when:
You set screen timeout to 10 min.
In the app's settings set "Disable in landscape" to on.
Then use an app in landscape mode.
Close flipcover while in landscape mode.
Then rotate to portrait. At this point it should start registering again and turn off screen..
The sensor does not register and screen stays on.
Drains battery.
It is a really cool idea, but it does not function properly.
It's too flaky, also when just handling your phone. I find myself accidentally turning off the screen.
Maybe if you use a case or some other cover with a different or thicker material it would work better.
I ordered a Zenuscase, I'll give it a try with that one.
Don't know how long it'll take to arrive though
reflective color
heey i found the problem , the sensor is working fine ... but when so close with any black object the light is not reflected back to the proximity sensor.(black color absorbs light).
Repeat your video with any white object and you will notice the difference..
Now i am using Autostart and it works great with samsung original flip cover (white flipcover).
you can use any white sticker on the black one.
ahmedtaha7 said:
heey i found the problem , the sensor is working fine ... but when so close with any black object the light is not reflected back to the proximity sensor.(black color absorbs light).
Repeat your video with any white object and you will notice the difference..
Now i am using Autostart and it works great with samsung original flip cover (white flipcover).
you can use any white sticker on the black one.
Click to expand...
Click to collapse
ya correct, just few day back i have asked this issue to developer
http://forum.xda-developers.com/showpost.php?p=22170417&postcount=5
But it will work perfact if you use proximity + light both sensor enabled.
Color has no influence, distance between an object and the proximity sensor is what matters. I've just tested this using pieces of paper, cloth, metal and wood in white and black colors. The sensor seems unable to correctly register anything that is less than approximately 1 mm away from the glass (it may report 0 cm or jump to 5 cm). Also it seems it only reports changes of a certain minimal distance between two readings, even if the reported value remains the same as the old one. Anything below the threshold of the 5 cm reading will always result in a reported value of 0 cm, but if the effective distance between reading A and reading B was below a certain threshold, the sensor will not report a new reading of 0 cm (thus an object hovering stable over the sensor will not produce a 2nd post). I'm not sure if the sensor has a state that can be read at any time. From my tests using AutomateIt Pro, it seems only new posts can be used by apps. And if the delta between two readings is to small to make the sensor post a "new" result, then this can be problematic under certain circumstances (like trying to turn the screen off after the flip cover got closed (prox. sensor = 0 for 0 sec) and stays closed (light sensor = 10 for 5 sec) while preventing the screen from going off after an accidental wipe over the prox. sensor e.g. with the hand).
@Dr. Ketan: I've tested Power Switch (again) and I'm quite certain that for the Note + Flip Cover it only works through the light sensor (which is unsatisfying since it then won't work correctly in the dark). Covering the proximity sensor only doesn't make the app reliably react.
Power switch works ok for me with the Samsung flip cover. I have the confirmation set to minimum Abe theactivation delay set to 0 seconds.
It doesn't always work from the lock screen but works fine from the home screen or apps
Sent from my GT-N7000 using xda premium
so is it a hardware issue of software?
might it be fixes in ICS? it's fu***ng annoying! just bought the flip cover(black) yesterday and also bought smart cover app, my note's screen keeps on turn off (when flip closed) then it turns back on (flip still closed)!
Any solution for gingerbread? like proximity calibrator perhaps? (while waiting for final version of ics to come out)
Power switch will work if you use proximity + light sensor both.
Sent from my GT-N7000 using xda premium
dr.ketan said:
Power switch will work if you use proximity + light sensor both.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
It's so sensitive that the moment my finger move over the sensor, the shutdown menu pops up.
Any app that works with the flip cover?
Howdy.
On the Model: SM-N900W8" Bell Galaxy Note 3
Basically when in call, Here is a problem that is reoccuring for the past few weeks ever since a couple over the air (ota?) updates I have received compliments of google.
Enabled right now, via "call settings" = "Turn off screen during calls" is CHECKED with Green checkmark.
Just handset call, moving handset to ear to talk. Handset goes black. When removing handset from ear to click hangup, or press buttons, ie to "see" the screen... screen is continually black. - Fix = PRESS HOME BUTTON... brings screen up...
When on speaker phone call, screen is lit. Move hand to the first of 2 sensor circles by the main earpiece part, screen goes black, but does not return on.
I have tried *#0*#. = "Connection problem or invalid MMI Code". - However try again, and I get red green blue receiver etc etc.
I clicked "sensor hub test" and it went BLACK.
I had to click home button, unlock screen, and I get a white with black text stating that..
INT Check: OK
FirmwareCheck
MCU Firm Version : ST0113090300
Bin Firm Version : ST0113090300
MCU Name: STM32F401CCY6B
"blue letters" PASS
I don't see how it passed, a screen went black, did not return, just went black..
Hit the back button. Tried "TSP HOVERING". That works fancy, drawing green squares everywhere...
Under "SENSOR"
I move the hand over proxmimity sensor - ACD goes to 1000+ when I put my finger over it and the screen goes green with black fonts of the prox, acceler, barometer, lights, etc...
Prox is native when sitting still anywhere from 80-95 averages for ACD
Proximity is 0.0 and TSP Color ID: 00
The different tests are rather cool to try, but not helpful in solving my issue...
What I have done: Use a lcd led plasma tv screen cleaner from nexxtech for non streaking. A cloth that came to clean my glasses I have to clean the screen. It is streak free. I have used compressed air to thoroughly blow the area around the upper speaker / sensors and even had the battery out / cover off, etc and blown every hole around the phone.
I still cannot solve this issue of black screening.
The only resolution which leads my ear to "hang up calls accidentally" is to "un check" ie single box, no checkmark, the "turn off screen during calls" option.... ie disable that sensor thing...
I have hard booted, rebooted, cleaned, etc...
Suggestions?
I have the same problem, hoping I won't have to send my device to the service because it's a pain in my country and I will be without a phone for more than a week.
Anyone know any fix for this?
Sent from my SM-N9005 using Tapatalk
Does anyone have an idea on this yet?
See here:
http://forums.androidcentral.com/sa...-sensor-issue-during-calls-3.html#post3233866
And here:
http://forum.xda-developers.com/showpost.php?p=47329433&postcount=22
I plan on trying to return mine before re-calibrating via the above technique. Though I would like to hear peoples opinion on if its a calibration issue (i.e they didn't calibrate it from factory properly) or a hardware defect and the sensor it self is bad. My ADC value's when not covered sit at about 70 (clean screen after blowing with air at ear piece) My screen was solid green, wouldn't go white until I blew it out, I didn't check the value beforehand.
Went to Bell today and they will let me exchange it (backing it up now) I checked out the new phone they have for me and its ADC value is 30 with nothing close. From the link above it shows the "normal" value with nothing close to the proximity is around 10, not sure if I should be concerned with the new phone and try and find another if they are willing? Either way its better then my ADC 90 I'm getting today (blew with air yesterday to get it down to 70)
Thoughts? I would love to know a few more peoples ADC values.
bnevets27 said:
See here:
http://forums.androidcentral.com/sa...-sensor-issue-during-calls-3.html#post3233866
And here:
http://forum.xda-developers.com/showpost.php?p=47329433&postcount=22
I plan on trying to return mine before re-calibrating via the above technique. Though I would like to hear peoples opinion on if its a calibration issue (i.e they didn't calibrate it from factory properly) or a hardware defect and the sensor it self is bad. My ADC value's when not covered sit at about 70 (clean screen after blowing with air at ear piece) My screen was solid green, wouldn't go white until I blew it out, I didn't check the value beforehand.
Click to expand...
Click to collapse
I can't install superuser as i'm on a different model then the 2 common series out there... Unless you have some way to install root to correct...
It's more then likely difficult to complete without this...
well, I've had this exact same issue, but I read somewhere that if I blow into the earpiece (no air spray, I mean by my mouth, normally blow air into earpiece) it might get fixed. so I did and it is ok now it seems there might be getting dust under the glass through the speaker
jmaciak said:
well, I've had this exact same issue, but I read somewhere that if I blow into the earpiece (no air spray, I mean by my mouth, normally blow air into earpiece) it might get fixed. so I did and it is ok now it seems there might be getting dust under the glass through the speaker
Click to expand...
Click to collapse
I used a can of compressed air... and ADC went form 120 and non working proximity sensor to 10-15 with a good working proximity sensor.
I've contacted the seller where I bought my device (Omegacell somewhere in Alberta... for a SM-N900 imported from some other country)... they told me that if I can reproduce the problem, they will replace my device since I bought the exchange warranty at the same time. So now I'm back to square one... because I got it working with the air through the speaker "trick". Hoping that this fix will last for ever... but if it ever comes back, I hope that it will be within my 1 year exchange warranty.
Deep cleaning
I had the same problem with my proximity sensor. First it wouldn't work at all. Then ,after wiping the screen and blowing (with compressed air and mouth), it would work somewhat. The screen would go black when I put it to my ear but would not come back on after I took it down.
I tested it by dialing *#0*# and using the "Sensor" button. It would sense my hand approaching the sensor but not my hand going away.
I disassembled the phone following the instructions from GalaxyNote3Root.com (Sorry I can't post a link, not enough posts yet).
I wiped the sensor and the inside of the glass with a clean cloth, reassembled and the phone is now good as new.
This might obviously void your warranty, but on my AT&T SM-N900A there are no seals or tapes of any kind that has to be broken to get access. So no warranty voidage. At least no way anyone can tell you the phone was opened as long as you are carefull.
The whole operations takes about 15 mins.
I was messing up with my Note 3 to fix proximity sensor and get it disturbed even more. I added offset value
and now when I checked the proximity sensor with *#0*#, Value are all screwed. Now it shows some Offset, High THD and Low THD values under proximity sensor as well and these values are crazy.. Offset: 8100, High THD: 8300, Low THD: 8200, All values are over 8000. when I put hand over sensor it change from some crazy ADC values of 839 to 1040 something. Can someone please help to reset to factory default. I want no offset, how I can remove offset or do factory default sensor values... please help
Yeah, i had the same problem with yours, it is cause by the dirt under the screen glass. I wonder why there is SO MUCH SAND UNDERNEATH THE GLASS. I was.. seriously? is the phone made on mud?
Only i can say is you go watch any disassemble video and clean it from inside.
and YES, ONLY WAY TO PERMANENTLY SOLVE THE PROBLEM
And the dust keep going back inside...
How to fix this permanently?
Is it? coz mine don't..
Yeah, it is. I have cleaned mine about 5 times already.
And I tried to put a piece of clean sheet inside the earpiece hole to filter out dusts, but it still can get in.
I'm at lost... Which one is need to be sealed in order to keep out the dusts?
I don't wanna open my phone again and again...
this will solve your problem for good!!!
Thanks me latte
http://www.infotales.com/samsung-galaxy-note-3-proximity-sensor-issue-fix