Hey guys,
I'd love to make use of the text response feature when someone calls me but there doesn't seem to be a Google Voice intent or option anywhere is there?
I heavily use my Google Voice number to the point I don't give out my cell phone number! I just tested ignoring a call with the text option and the text came from my cell phone number.
Has anyone figured out how to get it to use Google Voice? I have successfully configured texting from contacts/people and even voice actions because both had intents that popped up but nothing for the decline call feature.
Same issue here. Searched around, haven't been able to find an answer yet. I apologize if I missed something - Any help would be greatly appreciated.
This may be something I'm interested in for future use.
Sent from my Sensation using xda premium
Anybody?
Sorry, just trying to bump this thread. It seems ridiculous to me that Google would release a flagship Android device that doesn't allow full integration with another major product so naturally related, Google Voice - especially considering how hard they've been pushing integration with Google+. (I'd love VOIP to be activated too, but that's another can of worms...)
Plus, this seems like a pretty simple issue since GV can be made the default for SMS quite easily elsewhere in ICS (and Gingerbread, Froyo) as the OP states. Hopefully I'm just mistaken, thanks for the help!
Seems like certain roms have issues with Google Voice. I use Google Voice for my voice mail, and with certain roms, when I go to dial out from Google Voice, whether it be using my GV number or my native Verizon number, a +1 is appended to the phone number and I get an error stating the network is busy.
At the moment, I am using TSM Gingerbang Evolved and it works fine. I get the network issue with Virtuous Unity (is the name right?) and more recently with RunnyDroid. I like some of the features of these other ROMS but cant put my finger on what the common factor is that makes Google Voice cause problems with dialing.
I'd like any assistance at all on this.. I think I may have read elsewhere that there are issues with Sense 3.0 and up with Google Voice, but I cant seem to locate that article now.
Is there no way to properly use Google Voice with higher versions of Sense?
Thanks,
-myk
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Anybody? Are any other users experiencing the same issue? I read a few posts on random forums where some had the same problem, but no resolution other than trying a different ROM. Perhaps I should change my question..
What Sense-based ROMs have you guys used that still works great with Google Voice dialing out from a voicemail?
Seriously? I can't be the only one experiencing this. Anybody at all? Maybe I'm the only one who uses GV.
Sorry man, I don't use it. I read something about having to pay for voicemail using it one time and just stopped
Sent from my Mikrunny'd Vivo_w
myk.robinson said:
Seriously? I can't be the only one experiencing this. Anybody at all? Maybe I'm the only one who uses GV.
Click to expand...
Click to collapse
You're not the only one having this issue. I'm experiencing the same problem as well but I just did the work around and edit the number i'm dialing out to delete the + from the number. It's a pain in the butt if you do it all the time but I normally just "send a text" to that number, edit the number, delete the +, copy and paste it into the phone app and dial out from there. A lot of extra steps but it works.
I'm sure someone will get around to figuring out why this is happening
Myk
This bothered me so much over the past few days I finally did some digging and I found a great workaround. It's actually an app on the market. It can edit any number you dial automatically to remove or add whatever it needs to.
Prefixer
By 253°Below
Run the app, Menu>Add Rule>Manual>Outgoing
You can label the title whatever you want.
Make sure the Rule is enabled
Under "When Number Matches" Type this in
\+?[0-9]{7,}
That tells it if a number is at least 7 digits long preceded by a + in the beginning.
During Days>Mon-Sun
From Time> 00:00
To Time> 23:59
Remove Characters
\+[1]
That's it. Try dialing a number from anywhere. Some of my facebook contacts automatically have a +1 in front of them and i'm now able to call without editing the number manually every single time.
THANK YOU!
That was driving me crazy...
thank you very much, this works like a charm and makes ROMs much more usable
Wonder why the devs of these ROMs don't include something like this, as you would think everyone has this problem. It may not be an issue with the built in phone call log, but definitely is if you use Google Voice.
thanks again
Anybody else unable to locate a phone while Google Voice is integrated with Sprint? My two lines with GV always report "unable to locate" Go into Voice's settings and disable integration and it works great. Third line is always quickly located.
I have searched XDA, Sprint and Google and haven't found even a reference to the issue. Want to make sure it's not something on my end.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Here's my explanation:
Yah know how you can use your housephone/landline (if you have one) or someone else's phone and call yours. For example, if your phone number is: (860) 555-1255?
You use another phone and call your phone at that number, then when your greeting starts you press * and put in your passcode, then GV says "to Place a Call, Press 2". That means that you can call with two different phones, so as of now, the locator gets confused when it sees a Sprint phone and another number...
So basically it's like having two phones with one number, (which with Google Voice it is possible).
The locator gets really confused and doesn't work... Hopefully Sprint will catch up and fix this...
That's my theory.
Sent from my Epic Touch running Blazer Rom via xda premium
I wouldn't think that GV would break it because neither the MDN or MIN change. Although I'm familiar with the operation of GV on its own, I'm not sure what changes behind-the-scenes after integration. Hopefully it's just a simple fix.
I'm just surprised that I didn't find any posts or faq dealing with it. One of the reasons for my low post count is I can usually find whatever answer I'm looking for without needing to ask. I'm pretty sure that almost every question has been asked and answered on a forum somewhere.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
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