yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] elmdh:
Not sure what you mean. The display sleeps after two minutes of inactivity, but when I get or make a call it sleeps immediately.

_____________

Sorry, I see now. My proximity sensor is damaged, so I need to disable it.
[Xposed Framework Modules] Vtrendzzy:
I've been using this module for a long period of time. Never had any issues. Recently, i noticed something. Whenever i get a call or make a call, there's a tiny red light that blinks continuously. Not the led notification light. Is that proximity sensor? And this module disables it then why that red light keeps blinking?
[Xposed Framework Modules] WardellBagby:
You're right; that's the proximity sensor. In the current iteration of the software, the proximity sensor isn't truly "disabled"; Android still knows that the sensor is there and it is trying to query the sensor's status. What I do is when the sensor is trying to report back to Android what it's value is, I intercept the message and tell Android that the proximity sensor is reporting that nothing is close to it.

That's why you can see the sensor blinking.

In the future, they'll be the option to make it so Android will believe that the proximity sensor doesn't exist on the device, so Android won't try to query it and you shouldn't see the proximity sensor being active.
[Xposed Framework Modules] x111:
I'm using Nexus 6 with Slim-shamu-5.1.1.beta.0.10-UNOFFICIAL-20151025-1942

and have a problem with disableprox 1.02-1.1-1.1.1 all of them slowing down my phone.

but disableprox 1.0.1 works fine.

very handy app, proximity sensor works absolutely awful under fully transparent screen protector and must be turned off.
[Xposed Framework Modules] Vtrendzzy:
And i suppose that'll save us some more battery. Good.
[Xposed Framework Modules] WardellBagby:
I had been noticing some problems with slow down with the newer versions, and they'll be an update very soon that'll alleviate those issues.
[Xposed Framework Modules] WardellBagby:
It should, hopefully. It could cause some other issues with badly coded apps that expect a proximity sensor installed, but I haven't seen any instance of this yet.
[Xposed Framework Modules] avinoamsn:
Bug with newer versions

I've been having numerous issues with my prox sensor lately, and this tool has remedied the situation. Thanks!

Nonetheless, I do have one issue of note: the latest versions of the software (1.1.0, 1.1.1) seem to inhibit the unlocking function on my device. When the module is enabled, neither pressing the unlock button nor knocking on the screen wakes the phone. Additionally, I'm unable to bring up the "power down" menu (although the force-shutoff is still functional). However, version 1.0.1 functions perfectly. My load out:

Phone: LG G2

Firmware: D80030f (5.0.2 AT&T)

Xpose framework: v79

If you do end up looking in to this, let me know if you need any more details (I'd post logs now, but can't do so atm).

Thanks again!
[Xposed Framework Modules] WardellBagby:
I believe that LG has some sort of proprietary unlocking mechanism in their devices, where it'll check the proximity sensor to decide whether or not to unlock. Source: http://www.lg.com/us/mobile-phones/VS985/Userguide/033.html

For this version, you could use Tasker support to get around it, by telling Tasker to disable the module when the screen was turned off, but assuming you don't have Tasker, the next version soon to be released will have a feature that allows you to blacklist or whitelist apps, so you should be able to get around it with that. I can't say for sure how long it'll be until that is released, though.

I'm super curious as to why 1.0.1 would work but the newer versions don't. I'll look into this for you.
[Xposed Framework Modules] avinoamsn:
LG proprietary locking mechanism

Ah, that article does explain the issue I was originally having. Nonetheless, let me know if you need anything else when looking in to the differing behavior between 1.0.1 and the recent updates. I should also mention that I haven't tested the functionality @1.0.2, so this bug may not occur on that iteration either (I'd update to 1.0.2, but now that it's working I'd rather not mess with the module). Thanks!
[Xposed Framework Modules] ddzado:
Potential Bug - VS980 - CM13 - Location Services

Love the module. My phone had been wonky with the screen while in call.

