Database Info

[Q] cant change default sms app to google voice or others

when I try to set Google voice as my default SMS the only option I have is hangouts. I downloaded chomp and handcent just to test it and handcent shows as an option, but not chomp or Google voice. stock rooted, any ideas?

kellybrf said:
when I try to set Google voice as my default SMS the only option I have is hangouts. I downloaded chomp and handcent just to test it and handcent shows as an option, but not chomp or Google voice. stock rooted, any ideas?
Click to expand...
Click to collapse
8SMS from the Play Store works.

It will work. But I just don't like the gv app for reading sms because of the way they are grouped. If you like it, great...u won't have to worry about sync issues from gv to a default app.
In GV settings, select to receive SMS "via google voice" instead of the messaging app. And set up notifications with in gv.
In this case I don't think GV will forward messages to the system default app. If it does, you will get double notifications. If that happens turn off all notifications in hangouts and/or sign out maybe.
I've been using Textra as my SMS app.
Sent from my Nexus 5 using XDA Premium 4 mobile app

The developer of the app has to update the app to 4.4 comparability to add that feature. I am using Textra and I really like it.
Sent from my Nexus 5

Yes, apps need to be updated for SMS because Google changed the way how it works. Only one app can receive and send SMS, before any app can.
I just started using textra instead of hangouts because I want quick reply lol
Sent from my Nexus 5 using XDA Premium 4 mobile app

akenis said:
It will work. But I just don't like the gv app for reading sms because of the way they are grouped. If you like it, great...u won't have to worry about sync issues from gv to a default app.
In GV settings, select to receive SMS "via google voice" instead of the messaging app. And set up notifications with in gv.
In this case I don't think GV will forward messages to the system default app. If it does, you will get double notifications. If that happens turn off all notifications in hangouts and/or sign out maybe.
I've been using Textra as my SMS app.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks, I have those set and I get notifications just fine but when I send a text from the dialer it goes through hangouts. the gv app does suck, but it allows me to use two phones with my one number
expertzero1 said:
Yes, apps need to be updated for SMS because Google changed the way how it works. Only one app can receive and send SMS, before any app can.
I just started using textra instead of hangouts because I want quick reply lol
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
well damn, knowing Google the all well never be updated

kellybrf said:
thanks, I have those set and I get notifications just fine but when I send a text from the dialer it goes through hangouts. the gv app does suck, but it allows me to use two phones with my one number
Click to expand...
Click to collapse
kellybrf said:
thanks, I have those set and I get notifications just fine but when I send a text from the dialer it goes through hangouts. the gv app does suck, but it allows me to use two phones with my one number
Click to expand...
Click to collapse
Well make up your mind! Before you said you wanted to use GV as your messaging app. Hence my advice before to pretty much ignore whatever you choose as default SMS app and just send/receive your text from within the GV app (Having selected "receive messages through GV app).
Now you're saying that you are trying to send messages from the default SMS app (hangouts). So what you are really saying is that you want to use a default SMS app (hangouts, or textra) and have the text go out your through your GV number? This is totally possible and what I am doing. Bear with me...
We have to understand the GV is NOT really SMS. It just intercepts SMS messages sent to your GV number and sends them to the GV app. These messages are coming to you phone through data, not the radio. Think of GV app operating in two different modes:
1) GV app can operate independently from your devices SMS (select "Via the GV app). You can send and receive messages from the GV app and they will use your GV number. None of these messages will be "forwarded" to the system app. In this scenario, you can also use the system app separately. Messages sent and received from the system default app wil not appear in the GV app, and will use your REAL phone number.
2) GV app can be used to relay these pseud SMS messages coming across your data to the default system app (select "via the messaging app"). In this case, messages sent to your GV number will appear in the GV app, and then be forwarded to the system app and use it's notification settings. Now this gets a little weird, but when this forwarding happens, the message received in the system app appears to come from an unknown phone number in some random area code. Not sure why... has something to do with the whole forwarding process. Luckily, if the real incomming number is in you contacts, then GV appends the contact name to the message. Now if you reply from within the GV app, it goes right back to the sender (no copy of your reply will appear in the system app, because you replied from within GV). If you reply from the system app, and that pseudo phone number... then it will forward back to the GV app (a copy will be there), translate back to the real phone number and send out the reply. And it will be from your GV number. The key is using that pseudo number that translates to the contacts real number. If YOU initiate a message from within the native app, then it just sends a regular SMS using your phones number, NOT your GV number (incidently, this is the only way to send MMS as of now, so you just have to tell the recepient to use the real phone number for pics). When I first figured this out, I used to just make sure that I always initiated the conversation from the GV app. The last neat trick is to save that pseudo number to the existing contact as either a pager (who uses those?) or a custom "pseudo GV" number. No you can initate the conversation from within the system app, and slect the pseudo number.... it will route to GV and appear to come from your GV number. If you use their real mobile number, it will appear to come from your actual phone number.
Clear as mud? Supposedly there are some changes coming to the way GV works. Lets hope they get this stuff a little more user friendly and allow SMS. Actually, I wouldn't mind just using the GV app if it didn't make multiple threads per contact. Good luck...

