Anyone ever thought of pulling the raw data from the proximity sensor and using as a IR sensor for, say, a remote. Sticking my tv remote by the proximity sensor, I was able to use a sensor data app to tell me that the proximity sensor was reacting to the remote when I pushed volume buttons. Sound interesting to anyone?
yeah, sounds cool
Any devs think its possible to accomplish this realistically?
This is only slightly related, but I wish there was a way to use my phone to open to proximity gate to my unit complex.
Stupid $50 for key replacements.
Maybe close range phone-to-phone communication?
Yeah, trying to lookinto it now actually. Also if the proximity sensor is sending out IR and is positioned next to the camera...I imagine an ability to detect objects/"human invisible colors" in the dark may be possible... if the amount of energy to the IR/proximity sensor could be programmatically set, depending on what eventual resistor components are installed of course...
---------- Post added at 10:34 PM ---------- Previous post was at 09:58 PM ----------
Escaladez2 said:
Anyone ever thought of pulling the raw data from the proximity sensor and using as a IR sensor for, say, a remote. Sticking my tv remote by the proximity sensor, I was able to use a sensor data app to tell me that the proximity sensor was reacting to the remote when I pushed volume buttons. Sound interesting to anyone?
Click to expand...
Click to collapse
I just now tested my remote too (a couple of years later) and yes I can clearly see the proximity sensor is reacting to presses on my remotecontrol. Limits as I can see this far:
1. The remote has to be exactly pointing towards the sensor and if more far than a decimeter away it seems to not be detected.
2. The proximity sensor in my device only returns a binary value,either it returns 0 or it returns 5, nothing in between.
Related
I am doing a project analyzing sensors. I am trying to make an experiment using the proximity sensors. I have managed to utilize apps of the market to find out some things.
The sensor has a resolution of 100cm, meaning it can detect things 100cm away. But it only have 2 settings. 3 cm and 100cm, but nothing in-between.
If there anyway i can obtain the raw sensor data? I need the in between stuff.
For example the ambient light sensor. It has a resolution of about 27,000 sci. I am able to get all the in-between stuff. but not for the proximity sensors.
Is there a way to adjust the sensitivity of the proximity sensor. It does not always dial when I raise the phone to my ear to make a call. It seems to only work occasionally. Any help is appreciated
HarlyFan said:
Is there a way to adjust the sensitivity of the proximity sensor. It does not always dial when I raise the phone to my ear to make a call. It seems to only work occasionally. Any help is appreciated
Click to expand...
Click to collapse
+1
Sorry if you're more technically inclined than this response credits you to be, but have you tried getting a can of compressed air and a microfiber cloth to clean out the top of your phone? Around the area where the sensor is?
On every phone I've had and seen people have this problem with, this has always been the solution.
Also the act of dialing out the phone call is not tied to the proximity sensor at all. That's all telephony. Unless you're talking about some kind of motion gesture, then that shouldn't matter.
There's a samsung ?motion? under settings
motion settings allow for quick dialing a contact on the screen by holding phone up to ear when they are displayed some combination of accelerometer, prox sensor, and contact on screen is supposed to dial.
Mine is stock, has the option enabled, but doesn't seem to autodial as expected or at all I guess.
Oddly, under AndroSensor app from play store, prox shows 3.1" or 0 but nothing else (almost binary) ... screen does turn off right away when I make a normal call and hold up to my ear.
Odd.
I'm trying to figure out normal (functional) proximity sensor response to light.
(originally posted this to meanbean because I downloaded meanbean specifically because it mentions the proximity fix.
Would somebody who doesn't have a problem with their proximity sensor try the following:
1) Use whatever program you like that displays current proximity distance. I've been using Proximity Sensor Finder.
2) Confirm that near and far are reporting correctly (it's binary, but reports as 9cm versus 0cm).
3) Expose the phone to strong light (e.g. put it near a light bulb).
4) Remove from light source
--> Does the proximity sensor now report NEAR even when there's no object near the sensor?
I really appreciate your testing this and letting me know here or by DM.
Thanks so much!
Have you tried this:
http://forum.xda-developers.com/showthread.php?p=31452830
[MOD] [CM10] Proximity Sensor Fix
Even though it's for cm10 it might help you... Good Luck!
Sent from my EVO using xda app-developers app
Hi!
Can anyone tell me how I get the pressure sensor to get recognized? All apps I tried so far say it's not there, but apparently the compass app from the stock ROM does display the pressure data. Does anyone have the stock pressure app? I'm running AEX.
Would a different kernel help for that?
Thanks!
Molvol said:
Hi!
Can anyone tell me how I get the pressure sensor to get recognized? All apps I tried so far say it's not there, but apparently the compass app from the stock ROM does display the pressure data. Does anyone have the stock pressure app? I'm running AEX.
Would a different kernel help for that?
Thanks!
Click to expand...
Click to collapse
What u mn??? Pressure app ???
Almost every cell phone has a pressure sensor, and the Redmi 5 plus apparently too. But it doesn't seem to work like in all other phones. There are many apps that can read this sensor and display it - barometer apps namely and other sensor-display apps. I haven't found one that works with my 5 plus.
I have only seen mentioned that the built in compass app does display a pressure, all apps I have tried do not display a correct value, most just say "no sensor".
Sorry
No pressure sens. in RN5. Compass works with magnetic sensor which detects magnetic field of Earth. Not atmospheric pressure. Pressure sensor is only in more expensive phones included
Hello all,
Any chance someone would be interested in helping to implement fall detection on regular wear OS watches? Something similar to those on the galaxy and apple watches. Am I missing something that should be an obvious reason this hasn't been implemented?
Thanks
I have looked into this, and there are some difficulties to it. Most algorithms for fall detection use continuous accelerometer and/or gyroscope readings. There is a significant battery hit for making these recordings continuously.
As far as I know, the only way to make this viable is to use sensor batching with wakeup accelerometer and gyroscope sensors. That way, the device will be able to sleep for a significant portion of the time and be woken up when there are new measurements. Some devices (I'm looking at you ticwatch pro 3) don't even have wakeup accelerometer or gyroscope. The only way I see to get around this is using the significant motion detector which is always a wake-up sensor. Maybe this sensor will be triggered to wakeup the device when a fall occurs and sensors can be recorded at that time.
I think this is how I would go about it, but maybe I'm missing something
Sounds like a good plan for starters... cheers
permanentusername22 said:
I have looked into this, and there are some difficulties to it. Most algorithms for fall detection use continuous accelerometer and/or gyroscope readings. There is a significant battery hit for making these recordings continuously.
As far as I know, the only way to make this viable is to use sensor batching with wakeup accelerometer and gyroscope sensors. That way, the device will be able to sleep for a significant portion of the time and be woken up when there are new measurements. Some devices (I'm looking at you ticwatch pro 3) don't even have wakeup accelerometer or gyroscope. The only way I see to get around this is using the significant motion detector which is always a wake-up sensor. Maybe this sensor will be triggered to wakeup the device when a fall occurs and sensors can be recorded at that time.
I think this is how I would go about it, but maybe I'm missing something
Click to expand...
Click to collapse
I don't have a great understanding of how these all integrate into the system but I would think that the same sensor, what I am assuming is an accelerometer, that is used for the wake feature could also be used for this. Like you said, using the full suite would be prohibitively expensive from an energy standpoint, but I assume that the wake accelerometer can be used to directly measure the acceleration of the wake motion and could also be used to calculate fall detection, one that measures the acceleration and not just if said motion is occurring. So, there would be no need for the rest of the sensor suite to be used after, correct? As a side note, it would be pretty cool to have the watch read vitals and such and be able to report that with the fall notification via a continuous stream of text messages on set intervals.