Just recently my phone started locking up. The UI was very unresponsive. Couldn't get the navigation controls to pop up while in expanded desktop mode.

From what I can tell this module and location enabled are a bad mix. What can I do to help you debug this?
[Xposed Framework Modules] Sly_North:
VS980 CM13 too here, and I get lots of reboot with the last version - 1.1.1.

Downgrading to 1.0.2, the proximity wasn't disabled anymore.

I'm now testing with 1.1, I think there's something wrong with the new UI in 1.1.1, as I got some visual glitches before the crashes with 1.1.1: sometimes the home button was disappearing, and sometimes the status bar got transparent.

All these issues disappeared when disabling this module and rebooting.
[Xposed Framework Modules] gseror4:
Random Reeboots Nexus 6 6.0 (MRA58K)

I keep getting random reboots on my nexus 6 and I'm pretty sure that this module is the cause. It's the only module I have installed and I don't see why the framework itslef would cause it (it may but I don't know). Anyway I recorded a logcat up to the point of a random reboot and I attached it here. I don't know how to read a logcat really but hopefully one if you can and can maybe give a clearer answer as to the causehttps://drive.google.com/file/d/0B4z2IjSbR7ADSkxzVWZYbWM1Q0E/view?usp=docslist_api
[Xposed Framework Modules] Sly_North:
Heh I got so sick of these random reboots with CM13 that I fixed my proximity sensor. In my case it was a space between the black caoutchouc and the screen.

Still, thank you for the year this module was helpful.
[Xposed Framework Modules] Molitann:
Not working on official 6.0 on LG G3, was previously working on 5.1.1
[Xposed Framework Modules] franciscoO:
it works fine here. thanks ^^

Device: lg g2

ROM: cloudyg2 3.3 (5.0.2)

Kernel: dorimanx

and Xposed.
[Xposed Framework Modules] tnhh:
I get continual reboots with 1.1.1, but 1.0.2 seems to work. Xperia Z3C on Lollipop 5.1.1.
[Xposed Framework Modules] mmd1907:
Thank you for this useful module. Working fine for me.

LG g2 / cm 13

Version 1.1.1
[Xposed Framework Modules] Pigeon Flipper:
hltespr - Note 3 - AICP 10 ROM (CM 12.1 base)

1.1.1 no work. Skipped 1.1, 1.0.2 works fine. Thanks
[Xposed Framework Modules] cembellines:
Reboots all the time with the last version. I have a Note 2 with CM12. Thanks for the module tho, hope it can be fixed because it used to be very handy
[Xposed Framework Modules] cembellines:
Thanks, you are right
[Xposed Framework Modules] Pigeon Flipper:
Thank him below as I was following his advice.

Thanks mate!
[Xposed Framework Modules] yomoney:
Crashes when opening interface

Lg g2. I've been using this module since I found it a yearish ago. I downgraded to the previous version without an interface because it crashes Everytime I try and open it. Works fine with previous version. I could figure out how to upload a log if that would help. I'm surprised nobody else had had this issue. My framework is properly installed all my other module work.

Edit. I have no problem at all using the previous version. Proximity disable it's all I need. I was just curious about new settings.
[Xposed Framework Modules] WardellBagby:
Hmm. There might be a problem with the upgrade script. Try clearing the data after installing 2.0? Thanks for bringing this to my attention.

Out of curiosity, are you on a Kitkat or lower device?
[Xposed Framework Modules] yomoney:
I'm running 4.4.2 no Rom.

Updated. Cleared cache and data. Still same issue. "Unfortunately, sensor disable failed to open"

Edit: if the new version doesn't work with my android version there no need to put time into it. I don't need any additional features. Proximity disable is one of my favorite modules though.
[Xposed Framework Modules] WardellBagby:
I see the issue and it's not a difficult fix. Just me forgetting to test against <5.0 again.

