Related
Posting this to see if anyone else has this, and if any one knows how to make it work.
I use Google Voice for my international calls, but after the upgrade the dialer takes over, Google voice can not be used to "only make international calls"
i have to use "ask for every call" which is not the best solution.
[EDIT] that option does not work either
I'm having the exact same problem.
I even made several international phone calls, thinking that maybe Google Voice was running in the background... now I'll get hit with the charges for international calls from AT&T :s
Any solution to this problem?
I'm using the X10i 2.1 Global firmware on a X10a (AT&T)
hope this helps
http://code.google.com/p/android/issues/detail?id=9000
Looks like as sony do not use default dialer it is going to be a problem
alankstiyo said:
hope this helps
http://code.google.com/p/android/issues/detail?id=9000
Click to expand...
Click to collapse
unfortunately the suggested process does not work
I found a way to make calls by google voice. I went to the browser, went to the google voice website, and from there, I placed the call. Then I received the phone call from my google number, and it connected me to the number I was calling.
It's more troublesome than just using the app, but it is a workaround.
Any other ideas or solutions?
zch_fernando said:
I found a way to make calls by google voice. I went to the browser, went to the google voice website, and from there, I placed the call. Then I received the phone call from my google number, and it connected me to the number I was calling.
It's more troublesome than just using the app, but it is a workaround.
Any other ideas or solutions?
Click to expand...
Click to collapse
When you do that, aren't you still using the GSM network and your sim card to have the call connected?
I am having identical problems (2.1 Nordic) and trying to use google voice over WiFi to avoid using network minutes but Sony's dialer takes over... hopefully sony or GV will update and fix this real soon... very frustrating
NUTSgoWEEE said:
When you do that, aren't you still using the GSM network and your sim card to have the call connected?
I am having identical problems (2.1 Nordic) and trying to use google voice over WiFi to avoid using network minutes but Sony's dialer takes over... hopefully sony or GV will update and fix this real soon... very frustrating
Click to expand...
Click to collapse
I use Google Voice for international calls... so I'm still using my GSM minutes, but just as a local call, not with international rates.
Have same problem. Cost me one expensive international phone call.
Generic FW, Build 2.0.A.0504 - X10i/ATT USA
GV screen comes up, then native dialer takes over. Have used workaround posted above, but naturally would just like to be able to use it as intended.
Just a heads up to anyone who has updated to 2.1.
I have the Rogers 2.1 and using AT&T as the carrier. GV does not work for ANY of my outgoing phone calls even when I specify to use GV only.
If the issue is SE's dialer, is there a way to revert back to the generic dialer?
Thanks
I'm also having this issue, only after recently upgrading my X10 to the generic 2.1 software. I wonder if anyone has found a solution yet?
I've had this problem since day 1, since I'm from Canada and use my GV to call my american / long distance friends. I have had to use the website workaround since day one, and it really bugs me. When I was working from the iPhone app, it worked properly (call me, then call the number I'm trying to call). Since switching to my X10a, I can't have it just call me, it uses the dialer directly.
So, I use up about 100-200k of my data plan to make the call. Not a big deal, just kind of annoying.
Hello everyone. I'm having a bit of an interesting issue, and while (probably) not entirely confined to my new HTC One device, I was hoping you all could give me a bit of assistance!
Yesterday I made the switch from Sprint to AT&T and received my brand new HTC One in the mail. I'm a long time Google Voice user (using since late 2009), and have used it for all texting, calling, and voicemail on all android phones I've owned. I figured when I pre-ordered my phone, for simplicity sake I would just transfer my sprint number over to AT&T so I didn't have to deal with sprint customer support cancelling my service. This seems to have caused some major problems to my use of Google Voice, however. I was able to get everything set up again, but I'm having serious issues receiving calls forwarded from Google Voice to my phone.
During my tests trying to set this up, it appears that I DO have everything configured as I had previously on Sprint. I'm able to place calls and people see my google voice caller id, I can send and receive texts through the voice app, and my conditional forwarding sends all calls (both my regular number and google voice) to google voicemail. When I receive calls, however, I'd say 95% of the time it is so slow to foward that my phone that my callers will hit voicemail before it rings my phone. The only strange thing I see in my google voice settings is that my carrier for that number keeps getting recognized as Sprint instead of AT&T.
In my troubleshooting I've linked my girlfriend's phone (sprint) to my account and a co-workers phone (at&t), both forwarded just fine immediately. At this point I'm kind of running out of ideas. I'm thinking I might run down to an AT&T after work and request a new number. Would this be a reasonable thing to do to try to solve the problem? Since i'm such a new customer, do you think I could get that 36$ new number fee waived? Not being able to receive calls forwarded from my Google Voice number is kind of a deal breaker for me, as I'm heavily reliant on that number at this point. If anyone could provide any advice/assistance it would be greatly appreciated. Thank you!
--Tald
Hi guys, I bought a G zone Commando C811 to use it as a second phone in a GSM network because I know Verizon global ready phones are unlocked and i liked this model a lot. My issue is the phone works on gsm network ok (SMS, outgoing calls and 3g data) but it is rejecting all incoming calls, phone forwards incoming call to voice mail or if VM is disabled it sounds busy. I managed to root the phone and I disabled all verizon bloatware, I've looked phone logcat and it shows that phone utils is rejecting all incoming calls as soon as they arrive and even before the phone rings.
I asked about this issue in different forums but no answer yet maybe because this phone is very new and a low stream one. I'm not a dev but I could try to find the fix myself if somebody more experienced tell me how to start to troubleshoot this issue.
I'm pretty sure if this phone was a popular one as Verizon's GS4, Droid DNA or HTC One somebody had managed to fix this for GSM users.
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
Outgoing calls are allowed but incoming ones are not!!
No call logs.
I have called at&t support and when I was on call..I tried calling my htc one m8 from my landline. Then I am able to receive the call. Once the call is ended with at&t support no more incoming calls
btw at&t guy failed to help me with the problem.
Help me pls!!!
CM version-12.1-20150731-NIGHTLY-m8
venkat457 said:
Outgoing calls are allowed but incoming ones are not!!
No call logs.
I have called at&t support and when I was on call..I tried calling my htc one m8 from my landline. Then I am able to receive the call. Once the call is ended with at&t support no more incoming calls
btw at&t guy failed to help me with the problem.
Help me pls!!!
CM version-12.1-20150731-NIGHTLY-m8
Click to expand...
Click to collapse
Did you fix the problem? Try to install another rom
This issue is affecting me too
No inbound calls unless i disable LTE. Anyone ever find a fix for this?
br3g0 said:
No inbound calls unless i disable LTE. Anyone ever find a fix for this?
Click to expand...
Click to collapse
Its a common issue on non-ATT ROMs. ATT's implementation of Voice over LTE (they call it "HD Voice") is messing with your voice calls, and probably SMS as well.
Call ATT, talk to Tier 2 customer service, and ask them to turn off HD Voice, and it should solve your issue.
They may hem or haw that it can't be done, but believe me it can (based on multiple reports here).