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.
Related
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.
Does the current CM7 build restore functionality to the Proximity and Orientation sensors to the point where they can be used with standard apps?
Does the NT have a proximity sensor? I did not think so.
Sent from my NookTablet using Tapatalk
Just going by statistics from a couple of apps i.e. Android Assistant which purports to give Name, Vendor, Range Resolution and Power data for installed hardware as follows. (list not complete)
Proximity Sensor - SFH7741 By OSRAM
Rotation Vector Sensor - Google Inc
Temperature and Pressure Sensor - PMP085 by Bosh
Magnetic Field Sensor - HMC5843 Magnetometer By Honeywell
Linear Acceleration Sensor - Google Inc.
Light Sensor - BH1780gli By ROHM
Gravity Sensor - Google Inc.
Accelerometer Sensor - kxtf9_accel by kxtf9
No Gyroscope Sensor or Orientation Sensor listed
My error on the Orientation Sensor I should have said, and am most interested in, the Magnetic Field Sensor
Other apps report similar hardware available.
Besides the holy grail of Bluetooth, I was wondering if the CM7 versions have been able to natively find and activate them (if they in fact exist) or if each had to be detected and programing specially written.
Another possibility is that other necessary hardware was never included to utilize all the sensors.
In other words...
Has anyone with the latest CM7 root tried and successfully to run a compass program? I am happy with my simple Nook and Zergy root with BN access but would build a new SD card if I had a working compass for some astronomy apps.
Thanks for any additional info.
I tried a compass on CM9 and got a magnetic sensor error.
Sent from my NookTablet using Tapatalk
Screebl Pro doesn't work on CM7 alpha final.
I think you need to wait for next update...
Odd thing that Screebl doesn't work. I would think that it would use the same sensor for angle identification that other programs do. For instance a nice little program called Skeye can show you the night sky when you and change the vertical angle and/or rotate from portrait to landscape but it does not recognize rotation to different compass points apparently because there is no driver for the magnetic field sensor.
It appears that in my list of sensors above that anything listed with a Google driver is functional. Those without are not. But given that the manufacture of the sensor is listed, there might be Google drivers available that can activate them.
Thanks to those that did some testing
I don't know if this is exactly where I should post this but.. I have a zte valet (inexpensive android phone that tracfone is selling) It seems pretty decent for the price. Running 4.1.1
It seems to have a ak8962 magnetic field and rotation Orientation sensor. Using a few software programs like 'my android sensors' show these two sensors but they don't return any data.
3 questions.
-How the heck is my screen rotating if the orientation sensor doesn't return data...
-Are the sensors on chip? or is there a separate sensing module that just isn't installed?
-Could this be a android thing - not the right driver or something? ie.. Is it fixable?
I have done a few searches but am coming up with nothing.
Thanks!
sam
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.