Related
MMS Debacle/Debate/Laughter/Annoyance
Apps related but Development related for Future Builds, Move if Needed
"Error in Server Response" ***THIS APPLIES TO THE TOUCHWIZ MMS.APK VERSION***
It has been posted numerous times and people still numerous times have had problems & been easily dis-missed with the 10 or so work arounds suggested that still inevitably don't work for some select few out there. I have posted attempted possible solutions in the Apps section before & troubleshooted my own MMS problems for the past 2 months till blue in the face. I wanted to share everything I have tried and everything I have noticed in an effort that maybe a Developer out there can correct the issue for us.
Brief summary to Developers for what I think is the problem or solution: I believe in order for outgoing MMS picture messages to work you have to either A: Have the MMS.apk properly re-format the phone number that it pulls from the contacts list by removing the dashes and maybe adding the 1 in front. MMS has always worked without the 1 or the +1 in front for me.
B: Have the Contacts.apk or Contacts list designed so that it only saves phone numbers without dashes in them. I think from some of the recent Contact.apk's I messed with that current builds are not automatically putting dashes in anymore when phone numbers are saved so that may be helping alot of people.
Now onto what I have noticed past several months:
Many have dissed the poor people with failing MMS picture messaging by simply suggesting removing dashes, adding 1, adding +1, trying Handcent, Chomp SMS, Go SMS. etc etc. Also those same people said MMS works fine or works fine for them. However I question how many of those people are using Contacts saved to their actual phone as myself as it appears if your using your Google account or your SIM card to save your contacts to than this issue does not seem to exist. Also, removing dashes is not an option for Phone saved contacts or not in my current ROM build. Some newer ROM Contacts builds looks like it will let you save numbers without dashes now. Mine does not with Phone contacts. People wiht Google contacts probably did not have to worry about that as they could edit within Google. It specifically exists for people and myself with Contacts saved to their phone who may or may not be using their SIM or Google account to save their contacts to. I tried various APN and separate MMS apn settings with no difference.
I have pulled and tried just about every MMS.apk from AOSP and various froyo builds. Always Handcent, Chomp, Go SMS formatted and worked perfectly for MMS picture messaging. AOSP always worked for me but I had other issues with attaching Audio that caused force closes. propably due to my aging Obsidian V4.2 ROM. My issue was on previous build ROMs as well and been on my ROM since freshly loaded up to now where you cant recognize it is Obsidian anymore with all my mods. SMS always worked period. MMS always received perfectly for me. MMS always sent perfectly as long as I manually typed in the number without a 1 or +1 needed. MMS always worked when replying to an already received SMS/MMS. Only specifically when selecting Contacts to create a SMS/MMS does the "Error In Server Response" exist leading one to believe that its a formatting problem somewhere between MMS.apk and Contacts.apk when the softwares transfer over the phone number/contact information to create the message header.
This has been the only issue I would love fixed short of using alternative Handcent, Chomp, Go etc. It is also the reason why I have held off flashing newer builds as it is some work to re-setup my entire customized phone and still have the problem remain as I have been reading in recent Team Whiskey Nero v5 builds still.
Maybe I'm retarded or maybe I'm onto something but I felt I should put my efforts out there for developers to examine and also to take a Users poll of MMS issues regarding which people are using various ways to save their Contacts....SIM, Phone, Google account to pin point the cause.
Thank You for reading, sharing, and looking into this. If I had programming skills I would rewrite the damn MMS.apk myself since every other 3rd party seems to work and format the numbers properly to send MMS without issue.
MMS Issues
God knows I've tried just about all the ROMs in the forum and unless it's either the stock rom or one of the leaked ones, Touchwiz MMS has never worked. If I used the custom ROMs MMS suite it's fine. As soon as I mod it for Touchwiz MMS it pukes.
ive tested almost every rom and i always have my contacts save through sim and my mms is flawless every time.
I've had this issue a few times. I do NOT save my contacts to phone or sim, they are ONLY in my Google account. I finally went and edited all my contacts on the Google Contacts website to remove the dashes and 1s, and now it works fine every time.
raduque said:
I've had this issue a few times. I do NOT save my contacts to phone or sim, they are ONLY in my Google account. I finally went and edited all my contacts on the Google Contacts website to remove the dashes and 1s, and now it works fine every time.
Click to expand...
Click to collapse
Same story here. Removed the dashes and now MMS messages send perfectly.
As a way of troubleshooting why it seems to works for some people and not at all for others (even when considering the no-dash, no-paren formatting), it might make sense for people to post their configuration:
Think I'm interested in learning if people who are having this problem are
* syncing to Google,
* not syncing with Google,
* if they are typing in a phone number,
* if they are looking up a contact by name,
* if they are replying to a sent message,
* and so on.
My thought is that if we provide a little detail about each configuration - especially those that aren't working, that we might be able to figure out what's really going on.
Thanks.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant General
So far seems the majority of people are using the "Cloud" Google/Gmail Account to store their contacts and do not have the "Error In Server Response" problem. Few SIM card saving people said they have an issue but most of those have always seemed to work. Nobody has voted saving to their Phones as of yet....
Mainly cause SIM only saves basic information...the Name & the phone number so little room for error in storing the Contact data.
Contacts saved to Phone can save pictures, addresses, e-mails etc etc so I think because of that ability to save additional information it affects formatting somehow when the number is pulled and transferred over to the MMS messaging when creating a new picture message to send.
Seems like best answer for everyone is to use their Gmail/Google account to save & edit their Contacts if saving to Phone keeps causing the problem. Which is probably what I will do but have been avoiding because I do not want to see all my Gmail contacts and e-mail contacts on the phone at the same time hence why I liked keeping a clean Contacts list primarily on my phone.
***I Love all the people that voted I'm retarded
feelx77, it has nothing to do where the contact is saved, and EVERYTHING to with whether or not there are dashes in the phone number.
A phone number with dashes, ie: 000-000-0000 = "error in server response", every time, no exceptions.
A phone number without dashes, ie: 0000000000 = works fine.
Ah, but it does matter where it saved because certain locations willl or will not let you edit the dashes out and/or because SIM already saves the contact information in a basic information format without pictures, addresses, e-mails etc etc. Which is stated in my lenghty long post. Removing the dashes is already a well known solution but depending on where contacts are saved it may not allow the editin gor it may still not work with or without adding the 1 or +1 as well.
I'm full aware of the dashes removal trick. Hence why I recommended that maybe the MMS.apk (Touchwiz Version Messaging Program) or the Contacts.apk that hands over the contacts header to the MMS.apk should be rewritten/reprogrammed to automatically remove dashes in the phone number header regardless of what saved source was used IE: Gmail, SIM, or Phone.
Also this "Error In Server Response" is strictly in regards to MMS (Picture Messaging when creating a new picture message and selecting existing Contacts from within the Touchwiz Messaging app. This is not in regards to standard SMS (text messaing)
Clarified further?
BUMP
Its been a while so thought to BUMP for more poll statistics etc.
I finally caved last month and just moved my contacts over to my Google/Gmail account and as expected, as already known, I've had no problems sending MMS that way or off my SIM card. Just gave up trying to fix or get MMS Picture Messaging to work with having my contacts saved to the phone. Only saved contacts saved to the phones memory always returned the "Error In Server Response" when selcting a contact in the drop down in the messaing app.
Over all I'm going to like using Google/Gmail saved contacts better, was just avoiding as I was too lazy to port them all over and the error or issue should not have existed in the first place using phone saved contacts.
Just wanted to share, and BUMP this thread for anyone still having issues or wanting to vote in the poll. Laterz...
I have searched many forums and the market to no avail so I was hoping someone here could help.
Is there any way we, android users, can get a function similar to iOS4 users with their "group mms" option. To those of you not familiar, its basically a chat room like feature that uses your text messages. For example, if I were to create a new text on the iphone, I could add more people to it. Once it's sent out, if anyone replies, that reply will go to all of those in the group and so forth. In essence, a chat room is created where everyone receives a copy of everyone else's text.
At any rate, a few of my friends have iphones and I was hoping to be able to communicate with them in such a manner but neither the stock messaging application or handcent has this function. The few options that might work would involve having all of my friends download some new app along with myself and even that doesn't work all the time.
ANY help would be much appreciated.
Click to expand...
Click to collapse
This post was originally in a phone specific forum but I feel that it needs more exposure since it is a pretty significant issue for android. http://forum.xda-developers.com/showthread.php?t=774990
Basically it comes down to not being able to be part of a group MMS if you are not the sender.
iOS attaches all users in a group message to the header of an MMS message, and when this message is received on an android device the receiver can only see the sender, not the other people in the conversation. So, when the android user tries to reply to this message it only gets sent to the originator of the group message instead of all of the users in the group.
Currently, there is an application that handles this functionality and it is the Verzion Messages application. However, this application is out-dated and is missing other messaging features.
AT&T also has an application that addresses this issue, however, not many people have had success with it. At least for me, using my Galaxy Nexus on AT&T (4.0.2), the application opens and only shows a blank screen.
Can we get a developer to modify a current texting application, or create a new one that handles group MMS that recognizes all users of the group and will send a reply to everyone, not just the originator?
NOTE: Some other 3rd party texting applications allow group texting, but will only work if you are the originator.
How many other people have run into this issue?
I have run into the exact same issue. I have spent hours researching various workarounds, but a lot of people, forum topics, and companies think this issue isn't an issue at all. Handcent, Chomp, and Go SMS all say they have "group" messaging, but what they describe is more like a batch send out, not a threaded sms like the iphone and even now Verizon phones through the Verizon Messages Application.
I know there is an open ticket with google that is mentioned in the forum you linked to. I'm a new user so I can't link to it, but it is mentioned and linked to in post #92 on that forum you linked.
Hopefully someone or one of the bigger companies will get a handle on this.
I also would like to see this addressed. With many friends/family with iPhones it is crippling my texting abilities when I get so many group sms chats. Basically from an OS perspective it is making users of Android phones appear inferior to iPhone users.
I was looking into this today after becoming annoyed that i couldn't join a group mms thread w/ some iOS friends. It seems Verizon's VZMessages app works with the threaded group mms's. I did some tests w/ both iphone and android friends and it seems to work the same as for iphones. Since it's a vzw app, i have no idea what usability is for other carriers, and i've had some issues on my rooted dinc (display artifacts). Also, the design is terrible and looks like their target user is about 5 years old w/ all the bright primary colors and bubbly icons.
try it out and let me know how it works for you guys.
since i'm a new user, i can't post the market link to it, but you can find it in the google play app market.
Not sure if you guys saw this yet, but in the development section trikotret updated the handcent app to handle the iphone like group texts. I just installed it to try it out. I can't post links yet either but it the thread title is "Handscent Android group chat like iPhone"
Here is the flow on how to get there:
Android Development and Hacking | Android Software Development |Handscent Android group chat like iPhone
same issue
we had a text clan, or a group of people in a texting community, kinda popular here in the philippines. i've been looking for an app like those but nothing suits what we need. i tried groupme, but it crashes and needed to be online, also a force close issue in handcent which claims to have this feature. we used to do a traditional GMs or Group Messages in a send to many or batch mode only to send all GMs (equivalent to tweets in online world) to all our members. but as an android user i want to take advantage of it. here's the thing to address:
1. an app for sms/mms like gosms or equivalent.
2. this app can have a unified inbox. something like ChatOn or Socialhub of samsung but still integrated offline sms/text to local contacts.
2. options to offline only or if online.
3. group local/offline chat (threaded style, not just a batch send
4. whenever someone replied that is included in the group, it is in the same thread. or for short, sms with 2 or more person in a single thread locally.
5. even non android or typical mobile phone can receive it as a text message. so even nokia 5110 user can reply, ofcourse he will only receive what is sent to him. not always the entire thread content.
got my point?
by the way, sorry for my english.
Verizon Messaging works for me
GoSMSpro has a setting for this. Under send settings enable MMS grop chat.
handcent works ok for this but i'm in disbelief that it hasn't been addressed by google yet. did apple patent this feature or something?
i encourage everyone to star the issue at google's android project page:
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
1Speed said:
This post was originally in a phone specific forum but I feel that it needs more exposure since it is a pretty significant issue for android. http://forum.xda-developers.com/showthread.php?t=774990
Basically it comes down to not being able to be part of a group MMS if you are not the sender.
iOS attaches all users in a group message to the header of an MMS message, and when this message is received on an android device the receiver can only see the sender, not the other people in the conversation. So, when the android user tries to reply to this message it only gets sent to the originator of the group message instead of all of the users in the group.
Currently, there is an application that handles this functionality and it is the Verzion Messages application. However, this application is out-dated and is missing other messaging features.
AT&T also has an application that addresses this issue, however, not many people have had success with it. At least for me, using my Galaxy Nexus on AT&T (4.0.2), the application opens and only shows a blank screen.
Can we get a developer to modify a current texting application, or create a new one that handles group MMS that recognizes all users of the group and will send a reply to everyone, not just the originator?
NOTE: Some other 3rd party texting applications allow group texting, but will only work if you are the originator.
How many other people have run into this issue?
Click to expand...
Click to collapse
This has been addressed. This function is now standard in Jelly Bean 4.2 see link: http://forums.androidcentral.com/verizon-galaxy-nexus-rooting-roms-hacks/207431-group-text-messaging-jb-achieved.html
Hey, folks. I'm new, obviously.
I recently rooted and s-offed my LTEVO. I installed TWRP 2.6.3.0 and CM10.1 Stable (I also installed the exFAT fix). The problem I'm having and that I'm reading a lot of people are having is with MMS. I'm not sure if group messaging falls into MMS or SMS but I can neither send/receive picture or media messages, nor can I SEND group messages (although I can receive them). I'm not sure what's going on behind the scenes, whether there's a fix that I just haven't found (I have done extensive searching/trolling before making a profile to ask this question) or if this is a common issue which may have been resolved in newer builds. Essentially, I was wicked pumped when I found out that I could receive group messages from people because the stock, unrooted LTEVO would receive "multimedia messages" from everyone participating in the conversation individually instead of all within the same thread or whatever you wanna call it. But, as I've come to find out, I can't actually participate in these group sessions, I can only SEE them organized within one text thread (which is still better than stock, but disappointing that it doesn't take one seemingly essential step further). Also, I thought it was just crappy Sprint service, but it seems that I can't send or receive multimedia messages (that aren't in text form). I was excited, again, to see that the preview of the image I was going to send was minimally compressed, if at all. I was sick of sending people screenshots of blurry, illegible caca, but again this feature falls short and now I can't actually send or receive any form of media.
Anyway, any help would be greatly appreciated. I can't seem to figure out what I'm doing wrong, or maybe what I'm just NOT doing right. At any rate, if anyone could shed some light on my unfortunate situation that'd be stellar. I'm forced to use Voxer for the time being.
I'm having the same problem. Any assitance is welcome!
I can't say I completely understand your issue but will give an answer with my best guesstimate as to a fix.
You are trying to group messages with others that have iPhones. iPhones natively send texts as mms while android natively sends as sms. Hence your problem (I think).
You need to use a third party messaging app. There are a couple that handle this but I use Go Sms Pro. It allows you to send and receive texts all while staying in the group without splitting the messages.
Once you install go sms pro you need to change a few settings in the app (you can find the correct group settings on Google easily) and disable the notifications from the stock messaging app (so you don't get multiple notifications for one text).
Hope this is what you were asking about as it is an issue for a lot of people.
Sent from my Nexus 10 using Tapatalk 4
This module enables the use of other SMS apps to send and receive messages through Google Voice. When this module is activated, any SMS messages sent will be rerouted through Google Voice, and any messages that are received by the Google Voice app will be displayed in SMS apps.
Setup:
Download the APK and install.
Open the app, enable it, and select the account you want to use.
Open Xposed, activate the module, then soft reboot.
You will get a notification to sign in to authorizing the app to access your account. Tap the notification, then tap allow. For some reason the notification is not dismissed automatically; you can dismiss it manually.
If the module does not work at this point, try soft-rebooting again.
Known issues:
This module will only work with the old Google Voice app, version 0.4.7.10 or lower. If you already updated to a newer version, you must uninstall it and sideload the old version. You can find the latest working version here. Once you've downgraded, open the Play Store and set the app not to auto-update, so you won't run into the same issue later. This is fixed as of v3.1.2.
When I had the default SMS app is set to the AOSP Messaging app (com.android.mms, not to be confused with Google Messenger), the module would not work for outgoing messages. On one device, incoming messages did not work either. I was using version 5.1.1-720affab4e. I'm still not sure what causes it.
On my S3 test device, I sometimes experienced a crash of the system process on boot. This did not seem to affect the functionality of the module.
There is a known issue with Xposed reading SharedPreferences in certain situations, due to file permissions issues. With this module, this would cause that disabling the module from within its own settings would not help, and the only option would be to deactivate the module from inside Xposed Settings and soft-rebooting. I added some code to work around this, however it's possible that it could still occur. This is fixed (hopefully) as of v3.1.2.
Old issues:
Many of the old bugs present in the original XVoice+ are still in this version. These include:
Emojis may cause issues. (This issue should be fixed for incoming messages as of v3.2.0).
There is no support for MMS
Occasionally, messages may show up with the wrong timestamp, there may be duplicate messages, or there may be a delay before the messages appear.
Google Voice 5.0+
As mentioned above, the module will not work with the new updates to Google Voice. This is because they completely rewrote the code for the app, which would require XVoice++ to be rewritten as well to properly hook it. This is further complicated by the fact that Google obfuscated the code, making it much harder to figure out what is going on. Additionally, it is probable that with every update the code will be obfuscated diferently, requiring XVoice++ to be patched every time to support the new update. Since the whole point of this module is to replace the functionality of the Google Voice app, and it is functional with the old version, I will not be working on supporting the new versions of the app at this time. This is fixed as of v3.1.2.
Devices tested on:
Verizon LG G3 (vs985) running a custom build of CM 12.1
Sprint Samsung Galaxy S3 (d2spr) running CM 13.0 (11/17/2016 nightly) without phone service
Acknowledgements:
Koush
CM team
@runnirr
@B2OJustin
@iHelp101
Jake Hamby (a former engineer at Google, who helped maintain the internal SMS processing code for Android) for providing a lot of information about PDU structure and processing, and patiently answering my questions.
Xposed Repo
XDA:DevDB Information
XVoice++, Xposed for all devices (see above for details)
Contributors
BehindTheMath, @runnirr, @B2OJustin, @iHelp101
Source Code: https://github.com/BehindTheMath/XVoicePlus
Xposed Package Name: io.behindthemath.xvoiceplus
Version Information
Status: Stable
Current Stable Version: 3.2.1
Stable Release Date: 2017-05-08
Created 2017-02-15
Last Updated 2017-05-08
Reserved
Reserved
Nice to see something happening with this. I more or less abandoned it after switching over to Hangouts. What are your plans for it though? I'd probably consider hooking into Hangouts for any future development.
Edit: Btw, this latest source has also been tested and confirmed working on Nexus 7 stock (without cell service) and at least one other phone with a touchwiz based rom + smart watch (Don't recall which kind). Though rom updates may or may not have changed that since then.
B2OJustin said:
Nice to see something happening with this. I more or less abandoned it after switching over to Hangouts. What are your plans for it though? I'd probably consider hooking into Hangouts for any future development.
Edit: Btw, this latest source has also been tested and confirmed working on Nexus 7 stock (without cell service) and at least one other phone with a touchwiz based rom + smart watch (Don't recall which kind). Though rom updates may or may not have changed that since then.
Click to expand...
Click to collapse
Thank you for the feedback.
Truthfully, in my humble opinion, this app is mature. You guys have done a fantastic job of taking Voice+ and adapting it to a new platform. I only needed to fix the issues caused by new or changed Android internal code. Unless someone has a specific feature request, I think it's ready for a stable release.
That being said, there are a few things I would like to look into at some point in the future. The main one is the viability of supporting the new GV app. I never liked Hangouts. It was slow when it was first released, and it's still slow and buggy. 90% of my contacts use Whatsapp, and the GV app along with XVoice+ helped me with the handful that still use SMS. The only reason I still have Hangouts installed is to manage multiple accounts, and for VoIP calls. Now that the new GV app supports the former, and it looks like the latter is coming at some point, I would love to have XVoice++ support it so I could get rid of Hangouts entirely.
I am happy to see you figured out what I was unable to. In terms of Google Voice 5.0 you could in theory hook GCM messages directly. The class is "com.google.android.gms.gcm.GcmReceiver". You would use the same onRecieve hook already in the module. I have never seen GMS code obfuscated, so you likely would not have to worry about it. Even if a GCM message for some reason is not a text message the module would be able to filter it out (It checks the Intent contents).
iHelp101 said:
I am happy to see you figured out what I was unable to. In terms of Google Voice 5.0 you could in theory hook GCM messages directly. The class is "com.google.android.gms.gcm.GcmReceiver". You would use the same onRecieve hook already in the module. I have never seen GMS code obfuscated, so you likely would not have to worry about it. Even if a GCM message for some reason is not a text message the module would be able to filter it out (It checks the Intent contents).
Click to expand...
Click to collapse
That's an interesting approach. I'll have to look into it when I have time.
THANK YOU!
OP first of all thanks for doing this!
Second I have a question, I'm still running CM11, because I use Voice+, the original utility that XVoice+ was based on. I have updated my google voice app to the latest version and Voice+ still works, I'm not sure how. You might consider looking at the source code for Voice+ and see if the type of hooks it uses are possible with xposed.
Again thanks for what you have already done.
KnightTim said:
OP first of all thanks for doing this!
Second I have a question, I'm still running CM11, because I use Voice+, the original utility that XVoice+ was based on. I have updated my google voice app to the latest version and Voice+ still works, I'm not sure how. You might consider looking at the source code for Voice+ and see if the type of hooks it uses are possible with xposed.
Again thanks for what you have already done.
Click to expand...
Click to collapse
Voice+ works for you for incoming messages too?
Edit: I looked through the source for Voice+. They listened for the notification from the GV app, and then canceled it, which meant you had the notification flash for a second before being intercepted by Voice+. One of the benefits of XVoice+ was that you could disable the notifications completely in the GV app, and XVoice+ would intercept the message anyway.
iHelp101 said:
I am happy to see you figured out what I was unable to. In terms of Google Voice 5.0 you could in theory hook GCM messages directly. The class is "com.google.android.gms.gcm.GcmReceiver". You would use the same onRecieve hook already in the module. I have never seen GMS code obfuscated, so you likely would not have to worry about it. Even if a GCM message for some reason is not a text message the module would be able to filter it out (It checks the Intent contents).
Click to expand...
Click to collapse
I looked at the GV 5.0 code some more. I couldn't figure out how to hook com.google.android.gms.gcm.GcmReceiver, but I was able to hook the com.google.android.apps.voice.backends.gcm.GcmListenerService, which is the entry point for the message in the GV app. It appears to be very easy to intercept the messages from there. The issue is, since GV 5.0 added support for multiple GV accounts, there's no easy way to tell which account the message is for. The GCM message comes with a user_hash field, but it's just a hash, and I can't find a list of corresponding accounts in SQLite or in SharedPrefs. I presume it's decoded somewhere in the app, however, the only code that references it is obfuscated. It would technically be possible to implement a setup routine which would send a test message and grab the user_hash for that message, but that's a bit inelegant.
BehindTheMath said:
I looked at the GV 5.0 code some more. I couldn't figure out how to hook com.google.android.gms.gcm.GcmReceiver, but I was able to hook the com.google.android.apps.voice.backends.gcm.GcmListenerService, which is the entry point for the message in the GV app. It appears to be very easy to intercept the messages from there. The issue is, since GV 5.0 added support for multiple GV accounts, there's no easy way to tell which account the message is for. The GCM message comes with a user_hash field, but it's just a hash, and I can't find a list of corresponding accounts in SQLite or in SharedPrefs. I presume it's decoded somewhere in the app, however, the only code that references it is obfuscated. It would technically be possible to implement a setup routine which would send a test message and grab the user_hash for that message, but that's a bit inelegant.
Click to expand...
Click to collapse
Interesting, it is a nice discovery to have been made. Google has gone extremely with obfuscation recently. I also didn't realize they added multi-account support. My bad for giving any false.
iHelp101 said:
Interesting, it is a nice discovery to have been made. Google has gone extremely with obfuscation recently. I also didn't realize they added multi-account support. My bad for giving any false.
Click to expand...
Click to collapse
No, I think your idea is the best option for supporting GV 5.0. We just need to figure out how to identify the accounts. I'm going to try to dig through the code some more.
It has been a while since I've played with Xposed but when I get a little extra time I'll see what I can come up with. Figuring out exactly what to hook has always been the troublesome part though. If it turns out you do need to make use of the account hashes, I'd suggest looking lower in the callstack rather than higher. ie; Find the source of the hashes instead of the final target. You can then map those to usernames as soon as they're generated.
v3.1.2
I've released a new version, v3.1.2. The primary new feature in this version is support for Google Voice 5.0+.
I spent some more time poking through the GV sources, and I found that the list of accounts and corresponding user_hashes are stored in a Base64-encoded field in SharedPreferences called "registered_accounts". I added some code to decode the list and check the incoming message against user_hash of the account we want.
I also released the module on the XPosed Repo, so now it can be installed through the Xposed Installer.
Unfortunately, I lost the password to the signing key. I created a new key, but this means you will need to uninstall the old version before installing the new one.
New user. Tested on Voice 5.0+. Works flawless so far! This is excellent!
I have no idea why Google decided to NOT allow the Voice 5.0+ to be default SMS app.......but this module works around that issue AND allows me to use my fav texting app in its place. Thank you!
Could you explain the Sync settings a bit more. I just want to understand better. For example, why did you include those settings in the app Are there battery/data implications to using them? What is the downside to disabling all the sync settings?
Stupifier said:
New user. Tested on Voice 5.0+. Works flawless so far! This is excellent!
I have no idea why Google decided to NOT allow the Voice 5.0+ to be default SMS app.......but this module works around that issue AND allows me to use my fav texting app in its place. Thank you!
Could you explain the Sync settings a bit more. I just want to understand better. For example, why did you include those settings in the app Are there battery/data implications to using them? What is the downside to disabling all the sync settings?
Click to expand...
Click to collapse
When you send a message through XVoice++, XVoice++ doesn't put that message in the SMS database, the SMS app does. So if you send a message from another source, for example, the GV app or webapp, that message would not show up in your SMS app. Sync checks the master message list on GV's server to see if your device is missing any messages, and if it is, it sticks them into your SMS history.
It also has the benefit of catching any incoming messages that might have been missed. XVoice++ isn't perfect, and once in a while it won't catch an incoming message, sometimes because the GV app was sleeping (although I suspect this issue might be eliminated with GV 5.0+, since they switched to GCM). Enabling Sync will force XVoice++ to manually check if there are any new messages.
I personally have always had all the Sync options enabled, and the interval set to 15 minutes, and I haven't seen any issues. You can try it for yourself and monitor it. I don't think there's any reason it should impact battery or data usage, since it's just a quick request to GV's server. When I look the logs, it never takes more than a few seconds.
BehindTheMath said:
When you send a message through XVoice++, XVoice++ doesn't put that message in the SMS database, the SMS app does. So if you send a message from another source, for example, the GV app or webapp, that message would not show up in your SMS app. Sync checks the master message list on GV's server to see if your device is missing any messages, and if it is, it sticks them into your SMS history.
It also has the benefit of catching any incoming messages that might have been missed. XVoice++ isn't perfect, and once in a while it won't catch an incoming message, sometimes because the GV app was sleeping (although I suspect this issue might be eliminated with GV 5.0+, since they switched to GCM). Enabling Sync will force XVoice++ to manually check if there are any new messages.
I personally have always had all the Sync options enabled, and the interval set to 15 minutes, and I haven't seen any issues. You can try it for yourself and monitor it. I don't think there's any reason it should impact battery or data usage, since it's just a quick request to GV's server. When I look the logs, it never takes more than a few seconds.
Click to expand...
Click to collapse
Thank you for this explanation. So now I'd like to test how well these sync features work. if I understand correctly, I could test this by simply sending a text using GV app directly.....Then open my SMS app and check to see if my SMS app actually shows this newly sent message. The Sync features directly affect how and when SMS app grabs new Incoming/Outgoing GV messages. Am I understanding correctly?
Stupifier said:
Thank you for this explanation. So now I'd like to test how well these sync features work. if I understand correctly, I could test this by simply sending a text using GV app directly.....Then open my SMS app and check to see if my SMS app actually shows this newly sent message. The Sync features directly affect how and when SMS app grabs new Incoming/Outgoing GV messages. Am I understanding correctly?
Click to expand...
Click to collapse
Correct, besides for when you sent an outgoing SMS from the device itself, since then the SMS app stores it right away.
I'm so happy to see this working! Great job :victory:
one bug I've noticed, it seems to choke on accented characters. try sending " õœôöø ", for me it force closes both Voice and my SMS app
Hello,
I use/rely on Send SMS actions in multiple macros, throughout the macro stages to give me real time updates of what's happening in the Macros. It works fine for most parts.
The problem with some mobile carriers, specifically the one I use: Mint mobile (which is a MVNO on the T-Mobile network) that after sending many text messages, they might block you from sending new messages or put an invisible bottle neck so some text messages might arrive with a big delay or won't arrive at all. This makes it very unreliable and tricky as some "notification received" based triggers that you know that were supposed to trigger but didn't, so it's not entirely clear if it's because some legit issue with the notification not being received or identified by Macrodroid (yes, I know you can look at the macro logs) or just because your mobile carrier prevented you from receiving new text messages for a short duration.
All of this, is leading me to look for Send SMS alternatives (don't think Send Email is a good enough alternative as I want to receive notifications in my phone - And emails could suffer from the issues described above too) that don't require UI Interaction, and let me explain why: These are the main cons/issues with sending messages that require UI Interaction (for example Send WhatsApp message action that's being offered inside Macrodroid):
a.) If you have any macro that uses UI Interaction, and you want to send a message throughout the macro, because sending a message requires UI Interaction, this could break the existing flow of the macro as you need to be able to return to the same screen and state that you had before you had to send a message through UI Interaction.
b.) If you have multiple macros being triggered at the same time, and they all need to send messages, this will create a race condition - So what do you do? I don't think Macrodroid has a semaphore mechanism to prevent such case? As you basically need to make any existing macro to go to sleep, wait until the current macro that's using ui interaction to send a message finishes, before the ones that wait can continue in the same order they requested to send the message.
With that being said, are there any alternative ways (without rooting the phone) to send messages through 3rd party apps, without using UI Interaction?
Some methods to consider:
1.) Can you use the "send intent" action to tell an app to send a message to a certain user/phone without actually using UI Interaction? I know this could pose a security risk and it's unlikely to exist in any major big 3rd party messaging apps, but maybe smaller ones or ones that were created exactly for this purpose (such as MDHelper is using an older SDK to support certain actions that Macrodroid can't do)?
2.) Could you use some sort of APIs of certain big messaging apps, such as WhatsApp, Skype, Viber, Telegram, etc to send a message to a certain user/phone just by issuing some API call? Is there any support like that in Macrodroid to login to these services and then send messages (This is more Postman program level I suppose so might be a little out of scope)?
3.) Perhaps a more practical approach to avoid issues a & b, is simply not to use UI Interaction but simply send a message with the details (using send email or something like that - which again, as stated above, might not be 100% reliable) to another machine/phone that handles sending the messages, which is creating another point of failure, and could add some overhead/delay, so might not be the most ideal solution either.
Any other methods or alternatives that you know or could recommend?
Thank you.