i was having a problem with kitkat roms not being able to do mms. i could get sms and even have data but mms would not send or recieve. i finally went back to scratch and did 1 thing at a time til my mms would stop working. come to find out, it is busybox pro (stericson). if i used smart install in busybox pro (which i had been for most everything), then my mms would stop working. smart install is aggressive and it symlinks just about everything on your phone. just uninstalling busybox pro would not fix it as it had already altered whatever it was that stopped my mms from working and uninstalling it didnt revert it back right. lg flashtooling back to kitkat firmware is the only way i could get things back to stock. so doing the normal install in busybox pro only symlinks the essentials and this does not mess up my mms.
just posting this here in case anyone else is having kitkat mms issues and happen to be doing what i was doing also. hope this info helps someone out.
freebee269 said:
i was having a problem with kitkat roms not being able to do mms. i could get sms and even have data but mms would not send or recieve. i finally went back to scratch and did 1 thing at a time til my mms would stop working. come to find out, it is busybox pro (stericson). if i used smart install in busybox pro (which i had been for most everything), then my mms would stop working. smart install is aggressive and it symlinks just about everything on your phone. just uninstalling busybox pro would not fix it as it had already altered whatever it was that stopped my mms from working and uninstalling it didnt revert it back right. lg flashtooling back to kitkat firmware is the only way i could get things back to stock. so doing the normal install in busybox pro only symlinks the essentials and this does not mess up my mms.
just posting this here in case anyone else is having kitkat mms issues and happen to be doing what i was doing also. hope this info helps someone out.
Click to expand...
Click to collapse
Thanks!
Related
i rooted a friends samsung vibrant last night and everything went perfectly. i installed this rom.
now, whenever anyone sends him a picture message, it says something about "a problem with resolution or size restriction."
i've searched xda and come up with people getting blurry mms messages and the fix is to install either the cm6 mms apk or one of a few available. searching on google, everyone has the problem with the iphone and their fix is a package available through cydia.
i've had him check his apn settings and they are the same as seen in post number 7 of this thread. i've had him try using handcent and chompsms instead of the default. i've had him ensure his mobile data is on. the problem still persists.
he can send picture messages just fine. he can receive normal texts just fine.
he really wanted an aosp rom. i stuck with 2.2 so the clockwork 2.5.1.2 backup/restore would work fine.
my questions are these:
should installing a new mms apk fix this issue? does he need different apn settings? should i install a different rom altogether? should i install a newer 2.3 rom? if so, how can i get clockwork 3 installed? (i couldn't find how to do that anywhere either).
sorry this post is so long. thanks for any help.
ended up using odin back to stock then rerooted and reflashed the rom. seems to be working now.
I've done some searching on Google and didn't find anything helpful yet. I am running a mostly stock (rooted) ED04 w/ OTB 1.6 Kernel.
When I boot up my phone, I get a FC on com.android.mms
When I go into my Messaging and open an existing message it force closes.
This phone is pretty freshly setup. ie: I had a couple text messages on my phone from yesterday. I deleted those with no effect. When I sent a text message to myself (from google voice) and opened it up, I still get the FC on com.android.mms
I booted up into CWR and ran the Fix Permissions. That didn't do any good. I went back to CWR and cleared cache and Dalvik cache. That didn't do any good. Still getting FC. Any advice? I have a logcat of the crash when I try to open the message.
Here is the logcat: http://pastebin.com/YHwYs7ur
Any help in figuring out why my text messaging is crashing would be very helpful. I've been using a Fascinate since September. The only thing I did before this started happening was Titanium Backup was set to backup the green system applications and the user applications last night.
EDIT:
Sending a text message from the phone is causing a force close too. The message does send (I sent it to myself and it showed up a moment or two later after the fore close).
I think the mms database is screwed up but I'm not sure which database it is.
EDIT #2:
Well, I ran Titanium Backup again (just user apps+data, with the reboot option enabled). The system rebooted at the end of the backup and stuck at the SAMSUNG logo and will not boot up and not even into CWM with the three finger salute. Guess I'm doing the odin dance. Damn it. I had just gotten everything setup the way I wanted it. I will be leary of the Titanium Backup rebooting and see if that had anything to do with it. (Titanium Backup rebooted last night, the phone was off by the time I got to it this morning and it turned on fine except for the text messaging FC.)
I've odin'd the CWM (05-08-2011 version) and it still just sticks at the SAMSUNG screen....so ODIN back to ED03. Blech.
So am new to all this asop stuff but i followed BrwnSuperman's steps
HTML:
http://forum.xda-developers.com/showthread.php?t=1212239
to update from froyo comm romm 2.1 to JT's Vanilla Gingerbread and finally Miui 1.8.5. Now that im in Miui, everything works fine except my mms. I can only send outgoing messages but i get a force close every time am incoming message tries to come it (large or small). Is this a known issue or is there a fix for this? I reflashed it twice and even tried 1.7.29's mms.apk instead but to no avail. is there something i'm missing
Nevermind. I figured it out. I titanium restored my old txt data which has seemed to cause the problem, another fresh install with data wipe fixed it with the 1.8.12 update.
[Q] Galaxy S2 resurrection remix ics v1.3 "Currently cant send your message error"
Sup people, this is my first post....I recently flashed the resurrection remix v1.3 ROM with siyah kernel v3.1 and have been experiencing a problem with sending sms messages regardless of messaging app.
When i type the message and hit send my phone keeps losing signal and displays the message :
"Currently cant send your message.It will be sent when the service becomes available".My mobile data is enabled but still no change. How can i solve this problem?
I tried flashing ROM and kernel again but the problem still persists. I am able to receive sms messages but cannot send.
Any help would be much appreciated thanks!
Problem solved
vee4410 said:
Sup people, this is my first post....I recently flashed the resurrection remix v1.3 ROM with siyah kernel v3.1 and have been experiencing a problem with sending sms messages regardless of messaging app.
When i type the message and hit send my phone keeps losing signal and displays the message :
"Currently cant send your message.It will be sent when the service becomes available".My mobile data is enabled but still no change. How can i solve this problem?
I tried flashing ROM and kernel again but the problem still persists. I am able to receive sms messages but cannot send.
Any help would be much appreciated thanks!
Click to expand...
Click to collapse
After doing research and trying to input SMSC number numerous times i eventually got my sms working again
vee4410 said:
After doing research and trying to input SMSC number numerous times i eventually got my sms working again
Click to expand...
Click to collapse
Now iam at RR ICS 1.4 and facing sending sms problem too. Help me please...
alief.mux said:
Now iam at RR ICS 1.4 and facing sending sms problem too. Help me please...
Click to expand...
Click to collapse
Did you try setting your smsc number?
same error on 4.2.2
I have the same error. I noticed this once going to a 4.2.2 Revolt from Jelly verse. I then had baked.... Cm10 .all 4.2.2. Roms are giving me this grief. I've done everything from switching out 'bad' MMS.apk files.. Restoring APN backups with new .XML files for new APN.. Flashing over MMS fix.zip.. I've done it all and still no fix. Even downloaded goSMS and Handsceng SMs.. Applied the segtings aNd no fix. downgraded to Jelly verse... Magic.. Full MMS abilities. But.. I've had a taste of 4.2.2 and would rather dealwwith the pros until hopefully someone finds a fix for this small, yet annoying bug.
Thanks to everyone who already had put their effort into correcting this .
EPIC 4G Touch running SlimBean Build 3.3
still nothin
xxStarbucksxx said:
I have the same error. I noticed this once going to a 4.2.2 Revolt from Jelly verse. I then had baked.... Cm10 .all 4.2.2. Roms are giving me this grief. I've done everything from switching out 'bad' MMS.apk files.. Restoring APN backups with new .XML files for new APN.. Flashing over MMS fix.zip.. I've done it all and still no fix. Even downloaded goSMS and Handsceng SMs.. Applied the segtings aNd no fix. downgraded to Jelly verse... Magic.. Full MMS abilities. But.. I've had a taste of 4.2.2 and would rather dealwwith the pros until hopefully someone finds a fix for this small, yet annoying bug.
Thanks to everyone who already has put their effort into correcting this .
EPIC 4G Touch running SlimBean Build 3.3
Click to expand...
Click to collapse
So I went back to Jelly verse (4.1.2) for the sole purpose of pulling the APN XML file while MMS worked. To my surprise.. The backup APN ( using the APN Backup and Restore program mentioned in many MMS fixes) compiled a list of 1346 apns. Saved it to my SD Card. At first.. It seemed promising as I upgraded back to slimbean(any 4.2.2 build for that matter) and downloaded APN B&R .. Gave it system permissions via /system/apps program.. Backed up APNs.. And laughed at the list of 8 APNs it had backed up. nonetheless.. I moved my XML from the 4.1.2 build to the APN folder created from the backup process. Went back to APN B&R and deleted APNs as many times before.. And restored APNs via XML document from 4.1.2 build with 1346 APNs. Rebooted.. Nothing... Flashed MMS fix.zip as stated from various different resources in trying to remedy this error. .. Nothing....
EPIC 4G Touch running SlimBean build3.3. Yet again..
---------- Post added at 04:20 PM ---------- Previous post was at 04:13 PM ----------
As relevent and/or helpful as that might be as far as a universal diagnosis is concerned, rather than user-to-user, phone-to-phone ,ROM to ROM and carrier to carrier... Whilein jjelly verse I did get prompted to update Samsung software. Considering all failed attempts I went ahead and accepted the Samsung update. Given from my post above.. Obviously this doesn't have any merit towards fixing the issue.... As I'm still not getting MMS data transfer via 4.2.2 ROM.
Any and all info on things I've done I just want to document if it means the betterment of finding and identifying this as a ROM/carrier/phone issue. If not all 3 or just a combination of the 2. Or maybe even a variable and/or file overlooked this entire time.
Epic 4G Touch running SlimBean Build 3.3
I'm running stock NK1 rooted with Xposed framework installed, and it's been running fine aside from phone calls still being silent receiving and making occasionally, but just recently I list the ability to send texts using the stock MMS apk. I tried to go into Settings/More Networks and change the default to the stock Messaging apk, but Titanium is the only option. Same thing with Settings/Default Applications, only Titanium is available. Installing other SMS apps works, but nothing I do will let me choose the stock messaging app. I've tried overwriting the original with a copy of the original, turning the app off then back on again, but no luck. Permissions are correct and everything looks fine, but it will not work. Anyone seen this before?