I have Cyanogen's 4.2.3.1 installed with the 2.0 Maps application and Navigation works correctly for me.
Since I installed Navigation I am getting a huge "Double tap to answer" button that pops up on my screen when a call comes in.
A) It seems to have shortened the amount of time my phone rings before sending to voicemail
B) The double tap is flaky
C) It looks like ****
I have searched Google and the forums to see if this was an issue people had but can only find people talking about the in-call unlock screen.
Does anyone know why this is happening and how to stop it?
answered in your other thread.
Related
Hi guyz,
Googled it with no real solution, nobody in the Touch Pro forum seem to have it either.
Is there any way to disable waking my ppc or at least lock the touch panel on notifications like low battery, appointments etc. Message notification is easy to disable, Answerkeys Disabler works like charm when it comes to incoming calls but I want to disable waking up the device on any notification and have only audible alerts.
Often when in pocket or case my TP wakes on low battery or appointment reminder and starts random dialing, texting, etc. which is getting annoing.
Thanks in advance,
dEM
there may be a registry key you can delete so that you don't get notifications at all.... i'm not real sure about which ones though. i'll look around.
EDIT: SHNotificationRemove at msndn :
http://msdn.microsoft.com/en-us/library/aa455968.aspx
Good question,hope someone has an answer
how about usin s2u2? doesnt solve it exactly but maybe a workaround?
There are some locking solutions over there. I'm looking for one that doesn't lock my device all the time but only on these notifications. The best will be if it doesn't even wakes up.
Just great! More than a month I've been trying to find a solution to this problem with no success!
Hi,i hope this keeps the thread alive,i would also like to know if its possible and how
Me Too!
I have this exact same problem. When a reminder alerts me on the phone it wakes up the unit and turns the display on. If this stays in my holder it just keeps the phone on because it senses all the pushing... We have a PIN enable so it won't do anything major. But there are times I've pulled out my phone to find it awake (on) and there are * in the password field - so I know it is sensing touches when in the holder. This definitely drains the battery.
HELP PLEASE! Any Fix found?
I'm having this problem as well - anybody out there got any ideas...?
I hate how there seems to be no solution to this! It didn't happen to me in WM6.1, so it must be buried within 6.5 in some dark, fetid, unreachable place :-(
I keep accidentally dialing people with my bum when one of my reminders goes off. Grr!
EDIT: I did finally cave and install a slide to unlock feature (S2U2) which I got from http://a2-s2.com. I was surprised with the level of customization you can do with this program, and I do love how I can have the slider's wallpaper change randomly, so I am greeted with a different image each time I unlock the phone. I know it's not what any of us were looking for, but it's a workable solution for now.
I've since gotten round this by using PocketShield - works well for me. Doesn't work well with the PIN lock though....
I'm using Smartlock for locking the screen; incoming call and stand return from suspend.
It has an option "suspend after lock".
http://forum.xda-developers.com/showthread.php?t=505032
disable wake on notification
finally figured it out, a few years later.
still can't find a factory setting for it, but i downloaded NILS (notification lock screen) and it gives you the option to disable wake on notification. hope it helps
Newbie here and I apologize in advance if I overlooked a past thread on this problem as follows:
Anyone else experiencing the frustration of having to constantly tap the screen to unlock every few seconds once you hit a prompt after keying a main number. This happens whether you receive or generate calls and it is a nightmare using the provided dialer which is embedded in the software.
I understand the idea behind this to not inadvertently tag a button with your cheek, grasping finger, etc.. but why is there no time interval or delay setting as you may have with keeping your screen lit? No solutions from T-Mobile thus hoping this forum will have some remedies or compatible equally functioning alternative dialer.
Ok guys so the question has been asked a couple of times on XDA and there is still no viable solution. Maybe a Nexus section would be better to post and work on this.
I'm wondering if there is a solution or workaround to disable the built-in Google Voice Dialer that is launched from the lock screen when pressing the action button on a bluetooth.
When the phone is unlocked the action button on the Bluetooth typically launches Google Now, which is perfect. BUT I want to be able to Launch Google Now from the lock-screen using the Bluetooth action button, and NOT the crappy Google Voice Dialer.
The closest thing I've seen that allows this to be done so far is: Bluetooth Launch.apk from the PlayStore.
BUT this app has one major flaw.. when the headset button action is changed to com.google.android.googlequicksearchbox.VoiceSearchActivity, which is what is required to launch Google Now, the phone never sleeps/locks.
If this action>assign could be written and still allow the phone to sleep and lock, it would be ideal.
I was hoping that there would be an Xposed module to disable to Google Voice Dialer, but this has not been created as of yet.
Any help would be much appreciated and thanks will be given.
Get rom toolbox pro and take it out or freeze it. Simples
Ten min cutoff app.
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Unfortunately i can't help but i am getting the same issue
Sent from my SM-G930F using Tapatalk
I tried applying different dialer apps and they only serve to change the dialer/contact screens, but the default calling screen containing the HOLD button remains unchanged. I found that using Skype as the default dialer fixes this issue since it uses its own dialing/calling screens, but obviously it's not practical to just rely on Skype. So the problem still remains unresolved.
As an update, someone on Reddit posted a download link to the Google dialer app here at: http://forum.xda-developers.com/galaxy-s6/themes-apps/app-google-dialer-t3323432
This installs a new dialer, which actually provides a new calling screen as well, fixing the main issue. The default dialer is better in my opinion since it opens up the dial pad immediately while this one doesn't, but this is a good option at this point
gomulkaaa said:
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Click to expand...
Click to collapse
even worst than calls is when you press it while watching youtube vids, i wish there was a lock of some sort cuz the music stops paying all the sudden
It's embarrassing when I put my clients on hold and don't realise until they don't respond to me. The cheek hold doesn't result in any audible sound so you can be talking for 20 seconds with the other end on hold. I love the S7 edge but I'm contemplating sending it back. I'll try the Google dialer mentioned above first though
Same issue here. I talk on the phone almost 2 hours a day and this is happening at least 1-2 times in every call! Checked my proximity sensor and it's working as it should.
Any workarounds? Maybe someone can edit the phone.apk and remove this stupid button or disable it? I am against rooting but I will definitely root my phone if there's a fix for this.
Damn, I suffer exactly the same issue! Found this googling for ideas...
Very old thread, but I just wanted to give a suggestion to others with the same issue. I really love the Google Phone dialer app, which actually replaces the calling screen during calls with this app's own screen, so you no longer have the Hold button at such an unfortunate location. If you do choose Google's app, I recommend this specific version: http://www.apkmirror.com/apk/google-inc/google-phone/google-phone-2-05-07_rc4-release/google-phone-2-05-07_rc4-android-apk-download/
The caller-ID function by Google actually works with this version, whereas the other .apk files floating around do not have this function working properly.
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
robot1000 said:
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
Click to expand...
Click to collapse
Finally searched for the answer to this today, after several accidental holds on work calls.
The solution above with Google Phone APK worked for me. I just went to SETTINGS - APPLICATIONS - DEFAULT APPLICATIONS and then under Calling App near the top, changed it from Contacts to Phone. . For some reason, I cannot open the phone app itself (gives an error message) but calls do use the phone app rather than Samsung stock dialer.
Turn off screen!! Most phones allow you to turn screen off without interrupting the call.
Same issue with a galaxy A5 2016
Can't understand why samsung doesn't fix it
Sorry for the weird title, I didn't really know how to concisely describe this issue. I still don't fully understand what triggers it but basically I've noticed that if I lock my phone while on a text chat (in either Textra or Facebook Messenger but probably includes all text chats), then unlock it to reply, I can't click on the text input box or hit the navbar back button for 3-5 seconds. This can also happen while my phone is unlocked when I'm switching through apps so I wouldn't directly blame the action of being locked. I know the phone isn't frozen because I can still hit the back button at the top left corner of the screen fine.
It almost looks as if though it's navbar-related because the pill is white when I unlock the phone, then after a few seconds when it's responsive again the pill is grey. My previous phone was a Oneplus 3 and it never had any issues like this (although it had physical buttons for navigation, not a navbar) so I'm wondering if this is an issue or if this is by design for some reason. I've tested each of the navbar options (traditional navbar, pill, and gesture) and none of them resolve the issue so maybe it really isn't.
One other detail I noticed is that the cursor also doesn't blink for those 3-5 seconds, and then when it starts blinking again I can start typing so it could be something else.
I just find it annoying to have to wait a few seconds whenever I want to unlock my phone and reply to a text and this doesn't seem like regular behaviour, has anyone else heard of or experienced this and know of a fix?
Videos of the issue:
In Textra:
https://imgur.com/X0lw47J
In Facebook Messenger:
https://imgur.com/1IrRfPY
It could be part of the same ghost touch bug. Did you tried to disable NFC and see if those input lags reduce?
ducted said:
It could be part of the same ghost touch bug. Did you tried to disable NFC and see if those input lags reduce?
Click to expand...
Click to collapse
I've had NFC disabled since I got the phone so that isn't it.
I don't think it's ghost touch-related since it doesn't happen sporadically, it just seems to be when I open a text chat app or something too quick which doesn't make sense. Perhaps I can record the issue and upload a video to more clearly show what happens.
I just added videos of the issue to the OP.
That looks weird, did you tried to use the gesture navbar only or the one with all the buttons? I would try also another keyboard just to discard any GBoard related issue.
I've tried every other navbar type (including the one with just gestures and no bar) and the results are the same. I have also tried a different keyboard (Fleksy) and again, same issue. I had essentially the exact same setup as far as apps go on my Oneplus 3 and its fine, so I'm thinking it has to do with either a new version of android or the new OxygenOS but I have no idea.