Greetings,
It seems that according to specs, the Verizon Tab 7.7 has a proximity sensor. However, every app I have tired that will turn the screen off when I close the cover, does not seem to work. The most recent one I tried, "Cover Lock", says I do not have a proximity sensor.
Can anyone confirm if this device has a proximity sensor. Also, any working app to turn it off when I close my case?
Also thinking this version does not have the compass either.
Thanks for any advice.
Doug M.
My GT P-6800 tab has a proximity sensor, but it only works when I make calls.
Iam trying trial app on google play called Smart Screen Off, it seems to work ok.
Copyright© xda-developers.
Powered by Searchlight © 2012 Axivo Inc.
Related
Hi...
Does anyone knows if there is a way to disable the proximity sensor on a Milestone??? or better yet.. recalibrate it..
I have replaced the glass after having smashed the old one.. and now the phone always think the proximity sensor is activated..
my stone,too .
anybody help us? please!!! i lov my stone!
So, ur phone is thinkin' that sensor activated? If that has mean only in dialer, try installing this program: myLock phone tools and set there "Onscreen Accept", "Onscreen Reject" and "Touchscreen lock", that should help u.
I am having same problem, proximity sensor isn't working properly, once screen goes off, can't drop the call. Is there any script or app which can disable prox sensor completely. I am using Android 2.1 rooted phone.
Thank you very much in advance.
same problem
Same problem here my proximity doesn't works, if I call or I attend call screen gets black
None of the keys works at this time. I found an app in market called 'proximity screen off' but as its an app It eats ram & it needs to run anytime in background I need a permanent solution.
Somebody have any idea to disable this sensor using
Any scripts through terminal? Or ...
Check out here: http://forum.xda-developers.com/showthread.php?t=779189
I have the same issue I already put some spongy tape above the proximity sensor but it's not perfect. I always press the the display with my finger an inch below the left upper corner of the phone after a call and the screen is back.
http://www.youtube.com/watch?v=5R5BM9dXmMg
I used Proximity Sensor Finder app from market to test my sensor.
Hi all. I own a i9000 running aokp milestone 6 but decided to buy a faulty i9000 on ebay just for a bit of fun really.
The problem is when making a call the screen stays black or freezes and won't respond. The call stays connected so no way to hang up.
I installed "Proximity sensor finder" on my own i9000 which worked great. (0cm when sensor is on, 5cm when off). Tried this on the damaged phone and it stays at 5cm but still shows "proximity sensor: available". I have replaced the proximity sensor with a new one but didn't do anything. Also tried it on stock rom and AOKP milestone6.
Any ideas folks? Would really like to get this working.
My proximity sensor is not working on any app.
But *#0*# shows the sensor value changing....
Help.?
What apps are you trying it with?
As far as I remember proximity sensor works only with phone calls, pretty much only when you talk and it can be set to off, so check your settings. I also would like to know what other apps work with the sensor?
The proximity sensor doesnt turn the phone screen off during calls.
I meant to say that those sensor testing apps on the playstore is Not showing responses with the prox sensor but *#0*# does.
I'm having the same problem... Phone does not turn display off when it's at my ear.
I had the same issue wit mu new T-mobile Note8 (pre-ordered from Samsung) I have sent it back
Mine gets stuck at 0cm. (As if the phone is at my ear) it causes the screen to be off whenever I'm in a call. I have to reboot the phone to correct the issue.
Try this app and check if it works?
Phone INFO ★Samsung★: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
(in the HARDWARE tab > Sensors)
It will change between 8cm and 0cm.
today when I woke up, I suddenly realized that " all of the sensors" dont work!
even I tried *#0*# none of the sensors values are changing. even sensorhub self test fails!
also IRIS scanner stopped working!
isnt it STRANGE?
all of them stopped working suddenly
I have a exynos 950F, and proximity sensor does work fine with third party apps, I use gravity screen, and macrodroid mostly to make the screen on/off in diverse situations macrodoid is very useful for automation many things
none of the sensors work on my Galaxy note 8
I have the same issue, none of the sensors work, i mean proximity, gps, auto brightness, and gyroscope don't work on my Galaxy note 8.
Does anybody know what should i do?
I also rebooted my phone.
When i am on Google maps, and turn the location sensor on, suddenly the phone find the location, after that, the sensors doesn't recognize the location.
it also happens for auto brightness sensor, when i unlock the phone, it works, suddenly it stops working and doesn't change.
I tried *#0*# none of the sensors values are changing.
I don't know what the problem is? Is it about the software or the hardware?
I updated the phone, rebooted it, but nothing happened.
Hey All,
Im from Sri Lanka and i too have the same issue Non of the sensors works. I gave the device for service and as for them Samsung asked them not to do any repair but to rerun the phones to Samsung Korea and give a full cash refund till the issue is sorted . Issue begins with a official Samsung Software update and it cannot be reversed. They have done main board replacement in one phone they got but the same issue has come aft the software update and its a issue for one production batch. May be Affecting Asia region.
I'm developing app for WiFi calling.
I want to turn off screen when proximity sensor reports "near". It work fine on other phones but on S10 phone looks like proximity sensor is not even activated - there is no white dot blinking on top part of the screen.
If I make normal call or use WhatsApp dot starts blinking as soon as I start the call.
So what do I have to do in my app to make that white dot blink on Samsung S10 phone?
I'm not quite sure, but there seems some kind of known issue with the proximity sensor that dates back to at least March. Screen coming on while in your pocket, screen not lighting up when pulled back from your face during a call, screen randomly coming on while on a call, despite it being pressed against your ear/face. I've tried everything suggested and the issues remains, unfortunately I'll be returning my S10+ and going back to my S8+, pretty disappointing for a $1,000 phone.
It's always recommended to do a factory reset after an update, problems happen not only on Samsung, even on iPhones, not a big deal.
Try this?
https://forum.xda-developers.com/showthread.php?t=2568003
TheNurd said:
I'm not quite sure, but there seems some kind of known issue with the proximity sensor that dates back to at least March. Screen coming on while in your pocket, screen not lighting up when pulled back from your face during a call, screen randomly coming on while on a call, despite it being pressed against your ear/face. I've tried everything suggested and the issues remains, unfortunately I'll be returning my S10+ and going back to my S8+, pretty disappointing for a $1,000 phone.
Click to expand...
Click to collapse
During normal phone call my sensor works as it should.
I just don't know how to activate it in app that I'm developing.
On all other types of phones this is not a problem, since this sensor is always on. It is just S10 series that have some kind of special sensor which have to be activated. You can see white dot (left form the front camera) blinking during call... that means that the sensor is activated.
The only other app I saw apart from phone app that can activate this sensor is WhatsApp. It activates it during call or during listening to voice messages.
I also checked Google Duo, Messenger Lite and Linphone app and none of these doesn't activate sensor. So it must be something that WhatsApp knows and others don't.
I also asked this on WhatsApp support, but I was ignored of course.
Do you find how to activate it? I have the same problem in my app and it looks similar on new Samsungs (I find it out on Galaxy Note 10)
Thanks for replay.
I am having an issue where always on display is staying ON while in pocket/faced down on the table. Feels like the proximity sensor is not working while on the AOD.
Plus, the proximity sensor doesn't seem to work while in the pocket either. The setting 'prevent accidental touches' has been enabled, however it is still responding to 'double tap to wake' while in the pocket for whatever reason...
Is there any fix to this?
I noticed the AOD stays on in my pocket as well. I thought maybe it was by design that way, even though it makes no sense.
Have not had a single pocket wakeup though.
It does seem that the proximity sensor (which is really the camera) doesn't work especially well though, from reports of people noticing it on phone calls. Hopefully something that can be fixed in software.
jdock said:
I noticed the AOD stays on in my pocket as well. I thought maybe it was by design that way, even though it makes no sense.
Have not had a single pocket wakeup though.
It does seem that the proximity sensor (which is really the camera) doesn't work especially well though, from reports of people noticing it on phone calls. Hopefully something that can be fixed in software.
Click to expand...
Click to collapse
Thanks mate, appreciate your feedback. Proximity sensor works fine on my phone during calls. Can't think of any reason why Samsung would intend it this way...
Proximity sensor issue here as well
I have the same problem. I put phone into test mode and it was bad compared to my wife's s9 search proximity sensor s20fe on YouTube and see others with issue
There is no fix. This is apparently the way AOD works now. I can't remember if it started with the S10s or S20s.
uggies said:
I am having an issue where always on display is staying ON while in pocket/faced down on the table. Feels like the proximity sensor is not working while on the AOD.
Plus, the proximity sensor doesn't seem to work while in the pocket either. The setting 'prevent accidental touches' has been enabled, however it is still responding to 'double tap to wake' while in the pocket for whatever reason...
Is there any fix to this?
Click to expand...
Click to collapse
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
No problems with Verizon S20 FE 5G UW
Huberttus said:
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
Click to expand...
Click to collapse
I just purchased the Samsung S20 FE 5G UW (how about we shorten this to FE UW?) with all updates AND a glass screen protector and have no touch/proximity issues.
FYI I bought it at the Costco kiosk for a few dollars less per month, no activation charges and a 90 day return policy.
the Galaxy S20 FE (5G) has no physiscal proximity sensor.
Insted it uses a combination of the front camera, touch screen and gyroscope.
I have tested the proximity issues, luckily for me there were ok...turn green. The only thing that drive me crazy is the touch screen issues which never been fixed even after updates. Oh well at least its better than before.
Huberttus said:
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
Click to expand...
Click to collapse
Mate great information here, really appreciate this.
Tested the Proximity sensor using *#0*#, I agree with your analysis. The proximity must be using electric reaction to detect if my ears are touching it or not. Covering it with a book does not trigger a proximity sensor... This explain why my screen keeps waking up in the pocket.
As much as this is annoying, there appears to be no way out Just have to let the phone face outside rather than my legs.
I also have the same issue, while on a phone call, the phone's screen goes on and off constantly and I can see the notification bar moving. Very annoying.
This is a terrible design by Samsung. The punch hole usually goes in the "Empty" part of the ear, so the screen stays mostly on.
I might just return the phone because of this issue, I don't see it getting fixed by a software update.
I have the exact opposite issue with the proximity sensor on my Samsung S20 plus running Android 10 - i.e. it works well by turning the screen off when my ear/cheek/face is very close to the proximity sensor during phone calls; whereas, when the phone's screen is locked and turned off, the proximity sensor is turned off as well. Control by hardware? Software/firmware? Don't know?! To turn the screen on without using the Power hardware button, I had to enable the "Double Tap" feature in Settings.
On earlier/other Android mobile devices - Samsung included - the proximity sensor is always on - whether the screen is on, off, or currently locked. When it's always on, you can be innovative and build a widget, for instance, to turn the screen on by "waving" your hand above the proximity sensor to interrupt the laser. I suspect new(er) Samsung mobile devices like S20 and Note20 variants might be using a "virtual" proximity sensor setup/combo for controlling the device's screen - and that really sucks!
To test if the proximity sensor is always activated on Samsung S20 and Note20 variants, I type *#77692# - which displayed a hardware screen to test proximity and light sensors. Note: if you type *#0*#, the proximity and light sensor options are absent from the hardware test screen.
Has anyone found any method - via codes even - to permanently turn on the proximity sensor, even when the screen is locked and turned off?
I searched through AOSP framework vanilla codes and couldn't see anything out of the ordinary regarding control of the proximity sensor. Samsung might be doing something dubious with their firmwares/hardwares though - well, at least, the S20 and Note20 variants are having issues with the proximity sensor setup.
P.S: Not sure if you guys are aware, but Samsung mobile devices with odd designation tends to be more problematic than their even-designated counterparts, like screen's burn-ins/shadows on Samsung S3 devices, light sensor fluctuation (which affects screen brightness control) on Samsung S5s, and now proximity problems with the S20s and Note20. Samsung S20 variants are in fact "S11" variants renamed. So the trend continues with Samsung always stuffing up their odd-designated device releases.