Related
I've been trying to pour through the API and find a way I can access and disable the proximity sensor with some code, but have been unsuccessful.
Does anyone know of a way, rooted or unrooted, that I can disable the proximity sensor completely?
I searched the forums and the only ways I found seem applicable to WinMo based phones.
Heck, I'll pay for a way to do it, I hate the proximity sensor that much.
Even if someone knows of a way I could disconnect it by opening my phone, I might even spring for that - but obviously a software approach would be much more appreciated...
Thanks!
redball said:
Heck, I'll pay for a way to do it, I hate the proximity sensor that much.
Click to expand...
Click to collapse
Why do you hate it, if I may ask?
larsrya8 said:
Why do you hate it, if I may ask?
Click to expand...
Click to collapse
It is unreliable, and I know it isn't just my phone because a number of people I know also have an HTC Incredible and it seems to behave just as erratically on theirs.
Based on the code I read through for Phone.apk or whatever, it seems like it is supposed to disable the proximity sensor when you're using bluetooth, just like when using the speakerphone - but it doesn't. I can't figure out why, and I noticed another thread floating around with users having the same issue.
I want to be able to use my phone while on a call and not have to worry about a shift in overhead light or something passing over the sensor and flipping the screen off while I'm trying to use it.
I would much prefer the ability to disable it entirely, and have full control of the screen off/on using the power button.
There was one app on the app store recommended in my searches that let's you lock the screen on and only go off based on orientation or something, but it doesn't seem to work for the HTC Incredible
Try screebl? Should keep your phone on based on orientation, I think even during a call? Not sure though.
Sent from my ADR6300 using XDA App
drawde said:
Try screebl? Should keep your phone on based on orientation, I think even during a call? Not sure though.
Click to expand...
Click to collapse
I tried Screebl, too...but unless I'm configuring it wrong - it doesn't seem to work while in phone calls.
I hate it too. Makes my screen turn on and off when I use my bluetooth.
Sent from my HTC Incredible
I'm right there with you on this. I really hate being on a call and having the screen turn off and have to shake the phone around to be able to end the call.
JTCGiants56 said:
I'm right there with you on this. I really hate being on a call and having the screen turn off and have to shake the phone around to be able to end the call.
Click to expand...
Click to collapse
That's the worst! It's like it gets doubly worse just when I want to be able to hang up.
If it helps anyone...I found these links. (If you google for "mProximityWakeLock", and follow the first Stack Overflow link, it also has two links in it to PhoneApp.java and InCallScreen.java)
I tried making an app that just kept calling release(), but it ended up just creating force closes.
you guys should email HTC so t hey fix it in the next OTA.
I know this is not really about droid, but what proximity sensor also does is scale down CPU speed (even despite using setcpu) making Skype completely useless without a headset.
When you initialize a call - everything is cool.
If you hold your phone on your hand and use loudspeeker - it's cool.
As soon as you put it to close to your face/ear - not cool anymore. To the point where it's absolutely impossible...
Cheers!
It does check for a headset plugged in, bluetooth audio or the speakerphone enabled. For bluetooth, it gets a code from a getState method. It only prevents the screen from turning off if it equals a specific state. All you have to do is force it to always be true.
You can also put this in the build.prop to completely disable it.
Code:
gsm.proximity.enable=false
How i do this?
ihtfp69 said:
It does check for a headset plugged in, bluetooth audio or the speakerphone enabled. For bluetooth, it gets a code from a getState method. It only prevents the screen from turning off if it equals a specific state. All you have to do is force it to always be true.
You can also put this in the build.prop to completely disable it.
Code:
gsm.proximity.enable=false
Click to expand...
Click to collapse
I m a nerd....how i do this ? where i write this code in my htc desire?
Thanks
1. you need to be rooted (if your on this forum and running miui you already are rooted) and have ES File Explorer downloaded from market.
2. open es file explorer and press menu then settings scroll all the way to the bottom and go to root options & turn on root explorer & mount file system
3. go back to the view of your sd card now on the top left there is a image of sd card click that. look for a folder named system and click there
4. in system scroll to bottom and look for a file called build.prop long press on this file and click copy now click the house at top left and paste the build.prop to your sd card
5. now go back to the system folder click on build.prop and you will get a selection of apps to pick from depending on what you have installed. pick es note editor
6. now that you in your build.prop scroll down and WHERE i put "gsm.proximity.enable=false" ? i write this code where? in the end? Where?
Thanks
I need Help please
i need help in
http://forum.xda-developers.com/showthread.php?p=15689458#post15689458
Quick fix
I had a similar problem with my phone (Samsung Galaxy S2) when I put it in a waterproof box. The display went black when someone was calling, and it didn't reappear unless I opened the box and thereby deactivated the proximity sensor reading.
My quick fix is to put a piece of black electrical insulating tape over the sensor. Since the sensor basically is a light sensitive receiver looking for tiny reflections from a coded light source, total blackness will be read as "no near object".
But of course, a nice API call would be more elegant
For the love of god, bump!
Bump....seriously.....I've been looking everywhere for a way to disable proximity sensor. I wish Tasker had a simple Disable/Enable toggle on this sensor
Follow the post at the top of this page.
Make a backup of your rom just in case.
In summary, if you have root explorer then here's how I'd do it.
1. Navigate to /system.
2. Click the button at the top that says Mount R/W.
3. Open the file called build.prop.
4. At the bottom of the file add a line that says:
gsm.proximity.enable=false.
5. Hit menu, save and exit, reboot
It should work. If it doesn't you still should be ok. If unsure go ahead and restore your backup.
have the same problem but with incredible s. the screen goes down until on other end some body will not put the phone down! iv trued the false method. it did nothing.
Disabling Proximity Sensor works!
ihtfp69 said:
It does check for a headset plugged in, bluetooth audio or the speakerphone enabled. For bluetooth, it gets a code from a getState method. It only prevents the screen from turning off if it equals a specific state. All you have to do is force it to always be true.
You can also put this in the build.prop to completely disable it.
Code:
gsm.proximity.enable=false
Click to expand...
Click to collapse
For all those who are looking for a solution to a faulty proximity sensor and nothing else works, I can tell you that modifying the build.prop as described does work!
I simply can now press the button to turn the screen on or off while on call instead of relying on faulty sensor. Very pleased.
This was done using HTC WILDFIRE S a510a running HTC Sense GingerBread 2.3.3 which has been rooted with CWM root through CWM custom recovery installed after unlocking the bootloader at the HTCDEV site. The program used was called Rom Toolbox Lite and I used the "build.prop Editor" feature to safely make the modification to the file.
Hello everyone,
While I was testing my phone and pressing everywhere, I might found a feature I didn't read anywhere.
I know there is the ZenMotion, and it works great. By writing a "C" on the screen, you launch the camera app. But I don't talk of that (and I disabled this shortcut)
After locking the screen, press the volume button twice (down-down, up-up or even up-down and down-up). It launches also the camera app.
This isn't a ZenMotion feature (I disabled everything and the shortcut still works).
Is someone having this shortcut too? Did someone know how to disable the shorctcut?
matias49 said:
Hello everyone,
While I was testing my phone and pressing everywhere, I might found a feature I didn't read anywhere.
I know there is the ZenMotion, and it works great. By writing a "C" on the screen, you launch the camera app. But I don't talk of that (and I disabled this shortcut)
After locking the screen, press the volume button twice (down-down, up-up or even up-down and down-up). It launches also the camera app.
This isn't a ZenMotion feature (I disabled everything and the shortcut still works).
Is someone having this shortcut too? Did someone know how to disable the shorctcut?
Click to expand...
Click to collapse
The setting for the double click volume key to launch camera from sleep is in Settings -> Lock Screen
At least on the US version running the WW firmware. See attached image.
Ohhh. Got it. The setting is here.
Thanks!
I recently switched over to this phone from a Note 8. I've been happy with it except I don't use the Google Assistant. It's not entirely useful for me and I miss being able to remap the Bigsby Button on the Note 8, so I looked for a method of trying to remap it on the LG V50. I found this thread by cavalloz which used Tasker to remap they key, so all credit goes to him. I figured I would let you guys know about it, and then lay out a tutorial-like post in case some people needed more guidance.
First, you will need to disable the google assistant. Settings->General Tab-> Apps & Notifications->Default Apps->Assist & Voice Input. At the bottom, I turned off the open assistant (one press), talk to google (two presses), show visual snapshot (three presses). I have not tested to see if you can disable only the first button press method, because I don't use any of them, but you can try it because I know some of you like Google Lens.
Second, you will need Tasker. It is a paid app, but I feel like it is well worth it for what it provides.
Third, you will need to give Tasker some permissions. You can follow this guide they provide here.
Once Tasker has been closed, you can disconnect your phone from the computer, and then reopen the app. In the Profiles Tab, click the plus button at the bottom to create a new Event in the dropdown menu.
You will need to select System->Logcat Entry, select No in the popup, and you should have an Event Edit screen that says Output Variables, Component and Filter. Click the little magnifying glass icon, grant permissions for writing over other apps, and select OK in the Tasker pop-up.
Now try to be quick to minimize what is captured, but click the orange floating play-button on your screen to start recording, and press the assistant button. Then press the orange button again(now a square) which will stop recording. Tasker will pop-up again, and you will be given a panel containing everything that was recorded, including a response to you pressing the assistant button. In the filter text box field, start typing InputReader and the panel will be reduced to the relevant 'key events' we need.
It should read like
Code:
InputReader: Key event: device=4 type=0x0001 value=0x00000000 when=2087698767908
with the numbers being dependent on your phone (I think).
Select one of the events in the pop-up panel, and it will be loaded into the filter portion of the previous Event Edit screen. You should only keep
Code:
device=4 type=0x0001 value=0x00000000
in the filter text-field.
Click the back arrow in the top left-hand corner of the screen. You may get a small little box next to the new entry New Task +. Click it, and just click the check mark of the small box that appears at the bottom.
Now in the Task Edit panel, you should be able to click the plus button and add a response to the button press. I used Alert->Torch to toggle the flash-light. In the Action Edit panel, you should be able to change the action from Off to Toggle. Click the back button in the top-left again
Your button should now be able to toggle the flash-light. Let me know if this has worked for you guys. You could get more advanced and set it up for single press, double press, hold, etc.
Any other app than Tasker that can be used? Can it be used with force widemode application
I am only able to get this to work with the screen on... Is there a way to do this with the device locked and the screen off?
That's pretty cool, thanks for the guide. Works well on my LG G8. Also works when screen is off.
Played around with it a bit on my V60
Fantastic guide! Couldn't get the dual screen working at first, but I was eventually able to track down a log that corresponded to the button in all states (Locked/Unlocked, Case On/Off)
Honestly not 100% what I'm doing, so if anyone has any input that would be great! I can't post the URL yet because I just registered here, but I just linked to this thread on reddit /r/LGV60
TLDR; I found that using the Component "LGPhoneWindowManager" and Filter "hotKeyRelease count= : 0" works as a trigger while the phone is both locked and unlocked, and whether the case is on or off. Let me know if there's anything else I should know!
Do we need to add this for Tasker to read logs?
Code:
adb shell pm grant net.dinglisch.android.taskerm android.permission.READ_LOGS
Well I don't seem to be able to narrow down what actually works with this.
Code:
InputReader: Key event: device=5
was working ok to start with then I rebooted and device changed to 4!?
I've also tried
Code:
LGPhoneWindowManager hotKeyRelease count= : 2
for double tap and
Code:
HotKeyController HOTKEY_LONG_PRESS
for long press and they seemed to work initially but something stops them from working with the screen off after a while.
Just got my V50. I can't make it to work with your instructions
Done everything step by step.
Edit: Nevermind, now it works.
Morphy99 said:
Well I don't seem to be able to narrow down what actually works with this.
Code:
InputReader: Key event: device=5
was working ok to start with then I rebooted and device changed to 4!?
I've also tried
Code:
LGPhoneWindowManager hotKeyRelease count= : 2
for double tap and
Code:
HotKeyController HOTKEY_LONG_PRESS
for long press and they seemed to work initially but something stops them from working with the screen off after a while.
Click to expand...
Click to collapse
Double tap works for me, but it still keeps trying to open google assistant (even if its disabled from assistant itself and phone settings)
Does this also happens to you?
Anyway, ended using Button Remapper Pro from the Playstore. It also needs a PC and ADB, but it worked for long press with screen off.
Thanks XP_2, your instructions are impeccable! This worked well on my LG G8S - I used the Google Assistant button to launch my SatNav.
thanks a lot. I did all steps but, I have a problem. I can't turn off the snapshot (three clicks)
Make the video tutorial please
Sorry to revive an old thread. But can you remap the button to open a specific app, such as UAPP? By the way I own a V60, not V50.
I'm sorry but I can only get to the moment when I record my button press and go back to tasker.
Then I,m completely stuck. Please help.
What I can see is:
Code:
%lc_text
Text
The text that corresponds to the matched logical entry
COMPONENT [arrow button and magnifying glass button]
ViewRootlmpl
FILTER [arrow button]
ViewRoot's touch event: action down
GREP FILTER (check help) [tick place where I can turn it on or off]
And what to do now???
Clicking back button pops up missing permissions screen - but I can't grant any from this screen
Please help
I just learned I hate s10+ & android
S10+:
Uninstalled bixby using adb. Button still remains.
The orientation of volume keys and that damn bixby button that i had to create a samsung account to disable it. While powering the device i need to grab the other side with my fingers and squeeze which the volume keys are
Samsung phone app: on speaker screen sleeps after 10 or so seconds.
Found an option called smart stay. enabled that and found lift to wake option..
no way to disable face recognition to open up the screen to the lock screen. I end up hitting the power button to turn the screen on it gets turned on by seeing a face right after that I hit the button and it Powers off this is in a matter of seconds. can't break a habit of powering on the screen with the power button. And that's if the face recognition works. Sometimes it doesnt turn on. There is a way to disable this but face rec to unlock the phone has to be enabled, defeats the purpose.
Trying turn screen off, end up taking a screenshot.
Battery sucks.
When you grab the phone watching something horizontal, the palm covers the bottom speaker.
?Now i really hate s10+, no aptx hd support?
----------------------
Android "10"
Autofill fighting each other, Android, google chrome and lastpass auto fill is a disaster.
i find myself double tapping on the screen, i see the button as an example get tapped & button gets like shaded as if pressed, gotta tap again.
The clipboard, select all moves from the original place and jumps to "more" for more clipboard options.
the cursor upside down gps logo drag is stupid, draws up a magnifying glass, very irritating.
voice to text is just bad.
Some times highlight something, the clipboard does not popup, gotta grab the page n scroll it, clipboard pops up.
Google suggestions & auto correction sucks.
Battery sucks.
No screen protector, holding down on a field to paste, gotta hold field 2 or three times for paste clipboard pops up.
----------------------
I'll update this op as I go long or if I recall any bloops.
Let the discussion begin. Be adults.
strange... i have no problems at all... from button, auto fill, clipboard.
but sorry... i dont use any of samsung app.. (lastpass, keyboard, voice command etc).. I'm using google.
Sent from my SM-G9750 using Tapatalk
The only issues I am having with Android 10 is AT&T not knowing how to properly roll out an update before getting rid of all the bugs.
Last Pass is finally usable on Android 10. Not sure why your having problems with it.....
Hitti2 said:
I just learned I hate s10+ & android
S10+:
The orientation of volume keys and that damn bixby button that i had to create a samsung account to disable it. While powering the device i need to grab the other side with my fingers and squeeze which the volume keys are
Samsung phone app: on speaker screen sleeps after 10 or so seconds.
Android "10"
The damn clip board fighting each other, Android, google chrome and lastpass auto fill is a disaster.
i find myself double tapping on the screen, i see the button as an example get tapped & button gets like shaded as if pressed, gotta tap again.
the clip board again, select all moves from the original place and jumps to "more" for more clipboard options.
the cursor upside down gps logo drag is stupid, draws up a magnifying glass, very irritating.
voice to text is just bad.
----------------------
I'll update this op as I go long or if I recall any bloops.
Let the discussion begin. Be adults.
Click to expand...
Click to collapse
Weird. Just return the phone and get one that you like.
Maybe Android ai likes to piss me off eh.
https://www.blog.google/products/android/introducing-android-9-pie/
Powered by AI for a smarter, simpler experience that adapts to you
edit:
bloops are already happening, clipboard did not want to pop up highlighting text, had to move the web page for it to pop up.
google suggestions & auto correction sucks.
wow
Hitti2 said:
Maybe Android ai likes to piss me off eh.
https://www.blog.google/products/android/introducing-android-9-pie/
Powered by AI for a smarter, simpler experience that adapts to you
edit:
bloops are already happening, clipboard did not want to pop up highlighting text, had to move the web page for it to pop up.
google suggestions & auto correction sucks.
wow
Click to expand...
Click to collapse
Android Poops allover Crapple. So much more you can do with Open Source. Customisation and apps designed to do specific things that the IPhone can only dream of.
Id rather have a phone i can personalize rather than be held hostage by Apple and limited software .
Darkat70 said:
Android Poops allover Crapple. So much more you can do with Open Source. Customisation and apps designed to do specific things that the IPhone can only dream of.
Id rather have a phone i can personalize rather than be held hostage by Apple and limited software .
Click to expand...
Click to collapse
I have been Android user since the beginning and have a 2nd device which has been an iPhone for 4 years.
Android is superior to iOS in many many ways. The thing is, for the average Joe, the person who will use Verizon's Message+ app just because it was installed, for this user iOS is a better option. Simply works and also simple... no carrier crap.
I know a lady, had the IPhone 6, but really liked the look of the S7 or S8 , cant remember which, she only had it for a month, but she is like theres too much stuff on this to understand, so she went back to iPhone, then decided the IPhone was boring and migrated back to the S9.
As for performance, my partner's friend has the latest iPhone and when they are on a call together in messenger her friend keeps dropping out, my partner has the Samsung A50 because she dosent like curved edges. There never seems to be issues with other people in messenger.
And i think most governments use iPhones because they can't be modified by the average person. And this is why apple sales get their quota, government organizations and Reporter's. Even Mr Trumpty prefers his Samsung over IPhone.
This thread is just weird. If there are multiple apps that handle the same call on Android then you are presented with a prompt by the OS to select a default app to handle that function and then going forward that app will be the one to answer the call when an action triggers that function so I don't understand how this user is getting multiple clipboard apps getting triggered by the clipboard function.
to add another thing there's no way to disable face recognition to open up the screen to the lock screen. I end up hitting the power button to turn the screen on it gets turned on by seeing a face right after that I hit the button and it Powers off this is in a matter of seconds. can't break a habit of powering on the screen with the power button.
OP updated.
The phone turns off because the proximity sensor flashes so your ear doesn't cut people off
Perfectly sensible
Sent from my SM-G975F using Tapatalk
Davey Dual Sim said:
The phone turns off because the proximity sensor flashes so your ear doesn't cut people off
Perfectly sensible
Sent from my SM-G975F using Tapatalk
Click to expand...
Click to collapse
We're talking about loud speaker is on.
Hitti2 said:
to add another thing there's no way to disable face recognition to open up the screen to the lock screen. I end up hitting the power button to turn the screen on it gets turned on by seeing a face right after that I hit the button and it Powers off this is in a matter of seconds. can't break a habit of powering on the screen with the power button.
OP updated.
Click to expand...
Click to collapse
LOLWUTT? Just take the phone back and get something else because clearly you don't have a single clue what you're doing or you're trolling.
Only complain I have is that my 3-4 sot equates to 60-80% usage of the battery. I've cleared cache, put most apps to sleep, no gos, no wifi (at work no wifi) no media except Spotify to and from work (1hr total) no nothing autosync.
I'm sick of it. Makes me miss my old phones more because I could leave those things on and get 2 days avg out of them before charging, and that includes watching Netflix, Hulu, YouTube or my Plex server
Hitti2 said:
to add another thing there's no way to disable face recognition to open up the screen to the lock screen. I end up hitting the power button to turn the screen on it gets turned on by seeing a face right after that I hit the button and it Powers off this is in a matter of seconds. can't break a habit of powering on the screen with the power button.
OP updated.
Click to expand...
Click to collapse
There is an option in settings > biometrics and securtity> face id > "stay in lock screen" after the phone is unlocked by face-unlock.
You just toggle that switch on.
If you toggle this on, next time you press the power button, the phone will get into the lock screen, it will unlock (if it reads your face), but it will stay in lock screen (so as you can read your notifications etc.). You will have to scroll up to get into the home screen.
I suppose that's what you want to do, correct?
madvinegar said:
There is an option in settings > biometrics and securtity> face id > "stay in lock screen" after the phone is unlocked by face-unlock.
You just toggle that switch on.
If you toggle this on, next time you press the power button, the phone will get into the lock screen, it will unlock (if it reads your face), but it will stay in lock screen (so as you can read your notifications etc.). You will have to scroll up to get into the home screen.
I suppose that's what you want to do, correct?
Click to expand...
Click to collapse
So i have to enable facebrec to enable this??
I hate it even more. There is a way to disable this but face rec to unlock the phone has to be enabled, defeats the purpose.
OP updated.
leo72793 said:
Only complain I have is that my 3-4 sot equates to 60-80% usage of the battery. I've cleared cache, put most apps to sleep, no gos, no wifi (at work no wifi) no media except Spotify to and from work (1hr total) no nothing autosync.
I'm sick of it. Makes me miss my old phones more because I could leave those things on and get 2 days avg out of them before charging, and that includes watching Netflix, Hulu, YouTube or my Plex server
Click to expand...
Click to collapse
I recently installed a new fx30 battery in my moto x pure edition, I got more life in a day than this. thats with "android 10" optimized bat, adaptive power saving and have apps to be put to sleep, setup.
Hitti2 said:
So i have to enable facebrec to enable this??
I hate it even more. There is a way to disable this but face rec to unlock the phone has to be enabled, defeats the purpose.
OP updated.
Click to expand...
Click to collapse
Can you please explain what you are trying to do?
You want to press the power button and not get into home screen, but stay in Lock screen, correct?
If you don't enable face id, it will not unlock and take you to home screen directly. It will stay in lock screen till you unlock it either by the fp scanner or the pin etc.
If you want to have face id enabled, but not get into home screen directly, you toggle the switch I told you in my previous post.
So what is it that you want to do?
He's trying hard to troll, you just covered every other sensible option.
So last night I rebooted my phone and found that my fingerprint scanner isn't scanning my finger.
When my screen is locked, the fingerprint scanner doesn't work, it just doesn't respond (it's not consistent, when I use different lock methods (power button method, root method, accessebility method, Xposed method) it works one time and then again stops working)
There are 3 options of what happens:
I turn off the screen and put my finger on the scanner
1) the device unlocks
2) the device screen turns on and shows me the screen as if I pressed the home or power button
3) I get no response (this seems to be happening if I pressed the power button when the device is already locked)
1 and 2 are not always consistent, and I haven't pin pointed what the cause is
If 1) happens, then of course it works as expected and it will vibrate if it's the wrong finger, and unlock if it's correct
If 2) happens, it's the same as 1) just the device doesn't unlock, but just the screen turns on
If 3) happens, then it doesn't matter which finger, there is no response
I tried safe mode, it still didn't work.
I tried magisk core mode, also didn't help.
I saw someone wrote that it might be because of the dinner print gestures, but I don't use them, so I tried to activate them and they fully work even when the scanner isn't scanning my finger...
The scanner itself works, any app that I can use biometrics would recognize my finger...
And I know my fingers are still recognized, I made sure to check in settings... I even removed all my registered fingers and put in new ones, I rebooted between each step to see if it helps...
I have no idea what caused this problem, if any one knows please help.
My phone's situation is SM-G9600,
Magisk, EdXposed (obviously I tried the scanner after disabling both by putting magisk in core mode)
Android patch level from 1 September 2019
If this helps- build number: PPR1.180610.011.G9600ZHU5CSI2
I'll be happy to provide any information that might be helpful
The S9 has a common problem where the fingerprint scanner becomes unreliable even if there's a small scratch on it. Could you upload a photo of the back of your phone?
Here are some pictures taken with the phone through a mirror, no scratches on the sensor... Also it works in other situations, like anything that has somthing to do with fingerprint other then the screen lock.
I checked the the logs and I have some strange things there, for some reason the device is turning the fingerprint scanner off as if I don't have any registered prints... I also asked a friend to send me his logs, and the look like what one would expect, I'll attach the screenshots of both logs