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
Related
Ok in the galaxy s2. If you go to settings, display, then at the bottom, you have horizontal calibration and gyro sensor calibration.
If you choose horizontal calibration you get a little test thing with the dot in the middle and it moves as you tilt the device.
When I go to gyro sensor calibration the dot just stays in the middle and does not move. Is this normal ?
Can someone try the above please
yep i tried this before, same here, but i think it's normal
If you look two different calibrations .
jje
I know, but shouldn't the dot move when you tilt the device. I thought thats what the gyro does
Do it while you are in the car (as a passenger), and see if that move when the car accelerates or slows down
Why would one calibration act the same as another .
jje
I am having the same problem the gyro calibration was working till i click on calibrate as soon as i clicked it i no longer see the ball moving :/ tried wiping and everything nothing worked.
Mine doesn't move either.
I could of sworn mine was moving last time I checked! Very strange..
I cant get mine to move either.
Maybe this might help.
http://en.wikipedia.org/wiki/Gyroscope
the gyro problem is annoying .. every app just turn into landscape mode :/
hope someone fix it fast ;/
sorrowuk said:
Ok in the galaxy s2. If you go to settings, display, then at the bottom, you have horizontal calibration and gyro sensor calibration.
If you choose horizontal calibration you get a little test thing with the dot in the middle and it moves as you tilt the device.
When I go to gyro sensor calibration the dot just stays in the middle and does not move. Is this normal ?
Can someone try the above please
Click to expand...
Click to collapse
Before I root my Samsung, can you tell me what rom you have installed or what you did last?
Thx
Morichio said:
Before I root my Samsung, can you tell me what rom you have installed or what you did last?
Thx
Click to expand...
Click to collapse
Lite'ning rom , it was working untill i clicked on calibrate after clicking it it got stuck :/ well that me i don't know about the OP.
I have the same problem (indications for gyro callibration) but also a magnetic sensor problem (see this http://forum.xda-developers.com/showthread.php?t=1111355 threat)
I used an app called sensor test / plot which shows problems with the magnetic sensor and orientation.
Anyone having the same problem?
Try an App called GPS status, it displays the output of all the GS2s sensors on one screen, including satellites, compass, gyro and accelerometer, at least you can reassure yourselves that the various sensors are actually working
erikcornelisse said:
I have the same problem (indications for gyro callibration) but also a magnetic sensor problem (see this http://forum.xda-developers.com/showthread.php?t=1111355 threat)
I used an app called sensor test / plot which shows problems with the magnetic sensor and orientation.
Anyone having the same problem?
Click to expand...
Click to collapse
All the numbers move for me using the sensor test/plot app.
in sensor test everything is working but the phone just stay in landscape mode .. thats the problem that i have.
You can try *#0*# on your dialler and then use the Sensor test and check if everything is all right.
tested on *#0*#it says its working fine as well .. :/
Recently my magnetic sensor did not work. Yesterday suddenly it came to life exept I don't trust it.
Just to check if my sensors are OK I would like to compare some data. I use *#0*# and the SENSOR
My readings are (when on table):
ACCELEROMETER Sensor Raw Data
x:-10/10 y:-20/-40 z:3030/3060
Gyroscope Sensor
Y:-0.01/-1.00 P:0.01/0.80 R:0.01/0.90
Gyro self test OK, Graph shows normal plot with rotation around all axes)
Magnetic Sensor
Magnetic: x:-45 y:-600 z:1086 (values change with orientation but stay around the same range, exept for the z value, it stays at 1086.48 contantly)
Azimuth: 176 (changes just +/-2 degr with rotation and +/- 20 degr with roll)
Pitch: 0,050 (changes normal with pitch)
Roll: 0,40 (changes normal with roll)
Little compass indicates South (red line towards you) and does not change with rotation (just +/- 20 degr with roll). It also says need for calibration and the number 0.
I know values will be different with everyone but should be around the same range. I have values (Accelerometer) in the 10 / 30 and 3000 range depending on de axis. Same with the Magnetic sensor 50 /600 and 1080 range.
As the magnetic z-axis value is stuck I expect a faulty sensor.
the test is all good to me but the image test it failed to move from landscape to normal. hope someone can help :/
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 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.
So I've used the search bar and google
there are 4 circles at top
1. Ambient Light sensor
2. LED notification lights
3. ???
4. Proximity Sensor
so whats in between the earpiece and proximity sensor
also why dont apps recognize the ALS? I've used android sensor box, androsensors and my android sensors but still nothing. Though auto brightness works. I know, I move my finger over it and the screen gets dim
z50j said:
So I've used the search bar and google
there are 4 circles at top
1. Ambient Light sensor
2. LED notification lights
3. ???
4. Proximity Sensor
so whats in between the earpiece and proximity sensor
also why dont apps recognize the ALS? I've used android sensor box, androsensors and my android sensors but still nothing. Though auto brightness works. I know, I move my finger over it and the screen gets dim
Click to expand...
Click to collapse
The last 2 sensors are for proximity i guess, cause even on my mini pro i have 2 circles for proximity. In the stock rom, it is never detected, its on by default. In roms like cm10, CM10.1 etc. you can choose whether to use it or not, change the different levels etc.
Well in mini pro its
Led, ambient sensor, camera, proximity.
Tbh, I think I have seen two dots instead of one for sensor. (Really hard to see)
Regards
N
mnishamk said:
Well in mini pro its
Led, ambient sensor, camera, proximity.
Tbh, I think I have seen two dots instead of one for sensor. (Really hard to see)
Regards
N
Click to expand...
Click to collapse
Yep there are two sensors for proximity.
why are there 2 sensors for proximity? using the sensor apps I've noticed that only that the right most works the 3rd one doesnt really do anything when i cover it. but it works so I'm fine with that
but how come the apps dont detect the ambient light sensor? that too is obviously working because the screen dims when i hover over it
Try using the service menu and see if it works there
Regards
N
mnishamk said:
Try using the service menu and see if it works there
Regards
N
Click to expand...
Click to collapse
I did, it doesnt
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.