Ok so a few days ago i came across a thread to increase the mms sending limits on the One. However for the life of me i cant find the thread again I have searched for an hour. On stock settings i cant even send a 10 sec video clip through mms. I understand i can email it however thats not what im looking to do. If anyone knows how or can help point me in the right direction that would be greatly appreciated! Thanks in advanc
I'm looking for this as well
Sent from my HTC One using xda premium
jrock79 said:
I'm looking for this as well
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I swear I saw a post on how to do it. I just can't find it anywhere. I know it can be done tho. It's horrible even a 10 second video is to big to send via mms. At least for my phone it is.
MMS Compression kills me. Can't send someone a nice high res pic. Sizes it way down and compresses it to hell. The main way I share pics is through texting and now it's just stupid to send a pic through texting since it looks horrid. Never had compression issues on iPhone unless it's through video but I don't care much for that.
Sent from my HTC One TrickDroid 5.5.0 using XDA Premium
How about using a different texting app such as Gosms? You can adjust the maximum mms size in that app.
Sent from my HTC One using Tapatalk 2
MNDZA said:
How about using a different texting app such as Gosms? You can adjust the maximum mms size in that app.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
It's too bad gosms is ugly. :x
Sent from my HTC One TrickDroid 5.5.0 using XDA Premium
/system/customize/MNS/default.xml
Look for MMS_Msg_Size1, 2, 3, and MMS_Msg_Size_Choose
Edit values to something like 500K, 1000K, 2000K -- whatever you like. Save, reboot. Might have to clear data on messaging app to get new values to take.
Edit: Current values are in data/data/com.android.mms/shared_prefs/com.android.mms.customizationBySIM.xml. Edit there and reboot.
cschmitt said:
/system/customize/MNS/default.xml
Look for MMS_Msg_Size1, 2, 3, and MMS_Msg_Size_Choose
Edit values to something like 500K, 1000K, 2000K -- whatever you like. Save, reboot. Might have to clear data on messaging app to get new values to take.
Edit: Current values are in data/data/com.android.mms/shared_prefs/com.android.mms.customizationBySIM.xml. Edit there and reboot.
Click to expand...
Click to collapse
i changed them however on a reboot that reverted back to stock.. did i do something wrong?
Edit forgot to clear data sorry
Edit still wont keep new settings after reboot thanks for all you help tho much appreciated
ceelo2008 said:
i changed them however on a reboot that reverted back to stock.. did i do something wrong?
Click to expand...
Click to collapse
Need to be running a custom kernel that allow remounting /system as rw. Stock kernel write protects /system so modifications are lost on reboot.
I made some size changes to mine, and now it looks like it doesn't want to send mms messages any longer, text messages work just fine.
Sent from my HTC One using xda app-developers app
cschmitt said:
Need to be running a custom kernel that allow remounting /system as rw. Stock kernel write protects /system so modifications are lost on reboot.
Click to expand...
Click to collapse
if we edit the xml before we flash, will it keep the values or will the stock kernel make it revert back. Thanks for any info
cschmitt said:
/system/customize/MNS/default.xml
Look for MMS_Msg_Size1, 2, 3, and MMS_Msg_Size_Choose
Edit values to something like 500K, 1000K, 2000K -- whatever you like. Save, reboot. Might have to clear data on messaging app to get new values to take.
Edit: Current values are in data/data/com.android.mms/shared_prefs/com.android.mms.customizationBySIM.xml. Edit there and reboot.
Click to expand...
Click to collapse
I'm on a HTC One S and I did this too. Apparently the mms app now says the limit is what I've set (that is 1MB), but when I attach a photo this gets compressed nonetheless, even if it's smaller than 1MB.
Are you guys on the HTC One experiencing the same?
That's one main reason I moved away from stock messaging to Textra app. It's way smoother than the stock HTC one messaging not to mention It's light weight, not a memory hogger, very simple and smooth. The others like go sms and handcent are buggy and full of ads. Go to the playstore and try it for yourselves. All of my friends with Androids love it. BTW..it's Free.
Sent from the "ONE" phone for me
Related
The title says it all. I cannot get mms to work on Vanilla 2.2. Any Rom really. The only one it seems to work on is Stock 2.1. I've run various versions of KaosFroyo, Tazz Froyo, Nonsensikal, and the Sense Froyo Roms. None of them will work with mms on my phone for some reason.
I do however remember a while back that mms did work when I ran a version of KaosFroyo. Must have been something like v20 or somewhere around there. I've tried the methods of flashing and saving different apns and nothing works. Any help would be greatly appreciated. I dislike Sense. It's too laggy for me. Any help please?
Sent from my Eris using XDA App
Bump?
Sent from my Eris using XDA App
What carrier?
Sent from my Eris using XDA App
Verizon. I'm worried my phone is starting to die out.
Sent from my Eris using XDA App
Zalatorisaurus said:
Verizon. I'm worried my phone is starting to die out.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Why do you say that?
Sent from my Eris using XDA App
Bad battery life, this, major lag sometimes.
Sent from my Tazz Vanilla
Zalatorisaurus said:
Bad battery life, this, major lag sometimes.
Sent from my Tazz Vanilla
Click to expand...
Click to collapse
Bad battery life is common especially if your flashing a lot if Roms ...try recalibrating your battery there's a forum that walks u through it. I feel your frustration I had no MMS when I upgraded to 2.2 (cricket network) but I tried a lot of stuff and finally figured it out ..I also had bad battery life but I figured out a work around by disabling 3G after every use. I basically read a lot of forums and experimented with different things to get MMS working.
Sent from my Eris using XDA App
bigshotrob22 said:
Bad battery life is common especially if your flashing a lot if Roms ...try recalibrating your battery there's a forum that walks u through it. I feel your frustration I had no MMS when I upgraded to 2.2 (cricket network) but I tried a lot of stuff and finally figured it out ..I also had bad battery life but I figured out a work around by disabling 3G after every use. I basically read a lot of forums and experimented with different things to get MMS working.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
I've been on the same ROM for about a month now and no dice. I don't know what to do. Battery isn't terrible, it just doesn't seem to be what it used to be. I like sharing pictures with my friends and family while I'm out and about, so mms is crucial for me.
Sent from my Tazz Vanilla
Zalatorisaurus said:
I've been on the same ROM for about a month now and no dice. I don't know what to do. Battery isn't terrible, it just doesn't seem to be what it used to be. I like sharing pictures with my friends and family while I'm out and about, so mms is crucial for me.
Sent from my Tazz Vanilla
Click to expand...
Click to collapse
I agree. Make a backup of your current ROM and then load up 2.1 again and make sure the settings are correct. After that do a fresh flash of Vanilla Tazz and then delete Telephony.db from /data/data/com.android.providers.telephony/databases/. Then delete the MMS.apk from /system/app and then try installing the attached Mms.apk and reboot your phone. Let me know if this works
bigshotrob22 said:
I agree. Make a backup of your current ROM and then load up 2.1 again and make sure the settings are correct. After that do a fresh flash of Vanilla Tazz and then delete Telephony.db from /data/data/com.android.providers.telephony/databases/. Then delete the MMS.apk from /system/app and then try installing the attached Mms.apk and reboot your phone. Let me know if this works
Click to expand...
Click to collapse
Still a no go. Sigh. Are you sure I'm supposed to remove telephony.db and not mmssms.db?
Sent from my Eris using XDA App
You can do both..Try doing both and removing the MMS.apk and install the one I gave you again
Still doesn't work. Great.... thanks for the help though. I really appreciate it.
Sent from my Eris using XDA App
Zalatorisaurus said:
Still doesn't work. Great.... thanks for the help though. I really appreciate it.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Thats crazy. One more thing to try is deleting the mmssms.db and telephony.db but leave the stock mms.apk. Also make sure the build.prop has this ro.com.google.clientidbase=android-verizon-us
ro.com.google.locationfeatures=1
ro.cdma.home.operator.numeric=310012
ro.cdma.home.operator.alpha=Verizon
If that doesnt work than I have no idea whats wrong.
bigshotrob22 said:
Thats crazy. One more thing to try is deleting the mmssms.db and telephony.db but leave the stock mms.apk. Also make sure the build.prop has this ro.com.google.clientidbase=android-verizon-us
ro.com.google.locationfeatures=1
ro.cdma.home.operator.numeric=310012
ro.cdma.home.operator.alpha=Verizon
If that doesnt work than I have no idea whats wrong.
Click to expand...
Click to collapse
Tried the last method and it says all that already. Still a no go. I think my phone is just broken. Thanks for bouncing ideas with me though.
Sent from my Eris using XDA App
Well sorry I couldn't help. I tried everything I know. Im fairly new to this stuff.
Sent from my nonsensikal froyo using XDA App
bigshotrob22 said:
Well sorry I couldn't help. I tried everything I know. Im fairly new to this stuff.
Sent from my nonsensikal froyo using XDA App
Click to expand...
Click to collapse
Don't be sorry. You were really the only one that provided some possible solutions. Looks like it's Stock 2.1 or a new phone for me.
Sent from my Eris using XDA App
I like xtrSense myself. You can download ADW or LauncherPro and disable sense and it isn't bad.
Sent from my Eris using XDA App
That's what I was doing, still seemed kinda iffy on lag.
Sent from my TazzFroyo Eris
Zalatorisaurus said:
That's what I was doing, still seemed kinda iffy on lag.
Sent from my TazzFroyo Eris
Click to expand...
Click to collapse
Ok ... for your MMS problem ... I was having issues with randomly being able to send/not send MMS/Email/Pic messages ....
I tried all the backup/restore/APN/options and was still having issues.
In the Telephony database, I had 2 bad rows of data, one of which semi replicated some of the pathways used for my MMS messages. I downloaded SQLite editor ( I think by Speed Software, same people that make Root explorer ).... I was able to manual delete the bad rows of data from the database. I did a new APN backup, and the bad rows were gone.
TADA!!
The SQLite editor is available on the market, and it costs like $3 or $4 ...
- JB
johnrbrown1968 said:
Ok ... for your MMS problem ... I was having issues with randomly being able to send/not send MMS/Email/Pic messages ....
I tried all the backup/restore/APN/options and was still having issues.
In the Telephony database, I had 2 bad rows of data, one of which semi replicated some of the pathways used for my MMS messages. I downloaded SQLite editor ( I think by Speed Software, same people that make Root explorer ).... I was able to manual delete the bad rows of data from the database. I did a new APN backup, and the bad rows were gone.
TADA!!
The SQLite editor is available on the market, and it costs like $3 or $4 ...
- JB
Click to expand...
Click to collapse
NOT SO FAST, MY FRIEND!!!
***
I need to correct myself ... after I deleted the row of data with the "unnamed" APN, nothing happened when sending MMS ....
***
I did a restore ... went back into the telephony.db :: "carriers" table and gave the APN a name ...
In my case, I had two rows of data referencing Verizon .... ( using the www.vtext.com address ) .... I left the regular one for Verizon, but the unnamed row I gave an alias and called it "VZW" ....
did a backup of the APNs, tested through multiple messaging apps, text, mms, picture, and reply to MMS, and all have worked without any problems.
I hope all this makes sense .... PM if you have any problems ( If you haven't already given up on the possibility of getting it working ) ...
- JB
As the title says, here is a new mms.apk for you guys to use on the 2.2.1 roms that IS NOT blurry.
Just adb push it to system/app or use root explorer to move it there and overwrite - you can also rename your old one to mms.apk.bak in case you want to switch back later.
I'm still working on the smilies..
this is touch wiz yes?
edit: just pushed it, it is touch wiz and no blurry mms.
for those who like smiley on the keyboard this still doesn't have that.
Sent from my SGH-T959 using XDA App
xtone said:
this is touch wiz yes?
edit: just pushed it, it is touch wiz and no blurry mms.
for those who like smiley on the keyboard this still doesn't have that.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yeah, still working on that - but at least it is a step closer.
true, I used yours hoping you had that fixed coz I got the blurry mms taken care of myself, but we are getting closer! thx for all your contributions heathen.
Sent from my SGH-T959 using XDA App
Just look at my post on eugeens post and I posted a fix for it just change it to n95 on the custom user agent.
0bey <-_->
december.underground said:
Just look at my post on eugeens post and I posted a fix for it just change it to n95 on the custom user agent.
0bey <-_->
Click to expand...
Click to collapse
Yes, but that assumes you are using the cyanogen mms or another mms modded with user changeable user agent and not a straight stock mms like this - which has been changed to an iphone user agent. This is for people who want a stock mms.
Thnx gonna give this a try
is this flashable via CWM if complied in a zip?
This can be pushed with RootExplorer
AgentFour20 said:
This can be pushed with RootExplorer
Click to expand...
Click to collapse
dont have root explorer... nor do i know how to do system pushes... if its CWM flashable i can compile a zip.. that much i know how to do.. lol
NM I'm an idiot.
Sent from my SGH-T959 using XDA App
mytouchguy said:
dont have root explorer... nor do i know how to do system pushes... if its CWM flashable i can compile a zip.. that much i know how to do.. lol
Click to expand...
Click to collapse
I can probably build the flash from my phone, brb.
Built from my phone. Should work.
Flash:
http://db.tt/fEeC5OE
Want is "non-blurry mms"? Cause I've never really noticed anything "Blurry" in it.
Sent from my SGH-T959 using XDA App
Thank you so much! I was looking for a fix for a few weeks and was afraid I would have to flash back to plain 2.2 roms. I didn't want to switch to an AOSP mms to fix this either didn't like the feel of it. I guess I got used to the tw mms. Thanks Again!!
You sir are the MAN!!!
Sent from my SGH-T959 using XDA App
I'm getting a message "the media content was not included due to a picture resolution or message size restriction" when receiving a message from anyone besides myself. Has anyone else seen this issue?
thanks a lot man!
Doesnt work on bi winning v2 i keep getting failed messages when i send texts.
LowDub said:
I'm getting a message "the media content was not included due to a picture resolution or message size restriction" when receiving a message from anyone besides myself. Has anyone else seen this issue?
Click to expand...
Click to collapse
Getting the same problem, is there any fix to it, or does it mean it just doesnt work?
so when i take a screenshot using either power/home or i am on on CR 4.5 and it has a screenshot feature in the pwer menus, it saves to the gallery just fine. the pic is clear in the gallery.
the issue is, when i send it in a text it is all scrambled and fuzzy. i am using go sms, but i cheked the stock messaging app and it is fuzzy in that one also.
what is going wrong in the select a pic/send it in a text process that is screwing up here? and it is on both ends, the pic is fuzzy for me when i send it and for the receiver.
I have the same problem when sending it to my friend. She has a LG Thrill...I figured her phone sucks. Everyone else gets them fine.
Sent from my ADR6425LVW using xda premium
andrewp3481 said:
I have the same problem when sending it to my friend. She has a LG Thrill...I figured her phone sucks. Everyone else gets them fine.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
that cant be the issue because i can test it by sending it to myself...and both the pic i send and the one i receive are the same...fuzzy. but again, it's fine in the gallery when i select it
Go to stock messages and hit menu then mms. Then check to make sure the max size is highest. If it's not the highest it could downscale it
Sent from my ADR6425LVW using XDA
Po1soNNN said:
Go to stock messages and hit menu then mms. Then check to make sure the max size is highest. If it's not the highest it could downscale it
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
great suggestion, but it was already set to the highest (1200k). thanks tho!
Po1soNNN said:
Go to stock messages and hit menu then mms. Then check to make sure the max size is highest. If it's not the highest it could downscale it
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
i got it working based off your initial suggestion! it was GO SMS compressing mms messages. I upped the size limit and the compression limit to max and now everything is fine. I overlooked this initially due to the fact that the pics appeared fuzzy in the stock message app as well, but i guess it transferred in the compressed pics from GO.
alphabets said:
i got it working based off your initial suggestion! it was GO SMS compressing mms messages. I upped the size limit and the compression limit to max and now everything is fine. I overlooked this initially due to the fact that the pics appeared fuzzy in the stock message app as well, but i guess it transferred in the compressed pics from GO.
Click to expand...
Click to collapse
Glad I could help
Sent from my ADR6425LVW using XDA
So, I am unlocked, rooted, and have the unsecure kernel installed. I'm having trouble modifying my build.prop though. I've tried pushing a modified build.prop through ADB while in recovery, but the changes don't take. Any suggestions?
Never mind. Solved my own problem. Not sure which did the trick, but I mounted System in TWRP, pushed my file, and then did a CHMOD 755 from TWRP on the file... That worked. Yay!
What did you change in the build. prop?
I am trying to get google wallet to work.
Sent from my HTC6435LVW using xda premium
nev310 said:
What did you change in the build. prop?
I am trying to get google wallet to work.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I was only changing the LCD Density. But my difficulty was just in getting the file modifications to stick, so if all you are trying to do is make a change, the above method will make it stick.
SolusCado said:
I was only changing the LCD Density. But my difficulty was just in getting the file modifications to stick, so if all you are trying to do is make a change, the above method will make it stick.
Click to expand...
Click to collapse
Yes something with the phone won't allow to write to the system even with root. So mounting system in twrp is the only way until s-off.
Try deleting the current build.prop then push the new one. I've heard that works.
Sent from my HTC6435LVW using xda app-developers app
SolusCado said:
I was only changing the LCD Density. But my difficulty was just in getting the file modifications to stick, so if all you are trying to do is make a change, the above method will make it stick.
Click to expand...
Click to collapse
Did your LCD Density modifications work? If so, is this to make the resolution smaller on the screen? I hate how big the font and everything is even when the font is set to 'Small'
I'm also interested to hear if you were successfully able to modify the build.prop and change the density. I love this screen but it almost looks like an HDTV with a PC plugged in running at 648x480 resolution!
JWhetstone02 said:
Did your LCD Density modifications work? If so, is this to make the resolution smaller on the screen? I hate how big the font and everything is even when the font is set to 'Small'
Click to expand...
Click to collapse
PsyberEMT said:
I'm also interested to hear if you were successfully able to modify the build.prop and change the density. I love this screen but it almost looks like an HDTV with a PC plugged in running at 648x480 resolution!
Click to expand...
Click to collapse
Yes, it worked. The precise steps are as follows:
Copy your build.prop to a location where you can edit it and locate the ro.sf.lcd_density entry. The default value is 480. I have mine set to 370. The lower the number, the smaller your text. Save this file to your computer.
Boot into Recovery.
Within Recovery, mount the System partition. In TWRP, this is under the "Mount" button.
Use ADB to push the modified file into the system partition. You don't need to delete the existing build.prop first. From you command prompt on your computer, this would be "adb push 'file path/name of modified file' /system/build.prop".
I don't know if this step is required, but I used TWRP's file manager to browse to the system\build.prop file, and then ran CHMOD 755 on it.
Reboot into Android, and the new changes should have taken effect.
May we see a screenshot?
Sent from my HTC DNA using Tapatalk.
karn101 said:
May we see a screenshot?
Sent from my HTC DNA using Tapatalk.
Click to expand...
Click to collapse
Sure. A couple screenshots are attached.
Any weird visual issues with apps or anything?
suzook said:
Any weird visual issues with apps or anything?
Click to expand...
Click to collapse
No, and that's where I'm impressed with the latest Sense. It handles the adjustment much better than prior versions. It maintains its scaling in a lot of places despite my DPI changes - which preserves the integrity of its layout at the expense of taking advantage of the new DPI. And I'm okay with that, because it means I can keep the components I like without any "weird visual issues" and still use other apps that scale appropriately.
Had to bring it back up. I have changed my density, and I love it. but I noticed that not everything is scaled down. Is this the case for those of you that have successfully done this as well?
I have noticed that the htc messaging app, keyboard and the pulldown notification menu is not resize.
Also apps like the flashlight app in the CODIS rom is skewed as well as other apps.
Is this a problem that can be corrected or just have to deal with it?
JWhetstone02 said:
Had to bring it back up. I have changed my density, and I love it. but I noticed that not everything is scaled down. Is this the case for those of you that have successfully done this as well?
I have noticed that the htc messaging app, keyboard and the pulldown notification menu is not resize.
Also apps like the flashlight app in the CODIS rom is skewed as well as other apps.
Is this a problem that can be corrected or just have to deal with it?
Click to expand...
Click to collapse
At least for the messaging app you can just pinch to make it smaller.
Sent from my GT-P7510 using xda app-developers app
Bigandrewgold said:
At least for the messaging app you can just pinch to make it smaller.
Sent from my GT-P7510 using xda app-developers app
Click to expand...
Click to collapse
Yea, but I still prefer it to go smaller lol. It's still too big
JWhetstone02 said:
Yea, but I still prefer it to go smaller lol. It's still too big
Click to expand...
Click to collapse
Well I think all you can do is setting system font to small then pinching it to as small ax possible.
Sent from my HTC6435LVW using xda app-developers app
SolusCado said:
Sure. A couple screenshots are attached.
Click to expand...
Click to collapse
That's awesome. I may have to try that. Good job and thanks for the directions.
I'm also interested to hear if you were successfully able to modify the build.prop and change the density.：P
faner said:
I'm also interested to hear if you were successfully able to modify the build.prop and change the density.：P
Click to expand...
Click to collapse
Oh this mod works. Just follow the OPs steps.
My concern was a few apps not resizing. See screenshots
-HTC Droid DNA-
Has anyone been able to send and receive sms/mms messages on the Jetstream using At&t? I've tried Gosms,handcent sms,chompSms, etc., but No Luck :'(
Sent from my HTC One XL using Tapatalk 2
nymikey said:
Has anyone been able to send and receive sms/mms messages on the Jetstream using At&t? I've tried Gosms,handcent sms,chompSms, etc., but No Luck :'(
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
You would need to 1st enable sms by altering the build.prop settings - assuming you have root access and stuff.
The specific line to be altered would be:
ro.ril.reject.cs.ss.enabled=1
ro.ril.reject.mo.sms.enabled=1
ro.ril.reject.mo.ussd.enabled=1
This should enable messaging and should work provided your AT&T sim has the feature enabled. Not sure about MMS though-haven't tried.
kailashpchhabria said:
You would need to 1st enable sms by altering the build.prop settings - assuming you have root access and stuff.
The specific line to be altered would be:
ro.ril.reject.cs.ss.enabled=1
ro.ril.reject.mo.sms.enabled=1
ro.ril.reject.mo.ussd.enabled=1
This should enable messaging and should work provided your AT&T sim has the feature enabled. Not sure about MMS though-haven't tried.
Click to expand...
Click to collapse
In my build prop I only see the first line you have here not the other two. Do I have to add them manually? If yes, where in the build prop do i place it? Thanks!!!!!
Sent from my HTC One XL using Tapatalk 2
nymikey said:
In my build prop I only see the first line you have here not the other two. Do I have to add them manually? If yes, where in the build prop do i place it? Thanks!!!!!
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
They are on line 15,16,17 or so in the stock rom's build.prop file. Which rom you on? Could find it and let you know.
And if they are missing completely from the file, you can add it in anywhere. What I have noticed is, at the end of the original file, give a few spaces after the last part, feed it in, save, reset phone. And you would need to even enable the phone function - tutorials for that already on the forum.
kailashpchhabria said:
They are on line 15,16,17 or so in the stock rom's build.prop file. Which rom you on? Could find it and let you know.
And if they are missing completely from the file, you can add it in anywhere. What I have noticed is, at the end of the original file, give a few spaces after the last part, feed it in, save, reset phone. And you would need to even enable the phone function - tutorials for that already on the forum.
Click to expand...
Click to collapse
I'm using El Diablos Rom. I added the lines but still can't send or receive. I've used Hancent sms, chompsms. I even downloaded a stock HTC messaging app because my tablet was missing one. The only thing working for me is GOSMS using the goChat option, such is ok except for the fact that people who I send to don't see my number, they see some other username that GoSms assigned to me. I guess i will live with that. THANKS FOR ALL YOUR HELP!!!!!
Sent from my HTC One XL using Tapatalk 2
nymikey said:
I'm using El Diablos Rom. I added the lines but still can't send or receive. I've used Hancent sms, chompsms. I even downloaded a stock HTC messaging app because my tablet was missing one. The only thing working for me is GOSMS using the goChat option, such is ok except for the fact that people who I send to don't see my number, they see some other username that GoSms assigned to me. I guess i will live with that. THANKS FOR ALL YOUR HELP!!!!!
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I am also on el Diablo itself. The 16th line has got the sms function. It says reject sms. By default it is set to 1.change it to 0. Should solve the issue.
And I use go sms only. The others never worked for me.
Sent from my HTC PG09410 using xda app-developers app