Related
***** FIXED ***** CALLED AT&T TO RESET VOICEMAIL ***** PLEASE REMOVE THREAD *****
I am using a stock GSM GNex, unrooted, and I noticed, when I receive calls, the caller does not go to voicemail and when I attempt to check voicemail, I am told that I do not have a voicemail box. This is a new problem, because before, I had voicemail and I set it up using AT&T. When I long press the number "1" on the dial pad I get a recording that says to enter the phone number of the party you are trying to reach. I enter my phone number and it says that the number is not listed. I can receive and make calls to anyone no problem, but voicemail all of a sudden stopped working. I went into the phone settings and checked the phone number listed as my voicemail number, it is not the same as my regular phone number, so I changed it to my number and I was getting a busy signal when I tried to check my voicemail after that. Any ideas??? I don't think calling AT&T will do me any good as they think I am using a Galaxy S2 Skyrocket. Please help, I need to get voicemails if I don't get to the phone in time!!
Thanks
I'm not sure how to fix your problem but, have you tried google voice as your voicemail client? Maybe you can use that instead.
To be honest I want to fix the issue and I don't want to use Google Voice. When I did a search before posting this I read a lot of people were using that service, but I want to get the real problem fixed. Thanks though.
Does anyone think the problem could be because I have a Galaxy S2 Skyrocket as my main phone on my plan, and that phone uses visual voicemail? And somehow now the phone won't activate voicemail because of that? When I dial my number and call myself, I get a busy tone.
1) Your VM number is either incorrectly programmed into the phone, or whoever set up your account didn't provision you with the VM feature. Call your carrier, they can verify with you whether your phone is correct or it's their system. No one on XDA can't help you with a shortcut.
2) Get Google Voice. Carrier VM systems are utter crap by comparison. That is the "real" solution to your "real problem".
The voicemail number is the same as it was when I set it up the first time. BTW, using Google Voice is not the "real" solution to my "real problem". If you don't know the answer to the question or you think no one else here will, you don't have to emphasize your love of Google Voice, I just don't want to use it so I am trying to figure out how to fix it. Thank you.
Oh, and maybe you should change your user name if you hate AT&T so much.
I use the google voice app for making calls..
For some reason it started happening since switching to ATT/New ROMs.... the call log shows the Google Voice forwarded numbers instead of the contacts i call! please help
30secs said:
I use the google voice app for making calls..
For some reason it started happening since switching to ATT/New ROMs.... the call log shows the Google Voice forwarded numbers instead of the contacts i call! please help
Click to expand...
Click to collapse
Yes this is an issue with ATT stock rom. Annoying but workaround is to use Google Voice to check outgoing call log
Sent from my SAMSUNG-SGH-I747
Just upgraded to JB last night on ATT, using GV 0.4.2.66. Phone has never been rooted, stock ATT always. Problem still exists - place a call and the log shows the relay number, not the actual dialed number. Weirdly, back in August I think, after a bout of uninstalling/reinstalling GV, it worked perfectly for a while. Then some unnoticed update broke it and it started storing relay numbers in log again, and hasn't worked since.
As I understand from the MANY other threads out there on this issue, the problem lies with Samsung and their dialer not talking to GV properly. No-one has yet to have any help from Samsung, but the hope was JB would fix it.
Nope. I use GV all the time, so this is practically a deal-breaker for me
What are the options here ? Is it possible to use the stock JB dialer instead of the Samsung Touchwiz one ? I'll root and put in a different ROM if I have to ...
Thanks -
Google Voice stores relay number in call log, not called number
Is anyone out there using google voice with the S3 (on ATT) ? Have you gotten it to store the actual number you called rather than the damn GV relay number ? This is one of the most popular phones out there, and there are a metric ton of people using GV - surely someone has it working cleanly ?
It's frustrating. No workee for me either. Can't redial.
Actually, I wish Google supported GV more. No APIs, so many things can't be done due to using GV messaging.
According to this thread:
http://forum.xda-developers.com/showpost.php?p=35616192&postcount=29
Some users (on Verizon?) are seeing it work correctly. This leads me to believe that some builds of 4.1.1 for the S3 may have this functioning correctly.
Some questions:
Does anyone know of any ROMs for the S3 that have the correct behavior with Google voice that work on ATT?
Can we take the dialer from the Verizon S3 and use it on an ATT S3?
Any other suggestions for resolution?
isaacfinnegan said:
According to this thread:
http://forum.xda-developers.com/showpost.php?p=35616192&postcount=29
Some users (on Verizon?) are seeing it work correctly. This leads me to believe that some builds of 4.1.1 for the S3 may have this functioning correctly.
Some questions:
Does anyone know of any ROMs for the S3 that have the correct behavior with Google voice that work on ATT?
Can we take the dialer from the Verizon S3 and use it on an ATT S3?
Any other suggestions for resolution?
Click to expand...
Click to collapse
This can be made to work by using a ROM based on a canadian base:
http://forum.xda-developers.com/showpost.php?p=35700701&postcount=6
Fix for Google Voice outbound call entries
30secs said:
I use the google voice app for making calls..
For some reason it started happening since switching to ATT/New ROMs.... the call log shows the Google Voice forwarded numbers instead of the contacts i call! please help
Click to expand...
Click to collapse
There's an app in the Google Play store that will fix this problem. Just search the store for "GV Outbound Call Log Repair".
jumpsquares said:
There's an app in the Google Play store that will fix this problem. Just search the store for "GV Outbound Call Log Repair".
Click to expand...
Click to collapse
Thanks for pointing it out.
Looks like it is new to market. No reviews. ANd the link to the developer's web page appears to be broken.
I'll keep an eye on it and may try it later.
Would be nice if there were a limited time free version to check out.
I'm running Liquid Smooth rom based on JB 4.1.2 and my GV is working great. I noticed your issue on other roms that I test drove but I never did any troubleshooting to find out why it was happening.
Sent from my SGH-I747 using Tapatalk 2
Halfwalker said:
Is anyone out there using google voice with the S3 (on ATT) ? Have you gotten it to store the actual number you called rather than the damn GV relay number ? This is one of the most popular phones out there, and there are a metric ton of people using GV - surely someone has it working cleanly ?
Click to expand...
Click to collapse
I need google voice also, I have tried and flashed numerous roms, this is a google problem for sure, but this rom here, is stock and it displays the correct caller info everytime, been running this rom for 4-5 days, all #'s are listed correctly....
You can keep looking for an answer as I did, and it will come up with the same issue, google+samsung....quit wasting time and use this link...
http://forum.xda-developers.com/showthread.php?t=2075639
Hope this helps, hit thanks button....good luck. BTW the newest version of google voice has issues, revert back to version before the one listed, or you will see some more issues....DO NOT TRY THAT google callback app crap...worthless...
Stock 4.1.1 was showing the routing numbers for GV in the call log, but I've flashed CM10 and the call log is showing the correct contact numbers rather than the routing numbers.
jumpsquares said:
There's an app in the Google Play store that will fix this problem. Just search the store for "GV Outbound Call Log Repair".
Click to expand...
Click to collapse
FYI...Jumpsquares is the developer of the app, it appears. He has not responded back here to my response above, so I'm assuming he is not paying any attention to this thread. Just dropped in long enough to advertise.
That being said I am happy with my stock/rooted Rom, and decided it would be easier to spend the $2 on his app than installing a whole new different ROM and reconfiguring everything. But after install, it needs email and password; it would not accept it and move on.
I unstalled for refund. Sent him an email to see what hes replies with. Will post back here if there is any progress.
Hello all,
Does anybody know any current ROM that would solve the problem of the number dialed not being shown properly in the call logs when using google voice? For example, if I can my buddy: 716-466-6666 - it should show that number instead of a Google voice's access number.
Any current ROM has this feature for the NOTE 2 would make me so happy.
Or can someone recommend a good replacement dialer app that handles the Google Voice call log properly?
rickhuizinga said:
Or can someone recommend a good replacement dialer app that handles the Google Voice call log properly?
Click to expand...
Click to collapse
disclaimer: I'm a prospective Note2 owner.
With that, I use GV as my main number and use this app:
GV Callback
for all of my outgoing calls. Hopefully it's not a Note 2 issue, cuz that would kill me. But definitely give it a try if you haven't already. I don't like how GV natively handles calls, so I set it to *never* within the Google Voice app.
Feel free to check out the themed version in my sig too.
/end shameless plug.
Let me know if GV Callback works for you, as I'm curious to know. I think both were pulled off of the play store for some reason, hence the amazon link. (there's a free version too).
No, call back does not solve the problem... we can call out just fine, it's the display of the called number not showing... but instead it's a google access number....
calixdaman said:
No, call back does not solve the problem... we can call out just fine, it's the display of the called number not showing... but instead it's a google access number....
Click to expand...
Click to collapse
Really? Wait, so dialing out using gv callback shows the routing number on the call logs, for sure? I didn't think it used a Google number to place the calls.
There's another app called gv integration. I forget right now if it deals with calls or just SMS. Will check tomor.
Sent from my Paranoid GNex
decalex said:
Really? Wait, so dialing out using gv callback shows the rooted number on the call logs, for sure? I didn't think it used a Google number to place the calls.
Sent from my Paranoid GNex
Click to expand...
Click to collapse
That's right... it shows some crazy number from google, not our buddy we just called however, on the s3 with com10 it works just great!
calixdaman said:
That's right... it shows some crazy number from google, not our buddy we just called however, on the s3 with com10 it works just great!
Click to expand...
Click to collapse
That's really weird. I will try to investigate tomor. Even try contacting the Dev.
Sent from my Paranoid GNex
For users who've sold their soul to Google by porting to GV (I'm one of them), this "bug" is really debilitating. As the OP stated, it has to do with the dialer's outgoing call log. Every single call made (through GV) logs as the proxy number dialed to connect to Google's phone system.
When I was still on my Amaze (ICS Energyrom), the stock dialer would show the contact's number as the call was initiated, and momentarily a small white pop-up box would show the GV proxy being called. That pop-up would last for about 3 seconds. The stock dialer call log, however, would show the contact's actual number.
On the SGN2, the dialer's main screen shows the random proxy number as the call is made (and for the duration of the call). Further, the stock TouchWiz dialer log will also show the proxy number. There is no way to know who you actually called by looking at the log.
The (frustratingly inefficient) workaround is to open the GV app, click on "show all labels" and selecting "placed". There, the GV call log shows the actual contact's number called.
Obviously TouchWiz does not play nicely (or at all) with GV. It is unable to differentiate between the proxy number and the actual terminating (contact) number dialed. Very frustrating.
According to my brother, who's had the SGSIII since it came out, this has been a problem since day one with TouchWiz. His fix was to go with CM10. Unfortunately, that's not an option for us (yet), and I don't know if s-pen would be supported. ;(
Oh, wow, I hadn't noticed this yet. It's like a throwback to a couple of years ago, I haven't had to worry about this in a long time.
It's interesting because on my Verizon galaxy S3, running the latest leaked jellybean ROM, but otherwise stock, the dialer does not behave the same way as this T-Mobile galaxy note 2 does. On the galaxy S3, the number displayed is the number of the contact not the Google voice routing number. I wonder what is different about the note 2, since they're both TouchWiz and jellybean.
Anyways, it's a bit tedious to set up originally, but I worked around this on older phones by adding the Google routing number as an alternate phone number for each of my contacts as I used them. That way at least the proper name and contact picture shows up in the call log even if the correct number does not.
I tried using a third-party dialer just now, and as most of you probably know, it does not record the call number properly. Bummer!
Sent from my SGH-T889 using Tapatalk 2
Wow. Ya, I use GV only as well. I get my note 2 tomorrow, and will make it my mission to figure this out.. i.e. find someone smarter to help me figure this out.
I know really... I haven't had to deal with this in a long long time..
Just to be clear, you guys have tried the app GV callback that is only on the amazon app store (afaik) right?
Sent from my Paranoid GNex
---------- Post added at 07:23 PM ---------- Previous post was at 06:59 PM ----------
Could you guys try something, until I can test:
Go to http://google.com/voice/m
Try to place an outgoing call thru there, see what number shows up in call log.
Sent from my Paranoid GNex
decalex said:
Wow. Ya, I use GV only as well. I get my note 2 tomorrow, and will make it my mission to figure this out.. i.e. find someone smarter to help me figure this out.
I know really... I haven't had to deal with this in a long long time..
Just to be clear, you guys have tried the app GV callback that is only on the amazon app store (afaik) right?
Sent from my Paranoid GNex
---------- Post added at 07:23 PM ---------- Previous post was at 06:59 PM ----------
Could you guys try something, until I can test:
Go to http://google.com/voice/m
Try to place an outgoing call thru there, see what number shows up in call log.
Sent from my Paranoid GNex
Click to expand...
Click to collapse
I've tried several "dialers", but they all get fed the same garbage from TW. As for the call back apps, I didn't specifically try the one you mentioned, but did try two others. Unless I'm missing something, they intercept the outgoing call, call your GV number (where you can hear the GV girl say, "Press 2 to make a call to a new number...") and then the app uses DTMF tones to "dial" the intended contact. I've tried that, and it does work - sort of...
The one I tried (can't recall the name) took about 20 seconds to complete the process (too slow in my book). And while the call log showed a call to MYSELF during the call, once I hung up, the app somehow edited the call log to reflect the outgoing call being made to the intended contact. That alone tells me some app developer is two steps ahead of Samsung (and possibly Google).
In any case, having used GV on HTC's for the last three years - flawlessly without any hoop-jumping or other heroic efforts - I've become spoiled to where anything less than a direct call (i.e. no call back or audible multi-dials) is a failure for me.
Coming from Galaxy NOTE 1 I didn't have any problem with google voice but yea i am having the same problem of not showing the number you are calling in call log... just today i dialed a number which was not saved in my contacts so i wanted to redial the same number again in my call log the number is not there to redial so i had look at the paper and dial it in keypad and it sucks.
I emailed one of the 3rd party developers (Xinlu), but kinda doubt I'll hear back. I know he figured this out before, and know this can be solved with one of the call back apps. Wouldn't count on Samsung or Google to fix anything like this, obviously.
Sent from my Paranoid GNex
OK.
I got my note, and finally just got to test it. I wish you guys tried the app I recommended, because it works fine. Call logs show up correctly for outgoing calls.
Free Version Google Voice Callback
Donate Version - Google Voice Callback
The dev is no longer active.. and has never answered my emails ;P
But, on the other hand, he's saved me literally hundreds of dollars over the years.
decalex said:
OK.
I got my note, and finally just got to test it. I wish you guys tried the app I recommended, because it works fine. Call logs show up correctly for outgoing calls.
Free Version Google Voice Callback
Donate Version - Google Voice Callback
The dev is no longer active.. and has never answered my emails ;P
But, on the other hand, he's saved me literally hundreds of dollars over the years.
Click to expand...
Click to collapse
We don't want to have to install a third-party app that makes you take the extra step of being called back just to get an accurate call log. Your solution may work for you, but it's not the solution for everybody. What we really like is to just see Samsung make Google voice work with their dialer log on the note2 the same way it does on the jellybean version of the galaxy S3, and every other modern mobile phone that Samsung or HTC make. Thanks for the tip but I'll just put up with this outgoing call log bug rather than having a callback option.
I'm not even sure that I'll bother cluttering up my contacts with the routing number as an alternate number for them which was the prior fixed of this on older phones. I just don't look at my outgoing call log all that often. Your mileage may vary. Thanks again
Sent from my SGH-T889 using Tapatalk 2
I'd like to see a good replacement dialer app. The Samsung dialer is so ugly. Perhaps an AOSP stock dialer?
distortedloop said:
We don't want to have to install a third-party app that makes you take the extra step of being called back just to get an accurate call log. Your solution may work for you, but it's not the solution for everybody. What we really like is to just see Samsung make Google voice work with their dialer log on the note2 the same way it does on the jellybean version of the galaxy S3, and every other modern mobile phone that Samsung or HTC make. Thanks for the tip but I'll just put up with this outgoing call log bug rather than having a callback option.
I'm not even sure that I'll bother cluttering up my contacts with the routing number as an alternate number for them which was the prior fixed of this on older phones. I just don't look at my outgoing call log all that often. Your mileage may vary. Thanks again
Click to expand...
Click to collapse
Trust me, I would love that as well.. I just don't see it happening.
I've literally written a dozen emails over the years reaching out to Samsung and Google (lol), including Vincent Pacquet.
I used to save the routing number in all of my contacts, and I *still* find myself cleaning up stray numbers. Keep in mind, the routing numbers change every once in a while. So one day (this has happened to me sev times), some or all of them won't work.
Whatev works for you though I hope a solution is on the way.
---------- Post added at 05:14 PM ---------- Previous post was at 05:13 PM ----------
rickhuizinga said:
I'd like to see a good replacement dialer app. The Samsung dialer is so ugly. Perhaps an AOSP stock dialer?
Click to expand...
Click to collapse
There are several 3rd party dialers on the market. Some are better than others, but give it a search. I used to use RocketDialer for a minute.
decalex said:
Trust me, I would love that as well.. I just don't see it happening.
I've literally written a dozen emails over the years reaching out to Samsung and Google (lol), including Vincent Pacquet.
I used to save the routing number in all of my contacts, and I *still* find myself cleaning up stray numbers. Keep in mind, the routing numbers change every once in a while. So one day (this has happened to me sev times), some or all of them won't work.
Whatev works for you though I hope a solution is on the way.
Click to expand...
Click to collapse
I mentioned this in an earlier post, but it bears repeating and might lead us to a solution on our own.
I've had a Verizon Galaxy S3 for 5-6 months, using both stock ICS and now a leaked "stock" (debloated) JB ROM. I can't say with certainty that on ICS the call log behaved the way we want it to, but I'm pretty sure it did. I can, however, say with absolute certainty, that on the "stock" JB ROM I'm using right now, it works perfectly. I just dialed two different numbers and they displayed properly, no GV routing number.
So, Samsung, ToucWiz, Google Voice and Jelly Bean for all calls on two different devices; does't make sense that it works on one and not the other.
I tried copying the dialer app over from the S3 to the Note2, and it worked as a dialer, but it didn't address the call log issue, which on the Note 2 was still borked. I'm willing to move over other apps in an effort to see what's holding us back; any suggestions? There's a listing in Titanium Backup on both phones for "Call Log", could it be that simple?
I had a SGSIII before my Note II and on AT&T anyway, the call logs showed the routing number on both ICS and leaked GB, though all the GB builds I tried were from differant carriers. I'm getting the OFFICIAL JB update that was released last night installed, and will report back if it was fixed in that update. Just as a thought, All of the SGSIII JB builds were built after the Note II, maybe in our next update this will be fixed.
---------- Post added at 09:32 AM ---------- Previous post was at 09:14 AM ----------
dj_spore said:
I had a SGSIII before my Note II and on AT&T anyway, the call logs showed the routing number on both ICS and leaked GB, though all the GB builds I tried were from differant carriers. I'm getting the OFFICIAL JB update that was released last night installed, and will report back if it was fixed in that update. Just as a thought, All of the SGSIII JB builds were built after the Note II, maybe in our next update this will be fixed.
Click to expand...
Click to collapse
I just tried on the official AT&T JB on their SGSIII, and still shows the GV routing number, I think the only time I have seen the logs correct is in AOSP roms.
Yup. Google voice logs work when I had cm10 on my Galaxy s3. Stock JB is a no go.
Sent from my SGH-T889 using Tapatalk 2
When I was using stock ICS from AT&T with my S3 the call log history on google voice would show the GV connect phone numbers in my call history instead of the phone numbers that I was calling. Can anyone with stock Jelly Bean AT&T tell me if this is still the case with AT&T JB ? This is a deal breaker for me as being able to see actual real phone numbers in the call history is a pretty basic function of the phone.
I'm on stock JB AT&T and am still seeing the GV relay numbers in the Call Log, no change from ICS.
There's a setting the JB version of Google Voice to show the Voicemail Display could that be off?
I'm looking for the apparantly missing Call settings page for forwarding the calls to GV for transcription......
Stan more than likely it will fail to forward to GV and you have to set the number manually. Also for voicemail service mine says "My Carrier" but it uses GV. No idea why, but GV works if you put it in manually.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I must have had a brain fart and forgot that Call Settings moved from the logical Network Settings menu to the sort of forgettable Dialer Settings menu in ics/jb. I really think that it should be in both.
I upgraded using the root injected version from MrRobinson and Odin, that keeps my apps and settings so that I didn't have to reconfigure Google Voice.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
This is so disappointing. Do you folks think Samsung might fix their buggy ROM on Google Voice call log soon?
If not, what's the best option? I suppose just to go CM10 ? (assuming other stock ROM derivatives might also have this problem?)
If I go CM10 by following the steps listed in the CM GS3 wiki, it will be easy to unroot and relock in case warranty is needed, right? (the wiki had huge warning fonts regarding voiding warranty).
Really hope to know what route you guys take. Google Voice is my only number known to others, and I have to call using that, and the current call log is useless, and this is 2012 with a flagship android phone ....
Thanks.
mailxd said:
This is so disappointing. Do you folks think Samsung might fix their buggy ROM on Google Voice call log soon?
If not, what's the best option? I suppose just to go CM10 ? (assuming other stock ROM derivatives might also have this problem?)
If I go CM10 by following the steps listed in the CM GS3 wiki, it will be easy to unroot and relock in case warranty is needed, right? (the wiki had huge warning fonts regarding voiding warranty).
Really hope to know what route you guys take. Google Voice is my only number known to others, and I have to call using that, and the current call log is useless, and this is 2012 with a flagship android phone ....
Thanks.
Click to expand...
Click to collapse
You just have to configure it manually, just like the original rom. Put your Google number into the forward number settings. Even though it will say that My Carrier is the answering service, select Google at least once and Google WILL BE the answer services, and you will get messages transcription in the Google voice app. If you set Google voice to do all calls or ask you how you want to call it will bring up a dialogue box. I don't use the incoming call keypad stuff, but I assume that they would work on a incoming Google call.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
stan.s said:
You just have to configure it manually, just like the original rom. Put your Google number into the forward number settings. Even though it will say that My Carrier is the answering service, select Google at least once and Google WILL BE the answer services, and you will get messages transcription in the Google voice app. If you set Google voice to do all calls or ask you how you want to call it will bring up a dialogue box. I don't use the incoming call keypad stuff, but I assume that they would work on a incoming Google call.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
GV voicemail actually worked for me, as I initially set it up by using the code provided by GV website. My concern is with the called numbers shown in the call log. They are relay numbers not my contact numbers ..... Never had this with my old Nexus One.. And I see many complaints if you search for "google voice call log numbers, galaxy s3 or galaxy note II". Some claim CM10 fixes this, but would like to get some insight into this before I void the warranty for this .... Why can't Samsung get things right out straight
mailxd said:
GV voicemail actually worked for me, as I initially set it up by using the code provided by GV website. My concern is with the called numbers shown in the call log. They are relay numbers not my contact numbers ..... Never had this with my old Nexus One.. And I see many complaints if you search for "google voice call log numbers, galaxy s3 or galaxy note II". Some claim CM10 fixes this, but would like to get some insight into this before I void the warranty for this .... Why can't Samsung get things right out straight
Click to expand...
Click to collapse
I went back to CM10. AT&T Jelly Bean was awful. I couldn't get over the hideous status bar at the top with Green color and & AT&T spam. Also dialer is complete garbage if you want to use Google Voice. Everything is working for me on CM10 except I have no bass on blue tooth.
mailxd said:
GV voicemail actually worked for me, as I initially set it up by using the code provided by GV website. My concern is with the called numbers shown in the call log. They are relay numbers not my contact numbers ..... Never had this with my old Nexus One.. And I see many complaints if you search for "google voice call log numbers, galaxy s3 or galaxy note II". Some claim CM10 fixes this, but would like to get some insight into this before I void the warranty for this .... Why can't Samsung get things right out straight
Click to expand...
Click to collapse
while the phone in the phone's call list IS a routing number, the calls' correct number are recorded in the GV widget's PLACED list. You have to use the new "Show All Labels" to get there.
buffalo77 said:
I went back to CM10. AT&T Jelly Bean was awful. I couldn't get over the hideous status bar at the top with Green color and & AT&T spam. Also dialer is complete garbage if you want to use Google Voice. Everything is working for me on CM10 except I have no bass on blue tooth.
Click to expand...
Click to collapse
Could you point me to the particular CM10 version you use with ATT GS3? Did you follow the CM wiki direction ? Also, I suppose the route back to stock/lock/unroot is easy in case we need warranty, right?
I don't care ICS/JB... as long as there are no known issues/lags/fcs, and GV voice mail and call log display work as they should (as with N1 in 2010 or even earlier...) --- I can't believe we have to work so hard to get that ...
Thanks!
I had to remove voicemail from my phone in the Voice settings page. Then I had to add GV voicemail back to my phone with the forwarding code via GV. Now I am working, though it seems to take a lot of rings to kick to voicemail. Like 10 or so.
According to this thread:
http://forum.xda-developers.com/showpost.php?p=35616192&postcount=29
Some users (on Verizon?) are seeing it work correctly. This leads me to believe that some builds of 4.1.1 for the S3 may have this functioning correctly.
Some questions:
Does anyone know of any ROMs for the S3 that have the correct behavior with Google voice that work on ATT?
Can we take the dialer from the Verizon S3 and use it on an ATT S3?
Any other suggestions for resolution?
isaacfinnegan said:
According to this thread:
http://forum.xda-developers.com/showpost.php?p=35616192&postcount=29
Some users (on Verizon?) are seeing it work correctly. This leads me to believe that some builds of 4.1.1 for the S3 may have this functioning correctly.
Some questions:
Does anyone know of any ROMs for the S3 that have the correct behavior with Google voice that work on ATT?
Can we take the dialer from the Verizon S3 and use it on an ATT S3?
Any other suggestions for resolution?
Click to expand...
Click to collapse
This can be made to work by using a ROM based on a canadian base:
http://forum.xda-developers.com/showpost.php?p=35700701&postcount=6
Okay, so I know that Wi-Fi calling isn't a feature native to AOSP, although hopefully that changes when Lollipop gets ported/released to the G3 D851, but I am curious of the options that you all are aware of, if any, so that I can have my phone ring when people call my T-Mobile number while I am out of service range. I know I could give people my google voice number, but I don't want to confuse some of the older members of my family with two different numbers to reach me at (make that 3 if you include work). Is their anyway to forward your carrier number to google voice temporarily so that I can take calls over google voice on Wi-Fi? Any other solutions? Your insight will hopefully help me out in finding a solution. Wi-Fi calling has become very important to me, but man, I really wanna start using one of the newly developed AOSP roms that have been released in the past few days.
Get a Google voice number and set up forwarding from your tmo number to the Google voice. It will ring when called, won't be able to text and use completely normally though.
Sent from my LG-D851 using XDA Free mobile app