anyone experiencing this issue where during a call the camera randomly launches. Your face could be touching the screen and the phone will vibrate and launch the camera. Happens on almost every call. I have tried flashing bliss and then clean flashing to cyanpop but the issue still exists. Wondering if anyone has a fix or knows how to at least mitigate the camera from launching.
I have also found that this happens during whatsapp/wechat voice call but instead of the camera opening it would enable speaker phone during the call versus the camera.
Some lovely gents over at oneplus forums identifiissueslissue. Apparently it has to do with search and garak builds. Someone had posted the solution inside the straps thread.
This has to do with the double tap to wake gesture and once you disable double tap to wake and enable prevent accidental wakeup the bug goes away. Hope this helps others with the same bug.
Yeah Install Garaks or Seraph08s CM13 builds & Enable Prevent Accidental Wakeup
These ROM s are Stable than the Other CM Builds
Related
I'm sure most are familiar with proximity sensor issues in calls on 4.2.2 roms. It appears that everyone's experiences differ a bit. I've seen some say that buttons are pressed when the screen is off. For others, and myself, the screen doesn't turn off.
When I first moved to 4.2.2, I was pleased to find the Xposed module that fixes the issue. However, after I activated it, I had a black screen issue. During calls (if more than a few minutes), the screen/device would become completely unresponsive (temporarily). It wouldn't even respond to a long press of the power button. I attributed this to the xposed module and turned it off.
Unsurprisingly, the original issue resurfaced. I noticed that it seemed more pronounced when receiving a call (and the device was previously idle). It seemed as though the device wasn't waking up the proximity sensor when calls were received. I created a Tasker profile (with Secure Settings) to execute a "wake device" action when phone calls (incoming) are detected. It has been a week since I created this, and I haven't seen the problem since.
For anyone still experiencing the issue, this may be a solution.
EDIT: Solution quoted below.
CrazyTrond said:
If your screen doesn't turn off during a call and your ear is pressing buttons it means your sensor is not working. On my phone it works again after a reboot but after some time stops working again (you can check with android sensor box from play store). I found a fix that works, described in this post: http://forum.xda-developers.com/showpost.php?p=44872536&postcount=206
Click to expand...
Click to collapse
Simba501 said:
....It seemed as though the device wasn't waking up the proximity sensor when calls were received. I created a Tasker profile (with Secure Settings) to execute a "wake device" action when phone calls (incoming and outgoing) are detected. It has been a week since I created this, and I haven't seen the problem since.
For anyone still experiencing the issue, this may be a solution.
Click to expand...
Click to collapse
Interesting solution, this drove me crazy on a 4.2.2 ROM..... I'm on 4.3 now, and thankfully the issue isn't present. I really hope AT&T will stumble up to an official 4.3 release and skip 4.2.2.
Only experienced this on 4.1.2, all 4.2.2 roms have been fine for me
Galactus said:
Only experienced this on 4.1.2, all 4.2.2 roms have been fine for me
Click to expand...
Click to collapse
Funny. It was the opposite for me.
Sent from my HTC One
I'm on stock 4.2.2 and I have no proximity sensor issues. I've had some issues on 4.1.2.
Everybody has the proximity sensor issue: plug in the headphones, cover the sensor, make someone call you, after the call, the screen will wake. That will happen in your pocket, which is very bad. The only solution that works for me is copas' proximity tool extension (on Google play), which I enable every time I am using headphones...
Sent from my HTC One using Tapatalk 4
If your screen doesn't turn off during a call and your ear is pressing buttons it means your sensor is not working. On my phone it works again after a reboot but after some time stops working again (you can check with android sensor box from play store). I found a fix that works, described in this post: http://forum.xda-developers.com/showpost.php?p=44872536&postcount=206
No, you didn't understand. Sensor works during phone call. After hanging up, either the other party hangs, or you via the headphones button, screen turns on. This is a bug in all HTC devices, as far as I know. Try it. Make someone call you, cover the proximity sensor with your fingers, tell them to hang up, while still covering the sensor (simulating the phone is in pocket or bag) and see what happens. Screen will turn on.
Sent from my HTC One using Tapatalk 4
---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------
Otherwise my proximity sensor works perfectly, never had a problem with it.
Sent from my HTC One using Tapatalk 4
Hi, I've been having this issue since installed CM11 on this phone (D800, happens aswell on other models). Sometimes the proximity sensor will not trigger when incall and taking away the phone from your face. So the only way to get the screen back (to hang-up the call for example) is hitting the back button -wich is annoying-. The sensor is ok since it is working fine (call and screen) on a G3 based rom. Is there any workaround for this? Can anyone help to fix this?
Thanks all in advance!
I have same issue and been searching and posting to find the cause and solution.
But unfortunaly no responses and/or fixes so far.....
Incredibly, this bug happens me aswell on cyanogenmod 12 (lollipop)... Should I start thinking about a radio problem? Wich other radio could be tested with this roms?
I believe I was having this phone disconnect issue since I flashed a lollipop based rom. What happens is when I am on a phone call, the call will disconnect. My proximity sensor is working fine. To test what was going on, I made a call, put my finger over the proximity sensor, and can double tap anywhere on the screen (which is off), even a slower double tap, and it will end the call and wake the screen.
I cannot find any setting for this. It appears my face bumps the phone while talking. I've had this G2 for a while, and only experienced it since I flashed CM12 lollipop, and I even tried another lollipop Resurrection Remix and it still does the same thing.
Also another tidbit, my screen was dropped and a local shop did replace the front glass and digitizer recently, and I think I upgraded to lollipop shortly after I got it back. Not sure if it has anything to do with it. All other features on my phone work great.
Any ideas?
Hi All,
There is some hardware issue with my S4 that it will wake itself up randomly every few seconds. It has this issue with every touchwiz rom I put on, Kitkat or Lollipop (fresh install so that I know it's not caused by some apps installed later). I'm sure I have tried everything like disabling air gesture, every senor related function that I'm aware of.
I used wakelock trying to track which apps triggered the wake with no luck.
I also tried gravity screen, no luck.
The only fix so far is using a cm rom. I suppose it's because cm rom ignores some sensor info compared to touchwiz. I can stay with cm but I really like the stock camera.
Can anyone cast some light on how to fix this screen wake up issue on touchwiz?
Update: Finally got this fixed. The fix is very specific to this phone. As I mentioned this phone has some issue including home key not working and the random screen wake. After disable home key mapping in Generic.kl and gpio-keys.kl by adding # in front of key 172 Home, screen wont wake up by itself again.
shadowcliffs said:
Hi All,
There is some hardware issue with my S4 that it will wake itself up randomly every few seconds. It has this issue with every touchwiz rom I put on, Kitkat or Lollipop (fresh install so that I know it's not caused by some apps installed later). I'm sure I have tried everything like disabling air gesture, every senor related function that I'm aware of.
I used wakelock trying to track which apps triggered the wake with no luck.
I also tried gravity screen, no luck.
The only fix so far is using a cm rom. I suppose it's because cm rom ignores some sensor info compared to touchwiz. I can stay with cm but I really like the stock camera.
Can anyone cast some light on how to fix this screen wake up issue on touchwiz?
Click to expand...
Click to collapse
Hi
I've been having the same problems with my phone, I think I've managed to fix the problem,
I went to settings, device, display, then at the bottom turn off 'ambient display'
Problem seems to be gone
Solution in post #4.
I have a H872. I had been running Havoc OS v3.1 10/01/2020 without any issues. This past weekend I decided to update to Havoc OS v3.4 21/04/2020 (clean flash) and everything was great until I realized that the proximity sensor wasn’t working. When I received a call the screen stayed black. Swiping down from the notification bar let me answer the call but the proximity sensor didn't work - screen stayed black. I couldn't even hang up - had to wait for the other caller to hang up. Same issue when I initiated the call.
I then tried Havoc OS v3.4 18/04/2020 (clean flash again) and the same calling/proximity sensor issue remained PLUS I could not send/receive MMS even though APN was set up exactly the same as my original configuration (I had taken screenshots of my original setup). I attempted Havoc OS v3.4 21/04/2020 once again and MMS stopped working too! As well as the proximity sensor issue.
I then restored my original nandroid of Havoc OS v3.1 10/01/2020. While it restored successfully in TWRP, it never booted into the system. It just hung on the last frame of the boot animation. I am at a complete loss as to how to fix this phone now. I have just installed MSM Xtended and the proximity sensor is still non-functioning. I have since switched my sim to my Xiaomi backup but really want to get back to my G6.
It worked perfectly…I attempted a simple upgrade and all hell has broken loose! Any tips? Please.
Update:
I completely restored the phone to stock with H872 20g kdz/LGUP and was able to send MMS but the proximity sensor was still not functioning. Can the sensor just suddenly go bad like that? It was working perfectly until I updated Havoc.
Anyway, I have re-rooted and reinstalled the latest havoc. I am hopeful that I will get MMS to work, however, am not sure the proximity sensor will. I have found here that Android 10 allows for all sensors to be disabled with a Quick Settings Tile. This would work for when I initiate a call (can use the power button to turn the screen off/on). But would not be able to activate it once a call comes in. Is there a way to automate the sensor to turn on/off automatically when a call comes in? Or better yet, just disable the proximity sensor, and only the proximity sensor, completely? Been Googling all morning but haven't found much aside from this toggle, and an Xposed mod that may not even work with Riru Xposed...not to mention I want to avoid Xposed if I can.
Still looking for advice if you have any.
Thanks!
Update 2:
I am now running the latest Havoc with working MMS but still the proximity sensor issue persists. I am getting around it by using the Quick Settings Tile/toggle that is activated in Developer Options. This turns off the proximity sensor, as well as compass, accelerometer, & gyroscope. So I have to remember to disable it after a call.
I have searched to no end for a way to disable the proximity sensor permanently but there is very little on the subject. I've tried some apps that claim to turn it off, but they have not worked for me. It seems to me it should be an easy thing to do...but no!
My request:
Someone that can explain how to disable the proximity sensor on Havoc, or someone that could maybe recompile the dialer.apk to not utilize the proximity sensor.
Thanks again!
Final update: Solved!
I decided to install EdXposed and Sensor Disabler. After a lot of experimenting I found settings that work. In Sensor Disabler I selected:
LGE Virtual Proximity Sensor & selected "Remove Sensor" and Saved
Proximity (There are 2 listed - I set both the same) & selected Mock Sensor Values & set them to the highest setting possible and Saved.
Now I can make & receive calls and have access to the Accept/Reject/Message functions, as well as the keypad to input if needed and can end calls. The power button is easily accessible on the back and turns the screen off & on during a call, so I can keep it off the whole time I'm talking.
Not the most ideal situation but works for me considering the proximity sensor is completely useless now. Hope this helps anyone else in the same predicament.
EDIT - Sensor Disabler doesn't appear to be the most reliable. After a reboot it's hit or miss if it will work. It seems that after rebooting it takes a couple minutes for the app to "kick" in and function...but then it only seems to work more for incoming calls. Ultimately I am still using the Quick Settings tile to turn off all sensors during calls.