no, I want Google voice to be my one and only SMS app. on 4.3 and below, when I initiated a text from anywhere outside a messaging app it asked me what I wanted to use, Google voice or messaging or whatever SMS all I'd have installed. I'd get the use one or set as default dialog, and of i set as default gv would then handle all messaging.
with 4.4, when I initiate a text from outside an app it automatically goes through hangouts, and I cannot choose google voice as a default. if I want to send a text via gv, now I have to initiate it via gv. in the op I said I downloaded chomp and handcent just to see if I got the option to set them as a default, and of the 2 only handcent showed up one list. I think expertzero hit it, and Google just hasn't updated gv for 4.4 yet

Google voice messaging support with hangouts

On my galaxy nexus, I used an app called messaging plus Google voice to optionally send text messages from my Google voice number (fo free).
It doesn't appear to be supported in Kit Kat, and surprisingly the new and improved hangouts doesn't support this either.
This was a great option for me to help manage my text messaging plan. Does anyone have an alternative?
- Thanks, Kevin
Sent from my Nexus 7 using XDA Premium 4 mobile app

Why don't you use google voice app to send text messages from your GV number?

jj14 said:
Why don't you use google voice app to send text messages from your GV number?
Click to expand...
Click to collapse
The other app had them (both google voice and regular text messages) consolidated in a single view. The gv interface lacks usability IMO, and hangouts seems like the perfect place. It is a shame that the messaging + gv broke in kit Kat.
Sent from my Nexus 7 using XDA Premium 4 mobile app

KevinAlbrecht said:
The other app had them (both google voice and regular text messages) consolidated in a single view. The gv interface lacks usability IMO, and hangouts seems like the perfect place. It is a shame that the messaging + gv broke in kit Kat.
Click to expand...
Click to collapse
In Google voice app on Android, Settings--> Sync and Notifications --> click Receive Text Messages" and select Messaging app.
Now, any text sent to the Google voice number will show up in Hangouts.
Sending is a little more complicated.
I can’t compose a new message in hangouts to a ‘new’ sender from my GV number(one that I haven’t received a message from into hangouts).
But if I send a message to my GV number (from an unrelated number), it shows up in my hangouts app with a seemingly random number (GV assigns a different intermediary number to each sender in GV – existing functionality)
If I now respond to that message in hangouts, it shows my GV number instead of my regular number.
True integration should be coming later this year though.

jj14 said:
In Google voice app on Android, Settings--> Sync and Notifications --> click Receive Text Messages" and select Messaging app.
Now, any text sent to the Google voice number will show up in Hangouts.
Sending is a little more complicated.
I can’t compose a new message in hangouts to a ‘new’ sender from my GV number(one that I haven’t received a message from into hangouts).
But if I send a message to my GV number (from an unrelated number), it shows up in my hangouts app with a seemingly random number (GV assigns a different intermediary number to each sender in GV – existing functionality)
If I now respond to that message in hangouts, it shows my GV number instead of my regular number.
True integration should be coming later this year though.
Click to expand...
Click to collapse
Thanks for the heads up. I had that set already, trying to get the other app to work. I guess I have not gotten any GV messages on my new phone! and thanks for the info on the future integration (I hope).

