I am running the Hyperdrive RLS7 ROM with Lean kernel. I have decided that I like Chomp for messaging better than the AOSP style messaging app I installed using AROMA with this ROM. I used App Manager to disable the baked in messaging app and, after that, I could send SMS, but couldn't receive any SMS/MMS or send MMS. So I re-enabled messaging and could send both, but only receive SMS. I went back to a nandroid, but this didn't fix the problem. I ended up doing a clean install of Hyperdrive.
My question is whether this is a ROM issue, related to my use of the App manager or a problem with the messaging choice in AROMA or something else altogether? Should Chomp have still worked with the messaging app disabled and should it have worked correctly after enabling it again? Was there any way to fix it without a full clean install? TIA.
I think the problem is with Chomp. I've always had MMS issues with Chomp and Handcent fc'ing. Also, you should not disable your stock messaging app (as you found out), otherwise it will give you issues with the third party apps.
Honestly, I've tried a lot of different sms/mms apps, since I'm not a huge fan of the stock S3 one, and I keep going back to GoSMS. I do really dislike the push notifications they force on you, but it handles group messaging the best of anything I've tried, along with mms. I have tried the AOSP messenger tweak for TW, too. No bueno. Just my two cents.
Have you tried contacting your sim provider and asking them to send the default usage setting for your phone? It will come as a text and will install when you open it!
I've been having an issue since the 4.4.1 update. I primarily use Textra for SMS/MMS and it's set as the default. However, I'm on a limited texting plan and use Google Voice for a few of the people I text with most frequently.
I have direct message shortcuts on my homepage for my main contacts. I used to (before the 4.4.1 update) be able to click them and get prompted for what program to use, Textra, Google Voice, anything else. Now, it always defaults to Textra.
I can go clear the defaults in Settings-Apps-Textra-Clear Defaults and it works normally for a few minutes. However, it always seems to set Textra back as the default SMS client eventually.
I'm trying to figure out a way to let my direct message shortcuts work again. I've factory reset and set up just enough to let me test again (Textra, Google Voice and a direct message shortcut), but it still does the same thing. I've tried with other SMS clients (8SMS, Hangouts) and the behavior is the same.
Can anyone think of a way to fix this? Is there a way to automate the Textra-Clear Defaults? Is there a way to create a Google Voice direct message shortcut? A way to fix Kit Kat so that I can use whatever texting app I want?
I'm running rooted stock so root solutions are fine. Would I have better luck with CM or something based off of it?
Thanks for any feedback!
As some of you know Android Wear doesn't allow you to send SMS via Google Voice. I have a working solution and wanted to know if anyone would actually use it. The solution however requires Tasker and AutoWear to get the command from the watch and act on it. This is also a non-root solution. Last this will of course be open source.
Do you mean initiate a new Hangout with someone (a) or respond to an SMS via Google Voice (b)?
A. If you wish to send a Google Voice SMS through Hangouts, you should be able to use the "Send text to Sam Hey, how's it going?" voice command. If Hangouts is set as your phone's SMS app on your phone and it is setup to default to your GV #, that should work. If you wish to send a new hangout chat (non-SMS) through Hangouts, I think you're SOL or stuck with a very hacky Tasker/AutoWear situation.
B. You are able to respond to someone from hangouts. Hangouts will default to the method of contact that you received the prompting message in.
iHelp101 said:
As some of you know Android Wear doesn't allow you to send SMS via Google Voice. I have a working solution and wanted to know if anyone would actually use it. The solution however requires Tasker and AutoWear to get the command from the watch and act on it. This is also a non-root solution. Last this will of course be open source.
Click to expand...
Click to collapse
I'd like to know how you get this to work. What the previous poster said doesn't work for me as it still sends the texts from my real number even though i've told it to send texts from my google voice #.
iHelp101 said:
As some of you know Android Wear doesn't allow you to send SMS via Google Voice. I have a working solution and wanted to know if anyone would actually use it. The solution however requires Tasker and AutoWear to get the command from the watch and act on it. This is also a non-root solution. Last this will of course be open source.
Click to expand...
Click to collapse
Please share ..!
I just got my Moto 360 this past week and the fact GV/Hangouts is so horribly "unsupported" is a major turn off since being able to to send texts via GV via the watch was going to be a big use case. (But as I've learned through use and bunches of Google searches it's not that simple.)
I'm about to head off on my own Tasker+AutoWear solution but I only "kind of" know how to use Tasker properly and haven't used AutoWear at all so if you already have something that works I'd love to see it.
iHelp101 said:
As some of you know Android Wear doesn't allow you to send SMS via Google Voice. I have a working solution and wanted to know if anyone would actually use it. The solution however requires Tasker and AutoWear to get the command from the watch and act on it. This is also a non-root solution. Last this will of course be open source.
Click to expand...
Click to collapse
I'm Interested in this,, any ideas about incoming google voice call notifications?
Hangout SMS
I must appreciate for your fantabulous work on creating app that allows send hangout sms by voice.
Tried Quick for Wear?
I think you should be able to use Quick for Wear to send Hangout messages. And as a bonus, you have the option of using voice, or one of their built in keyboards, or FlickKey for Wear - which also lets you edit voice messages with a keyboard if you use voice through it.
Yes please share!
Quick for Wear
jclendineng said:
Yes please share!
Click to expand...
Click to collapse
Quick for Wear: https://play.google.com/store/apps/details?id=com.michy.quickforwear
Hi, I really would use and appreciate this feature. I only use GV for sms over Hangouts. Even when using send text via the phone's "okay Google" send text feature, it defaults to sending a hangouts sms (from my real cell#) instead of my gv #. It drives my nuts. Is there anyway to TWEAK a setting on the office for okay Google?. So that Okay Google command, sends all sms by default using the GV number. This may be the solution...
Sent from my Nexus 5 using Tapatalk
monter_man said:
Hi, I really would use and appreciate this feature. I only use GV for sms over Hangouts. Even when using send text via the phone's "okay Google" send text feature, it defaults to sending a hangouts sms (from my real cell#) instead of my gv #. It drives my nuts. Is there anyway to TWEAK a setting on the office for okay Google?. So that Okay Google command, sends all sms by default using the GV number. This may be the solution...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This is because when you use the voice commands to send a message, it is never touching the default SMS app (in this case, Hangouts). Rather, it composes the whole thing and even sends from its own user interface. Up until a recent update to Hangouts, this is how it worked system-wide. In other words, clicking send msg from the dialer or contacts screen, for example, would open hangouts as the sms app (if set to be the default for sms), but always start out as sending from the carrier instead of GV. We could change the setting in Hangouts to always start messages with the GV account by default, but that only helped when opening and composing a new message in hangouts. Initiating a text anywhere in else in the OS, for some reason made Hangouts go back to the carrier. My guess is that they always intended GV to be a companion to the carrier, but not actually replace it. For example, if you wanted to have a private number for personal use and another more public number to give out, this would make sense.
I kept submitted bug reports about this behavior (that Hangouts should respect your default account to send from), and I know other people as well. It seems they finally got the memo and made that change a few months ago I think, and the current version of Hangouts finally respects your SMS account of choice when initiating a new msg from anywhere.
But using "OK GOOGLE" does not. Because it uses its own interface and therefore never touches your default SMS app. I'm guessing the solution proposed above uses Tasker to intercept the command, copy the transcribed message, then open a Hangouts message to paste it in. I really wish Google would issue a proper fix for this so that those of us who wish to use GV as our seamless phone number could be a globally supported function of the OS. I honestly got excited that the new GV app finally supports MMS and group texts without requiring hangouts, but sadly you still can't set GV to be the default messaging app. Its like, they almost get what we want to do, but aren't quite ready to embrace it yet. So I wouldn't hold me breathe for the compose via voice feature to be rolled out in an official fix so soon.
I'm a little confused about how Hangouts works on AW. I'm specifically interested in the functionality on an LTE watch when it's not connected to a phone.
Can Hangouts messages be received and responded to from a watch in standalone mode? Is it possible to initiate a message from Hangouts, preserving the GV caller id?
I have a Gear S3 and can receive and respond to Hangouts messages, but not initiate them. I was hoping that AW watches would handle this better.
afblangley said:
I'm a little confused about how Hangouts works on AW. I'm specifically interested in the functionality on an LTE watch when it's not connected to a phone.
Can Hangouts messages be received and responded to from a watch in standalone mode? Is it possible to initiate a message from Hangouts, preserving the GV caller id?
I have a Gear S3 and can receive and respond to Hangouts messages, but not initiate them. I was hoping that AW watches would handle this better.
Click to expand...
Click to collapse
So before Android Wear 2.0 was released, you'd get notifications that you could respond to but not necessarily do much more than that - sounds a lot like your setup on the S3. Now, you have fully functioning apps that are separate from your phone. I don't use Google Voice, but the Hangouts app lets you see all your conversations including media. Of course, you can initiate a new message in any of those conversations (without needing a notification to reply to). But, I don't see an option to start a new conversation from the watch app. Otherwise, you have full functionality. This is how most apps will work once devs release a version to the Play Store on Android Wear watches.
In short, get an Android Wear watch with a sim card and you can leave your phone at home without losing connectivity.
So I am what I would call a Tasker Beginner/Intermediate user. I have recently created a profile that triggers on the geofence of my local grocery store. The task waits 5 min, checks if the profile is still active and sends my wife a SMS asking if she would like me to pick something up.
I know she receives the SMS but it doesn't show up in either the stock messaging app or google messages app on my end. I have Messages set as default and thought that it may be playing up, so I made the built in Messaging (stock) app default and still nothing shows up in the conversation. I have also set up just a SMS task and manually fired it, SMS is received, just doesn't show on my end.
I have "Store in Messaging App" tickbox selected.
Has anyone else had issues with seeing the SMS that Tasker sends?
Matt.
MattJY said:
So I am what I would call a Tasker Beginner/Intermediate user. I have recently created a profile that triggers on the geofence of my local grocery store. The task waits 5 min, checks if the profile is still active and sends my wife a SMS asking if she would like me to pick something up.
I know she receives the SMS but it doesn't show up in either the stock messaging app or google messages app on my end. I have Messages set as default and thought that it may be playing up, so I made the built in Messaging (stock) app default and still nothing shows up in the conversation. I have also set up just a SMS task and manually fired it, SMS is received, just doesn't show on my end.
I have "Store in Messaging App" tickbox selected.
Has anyone else had issues with seeing the SMS that Tasker sends?
Matt.
Click to expand...
Click to collapse
Same issue here. I never noticed it because I dont have that option set but I just tried it and can verify the same result. I have posted a question on the Tasker group. Hopefully the developer can address the problem.
Thanks tboooe,
Good to know I'm not the only one. I'll find your post and sub to it.
I've had this issue before too. Also with using Join to SMS from my PC. I was told that it isn't an issue the developer can fix as it's really just something some phones and some messaging apps.
I am having problems with Google Messages where I can't enable the chat features (it get's stuck at 'Excuse the wait...'). So I am curious if there are other messaging applications that support RCS. I tried a search but all I got are SMS/MMS apps.
I'm getting the same issues
I never got mine to work either, anyone else?