Expect an update in a few hours. But still, feel free to stick with the old version. However, if you've been having some issues with the old versions (device slowdown and other weird issues) the 2.0 version should fix that.
[Xposed Framework Modules] yomoney:
Works now.

Another small bug is when I open it it is automatically In amd sensor settings. The back button when you are in any of the sensor settings (amd for example, or proximity settings) rather than going to the main menu it exits the app.
[Xposed Framework Modules] phantom146:
Hi! Havent tried the app yet but before i do i just wanna clear things out..

If i disable motion sensor.. Will it disable "doze" on MM trying to check motion sensing as well? As per say.. Will this mean that my doze wont go off on significant motion? Thanks!
[Xposed Framework Modules] WardellBagby:
Hmm. I can't say for sure, but possibly. Might as well give it a go, see if it works! If it doesn't, I'll see what I can do.
[Xposed Framework Modules] xDaaexplorer8:
thanks so much so saved me
[Xposed Framework Modules] cembellines:
Im afraid to update my version...
[Xposed Framework Modules] aillez:
I have some terrible issue with my gyroscope sensor on my note 3 (on CM 12.1 rom) which don't have app to calibrate my gyroscope (in Stock ROM have it)

so I want to use your app to fix my Gyroscope drift problem and after play it awhile I finally found a parameter to set it to as zero

but in mock sensor values is a fix value right ? after try to rotate my phone to see how gyroscope values changing it's stuck as zero.

my question/request feature is

Can you implement feature to initial mock sensor values and still let input from sensor to use value after it's combine together ?

I'm not sure that you understand me or not (sorry for my english)

e.g. my gyroscope value start with this value (which is suppose to near to zero)

x = 6.32 y = -41.80 z = -1.36

and use your app to mock initail value to combine with it

x = 6.32 - 6.32 = 0 (from your mock value) y = -41.80 + 41.80 = 0 (form your mock value) z = -1.36 + 1.36 = 0 (from your mock value)

and after rotate my phone new value from sensor will change from 0,0,0 to something like 4.1,30.5,6.1 (from phone movement)

I hope you can understand me T__T

thank you in advance.
[Xposed Framework Modules] Slosh3719:
I tried to install 2.0.1 on a LG G2 D801 version (5.0.2) and got caught in a bootloop. The G2 would attempt to optimize apps, but always freeze at the starting apps area. I tried clearing the caches and that did not fix the issue. I have disabled the module and my phone is working again.

Would another older version work or is there other information I can provide to try and help figure out why the Sensor Disabler is not working on my G2?
[Xposed Framework Modules] WardellBagby:
Yes, there is. After you reboot and you get the boot loop, post the error.log file that Xposed Installer has as an attachment here. It's located in /data/data/de.robv.android.xposed.installer/log/error.log and also error.log.old.

You're going to have to do it via recovery, but TWRP has MTP support in recovery now so you should be able to just transfer them to your computer from recovery.
[Xposed Framework Modules] Choubix:
Hi,

I have a z ultra on cm12

The proximity sensor went bonkers a few months ago after updating Ota. I did a fresh install: same problem.

Basically the screen is black whenever I make/receive a call.

The only workaround is to plug my earphones in the phone then I can use the screen while in a call.

I installed your app but after activating it in xposed and rebooting I have a message saying that the app has stopped working. How could I fix this so that my proximity sensor is turned off?

Thanks!
[Xposed Framework Modules] alphatestr:
I have disabled some sensors and realized that QuickPic (photo gallery) which normally rotates landscape on tilt stopped working. I have tried to "do nothing" on rotation, gravity and gyroscopic sensors without luck. Does anyone know what to undo? Or should I just do a wipe on the mod?

Thanks
[Xposed Framework Modules] Doc_cheilvenerdi.org:
Motorola Moto E & Marshmallow 6.0.1

Proximity Sensor working fine here (:D):

Motorola Moto E xt1021 (condor);

