OnePlus 3 gyroscope not calibrated can't play traffic rider at comfortably, cpux shows uncalibrated is there anyway to fix this issue Any idea ?
Related
Just curious if anyone else has noticed this... I'm using CM10 and the proximity sensor says it requires 20.0 mA (I think that is per hour), whereas other sensors are always less than 1, ie accelerometer is 0.13 mA.
Can others post their sensor power requirements for reference? You can use a variety of sensor apps from the play store to get this data:
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox (my favorite)
https://play.google.com/store/apps/details?id=com.fivasim.androsensor
https://play.google.com/store/apps/details?id=com.sensortester.android.apis (has a better info screen listing all sensors/power requirements)
This is the info I got from Sensor Tester (the last app I linked to)
Rotation Vector Sensor 2: 0.8
GP2 Proximity: 20.0
AK8975 Magnetic Field: 0.8
AK8975 Compass Raw: 0.8
AK8975 Compass: 0.8
BMA150 accelerometer: 0.13
I'm curious why the proximity sensor is so abnormally high relative to the others or if this is just a case of misreported data. So if anyone has other values for reference or an explanation as to why this might or might not be the case, please chime in!
I also noticed before that in the "stable" version of CM9 the proximity sensor was broken, but it has since been fixed. Not sure if this might have anything to do with it or be relevant.
Also, does our phone just not have an (ambient) light sensor? How does auto-brightness work/not work on our phone?
~Troop
Trooper_Max said:
Just curious if anyone else has noticed this... I'm using CM10 and the proximity sensor says it requires 20.0 mA (I think that is per hour), whereas other sensors are always less than 1, ie accelerometer is 0.13 mA.
Can others post their sensor power requirements for reference? You can use a variety of sensor apps from the play store to get this data:
This is the info I got from Sensor Tester (the last app I linked to)
Rotation Vector Sensor 2: 0.8
GP2 Proximity: 20.0
AK8975 Magnetic Field: 0.8
AK8975 Compass Raw: 0.8
AK8975 Compass: 0.8
BMA150 accelerometer: 0.13
I'm curious why the proximity sensor is so abnormally high relative to the others or if this is just a case of misreported data. So if anyone has other values for reference or an explanation as to why this might or might not be the case, please chime in!
I also noticed before that in the "stable" version of CM9 the proximity sensor was broken, but it has since been fixed. Not sure if this might have anything to do with it or be relevant.
Also, does our phone just not have an (ambient) light sensor? How does auto-brightness work/not work on our phone?
~Troop
Click to expand...
Click to collapse
Hi,
I got to this site from google trying to see what's the declared memory usage of a proximity sensor (I remembered ~50mA).
To answer your question (and correct you a bit):
1. The power consumption is 20mA. It does not depend on time.
If you wanted to know how much it consumes per hour then... just multiply it by an hour - result is very simple: 20mAh.
Some example what does it mean:
Let's say that your phone has battery ~1800mAh and can withstand ~30 hours without charging (I'm neglecting voltage what might be a mistake under some circumstances) having proximity sensor disabled. It means that normally your phone is consuming 1800mAh/30h=60mA.
If your proximity was always on then cummulative current would be 60mA+20mA=80mA. The phone could withstand 1800mAh/80mA=22.5h
2. High power usage is related to how a proximity sensor works.
Look close and you would see 2 "windows".
Use another phone's camera in a very dark place (usually you might even see it with your own eyes depending on the light wavelength). You should see that it's glowing with a "red" light from one of the windows.
The second window is a kind of "camera". It has very low resolution (probably a single pixel). More technically it is just an optical element.
When your windows are covered - the camera won't see the light (but still some gets there through your skin).
Your skin works like an mirror reflecting the light when it gets near.
When it's far then light is not reflected into the window.
Proximity sensor usually reports 2 states when enabled: near or far.
So you need to power 2 devices: light emitter (at least 10mA) and light detector.
Normally you won't see the light as it is "not visible to human eye",ex. near infrared (but you might observe its glow or some other effects generated by it).
Cars have different proximity sensors: sound wave is used instead of light wave. Sound wave is much slower and it is possible to measure how long the sound travels back. This way you know the distance and it does not depend on the type of surface reflecting the sound.
And LED (Light Emission Diode) has often power usage ~100mA - then it's shining bright and shouldn't burn that fast.
compass app showing wrong directions, i tried other compass apps but non of these are showing right direction. i dialed *#0*# and checked sensors and found that magnetic sensor needs calibrating, how can i fix compass issue, and how to calibrate magnetic sensor, i tries moving phone in "8" direction but didn't helped....
Mohanshbhr said:
compass app showing wrong directions, i tried other compass apps but non of these are showing right direction. i dialed *#0*# and checked sensors and found that magnetic sensor needs calibrating, how can i fix compass issue, and how to calibrate magnetic sensor, i tries moving phone in "8" direction but didn't helped....
Click to expand...
Click to collapse
Just shake your phone in multiple directions, when the meter indicates 3 and blue in color. Then you have successfully calibrated your compass.
Done that on my phone too. :good:
I'm using nokia x and found a setting (Turn on Proximity sensor) in it that states it will dim the display when attending a call .
It works as like a light sensor and it seems proximity sensor is not present.
CPU z app shows a record for the proximity sensor but doesn't show any reading all the time.? Is this issue only on my device ?
I have a compass problem. About 180 degress mistaken..
I checked the sensor with Sensor List program and It works
But When I check calibration menu, blue point could move.
Do you have any idea?
firmware XXUBNA1
I've installer the GPS and compass calibration app and I still get jumps and weirdness from the compass.
Anybody?