Well, this is an odd issue and i'm sure many other have it because all of my friends with GS3's have this problem. I have a rogers GS3, my friend has a Telus and other videotron and multiple times a week, when we try to send a moderate or long sms (3 lines and more) the phones fails to send the message. This is very odd because i've tried everything from a factory reset, full odin wipe, different roms, and nothing works. I'm on CM10 M2 now and the problem is also there.
When i try to send a long sms, it fails, then i sent a short one right after, it works, then i copy and resetn the original one that failed and it faisl again. I pretty sure many of you have it because we have 3 different GS3 on 3 different networks and it happens to all of us
I tried looking around, i have not found much, maybe somebody has such problem and perhaps a solution?
This happened to me earlier this morning. No idea what can even cause an issue like this.
nobody??? im sure many people have this
I think this is based on all aosp roms.
I don't know if it's fact or opinion, but I always get the "sent" message after receiving the "not sent" error.
In other words, it seems like it still sends the whole text, but just throws you an error initially.
Can someone correct me if I'm wrong?
Well i can correct you wrong because i've tested it it does not sent the messages nor does it have anything to so with AOSP roms because i've used both AOPK and they both have the issue,
I send long sms no problem.. some in fact so. Long it automatically breaks them into two. What firmware are you on.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
First off this belongs in Q&A so I will move it
Second AOKP is also considered an AOSP type ROM
There should be an option in your mms app to split messages over 160 characters. Make sure it is checked.
On the Touchwiz ROMs that came with the SIII and all TW custom ROMs this is not an issue. This is a Touchwiz phone so changing your ROM to anything but that will have some bugs and require fixes and workarounds.
Friendly Neighborhood Moderator
Contact your carrier
Especially if you're having this issue on and off
Do other apps work? I use ChompSMS (fixes lots of annoying bugs in the TW SMS app) and I can send long messages fine.
kennyglass123 said:
F
On the Touchwiz ROMs that came with the SIII and all TW custom ROMs this is not an issue. This is a Touchwiz phone so changing your ROM to anything but that will have some bugs and require fixes and workarounds.
Click to expand...
Click to collapse
i have to disagree. I had like i said in OP, i tried ALL roms, stock, stock rooted, cyanogen and many other, this was an issue in all roms.
polish_pat said:
i have to disagree. I had like i said in OP, i tried ALL roms, stock, stock rooted, cyanogen and many other, this was an issue in all roms.
Click to expand...
Click to collapse
are you using a mms app other than what's provided with the rom? And are you able to send any messages at all? or does it fail to send only on long ones?
If you were on stock and still can't send any/long messages, check your apn settings and make sure it's correct for your provider, especially if you are installing roms (stock or custom) that are specifically developed for AT&T phones. From your profile I'm assuming you have a Canadian version.
Check the APN settings. If that's all correct, return the phone for a new one
all apn settings are fine and this is not an issue with the phone because like i said, it would be one hell of a coincidence if this happened to both of my friends with gs3s on different providers. Also i am using stock sms app and this only happens with moderately long sms, it doesnt always ahppen, its random
If it's intermittent, and it's not just you but also your friends, it sounds like a provider problem. From what I have been reading on different forums, it seems service in Canada has been sketchy because they're adding LTE towers everywhere.
I don't know if that's really the case, but all I can say is texting works well for me down here on the AT&T network, both on AOSP (which also includes AOKP as you were mistaken earlier) and stock-based ROMs, although I do get the error on AOSP based roms for long messages. I've asked my friends and they say they receive the whole message just fine.
Last thing I can think of is if you flashed a custom kernel and it messed with some of your drivers. I know KToons kernel has modified drivers, and you're supposed to flash the stock kernel provided in that thread if you're going back to stock. Try that and see if that fixes your problem.
yup, i've flashed ktoon kenel as i had major issues with faux kernel as per this thread: http://forum.xda-developers.com/showthread.php?t=1937476
i'll report back in a week to see if any different
thanks for you help
Related
Hi folks,
Sometimes I can't receive picture messages and I can never send them to my wife's telus phone. They show up as white squares with no text included. Anybody had this or can provide suggestions? I have tried many things so far. Full story below...
Thanks
**************************
I have a Telus T989/ S2X. I have had it for 1.5 yrs and have flashed numerous ROMS since I rooted it about a year ago. Over this time I have had MMS issues on and off.
From early ICS ROMS (darkside) and now to Jelly Bean roms (CM10 nightly, Jedi Jelly, Slim-Star...and more) I have had a strange issue. I can send picture messages to almost everyone and receive from almost everyone. Occasionally I have an issue receiving from friends on the Rogers/ Fido network and it stalls at 'downloading'. I tried unchecking auto-retrieve and it does not fix it. I have also tried multiple radios on multiple roms.
More recently my msgs cannot be viewed when I send them to my wife's phone ( I know, a blessing sometimes right?). She is on the same network (Telus) and has no problem sending/ receiving from anyone. When I send to her it shows as a white/ blank square and none of the text I typed shows up. Regular text are no problem ever.
I called Telus support and they ran me through checking the APN settings and a bunch of other tests sending pics back and forth and no fix. They are going to escalate the problem. I tried the trick of sending yourself a picture via gmail too without any luck. I didn't tell them I was rooted and on 4.1.2....but I have tried tons of diff roms and done a bunch of searching on the forums and google.
Just today I tried the Koodo 4.0.4 rooted ROM with no luck. Then I got pissed off and backed everything up and rolled back to the Telus 2.3.5 Gingerbread ROM. Guess what? MMS worked just fine!!?? I double checked the APN settings and they were identical.
So....has anyone else had this issue? I don't want to be stuck on Gingerbread just to use MMS. Could it be that the newer versions of the MMS/ SMS have issues? I noticed that when I went back to 2.3.5 it said "converting to MMS" when I attached a pic. I never see that in any other ROM.
Any suggestions or solutions that people have come across? I am slightly frustrated....especially since my wife's Nexus S has no problems and my S2X is way better but failing.
Thanks for your time and thoughts folks!
CHBAD
maybe u were send pics that were larger than the network supports. Hypothetically telus may only support 5meg attachments while Rogers/Fido does 10 ( I think this is actually the case but I'm not 100% sure). Use a third party app like hand cent or gosms that supports MMS compression and see how u fair
icenight89 said:
maybe u were send pics that were larger than the network supports. Hypothetically telus may only support 5meg attachments while Rogers/Fido does 10 ( I think this is actually the case but I'm not 100% sure). Use a third party app like hand cent or gosms that supports MMS compression and see how u fair
Click to expand...
Click to collapse
Thanks for the response. I will try that...and update later.
CHBAD
CHBAD said:
Thanks for the response. I will try that...and update later.
CHBAD
Click to expand...
Click to collapse
It seems like some are getting through with Handcent. So the stock app in CM10 is not working then? I should try different size files maybe to see if that is a factor like you said.
Alright, I’ve had Sourcery JB on my phone for a while now. V4.3
Over time these are the problems I just can’t understand and need some light shined on them please.
The GPS:
Is a joke. It has NEVER been accurate one single time since I’ve installed the rom. It’s always 2000+m OFF. what the faq? All my apps are updated, what’s the deal?
Sending pictures:
I use GOSMS. However, I CANNOT for ANYTHING send pictures via text in this app. I have to go through the native app every single f’ving time and that only works 50% of the time. Wtf is going on here? Is it AT&T? Is it the rom or my phone or what?
Would going back to stock JB fix all these issues? I love the ROM(s) but the problems listed above are VERY important to get working as they are some of most basic functions phones have.
I almost just updated to JBSourcery V5 and tried sending picture using default text msg app. Still, same results. It won’t f’ving send.
Please help.
Not sure about your GPS issues - mine has always been pretty quick to lock regardless of the ROM I'm using.
But in regards to your problems with MMS messaging - I had the same issue on every ROM, including stock until I switched to AOKP. I called ATT to make sure everything on their end was as it needed to be. Double and triple checked my APN settings, all to no avail. Not sure what it was about this particular ROM, but since flashing, I haven't had any issues.
Long time fan; first time post.
I was hoping this posting had provided a solution, but the 'Contacts Fix' did not help with my apparent issue:
(Synergy ROM) Phone app now not working?
I'm lovin' the Synergy ROM, however every time I start up the phone, I always get the 'com.android.phone has stopped' error.
Please, would anyone like to take a look at the Logcats provided?
Attached in the zip file are two logcats. One records my attempt to make a phone call; the other I hope reflects what's happening when the phone is starting up: AttemptedPhoneCall.txt & StartingUpPhone.txt
Sure, I could go back to my High On Android ROM (Have to give a nod to its author, Max of GalaxyS3root.com), but it was Max that raved about Synergy in the first place, and it has grown on me.
Despite the fact I can't send or receive any calls. I can text and surf, but it's not a phone anymore.
I never received that error on Synergy, but I have seen it on other ROMs. Have you tried a full wipe and reflash? In my experience, flashing Synergy worked best when I flashed it from another TW based ROM.
You could try a different kernel such as ktoonsez kernel. I had a lot of issues with the standard ziggy kernel when I used synergy
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Will do
altrikdout21 said:
I never received that error on Synergy, but I have seen it on other ROMs. Have you tried a full wipe and reflash? In my experience, flashing Synergy worked best when I flashed it from another TW based ROM.
Click to expand...
Click to collapse
Thanks, altrikdout21.
Yes, I intend to. I was just curious if there were some developers out there that like to look at logcats for kicks.
Didn't think of that.
Domoo said:
You could try a different kernel such as ktoonsez kernel. I had a lot of issues with the standard ziggy kernel when I used synergy
Click to expand...
Click to collapse
Problems with the ziggy, uh?
Ok, I'll try another and let you know.
Thanks, Domoo.
Got it working...almost sort ya.
Restored my last ROM, HighOnAndroid. I did do the reflash of Synergy with a stock kernel, but there was no improvement, and so I restored my previous ROM. I can now start up the phone without the 'com.android.phone has stopped' error. However, there's a problem. I still can't make a phone call! Yikes! Now how can that be??? I did a ROM restore. Shouldn't the phone app be back as it was? It appears all the other apps are working. I can text, surf, etc. What's happening here?
I start up the phone app, select a contact, press the phone icon on the contact's screen, it comes up like it's going to initiate a call but then I see the 'end call' just as fast and the phone app then retreats back to the previous screen listing the contact I had selected to call.
As an aside, is there a place to drop off you logcats on this forum? Being an old VB programmer (what's that you ask?!), I'm curious to see what these new fangled 'android programmers' can do. However, now I'm ever more anxious to find out what's wrong with the phone app since I've restored my ROM only to find the one lone thing I do use regularly (it's a phone for pete sake!) is still not working.
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
The newest firmware from the latest OTA can be found in the 2nd post in this thread: http://forum.xda-developers.com/showthread.php?t=2485319
If you've already flashed the latest firmware then I'm not sure what to tell you... maybe ask your favorite rom developer to take a look at the latest OTA in regards to this issue?
If it has the stock rom and OTA update why not take it to the store and let them look at it. Something might be wrong with your account.
movieman999 said:
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
Click to expand...
Click to collapse
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
movieman999 said:
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
Click to expand...
Click to collapse
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
dickenam said:
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
Click to expand...
Click to collapse
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
movieman999 said:
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
Click to expand...
Click to collapse
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
dickenam said:
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
IM getting it now. but not exactly the same. phone freezes without warning and I have to toggle airplane mode and restart to get it to unfreeze. this happened after the last OTA update. I am going to a custom ROM until I don't read anything about this for a while
Alright, first off, i've been trying to fix my device for a few days, and scouring the internet; i've been completely unable to fix this issue
After installing an AOSP rom, I accidentally screwed with my Sim settings. My LTE and MMS are both broken on all roms that I have tried, and I can't for the life of me get them fixed. LTE sometimes works when I force LTE only, but then I can't make calls or send SMS.
(Just a quick rundown to highlight the main points)
☻LTE won't work unless I force LTE only. (AOSP)
☻MMS won't send, unless i'm on the stock ROM (I've used GOSMS, Hangouts, and Stock)
I feel like I have literally tried everything. Different recoverys, different root methods, different basebands, I've reflashed the APN, and even paid a visit to my friend Murry at Sprint; still no fix. My ESN is still good, along with my MEID. Any help would be greatly appreciated; this has been giving me hell for the past few days.
Akasa Fox said:
Alright, first off, i've been trying to fix my device for a few days, and scouring the internet; i've been completely unable to fix this issue
After installing an AOSP rom, I accidentally screwed with my Sim settings. My LTE and MMS are both broken on all roms that I have tried, and I can't for the life of me get them fixed. LTE sometimes works when I force LTE only, but then I can't make calls or send SMS.
(Just a quick rundown to highlight the main points)
☻LTE won't work unless I force LTE only. (AOSP)
☻MMS won't send, unless i'm on the stock ROM (I've used GOSMS, Hangouts, and Stock)
I feel like I have literally tried everything. Different recoverys, different root methods, different basebands, I've reflashed the APN, and even paid a visit to my friend Murry at Sprint; still no fix. My ESN is still good, along with my MEID. Any help would be greatly appreciated; this has been giving me hell for the past few days.
Click to expand...
Click to collapse
Cant help you with the LTE...
As for the MMS, try the attached file - bryansmmsfix (at your own risk). just flash in your recovery of choice (just not stock, of course). This worked for mine last night.
Akasa Fox said:
Alright, first off, i've been trying to fix my device for a few days, and scouring the internet; i've been completely unable to fix this issue
After installing an AOSP rom, I accidentally screwed with my Sim settings. My LTE and MMS are both broken on all roms that I have tried, and I can't for the life of me get them fixed. LTE sometimes works when I force LTE only, but then I can't make calls or send SMS.
(Just a quick rundown to highlight the main points)
☻LTE won't work unless I force LTE only. (AOSP)
☻MMS won't send, unless i'm on the stock ROM (I've used GOSMS, Hangouts, and Stock)
I feel like I have literally tried everything. Different recoverys, different root methods, different basebands, I've reflashed the APN, and even paid a visit to my friend Murry at Sprint; still no fix. My ESN is still good, along with my MEID. Any help would be greatly appreciated; this has been giving me hell for the past few days.
Click to expand...
Click to collapse
Did you get it fixed? If you can't get it, start fresh.
http://forum.xda-developers.com/showthread.php?t=2648855
ColeTrain! said:
Did you get it fixed? If you can't get it, start fresh.
http://forum.xda-developers.com/showthread.php?t=2648855
Click to expand...
Click to collapse
You're the man! Thank you very much for pointing me towards that topic, that just solved each and every one of my problems. Thank you!