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
Related
I would like to find a way to send incoming "Private number" calls to voicemail, without downloading an app (with the security risks involved with this, as all apps I found want to read phone #, all of my contacts, and have access to the internet).
In Googling I found that on other, older, phones you could create a contact with "Private number" in the mobile phone field and select the "All calls to voicemail". I tried this on my Galaxy Nexus running 4.0.4 and it doesn't seem to be working.
Is there another built-in procedure that works to accomplish this?
Or does anybody know an app that is not a security risk (i.e. does not request access to the internet and/or my phone and/or my contacts)?
BTW, these are the permissions that one of these Apps (this one called Calls Blacklist) is requesting:
DIRECTLY CALL PHONE NUMBERS
SEND SMS MESSAGES
RECEIVE SMS
READ SMS OR MMS
EDIT SMS OR MMS
NETWORK COMMUNICATION
FULL INTERNET ACCESS
READ CONTACT DATA
WRITE CONTACT DATA
READ PHONE STATE AND IDENTITY
INTERCEPT OUTGOING CALLS
MODIFY/DELETE USB STORAGE CONTENTS MODIFY/DELETE SD CARD CONTENTS
RETRIEVE RUNNING APPS
CHANGE WI-FI STATE
PREVENT TABLET FROM SLEEPING PREVENT PHONE FROM SLEEPING
MODIFY GLOBAL SYSTEM SETTINGS
CHANGE/INTERCEPT NETWORK SETTINGS AND TRAFFIC
DISPLAY SYSTEM-LEVEL ALERTS
You can't have an app send private calls to voicemail, but not be granted permission to see who is calling.
That would be like me saying to you; "I'm sorry sir, you're not appropriately dressed for this restaurant." over the phone.
Read reviews, not all of those apps are bad (some are though), and most of them will do exactly what you are looking to accomplish.
Security risks? The app kinda needs that information. You're better off not installing any apps as any of them could steal your valuable phone number.
Sent from my Galaxy Nexus running AOKP+Franco
Liskrig said:
You can't have an app send private calls to voicemail, but not be granted permission to see who is calling.
Click to expand...
Click to collapse
Duh, of course, it's not listed above as one of the unneeded permissions above.
But none of these are even remotely needed to do the job:
INTERCEPT OUTGOING CALLS
FULL INTERNET ACCESS
READ CONTACT DATA
WRITE CONTACT DATA
RETRIEVE RUNNING APPS
DIRECTLY CALL PHONE NUMBERS
SEND SMS MESSAGES
EDIT SMS OR MMS
Liskrig said:
Read reviews, not all of those apps are bad (some are though), and most of them will do exactly what you are looking to accomplish.
Click to expand...
Click to collapse
How exactly could a reviewer know that the app author isn't selling all of my contacts to some spammer? The tenet of good security is to not leave the door open unecessarily.
Besides the fact that yet another app means yet another thing that can go wrong (battery drain, system instability, etc.)
Back to the original question: "Is there another built-in procedure that works to accomplish this?"
hillrider said:
Duh, of course!
But none of these are needed to do the job:
INTERCEPT OUTGOING CALLS
FULL INTERNET ACCESS
READ CONTACT DATA
WRITE CONTACT DATA
RETRIEVE RUNNING APPS
How exactly could a reviewer know that the app author isn't selling all of my contacts to some spammer? The tenet of good security is to not leave the door open unecessarily.
Click to expand...
Click to collapse
Get one that doesn't ask for those permissions then. You're so paranoid that maybe a smartphone just isn't for you. Ever thought of who could be hacking your Wi-fi? They could steal and intercept ANYTHING sent through your home internet.
Sent from my Galaxy Nexus running AOKP+Franco
theking_13 said:
Get one that doesn't ask for those permissions then.
Click to expand...
Click to collapse
None found, hence this thread.
A response to the OP, without flaming and personal attacks would be greatly appreciated.
theking_13 said:
... You're so paranoid that maybe a smartphone just isn't for you...
Sent from my Galaxy Nexus running AOKP+Franco
Click to expand...
Click to collapse
+1
If you're willing to install Google Voice (and really, it doesn't matter what permissions it asks for, you're running Google's OS which has access to EVERYTHING, so there's not much to think about) and switch to a Google Voice number, you can set it through the website settings that anonymous callers are directly routed to voicemail.
copkay said:
If you're willing to install Google Voice (and really, it doesn't matter what permissions it asks for, you're running Google's OS which has access to EVERYTHING, so there's not much to think about)
Click to expand...
Click to collapse
Agree about this--somehow I got painted as someone who trusts nobody, but of course while I wouldn't give my house keys to anyone, friends and cleaning service all have them.I do run many apps from trusted providers!
copkay said:
and switch to a Google Voice number
Click to expand...
Click to collapse
This is the issue: "Private number" callers will still call my regular, non Google Voice number, so it doesn't really do the trick.[/QUOTE]
So it seems that Google removed a feature that was available in previous versions of Android? Seems strange...
hillrider said:
Agree about this--somehow I got painted as someone who trusts nobody, but of course while I wouldn't give my house keys to anyone, friends and cleaning service all have them.I do run many apps from trusted providers!This is the issue: "Private number" callers will still call my regular, non Google Voice number, so it doesn't really do the trick.
So it seems that Google removed a feature that was available in previous versions of Android? Seems strange...
Click to expand...
Click to collapse
Yeah, the replies haven't been particularly helpful so far. It's not "paranoid" to at least question the security of these apps, although the most popular ones are most likely fine.
You have a point with the non-Voice number. There's also the "no-turning-back" solution of porting your existing number to Google Voice for $20, which would then fix the problem, but it's not particularly ideal unless you're 100% sold on GV.
hillrider said:
Agree about this--somehow I got painted as someone who trusts nobody, but of course while I wouldn't give my house keys to anyone, friends and cleaning service all have them.I do run many apps from trusted providers!This is the issue: "Private number" callers will still call my regular, non Google Voice number, so it doesn't really do the trick.
So it seems that Google removed a feature that was available in previous versions of Android? Seems strange...
Click to expand...
Click to collapse
Port your actual phone number to Google Voice and ask for a new one from the carrier. Thats what I did. I setup a contact in my phone with my old number and have it setup to send the caller ID as my old number. So any call to that number all display as "Personal Call". The carrier number is my "Work Number".
I actually have 2 Google Voice numbers and my normal Verizon one (3 total). One for Personal, one for my side Website business, and my normal job.
I don't restrict any callers but there are options in there for unknowns and the likes. At least you can setup CALL SCREENING, where it asks for the persons name. So I can answer ANY call, it will say, "Call from... Donut Marketing" and it gives me 2 options, 1 to take the call... and 2 to send to VM.
If you press 2, it then says, "Ok I've sent the caller to VM. Press STAR at any time to join the call". So if the VM is someone I WANT to speak with, I just pop in and say Hi. Most Marketers will shy away from leaving their name... no name, no call. They typically hang up immediately. Still prevents me from having to talk to them and try to get off the phone.
Even when they do leave me a Google Voice Mail, it gets translated to text and emailed to me so I can read it seconds after they've left it. Then just delete like a normal email.
Super easy.
You can probably also call up your carrier and say you are getting lots of Marketing calls from Unknown numbers and want them blocked. They'll probably want to charge you a fee... but maybe not.
player911 said:
Port your actual phone number to Google Voice and ask for a new one from the carrier. Thats what I did. I setup a contact in my phone with my old number and have it setup to send the caller ID as my old number. So any call to that number all display as "Personal Call". The carrier number is my "Work Number".
Click to expand...
Click to collapse
how did you get verizon to port your number without killing your contract? i just called and they said its not possible.
Root call blocker does this.
Both my T989 (Galaxy II) and T999 (Galaxy III) are setup to use google voice for all calls.
On my T989 the call logs showed the numbers of the contacts I dialed in the call log and I believe when I was dialing out.
On the T999 the call logs show the google voice number that bridges the call, not the callers phone number and shows the same when dialing out.
I can't seem to figure out how to fix this so the contact's name/number is shown in the call logs rather than the number the phone dialed to connect the call.
Anyone had and fixed this issue?
Thanks!
I'm experiencing the same issue with outbound google voice calls and the stock dialer logs.
Thanks. It's nice to know I'm not the only one having this problem.
by any chance is this working as expected for anyone? hard to believe no one else has noticed and commented.
seeing the random outbound number in the dialer's call log is frustrating.
Same issue here on my AT&T Samsung Galaxy S III
Same here.
having the same problem as well on my SGS 3... works as expected on my HTC 1XL. seems you can redial the number you intended to dial from the call log.
ronin4740 said:
Both my T989 (Galaxy II) and T999 (Galaxy III) are setup to use google voice for all calls.
On my T989 the call logs showed the numbers of the contacts I dialed in the call log and I believe when I was dialing out.
On the T999 the call logs show the google voice number that bridges the call, not the callers phone number and shows the same when dialing out.
I can't seem to figure out how to fix this so the contact's name/number is shown in the call logs rather than the number the phone dialed to connect the call.
Anyone had and fixed this issue?
Thanks!
Click to expand...
Click to collapse
same problems on my I747 (AT&T S3). Very annoying.
Ditto. Very frustrating. It seems to my limited brain that it might be the phone apk taking it's data from a network source rather than the phone's dialer. I'm contemplating trying a different model's phone.apk, but I really need my phone to work, and I haven't flashed a ROM yet on this one.
No more comments since, have you guys figured out how to fix this. If yes, kindly post the solution.
This is ridiculous, I am seriously considering taking this (otherwise a fine) phone back to store.
This bug is a deal breaker for me. Good phone/hardware/software design should follow standards.
Janis said:
Ditto. Very frustrating. It seems to my limited brain that it might be the phone apk taking it's data from a network source rather than the phone's dialer. I'm contemplating trying a different model's phone.apk, but I really need my phone to work, and I haven't flashed a ROM yet on this one.
Click to expand...
Click to collapse
---------- Post added at 10:12 PM ---------- Previous post was at 09:40 PM ----------
Seriously, this is absolutely a huge annoyance. Completely a deal breaker. I am going to take this phone back if this can't be fixed.
I refuse to deal with this. I need GV to work as intended. I need to have this ANDROID phone behave like an android phone. If I wanted a phone controlled by the manufacturer, I would buy the crap iPhone.
Really, either Samsung fixes this issue within this week, or this phone is going back.
cortez.i said:
having the same problem as well on my SGS 3... works as expected on my HTC 1XL. seems you can redial the number you intended to dial from the call log.
Click to expand...
Click to collapse
ragarwal74 said:
No more comments since, have you guys figured out how to fix this. If yes, kindly post the solution.
This is ridiculous, I am seriously considering taking this (otherwise a fine) phone back to store.
This bug is a deal breaker for me. Good phone/hardware/software design should follow standards.
---------- Post added at 10:12 PM ---------- Previous post was at 09:40 PM ----------
Seriously, this is absolutely a huge annoyance. Completely a deal breaker. I am going to take this phone back if this can't be fixed.
I refuse to deal with this. I need GV to work as intended. I need to have this ANDROID phone behave like an android phone. If I wanted a phone controlled by the manufacturer, I would buy the crap iPhone.
Really, either Samsung fixes this issue within this week, or this phone is going back.
Click to expand...
Click to collapse
Just install one of the many alt dialers till you find one that works how you want it to, no need to get all hysterical over this so called bug
z0phi3l said:
Just install one of the many alt dialers till you find one that works how you want it to, no need to get all hysterical over this so called bug
Click to expand...
Click to collapse
Has anyone found a dialer that will work. I tried about 5 and still the same issue.
I have the same problem with GV and Galaxy S3.
Did you ever find a solution?
ragarwal74 said:
No more comments since, have you guys figured out how to fix this. If yes, kindly post the solution.
This is ridiculous, I am seriously considering taking this (otherwise a fine) phone back to store.
This bug is a deal breaker for me. Good phone/hardware/software design should follow standards.
---------- Post added at 10:12 PM ---------- Previous post was at 09:40 PM ----------
Seriously, this is absolutely a huge annoyance. Completely a deal breaker. I am going to take this phone back if this can't be fixed.
I refuse to deal with this. I need GV to work as intended. I need to have this ANDROID phone behave like an android phone. If I wanted a phone controlled by the manufacturer, I would buy the crap iPhone.
Really, either Samsung fixes this issue within this week, or this phone is going back.
Click to expand...
Click to collapse
Can you explain the problem better. I think my iPad shows the random google number too. If that's what you're talking about.
When your phone is set to use GV when dialing then GV does use some (random?) number (say you dial 202-123-1234 GV might show dialing 617-444-3333) but then in the Log you would see the number you dialed (202-123-1234) not the num that GV used (617-444-3333). This is how it works in other phones that I have used. Bug is with the Galaxy S3 that show the GV number in the log. If you click on the GV num that appears in the log you will be connected correctly, but it's beyond annoying to not be able to see/find numbers/people (people cause the contacts are associated with the real number, not the one that GV uses).
I'm getting there, I think lol.
Are you dialing out using the phone app? Or gv app? Can you make the call/see it correctly if you dial out through the web browser?
And what you're saying is that the call log shows the google service number not what was dialed.
In my stock phone app my call log shows the number of a person who called my gv number and was forwarded to me. Do incomming calls display correctly?
I am dialing out using the Phone app.
When you say the "call see it" I figure you mean the Log. I don't know how to dial using Voice (GV on the phone) as I don't see a dial pad there as I do on my desktop computer.
>>And what you're saying is that the call log shows the google service number not what was dialed.
EXACTLY
Install google chrome and navigate to the voice site. I don't really use gv anymore but it could interest you. I found using it through the web always gave a better experience because it's more robust.
In the phone app is it just outgoing that's messed up or incoming too? I didn't even know the stock dialer could be used for gv
going to the website, and using the call back, it works fine - but that defeats the whole beauty of being able to use the phone dialer and transparently it uses GV (this might be new to Android v 4). The setting for this is in Voice (android app for GV) under settings, Making calls. For me the reason I want to use GV for all outgoing calls is so that ppl know me by the GV number since my SIM changes often and if they get the SIM number they tend to save it, later trying to reach me at this number and finding it's no longer in use....
sun365 said:
I am dialing out using the Phone app.
When you say the "call see it" I figure you mean the Log. I don't know how to dial using Voice (GV on the phone) as I don't see a dial pad there as I do on my desktop computer.
>>And what you're saying is that the call log shows the google service number not what was dialed.
EXACTLY
Click to expand...
Click to collapse
this is an issue with the Touch Wiz ROM and Google Voice.. if i use a stock TouchWiz ROM and GV, and call a contact, then the service number is in the call log. when i use the CM10 ROM and, i call a contact, the call log lists contact phone number. either way, i'm disappointed that Samsung and/or Google haven't addressed this issue. t
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.
Has anyone noticed that Google Voice no longer integrates into the stock Samsung dialer app? Basically the problem is, if I use Google Voice for an outgoing call, the number that shows up in the call log is the Google Voice proxy phone center, not the actual number I'm dialing. It also shows the proxy phone center number on the screen while the call is ongoing. On the original Note (which now runs ICS), the stock Samsung dialer seems to work as you would expect and only shows the number of the person you are actually calling.
I'm hoping there is a fix for this somewhere. I'm not sure if similar threads for the Galaxy S III that I've seen are applicable to the Note II since it is running Jellybean, and it seems like Samsung has updated the dialer app (it looks different from the ICS dialer on the original Note)
Yep, I saw that yesterday
Yes, gv on this device is def wonky but as long as it works I'm not gonna complain.
Then again I'm seeing gv is acting up on other devices as well. Is google slowly dropping support? Hasn't been updated since beginning of year I think.
Android.Addiction said:
Has anyone noticed that Google Voice no longer integrates into the stock Samsung dialer app? Basically the problem is, if I use Google Voice for an outgoing call, the number that shows up in the call log is the Google Voice proxy phone center, not the actual number I'm dialing. It also shows the proxy phone center number on the screen while the call is ongoing. On the original Note (which now runs ICS), the stock Samsung dialer seems to work as you would expect and only shows the number of the person you are actually calling.
I'm hoping there is a fix for this somewhere. I'm not sure if similar threads for the Galaxy S III that I've seen are applicable to the Note II since it is running Jellybean, and it seems like Samsung has updated the dialer app (it looks different from the ICS dialer on the original Note)
Click to expand...
Click to collapse
Yeah I noticed it too. Here's how I'm dealing with it:
Assuming you set things correctly in the Google Voice app...
Calls - I don't call many people from my contacts anyway so every time that proxy number shows, I save that to the contact. I learned that each contact receives a specific number, so it's been working.
Texts - I downloaded an app called GV Integration. It costs $5. This app makes sure that all your texts use you google voice number going out.
Note: You may not need the integration app if you save all the proxy numbers in your contacts but I found the integration app before saving the numbers. The only annoying thing now is receiving the texts with the person's name also in the message. I hope all this gets fixed too though. This is one this Sprint has the upper hand on for every phone.
this is the same behavior on my S3 as well. not sure it's a GV thing though, cuz on my HOXL, GV stores the contact number in the log and not the bridge number.
I just refer to GV's own logs instead of the phone-dialer log. I do all texting from GV itself, and I only give out my GV number (not the native cell number) for others to text me. That way, all the texting is handled in GV, and comes for free without needing a texting plan from my carrier.
My S3 on Verizon did this initially, then started working correctly, the call log would show the number I called instead of the GV proxy number.
My AT&T Note 2 is showing the GV proxy number, which I find annoying and wrong.
Google/Samsung/AT&T: I would like my call log to show the phone number of outgoing calls when I dial with GV. Thanks
Bump
has anyone found a fix for this? This really bugs me..
same here. is google dropping GV?
This isn't an issue on the Nexus phones or the HOX. It has to have something to with the Touchwiz dialer.
Sent from my SAMSUNG-SGH-I317 using xda premium
Google Voice update came out today but alas the issue persists...so it must be the dialer that's the cause.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
dnanj said:
Google Voice update came out today but alas the issue persists...so it must be the dialer that's the cause.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
i'm using a recently released, ported JB 4.1.2 GT-N7105 ROM with the newest Google Voice app and all of my outgoing calls in the call log show the number i dialed - not the proxy/bridge number. however, i'm using the same updated GV app on my SGS3 and it still lists the proxy/bridge number in the call log. stumped.
cortez.i said:
i'm using a recently released, ported JB 4.1.2 GT-N7105 ROM with the newest Google Voice app and all of my outgoing calls in the call log show the number i dialed - not the proxy/bridge number. however, i'm using the same updated GV app on my SGS3 and it still lists the proxy/bridge number in the call log. stumped.
Click to expand...
Click to collapse
Sounds to me like the ported JB 4.1.2 GT-N7105 rom has a different or updated dialer maybe?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
cortez.i said:
i'm using a recently released, ported JB 4.1.2 GT-N7105 ROM with the newest Google Voice app and all of my outgoing calls in the call log show the number i dialed - not the proxy/bridge number. however, i'm using the same updated GV app on my SGS3 and it still lists the proxy/bridge number in the call log. stumped.
Click to expand...
Click to collapse
Which n7105 rom did you get gv to work with? Mind posting a link to it?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
frewys said:
Which n7105 rom did you get gv to work with? Mind posting a link to it?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
I think it might be this one: http://forum.xda-developers.com/showthread.php?t=2016575
OrangesOfCourse said:
I think it might be this one: http://forum.xda-developers.com/showthread.php?t=2016575
Click to expand...
Click to collapse
Okay. Thanks. I am continuing with this one: http://forum.xda-developers.com/showthread.php?p=33950457 but they have the same base.. Crossing my fingers for working gv.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
frewys said:
Which n7105 rom did you get gv to work with? Mind posting a link to it?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
i'm using this GT-N7105 ROM with a stock at&t kernel, not the one that's included with the ROM
frewys said:
Okay. Thanks. I am continuing with this one: http://forum.xda-developers.com/showthread.php?p=33950457 but they have the same base.. Crossing my fingers for working gv.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Let me know if that works for you... I'm rom shopping...
The problem seems to be fixed in the recent OTA 4.1.2 update.
Is it working for anyone using Cleanrom? I'm on version 3.5 and am not seeing it. :|
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