KevinAlbrecht said:
Thanks for the heads up. I had that set already, trying to get the other app to work. I guess I have not gotten any GV messages on my new phone! and thanks for the info on the future integration (I hope).
Click to expand...
Click to collapse
Also look for VoIP calling using hangouts later this year

The only real integration you can get until Google adds support, is through CyanogenMod 11. There is a framework modification called Voice+ that synchronizes your Google voice inbound/outbound messages to either the stock messenger or hangouts. It even automatically routes MMS through your phones real number.
Just to be clear this is what it does:
Your friend texts your google voice number > your default SMS app shows notification with their real number (not their GoogleVoice routing number) > you reply in your default sms app > they recieve the text from your Google Voice number.

bilago said:
The only real integration you can get until Google adds support, is through CyanogenMod 11. There is a framework modification called Voice+ that synchronizes your Google voice inbound/outbound messages to either the stock messenger or hangouts. It even automatically routes MMS through your phones real number.
Just to be clear this is what it does:
Your friend texts your google voice number > your default SMS app shows notification with their real number (not their GoogleVoice routing number) > you reply in your default sms app > they recieve the text from your Google Voice number.
Click to expand...
Click to collapse
Yeah, that is what the Messaging Plus GV app did (sort of) It was a stock replacement app and you managed everything from within it. GV conversations were a separate thread, but the originating number did not change.
- Thanks, kevin

KevinAlbrecht said:
Yeah, that is what the Messaging Plus GV app did (sort of) It was a stock replacement app and you managed everything from within it. GV conversations were a separate thread, but the originating number did not change.
- Thanks, kevin
Click to expand...
Click to collapse
i just purchased this: https://play.google.com/store/apps/details?id=com.klinker.android.messaging_donate
and it works with GV. you still have to have the GV app installed.
NOTE: its a separate messaging app

[Q] Hangouts, Google Voice, Group Messaging

I currently have Hangouts receive text messages from Google Voice (not using Voice+) and it has been working smoothly so far, however today I had a strange issue.
I received what I assume was a group message from my cousin (who uses a Galaxy S3 on sprint) but the contact number was formatted strangely. Let's assume my number is 555-1234-567 and his number is 555-8675-309. The contact number showed up as [email protected] The message was also preceded by a "/"
When I open Google Voice, however, I see his proper contact name with his proper message (but no other recipient numbers). Of course, everyone who replied to the group message showed up in Hangouts in a similar fashion with their number in place of my cousin's, but in Google Voice they had their own separate thread with their proper contact name and message.
Is this just an issue with Google Voice and MMS? I assume the group message he sent was converted to MMS through the stock messaging app on the S3, but I'm not certain.

blanksuspect said:
I currently have Hangouts receive text messages from Google Voice (not using Voice+) and it has been working smoothly so far, however today I had a strange issue.
I received what I assume was a group message from my cousin (who uses a Galaxy S3 on sprint) but the contact number was formatted strangely. Let's assume my number is 555-1234-567 and his number is 555-8675-309. The contact number showed up as [email protected]. The message was also preceded by a "/"
When I open Google Voice, however, I see his proper contact name with his proper message (but no other recipient numbers). Of course, everyone who replied to the group message showed up in Hangouts in a similar fashion with their number in place of my cousin's, but in Google Voice they had their own separate thread with their proper contact name and message.
Is this just an issue with Google Voice and MMS? I assume the group message he sent was converted to MMS through the stock messaging app on the S3, but I'm not certain.
Click to expand...
Click to collapse
When a MMS comes in on Sprint from GV, it sends an e-mail from a [email protected] much like what you said. It's probably because it's Sprint since Sprint + GV + MMS works.

[Q] Sending/Receive MMS app using Google Voice?

We all know Google Voice doesn't support MMS (at least photos sending). Is there any app that support Sending/Receive MMS (at least pics) using Google Voice number? Receiver can see GV number. If they send pics GV number, I can get it.
Please share me if any available.

ItsMeSri said:
We all know Google Voice doesn't support MMS (at least photos sending). Is there any app that support Sending/Receive MMS (at least pics) using Google Voice number? Receiver can see GV number. If they send pics GV number, I can get it.
Please share me if any available.
Click to expand...
Click to collapse
I've been reading that you can use Hangouts to send photos. I'm about to test it out tonight.

