Just throwing this out as a non-developer.
Would a software fix to increase compass sensitivity fix the compass issues we are having? I've seen apps that allowed you to dumb down the compass, with the goal to be anti-jitter, perhaps making it more sensitive would make it more responsive? (Compass app for one, but sadly it doesn't let you turn the sensitivity up)
..again, just a thought, and hopefully not a dumb one.
-Matt
Related
Ok Ive drawn a blank.
I want to measure the ambient light level; it seems that SE must have used a non-standard (surprised?) implementation, as various apps that can read the sensor on other phones cant read the light level on the X10.
I can find no help in the XDA forums or through google.
I have searched through /sys/devices for anything looking hopeful but no luck. I was hoping a file would hold the sensor value, just as http://forum.xda-developers.com/showthread.php?t=1284938 shows how to measure charging current by reading a file deep in /sys/devices.
I want ideally to use light readings with Tasker to control the phone, but also it would be great if Juicedefender could control screen brightness for us as the screen is my main battery drain.
Pointers, hints or even the answer all welcome!
Thanks in advance
Chris
Hello guys,
My proximity / light sensor is not behaving correctly for past few days. Now whenever i dial a call, the proximity sensor turns the LCD off and it does not turn it on until the call ends somehow. It seems to be that the sensor is unable to sense the incoming light. Also the little red LED of the sensor stays on for very long, even after the call.
Also, the screen's brightness does not change when i move from low light to high light areas (and vice versa).
I have jokersax's CM9 build 0.6.1 installed with the built in kernel. (Which is probably the CM9 kernel too).
I suspect the proximity sensor is faulty. And also that this is a hardware problem. Now the question I'd like to ask is does anyone know what parts do i need to replace in order to get it back working. What would I tell the repair part vendors to send me ?
Also, do you agree that this is a hardware problem??
OR do you think, it is the ROM may be or the way I've installed it??
shabeepk said:
Hello guys,
My proximity / light sensor is not behaving correctly for past few days. Now whenever i dial a call, the proximity sensor turns the LCD off and it does not turn it on until the call ends somehow. It seems to be that the sensor is unable to sense the incoming light. Also the little red LED of the sensor stays on for very long, even after the call.
Also, the screen's brightness does not change when i move from low light to high light areas (and vice versa).
I have jokersax's CM9 build 0.6.1 installed with the built in kernel. (Which is probably the CM9 kernel too).
I suspect the proximity sensor is faulty. And also that this is a hardware problem. Now the question I'd like to ask is does anyone know what parts do i need to replace in order to get it back working. What would I tell the repair part vendors to send me ?
Also, do you agree that this is a hardware problem??
OR do you think, it is the ROM may be or the way I've installed it??
Click to expand...
Click to collapse
If you have face unlock enabled then disable it and try it again.
Sent from my MB860 running Jokersax's CM9
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.
For quite a while, almost over all recently updated roms, i found out that ambient display feature now activates the touch screen which may lead to a turn on if pressed. I haven't encountered this issue back then, i was very happy with this feature, but now i misclick things most of the times when i take out to check the clock and put back my phone in the pocket.
It's not kind of major issue, but it's bothering, and i can't live without ambient display.
The reason i made this thread is to ask if anyone found any solution to disable the touch when im using ambient display, thanks.
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.