How can I keep from accidentally placing a phone call from my Moto X?
Last night I fell asleep with my phone in the bed. Sometime during the night, I accidentally placed a call to someone who had recently called me. I really don't want this to happen again, as the consequences could be highly embarrassing.
Note: I *think* this was just the equivalent of a butt-call, but it's possible that, in my Ambien-induced stupor, I actually placed the call.
I tried disabling the Dialer app, but I don't think that's sufficient, as I could still dial out via People/Contacts. I want to put more barriers between me and making a call.
At the same time, I don't want to disable incoming calls, as I have family members who may need to contact me in an emergency.
Thanks.
How do you pocket dial these days.... Would need to press phone app, a contact and dial. Seems like a very specific chain of stray touches.
Aside from disabling every app that can call, or airplane mode... Not sure how you could do this.
Maybe some of those blacklist apps work for calling out.
KJ said:
How do you pocket dial these days.... Would need to press phone app, a contact and dial. Seems like a very specific chain of stray touches.
Click to expand...
Click to collapse
Yeah, I'm mystified, too.
Maybe some of those blacklist apps work for calling out.
Click to expand...
Click to collapse
I'll look into some 3rd-party apps and see. Thanks.
O.K., I just installed a fee app called Call Confirm that seems to do the trick. After I dial or after I hit a speed dial item, it asks me if I really want to dial that number. I think it's designed to protect people from drunk dialing, but it should work fro sleep-dialers, too.
Use a PIN or something on the lock screen.
I gave pocket dialed more with this phone... Forgetting to lock after texting and putting it in me pocket.
Sent from my XT1060 using Tapatalk
Just like mandrsn1 said, put a lock/pin on it so it won't do that.
Related
I have moved away from WinMob for the same reasons as many others and now find myself searching for similar Apps for Android (T-Mobile UK G2) now....
One such app I used was the 'In Call Tweak' app which woke the phone screen up when you removed it from your ear during a call.... very useful.
Has/does anyone have information as to this type of app existing for Android or know that it's being worked on?
Many thanks and I apologise in advance if I have been a numpty and not searched hard enough.
I am not going to be helpful here. There was an app, I removed it for some reason and now I cant remember what the app was called!
I do remember that it stopped the screen going off fully and it was a bit oversensitive but otherwise ok.
Thanks for the reply..... At least I know that one existed.
Can you remember if you found it in the Market? that could narrow down the search.
Ta,
I believe that "Shake Awake" is what you're after...
http://www.androlib.com/android.application.com-maplekeycompany-apps-shake-ptw.aspx
cdmackay said:
I believe that "Shake Awake" is what you're after...
http://www.androlib.com/android.application.com-maplekeycompany-apps-shake-ptw.aspx
Click to expand...
Click to collapse
You could not be more right! Thank you very much for reminding me...
Thanks guys.... I'll give it a whirl.
Having done some testing.....
The 'Shake Awake' app doesn't seem to work as well as the windows version which uses the light sensor as a trigger...
So if any one else knows of another appI could test I would be grateful.
by coincidence, i had need of it today, and it didn't seem to work at all. worked fine when I tested it using its own calibration tester thing.
I need to do some more real-call testing before I can tell if it's me, or it's broken.
You should try these settings for the HTC Hero:
select sensitivity: Like it ows you money..
enable cheek guard screen : OFF
show status : ON
outgoing calls : ON
incoming calls : OFF or ON as you like it (save would be OFF)
Don't forget to only leave this app with the back(arrow)button !
have fun!
Rubbish
This app suck major a$$ and rarely works properly.....
cdmackay said:
by coincidence, i had need of it today, and it didn't seem to work at all. worked fine when I tested it using its own calibration tester thing.
I need to do some more real-call testing before I can tell if it's me, or it's broken.
Click to expand...
Click to collapse
I'd failed to note that it only works for outgoing calls, by default, and it's a security problem if you enable it for incoming calls. I suspect that when I wanted to use it, it was an incoming call.
Can anyone explain what the cheek guard option is for? I can't find it explained anywhere...
Hi cdmackay,
I saw some reference to it in the help file but it wasn't specific but I think that it might stop your cheek from accidentially activating the screen.....
I still find it unreliable... about an 80% hit rate...
I'm not a programmer (in the true sense) but I can't see why it can't be made to work like the Win Mob version which senses the attitude of the phone together with what the light sensor is reading to check if the phone is by your ear or you are looking at it to enter data of some kind..
I might email the developer to see if this is possible.
Somebody else has also raise the same question...
http://forum.xda-developers.com/showthread.php?t=553108
they have mentioned an app called keepscreen which can keep the screen alive but this can also be done by PowerManager (for calls).
thanks much
I can't seem to get "assist" to not accept calls while in sleep mode. All calls ring through no matter what. I have "silence" checked and if I set the time from 7am-5pm when I test it with another phone the call comes through. The phone number I am calling from is not marked as a favorite. Any tips would be appreciated. Thanks.
tonyguy2000 said:
I can't seem to get "assist" to not accept calls while in sleep mode. All calls ring through no matter what. I have "silence" checked and if I set the time from 7am-5pm when I test it with another phone the call comes through. The phone number I am calling from is not marked as a favorite. Any tips would be appreciated. Thanks.
Click to expand...
Click to collapse
I've found this feature to be so buggy that it's not even usable. I had the same problem as you, and read tips online that say to reset the app data. I did that, reconfigured the app, and then sleep mode worked as advertised. Next day, busted again. If you want to reset the app every day, that seems to be the only way to get it to work. Lame...
I guess we are the only ones with this problem! I'll call their tech support and see if they could help me.
So I picked up a stock AT&T active and been using it for a month now. I love the phone but a few annoying things that it does daily on me is really starting to make me want to throw the poor phone! First the screen is way to sensitive sometimes! I try to text and it adds letters or I try to move between my home screens and it will open an app like I tapped on it, but I didn't. Or when I close out my running tasks it will act like I double tapped in that certain area and will open my mail app since it was in that touch zone. Anyhow I have played around with all the settings like "Air View" or "Motions and gestures" under the settings menu. Also the calling contact feature is really pissing me off. Say someone calls me but I miss the call, so I bring up my call log and I tap on the person that called me. It shows the phone icon and usually when you tap that, it suppose to call the person, but no stupid phone goes back to the call log list instead. I have to keep doing this like around 5 to 10 times before the dumb phone will finally decide to call the person! I am running the stock, or at least what came with it, firmware. Android version 4.3 with Baseband of I537UCUBML2. Has anyone else had these issues with this phone? Plus how can I fix this?
kcraptor82 said:
So I picked up a stock AT&T active and been using it for a month now. I love the phone but a few annoying things that it does daily on me is really starting to make me want to throw the poor phone! First the screen is way to sensitive sometimes! I try to text and it adds letters or I try to move between my home screens and it will open an app like I tapped on it, but I didn't. Or when I close out my running tasks it will act like I double tapped in that certain area and will open my mail app since it was in that touch zone. Anyhow I have played around with all the settings like "Air View" or "Motions and gestures" under the settings menu. Also the calling contact feature is really pissing me off. Say someone calls me but I miss the call, so I bring up my call log and I tap on the person that called me. It shows the phone icon and usually when you tap that, it suppose to call the person, but no stupid phone goes back to the call log list instead. I have to keep doing this like around 5 to 10 times before the dumb phone will finally decide to call the person! I am running the stock, or at least what came with it, firmware. Android version 4.3 with Baseband of I537UCUBML2. Has anyone else had these issues with this phone? Plus how can I fix this?
Click to expand...
Click to collapse
First off I'll say that ML2 had been known to be buggy. For your first problem, did you make sure Glove Mode is disabled? For your second problem I have no idea. Sorry I can't be more helpful.
If it is in fact stock, do a software update to KitKat and it should fix your stability issues. I can't because of root.
Is anyone else having issues with their AT&T GS5 pocket dialing 911? In the year I had my international GS4, it never once pocket dialed anyone (especially not 911). In the past month that I've had my GS5, I've pocket dialed 911 about 15 times. I'm pretty sure they are going to come after me at some point.
I have pin lock enabled, so the bottom left corner says "Emergency call" below the AT&T wording (camera icon is to the right). To dial 911, my leg seems to push "Emergency call", then the button below * on the dial pad (face with a emergency light icon), then the contact entry for "911". Very nice of AT&T to put the emergency contact button in the exact same place as the lock screen Emergency button... uggh
I can't find any way to remove the "911" contact that is listed in Emergency contacts. If I could remove it, at least my leg would have to push the emergency button, then dial 9, 1, and 1, and hit send - which is much less likely.
It has happened once to me on my S4 Active, and once with the S5. At some point, 911 will just start ignoring calls coming from Samsung phones.
Sent from my SAMSUNG-SM-G900A using Tapatalk
It is patently absurd that this happens. Mine has done it twice in a week now. There needs to be an option to remove the "emergency call" button from the lock screen. Its a lock screen. Its meant to keep the phone locked until action is taken to unlock it. I don't need a camera on it, and I don't need the ability to call 911 by simply walking around with the device in my pocket. Infuriating. Piss poor design. Anyone find a way to edit the ICE emergency contacts? While still a band aid it would at least stop us from tying up the emergency service lines.
Mine did it yesterday, i pulled my phone out of my pocket and it was ob the lock screen, and no 911 calls on my recent calls list.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
It happen to me all the time because of my huge pecker. Everytime I walk, my pecker pokes the key pad
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Wanam has an option to hide the emergency call on lockscreen
I am a 911 operator and it happens to a lot of people.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
csfile said:
Wanam has an option to hide the emergency call on lockscreen
Click to expand...
Click to collapse
I was super excited to read this, what with towelRoot and all... but, after trying this, Wanam Xposed doesn't seem to properly patch things on the S5. I tried the option to remove the emergency button from the lockscreen and the option to disable wake when the home button is pushed - neither worked (before or) after the Wanam prompted reboot.
shaunco said:
I was super excited to read this, what with towelRoot and all... but, after trying this, Wanam Xposed doesn't seem to properly patch things on the S5. I tried the option to remove the emergency button from the lockscreen and the option to disable wake when the home button is pushed - neither worked (before or) after the Wanam prompted reboot.
Click to expand...
Click to collapse
That's odd. Both those options work fine for me.
I can confirm that the option in Wanam to make the emergency call button go away worked for me.
But I will also say that this is not exclusive to Samsung phones. This happened on my LG Nitro HD as well. Ultimately, I completely changed the way I store my phone in my pocket. I keep the screen facing away from my leg (touching the skin through the cloth is enough to trigger that). I probably did it 15 times a week on my last phone and got tired of it. This was before the days of XPOSED and being able to make that button go away so easily.
shaunco said:
Is anyone else having issues with their AT&T GS5 pocket dialing 911? In the year I had my international GS4, it never once pocket dialed anyone (especially not 911). In the past month that I've had my GS5, I've pocket dialed 911 about 15 times. I'm pretty sure they are going to come after me at some point.
I have pin lock enabled, so the bottom left corner says "Emergency call" below the AT&T wording (camera icon is to the right). To dial 911, my leg seems to push "Emergency call", then the button below * on the dial pad (face with a emergency light icon), then the contact entry for "911". Very nice of AT&T to put the emergency contact button in the exact same place as the lock screen Emergency button... uggh
I can't find any way to remove the "911" contact that is listed in Emergency contacts. If I could remove it, at least my leg would have to push the emergency button, then dial 9, 1, and 1, and hit send - which is much less likely.
Click to expand...
Click to collapse
I don't have an emergency call button showing. Running Kool kit rom too. Never pocket dialed 911 since I've had the phone.
Edit. Never mind It only shows when you use a lock code of some sort. Not when you have swipe enabled for lock
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Killer Okain said:
It is patently absurd that this happens. Mine has done it twice in a week now. There needs to be an option to remove the "emergency call" button from the lock screen. Its a lock screen. Its meant to keep the phone locked until action is taken to unlock it. I don't need a camera on it, and I don't need the ability to call 911 by simply walking around with the device in my pocket. Infuriating. Piss poor design. Anyone find a way to edit the ICE emergency contacts? While still a band aid it would at least stop us from tying up the emergency service lines.
Click to expand...
Click to collapse
You can remove the emergency call feature in gravity box.
csfile said:
That's odd. Both those options work fine for me.
Click to expand...
Click to collapse
Turns out I missed the important step of actually installing the Xposed framework (I installed the APK, but never launched the XPosed Framework Installer to do the actual install... I then also needed to enable the Wanum module in XPosed).
Emergency button is gone, and the home button no longer wakes my phone! Woohoo!
conoro123 said:
You can remove the emergency call feature in gravity box.
Click to expand...
Click to collapse
Nice thanks, looking into this now. Anyone confirm xposed framework and gravitybox working for the active?
Killer Okain said:
Nice thanks, looking into this now. Anyone confirm xposed framework and gravitybox working for the active?
Click to expand...
Click to collapse
I used wanam xposed on my active to hide the emergency call button.
simmyrit said:
I used wanam xposed on my active to hide the emergency call button.
Click to expand...
Click to collapse
Yeah xposed works on the active, got the emergency button removed using gravitybox. However ever since installing xposed the phone has been rather sluggish to all inputs. Laggy scrolling, button and touch response etc. Ima give it a few days, may just uninstall xposed and figure something else out. Would be unfortunate tho as it seems there is a ton of potential in xposed and various modules. At least for now I won't be calling the damn cops once a day.
911 pocket dial
Just bought an AT&T Samsung Galaxy S5 so far it's dialed 911 3 times in 2 days while off in and in my pocket. I have a swipe pattern un-lock set up and no numbers pre-loaded into my emergency number memory.
Went to the AT&T store to try to find a solution. All I got was the usual baffled expression and stupid babel.
Does anyone know how to remove 911 emergency call function from the lock screen?
Until AT&T releases a fix for this I will keep telling the 911 emergency operators that this a function of my AT&T, Samsung Galaxy phone, and that it can not be disabled.
Maybe if 911 operators become swamped with pocket dial calls AT&T and/or Samsung will fix the problem with this phone.
Use Gravity Box, it's an xposed module, if you need help PM me and I'll be glad to walk you through it.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Killer Okain said:
Yeah xposed works on the active, got the emergency button removed using gravitybox. However ever since installing xposed the phone has been rather sluggish to all inputs. Laggy scrolling, button and touch response etc. Ima give it a few days, may just uninstall xposed and figure something else out. Would be unfortunate tho as it seems there is a ton of potential in xposed and various modules. At least for now I won't be calling the damn cops once a day.
Click to expand...
Click to collapse
Have you seen this thread? http://forum.xda-developers.com/showthread.php?p=53449642
Maybe it'll help. I just froze shealth and that stopped the lag.
csfile said:
Have you seen this thread? http://forum.xda-developers.com/showthread.php?p=53449642
Maybe it'll help. I just froze shealth and that stopped the lag.
Click to expand...
Click to collapse
Indeed. That fixed it. Now I'm not calling the federalis AND the lag is gone. Great success. So to recap, the solution is:
1. Root
2. Edit build.prop line "ro.securestorage.support=true" to =false
3. install xposed framework
4. Clear app data for s health and health service (under "all" in app settings)
5. Install module (gravitybox, wanam, etc)
6. Remove emergency button in lockscreen options.
7. Enjoy no longer getting vmails from minimum wage state employees telling you to "keep the phone out of the reach of children"
About 2 days ago I noticed when i receive a call, it rings but the screen is black. If i hit the power button it will wake the screen but it doesn't show I'm receiving a call except for the fact I lose LTE ( I'm on Verizon). I can also double tap the screen ( have the mod) and it will wake but still nothing. Once the call is over it will show a missed call in the status bar. I'm rooted but on 5.0.1 stock. Was working fine until a few days ago. Anyone else?
Are you using Lux? If so, uninstall it. Problem solved. If not, then I'm not sure what to tell you.
KB112 said:
Are you using Lux? If so, uninstall it. Problem solved. If not, then I'm not sure what to tell you.
Click to expand...
Click to collapse
No, not using Lux. Starting to piss me off. Just shows up out of the blue and haven't really installed any new programs in a while.
Well I'm still having the problem but i have found if I can wake the screen and then hit the phone icon, one of the options it gives me is to "return to call in progress" and if I hit that it gives me the option to answer the call. This sucks.
Any chance you've got something covering or blocking the ambient light sensor? When my screen got cracked, there was a fissure that went directly over the sensor, and I had the same problem you're having. Maybe some dust under a screen protector?
chemguru said:
Any chance you've got something covering or blocking the ambient light sensor? When my screen got cracked, there was a fissure that went directly over the sensor, and I had the same problem you're having. Maybe some dust under a screen protector?
Click to expand...
Click to collapse
That was a great idea but still didn't work. I took the screen protector off and still the same thing. I might try a custom rom but I think it's time to sell. I love big phones and I do like this phone but it may be a tad too big for me. Might put it on Craigslist but the hicks in my area don't understand what "Nexus" is or "price is firm"...."will you take $150 for that there phone?"
alnova1 said:
Well I'm still having the problem but i have found if I can wake the screen and then hit the phone icon, one of the options it gives me is to "return to call in progress" and if I hit that it gives me the option to answer the call. This sucks.
Click to expand...
Click to collapse
Do you have your phone number integrated with Google Voice? If so you might want to double check your Google Voice integration settings as I know they have that caller ID that lets it ring to voice mail and you can decide if you want to take the call after they start to leave a message
Google just did some changes with Hangouts this week that nerfd Messenger and Google Voice for me
Post here in the Q&A section is forthcoming but in the mean time you can check out my post on the Google forums about what their changes broke HERE
If you are looking to try a ROM check out Clean ROM - link is in my signature below
SP_Kenny said:
Do you have your phone number integrated with Google Voice? If so you might want to double check your Google Voice integration settings as I know they have that caller ID that lets it ring to voice mail and you can decide if you want to take the call after they start to leave a message
Google just did some changes with Hangouts this week that nerfd Messenger and Google Voice for me
Post here in the Q&A section is forthcoming but in the mean time you can check out my post on the Google forums about what their changes broke HERE
If you are looking to try a ROM check out Clean ROM - link is in my signature below
Click to expand...
Click to collapse
I do use my google voice number but I don't have it setup like you were talking about. It rings directly to my phone. I checked my setting and they are the same. I tired using hangouts for my voice text messages but found that a lot of the time it wouldn't notify me that I had received a message so I went back to the Voice app. I'm just stumped. I my give the Clean Rom a shot. Do you know if it works well with Verizon? Seen some people saying they were having a few problems with some of the roms on Verizon. Thanks for the input.
alnova1 said:
I do use my google voice number but I don't have it setup like you were talking about. It rings directly to my phone. I checked my setting and they are the same. I tired using hangouts for my voice text messages but found that a lot of the time it wouldn't notify me that I had received a message so I went back to the Voice app. I'm just stumped. I my give the Clean Rom a shot. Do you know if it works well with Verizon? Seen some people saying they were having a few problems with some of the roms on Verizon. Thanks for the input.
Click to expand...
Click to collapse
Clean ROM is a striped down and tweaked stock rom so it doesn't have some of the issues the ASOP roms do. I had to look through a few pages from about page 18 on, as that is when he announced CR was no longer in beta and released the 1.1 rom. Saw more t-mob, at&t and sprint peeps in there but at least 1 person on verizon reported in all was good and tether is supposed to be working
SP_Kenny said:
Clean ROM is a striped down and tweaked stock rom so it doesn't have some of the issues the ASOP roms do. I had to look through a few pages from about page 18 on, as that is when he announced CR was no longer in beta and released the 1.1 rom. Saw more t-mob, at&t and sprint peeps in there but at least 1 person on verizon reported in all was good and tether is supposed to be working
Click to expand...
Click to collapse
I just installed it and it seems to have fixed my problem for answering calls. Have no idea what was wrong before on the original rom. Seems to be running nicely and Verizon is working fine it seems like. Thanks for the recommendation.
Nice!! :highfive:
If you could please chime in on the clean rom thread so others see that a verizon user is up and running on it as I had seen way more peeps on the other 3 carriers there
SP_Kenny said:
Nice!! :highfive:
If you could please chime in on the clean rom thread so others see that a verizon user is up and running on it as I had seen way more peeps on the other 3 carriers there
Click to expand...
Click to collapse
I definitely will as soon as I head out and do a little testing on it.
I had this exact problem with my wife's Nexus 6 but mine was functioning fine. Turns out that under SETTINGS - SOUND & NOTIFICATION - APP NOTIFICATION she had the Goggle Dialer blocked.
Have the exact problem outlined by the original thread starter, scour a few webpages with different sort of solution.... nothing works!
My solution: Simple, just uninstall the Phone app updates, voila, all back to normal.
Hope it'll help someone.