How Android Parses Phone Numbers For SMS

So, I posted this on a google forum and had a look across XDA in general, but either the silence is deafening, very few people have noticed (or care) or no one has an answer?
It's bugging me, so I'm hoping someone here might know or at least offer some suggestions..
Trying to use Voice Search to create and send an SMS message to one of my contacts exposed really weird behavior in Android...
** Contacts set up correctly with properly formatted phone numbers and defaults set. I'm in the UK but often travel so want to set up numbers
for people in the standard format e.g. +44 7973 XX XX XX
** I can dial the number exactly as formatted and the call goes through
** I can send an SMS from Hangouts.. BUT when I select a contact and their number appears as an option to SMS to.. the "leading" +44 (country code) gets
stripped out by Hangouts and a "0" is added in (to be compliant with the format for dialing within a country I guess).
So +44 7973 XX XX XX appears as 07973 XX XX XX - and this works fine!
** When using Voice search to create and send an SMS however, the number that appears on screen that it's trying to send to is the *exact* number
from the phone book - that is, the country code is NOT stripped out - so different from how the hangouts app displays it.. and the message fails to
send as a result.
So, it seems as though Google deliberately re-format the phone number for SMS when you do it through Hangouts, but not when you use Voice
(even though that message does get sent through Hangouts ultimately?)
The only solution I can think of, is to go through and remove the +Country Code prefix from all of my contacts, to ensure
that SMS via Voice Search will work consistently... What's going on?!?!? Anyone got any ideas ? Its not an obvious bug, but its definitely there..

Anyone?!

jms_uk said:
Anyone?!
Click to expand...
Click to collapse
I can't talk about hangouts because I don't use it, nor voice.... but +44 should not fail to send SMS. All my frequently contacted contacts are +44 and send fine, without being changed or stripped out.
Please wait 24 hours before bumping threads

rootSU said:
I can't talk about hangouts because I don't use it, nor voice.... but +44 should not fail to send SMS. All my frequently contacted contacts are +44 and send fine, without being changed or stripped out.
Please wait 24 hours before bumping threads
Click to expand...
Click to collapse
Sorry, will do in future. But thank you for replying
I agree with you that having +44 in the number shouldn't fail when sending SMS, but Hangouts definitely re-formats the number and I have to wonder
if it does that for a reason. Does the number displayed on the SMS app you do use, display the full number then when compared against the same
number in your contacts?
I'm going to install something like Handcent and see what that does (of course all bets are off ifthe app re-formats the number "internally" but displays
the unchanged number to the user). The only reason I've noticed this odd behaviour is because Hangouts makes it reasonably obvious that something
is going on.

jms_uk said:
Sorry, will do in future. But thank you for replying
I agree with you that having +44 in the number shouldn't fail when sending SMS, but Hangouts definitely re-formats the number and I have to wonder
if it does that for a reason. Does the number displayed on the SMS app you do use, display the full number then when compared against the same
number in your contacts?
I'm going to install something like Handcent and see what that does (of course all bets are off ifthe app re-formats the number "internally" but displays
the unchanged number to the user). The only reason I've noticed this odd behaviour is because Hangouts makes it reasonably obvious that something
is going on.
Click to expand...
Click to collapse
Yes the number in the default messaging app displays the same as in contacts and dialer. In full with +44 7*
It's been a while since I used KitKat stock, but does it not have the standard messaging app included, that lets you change to that? Lollipop does.

