Related
Now with Nougat Support!
Shout to Rovo89 for the Xposed Framework, and the various people who inspired this.
Sensor Disabler (previously known as Disable Proximity) is an Xposed application that allows you to disable or modify most of the sensors on your device, including the proximity sensor. It supports Tasker for changing the sensor status (via In-App Purchase), a blacklist/whitelist for choosing how certain apps will respond to Sensor Disabler, and a reliable and efficient way of modifying and disabling sensors without causing unnecessary slowdown on the device.
I can't offer support for phones that I don't own, but if your phone runs a close to AOSP ROM (for instance Nexus devices) or a CM-based/Lineage ROM (which I can easily see the sources for), this should work. If you're having issues, try to gather the logs from the Xposed app that relate directly to this app and post them here as well as your issue. I recommend reading over the logs yourself to see if the issue might be with your Xposed installation and not the app itself.
Links:
Source Code
Module
Google Play Link
This has been tested on:
Nexus 5 running 4.4.2.
Nexus 5 running 5.0.1.
Nexus 5 running 5.1.
LG G2 running 4.2.2.
OnePlus One running CM11S.
OnePlus One running COS12.
Nexus 6P running 6.0
OnePlus One running LineageOS 14 (Nougat)
Currently, this mod works on 4.2 - 7.1.
Post any questions/requests/etc in this thread, and I'll attempt to get to them in a timely manner.
- Wardell Bagby.
here's link : http://repo.xposed.info/module/com.mrchandler.disableprox
and there is any ways to disable it totally??
WardellChandler said:
I saw a fairly important need for this app, so I decided to make it.
Click to expand...
Click to collapse
Why could I need this app and want to disable proximity?
defim said:
Why could I need this app and want to disable proximity?
Click to expand...
Click to collapse
Someone like me who does not find much of a use of the proximity sensor which has been eating up battery while im on call, would be interested in this feature
Don't work with Themasek KK 4.4.4 v105. Galaxy S3
HGT - Galaxy S3 S5 blue - any KK ROM
defim said:
Why could I need this app and want to disable proximity?
Click to expand...
Click to collapse
If, like me, your Nexus 4's proximity sensor is dead and you're unable to wake up your phone during calls!
HorstiG said:
Don't work with Themasek KK 4.4.4 v105. Galaxy S3
HGT - Galaxy S3 S5 blue - any KK ROM
Click to expand...
Click to collapse
Alrighty, thanks for that!
ravijani said:
and there is any ways to disable it totally??
Click to expand...
Click to collapse
Thanks. Possibly, using the Hardware Disabler app on the Play Store. I've never gotten that to work for me, though.
There might also be a way to truly truly disable it using Xposed, but I'd need to delve extremely deep into the Android sources. I'll look more into it, but definitely no promises.
Could you make an app that has an interface and that can disable touch?
Basically when I put YouTube on my device and give it to my daughter to watch her cartoons she presses the screen and videos go back and forth and even exit, I've tried searching everywhere for a touch disable option, there's 2 apps on the play store but don't work, are very old and outdated...
If anybody knows where I can find one please let me know....
Sent from my GT-I9195 CarbonKat 4.4.4
kamikaze702k said:
Could you make an app that has an interface and that can disable touch?
Click to expand...
Click to collapse
To get OT for a minute, while this might be possible, there are some inherent difficulties associated with this. You should look into an app like Live Lock: YouTube & Kids Lock for Android. Best of luck!
Update 1.01 don't work. S3 Temasek KK 4.4.4 v1.05, Boeffla Omni Kernel.
HGT - Galaxy S3 S5 blue - any KK ROM
HorstiG said:
Update 1.01 don't work. S3 Temasek KK 4.4.4 v1.05, Boeffla Omni Kernel.
Click to expand...
Click to collapse
Hmm. I'll have to wait until I get get the 4.4.4 source straight. Expect an update in a day or so for that.
EDIT: So I've gotten the 4.4.4 source, and I can't see why it wouldn't work. Did you reboot after installing?
A problem that plagued me for a year, gone in 2 minutes. Thank you very much.
rohail6 said:
A problem that plagued me for a year, gone in 2 minutes. Thank you very much.
Click to expand...
Click to collapse
That's what I made it for! I'm very happy to help!
Instead of disabling the sensor, you could try recalibrating, as described in this post. it worked for my Sprint GN2.
http://forum.xda-developers.com/showthread.php?t=2569141
Since the N4 suffers an annoying bug which causes a crackling noise to the headset signal whenever the proyimity sensor is active, I'd like to request an option to disable the sensor only when headset is plugged.
It would be even better if you would consider to integrate your app with Tasker so we could disable the sensor on different contexts too.
cramu said:
Since the N4 suffers an annoying bug which causes a crackling noise to the headset signal whenever the proyimity sensor is active, I'd like to request an option to disable the sensor only when headset is plugged.
It would be even better if you would consider to integrate your app with Tasker so we could disable the sensor on different contexts too.
Click to expand...
Click to collapse
I actually have been wanting to try out Tasker support, so I'll look into that. I think I can push an update that'll disable during headphone disconnected only in the next few days, then I'll work on Tasker support.
Thanks for responding so quickly and for considering my suggestions.
Working on HTC Sensation XE running Vipers ROM 5.1.2 (Android 4.1.2)
Thank you very much!!! :good: I finally solved a problem due to the proximity sensor (probably broken) whose wakelock plagued my battery after a call or automatic brightness; thank you!
Noob question: can RILJ wakelock also be related to the proximity sensor?
Bino92 said:
Working on HTC Sensation XE running Vipers ROM 5.1.2 (Android 4.1.2)
Thank you very much!!! :good: I finally solved a problem due to the proximity sensor (probably broken) whose wakelock plagued my battery after a call or automatic brightness; thank you!
Noob question: can RILJ wakelock also be related to the proximity sensor?
Click to expand...
Click to collapse
To be honest, I don't know. I've never come across the RILJ wakelock issue (literally had to Google it to figure out what you meant) but it could be a possibility?
Although, according to this article here, it has something to do with accessing your location.
My two cents is, go ahead and give my app a try and if it works, great! But I don't know anything about the RILJ wakelock issue to provide any concrete data on whether this will fix it or not. Doesn't hurt to try!
I went into google now search settings and performed the voice training and enabled the option for hot word detection from lock screen and power off but it doesn't work. the only time it works is when i'm at the home screen UNlocked OR at the google now search area. Screen off or from lock screen detection simply does not work.
does anyone else notice this?
I don't have the nexus 9 but I did install the latest google now search and launcher from apkmirror .com and there was an always listening option in 'hotword detection' in voice settings of the google now. There was also the screen off detection option but it was greyed out. I had the always listening in all apps option enabled and it was working greatly but the next day I woke up and the feature wasn't working so I went into settings and discovered that both of those options had disappeared (not greyed out but freaking disappeared), its some kind of google restriction, they are remotely restricting users from using these features for some unexplained reason.
Maybe its the same for u or it might be something else.
Same here, bit worked arter reboot
It works for a while after a reboot, but eventually stops working after a couple hours.
Looks like a common bug, I've seen some threads about this same issue (and I'm experiencing the same problem, too)
Ok, let's hope Google is on it
borchgrevink said:
Ok, let's hope Google is on it
Click to expand...
Click to collapse
OK Google... get on it RIGHT NOW! same issue on the Nexus 4 AOSP build too...
mackendw said:
OK Google... get on it RIGHT NOW! same issue on the Nexus 4 AOSP build too...
Click to expand...
Click to collapse
Is it supposed to work on the N4? (I mean when screen off).
borchgrevink said:
Is it supposed to work on the N4? (I mean when screen off).
Click to expand...
Click to collapse
think about it...you're in your car, the screen times out and you want to make a call using voice recognition....so you have to unlock the screen and then use the voice recognition... sounds like a dangerous bug to me....serious liability IMHO
mackendw said:
think about it...you're in your car, the screen times out and you want to make a call using voice recognition....so you have to unlock the screen and then use the voice recognition... sounds like a dangerous bug to me....serious liability IMHO
Click to expand...
Click to collapse
I know, but the N4 doesn't support the neccessary hardware for this feature. Only the N6 and N9 does.
borchgrevink said:
I know, but the N4 doesn't support the neccessary hardware for this feature. Only the N6 and N9 does.
Click to expand...
Click to collapse
when I initially set it up, IT DID WORK....but then after a few hours, days (dunno for sure) it stopped. voice recognition works from google now screen, or the home page fine. something not right somewhere...
Hmm. From locked screen? Strange. Absolutely sure?
borchgrevink said:
Hmm. From locked screen? Strange. Absolutely sure?
Click to expand...
Click to collapse
there is an option in Google Now -> Settings -> Voice -> OK google detection ....a check box exists here stating:
When Locked
Allow "OK Google" to start a voice search or action from a secure lock screen
so, it would seem that this is what was intended. perhaps what they meant here was that the screen has to be on and not timed out. dunno.
Yes, but screen has to be on. Only nexus 6 and 9 support GN with screen locked and off
Google search from locked screen works for a while and then stops. It's done this on my s4 and note 3. It is defenetly supposed to work from secure lock screen. In Google now settings there is a 3rd check box and you even get a warning stating anyone may be able to unlock your phone.
Google needs to fix this issue. I'm not sure what's up with these companies making screwed up software. Where are the devs, and why are they getting paid if they can't make flawless software. When I crash My car into a tree trying to unlock my phone and I press a law suit against google I'll bet they will fix it. Always takes a law suit to fix ****.
Oh. Anyone notice every app you've ever paid for or downloaded is under my apps "all" what's up with "all" I'll file my documents in my office under the "all" folder and see how quickly I get fired...Thanks for allowing me to rant.
Happy new year!
https://productforums.google.com/forum/#!topic/websearch/xGiV6D4PMS8/discussion[1-25]
Major issue
Hey guys!!
Just got my S6 Edge and loving everything about it so far except...
My Ok Google anywhere isn't working. It's not even presenting me an option to turn it on. Also "enable audio history" option is missing which I know is necessary to get it all working.
I have done a factory reset, enabled and disabled S Voice, primary language English US, and deleted app data etc! I am running a stock Telus Samsunf S edge. I don't know if it's firmware dependent or not.
If anyone can suggest anything else, I'm all ears!!
Thanks in advance!
nvict said:
Hey guys!!
Just got my S6 Edge and loving everything about it so far except...
My Ok Google anywhere isn't working. It's not even presenting me an option to turn it on. Also "enable audio history" option is missing which I know is necessary to get it all working.
I have done a factory reset, enabled and disabled S Voice, primary language English US, and deleted app data etc! I am running a stock Telus Samsunf S edge. I don't know if it's firmware dependent or not.
If anyone can suggest anything else, I'm all ears!!
Thanks in advance!
Click to expand...
Click to collapse
Looks like they removed it I had it yesterday now it's gone there was a update last night
Ah, that's a shame. At least I'm not the only one!!
Hope they come to their senses and come out with an update to enable it again!
Yep was there yesterday and gone now.
Perhaps it was sucking too much battery? Can't say I really used it that much but it was a cool feature. Will just have to press and hold home button to use it! A bit of a pain!
Found a work around for now...
Using an app called "Now Gesture Tweaks" which allows me to press and hold the home button to activate Voice Search and Nova Launcher gesture "Swipe Up" for Google.
Gives us a similar effect.
voice your disapproval: @S6NoOKGoogle https://twitter.com/S6NoOKGoogle
Don't you guys have "google settings" in your app drawer? All "OK Google" settings are right there.
EDIT: My bad.. deep down to the detection settings, it is gone!! How!? So is this Samsung's fault or Google's fault?
Yup. It's global and it's just all the variants of the S6 & S6 Edge. Some Nexus devices seem to be broken but still have their options.
https://productforums.google.com/forum/#!topic/websearch/xGiV6D4PMS8[201-225]
I used it on a regular daily basis. Very frustrating for them to pull it without notice...
What is even more frustrating is that neither Google or Samsung is taking the heat for this,,,both are referring us to each other LOL,,,classic tactic.
SuperSport said:
I used it on a regular daily basis. Very frustrating for them to pull it without notice...
Click to expand...
Click to collapse
What if you use the Google now launcher?
jasonbiggs said:
What if you use the Google now launcher?
Click to expand...
Click to collapse
Unfortunately same, not working.
It doesn't work on my Note 2, my wife's S3, and even my coworker's Walmart Alcatel phone alll running Kitkat and all did the latest update.
Its a bigger issue and Google doesn't seem to be too concerned
I got an update yesterday and it is working now, well at least from the homescreen.
Sprint S6 Edge w/Nova Launcher, OK Google works from any screen.
Does the widget need to be on the home screen for it to work
Sent from my SM-G925F using XDA Free mobile app
Not for me
Wow, just realized I don't need the widget at all for hotword to work. Cool
supposedly the 5.1.1 update will bring the OK Google functionality back.
Is your S-Voice App activated? Or did you disable that? I've read that either having it on or off might enable OK GOOGLE from any screen to work.
rank78 said:
Sprint S6 Edge w/Nova Launcher, OK Google works from any screen.
Click to expand...
Click to collapse
Has anyone has had good luck using the mini view feature under Settings/Display/More. I got it to work once in the two months I've owned the phone. I have the display set to default 2880x1440. Is it me not knowing how to swipe or does this just not work very well?
Works fine for me. But yes, you have to practice the right swipe a few times ?
Go to Settings -> Accessibility -> Services
Check is all off
When I have Norton on mini view not working.
GhostofRonin said:
Go to Settings -> Accessibility -> Services
Check is all off
When I have Norton on mini view not working.
Click to expand...
Click to collapse
Well done! It was just one app getting in the way: Automate. I'll let him know, maybe he can find a fix.
Cheers!
I had the same issue. I turned off Amazon assistant and now it works.
Mini View Not working on LG G7
It is simply a matter of swiping VERY quickly
LG V30 mini swipe does not work
This feature wasn't working for me, but I figured out what was doing it. In my case it was LastPass, the accessibility being turned on under services in settings was the culprit. If you turn it off it works you turn it on it doesn't.
NateAtHome said:
This feature wasn't working for me, but I figured out what was doing it. In my case it was LastPass, the accessibility being turned on under services in settings was the culprit. If you turn it off it works you turn it on it doesn't.
Click to expand...
Click to collapse
Last Pass has caused other problems too. A lot of people had to ditch it. Causes lots of lag. There was even a thread about it, besides comments in other threads when this phone was first released last year.
This phone is super smooth. When people complain they have lag, I always think "Are they perhaps using Last Pass?" Or either they disabled stuff that then causes lag.
I have a problem with Smart Lock on Pixel 6.
When Trusted Locations or Trusted Devices is activated the fingerprint reader will not work properly from the lock screen.
It does not light up properly and I always have to put my thumb on it twice for it to unlock.
Have been like this since I bought it in November, have hoped that an update will solve it, but apparently not.
Have also googled a lot about the problem but can not find anyone else with the same problem, so do not really know what to do.
Does anyone else have this problem or anyone who has tips on how to solve it?
I have uploaded two videos so you can see my problem.
Smart Lock activated:
Smart Lock disabled:
My advice is to stop using Always On Display. That behavior is what was too annoying for me to bear with.
mosio said:
My advice is to stop using Always On Display. That behavior is what was too annoying for me to bear with.
Click to expand...
Click to collapse
Meow meow!
mosio said:
My advice is to stop using Always On Display. That behavior is what was too annoying for me to bear with.
Click to expand...
Click to collapse
I rather disable Smart Lock. But there must be something wrong with my unit, because other people don't seem to have the same problem.
Can someone try Smart Lock and see if they have the same problem?
P1an said:
I rather disable Smart Lock. But there must be something wrong with my unit, because other people don't seem to have the same problem.
Can someone try Smart Lock and see if they have the same problem?
Click to expand...
Click to collapse
I do have the same problem and I suspect that it may be connected to the fact that I've disabled the "forced lift to check phone" via adb before.
P1an said:
I rather disable Smart Lock. But there must be something wrong with my unit, because other people don't seem to have the same problem.
Can someone try Smart Lock and see if they have the same problem?
Click to expand...
Click to collapse
Hello P1an,
I have Smart Lock enabled with a Fitbit band and all seems to work well.
When on the lock screen, the phone is already unlocked through Smart Lock or if my fingerprint is asked, it is really fast.
ichi go said:
Hello P1an,
I have Smart Lock enabled with a Fitbit band and all seems to work well.
When on the lock screen, the phone is already unlocked through Smart Lock or if my fingerprint is asked, it is really fast.
Click to expand...
Click to collapse
Happy to hear it's working like it should for you
Could you be so kind and make two videos like I did, one with Smart lock activated and one with it disabled so I can see how it's working for you. That would be very much appreciated!
P1an said:
Happy to hear it's working like it should for you
Could you be so kind and make two videos like I did, one with Smart lock activated and one with it disabled so I can see how it's working for you. That would be very much appreciated!
Click to expand...
Click to collapse
Hi P1an!
I hope I understood correctly the issue you’re facing .
Here are my videos:
ichi go said:
Hi P1an!
I hope I understood correctly the issue you’re facing .
Here are my videos:
Click to expand...
Click to collapse
Thank you for your videos, but the second video was not really like mine.
Could you try turning off "Tap to wake phone" under lock screen settings. And then try to use the fingerprint sensor and post a video of what happens for you
Finally it's fixed with the latest update! Now Smart Lock is working like it should with Always on display.
P1an said:
Finally it's fixed with the latest update! Now Smart Lock is working like it should with Always on display.
Click to expand...
Click to collapse
Nice to hear! What update are you talking about ?
The latest system update: SP2A.220305.013.A3
Google Pixel Update - March 2022 - Google Pixel Community