AOSP-CAF Marshmallow 6.0.1

Xposed Framework V82 SDK23

Great Work!
[Xposed Framework Modules] gresziu:
Hi, I tested your app to disable the proximity sensor on Samsung galaxy mini s3, CyanogenMod 11 (Android 4.4.4) and isn't working.

Just letting you know.
[Xposed Framework Modules] jawz101:
Every time I click on significant motion setting the app crashes
[Xposed Framework Modules] tmacher:
Android 6.0 stock Moto g disabling magnet sensor don't work.
[Xposed Framework Modules] h4cxxc0r3:
Always got random reboot whenever this module activated on my Stock ROM Xperia Z Ultra 5.1.1 with xposed v78
[Xposed Framework Modules] zeratos:
Use the 1.1.1 version, the latest one causes boot loops and app crashes.
[Xposed Framework Modules] ingtomy:
Blacklist call app

Hi everyone!

I've read most of the thread and I can't find the answer to my problem...

I've had a serious battery leak caused by the Proximity Sensor, which I've fixed installing this beautiful app, blacklisted WhatsApp (for hearing audios in private) and the Dialer (for enabling the screen lock during calls), and disabling the sensor for everything else.

So far, so good... in theory. The reality is that I can't manage to allow the phone to lock the screen using the Proximity Sensor when I put it in my ear, leading to phone overheating and crazy battery usage (I talk a lot...).

I got a Samsung Galaxy S2 i9100 (intl), with CyanogenMod 12.1 (Android 5.1.1). I've only set the Proximity Sensor to disable and Blacklisted this apps (only for that sensor):

Dialer

In-call Interface

Phone (with no themed icon)

Phone (whit themed icon) (I use Whicons)

