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!
The text in app screen is interchanged.
cause it shows visible to Perceptible apps and when I exit from app it shows Perceptible.
I think only names are interchanged there is no change/ problem in functionality of app.
In 1. you can see that internet speed meter is running and Greenify shows as visible
when I close the app in part 2. it shows Perceptible
This bug present only in Lollipop
bhavin192 said:
This bug present only in Lollipop
Click to expand...
Click to collapse
That is because Xposed is not yet compatible with Lollipop. It is not a bug.
tnsmani said:
That is because Xposed is not yet compatible with Lollipop. It is not a bug.
Click to expand...
Click to collapse
Then why it shows correctly on non rooted KK device.
and only texts are interchanged, functionality of app is still perfect.
bhavin192 said:
Then why it shows correctly on non rooted KK device.
and only texts are interchanged, functionality of app is still perfect.
Click to expand...
Click to collapse
Whether rooted or not, Greenify runs perfectly on Kitkat. It is Xposed which requires root and Xposed increases functionality of Greenify.
When an app is not made for or is not compatible with an OS, then what will work and what will not, can not be predicted. It may not work totally or some features may work or some parts of the app may be skewed as in your case.
I installed xposed on my nexus 6 and have the greenify module enabled in xposed. How ever, once I go to greenify settings and enable some xposed feature it will give me a pop up about activating the module + rebooting. It is already activated.. the reboot didn't help as well.
Any ideas?
Thanks
Yes, greenify for 5.0 is still in beta for now, you just have to access the beta, download, and it will work fine
Tapatalked from my D802 - BlissPop 2. 1
Utini said:
I installed xposed on my nexus 6 and have the greenify module enabled in xposed. How ever, once I go to greenify settings and enable some xposed feature it will give me a pop up about activating the module + rebooting. It is already activated.. the reboot didn't help as well.
Any ideas?
Thanks
Click to expand...
Click to collapse
I had the same issue with 2.6 beta 6 that was pushed today. Hopefully there will be a quick bug fix, but in the meantime I went back to 2.6 beta 5. http://www.apkmirror.com/apk/oasis-feng/greenify/greenify-2-6-beta-5-android-apk-download/
EDIT: no need to downgrade, 2.6 beta 8 is out and fixes the issues in beta 6
amd_h4x0r said:
I had the same issue with 2.6 beta 6 that was pushed today. Hopefully there will be a quick bug fix, but in the meantime I went back to 2.6 beta 5. http://www.apkmirror.com/apk/oasis-feng/greenify/greenify-2-6-beta-5-android-apk-download/
Click to expand...
Click to collapse
Well I am running 2.5.2 from the play store?
Utini said:
Well I am running 2.5.2 from the play store?
Click to expand...
Click to collapse
You'll probably have to opt-in to the Greenify beta as Wycer mentioned above to get the latest for Lollipop.
amd_h4x0r said:
You'll probably have to opt-in to the Greenify beta as Wycer mentioned above to get the latest for Lollipop.
Click to expand...
Click to collapse
Oh alright... Well I wilk wait for the google play release
Maybe I csn follow up with another xposed question? I installed blacklist in xposed and it blocks phone calls. However sms aren't getting blocked. I grt a notification from blacklist that a sms was blocked but the sms still comes through?
Thanks
Utini said:
Oh alright... Well I wilk wait for the google play release
Maybe I csn follow up with another xposed question? I installed blacklist in xposed and it blocks phone calls. However sms aren't getting blocked. I grt a notification from blacklist that a sms was blocked but the sms still comes through?
Thanks
Click to expand...
Click to collapse
You have to opt-in on Google+ to get access to the beta channel on play.
Hey
Was wondering what's the chances of building Greenify to use GCM push without the need of Xposed? I've been running Greenify for a long time now, but since Samsung pushed Lollipop, Xposed module no longer works with samsung lollipop roms. At this moment, it looks like the new Art system is causing trouble and the dev of Xposed isn't promising it will ever work.
For me, I paid for Greenify, was hoping there will be a solution in the future. I do understand it might involve a whole recoding.. But looking to see what's the possibility.
twe90kid said:
Hey
Was wondering what's the chances of building Greenify to use GCM push without the need of Xposed? I've been running Greenify for a long time now, but since Samsung pushed Lollipop, Xposed module no longer works with samsung lollipop roms. At this moment, it looks like the new Art system is causing trouble and the dev of Xposed isn't promising it will ever work.
For me, I paid for Greenify, was hoping there will be a solution in the future. I do understand it might involve a whole recoding.. But looking to see what's the possibility.
Click to expand...
Click to collapse
First of all, you didn't exactly pay for the App per se, you DONATED to the Dev to get Extra "Experimental" features, quite different you know
Second, the Dev of Greenify can't further develop the App without Xposed being Stable for Lolipop, and Xposed is still at Alpha-Stage, not even Beta, so you either wait patiently for an update, or start to search for alternatives, or go back to KitKat and have everything working :good: :victory:
-m3ta- said:
First of all, you didn't exactly pay for the App per se, you DONATED to the Dev to get Extra "Experimental" features, quite different you know
Second, the Dev of Greenify can't further develop the App without Xposed being Stable for Lolipop, and Xposed is still at Alpha-Stage, not even Beta, so you either wait patiently for an update, or start to search for alternatives, or go back to KitKat and have everything working :good: :victory:
Click to expand...
Click to collapse
Yes that is true that donated vs paid is a different term. But you get the point.
As far as your second part, doesn't directly answer my question. Samsung TW Lollipop isn't supported by Xposed and the Dev doesn't know if it will ever work.
I try to use without exposed but there are many difference ?
Tk
MrPingle
misterpingle said:
I try to use without exposed but there are many difference ?
Tk
MrPingle
Click to expand...
Click to collapse
yes. if you install it without exposed you will see that a majority of functions do not work. go to the settings tab to see
Disable restricting Android API to get recent tasks in Lollipop and newer. This restriction causes that some apps (e.g. Greenify) don't work as they should, since Android now returns nothing or useless info when they want to get recent tasks. This module should fix it as it was before.
http://repo.xposed.info/module/com.pyler.unrestrictedgettasks
Thank you! Switchr now working on Lollipop with this!
Double thanks to @pyler to bring back recent task usable again....
Sent from my SM-N910G using Tapatalk
chaimc said:
Thank you! Switchr now working on Lollipop with this!
Click to expand...
Click to collapse
Oh yeah!! You're the man pyler
pyler said:
Disable restricting Android API to get recent tasks in Lollipop and newer. This restriction causes that some apps (e.g. Greenify) don't work as they should, since Android now returns nothing or useless info when they want to get recent tasks. This module should fix it as it was before.
http://repo.xposed.info/module/com.pyler.unrestrictedgettasks
Click to expand...
Click to collapse
Does it work with 5.1.1 superalpha xposed?
Thanks dev.. More wisdom. Work great on lollipop
Sure, it works on any Xposed build for 5.0,5.1.
Thanks a ton dev, working smoothly [emoji106]
Sent from my YU5010 using Tapatalk
Would I need this with a nexus 5 with greenify and amplify?
Xenonhd rom
Imho the app developers should update their apps. There are new permissions like PACKAGE_USAGE_STATS. I checked wiht an M emulator my apps (non-xposed & non-root apps) TaskManager and KeepRunning and they still work without this module
defim said:
Imho the app developers should update their apps. There are new permissions like PACKAGE_USAGE_STATS. I checked wiht an M emulator my apps (non-xposed & non-root apps) TaskManager and KeepRunning and they still work without this module
Click to expand...
Click to collapse
Is that a yes or no?
PackageUsageStats is not same as getRecentTasks. I doubt you can get same info from PUS as in getRecentTasks in pre-LP.
Hi,
May I ask what you mean by giving the example of Greenify? What exactly is the shortcoming with Greenify in L in contrast to pre-L?
I was following their change logs and it seems to me that there is nothing Greenify nowadays couldn't do in L. What am I missing?
I am just asking, because I am not sure why and whether I should install this module as a Greenify (beta) user.
Wouldn't it be easier to introduce your fix in their own code?
Modify module to work for only one app?
I'm wondering how I could modify this module to make it so that it only works for one particular app (Last App Switcher). I like the idea of Android preventing third party apps from getting my recent app details, but I also miss using LAS.
I'm thinking that in the call to XposedBridge.hookAllMethods() I could replace the third argument XC_MethodReplacement.returnConstant(true) with a instance of XC_MethodHook that checks the calling app's package name and if it matches the package I want to target (com.abhi.lastappswitcher) then it would return true, otherwise it would call the standard Android isGetTasksAllowed function normally. I've never done any Xposed development though so I'm not sure I'm going about it the right way.
Hi @pyler,
Is this module still needed in Android M for apps like Greenify?
Thanks
Phil
Droidphilev said:
Hi @pyler,
Is this module still needed in Android M for apps like Greenify?
Thanks
Phil
Click to expand...
Click to collapse
I want to know that too
Anymore info on this? Im on g900i lolipop.
Sent from my Samsung Galaxy S5 using XDA Labs
Needed for Marshmallow? Thx
Sent from my lightning fast SM-G930F (S7)
No, since many devs already use new APIs.. If you have old app, not updated for LP/MM, this maybe needed for full app functionality.
A fantastic module, some apps still require this to work, an app from myself for myself for example: RAMTool https://tiziocaio.store.aptoide.com/app/market/com.thepriest.andrea.ramtool/1422/22796519/RAM+Tool
Since my app analyzes recent and running apps and on a regular interval, I fear that using UsageStatsManager will degrade performance, I am afraid that the cpu will be more stressed.
Rewriting my code to get worse perfornce than before doesn't make me happy ...that's probably the reason i hadn't yet wrote it.
Are my fears unfounded?