If you think you've experienced this, please star the bug tracker issue here: https://issuetracker.google.com/issues/211840063. It may also affect the Pixel 6.
Demo made with Tasker (vs. Pixel 3, turn on sound): https://imgur.com/a/JlvKKR0
When I first got the P6 pro it woke me up a couple of times even though Flip to Shhh was supposed be on, and after some testing I realized it was due to my dark bed frame where I put my phone. Turns out the prox sensor does not work on dark surfaces (it does have* a proximity sensor even though the diagram doesn't mention it). If you are wearing clothes whose pockets are lined with dark fabric, or when setting down the phone face down, the Ambient Display may not turn off.
It's still not fixed in the December update (SQ1D.211205.017), hopefully it's fixable.
*Source: https://www.ifixit.com/News/55239/pixel-6-pro-teardown-google-actually-did-something-right
So it looks like my proximity sensor crapped out on my Pixel 5, and I need to get warranty repair done. I'm curious about the repair process and nervous about losing my factory water seal when it gets opened up by the repair store.
I've read that it is not advisable to buy any phone with a virtual proximity sensor because it'll make calling annoying and will turn the phone on in my pocket. I frankly like everything about this phone except that it doesn't have a proximity sensor. I don't think I can wait for the Note 11 pro because I may not be able to afford it. Any thoughts?
Edit: Maybe buy the Poco X3 pro which is more expensive and I'm not a gamer or get the Redmi Note 9 pro instead which is 60$ cheaper?
is there a problem with using the Omron tl-q5mc2-z proximity sensor? When i finished building the printer a couple weeks ago i was dialing in the z offset and the extruder crashed into the bed. after some troubleshooting i found that the sensor was no longer responding so i replaced it which fixed the issue and it worked fine for a few hours and crashed again. I thought maybe a wiring issue so i re-ran the wiring to the gantry to ensure i had good connections and even replaced the diode for good measure... No change so again i replaced the sensor and that fixed the issue for a couple of days then again the extruder crashed into the bed. These sensors aren't exactly super expensive, but i don't think that i should have to take apart the After-burner every few prints to replace the sensor. so again i Buy another thinking maybe i just got lucky and came across 3 faulty sensors (seems doubtful to me), and replace the sensor again. And again it this fixes the issue for a few prints and suddenly fails.
After reading thru some posts and seeing that people are having issues with z and inductive sensors i found that most issues were based on wiring and using other probes which doesn't seem to fit my problem, but i did come across a post that suggested that the Omron sensor fails with too much heat, Im trying to print ABS 240c hot end and 100c bed so i put some thermal reflective tape over a new sensor and got a whole 2 days before it failed again... more tape maybe?
I'm at a loss for what to do... should i really be spending more on sensors than filament? is there another sensor i should use? is there a solution for this? has anyone else had this problem?
I bought a used Pixel 3a in great conditions, but I'm getting some bugs after restoring my Pixel 1 backup. So maybe it's software related.
Is anyone else experiencing malfunction with the proximity sensor?
When I’m on a call and want to switch to speaker. The screen turns dark and doesn’t turn on when I tap on it and even when I click on the power button. If the press the power button excessively it’ll just end the call.
Is anyone facing this problem or is it just me ?!
Putting a pir to switch lights on would be great but what about if you sit down to watch TV they will switch off after the timer expires when it saw you move last won't it?
Found this out yesterday, maybe everyone knows about it already but I walked over an enemy proximity sensor and the interaction prompt came up. When I hit square to interact, it gave me spotting points! You can turn enemy prox sensors into your own!
From what I can tell, there is no height limit to spotting people with a proximity sensor grenade. This means you can throw them on the bottom of a building, and spot people at the very top as long as they are within the horizontal radius.
When playing breakthrough, all you need to do is keep throwing these nades towards the objective to rack in easy assists/xp. Like I mentioned earlier, if the objective is a tall building, throw it either at the top or the bottom and everyone at the building will be pinged, providing you with an assist and xp on their death. It just doesn't feel right, you're getting rewarded for multiple fights that you are far from, with no line of sight and no involvement, other than throwing a grenade when you spawned.
At the same time, the people at the top/bottom of the building can't see the sensor grenade and cannot destroy it.
hi all! Any ideas on this would be super appreciated...
Here's what I'm trying to accomplish:
- Set up a sensor that knows if my garbage bins are next to the garage or not.
- Set up an aggressive notification (e.g. flashing lights) at bedtime the night before garbage day if the bins are still next to the garage.
I've seen one other thread on this: https://www.reddit.com/r/homeautomation/comments/nudqv8/automate_trash_alert/
But am still struggling to come up with a workable solution. I want some simple sensors that know whether my garbage bins have been taken out or not. Suggestions I've come across include NFC, BLE beacons, open/close sensors. But, I haven't figured out which if any will actually work.
I have a Homeseer hub with Z wave and Zigbee radios, and the bins are also within wifi range if I have to go that route.
I'm pretty new to home automation, but am fairly technical. I'm ideally looking for specific product recommendations (or at least specifics on the types components I'd need), because I don't have any experience with things like NFC and couldn't easily figure out what I would actually need to buy to get some sort of NFC tags + reader setup working with my existing system.
I'm a PhD student and my friend in the same lab is about to defend her thesis. It's traditional that the lab makes her a fancy graduation hat. I'm the only other PhD student in the lab so... I'll be the main person building it. She works a lot with radioactive assays, and so one cool idea I had is that I build a fake Geiger counter hooked to a proximity sensor, and I place the sensor on the inside of the hat, that way, as she's putting it on, the closer her head gets to the flat part of the hat, the faster the scintillation sound frequency. Of course the hat will have dozens of other little things, but I want this to be the cherry on top.
The problem is, I'm a physiologist, I work with mice and cells and shit, I haven't the faintest idea where to even begin to make such a thing. I found this link showing to make a position based fake Geiger counter, but it sounds like too much work for someone who never even attempted anything like this. So what are your thoughts? Is this feasible? And what budget are we talking?
Also.. if this is the wrong sub, I apologize and ask that you please direct me to proper place if you can.
I recently saw a popular submission that is dated to 3 months ago which claims how "Virtual proximity Sensors are inconsistent and many times the screen turns on during calls and misstouches are frequent."
https://old.reddit.com/r/Android/comments/on7b0y/avoid_android_devices_with_virtual_proximity/
For those who not sure what it is (skip to 4:15): https://m.youtube.com/watch?v=zJNc3lMxN1U
So I want to know what are your experiences with the phone so far during calls?
For me I tested it by calling 611(canadian carrier bot helper where you make payments/getinfo) and putting the phone to my ear and alternating it to see if i could replicate some troubles that people with the s20 fe have but so far the virtual proximity sensor works fine, no problems (had the phone since Dec 24th 2021).
https://www.google.com/search?q=samsung+s20+proximity+sensor+not+working+reddit&rlz=1C1VIQF_enCA982CA982&sxsrf=AOaemvJUG3h4JMG6z1ixmabCV47l5GbDCQ%3A1640615368600&ei=yM3JYfPkI5W3tQb5jrJA&ved=0ahUKEwjz6IfCmIT1AhWVW80KHXmHDAgQ4dUDCA4&uact=5&oq=samsung+s20+proximity+sensor+not+working+reddit&gs_lcp=Cgdnd3Mtd2l6EAMyBQghEKABOgcIABBHELADOgYIABAWEB46BwghEAoQoAFKBAhBGABKBAhGGABQrxZYzxtglxxoAnACeACAAbwBiAGWB5IBAzAuNpgBAKABAcgBCMABAQ&sclient=gws-wiz
Hi to everyone, I've just read on some groups that Mi 11 Lite has virtual proximity sensor, but nobody was able to explain me what does it mean. So I propose the question in this topic, hoping for an answer. Thanks in advance to anyone who will be able to solve my doubt!
I have a two wire sensor that says on the manuf site that it is normally closed but when I check continuity across the leads they're open. Does the sensory require power first for it to close and then once it's flagged it'll open or is their something else going on with it?
Sooo I've seen that it is a frequent problems for older phones, but I didnt see anyone having this problem with a 8.3. Basically the screen of the phone turns off during calls (regular calls, whatsapp etc) and it is impossible to do anything until the other person hangs up. It's a recent phones (less than 6months) and besides this it's working great.
Are there other people experiencing the same issue?
Cheers
Many of the newer phones are coming with virtual proximity sensors, meaning they don't have a hardware proximity sensor, but they utilize the gyroscope and the accelerometer to sense when the phone is raised to the ear.
Those phones are inconsistent and many times the screen turns on during calls and misstouches are frequent.
I am finding these phones that are listed to have a virtual proximity sensing, but I am sure there are more, especially newer phones with "full screen" design.
https://www.gsmarena.com/results.php3?sFreeText=virtual%20proximity
I recently used one model with virtual sensor, and came to hate it, it was pain to use for calling. There were hundreds complaints on the internet for the proximity sensor, but nobody knew that the phone in question didn't even have a hardware proximity sensor, but some software that guessed when the phone is raised to the ear.
Judging by the models, it will be hard to buy a midrange or lower range device without this technology, but I will never buy a phone without standard proximity sensor again.
I have a poco f3 that uses a virtual proximity sensor, which results in screen turning on during phonecalls and causing accidental touches, so what I'm trying to do is disable the sensor when I get a call then enable it once the call is over, and I'll manually lock/unlock screen during call as needed. So far this is what I've tried after researching this matter, but it doesn't seem to work. I've also tried to set state to "phone: off hook" but still didn't work.
I've also noticed my ROM offers a "disable sensors" quick toggle, any way I can use that through tasker?
Device: Xiaomi poco f3
Android version: AICP custom ROM Android 11
Any help would be much appreciated
Profile: Proximity Switch
Settings: Restore: no
State: Not Proximity Sensor
State: Not Call [ Type:Any Number:* ]
Enter Task: Sensor Off
A1: Set Tasker Pref [
Set: Proximity Sensor
Value: No ]
Exit Task: Sensor On
A1: Set Tasker Pref [
Set: Proximity Sensor
Value: Yes ]We need a specialist or gadget that allows us to counter the proximity sensors. Everyone carries them and tryin to flank or even be remotely sneaky is impossible since they detect you through walls and any height. Maybe they could tell us that we are being spotted by them like in bfv or something. At least in bfv the spotting flares had to be shot in the air and the ones that could be shot on the ground had a smaller aoe and was easily visible. While the sensors are hard to see and barely make any noise and can be carried by everyone so there is always enemies throwing them on the obj. Like there isn’t even a reason to use the silencers if your going to be spotted by the sensors anyway. I’m just tired of trying to capture a point and instantly having a whole squad know my location and rushing at me all at once.
Want to be a highlighted player? Want 25k+ points per match? Run proximity sensor grenade and throw it into contested checkpoints while doing absolutely nothing else of value. Thank me later.
I already have an Awair set up in my house, but I have an Atmotube on order. I understand that the Atmotube must be away from my house location for a set period of time every day (7 hours, I think) or I will be penalized. My question is that sometimes I stay home for a few days...weekends and such and lots of times when I am home I will do some puttering around in my shed which is about 25 - 30 feet behind my house. My question, is this enough of a distance from my house to count as being away? Trying to figure out what counts as too close.
Hello,
I placed an order for the Poco F3 since there were so many good reviews of it. However, I had no idea there was a proximity sensor problem.
I can still cancel my order, so should I? How bad is the problem?
Thanks!
Especially with the advent of Solo/Co-Op servers that allow you to build up xp in an organic way, the motion balls are sort of losing their niche. Obviously they're still incredibly useful for spotting, in fact I'd argue they're currently the MOST useful spotting gadget by a long shot, but that's part of the problem. Casper's drone is decidedly a step down from them, so they ought to at least be brought in line with his drone, but I'd rather they took them out of the gadget rotation, if not now then at least once they've added a few more in.
With 128 players on the field, even 8 players per team using motion balls in a game of Breakthrough is liable to light up the whole enemy team more often than not. And I think 8 per team is a conservative estimate; any more than that and it's pretty much a match with the setting of "always show players on minimap", but with extra steps. Considering the lack of cover on most maps, the last thing we need is for everyone to be spotted all the time so there's really nowhere to hide.
That just leaves the motion ball's prolific xp farming capabilities, which is probably what pumps up the number of players using them. It's a secondary use for a gadget that's already astoundingly useful, making them ubiquitous on the battlefield and keeping everybody spotted a good chunk of the time. Perhaps the only good thing about their popularity is that it cuts down on grenade spam, but I'd argue it can functionally have the same effect when a player rounding a corner can prefire you with high accuracy.
Anyway I'm just diving into theory because I haven't been able to play in a few days so I want to talk about battlefield, so take my word with a grain of salt. I just think it might improve the quality of the gameplay loop if the motion balls weren't an option.
Everything in this phone s20 FE 5g (snapdragon) has pleased me to buy it but one thing is holding me back and that is its virtual proximity sensor. I would usually be on long calls and I don't want accidental touches while I am on call. How reliable is the proximity sensor ? I have read about many users who had issues with it and all articles related to it are about an year ago. Maybe Samsung might have pushed updates to fix those minor bugs related to virtual proximity sensor. To all the users here who have been using this phone for almost an year or so, did you encounter any issues ? Please let me know. Thank you.
Does anyone have a cheap method for using a raspberri pi & motion sensor or a smart motion proximity sensor?
Or maybe there's a guide out there that I couldn't find from searching before and overlooked and someone can point me to it.
It all started when I updated to android 12. I turn on the phone, it functions normally. After about twenty minutes I get the "clean the black bar at the top of the screen" warning and I have to use my pin to unlock. Now, I don't overlymuch use the face unlock anymore anyways - I wear a mask a lot of the time now - but tap to wake, lift to wake, and all proximity sensing are broken.
Then I restart the phone, and it's back to normal for a while.
I contacted google, and after a few weeks of "looking into it" they responded with "you're out of warranty so please contact this partner company and they will quote you for the repair".
I have factory reset, and I've tried proximity sensor recalibration apps.
The sensor itself can't be broken, because it functions after a restart. It started when I updated so it feels like a software problem to me?
However, I'm fairly techy. I'm willing to attempt a repair myself once I upgrade (away from Google, too many problems like this...), In the event that it is hardware related. But I was hoping that someone here had a decent solution in the meantime!
There are countless articles about this problem, and I've read several reddit posts related to it too.
You'd think that google would put in some effort and have the sensor restart if it stops reporting, or give the user a workaround so that phone calls were a bit more manageable for people in this situation.
Anyways, there's my story.
***** EDIT**** FIXED FOR NOW. I noticed that my Fitbit was also acting up, and couldn't find a solution until I unlinked the watch, reinstalled Fitbit and relinked the watch (which took far longer than anticipated). And suddenly all the sensors work again. Seemingly unrelated, but it at least proved that it's a software problem. NOT HARDWARE. Google tried to have me pay for a repair that likely wouldn't have resolved the issue at all.
Hope it helps someone.
Not only disabling proximity sensor did nothing to addressing rubberbanding, but also introduced a shit load of bugs that actually made the game frustrating to play. Just to name a few new bugs, unable to save a load out, wrong load out at the start of a match in every match, showing the wrong grenade selected etc. All the while, I'm still rubberbanding hard from time to time, especially when a helicopter bombarding down to me, I keep getting pulled back into the center of the explosions like a free dummy target practice.
Hey!
I received my 5III yesterday, and I noticed that my proximity sensor isn't responsive.
Am I the only one which faces this problem?
Here is a video to demonstrate it: https://imgur.com/a/mS7ctCM
Edit: it seems that the glass protection was the cause!
Using Galaxy S9. During a viber call, when I block the proximity sensor with my hand (on purpose), the screen goes black. But it is disabled at Viber settings. Anyone know why?
I have a Poco F3 and it is totally crap at detecting my face during phone calls. I've installed a proximity sensor tester from the app store and just by moving my hand slowly over the phone I can fake it detecting close/far away regardless of the phone being close to anything. Just terrible engineering.
So I've read the Redmi Note 10 pro also has the same crap hardware. Is there a list of devices which fail at being phones? I don't care if the device has a real proximity sensor or not, for all it's worth it could have a little gnome inside. Tell me which devices work as normal phones.
Devices which work as phones:
- Mi6
- Mi8
- K20 Pro
- Mi mix 2s (Adsobar)
- Poco X3 pro (biohazard_IRM)
- Note 10 (Alex11039)
- 11 Lite5g NE
Devices which fail:
- Poco F3
- Note 10 pro max (0Abdullah0)
- Note 10s (guzelino)
- Mi 11x (Diligent_Mango_4952)
Hit and miss:
- Note 9 pro (sir_bazz hit, kadorna1 miss)
- Mi 10T pro (malctalk)
- Note 10 pro (ghani256 hit, kAOStics69 miss)
- Poco X3 NFC (xkiririnx hit, 9poorguy miss)
