How will you implement on kernel side the auto detection of different ALSPS or proximity sensor? lets say for example we have a 2 sensor driver namely cm3607 and cm36283, how could we implement them on the ProjectConfig.mk to make the sensor working without create two different kernel images for two different ALSPS?
Related
Hi,
What ist the difference between the Proximity Sensor and the Ambient Light Sensor?
I know, the output of the Ambient Light Sensor depends on the ambient light
but what is the proximity Sensor? How does it work on the HD2? What are the output values etc?
And: what is the main use for it?
The proximity sensor uses IR light to detect when an object is close to it. In the case of a mobile phone it uses this information so the screen can be turned off when the proximity sensor notices your head (or more accurately, your ear) which may inadvertently press on the screen when making a call. As far as the output values? I have no idea.
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.
Hiya,
I've developed an auto-brightness app and it seems to be a popular prospect among Xperia users.
However, Xperia models don't have properly implemented light sensors and naturally don't work properly. Android doesn't recognize the sensor as such, but ROMs still implement the driver since it seems some auto-brightness works on these phones.
The question(s):
Has anyone managed to gain control over this sensor?
Does some custom kernel implement it properly?
Hi to all! I have the issud with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reeding for PROXIMITY parameter from 2 up to 220 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't understand it because of ADC absence.
Moreover I tried to change proximity for working obe (from another phine), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed differenf firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
Can somebody assist in the matter?