proximity

I want to get notified when the user raises the iphone to his face. Just like siri does. Is it possible? Add more specific requirement: I want to darken the screen when user put the phone near his ear. I know the Proximity Sensor can be enable to implement this. But it's annoying that the screen will be darkened from time to time when user moves the finger upon the sensor. So I wonder how to avoid this case and only darken the screen when user raise the iphone to speak? See Using the Proximity Sensor in the UIDevice Class Reference. So, you: Enable it: UIDevice *device = [UIDevice

I want to intercept the proximity sensor without turning off the display. I know by the documentation that I have two Bool variables: proximityMonitoringEnabled proximityState and this code [UIDevice currentDevice].proximityMonitoringEnabled = YES; When the proximity sensor detects something it turns off the display, same way it does when you're holding the phone to your ear when on a phone call. How do I keep the display on when the proximity sensor is covered? After reading different forums on the topic, its currently not possible for us in the public api to prevent the iPhone screen from

Question 1: In Lucene's SpanNearQuery (or span_near in ElasticSearch), what is the exact meaning of slop ? Is it the number of words separating the two matching words, or is it the separating number of words plus 1? For example, suppose your indexed text is: foo bar biz Which queries would match this text: "foo biz"~0 , "foo biz"~1 , "foo biz"~2 I would expect that the first wouldn't match and the last would. But what about the middle? Question 2: Now a second and more complex corollary question: how is slop handled if there are more than two search clauses? Is it applied to each pair of

Problem definition: I've been trying to use BLE proximity profile for Bluetooth LE on Android. Some of the devices like new generation Google Nexus tablet with 4.3 Android support BLE and can act as a central device. I read the Android official documentation of the Bluetooth LE but their doesn't seems any support for that. Is their any workaround to implement our own proximity profile? Questions which talk about proximity profile on Android but are of no help Reading Bluetooth RSSI for BLE proximity profile in Android . How to use the profile of PROXIMITY PROFILE,IMMEDIATE ALERT SERVICE and

(This is a follow-up from this previous question ). I was able to successfully use OpenCV / Hough transforms to detect lines in pictures (scanned text); at first it would detect many many lines (at least one line per line of text), but by adjusting the 'threshold' parameter via trial-and-error, it now only detects "real" lines. (The 'threshold' parameter is dependant on image size, which is a bit of a problem if one has to deal with images of different resolutions, but that's another story). My problem is that the Hough transform sometimes detects two lines where there is only one; those two

This question is not exactly about code but rather implementation. I am working on an app that requires to check if the phone is in pocket or not. I have a simple algorithm to detect user steps when walking. The problem is movement in hand can also be registered as a step, e.g. when user runs the app and zeros the step values from the time that he/she does this to the point that the phone is in pocket, the app registeres a few steps. My idea is to check proximity sensor and see if the phone is in pocket. What I do with accelerometer sensor is that I continuesly read the accelerometer values in

I use Solr's proximity search quite often to search for words within a specified range of each other, like so "Government Spending" ~2 I was wondering is there a way to perform a proximity search using a phrase and a word or two phrases. Is this possible? If so what is the syntax? This appears to be "somewhat" doable. Consider this text: This is more about traffic between Solr servers themselves "more traffic between solr" ~2 "more about between solr" ~2 Even if you change the order it works: "more about solr between" ~2" ~2 But too far apart and it stops working: "more about servers