I am using the "CM 11.0 with app2sd, glove mode, dual boot for all S4 variants" (http://forum.xda-developers.com/showthread.php?t=2383143&nocache=1) ROM on my US Cellular Galaxy S4 (SCH-R970). I have been updating regularly, but skipped a few. Somewhere between the 20140412 build, and the 20140423 (and newer) build, my phone stopped being able to break long SMS into smaller. I reverted back to the 20140412 build, and the problem is resolved. With the newer build(s), the SMS simply fails to send; using any SMS app (Hangouts, Handcent...). No error message is announced; other than "SMS failed to send." Reducing the character count to less than 160, and the message sends fine.
Thoughts?
Thank you.
Related
Hi,
I have a unrooted absolutely Stock Nexus S T-MOBILE version which I manually updated to Ice Cream Sandwich 4.0.3 using the official update file.
The problem I'm facing is that ever since I upgraded to ICS I'm unable to send SMSs but I can receive SMSs just fine. I did some searches and realized that the SMSC should be a valid number where as mine is showing 00. I tried to edit this by going to *#*#4636#*#* > Phone Information > SMSC update. But every time I try to update it, it says update error.
I'm using the phone in India Mumbai and the SMSC should be +919820005444 (verified on my friend's Android Device.
I also read that this could be an error due to a faulty SIM card but when I used the same SIM card in another device it works perfectly. I also tried other SIM cards in my phone, all of them are unable to send SMSs.
Please help!
Use this guide: http://forum.xda-developers.com/showthread.php?t=979564
I was unable to send/recive mms on ICS if i were on 2g/3g, but wifi worked.
Finally found out how to fix it today (at least my issue).
I wrote down whatever info i had in the APN-settings for wap and mms on my phone and merged them, putting all the mms info in the wap-apn, where none existed and added an extra ",mms" to the apn type-field.
Mine dont work too i am in uk called cs told me tobcheck apn still nothing
Sent from my Nexus S using Tapatalk
Hi.
I have LG Optimus L3 E400f (LG-E400f), with SDMergE400 Mod by gellmaR & cRaZyByte, which was posted here by f3tus.
Whenever I'm trying to send sms, it seems that I can't insert a new line by clicking enter.
Instead, clicking enter causing the message to be sent.
However, I'm able to paste a message that already has new lines in advance.
Which means, if I'm writing the message in another platform, e.g. whatsapp, in which I can insert new lines by clicking enter, and then I'm copying the message and pasting it in a sms, then it's successful - the message has new lines, and the recipient receive it with these new lines.
BTW, this is not a ROM issue, since I used different ROMs, like AOKP E400M6 (Stable and unstable) by yayakuya.
Here are my device details:
Model number: LG-E400
Baseband version: LG-E400f-V10f
Kernel version: 2.6.38.6-CM [email protected] #1 (with AOKP E400M6) or 2.6.38.6-CM [email protected] #3 (with SDMergE400)
Does anyone else have this issue with this or with a similar device?
need4steer said:
Hi.
I have LG Optimus L3 E400f (LG-E400f), with SDMergE400 Mod by gellmaR & cRaZyByte.
Whenever I'm trying to send sms, it seems that I can't insert a new line by clicking enter.
Instead, clicking enter causing the message to be sent.
However, I'm able to paste a message that already has new lines in advance.
Which means, if I'm writing the message in another platform, e.g. whatsapp, in which I can insert new lines by clicking enter, and then I'm copying the message and pasting it in a sms, then it's successful - the message has new lines, and the recipient receive it with these new lines.
BTW, this is not a ROM issue, since I used different ROMs, like AOKP E400M6 (Stable and unstable) by yayakuya.
Here are my device details:
Model number: LG-E400
Baseband version: LG-E400f-V10f
Kernel version: 2.6.38.6-CM [email protected] #1 (with AOKP E400M6) or 2.6.38.6-CM [email protected] #3 (with SDMergE400)
Does anyone else have this issue with this or with a similar device?
Click to expand...
Click to collapse
I had a similar issue. Then i installed Go sms app from Play store.. it worked well.. My issue was confined only to text messages and not whats app as you said above !
Thanks a lot for your confirmation!
Will you please write here your Baseband version?
Mine is LG-E400f-V10f.
BTW, I saw that GO SMS Pro suggests to turn off the built in sms system in order to prevent double notifications. How did you did it?
EDIT: Did you turn it off by just unticking the notification setting in the settings? If so, there are still double messages.
Hi,
I search the internet for the notification "unsent messages" but I is not successful. I can not find the "badgeprovider" in running applications and "do not keep activities" in the development options. When I clear the notification it disappears "unsent messages", but when I return to the menu SMS / MMS it reappears and I can not get rid of it .. If someone has a real solution please. For even *#272#IMEI# does not work, I get a message marked with "UNKNOW APPLICATION". And by the way I also have another problem, I do not know if its just the ROM or another, but by the time the two touch buttons at the bottom of the phone no longer works, I have to press the "Home" button and keys working again again.
ROM: CM 10.2 Nightly
Kernel: KT-SGS4
Launcher: Nova
Widgets; ZooperWidget
Recovery: CWM Touch 6.0.3.6
Model: GT-I9505 16Go (Intl - jfltexx).
Sorry for my bad English, i'm French and i use Google Translation .
Attachement Image.
Here is the logcat, I do not know if this will help you :/.
Hi Guys,
Has anyone tried the encryption feature found in Security settings? I'm using a recent nightly CM11 from Quarx/Blechd0se (Thanks, brilliant work!) quite stably for days now, but fail to make the encrypt phone function work...
When fully charged and USB powered, which are requirements, the successive encrypt phone buttons end up on a green android picture. This screen misses text and a progress bar which should normally appear on top of the screen, as seen on some screenshots. Even left for several hours, nothing progresses and a simple press on back button cancels action immediately which proves nothing has been encrypted in the meanwhile.
Took a Catlog and the only interesting message is the following:
Code:
01-02 01:34:23.732 E/Cryptfs ( 1197): Cannot get size of block device
In case it helps, find attached the output of mount command : View attachment mnt.txt
Could you have a look / help me out? (add to bug list if it applies)
In fact, for me, this function needs to be activated for connecting to my professional mails ...
Thanks in advance! :good:
Cheers
Further tested...
Hello all,
Just some more info... I flashed back to Quarx' CM9 and quickly tested once more the encryption and face the same problem but I didn't catlog, neither checked the mounts... Then I flashed Epsylon3's CM9 and quickly checked with the same result too...
But then I checked at catlog and now I get another type of error... Which is interesting and maybe promising as I already read some posts about this message...
Code:
04-14 21:11:13.101 E/Cryptfs ( 2219): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Problem seems to be more general than only Quarx/Blechd0se's CM11 but a friend uses a CM9 flavor on a Samsung Galaxy S and has encrypted the phone successfully...
All in all it's linked with the filesystem (block device or not), how it is formated (yaffs/ext3/ext4) and mounted (mount/mount_all)...
Some interesting reading on jira.cyanogenmod.org/browse/CYAN-87 (not linked, I don't have 10 posts yet)...
Hope to find, test and come back with some more info soon...:fingers-crossed:
Cheers!
Device : Oneplus 6T (A6013)
Oxygen OS Version : 9.0.11
Android Auto Version : 3.9.585064-release
Whatsapp Version : 2.19.17
If i receive a whatsapp, i can reply.
If i ask it to send a whatsapp independent of a message being received, it goes through the motions, confirms what i've said and asks if i want to send it.. When i confirm, it says "sending" but it never does it.. The whatsapp application has no knowledge of any message even attempting to be sent...
Has anyone else seen this problem or have a work around for it?