Cannot dial out -- reset phone dialer associations? - HTC Sensation

Not sure if this is a coincidence or what, but the problem started after I flashed the new wifi calling app. Since then, I have wiped /system and reflashed ARHD to no avail.
Background: I am on TMO's $30 100 minute plan, so in an effort to conserve airtime, I use sip calling most of the time. I am using the native sip client (internet calling). I have it set to use internet calls whenever data is available. I have Google Voice set to prompt each time I make a call. If I choose to use Google Voice, it will make the call over cellular. Otherwise, it will make the call over sip. Works great, and everyone sees the same Google Voice number.
However, since flashing the new wifi calling, I am now stuck in a Google Voice prompt loop. So for the time being, I have switched off GV prompting, so all outbound calls are using the sip connection.
Here's a video to show what goes on. For some reason, the video stops recording right before going back to the GV prompt if I decline GV.
I'm trying not to wipe all data and start over, so I need to know what specifically needs to be wiped. I tried deleting data for the dialer, but it doesn't fix anything. Maybe it's an association problem with which dialer to use?
The issue is present regardless or whether wifi calling is on, regardless of if I have the GB or ICS version installed.
Help!

Related

Lower your bill w/ Llama, location based voip over wifi, + googlevoice, automatically

Hi All! This is my first guide/thread so be kind. I was looking for a way to conserve money... I am on boost prepaid and it gets quite expensive when talking, or sending a few txt messages. I found there is a way to activate unconditional call forwarding which, now unfortunately does use up minutes, once activated (*72XXXXXXXXXX for boost) calls are automatically forwarded to a google voice number, and can be deactivated (*720 on boost). There maybe many ways to call forward depending on your carrier; http://en.wikipedia.org/wiki/Call_forwarding... EDIT: now boost is charging me for forwarded calls, so I just call back with groove... the automation is still helpful though:
I think I have finally found the easiest most reliable method; you will need to enter your forwarding codes if you aren't on boost:
Needed items:
Android phone on carrier of your choice. Or you can use a tablet for wifi only calls, if your tablet doesn't have a mic, then try using a bluetooth headset.. maybe even a usb dongle if there is no bluetooth, but usb is available
Google voice (from market), and a google voice account (to send free SMS messages)
Groove IP ($4.99 one time in market to make/receive free voip calls)
LLama app (free, but we need this test version: http://www.mediafire.com/?qp5dfbqsc8ci88g) This version of LLama includes permission to dial #s, this is needed for forwarding #s, so don't use the one from the market.
In theory, groove IP can work over 3g, but in reality it doesn't for me. A short call to someone on the same cell network works at times, but calling anywhere else results in a choppy frustrating mess... therefore this guide assumes groove only works for you over wifi.
1) Get your apps installed.
2) Open Google voice, login, choose never use google voice to make calls, I had to skip the part where it asks you to setup voicemail because this requires conditional call forwarding (rings phone first then forwards to voicemail) which my carrier doesn't support. Your miles may vary here, but I recommend skipping this for now. When responding to, or sending text messages check the box 'always perform this action' and choose voice. Ask the people who txt you to now txt your google voice number. They will figure this out if you always respond to their messages via the google voice app.
3) Connect to wifi, run Groove IP, and login. Groove can be tricky to get working perfectly, but with some tweaks it works great for me. Here's my grooveIP settings:
uncheck 3g/4g calling, check accept calls on answer, under native dialer options-built in dialer preference- choose wifi only, under native dialer-exclusion numbers, enter your forwarding and 'disable' forwarding codes (dependent on carrier) separated by commas. Under audio/echo settings lower your mic gain, mine is set at -8, but yours may be different. Under miscellaneous check autostart and enter your default area code for easier dialing. Now verify calls are working by dialing the google voice test number: 9093900003. This will echo back everything you say so listen for echos/distortion, then make adjustments necessary. Use the 'troubleshooting' section under settings as a last resort, as you *should* be able to get everything working better if it is working at all at this point... tested on an evo 3d and an evo shift.
4) Run the LLama app. This will take the longest to configure of the three, click through the app and read the little one time dialogue boxes. This is a great free app, so if you find it useful, please donate some money to the developer. The configuration here may take some tweaking depending on your personal lifestyle, but I will share my current configuration(s):
a) Under Areas, I have Home, work, etc, anyplace there is a reliable wifi connection. Locations are based on cell towers and will need to be 'learned'
b) Under events: I deleted all the defaults and created:
* 'Near Hotspot': At 'locations' home, work, friends, family, school, etc (fill these in with your wifi enabled locations), delay for 4 minutes cancelling delayed if false, then turn on wifi.
* 'Wifi connected' When wifi is connected to <Any Wifi network> run Groove IP, run shortcut 'Forward' (direct dial to contact 'Forward' - *72XXXXXXXXXX), queue another event; wait one minute, disable mobile data (optional)
* 'Wifi Disconnected' When the phone is disconnected from <Any Wifi network> delay for one minute and enable mobile data
(disabling/enabling mobile data are optional but help conserve battery)
* 'Away from hotspot': When the phone disconnects from <Any Wifi network> delay for 2 minutes cancelling delayed if false, then disable Wifi, run a direct dial shortcut 'unforward' (*720), then run an android intent com.gvoip.STOP_GROOVE_IP. For this intent, choose custom, broadcast for the intent send mode, the package name is 'com.gvoip', and the action is 'com.gvoip.STOP_GROOVE_IP', leave everything else blank. This is needed because simply killing groove IP will result in it restarting automatically.
c) leave profile tab alone for now
d) troubleshoot to work out glitches... you can use the little clock icon in LLama to see history and what triggered last events
This does take some initial configuration/tweaking, but once everything works, it's just awesome. Now whenever I'm nearby a wifi hotspot I don't have to pay for minutes when making calls, and SMS through google voice is free always. Best of all, everything happens automatically so you don't forget about connecting wifi, forwarding/unforwarding, or starting/stopping groove IP. Remember to hit thanks if this helps you lower your phone bill.
**Edit**
This guide may still be helpful for a quite a few people, but unfortunately Boost is now using minutes on forwarded inbound connections... which sucks, because they weren't for about 2 months, and nothing changed. What you can do though, is leave out the forwarding aspect of this automation sequence. When people call, just don't answer and call them back right away via groove, or sms from google voice, this way you will still be able to conserve your minutes while on wifi. You still must use minutes both calling and receiving a call while driving or in motion, and google voice is always free for sms.
Terrific guide. Very detailed, thanks button pressed. Quickie question: If I begin a call on WiFi, but wander away from the hotspot coverage, it will drop correct?
Happy Thanksgiving!
Hey KidFromBigD, like your logo, I am a fellow boilermaker
To answer your question: you would drop the call if you were to disconnect from wifi or leave the area. This is why it's important to stay in range of the wifi hotspot, make sure there is no interference by doing a scan initially and setting your router to a channel not occupied. Also make sure transmission or your other torrent client isn't running full throttle, otherwise voice will sound all garbled. In terms of QoS voip should be prioritized, but I don't think all home routers treat groove with priority.
q-killer said:
Hey KidFromBigD, like your logo, I am a fellow boilermaker
Click to expand...
Click to collapse
Wow, since I installed llama, I've been obsessed with making it work for me. Truly haven't even scratched the surface of what this thing can do. Of course your original post described how to make VoIP calls with Groove, but running out of minutes hasn't been a problem for me. This is why I like the forums: You never know what you'll see and how you can improve your smartphone experience with a simple app.
PS: Earned my BSEE from Purdue in 1992.
You could port your number to google voice to get around forwarding
I am using GrooveIP and Llama as well, I ported my number to google voice and i have all calls go to 'chat'. when I am on Wifi, I will receive calls, but when I have data turned off (when I am not on wifi I usually do) it goes to voice mail. The fact that Google Voice is involved is transparent to people calling me. I don't think you have anything to lose if you port your number to google voice, because then it can follow you across any carrier, sim card or phone.
If I am expecting an important call I will forward to both my mobile number (sim card number) and to chat. So I can pick up if I need to.
This is not perfect but it saves a ton of minutes.
I would like to have llama change my GV to forward calls only to chat during wifi connections, and then forward to my mobile number when not on wifi. anyone know how to do this?
Thanks for the tutorial