WhatsApp (it's working fine with this one)

Anyway... What I'm doing wrong? I have to blacklist another app? It's even possible to do what I want?

For what I've read in the thread most of the people wants the exact opposite for what I want to do, is that right? In that case, this app works fine! :good:

Thanks all, and special thanks to the developer! :highfive:
[Xposed Framework Modules] jawz101:
I'm confused by the whitelist and blacklists functions because they are the opposite of what they should mean.

This app is called Sensor Disabler, so it disables sensors.

The blacklist allows you to exclude apps from being affected by this module. Shouldn't the "blacklist" be labeled "whitelist?"
[Xposed Framework Modules] S0bes:
[MENTION=5535147]WardellChandler[/MENTION] , Hi, could you please clarify to me a few things?

I saw in the description the line "allows you to disable and modify the values for all the sensors available in your phone".

I can't install and test your module right now but I have to know does the module able to forbid light sensor give values lower then 10 lux?

I need the light sensor in my phone to provide data to other programs (including android system) only in range 10-10000 lux instead of 0-10000 lux. Can your module do such a thing? If it doesn't can you help me with that? I know a bit about xposed programming and I read through the files android.hardware.Sensor.java (SensorManager.java, SensorEventListener.java, SensorEvent.java) but don't really know how to replace light sensor data (values[0] if I understood right)

Thanks in advance

upd

looked at your source code... still don't know what exactly should I do :(

does this code seems legit regarding my problem?

package com.s0bes.redmi.light.fix;

import de.robv.android.xposed.IXposedHookLoadPackage;
import de.robv.android.xposed.XC_MethodHook;
import de.robv.android.xposed.XposedBridge;
import de.robv.android.xposed.XposedHelpers;
import de.robv.android.xposed.callbacks.XC_LoadPackage.LoadPackageParam;

public class XposedMod implements IXposedHookLoadPackage {

@Override
public void handleLoadPackage(final LoadPackageParam lpparam)
throws Throwable {
ChangeSensorValues(lpparam);
}

private void ChangeSensorValues(final LoadPackageParam lpparam) {

XC_MethodHook mockSensorHook = new XC_MethodHook() {
@SuppressWarnings("unchecked")
@Override
protected void beforeHookedMethod(MethodHookParam param)
throws Throwable {

int type=(Integer) param.args[0];
float[] sensor_values=(float[]) param.args[1];

if ((type==5 ) & (sensor_values[0]<=10)) //type 5 - LIGHT_SENSOR afaik
{
XposedBridge.log("SOMETHING WORKS!");
XposedBridge.log("type= "+ param.args[0]);
XposedBridge.log("values= "+ param.args[1]);

sensor_values[0]=(float) 10;
param.args[1]=sensor_values;
}

}
};
XposedHelpers.findAndHookMethod("android.hardware.SystemSensorManager$SensorEventQueue", lpparam.classLoader, "dispatchSensorEvent", int.class, float[].class, int.class, long.class, mockSensorHook);
}
}
[Xposed Framework Modules] shayraz:
Does not seem to work on any sensor except proximity on Note 4 N910U 6.0.1.

When disabling proximity sensor it works, phone screen doesn't go off when making a phonecall and something is placed near the sensor.

When disabling all other sensors like motion, this has 0 effect. dumpsys deviceidle step still shows the phone is checking constantly the motion and location sensors.
[Xposed Framework Modules] rbrandser:
This app is great, it has saved my devices from the dump. Nothing more annoying that fked proximity sensors!

I use it on both my Nexus 6 and my Z2.

The only issue it causes, that I've noticed; my devices crash and reboot while playing blossom blast saga ?
[Xposed Framework Modules] Flipz77:
Proximity sensor unaffected by this module on moto x2 stock 6.0
[Xposed Framework Modules] louislelu:
Hello !

I have a LG G2 in 4.4.2.

I just rooted it.

After this I installed xposed and his framework.

Then I downloaded the app => Xposed sensor disabler

In the app i went to "proximity" and checked "remove sensor" and clicked on the save button. I reboot the phone.

But the sensor is still working.

Basically my problem is that after changing the screen of my phone with apparently a ****ty one, the proximity captor doesn't work anymore and seem to see everything "near". That means that when i call someone, it stays Black all the time even if in don't have my ear on it anymore etc.

Have I done something wrong ?

Thank you

Louis.
[Xposed Framework Modules] Gio Lokks:
so I have the Samsung Galaxy s6 edge and there's games that are still reading sensors like bowling king does the freeloader button work or do I still have to purchase to get it to work?
[Xposed Framework Modules] koemski:
Crash when setting mock values

Hello!

When I try to set mock values for the proximity sensor, the app crashes (log's here: http://pastebin.com/f4N7fj2K). I first choose "Mock sensor values" radio button, then move the slider. When I release the slider, the app crashes.

Greetz, koem
[Xposed Framework Modules] Kloosek:
I try disable Significant Motion Detector, select "Remove sensor" and when I try to re-enter the sensor option, the app crashes.
[Xposed Framework Modules] DIXES:
Is it possible to make Pokémon Go always into battery saver mode (it needs phone upside down)? Which value(s) should I try it? Thanks.
[Xposed Framework Modules] starbase64:
Please add live sensor data in settings.
[Xposed Framework Modules] MrHaroldA:
Any chance of disabling my broken proximity sensor on Android 7.x? Seems like Xposed is far from finished for Nougat.
[Xposed Framework Modules] sweetmyke:
If you find a solution to this please let me know. I've been all over google and tried every app with no luck. This is the only thing that helped my situation, but like you I'm on android 7
[Xposed Framework Modules] Blackwolf14:
Hi, I have a LG G2 D800 (4.4.2). I installed Sensor Disabler (2.0.1) and I disabled the proximity sensor but when I call any number, phone is locked.
[Xposed Framework Modules] aikon96:
For all who have a broken proximity sensor and can't use this module or have freezes using this Modul, like me:

go to BUILD.PROP and add the following line:

ro.qti.sensors.proximity=false

then reboot and enjoy!
[Xposed Framework Modules] RawSlugs:
Running stock Android 6.0 tried disabling proximity sensor for WhatsApp but it does not seem to be working tried both disable and mock WhatsApp is on whitelist with proximity selected

Screen still goes black when listening to voice notes then...
[Xposed Framework Modules] bullracing:
Not working, tried on a Nexus 5 Android 6.0.1
[Xposed Framework Modules] sweetmyke:
Proximity fix without xposed

Forgot the original thread but here's a fix without xposed
[Xposed Framework Modules] tawaryeehaw:
just flash it on twrp?
[Xposed Framework Modules] setheleh:
I am having random reboots even i remove or mock. Mi5s global developer. My fking proximity sensor not working thats why i am using this module thx so much by the way...
[Xposed Framework Modules] DavidMelb:
THANKS!

Thanks [MENTION=5535147]WardellChandler[/MENTION] works well on Samsung S4 i9506 running LineageOS 13 :good:
[Xposed Framework Modules] ks123:
Hi, i have a Samsung Galaxy Note 3 (HLTE) running Phronesis v7 (dirty flashed new versions since ages ago)

My problem is that after a while (or a trigger i did not find yet) some of my sensors (pressure,orientation, sometimes others as well) do not work anymore until the next reboot.

Once i played around with sensor self test apps etc. and i had the impression that one sensor did work again.

I would like to avoid Xposed since it (or one of the modules or just me) made my system less stable last time.

Is there something like a sensor-reset (without the need for a reboot)?
[Xposed Framework Modules] OmTatSat:
Hello, can you get it worked in android 7? I will be glad to be betta tester. I need your app becouse my accelerometer show 5% tilt, and I want to fix tilt with your app. Is it possible?

I have Huawei G9 Plus, (Nova Plus)

I can run some terminal commands if you need it to get work in android 7 and post results.
[Xposed Framework Modules] lung1:
hi!

Anything about this crash? This is on Android 7.1.1

com.google.android.gms.persistent E/Xposed: java.lang.ClassCastException: java.util.HashMap cannot be cast to android.util.SparseArray

at com.mrchandler.disableprox.XposedMod$2.beforeHookedMethod(XposedMod.java:96)

at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:319)

at android.hardware.SystemSensorManager$SensorEventQueue.dispatchSensorEvent(<Xposed>)

at android.os.MessageQueue.nativePollOnce(Native Method)

at android.os.MessageQueue.next(MessageQueue.java:323)

at android.os.Looper.loop(Looper.java:136)

at ampj.run(:com.google.android.gms@11530430:1)
[Xposed Framework Modules] hany0u:
I was so happy to have found a solution but it did not work.

Nexus 6p / 7.1.2
[Xposed Framework Modules] MrHaroldA:
So, we now have Xposed for our 7.1 devices! Too bad this Xposed module doesn't work, or at least not for removing the proximity sensor ...
[Xposed Framework Modules] darkdoll69:
Please help me. I upgrade my my N5 to nougat now sensor disabler is not working. Please any solution...
[Android Q&A, Help & Troubleshooting] dexterrio14:
My phone is rooted and i was modifying something in the system file then i accidentally deleted the entire system file of my phone.. My phone turned off after ive deleted and when i tried to turn it on it is stuck on boot..or the logo of my phone.. Can anyone help me recover the system file of my phone or the operating system i may say.. I have tried the android system recovery 3e and wipe/factory set my phone but still stuck on boot..im using cherry mobile flare 2.1 running on android jellybean 4.1:crying:
[Android Q&A, Help & Troubleshooting] emanuelrv:
you have to flash the same rom with a custom recovery you kill you android
[Android Q&A, Help & Troubleshooting] dexterrio14:
. Could you please tell me in details what steps should i do in order to flash the same rom.. Thanks..i really needed to get my phone back:crying: