Related
I'm coming from the Captivate, and the only option I'm really missing on the Atrix is the call reject feature. I want to be able to automatically reject calls from certain numbers and unknown numbers, can't find the option there anywhere.
I know I can use the 'silent rington' trick, but that's not idea and doesn't work with unknown numbers.
Any thoughts?
Are you asking to blacklist certain numbers, dismiss a call like with volume down, or have all calls for a period of time go straight to voicemail?
Blacklist numbers, I found an app for it though that I'm gonna try
Reject with Text
I was wondering something similar. With the Captivate and many other phones I had, there was an option to "Reject with Text." This was a nice feature I used every now and then. It seems that it is missing on the Atrix, does anyone know of an app or something that can do something similar?
I would suggest using Google Voice, which is free and open to anyone now.
You give out your GVoice number, and set GVoice to forward to your cell phone. No one ever needs to know your cell number direct, and if you change it..you just change the setting in GVoice.
GVoice allows you to actually block individual numbers--and generate specific responses to them! And you won't pay for the call, which would use cellular airtime if it was just your cell phone blocking it.
When editing a contact ---- under "Additional info" -> "Call handing" you can select "send strait to voicemail" .... however Mr. Number block is great for this by automatically blocking known spam by sending straight to voice mail or my favorite the "answer and hangup" tactic
The best solutions as stating before is Google voice as you can play a "this number is disconnected" or "the number you are calling does not accept unknown/blocked numbers" voice mail greeting.
Contacts > [Select a contact] > Additional Info > "Send straight to voicemail" [Check box]
I downloaded an app that works for me. The Contact thing is fine for numbers that you know, but not for unknown caller numbers.
I've tried Google Voice and wanted to like it, but its not my cup of tea.
It looks like the reject call feature and list is missing on this ROM, but not a big deal since there are apps to handle it.
AsSiMiLaTeD_77 said:
I downloaded an app that works for me. The Contact thing is fine for numbers that you know, but not for unknown caller numbers.
I've tried Google Voice and wanted to like it, but its not my cup of tea.
It looks like the reject call feature and list is missing on this ROM, but not a big deal since there are apps to handle it.
Click to expand...
Click to collapse
The reject call feature works perfectly...the reason they don't allow you to just block all unknown calls is because almost nobody would actually need that. What if your mother ends up being rushed to the hospital because of an accident and the police try calling your phone (the number she gives)? Police officers usually leave messages but what if he doesn't want to so he tries calling a few times and thinks your phone is off because it always goes directly to voicemail?
It's not that hard to just hit "Reject" when you get a phone call from an unknown number...
hotleadsingerguy said:
The reject call feature works perfectly...the reason they don't allow you to just block all unknown calls is because almost nobody would actually need that. What if your mother ends up being rushed to the hospital because of an accident and the police try calling your phone (the number she gives)? Police officers usually leave messages but what if he doesn't want to so he tries calling a few times and thinks your phone is off because it always goes directly to voicemail?
It's not that hard to just hit "Reject" when you get a phone call from an unknown number...
Click to expand...
Click to collapse
The police would not be calling from an 'Unknown' number, if the police are calling me I'd see a number displayed on the caller ID.
I've NEVER received a call from a number tagged as unknown or blocked that wasn't a telemarketer call.
The 'reject call' feature, as I've seen it implemented on MANY other Android phones in the settings menu, is MISSING on this phone. Its not that it doesn't work, its that it is missing (AFAIK anyway)
I agree that it is missing, I miss it too. I used it all the time for a few numbers that kept calling me and asking for random names. Seriously though the same number would call and each time ask for a different name. All i ever had to do before was enable auto reject and click "add to reject" when that number, or set of numbers called. Now I will have to add it to contacts and then reject it. Not a big deal, and good to know that I have an option.
soo in the end whats the name of the free program that can reject automatically the unknown callers? i need that 2.(the SGS+ had that feature and it was awsome, i really need it)
OK, I know I'll probably get slammed, but I searched and searched and can't find the answer...
I'm coming from the Nexus One on ATT where google voice worked flawlessly. Now, on Verizon with the Thunderbolt, it's a nightmare. Incoming calls don't get my Gvoice message, just a notice saying to enter a PIN. Also, Gvoice isn't showing the correct outgoing caller ID... even though everything "appears" to be setup properly in Gvoice settings and on the Thunderbolt.
I feel like I'm taking crazy pills!! Any ideas?
The information on the Google Voice Settings page didn't work for me. Telling you to dial some crazy * #### blah blah blah.
So I did some calling to Verizon and dug deeper. In order to get GV on your VZW, you need to do these steps:
*71[Google Voice Number]
*90[GVnumber]
*92[GVnumber]
Then GV should work.
I was in the same boat as you. Upgraded from TMO Nexus to this and was going crazy trying to figure out why GV wouldn't work.
Hope it helped?
Why don't u just fork out the money for Verizon's awesome visual voicemail! What a joke. Don't think Verizon likes gv.
Sent from my ADR6400L using XDA App
I just installed the app, dialed *xxxxxxxxxx (whatever number i was told to dial by the app or site) and it seems to be working fine. I've never used it before though, so I'll update this if something goes wrong.
Sent from my ADR6400L using XDA App
I did that and the voicemail still were intercepted by Verizon
Sent from my ADR6400L using XDA App
I just followed the directions on google.com/voice and mine worked fine. My voicemail gets picked up by GV.
i had previously set up gvoice with sprint so what I had to do in gvoice was delete my cell number and re-set it up so it would register with Verizon. Works fine after that.
usafle said:
So I did some calling to Verizon and dug deeper. In order to get GV on your VZW, you need to do these steps:
*71[Google Voice Number]
*90[GVnumber]
*92[GVnumber]
Then GV should work.
Click to expand...
Click to collapse
Thanks for the post, let me try it out. Also, after digging more at Google.com, I found these bonus codes depending on what network we're on...
Verizon (CDMA network): *71[GVnumber] AND *90[GVnumber] AND *92[GVnumber]
Verizon (TDMA Network): *74[GVnumber] and *73[GVnumber]
What net are we on with LTE?
Worked! THANKS!
Worked fine for me with just the *71-XXX-XXX-XXXX code BOTH times I had to set it up (thursday new phone, last night after rooting). I just called myself from my Skype out # and it rolled to GV voicemail.
All U.S. Verizon Customers are on the CDMA network.
Lipmonger said:
What net are we on with LTE?
Click to expand...
Click to collapse
distortedloop said:
Worked fine for me with just the *71-XXX-XXX-XXXX code BOTH times I had to set it up (thursday new phone, last night after rooting). I just called myself from my Skype out # and it rolled to GV voicemail.
Click to expand...
Click to collapse
That code only sets up forwarding for one group of calls. Unfortunately, you need to setup GVoice on the Thunderbolt to properly forward BOTH unanswered (missed) calls, and ignored (intentionally declined) calls. The two different actions are handled differently by Verizon - hence the multiple dial-in codes. Although I don't know what the third code is for.
More here... http://www.google.com/support/forum/p/voice/thread?tid=00a93855af6943b4&hl=en
Lipmonger said:
That code only sets up forwarding for one group of calls. Unfortunately, you need to setup GVoice on the Thunderbolt to properly forward BOTH unanswered (missed) calls, and ignored (intentionally declined) calls. The two different actions are handled differently by Verizon - hence the multiple dial-in codes. Although I don't know what the third code is for.
More here... http://www.google.com/support/forum/p/voice/thread?tid=00a93855af6943b4&hl=en
Click to expand...
Click to collapse
I'm not going to get into a huge back and forth over it, but I just tested my Thunderbolt phone both ways...I called it and let it go unanswered, and then I called it and hit the decline button on the screen. Both times it rolled to my Google Voice voicemail. I only set it up with the *71 code.
I'm not disputing that your experience may be different, but that's how it worked for me.
Whenever I try to add my new Verizon phone number, it shows up as a Gizmo account no matter what I select (Mobile, Home, or Work).
Just what I was looking for, thanks!
works the same as it did for me from my og droid. i wish there would be an icon telling me what number the people are calling me on. i have a bunch of people call the wrong number and i never know what line its on.
I had Google voicemail set up on T-Mobile with my N1, MyTouch 4G and it worked perfect. Tried to set it up on my Thunderbolt with Verizon and I went thru the set up procedure, dialed the *71 and my google # then *90 and finaly *92. When I was done I tried to call myself and see if it works, I get a message asking me to put the # I am trying to call and hit the pound button. Please help, Love Google Voice and I tried Verizon tech help and absolutely useless, tried to sell me theirs.
Please anyone, I want that Google voicemail app working.
vinnyjr said:
I had Google voicemail set up on T-Mobile with my N1, MyTouch 4G and it worked perfect. Tried to set it up on my Thunderbolt with Verizon and I went thru the set up procedure, dialed the *71 and my google # then *90 and finaly *92. When I was done I tried to call myself and see if it works, I get a message asking me to put the # I am trying to call and hit the pound button. Please help, Love Google Voice and I tried Verizon tech help and absolutely useless, tried to sell me theirs.
Please anyone, I want that Google voicemail app working.
Click to expand...
Click to collapse
Are you test calling from another # you associated with Google voice? If so try *67
hurl03 said:
Are you test calling from another # you associated with Google voice? If so try *67
Click to expand...
Click to collapse
I had a friend of mind call in and he got the same message. I have seen other posts of people with the same issue. I can not find out how they resolved their issue. Someone must have the answer, Verizon tech help didn't have a clue unless I was buying their V Voice Mail.
I also came over from t-mobile. All I did was set my phone's voicemail setting to my Google number, then did *71(my Google number) and my voicemail works fine.
Sent from my Bolt
This maybe due to my "upgrading" SIM cards at T-mo earlier today, but my new Amaze is not allowing me to set up Google Voice or utilize the Visual Voicemail preinstalled features and keeps directing me to call 611. Google Voice sends back an error stating "Failed to retrieve and save current forwarding number settings." When I click on Voicemail Settings it looks bad. The page doesnt load up (ie appears greyed out, with a jumble of numbers at the top where my phone # should be. Anyone else having similar issues? My first guess is either an issue with Sense or T-Mo.
do you have wifi calling ?
vinterchaos said:
do you have wifi calling ?
Click to expand...
Click to collapse
No I dont see the app. At least like there was in myTouch4G, also no references to it in my settings menu.
my google voice works. it wasnt able to set up the forwarding numbers, but i always check my vm via the app anyway so. It downloaded all my vm and a test call was sent to my google mailbox
domin8 said:
my google voice works. it wasnt able to set up the forwarding numbers, but i always check my vm via the app anyway so. It downloaded all my vm and a test call was sent to my google mailbox
Click to expand...
Click to collapse
If you try to open VM Settings does it look normal, or is it all greyed out and the number all jumbled?
mines not greyed out. double check and run the setup a few times, maybe itll work through. mine said some error, but i dont have anything greyed out actually. i check mine with the google voice app itself, so i dont see it as an immediate issue (for me at least)
I went from the LG G2x to this device and I had GVoice on that. The voice app failed to set call forwarding options for me, too, when I first installed it on the Amaze4G but becuase they are subscriber specific with the carrier, and not the device it doesn't matter.
If you go through google voice web site and go through the settings you can get the call forwarding codes and dial it from the device and it will accomplish the same thing and work fine.
I was on the phone with TMO this morning about a network issue happening with my phone that's unrelated to voicemail. In investigating potential service issues they mentioned that Seattle and the surrounding area has a new visual voicemail system issue. It could be that. I'm not sure if that's specific to my location or if they rolled out something service wide.
I am looking to integrate Google Voice beyond my typical one phone, one account setup. I would like to validate my understanding/logic, and make sure that everything is reversible. Please contribute with knowledge however you can.
Phones: (1) Sprint and (1) ATT. Both Android. My goal is to be able to call, text, VM (and MMS via Gmail) via one phone number, using two phones. I want other people to see the single number. And, I want to be able to reverse the setup if I choose.
1) Use Sprint phone and Sprint/GV integration Option 1 (Sprint # as GV).
2) I’ll pay the $20 to preserve my GV# so it becomes secondary.
Question: Is the Sprint/GV integration fully reversible, so that the Sprint # goes back to the Sprint phone and my original GV# I paid $20 to save becomes the primary GV # again?
Yes or No?
Question: Can I log into the GV client using the same account on both the Sprint and ATT phones, so I can pick up VM and messages on either phone?
Yes or No?
3) I’ll set up GV to ring on both my Sprint and ATT phone
Call flow: Someone calling my Sprint # (integrated, used as GV#) will cause both my Sprint and ATT phones to ring simultaneously?
True? Yes or No?
Call flow: When I make an outbound call with my Sprint phone, the call recipient will see my Sprint #?
Yes or No?
Call flow: If I can log into GV on my ATT phone using the same account as the one I use on Sprint, when I make an outbound call with my ATT phone (“Using Google Voice”), will the call recipient also see my Sprint #??
Yes or No?
If all of the above is Yes, I presume I can send/receive SMS via the GV client, and therefore the recipient will see my Sprint #?
Yes or No?
If all of the above is Yes, I presume I can RECEIVE MMS via Gmail? I’m just not sure about sending…
Yes or No?
Thanks for any info…
Just spent an hour and a half on the phone with Verizon, and then Samsung. Remember that *92 issue where hitting "Turn on Call Forwarding" in the Gear Manager or on the Gear S would try dialing *92 (a non-working short code) instead of *72? Yeah, that's still a thing. And Verizon and Samsung don't care. They don't care about you. Here is a run-down of what I went through in almost 2 hours.
-Call Verizon
-"I can activate call forwarding on your phone?"
-"No, I just want the *92 short code added to my area's cell switch."
-"You sure you don't want me to activate call forwarding?"
-"No, I can do that MANUALLY myself fine. I need either *92 to be added to my area's cell switch as a "call forwarding" short code, or I need someone to fix my Gear Manager/Gear S so that it dials *72 instead of *92."
-"OK, let me ask our engineer."
...
-"He says that would interfere with FiOS."
-"Other people in other areas have been able to do it fine."
-"He says it would interfere with FiOS."
-"OK...then can you fix the Gear Manager/Gear S so it dials *72 instead of *92?"
-"I mean...we can call Samsung."
-"OK, lets do that."
-3-Way Call with Samsung
-"We're not responsible for call forwarding. That's the carrier (Verizon)."
-"That makes NO sense. I can manually dial *72 then the number fine. It's only through your Samsung Gear Manager and Samsung Gear S firmware when I hit "turn on call forwarding" that it tries to dial *92. It's YOUR app that has the problem."
-"We're not responsible for call forwarding. That's the carrier."
-"So, you're saying that the reason my SAMSUNG Gear Manager app dials *92 rather than the *72 EVERYONE ELSE knows as the proper code...is Verizon?"
-"Yes. We're not responsible for call forwarding. That's the carrier."
-"So...you can't look into it and see if there's a way to update anything?"
-"You can take it to a Samsung Experience Store and they can try doing a Smart Update."
-"I've already been to a Samsung Experience Store. They said there was nothing they could do. It sounds like this is a fundamentally broken feature that neither of you are willing or capable of fixing."
-"I do apologize. Is there anything else I can help you with today?"
Just a heads up. I was FAR nicer than the above implies, that is a shortened version. The bottom line, Samsung and Verizon do not care that your call forwarding does not work. They do not care about you. They literally have to change ONE number, and both of them are refusing.
The only way to make Verizon listen is vote with your wallet. I personally don't want to deal with Verizon, ever. Not even consider their FIOS unless I have no alternatives.
The thing is you bought a branded watch that is custom-made by Samsung per Verizon's requirement. Samsung can't just make a change to use different code (which requires a firmware update, BTW, new Verizon firmware for the watch just released today) without Verizon's explicit request.
What phone are you using? I actually turned off auto call forwarding all together and set up conditional call forwarding on my phone. Now when I get a call my phone rings, then if I don't answer it goes to voicemail, only its the watch's voicemail. When I'm connected remotely, my phone rings first, then my watch rings and I answer normally. Works perfect without the hassle or that ugly forwarding icon on my watch's screen. Just look under phone call settings. I changed the forward when busy, forward when unanswered, and forward when unreachable to my watch's number. That's all the auto call forwarding does anyway. I'm using the note edge on at&t but I imagine it should work that way with other carriers.
I hear your pain.....mine dials *28 and *38 for sprint and they don't use those codes so I get a call forward error......they need to change it to *72 and *720. I left a comment on the gear manager app....and they were going to send it to the software engineers for a change on a future update.....but you knows how that goes. As of now......I just down loaded a app.....and when I go jogging I use the app on the phone to call forward to the gs while the phone is at the house. Now I was playing with a file in gear manager that has the codes for call forwarding...but I could not get the changes to stick.......if they would of.....the problem would of been fixed. I guess I will be waiting for an update and hope for the best.
It would of been great if you would of ref this file below to samsung when you had them on the phone.
This was the file:
data/data/com.samsung.:android.hostmanager/files/callfwdlist.xml
supergame2038 said:
Just spent an hour and a half on the phone with Verizon, and then Samsung. Remember that *92 issue where hitting "Turn on Call Forwarding" in the Gear Manager or on the Gear S would try dialing *92 (a non-working short code) instead of *72? Yeah, that's still a thing. And Verizon and Samsung don't care. They don't care about you. Here is a run-down of what I went through in almost 2 hours.
-Call Verizon
-"I can activate call forwarding on your phone?"
-"No, I just want the *92 short code added to my area's cell switch."
-"You sure you don't want me to activate call forwarding?"
-"No, I can do that MANUALLY myself fine. I need either *92 to be added to my area's cell switch as a "call forwarding" short code, or I need someone to fix my Gear Manager/Gear S so that it dials *72 instead of *92."
-"OK, let me ask our engineer."
...
-"He says that would interfere with FiOS."
-"Other people in other areas have been able to do it fine."
-"He says it would interfere with FiOS."
-"OK...then can you fix the Gear Manager/Gear S so it dials *72 instead of *92?"
-"I mean...we can call Samsung."
-"OK, lets do that."
-3-Way Call with Samsung
-"We're not responsible for call forwarding. That's the carrier (Verizon)."
-"That makes NO sense. I can manually dial *72 then the number fine. It's only through your Samsung Gear Manager and Samsung Gear S firmware when I hit "turn on call forwarding" that it tries to dial *92. It's YOUR app that has the problem."
-"We're not responsible for call forwarding. That's the carrier."
-"So, you're saying that the reason my SAMSUNG Gear Manager app dials *92 rather than the *72 EVERYONE ELSE knows as the proper code...is Verizon?"
-"Yes. We're not responsible for call forwarding. That's the carrier."
-"So...you can't look into it and see if there's a way to update anything?"
-"You can take it to a Samsung Experience Store and they can try doing a Smart Update."
-"I've already been to a Samsung Experience Store. They said there was nothing they could do. It sounds like this is a fundamentally broken feature that neither of you are willing or capable of fixing."
-"I do apologize. Is there anything else I can help you with today?"
Just a heads up. I was FAR nicer than the above implies, that is a shortened version. The bottom line, Samsung and Verizon do not care that your call forwarding does not work. They do not care about you. They literally have to change ONE number, and both of them are refusing.
Click to expand...
Click to collapse
The call forwarding feature works just fine on my Verizon Note Edge paired with my Verizon Gear S
Unknown Zone said:
I hear your pain.....mine dials *28 and *38 for sprint and they don't use those codes so I get a call forward error......they need to change it to *72 and *720. I left a comment on the gear manager app....and they were going to send it to the software engineers for a change on a future update.....but you knows how that goes. As of now......I just down loaded a app.....and when I go jogging I use the app on the phone to call forward to the gs while the phone is at the house.
Click to expand...
Click to collapse
How do you guys know what code your phone dials? I have an ATT Gear S with a Tmo sim and a Tmo Note. Call forwarding sometimes does not work, and sometimes does, but I could never figure out why that is.
Also, what's the name of the call forwarding app that you use?
xendula said:
How do you guys know what code your phone dials? I have an ATT Gear S with a Tmo sim and a Tmo Note. Call forwarding sometimes does not work, and sometimes does, but I could never figure out why that is.
Also, what's the name of the call forwarding app that you use?
Click to expand...
Click to collapse
For the call forwarding codes you can google your carrier call forwarding codes for that info.
Don't quote me on this, but I know on some phones in the call setting you can edit the call forwarding codes. But, I think the Gear Manager overrides the phone and uses this own. I have the Sprint Note2 (4.4.2) and I don't have that call forwarding setting in the call setting menu. So either I enter it manually on the key pad or have a program do it for me. The Gear Manager has a call forwarding list in the program that it uses when you use the gs to call forward. The codes that it uses for sprint is wrong and needs to be fixed...so for me I have to override manually with a program.
I use "Simple Call Forwarding" play store.
Unknown Zone said:
For the call forwarding codes you can google your carrier call forwarding codes for that info.
Don't quote me on this, but I know on some phones in the call setting you can edit the call forwarding codes. But, I think the Gear Manager overrides the phone and uses this own. I have the Sprint Note2 (4.4.2) and I don't have that call forwarding setting in the call setting menu. So either I enter it manually on the key pad or have a program do it for me. The Gear Manager has a call forwarding list in the program that it uses when you use the gs to call forward. The codes that it uses for sprint is wrong and needs to be fixed...so for me I have to override manually with a program.
I use "Simple Call Forwarding" play store.
Click to expand...
Click to collapse
By poking around in Gear Mgr, I don't see any such code, so where exactly is it listed? I see my Gear's number under auto call forwarding, but no short code anywhere.
Also, thanks for the app tip!
The short code is hard coded. You won't find it. Gear S auto-forwarding is designed to use conditional forwarding for all carriers. I guess Samsung wants you to be able to pick up calls from either device. The thing is on AT&T, I can easily change my conditional call forwarding time via another short code dialing. But you can't do so with Verizon IIRC. Right now, I have my forwarding wait time set to 15 seconds and tell my friends and family to be patient.
You can google your carrier's conditional forwarding code on the internet.
xendula said:
By poking around in Gear Mgr, I don't see any such code, so where exactly is it listed? I see my Gear's number under auto call forwarding, but no short code anywhere.
Also, thanks for the app tip!
Click to expand...
Click to collapse
foxbat121 said:
The short code is hard coded. You won't find it. Gear S auto-forwarding is designed to use conditional forwarding for all carriers. I guess Samsung wants you to be able to pick up calls from either device. The thing is on AT&T, I can easily change my conditional call forwarding time via another short code dialing. But you can't do so with Verizon IIRC. Right now, I have my forwarding wait time set to 15 seconds and tell my friends and family to be patient.
You can google your carrier's conditional forwarding code on the internet.
Click to expand...
Click to collapse
This was the file:
data/data/com.samsung.:android.hostmanager/files/callfwdlist.xml
This file has the list of codes to use.....I tried to edit but the changes would not stick.
foxbat121 said:
The short code is hard coded. You won't find it. Gear S auto-forwarding is designed to use conditional forwarding for all carriers. I guess Samsung wants you to be able to pick up calls from either device. The thing is on AT&T, I can easily change my conditional call forwarding time via another short code dialing. But you can't do so with Verizon IIRC. Right now, I have my forwarding wait time set to 15 seconds and tell my friends and family to be patient.
You can google your carrier's conditional forwarding code on the internet.
Click to expand...
Click to collapse
Thanks. Lots to research at this point!
I don't know if it'll help any but I left samsung and email about this. I suggest everyone does it. I just said they should let us manually put in whatever we want.
My local area cell switch did not have the *92 short code programmed into it. So the auto forward from the watch failed every time. After talking with Verizon Tech support & Samsung (both pointing fingers at each other) I stopped the insanity and ended the call. I called Verizon back a few days later and got a tech support person that had a Gear S in their hand. He was located in a California call center and was able to get *92 auto forward from the Gear S to work perfectly. So he entered a ticket with the Verizon "Network team" to have the *92 shortcode added. A few days later someone from Verizon called me back to make sure the changes he made fixed the problem. It did not. So I explained to him the problem of my local switch not having the *92 shortcode and he said he would fix it and call me back. He called back in about 30 minutes and it worked!
I wish they would allow you to change the short code used to auto forward calls. I would prefer the *72 immediate forward over the *92 no answer forward.
But at least the keyboard now has a $ (dollar sign) as part of the keyboard symbols (newest software update), so slow progress is being made.
I expect that new features and more compatibility will be in future FW updates but they really need to make the Gear S compatible with more smart phones to gain greater sales! They also need to better explain in their advertising the true un-tethered features (like not needing the phone to make calls).
TL