Incoming calls going directly to voicemail

I am running the Powerwashed ROM on my Samsung Fascinate:
http://forum.xda-developers.com/showthread.php?t=1242747
Everything was working perfectly until I decided to try out a new ICS rom, then I found out that data wasn't working with Cricket and I couldn't get the phone to connect to a COM port to work on programming the data again.
I gave up and decided to restore my nandroid backup, which I eventually got working. The problem I have now is, I have data, web, mms, and outgoing calls. Incoming calls however go directly to my voicemail, using Google Voice. DND is not checked, the phone is registered in GV, no call restrictions, no forwarding enabled.
What else can I check?

[HOWTO] Comprehensive Automated Free VoIP with Google Voice

Preface
This guide only deals with VoIP calling over wifi. You can experiment with calling over a data connection as well; just make sure to use only the speex or GSM codecs. I have had pretty good success with VoHSPA calls with T-Mobile. However, this would require manually switching call forwarding to the cell number on and off. I am looking into creating an app to automate this (as well as combine features of all the accessory apps used in this guide). However, I have limited programming experience and no Android experience yet, so it's a long term project.
Apps
Sipdroid
https://play.google.com/store/apps/details?id=org.sipdroid.sipua
Google Voice
https://play.google.com/store/apps/details?id=com.google.android.apps.googlevoice
Y5 - Battery Saver
https://play.google.com/store/apps/details?id=pl.polidea.y5
Plane Mode Tweaker
https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.airplanemodetweak
AutoAir
https://play.google.com/store/apps/details?id=Com.YangSoft.AutoAir
GV SMS Integration Free
https://play.google.com/store/apps/details?id=com.mdrtools.apps.gvintegration.free
Guide
Free VoIP is a great addition to plans with low airtime minutes, such as T-Mobile's contract-free $30 100 minute, 5GB 4G plan. An activation kit can be purchased for $0.99 shipped from http://prepaid-phones.t-mobile.com/prepaid-phone/T-Mobile-Prepaid-SIM-Activation-Kit.
This guide assumes that your primary number is with Google Voice, http://www.google.com/voice. You can port your number from one of the major carriers (Verizon, AT&T, T-Mobile, Sprint) to Google Voice for $20. Do note that porting your number will terminate service with your provider, and you will be responsible for any ETF. If your number is currently with an MVNO or other carrier, you should be able to use a prepaid T-Mobile account as the middleman. Simply pick up an extra kit (if you will be using the T-Mobile $30 plan) to use for the number porting. Kits come with an initial value of $3.34, more than enough for the process.
If you are not attached to your current number enough to spend the $20 port fee, you can pick a new number when signing up for Google Voice. You can specify desired characters or numbers, and it will attempt to find a match.
Once you have created an account, add your cell number and enable call forwarding from your Google Voice number. Most prepaid accounts, including the $30 T-Mobile one, do not allow call forwarding, so you will not be able to "Activate Google voicemail on this phone." However, this shouldn't be an issue since people shouldn't be calling your cell number directly anyway.
Also enable call forwarding to Google chat. This is critical for receiving VoIP calls. It may be necessary to first place a call within GMail to ensure that Google chat calling works as it should.
Now it's time to download and setup the apps listed above.
Sipdroid
When first starting Sipdroid, you will find a button on the bottom of the screen to create a new account with PBXes.com linked to your Google Voice account. Use the same password as used with your Google Voice account. After signing up with Sipdroid, you have a week or so to login to the pbxes.com website and fill out some personal information. This must be completed, or your account will be deleted.
As far as configuring Sipdroid itself, you may want to go into Audio/Video and adjust Earpiece Gain to Highest. Adjust as necessary if echo is a problem.
Under Audio Codecs, set G722, PCMA, PCMU, GSM, and BV16 to Never. Speex is the only codec we want to use due to its ability to compensate for packet loss and jitter and its low bandwidth consumption. However, it can be quite CPU intensive, and if you have a slower phone, GSM may be a better option. Experiment with the two and find what works best for you. Snapdragon and faster CPUs will have no problems with speex.
Under Wireless, you can experiment with the Control Wi-Fi Power option. It may save you some battery life, but disable it if it cause otherwise slow wifi or disconnects. If not using this setting, you will need to set Android to keep the wireless connection on all the time. You can access this from Android's Wi-Fi settings page, where it lists the wireless connections. Hit the menu button and choose Advanced. Change Keep Wi-Fi on during sleep to Always.
Enable Bluetooh (experimental) if you will be using a bluetooth headset to make VoIP calls.
Finally, in PBXes Features, enable Improve Audio. In the event packet loss / jitter is detected, all data will be transmitted/received twice, effectively decreasing packet loss considerably (ideally).
Google Voice
Setup should be fairly straight forward. You may run into issues setting up call forwarding for voicemail, but this shouldn't be an issue. Set it to Use Google Voice to make all calls. This way, all non-VoIP outgoing calls will still have your Google Voice caller id.
This will also be the app you use for text messaging. Unfortunately, Google Voice is still working on implementing MMS. As of now, receiving MMS messages from certain providers is functional, although they will be sent to your email.
Y5 - Battery Saver
This app remembers wifi APs that you have associated with and switches wifi on when you are in the area. When out of area, it will be disable wifi. It requires both the cell radio and wireless to be connected to determine location. Therefore, airplane mode must not be enabled during this step.
The only setup required is to enable the app. It will then run in the background automatically.
Plane Mode Tweaker
Enabling airplane mode on most phones will disable the cell radio, wifi, and bluetooth. While in Airplane Mode, wifi is allowed to be re-enabled, while bluetooth usually is not. Make the appropriate changes with this app to prevent wifi/bt from turning off when entering airplane mode, and to allow wifi/bt.
AutoAir
AutoAir polls the wireless state in the background. When connected, it enables airplane mode; when the connection is lost, it disables airplane mode. Hit the power button in the app to enable initially. Set it to Start Service on system up and Start Service on application start up. To disable the icon in the notification bar, uncheck Show message on status bar. This serves to save battery by disabling the cell radio and to prevent double ringing, since Google Voice is forwarding to both your cell number and Sipdroid.
GV SMS Integration Free
While not related to VoIP, a lot of users would prefer the native SMS client over the GV app for text messages. Google Voice can forward texts, but it will obviously be encapsulated in a forwarded message from a shortcode instead of the actual sender's number. Not exactly clean by any means, but it is the only solution when in an area without data (i.e. roaming). Otherwise, this app will work alongside the GV app to offer seamless integration with the native SMS app (or GoSMS). You must enter your credentials in the app again for it to be able to send messages. Upon enabling integration, the phone will reboot. There looks to be three types of integration: standard, root user, and airplane mode. I've only used root user, which seems to work just fine in airplane mode.
Since I never use my cell number for texting, I have it set to send all text messages via Google Voice account. It does have the option to allow replying to texts from the number it was received from, which can be useful. There's some warning about hiding the notification bar, but I haven't had any issues yet.
Going after strictly GV SMS integration, and nothing else, I've disabled the send/receive text signatures, turning the screen on when there's a new notification, and showing popups when there's a new text.
Be sure to disable text notifications in the Google Voice app.
Do note the warning when you first enable integration-- if you decide to uninstall the app, DISABLE INTEGRATION FIRST.
That should be it! When you are home, the phone should automatically switch wifi on, connect to Google Voice (PBXes to be accurate), and enable airplane mode to disable the cell radio. Incoming calls should ring through Sipdroid. Outgoing calls are made through the native dialer as usual, and will be intercepted by Sipdroid.
When you leave home and lose wifi, airplane mode will be disabled, re-enabling the cell radio, and wifi should be disabled (saving battery by not constantly searching for APs). Inbound calls will be forward to your cell number, ringing through the native dialer. Calls made with the native dialer will dial through Google Voice (still uses airtime) and allow your Google Voice caller id to be shown.
Messaging is not a problem in airplane mode since you will be using the Google Voice app (and GV SMS Integration). The only downside is that a data connection is required for messaging while on the go. You can enable forwarding messages to your cell number if this is an issue.
Notes
It would have been nice to use the native SIP client, but it simply lacks too many features. Even over a strong wifi connection, a high(er) bandwidth codec like PCMA/PCMU may not be feasible, because of the lack of packet loss/jitter compensation. Many people prefer CSIPSimple over Sipdroid, but it does not play nicely with the Google Voice app, and does not support PBXes' proprietary features.
The main advantage of using the Sipdroid/PBXes combo over GrooVeIP is the ability to use speex/GSM codecs. GrooVeIP connects directly to Google Voice, which only supports PCMA/PCMU.
If you want to experiment with other SIP clients, do make sure to connect using TCP. UDP is a battery pig.
I've experimented with a few Android phones and have to say that some of the lower end ones are simply plagued with call quality issues, especially with regards to echo. Other issues may involve wifi quality with the screen off, so play with those settings as necessary.
Some phones have issues maintaining a wifi connection. Check for any ROMs that may address this issue. The plus side is that AutoAir will disable airplane mode if the wifi connection is lost, so there shouldn't be any missed calls. Specific to HTC Sense, there is a bug (feature) that causes the wifi connection to be dropped between midnight and 7am. The app SmartSync Disabler attempts to address this issue: https://play.google.com/store/apps/details?id=com.j4n87.smartsyncdisabler.
I am using this setup with good success on an HTC Sensation running ICS. I'm at the end of my current billing period and haven't even used half of my allotted minutes. In comparison, I've clocked over 500 minutes over VoIP.
I hope this guide saves you some minutes and battery life.
How overall is the voice quality?
It's fine for the most part. Speex has good provisions to handle mild packet loss and jitter. Over wireless, you should have no issues. I make a decent amount of calls over T-Mobile's HSPA as well, and I've found that as long as you aren't moving too quickly (in a car for example), call clarify / delay is completely fine.
Just tried setting it up. Everytime I try to dial from sipdroid, I get "unfortunately sipdroid has stopped" message. Any suggestions?
What phone are you using? Have you tried using the native dialer? I only use Sipdroid itself to make SIP calls.
Just wanted to chime in and say thank you! I followed the instructions as they pertain to my situation (SGS3, Sprint, unlimited data plan) and I've tested VOIP calling and it works great. Called my brother, and we were both immediately shocked by how good the call quality was. Only thing I did different was not install Y5 battery saver. The SGS3 (or maybe all Sprint smartphones?) has a built in function (Settings--under Wireless and networks, More Settings -- Mobile Networks -- Automatic Connections -- enable Sprint automatic connection) that seems to serve this feature.
Anyway, thanks!
Anyone else have trouble sliding up the box to answer an incoming call? Sometimes I slide it up, but it doesn't stay up, it slides back down so I can't answer. Or it has trouble sliding to begin with.
Awesome guide by the way! Thanks for sharing.
EDIT: Happens on Galaxy Nexus GSM running AOKP JELLY BEAN BUILD 5 and Galaxy S I9000 running Slim Bean 2.9
sk8erfrombham said:
Anyone else have trouble sliding up the box to answer an incoming call? Sometimes I slide it up, but it doesn't stay up, it slides back down so I can't answer. Or it has trouble sliding to begin with.
Awesome guide by the way! Thanks for sharing.
EDIT: Happens on Galaxy Nexus GSM running AOKP JELLY BEAN BUILD 5 and Galaxy S I9000 running Slim Bean 2.9
Click to expand...
Click to collapse
Yeah, I've had this problem in the past. Not sure exactly what the deal was with it. I haven't really had that problem too much lately though, and don't think it's caused me to miss a call. I think I've been giving it an extra second before I swipe it up and it seems to be fine.
I might explore other SIP apps again. Everyone likes csipsimple, but it seems to go into a loop when dialing out if used with the Google Voice app. I believe it does support speex and ilbc though, which would be nice.
Sipdroid supposedly has some proprietary support with pbxes in that it can initialize a redundant stream for purposes of mitigating packet loss / jitter.
Hey ziddey, I've heard that Google has removed the ability for third party apps to toggle airplane mode in Jelly Bean 4.2. Will this cause double ringing if AutoAir won't work? Do you know of any workarounds?
Thanks for posting this incredibly helpful tutorial. I've been using tmo's $30 plan with a GNex for awhile now. First I used GrooveIP, then pbxes+sipdroid. But, I never played around with the codecs, and speex is so much better than the default. I'm having a much better calling experience now. Thank you very much for sharing.
sk8erfrombham said:
Hey ziddey, I've heard that Google has removed the ability for third party apps to toggle airplane mode in Jelly Bean 4.2. Will this cause double ringing if AutoAir won't work? Do you know of any workarounds?
Click to expand...
Click to collapse
If Airplane mode can't be triggered, then double ringing will occur . I've stalled out on my project to make an AIO app a while ago, and am not sure what's possible now-- if there's something that can toggle the radio itself instead of triggering airplane mode.
Back in the day, I emailed Talkatone requesting that they add automatic toggling of the cell number on Google Voice when connected to Talkatone's server. In response, they added the feature, but made it available only for the premium subscription tier. But it does work. My research into GV hasn't gotten me far enough to see if there's an API I can call, or if they're manipulating the website/URL directly (imagine it's the former..). Once Talkatone sees that the client has disconnected / timed out, it will again re-enable forwarding to the cell number.
quarksurfer said:
Thanks for posting this incredibly helpful tutorial. I've been using tmo's $30 plan with a GNex for awhile now. First I used GrooveIP, then pbxes+sipdroid. But, I never played around with the codecs, and speex is so much better than the default. I'm having a much better calling experience now. Thank you very much for sharing.
Click to expand...
Click to collapse
You are very welcome! I hope it works out for you. I've been logging a lot of pbxes minutes recently and have found call quality to be inconsistent. Of course, a lot of that may have to do with wireless signal issues on my end. I would be running my own pbx server full time for personal use, but given the costs of electricity in my area, I don't have a 24/7 box anymore Maybe a Raspberry Pi is in my future.. I need something with low power consumption.
If you are ever looking to experiment, there are other sip clients available, and ilbc is another good codec to try. I believe pbxes.com supports it as well.
Does anyone know the phone number you can call to test echo? I think it plays your voice back on a delay or something...
I've seen it in the forums here but I can't find it after searching for a while.
Google for sip echo test
Use sipdroid or whatever sip client you're using to dial it.
[email protected] should work.
Trying this
I'll be trying this configuration out in the next week. I'm very curious to hear from others about how well it does for them. I'm new to the android platform, but have wanted to save the minutes and use voip as much as possible. It took a lot of searching to find this thread, and then a couple of days getting used to my new phone to have it set up.
I did note a strange loop (flashing screen) because in seeking out this guide I had had csipsimple installed (and grooveip) and Voice+ (Google Voice callback) and that caused trouble with outgoing calls. I've got it sorted out now, and it looks like it's all working.
Thanks for the well written guide!
---------- Post added at 03:51 AM ---------- Previous post was at 03:23 AM ----------
It does look like this guide might not work completely well with the airplane mode API change in 4.2. There's another thread that suggests the secure settings plugin for Tasker (paid) or running Llama - Location Profiles on a rooted phone.
Tomcat23 said:
It does look like this guide might not work completely well with the airplane mode API change in 4.2. There's another thread that suggests the secure settings plugin for Tasker (paid) or running Llama - Location Profiles on a rooted phone.
Click to expand...
Click to collapse
Bummmmmer. I'll be on the N4 boat soon enough and depend on this solution to keep under 100 minutes of actual airtime a month.
I'm switching nexus phones from the galaxy nexus to the nexus 4. Sipdroid is working great on the galaxy nexus thanks in part to this tutorial. When I boot up the N4 I sign into google voice, then I open sipdroid and put in my username and password, but I get a red dot and a "registration failed (401 Unauthorized)" error. I'm still able to open sipdroid on the gNex and it works fine.
I'm thinking of deleting my pbxes account, and then uninstalling/reinstalling sipdroid on the N4 and just setting up a brand new account.
Anyone have any thoughts? Thanks for any ideas,
k
---------- Post added at 07:54 PM ---------- Previous post was at 07:17 PM ----------
Dang. So I deleted my pbxes account, but when I try to create a new account with sipdroid, it says 'myname' trunk is already in use. I guess I should have deleted that trunk, then deleted my account. But, I can't log in to pbxes.org anymore. So, I feel stuck.
to answer my own question, in case anyone searches. You just have to wait a few hours (3-4) for me, and then you can create a new account because that old trunk gets deleted.
GV SMS Integration Free
https://play.google.com/store/apps/details?id=com.mdrtools.apps.gvintegration.free
GV SMS Integration Free
While not related to VoIP, a lot of users would prefer the native SMS client over the GV app for text messages. Google Voice can forward texts, but it will obviously be encapsulated in a forwarded message from a shortcode instead of the actual sender's number. Not exactly clean by any means, but it is the only solution when in an area without data (i.e. roaming). Otherwise, this app will work alongside the GV app to offer seamless integration with the native SMS app (or GoSMS). You must enter your credentials in the app again for it to be able to send messages. Upon enabling integration, the phone will reboot. There looks to be three types of integration: standard, root user, and airplane mode. I've only used root user, which seems to work just fine in airplane mode.
Since I never use my cell number for texting, I have it set to send all text messages via Google Voice account. It does have the option to allow replying to texts from the number it was received from, which can be useful. There's some warning about hiding the notification bar, but I haven't had any issues yet.
Going after strictly GV SMS integration, and nothing else, I've disabled the send/receive text signatures, turning the screen on when there's a new notification, and showing popups when there's a new text.
Be sure to disable text notifications in the Google Voice app.
Do note the warning when you first enable integration-- if you decide to uninstall the app, DISABLE INTEGRATION FIRST.
ziddey said:
GV SMS Integration Free
Going after strictly GV SMS integration, and nothing else, I've disabled the send/receive text signatures, turning the screen on when there's a new notification, and showing popups when there's a new text.
Be sure to disable text notifications in the Google Voice app.
Click to expand...
Click to collapse
ok
errorcod3 said:
I'm using the same exact setup as you -- I don't even know my phone number with my carrier... But, I am having a problem with GV SMS Integration. I'm a recent iPhone transplant and I switched to a Google Nexus 4 running 4.2.1.
Again, my setup is exactly the same, but I'm not getting notified for new text messages. When I open the native text message app I have new messages, I'm just not getting notified. I have turn screen on and show popups -- and I get nothing. I also have text notifications disabled in the GV app. Any ideas?
Click to expand...
Click to collapse
Do you get notified of new messages that are sent to your cell number?
Since GV SMS Integration essentially backdoors the native app, it sounds like something changed in the code with JB. Seeing how the app hasn't been updated in a while and the website is non-existent, let's hope for an update soon.
In the meantime, I'm imagining that it might work fine with GoSMS on JB if that app is okay by your standards..
Have you found an automated airplane mode toggler that works with JB? I understand AutoAir is not compatible.

[Q] Google Voice, Obi, Samsung Galaxy II, and TMobile

A while back, we got an Obi 201 device and got rid of our ridiculous $65/month basic landline (we live in the sticks). I signed up for a Google Voice number and got everything working. The Obi works great with the same phones we used for our landline, just wireless Panasonic things.
I also set up the Samsung Galaxy II thinking it would be great to have that phone ring with the same number.
We're supposed to be able to use the Obi app for Android to call home when we're away, or to allow the kids to call us. While the kids can call us no problem, we can almost never get the Obi app working where we can call from the cell to home. It's really inconvenient at times.
So I decided to just go back to using the regular Tmobile number on the cell phone.
First, I changed the google voice app so that it wasn't responsible for making outgoing calls. This didn't work. I still heard the little google voice chime whenever I made a call.
Next, I uninstalled the google voice app entirely. Still no dice, weirdly it still chimes the google voice noise when I make an outgoing call. And trying to call home using the google voice number just takes me to my voice messaging system. I can't ring the Panasonic phones.
I go into Google Voice on my desktop and uncheck the cell phone number so it won't forward the calls. I restart my phone and try to call the google voice number, which should now ONLY be forwarding to the Obi machine - but I'm *still* getting the google voice chime and it takes me to voice mail rather than the home phones.
The only other thing I can think of is that in the Obitalk website the cellphone is entered, but it doesn't give me any way to delete it, and the status is 'red' suggesting it's not working.
What in the world do I need to do to this dang phone to get it to simply use the Tmobile number? It's rooted.
I searched everywhere and couldn't find anyone with this same problem. I hope I'm being super dense and missing something obvious, because this is a bit nuts.
Thanks!
You may need to reinstall the Google Voice app and go through the settings. Disabling mobile data should successfully force the phone to use old-fashioned cellular for calls. If so, then something's telling your phone to make VOIP calls over mobile data.
Also, check the settings within the phone app.
post-mortem said:
You may need to reinstall the Google Voice app and go through the settings. Disabling mobile data should successfully force the phone to use old-fashioned cellular for calls. If so, then something's telling your phone to make VOIP calls over mobile data.
Also, check the settings within the phone app.
Click to expand...
Click to collapse
I have done all of that. Uninstalling the app completely - to the point where I can no longer find any reference to it in the phone settings, STILL calls out with that blasted google chime.
I reinstalled the app, and set it to never make calls with google voice, and it still calls out with the google chime, resulting in a total inability to call home - it goes straight to voice mail, thinking I'm calling myself.
I tried to delete my mobile number from google voice's website, but it says the account *has* to forward somewhere, even though my husband's google number does not forward anywhere.
If I un-check the mobile number to stop forwarding calls in the google voice website, calls stop coming to my OBI device, resulting in no home calls ringing, and the cell STILL calls out with that number.
I'm ready to throw this phone in the street and run over it a few times with the car. AUGH.
Should I just do a factory reset? I don't have any data that needs saving. I just want this stupid phone to be able to call my house when I'm out.
If that's the case, then go ahead and do that.
post-mortem said:
If that's the case, then go ahead and do that.
Click to expand...
Click to collapse
I did, but it didn't help. I begged for help on the Obitalk forums and finally found the setting I needed to change. For anyone else having this issue:
1. Add your t-mobile (or cell number) to Google Voice as a contact. Then, edit the google voice settings in the contact and make sure only 'ring google voice' is checked.
2. Then, go to the phones tab in the settings, and at the bottom click the 'edit' button. It's gray and hard to see. From there, click "advanced settings" and under voicemail check "no."
This will allow the cell phone to ring the Obi / google voice home number. Hooray.

[Q] Google Voice not working on your S6?

I noticed I hadn't gotten any Google Voice/Hangout notifications of voice mails. I reset my Google Voice (deactivated/reactivated) to no avail. However, once I deactivated Advanced Calling (Settings...Wireless and Networks), and reset Google Voice, it's working again. Anyone else experience similar/same?
Yeah, I did a search and saw others with Verizon phones and advanced calling that were having this issue. It looks like if you have advanced calling, you can't use google voice.
Don't know if there is any solution yet.
On edit, this link provides a possible fix:
http://forum.xda-developers.com/droid-turbo/general/fix-google-voice-forwarding-advanced-t2980980
I've had no problems with Google Voice and Hangouts, both with VoLTE enabled and disabled, and on my S6 and G3. I don't use VoIP for calls via Hangouts though, it rings my actual cell number that I have set to forward to with Google Voice.
Working extremely perfect. No issues.
chris mackenzy said:
Working extremely perfect. No issues.
Click to expand...
Click to collapse
Well, I must be doing something extremely wrong. I tried again, same result. I have to turn off HD calls, and then reset Google Voice. If anyone has more suggestions, I'd love to hear them.

			
				
I'm having no problems with Google voice but having said that I'm using mine on Cricket. Are you using Hangouts for your GV messages? I had nothing but problems getting notifications for GV on it so I switched back to the old GV app.
jimbobtexas said:
I noticed I hadn't gotten any Google Voice/Hangout notifications of voice mails. I reset my Google Voice (deactivated/reactivated) to no avail. However, once I deactivated Advanced Calling (Settings...Wireless and Networks), and reset Google Voice, it's working again. Anyone else experience similar/same?
Click to expand...
Click to collapse
i had the same issue and turning off Advanced calling seems to have fixed it as well. thanks!
alnova1 said:
I'm having no problems with Google voice but having said that I'm using mine on Cricket. Are you using Hangouts for your GV messages? I had nothing but problems getting notifications for GV on it so I switched back to the old GV app.
Click to expand...
Click to collapse
Yeah, I'm using Hangouts now without issue. I did install Google Voice, because I think that's still required for everything to wire up right. I just turned off the HD calling all together. Not worth my while, at least for now.
So, I tried some of the fixes suggested on this forum and they haven't taken yet. Disabling HD Voice works but causes other problems I'll describe below. With HD Voice active, I tried uninstalling GVoice app and removing my number altogether, then adding it all back again as if for the first time. That did not work. I tried twice. All voicemail still gets routed into my Verizon voicemail.
Spent a good hour on the phone with Verizon customer support and elevated to L2 technician. TLDR: There appears to be a conflict based on how Verizon has chosen to employ the HD Voice function. Right now, I'm forced to either have Google Voice active on my mobile phone OR retain the ability to use data and voice at the same time, but I can't have both.
I just activated my Verizon 64GB Samsung Galaxy S6 two days ago. Today, I noticed I had a Verizon voicemail message for the first time in years. I have been using Google Voice(mail) for as long as I can remember. Concerned why voicemail was skipping my GVoice, I soon discovered that others had noted that turning off the HD Voice option fixed the problem. Sure enough, it did. I thought I was good to go.
Until, the next time I made a call, I noted that my 4G immediately turned into a greyed out 1x and any attempt to use other functions of my phone while on the call were met with a warning that said I can't make calls and use data services at the same time. That was news to me, since that has never been an issue before. Surely my GS6 is not less capable than the GS3 it just replaced in this area.
This took me to Verizon customer support, which to its credit, hung in with me the entire way in troubleshooting this. We confirmed the relationship between GVoice and their Advanced Calling service (HD Voice). And we confirmed that by turning the service back on, my ability to use data while on a call would be restored. We could not determine anything in Verizon's playbook that would allow the two to co-exist. The L2 engineer confirmed that Verizon designed its build so that the only way Data and Voice could flow simultaneously is with HD Voice activated and selected. Verizon customer service was left to advise me to choose between GVoice or dual Voice/Data based on which was more important, and maybe Google will update Google Voice in the future to fix the problem. I found that last part somewhat funny, since I don't think this is Google's problem to fix since this appears to be a Verizon specific problem and I have never had a phone that hasn't worked perfectly with GVoice. Oh, and it's not like Google is pushing out patches to Voice with any intentionality either.
I joined the forums specifically to post this in the hope it helps someone else and sparks other ideas how to beat this. This appears to be a recently discovered phenomenon. Also, since the GS6 is still relatively new, maybe this will help to raise awareness and provoke a patch. Who knows.
Anyone encounter other ideas for getting Voice to regain prime position again?
FractalK said:
So, I tried some of the fixes suggested on this forum and they haven't taken yet. Disabling HD Voice works but causes other problems I'll describe below. With HD Voice active, I tried uninstalling GVoice app and removing my number altogether, then adding it all back again as if for the first time. That did not work. I tried twice. All voicemail still gets routed into my Verizon voicemail.
Click to expand...
Click to collapse
Finally got this to work by ensuring to clear app data before uninstalling an making sure not to prematurely hang up on Google voice as it reinstated the call forwarding on my new mobile phone. With this fixed e now have a work-around for using Google voice while still maintaining advanced calling features.
FractalK said:
Finally got this to work by ensuring to clear app data before uninstalling an making sure not to prematurely hang up on Google voice as it reinstated the call forwarding on my new mobile phone. With this fixed e now have a work-around for using Google voice while still maintaining advanced calling features.
Click to expand...
Click to collapse
I can confirm this process works. I turned on HD calling. In Application Management, I cleared cache and data on the Google Voice app, then uninstalled it. I then went to my computer and deactivated Google Voice mail. I then reinstalled Google Voice on my phone, and stepped through the configuration (Verizon doesn't support it directly, so you'll see that boogie-woogie - just take the defaults and move through it). I then went back to the PC and enabled Google Voice, and let the lady finish and hang up on me. Subsequent tests confirmed that I have Google Voice mail now, while HD calling is active.
jimbobtexas said:
I can confirm this process works. I turned on HD calling. In Application Management, I cleared cache and data on the Google Voice app, then uninstalled it. I then went to my computer and deactivated Google Voice mail. I then reinstalled Google Voice on my phone, and stepped through the configuration (Verizon doesn't support it directly, so you'll see that boogie-woogie - just take the defaults and move through it). I then went back to the PC and enabled Google Voice, and let the lady finish and hang up on me. Subsequent tests confirmed that I have Google Voice mail now, while HD calling is active.
Click to expand...
Click to collapse
I followed your steps exactly and from what I can tell everything is working properly on mine as well. THANK YOU!!
Fixed
I only have hangouts installed, I don't use the Google Voice app anymore. After I enabled advanced calling, apparently my VM forwarding also stopped.
All I had to do to fix it was re-enable the call fowarding options, and I'm back in business.
*71[Your Google Voice number]
*90[Your Google Voice number]
*92[Your Google Voice number]
The key to the whole thing is to let the call forwarding calls fully finish and hang up on you. If you hang up, they won't complete.
Didn't have to do anything on my S6 besides going through the prompts again and letting them finish. The whole uninstall/reinstall thing may be overkill.
mustangz5 said:
All I had to do to fix it was re-enable the call fowarding options, and I'm back in business.
*71[Your Google Voice number]
*90[Your Google Voice number]
*92[Your Google Voice number]
Click to expand...
Click to collapse
Still not working....
Unfortunately I still can't get it working on my s6. It works if a person calls my "google voice" number. However, if they call my "verizon" phone number it just will not go to voicemail...it rings and rings. Call forwarding is on, i've done all the steps. Any one else having this problem?
Yeah same here at least visual voice mail is free now
Sent from my SM-G920V using XDA Free mobile app
golfprorm said:
The key to the whole thing is to let the call forwarding calls fully finish and hang up on you. If you hang up, they won't complete.
Didn't have to do anything on my S6 besides going through the prompts again and letting them finish. The whole uninstall/reinstall thing may be overkill.
Click to expand...
Click to collapse
I wonder why it worked so easily for you.
I've tried letting it hang up on me for all 3 numbers (*71, *90, *92), but it seems to refuse to work. I'll have to try the uninstall/reinstall stuff later and see if that triggers it for me.
Not working....
For those of us still having problems....I created a post on verizon's S6 community support site as well....
https://community.verizonwireless.com/thread/858976
ajbang said:
For those of us still having problems....I created a post on verizon's S6 community support site as well....
https://community.verizonwireless.com/thread/858976
Click to expand...
Click to collapse
Hopefully Verizon will figure this out quickly.
Now I can't get google voice to work even with advanced calling disabled. I have it entirely set to off in settings, called all 3 numbers to setup the forward (and let them hangup on me), yet when I call my number, I get a Verizon message about needing to enter the phone number of the mailbox you're trying to leave a voicemail for...

Categories

Resources