rootSU said:
Yes the number in the default messaging app displays the same as in contacts and dialer. In full with +44 7*
It's been a while since I used KitKat stock, but does it not have the standard messaging app included, that lets you change to that? Lollipop does.
Click to expand...
Click to collapse
Yeah, I tried Handcent SMS, that didn't modify the number either and the SMS sent just fine. I guess why Hangouts modifies the number
for SMS when other apps don't, is for some mysterious reason Google has cooked up.
However, the "problem" is most definitely with the implementation of Voice Search for creating SMS (I only fell onto this thing because I wanted to - more safely -
send/reply to the occasional SMS whilst driving). Basically, it doesn't matter what SMS app is set as default.. creating a message and sending
by Voice Search just won't work if the number in your contacts has a +44 in it.. from the testing I've done anyway. The moment I edit the number
against the contact to just have an 0 (and re-sync Google Contacts), Voice Search created SMS's work...
(Also, whatever SMS app is the default always appears as an "Open Message in XXXX" after the Voice Search created SMS has been sent. If you click on it,
it takes you into the app but you can't see the most recently sent message in the message thread if the number is +44)
Perhaps you could give it a go with a +44 contact "Ok Google, Send text to XXXXX, Message, YYYYYY" ??
..aaaaand, I'm done. Any thoughts?

jms_uk said:
Perhaps you could give it a go with a +44 contact "Ok Google, Send text to XXXXX, Message, YYYYYY" ??
Click to expand...
Click to collapse
Say's sent, but when I open the messaging app, there is a Red triangle... When I open the existing message thread, it only shows THAT failed message. When I delete that message, the rest of the thread becomes available.
So yeah I guess it fails the same way

rootSU said:
Say's sent, but when I open the messaging app, there is a Red triangle... When I open the existing message thread, it only shows THAT failed message. When I delete that message, the rest of the thread becomes available.
So yeah I guess it fails the same way
Click to expand...
Click to collapse
Ahh.. so I'm not going crazy! Wonder how long that's been broken?

jms_uk said:
Ahh.. so I'm not going crazy! Wonder how long that's been broken?
Click to expand...
Click to collapse
Dunno but I'm using the latest Lollipop preview released last week or two...

By the sounds of things.. for some time then if you're on Lollipop. I guess people either don't use Voice for that much (at all?), or haven't put two and two together enough for it to be something that's made its way back to Google to add to their fixes

jms_uk said:
By the sounds of things.. for some time then if you're on Lollipop. I guess people either don't use Voice for that much (at all?), or haven't put two and two together enough for it to be something that's made its way back to Google to add to their fixes
Click to expand...
Click to collapse
...or only have nationally formatted numbers instead of international...

True. Though out of curiousity I'd love to know why Hangouts does do a number re-format.. as a completely separate thing..

Not sure if this is related as I am UK based like you (so not really sure what it is) but google voice doesn't send texts to international numbers. I wonder if google now has some voice aspects built in and if hangouts is configured to allow sending through voice if you're subsribed? Hence the number changing? and possibly failures?

Manually sending SMS messages using a 3rd party app to numbers formatted for international dialing works. Going "via Google" be it using Voice Search or Hangouts, only works with internal numbers...
I think you might be onto something... :|

jms_uk said:
Manually sending SMS messages using a 3rd party app to numbers formatted for international dialing works. Going "via Google" be it using Voice Search or Hangouts, only works with internal numbers...
I think you might be onto something... :|
Click to expand...
Click to collapse
Yeah there may be a link...
But the stock messaging app built in (you have a choice of hangouts or sms) also works as desired...

rootSU said:
Yeah there may be a link...
But the stock messaging app built in (you have a choice of hangouts or sms) also works as desired...
Click to expand...
Click to collapse
Good to know.. but not when creating and sending SMS via Voice Search (so far I think we've established that unless contact numbers are reformatted and re-synced to omit the +44 and reinstate the 0, then
it can't be used for SMS)

jms_uk said:
Good to know.. but not when creating and sending SMS via Voice Search (so far I think we've established that unless contact numbers are reformatted and re-synced to omit the +44 and reinstate the 0, then
it can't be used for SMS)
Click to expand...
Click to collapse
Correct.
Manual through Stock SMS > +44 > OK
Manual through Hangouts > Convert to 0 > OK
Voice Command through anything > +44 > FAIL

Thanks for being a sounding board. Guess there's nowt left that can be done

rootSU said:
Correct.
Manual through Stock SMS > +44 > OK
Manual through Hangouts > Convert to 0 > OK
Voice Command through anything > +44 > FAIL
Click to expand...
Click to collapse
..and to close things out, I received an auto-generated sms from my network saying..
"Yesterday you sent a message to an invalid number. UK mobile numbers start with 07 or +447. Numbers starting with 447 without the leading + are invalid"
So that pretty much confirms that whatever mechanism Voice Search uses to try and send texts is broken and doesn't/can't parse the + in a contact's phonenumber
where as the SMS apps do (probably due to the reasons you posted above)