Related
I have my EVo on MetroPCS, and i have been trying to get MMS and other things working for a while.
For the most part i have had everything working 100% at one time or the other, but most things not at the same time, due to kernel and apks.
I wrote a guide to getting the MMS working, but it relies on Ava' v2RC3 ROM, witch is a port from the incredible.
http://forum.xda-developers.com/showthread.php?t=739409
I was messing around with a stock Fresh 3.1 ROM, i rebooted to recovery and pushed the Mms.apk from the incrediable to the /ssytem/app folder, then rebooted the phone.
I started the messaging app.... it now looked like the MMS app from the Ava_v2RC3! So i tired to send a MMS to my email address....it sent!! SO to recap, OEM EVO ROM working 100% + the Mms.apk from the incredible + Token419's metrov3 flash = working MMS!!
BUT, now here in lies the problems:
When you send a message on the OEM EVO MMS, it takes you to the thread page so you can view the conversations of that person and you.
With the MMS app from the incredible it goes to "loading"....and hangs, it does nothing...BUT the MMS is still sent. Now if you open the MMS app and click on a person to view their conversation thread, it says "loading"....and hangs....
SO i think we need a custom Mms.apk from the incredible for the EVO for metropcs/cricket users!!!!!
I want to know if anyone out their can modify the Mms.apk to work on the EVO.
Or point me in some direction...
It just needs to finish loading the threads...thats alll...
If you compare the Mms.apk from sprint and the Mms.apk from incredible, the sprint is bigger. I have decompiled both files, but now i have no idea what i am looking at.
Now before we get in to posts about "did you try..."
-I tried Fresh and OMJ Froyo ROMs, both had same results from above.
-I tried pushing the com.htc.recources.apk .... framework-res.apk ... Rosie.apk from the incrediable to the phone (with working MMS), rebooted, still same results from above.
-I tried building a ROM from the Fresh and OMJ ROMs, and packing the framework files into it. Still same results from above.
-Downloaded handcent form market... was NOT able to send MMS at all with handcent. so i uninstalled it, then was able to send again.
i had the same results, this seems to plague not only the Evo but also the Hero Sprint stock MMS.apk's, i loaded a sprint port on my eris and had the same issue, swapped in an Mms.apk from a verizon rom and had the same results.
I too have been decompiling both Mms.apk's with the apktool and am going to run a dif later on the files to check for differences.
one thing i saw was some references to some sprint frameworks, im going to dig and ssee if i can find them as well.
A resolution seems to be simply swapping the mms.apk file, BUT i think the issue is actually in a framework file, and that swapping the mms.apk simply does not point to that framework that is not working properly on alternate carriers.
we will have to see
@token:
But i took the com.htc.resources.apk and the framework-res.apk from the incredible, pushed them to the EVO, still with same results. Did i miss a framework file??
All you need is Mms.apk from any aosp Rom. Bugless beast, or cyanogenmod for example.
chavonbravo said:
All you need is Mms.apk from any aosp Rom. Bugless beast, or cyanogenmod for example.
Click to expand...
Click to collapse
Tried it....did not work. I tried one from CM and one from AVa.
When you goto send a MMS, it seems to do nothing... and the send button gets grayed out.
i saw somewhere about a code change that needed to be done from hero rom to port to g1, but i cant find the thread with the code change in it anymore.
but pushing the raw frameworks from another rom will surely break the rom im guessing. i would stay away from that if at all possible but its definately worth testing out, to find where our issue is.
unfortunately my time will be very limited for the next month or so, have quite alot of stuff to attend to.
As suggested by chavonbravo, i tired the Mms.apk from the supersonic AOSP ROMs (for my EVO) With NO luck
So i thought, how about a Mms.apk from cyanogenmod for a Verizon phone...
It worked well, send and receive MMS, but sometimes it would fail on both.
Now the strange part, when you send a MMS with the cyanogenmod Mms.apk for the incredible, it will attach a XML file before the image. i think it was a SMIL.xml. So if you send a MMS to another mobile user, they cant see the image, because of the XML file. If you send the MMS to a email address, its ok, because you get the image and the XML, and you can open just the image.
Why is it sending the XML file too?
Now even stranger, after useing this method, i downloaded the handcent app. It also would send the XML file first. SO i then deleted the Mms.apk (adb shell rm /system/app/Mms.apk), rebooted, and the handcent STILL sent the xml......
getting closer...
xboxhacker said:
As suggested by chavonbravo, i tired the Mms.apk from the supersonic AOSP ROMs (for my EVO) With NO luck
So i thought, how about a Mms.apk from cyanogenmod for a Verizon phone...
It worked well, send and receive MMS, but sometimes it would fail on both.
Now the strange part, when you send a MMS with the cyanogenmod Mms.apk for the incredible, it will attach a XML file before the image. i think it was a samil.xml ?? So if you send a MMS to another mobile user, they cant see the image, because of the XML file. If you send the MMS to a email address, its ok, because you get the image and the XML, and you can open just the image.
Why is it sending the XML file too?
Now even stranger, after useing this method, i downloaded the handcent app. It also would send the XML file first. SO i then deleted the Mms.apk (adb shell rm /system/app/Mms.apk), rebooted, and the handcent STILL sent the xml......
getting closer...
Click to expand...
Click to collapse
I am not an expert on the MMS protocol(s?) but i believe the XML file IS THE MMS, and the picture is the attachment from the XML if that makes sense.
I believe the XML file contains the recipient/sender/subject/text/ and what attachments there are to the message, the picture is then the attachment and called upon by the XML file.
Definitely a good find and im still working on this as well, my time is just limited but i have a few things i want to try.
one thing i noticed when i unpacked a sprint based mms.apk file was that it was calling on the specific hardware (hero) in this case, and since the app i dropped in was desirec (eris) it didnt match up, im going to go through and edit that to point to the proper frameworks to see if i can at least get it working on my phone, but that could explain why the incredible didnt work on the evo.
Im also toying with getting a AOSP or Cyanogen one together, since that would be legal to distribute i belive, even if i do find a solution, it will be instructions, as i dont want to edit/repackage/redistrubute proprietary files without consent, which i dbout we would get since we are taking their hardware/development to use on an alternate carrier.
i found this:
http://www.w3.org/AudioVideo/
which points to SMIL, which is the spec for MMS messages i belive, i belive it gets put into an XML, then wrapped with SMIL, which links to all the stuff in the message.
I could be way off, but im pretty certian the XML file its sending is actually the MMS message itself.
I think our problem is still within the sprint mms.apk or an associated framework, because i think its still trying to interact with sprint's servers and not our alternate carrier.
I believe the XML file contains the recipient/sender/subject/text/
Click to expand...
Click to collapse
Nope...just images info.
here is a sample of the SMIL.xml file....
Code:
<smil>
<head>
<layout>
<root-layout width="320px" height="480px"/><region id="Image" left="0" top="0" width="320px" height="320px" fit="meet"/>
</layout>
</head>
<body>
<par dur="5000ms"><img src="screenshot_3.png" region="Image"/></par>
</body>
</smil>
one thing i noticed when i unpacked a sprint based mms.apk file was that it was calling on the specific hardware (hero) in this case, and since the app i dropped in was desirec (eris) it didnt match up, im going to go through and edit that to point to the proper frameworks to see if i can at least get it working on my phone, but that could explain why the incredible didnt work on the evo.
Click to expand...
Click to collapse
I saw that too, when i unpacked the sprint one.
Now this is funny... Incredible users putting the EVO Mms.apk on the incredible and it works fine!!!! LOLOLOL
For anyone having a problem with pictures showing up from contacts in the stock MMS application on Froyo ROMs, the EVO Mms.apk works fine.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=754832
Also, you can't put an Mms.apk from 2.2 aosp on a 2.1 rom, and vice versa. The bugless beast Mms.apk works great for the stock 2.1 rom.
FYI...
Bug report:
Using the stock Mms.apk from a Incredible, you can not send a MMS with Wifi is on. It might be ROM specific, i am using Fresh 3.0.
xboxhacker said:
FYI...
Bug report:
Using the stock Mms.apk from a Incredible, you can not send a MMS with Wifi is on. It might be ROM specific, i am using Fresh 3.0.
Click to expand...
Click to collapse
Just curious, in your APN, do you have the type set to MMS?
If so that should tell it to send MMS via your mobile network even if you are connected to wifi.
token419 said:
Just curious, in your APN, do you have the type set to MMS?
If so that should tell it to send MMS via your mobile network even if you are connected to wifi.
Click to expand...
Click to collapse
Yes it is... i am using your V3.5 (also tired v3.0) Now when i used a ROM based on incredible ported to the EVO, it sent fine with your v3 and sent fine with WIFI on.
im almost certain its a framework issue, and the reason the incredible mms is working is that its not calling in the framework that sprint has, its a bandaid so to say, not a resolution. Im assuming if you went through the Mms.apk from incredible and aligned all the framework calls that it may work, with wifi, but that may break the Mms again.
I just havent had the time to do a dif on the sources to compare where there are differences yet. but i think that will provide us some good information as to where the issue is.
Also im hearing reports of the paid Mms.apk not sending some pictures correctly, he can send anything that has been sent to him previously (i.e. resized properly) and also can send pics resized from his pc, so even the paid solution Mms.apk needs work. Hopefully we can nail this down and potentially even get the settings 100% for our carriers so that it will resize anything and work well
Alright, movie time, then bed, then work, then vacation!! Ill check back in a few weeks when im back
token419 said:
im almost certain its a framework issue, and the reason the incredible mms is working is that its not calling in the framework that sprint has, its a bandaid so to say, not a resolution.
Click to expand...
Click to collapse
Then why are the Incredible guys putting the EVO Mms.apk on the incredible and it works fine?
That would tell me that that, both Mms.apk are calling the same thing....
xboxhacker said:
Then why are the Incredible guys putting the EVO Mms.apk on the incredible and it works fine?
That would tell me that that, both Mms.apk are calling the same thing....
Click to expand...
Click to collapse
The Mms.apk is what sets up what com.android.xxx libraries it pulls up. for example if the sprint one pulled up com.android.sprint.mms.settings.blah, and you use the verizon one that points to com.android.verizon.mms.settings.blah, then it isnt calling the broken framework to run the instruction on.
Thats just an example, not based on any findings.
Whats interesting though is that the Cyanogen and AOSP roms are failing, which as far as i know only reuse a few things from a base rom (libs and whatnot), so what im thinking is to find out a vendor tree for cyanogen and see which frameworks/libs etc that they pull from an original rom that don't get built from cyanogen sources, and that will help us narrow down what could be not working correctly.
Just a thought, ill have to experiment when i get back from vacation.
Eager to see if anything arises
Phew, I've finally got a 99% working MMS solution on my EVO on Cricket. I can send and receive everything however you have to jump through a tiny hoop for sending, pretty livable though until a real solution comes out.
I am using the latest APNs posted around the forums for Cricket/Android:
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="2">
<apn name="CDMA-MMS" numeric="46605" mcc="466" mnc="05" apn="mms" user="my#[email protected]" server="NA" password="cricket" proxy="wap.mycricket.com" port="8080" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="http://mms.mycricket.com/mycricket/mms.php" type="mms" />
<apn name="8960-MMS" numeric="46605" mcc="466" mnc="05" apn="mms" user="" server="" password="" proxy="null" port="null" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="http://10.113.63.8:8080/12345=abc" type="mms" />
</apns>
I haven't gone back and tested with previous APN settings, but I know this is working for me for sure.
You still cannot use the MMS.apk from a Sprint or AOSP based rom. You need to have one from a Verizon based rom. I am using the MMS.apk from the Incredible as was posted in another thread I believe. I think this is the one ripped out of AVA Froyo V2RC3.
I did finally get MMS working under V2RC3 one I realized my real problem after the APN settings. The MMS app by default has the MMS size set too high for cricket. It was up over 1mb. Once I dropped the size of MMS down to 500k everything started sending.
I have installed this MMS.apk on to the Fresh 3.2 rom for EVO. As it has was stated earlier in this thread I think it is allowing me to send just fine, however it cannot load a conversation. I can see multiple conversation but if I try to open one up it just goes to "loading".
As a work around I am now using Handcent as my primary messaging app. It will allow me to send/receive all regular texts, receive MMS, and view conversations. It won't send an MMS for some reason, so for that I just go to the picture I want to send, select share, and then use the "stock" MMS app to send the picture, then back to Handcent. Not pretty but highly functional for now and certainly not a major pain in the ass.
The REAL trick which may have allowed MMS to work a while back if I had known was to get that MMS size down to like 500k or something. I bet I could have been sending MMS long ago if I had done that.
As far as getting the Incredible MMS apk to work, it's definitely a missing library/framework problem. I had to open the APK and resign it in order to attempt to install it on the CM6 rom (installed without a hitch on Fresh) and after resigning the next error I get is that there are some missing shared libraries. If someone who knows more about what they're doing can determine what libraries the APK requires maybe those can easily be loaded into whatever ROM someone wishes to use?
I also get no MMS in or out when Wifi is on.
I would just stick on the Ava Froyo V2RC3 rom since MMS works so fantastically on it, but Youtube can't play anything worth a damn over 3G.
Can you explain what apn settings you changed? Im following the guide that's here that works for everyone else except me and I'm willing to try anything right now!
Swyped from an HTC Evo on MetroPCS...
does anyone know how to change the mms LIMIT size on the g2 sense roms?
my default mms limit on my message app is 300k and i wanna change it to 3500k.
ive been looking around and i have not found a solution -___-
appreciate any help.
thank you in advance.
To go up that high you would need to rip apart the Mms.apk, something I've actually been working on for CM/Vanilla since Calkulin over in the EVO 4G section managed to do it. He did it with the Sense mms app so it's a bit different and I'm newish to this whole decompile/recompile business.
Here's a link to his stuff if anybody want's to give it a go (maybe it'll work with our Sense ROMs?).
Handcent would still compress images to a crap 1KB-25KB size when sending since it relied on the Mms.apk to do some of the work, even if you set the limit to 1MB or higher (now you can set it to 5MB, says only for the EVO though). Lately though with CM7 I noticed that it's not an issue anymore. Maybe it's a self reliant app, in which case you may be able to completely remove the Mms.apk. I'll try it later and report back. The stock Mms app still seems to compress though, at least last time I checked it did.
That's all I have for you right now. Hope it helps.
KCRic said:
To go up that high you would need to rip apart the Mms.apk, something I've actually been working on for CM/Vanilla since Calkulin over in the EVO 4G section managed to do it. He did it with the Sense mms app so it's a bit different and I'm newish to this whole decompile/recompile business.
Here's a link to his stuff if anybody want's to give it a go (maybe it'll work with our Sense ROMs?).
Handcent would still compress images to a crap 1KB-25KB size when sending since it relied on the Mms.apk to do some of the work, even if you set the limit to 1MB or higher (now you can set it to 5MB, says only for the EVO though). Lately though with CM7 I noticed that it's not an issue anymore. Maybe it's a self reliant app, in which case you may be able to completely remove the Mms.apk. I'll try it later and report back. The stock Mms app still seems to compress though, at least last time I checked it did.
That's all I have for you right now. Hope it helps.
Click to expand...
Click to collapse
on Virtuous rom i was on 3500k mms. now on SEGA rom the limit is 300k.
Yeah, some devs change these limits. Doesn't really matter much if they don't edit the compression though which *i think* virtuous does.
Anyone? It seems no one will ever comment on the posts I make at their forums? I am testing cyanogen 7.1 out for a bit.
Some background info. Doubled wiped everything except sdcard. downloaded a fresh cyanogen 7.1 and flashed it. I have the GPS fix, and the gapps thing flashed with tiamat 4.0.8
So can someone tell me how to either fix this or why it does this?
This is a huge dealbreaker.. It compresses whatever photo i try to attach and it losses quality of the picture... I like the stock android and having to use handcent to send my mms seems like a *WTF* should i do this moment...
Apps like Handcent and Go SMS are better than the stock messaging app anyway. Why would you be willing to throw away the entire ROM over the messaging app when you can use more powerful messaging apps that don't compress the image AND have more customization options?
I've used stock CM, Handcent and Go SMS. By far my favorite one is Go SMS. Way better than the one that comes with CM.
I have used them both. I dislike them. Its just the feel. And the popups I just dislike the whole thing even after i messed with the settings to get rid of what i dont like. The options arent there and i do dislike them.. Also it wont send multiple split messages it freezes my ability top send messages and i need to reboot my phone....
And the Messaging app isn't the only issue.
Btw not my first or second time using CM either..
cmsjr123 said:
I have used them both. I dislike them. Its just the feel. And the popups I just dislike the whole thing even after i messed with the settings to get rid of what i dont like. The options arent there and i do dislike them..
And the Messaging app isn't the only issue.
Btw not my first or second time using CM either..
Click to expand...
Click to collapse
Huh? I don't get any pop ups whatsoever on mine. Not quite sure what you mean. And what options are you looking for? Out of all the ROMs I've tried CMseems to have the most flexibility and most customization options. What exactly are you looking for in a ROM? Handcent and Go SMS also provide more flexibility and customization options than the stock messaging app. Let me know what you're looking for and maybe I can point you toward a ROM that fits.
Concordium said:
Huh? I don't get any pop ups whatsoever on mine. Not quite sure what you mean. And what options are you looking for? Out of all the ROMs I've tried CMseems to have the most flexibility and most customization options. What exactly are you looking for in a ROM? Handcent and Go SMS also provide more flexibility and customization options than the stock messaging app. Let me know what you're looking for and maybe I can point you toward a ROM that fits.
Click to expand...
Click to collapse
Its not that I'm looking for felxibility i just want to get my mms to stop sending at low resolutions.
It may be the user agent but every one of them makes me receive a pic at 8XX by ^XX resolutions..
I just want the stock one to have correct mms. And preferably a mms with a user agent for my phone or a equivalent phone. I have been searching for days and no one seems to post a fix. All the fixes seem to be for tmo for what i can find :/
Well I understand that you want your stock messaging app to work properly. However, I don't know a means to directly resolve the problem. Test with Handcent/Chomp SMS/Go SMS, reflash your ROM/kernel, update your radio, wimax, nv, etc., and if worse comes to worse....completely unroot your phone back to bone stock. Seems ridiculous that something that drastic is needed to fix your issue. But I did that as a last resort for my phone and it fixed my 2 month long SMS/MMS issue that I had been having.
Here OP try this. Is splits and the limit is big
http://db.tt/eOzGdVB2
Work out for you?
Dont know if this has been discussed alrrady, but I think i found a workaround fix for the blurry mms on 2.3.6. Download handcent and go to Settings> Application Settings> Default Messaging Application and set to MMS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that my mms come in a lot better. This is with leaving it disabled
And this is after i change the Default Messaging Application to MMS
Hope this helps someone
Sent from Flip's SGS2
It worked for me man thanks!!
Sent from Samsung Galaxy S II running Ginger-Snap v1.1
Working for me as well, thank you so much.
Sent from my SGH-T989 using xda premium
Didn't work for me. Just shows Download button and image doesn't download.
Thanks anyway.
razormy said:
Didn't work for me. Just shows Download button and image doesn't download.
Thanks anyway.
Click to expand...
Click to collapse
Try a reboot, mine was doing that also at first l
Sent from Flip's SGS2
elflip88 said:
Dont know if this has been discussed alrrady, but I think i found a workaround fix for the blurry mms on 2.3.6. Download handcent and go to Settings> Application Settings> Default Messaging Application and set to MMS
After that my mms come in a lot better. This is with leaving it disabled
And this is after i change the Default Messaging Application to MMS
Hope this helps someone
Sent from Flip's SGS2
Click to expand...
Click to collapse
wait, so are you saying that since making these changes in handcent's settings, and now you're using the stock messaging app-it's not blurry anymore? or you're talking about using handcent only?
DocMark's MMS Bible
MMakoto said:
wait, so are you saying that since making these changes in handcent's settings, and now you're using the stock messaging app-it's not blurry anymore? or you're talking about using handcent only?
Click to expand...
Click to collapse
Before I go into a long primer below, I still recommend E-Mail for sending a pix. We have smartphones and we have Gmail, so educate others into using this method for the best quality in a picture sending experience. But, for those that insist on MMS.....see below.
As far as I know and have been doing, you just use Handcent period. Handcent does not over compress the pix, so they are larger to begin with and therefore less blurry (or not blurry) to begin with. 99% of the ROMS based on 2.3.6 and using WiFi calling seem to NOT allow sending or receiving with WiFi calling enabled. (TMobile states at least in a tech support ticket to me they know this is an issue, BTW) So...turn off, WiFi calling, use Handcent and it will download/send etc. No reboot required. And you don't need to change anything in that application settings to turn off stock mms. If you go into Handcent send settings and use 1.2Mb mms sizes instead of 1.0Mb, the sizes will be as high as 600-850Kbs on average, depending on what you started with. But larger files take longer to send or receive, obviously. With 1.0 Mb mms settings enabled in Handcent send settings, I typically see 128kbs file sizes which is typically fine for mms messaging. This has always worked for me without doing the CM7 mms.apk shuffle btw also. I hope I covered everything. Oh, obviously if more than one messageing app is in residence, you need to turn off notifications for the ones that you are not using, unless you don't mind redundant notifications
Lastly, it's been hit or miss on whether 2.3.6 based wifi calling Roms will work leaving wifi calling enabled. The Zombie 2.x ROMs had been working for me with WiFi calling enabled, but even on that one, occasionally I get the message that the network is not available blah blah message and it won't send or receive. But turning off wifi calling is always the fix and use Handcent, for pix that are NOT over compressed.
Docmjldds said:
Before I go into a long primer below, I still recommend E-Mail for sending a pix. We have smartphones and we have Gmail, so educate others into using this method for the best quality in a picture sending experience. But, for those that insist on MMS.....see below.
As far as I know and have been doing, you just use Handcent period. Handcent does not over compress the pix, so they are larger to begin with and therefore less blurry (or not blurry) to begin with. 99% of the ROMS based on 2.3.6 and using WiFi calling seem to NOT allow sending or receiving with WiFi calling enabled. (TMobile states at least in a tech support ticket to me they know this is an issue, BTW) So...turn off, WiFi calling, use Handcent and it will download/send etc. No reboot required. And you don't need to change anything in that application settings to turn off stock mms. If you go into Handcent send settings and use 1.2Mb mms sizes instead of 1.0Mb, the sizes will be as high as 600-850Kbs on average, depending on what you started with. But larger files take longer to send or receive, obviously. With 1.0 Mb mms settings enabled in Handcent send settings, I typically see 128kbs file sizes which is typically fine for mms messaging. This has always worked for me without doing the CM7 mms.apk shuffle btw also. I hope I covered everything. Oh, obviously if more than one messageing app is in residence, you need to turn off notifications for the ones that you are not using, unless you don't mind redundant notifications
Lastly, it's been hit or miss on whether 2.3.6 based wifi calling Roms will work leaving wifi calling enabled. The Zombie 2.x ROMs had been working for me with WiFi calling enabled, but even on that one, occasionally I get the message that the network is not available blah blah message and it won't send or receive. But turning off wifi calling is always the fix and use Handcent, for pix that are NOT over compressed.
Click to expand...
Click to collapse
BS. No matter how big I set my mms in hancent they are never over 128kb. And this "fix" doesn't work for me. Mms is still blurry with handcent.
Sent from my SGH-T989 using Tapatalk
Maybe I just don't MMS enough.. but this works fine for me:
http://forum.xda-developers.com/showthread.php?t=1386532
I didn't flash the CWM.. but used Root explorer to replace MMS.apk with it.
For some reason when I flash using CWM it doesn't work. May work for you let me know.
let me know how it fairs for you all.
mikeyinid said:
BS. No matter how big I set my mms in hancent they are never over 128kb. And this "fix" doesn't work for me. Mms is still blurry with handcent.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I have no idea why it doesn't work for you. But to say BS is beneath your normal replies, IMHO. Here is a test shot screenie I'm posting using Handcent. Not sure which ROM. I believe at the time, I actually had to reboot to get my WiFi calling back to work since you can see the icon has that reddish color, meaning it was not working correctly. The few times this has happened to me, a reboot fixed this. I believe I was getting one of those erroneous sim card not correct messages. I do have a prper sim card. On a few slect times, it will get that message for some strange reason. And this has happened with more than one of the proper new sim cards since I already had TMobile replace mine the first time it happened. Again, a reboot fixes. If this is BS, then explain my message size properties? And it was not blurry either.
Docmjldds said:
I have no idea why it doesn't work for you. But to say BS is beneath your normal replies, IMHO. Here is a test shot screenie I'm posting using Handcent. Not sure which ROM. I believe at the time, I actually had to reboot to get my WiFi calling back to work since you can see the icon has that reddish color, meaning it was not working correctly. The few times this has happened to me, a reboot fixed this. I believe I was getting one of those erroneous sim card not correct messages. I do have a prper sim card. On a few slect times, it will get that message for some strange reason. And this has happened with more than one of the proper new sim cards since I already had TMobile replace mine the first time it happened. Again, a reboot fixes. If this is BS, then explain my message size properties? And it was not blurry either.
Click to expand...
Click to collapse
Hmmm. I've tested every possible scenario and I can't get mms to be larger than 128. And no matter what, outside of the cm7 mms.apk its always blurry.
Sent from my SGH-T989 using Tapatalk
mikeyinid said:
Hmmm. I've tested every possible scenario and I can't get mms to be larger than 128. And no matter what, outside of the cm7 mms.apk its always blurry.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I will try to bemore consistent in exact ROM, kernel, MMS apk used if not stock etc etc when posting a test shot etc. I honestly believe we see too many inconsistencies since T-Mobile says it's an issue, so the added variable of a Network issue just adds to the confusion and test results. Just my opinion.
mikeyinid said:
Hmmm. I've tested every possible scenario and I can't get mms to be larger than 128. And no matter what, outside of the cm7 mms.apk its always blurry.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
OK...I did a complete clean install of the Zombie 2.2 ROM since I know this was an original work 2.3.6 based ROM not copied from Juggernaut etc etc. My apologies to anyone that may be offended by this, but I know for a fact that this ROM works for whatever reason with the following parameters.
First, after the complete clean install and ONLY setting up WiFi for WiFi calling as well as my Google account. I only installed Handcent as well as a freebie screen shot program. No Titanium backups or anything to muddle the situation. I left Handcent stock. Did not touch any settings. Using the stock mms file as well as stock kernel. First with regards to blurry mms. I am posting a screen shot of the received mms I sent to me. Using the Tennis racquet here as a decent picture for showing that there is no blurring of the shot. Next is the properties of the file to show compression based on stock Handcent settings which again, I did not alter at all, but I know Handcent does use 1.0Mb mms file sizes.
What is nice with this ROM is that you CAN have WiFi calling enabled which allows an almost instantaneous send/receive of a picture instead of the normal wait time with any significant sized attachment.
I am not showing pix from using the stock messaging app, since it did compress my test shots down to 26kb sizes on average. Viewing was ok, only because there was NO blurring. Bottom line so far..the Zombie 2.2 ROM is the only ROM so far for me that has zero blur, allows WiFi calling to be enabled and working with a third party or stock messaging app, but is the one rom that at least for me along with Handcent, allows for wifi calling to be used with no blurring and really nice minimal file compression.
I know the following has been mentioned by others besides me. It just seems that the Juggernaut ROM was probably the first on the scene here that used 2.3.6 and all the others that followed, UP to the Zombie ROM, seem to have the same issues. I'm not a developer so I can't comment on the source material being used for the ROMs here. But the OP for Zombie has basically stated his work is all original and since his works with Wifi calling and the third party Handcent app, some conclusions have to be drawn from why is his ROM working and all the others seem to have the problem. Lastly, just for fun, I did install an new just posted Skyrocket ROM from the ATT thread just for the heck of it. SKYICECREAM RC6.zip. The stock mms app I thought would actually work, since it didn't seem to compress much at all. But after receiving the files I tested, it did end up compressing as well as providing extremely blurry file results.
Sorry for the long post, but this backs up basically a few other posts on other threads I have made in the past week or so as well as another user that came to the same conclusion as me WRT the Zombie ROM. Will provide the OP name after I post this
EDIT: jlaigo2 is the Zombie developer. BTW I was NOT wearing my glasses when I took the pix of my racquet. The original pix was not super sharp, so my applogies for using a slightly off focus test shot. But this is not a blur as we have seen with the MMS issues here.
Docmjldds said:
OK...I did a complete clean install of the Zombie 2.2 ROM since I know this was an original work 2.3.6 based ROM not copied from Juggernaut etc etc. My apologies to anyone that may be offended by this, but I know for a fact that this ROM works for whatever reason with the following parameters.
First, after the complete clean install and ONLY setting up WiFi for WiFi calling as well as my Google account. I only installed Handcent as well as a freebie screen shot program. No Titanium backups or anything to muddle the situation. I left Handcent stock. Did not touch any settings. Using the stock mms file as well as stock kernel. First with regards to blurry mms. I am posting a screen shot of the received mms I sent to me. Using the Tennis racquet here as a decent picture for showing that there is no blurring of the shot. Next is the properties of the file to show compression based on stock Handcent settings which again, I did not alter at all, but I know Handcent does use 1.0Mb mms file sizes.
What is nice with this ROM is that you CAN have WiFi calling enabled which allows an almost instantaneous send/receive of a picture instead of the normal wait time with any significant sized attachment.
I am not showing pix from using the stock messaging app, since it did compress my test shots down to 26kb sizes on average. Viewing was ok, only because there was NO blurring. Bottom line so far..the Zombie 2.2 ROM is the only ROM so far for me that has zero blur, allows WiFi calling to be enabled and working with a third party or stock messaging app, but is the one rom that at least for me along with Handcent, allows for wifi calling to be used with no blurring and really nice minimal file compression.
I know the following has been mentioned by others besides me. It just seems that the Juggernaut ROM was probably the first on the scene here that used 2.3.6 and all the others that followed, UP to the Zombie ROM, seem to have the same issues. I'm not a developer so I can't comment on the source material being used for the ROMs here. But the OP for Zombie has basically stated his work is all original and since his works with Wifi calling and the third party Handcent app, some conclusions have to be drawn from why is his ROM working and all the others seem to have the problem. Lastly, just for fun, I did install an new just posted Skyrocket ROM from the ATT thread just for the heck of it. SKYICECREAM RC6.zip. The stock mms app I thought would actually work, since it didn't seem to compress much at all. But after receiving the files I tested, it did end up compressing as well as providing extremely blurry file results.
Sorry for the long post, but this backs up basically a few other posts on other threads I have made in the past week or so as well as another user that came to the same conclusion as me WRT the Zombie ROM. Will provide the OP name after I post this
EDIT: jlaigo2 is the Zombie developer. BTW I was NOT wearing my glasses when I took the pix of my racquet. The original pix was not super sharp, so my applogies for using a slightly off focus test shot. But this is not a blur as we have seen with the MMS issues here.
Click to expand...
Click to collapse
It is definitely clear. But when I send myself pics they are always clear. Soon as someone else sends me a pic it's blurry. Ill flash the stock rom I posted and do some research. Its the absolute closest to stock as it hasn't been doedexed or anything.
Edit: still blurry. Handcent or not. I really don't understand. people have reported in my thread that mms is clear on this rom but it never has been for me. Idk
Sent from my SGH-T989 using Tapatalk
mikeyinid said:
It is definitely clear. But when I send myself pics they are always clear. Soon as someone else sends me a pic it's blurry. Ill flash the stock rom I posted and do some research. Its the absolute closest to stock as it hasn't been doedexed or anything.
Edit: still blurry. Handcent or not. I really don't understand. people have reported in my thread that mms is clear on this rom but it never has been for me. Idk
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
My only comment back would be my tests of clean installing that Skyrocket ROM and the jpgs I sent to myself were extremely blurry, which is at least for my own testing doesn't follow that sending to myself is always clear, as is for your own testing. IDK either....Confusing at best, but at least for me, I consistently have the same results wrt the Zombie ROM vs any other 2.3.6 based ROM.
I think I may have found the issue. I changed the max size and user agent on the mms_config.xml.
I'll post the apks I tweaked myself for Jugs4.1 and the ICS themed Mms.apk for Jugs4.1 from the ICS Complete package theme.
I confirmed they worked on my phone by sending myself MMS's from other phones. Hope this works for you.
make backup of your current Mms.apk just in case you have issues you can revert
adb push into /system/app/Mms.apk (basically replace your Mms.apk with one of the ones attached)
reboot if necessary
I haven't tested with any other ROMs besides Jugs4.1 so I can only say it's working for Jugs4.1
Also, sending yourself a large MMS may still cause the compression, but at least now you should be able to receive MMS from other phones without them being compressed to ~19K.
mastajest said:
I think I may have found the issue. I changed the max size and user agent on the mms_config.xml.
I'll post the apks I tweaked myself for Jugs4.1 and the ICS themed Mms.apk for Jugs4.1 from the ICS Complete package theme.
I confirmed they worked on my phone by sending myself MMS's from other phones. Hope this works for you.
make backup of your current Mms.apk just in case you have issues you can revert
adb push into /system/app/Mms.apk (basically replace your Mms.apk with one of the ones attached)
reboot if necessary
I haven't tested with any other ROMs besides Jugs4.1 so I can only say it's working for Jugs4.1
Also, sending yourself a large MMS may still cause the compression, but at least now you should be able to receive MMS from other phones without them being compressed to ~19K.
Click to expand...
Click to collapse
Will try and report back. Thanks a lot
mastajest said:
I think I may have found the issue. I changed the max size and user agent on the mms_config.xml.
I'll post the apks I tweaked myself for Jugs4.1 and the ICS themed Mms.apk for Jugs4.1 from the ICS Complete package theme.
I confirmed they worked on my phone by sending myself MMS's from other phones. Hope this works for you.
make backup of your current Mms.apk just in case you have issues you can revert
adb push into /system/app/Mms.apk (basically replace your Mms.apk with one of the ones attached)
reboot if necessary
I haven't tested with any other ROMs besides Jugs4.1 so I can only say it's working for Jugs4.1
Also, sending yourself a large MMS may still cause the compression, but at least now you should be able to receive MMS from other phones without them being compressed to ~19K.
Click to expand...
Click to collapse
Nice. I'm using the Zombie 2.2 ROM. I also test just now using the ICS mms file you posted. I installed it using root explorer copying to system/app. Fixed permissions and renamed it Mms.apk just in case it needed to run with out changing the name. Rebooted. At first it looked like it was going to compress a pix down to 26kb when using the stock messaging app, so I first used Handcent, with wifi calling enabled and 1.0Mb mms settings. That worked fine. I then went and opened up the stock messaging app. Sent the same file to myself using the stock message app. Attached shows no blur as well as 591kb sized pix. And it was almost instantaneous with wifi calling enabled and the Zombie Rom.
EDIT: At least wrt sending to myself from my phone, Handcent still is the only app for me that leaves compression to a min. If I send a new pix using stock app, it still seems to compress down to 25kb approx. Guess I need to test with another phone sending to me to know for sure
Docmjldds said:
Nice. I'm using the Zombie 2.2 ROM. I also test just now using the ICS mms file you posted. I installed it using root explorer copying to system/app. Fixed permissions and renamed it Mms.apk just in case it needed to run with out changing the name. Rebooted. At first it looked like it was going to compress a pix down to 26kb when using the stock messaging app, so I first used Handcent, with wifi calling enabled and 1.0Mb mms settings. That worked fine. I then went and opened up the stock messaging app. Sent the same file to myself using the stock message app. Attached shows no blur as well as 605kb sized pix. And it was almost instantaneous with wifi calling enabled and the Zombie Rom.
Click to expand...
Click to collapse
Glad it worked!
I may have named the files incorrectly since you tried the ICS one and it's not themed. Woops
mastajest said:
Glad it worked!
I may have named the files incorrectly since you tried the ICS one and it's not themed. Woops
Click to expand...
Click to collapse
No problem. BTW didn't want to confuse 591 vs 605Kb. Different test with pix changed to slightly different compression, for whatever reason. So disregard the exact numbers. Will borrow one of my family members phones when I can to test this out from another account to me. Haven't used Juggs ROM in a while. Assuming it's 2.3.6 based and wifi calling, does having wifi calling enabled work for you when sending or receiving mms. For me, ONLY the Zombie ROM can work with WiFi calling enabled.
Disclaimer--- this is simply a thread to discuss and rant about issues with wifi calling related to MMS sending and retrieval as well as blurry mms. This is also to keep it in one place rather than on other posts where it becomes unrelated to the original topic. I have tested sending MMS through stock, hand cent, and go SMS and am unable to send pictures. This said I am using kl1 deodexed rom by whitehawx. This is just the beginning of my research and observation. Another user (docmjldds) mentioned that it was working on zombie rom but only using hand cent. Please post what roms you have tested and whether or not sending over wifi calling works for you. Also post what SMS app you are using and what file size it was also. Screenshots help but keep them G rated. Also post whether the pics where blurry. If it helps post what types of mms mods you have flashed. I will clean this up more when I get to a computer and update the list... please feel free to rant and rave. Just don't take it personal.
You can help research by posting the following:
1.) Rom you are using and version
2.) Kernel you are using
3.) Any mods, scripts, etc.
4.) Using wificalling only, NOT 4g, attempt to send MMS to yourself or other person using either
1.) Stock Rom
2.) Other sms app (please state which one works)
3.) State whether or not it DID or DID NOT compress the image when sending and if it failed, or when receiving if it ends up blurry.
My rom:
Deodexed KL1 by Whitehawx. Using Fauxkernel 07b5 default with no scripts or mods added.
[stock mms app] = unable to send large pictures but can send decent size. Takes more than 10 minutes for me to send. Compresses the images right away.
[Go Sms and Handcent] able to send regular sized pictures but not large ones >1mb. Still took 10 minutes to send. Compression occurred.
Did not notice any blurriness from the pictures that I did receive.
Updated List for ROMS able to send MMS/Large sized MMS, etc
--ZombieRom 3.0 Thank you Docmjldds for the heads up on this info.
Updated List for tweaks, mods, tricks to get MMS to send.
--Will update as people post.
Thanks for your contribution. I will post better screenshots of pictures sent and received.
I can send through Go SMS ...
I am running a mishmash of ROM's I threw together myself, I know not much help
It is 2.3.6 with KL1 ...
Using the alternate APN but transferred all the MMS settings to the new APN ...
I can send while on Wi-Fi with wifi calling enabled, BUT, it does seem to take a very long time ...
yes it helps. I noticed I sent one large pic about 200 KB and the other was less. After ten mins I got a link to download the smaller of the two. The bigger failed. No blurriness though. I got notifications from all the SMS apps with the smaller pic.
tcboo said:
I can send through Go SMS ...
I am running a mishmash of ROM's I threw together myself, I know not much help
It is 2.3.6 with KL1 ...
Using the alternate APN but transferred all the MMS settings to the new APN ...
I can send while on Wi-Fi with wifi calling enabled, BUT, it does seem to take a very long time ...
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
chib1panda said:
yes it helps. I noticed I sent one large pic about 200 KB and the other was less. After ten mins I got a link to download the smaller of the two. The bigger failed. No blurriness though. I got notifications from all the SMS apps with the smaller pic.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Not going to repeat the same old same old. I will simply watch and learn what others state. Until I see otherwise, I only ask users to try every ROM 2.3.6 based and tell me if they can specifically send and receive with the following parameters
1. Use WiFi calling enabled. I am NOT interested in 4G. That's NOT the issue here.
2. Be able to enable 1.0Mb file sizes to send with MMS and NOT have files shrink to 16-26Kb file sizes.
3. Not have to R+R any mms.apk files from one source to get around blurry mms issues.
Now, based on these parameters, I am simply going to make the following statement regarding what works for me and specifics. For those that have already heard me say this, hold your ears please since many users here may not have had the misery of reading my prior posts.
I have found that consistently only one ROM here for our model works. I have no idea on why. I am only stating to try the following.
The Zombie based ROM, currently 3.0 version here. Install per OP directions. Then install Handcent SMS third party app. It's the only app that works consistently for me where I can send large sized MMS files (350-950Kb sized) using WiFi calling enabled. It should only take a few seconds to send. And yes, these are the sizes received. I am using 2-3Mb pictures I take with our phone, using the 1.0Mb MMS settings for sending in the Handcent preference setup for MMS. You can use the stock message app to read the same file, AFTER it is first received with Handcent, BTW. Oh, like GoSMS Pro, you don't have that arrow showing in the mms file as if it's a video file you are seeing, BTW. I have seen this asked by others. But Handcent does not give that message "Unable to send. Wait till Network is available message". GoSMS Pro does give that message for me.
I have posted enough screen shots on various development threads so I won't clutter up the post here. If users ask, I will post to prove that with the ROM mentioned and Handcent, it works, but I cannot get this to work with any other ROM. Again, NOT 4G and not 16-26KB file sizes that I am interested specifically in.
1) didn't use 4g
2.) File over 1mb did not com press with hand cent nor go SMS but did with stock. I couldn't test what file size it was received as because large file never was sent.
3.) Did zombierom dev state what specific tweaks mods or scripts he used that other 2.3.6 roms. Don't have in them?
4.) I will have more time tomorrow so I can flash zombie and see if I can duplicate the same as you.
Thanks
chib1panda said:
1) didn't use 4g
2.) File over 1mb did not com press with hand cent nor go SMS but did with stock. I couldn't test what file size it was received as because large file never was sent.
3.) Did zombierom dev state what specific tweaks mods or scripts he used that other 2.3.6 roms. Don't have in them?
4.) I will have more time tomorrow so I can flash zombie and see if I can duplicate the same as you.
Thanks
Click to expand...
Click to collapse
Before 3.0 just posted it basically has been a plain Jane ROM much the same as the Original MrX first 2.3.6 or Whitehawk 2.3.6 ROM. No themeing to speak of. In fact, it doesn't even have the 13-14 toggle above the notification area. I would have to look at the original change-logs to see specifically what exact tweaks etc may have been incorporated. AFAIK, nothing at all different from the others. I can only add that I routinely change to the Faux kernels since I want BLN support, and the kernel he uses for stock doesn't offer it. But Kernels never played any role in what made this work or not work. Just an fyi.
Do you think kernel has anything to do with it? I would be very surprised to find out. Plus, I want to know why my wife's Mytouch 4g is able to send any type of picture, text quickly with good results?? whats different about HTC's wifi calling than ours? I know hers is activated by an actual app like other legacy wifi calling phones still do. I wonder if the way it is now implemented messes with sending MMS.
Docmjldds said:
Before 3.0 just posted it basically has been a plain Jane ROM much the same as the Original MrX first 2.3.6 or Whitehawk 2.3.6 ROM. No themeing to speak of. In fact, it doesn't even have the 13-14 toggle above the notification area. I would have to look at the original change-logs to see specifically what exact tweaks etc may have been incorporated. AFAIK, nothing at all different from the others. I can only add that I routinely change to the Faux kernels since I want BLN support, and the kernel he uses for stock doesn't offer it. But Kernels never played any role in what made this work or not work. Just an fyi.
Click to expand...
Click to collapse
chib1panda said:
Do you think kernel has anything to do with it? I would be very surprised to find out. Plus, I want to know why my wife's Mytouch 4g is able to send any type of picture, text quickly with good results?? whats different about HTC's wifi calling than ours? I know hers is activated by an actual app like other legacy wifi calling phones still do. I wonder if the way it is now implemented messes with sending MMS.
Click to expand...
Click to collapse
My wife also has a MyTouch4G and I believe it really has something to do with the newer implementation used by our style WiFi calling. I know that TMobile has already acknowledged to me it's an issue they are looking at. I really have a feeling they know they are intentionally overcompressing on the newer models like our SGS2. The Sensation I used to use also was on the older standard and worked just fine, as long as the model and brand name was correct in the build.prop files. Kernel is NOT an issue. I have basically tested every Kernel there is with all the ROMs. Zombie consistently works with any of them. Anecdotal here, the Revolution ROM that I believe is retired because of some XDA issues with the Developer, also did work, like the Zombie ROM too, but I am going on another close friend here that remembers it worked for him.
When I get the time, I have several programs that can do a file by file comparison. Takes a lot of time, but that's the only way I know of to see what is different from the base that Zombie is using vs the others. My feeling is it's a source files used issue. Just a guess.
EDIT:
PS... I have all the older files for the legacy method here along with the necessary build.prop edits that are required to make that older HTC method work. Not sure it will even be worth it, but I am going to try adding that stuff, lib files and APK and edits to see if it's even possible to use the older wifi calling.
It may also mean also going back to Android 2.3.5 base. I'm pretty ADD about this subject. I just need to find the time
Sounds like that too. I hope they fix it. It looks like you have more time than I do for testing. Ill be getting my new white one tomorrow so that means rerooting and installing everything again.
Edit-.saw your edit. That would be great if you could get that working.
Docmjldds said:
My wife also has a MyTouch4G and I believe it really has something to do with the newer implementation used by our style WiFi calling. I know that TMobile has already acknowledged to me it's an issue they are looking at. I really have a feeling they know they are intentionally overcompressing on the newer models like our SGS2. The Sensation I used to use also was on the older standard and worked just fine, as long as the model and brand name was correct in the build.prop files. Kernel is NOT an issue. I have basically tested every Kernel there is with all the ROMs. Zombie consistently works with any of them. Anecdotal here, the Revolution ROM that I believe is retired because of some XDA issues with the Developer, also did work, like the Zombie ROM too, but I am going on another close friend here that remembers it worked for him.
When I get the time, I have several programs that can do a file by file comparison. Takes a lot of time, but that's the only way I know of to see what is different from the base that Zombie is using vs the others. My feeling is it's a source files used issue. Just a guess.
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
chib1panda said:
Sounds like that too. I hope they fix it. It looks like you have more time than I do for testing. Ill be getting my new white one tomorrow so that means rerooting and installing everything again.
Edit-.saw your edit. That would be great if you could get that working.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Just to show how lame TMobile support is, out on their tech Forums they are basically telling users NOT to even have wifi calling enabled. Below is a stock answer I see this mod. posting to everyone with issues complaining about this subject.
Being a retired bum, I do have some time on my hands. I can think of better ways to spend it, but this is one nut I really would like to crack. But at least there's a method on a particular ROM that does work. So deoending on importance of this feature will dictate what any user wants in a given ROM. BTW, don't know why the Zombie developer is placing his beta stuff outside of XDA, but there are references to links. Latest 3.1.1 includes update for the multiple toggles above notification area. Just an FYI...NOT...again NOT trying to be a Troll, but I can see how I can be accused, by now
IF...other ROMs would work, I would have no reason to state what to use...really...
http://www.androidzombie.com/az/Andr...x0.9KERNv2.zip
***********************************************************************************
TMobile Reply
8. Jan 11, 2012 8:42 AM (in response to sjmrshll)
Correct AnswerRe: MMS will not download while WiFi is enabled...
Hi!
Let me first thank you for being part of our community! We are happy to have you here and love to see you as an active participant. Unfortunately we cannot guarantee any of your services will work over the wi-fi network. Not being able to both send and receive MMS over wi-fi is an issue that can be slightly common.
If you have any further questions, please feel free to reply to this message or contact any member of the staff. Thank you and have a great day!
- Alicia B.
Community Moderator
1.) Juggernaut 4.1
2.) Faux .007
3.) ICS Mod
4.) No matter what the file size no MMS will come through while I am connnected to wifi calling. If I disconnect and switch to 4G it will go through provided it has synced with Google.
1.) Stock SMS App doesn't work. Neither does GOSMS which is my go to texting app.
2.) See above.
3.) Fails completetly on download or upload.
Hope this helps!
Haven't tried zombie but the only rom I have tried that lets me send and receive mms while using wifi is when I'm on complete stock with root of course but its not really too much of a hassle to just switch wifi off if needed while using jugs 4.1 if it ever does get too annoying I always keep a backup of my stock just in case... So I know it has to be something that's been removed from the custom roms that keeps the phone from auto switching to data from wifi when using mms
Sent from my SGH-T989 using Tapatalk
rickm8384 said:
1.) Juggernaut 4.1
2.) Faux .007
3.) ICS Mod
4.) No matter what the file size no MMS will come through while I am connnected to wifi calling. If I disconnect and switch to 4G it will go through provided it has synced with Google.
1.) Stock SMS App doesn't work. Neither does GOSMS which is my go to texting app.
2.) See above.
3.) Fails completetly on download or upload.
Hope this helps!
Click to expand...
Click to collapse
IT basically verifies what my claims have been. Something about the Zombie Rom is different to allow MMS to work correctly as long as Handcent is being used. I used Tmoble_SGH-T989UVKL1_Stock_Rooted.zip as a base 2.3.6 to compare with the latest Zombie ROM although versions of this ROM have always worked. Using a program that actually does a great job of side by side taking files withing a given folder to compare with another source of given files. All of the folders basically used the same exact files. The few times lets say that one ROM used a slightly different version lets say of wificalling.apk as an example could not break either the working Zombie functionality, nor could using the Zombie based file in the stock ROM would NOT make that ROM work either. IOW I tried to switch files between these two ROMs, to either create a working stock ROM, or break the function of the ZOMBIE Rom. Could not succeed in making or breaking opposing ROMs.
If it as you say it's probably the system framework differs somewhere. Causing mms not to send.
Sent from my SGH-T989 using xda premium
Coming from my nexus one, we needed specidifc kernels built to support wifi calling. Maybe this new wifi calling is implemented different
Sent from my SGH-T989 using Tapatalk
Killbynature said:
If it as you say it's probably the system framework differs somewhere. Causing mms not to send.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I am pretty much confident that you are correct it's a framework issue. I have used file comparison programs and rulled out every other source file, such as all of the lib files etc. And it has nothing to do with kernels. I have tested every kernel on all these ROMs and the same results occur, irregardless of kernel.
---------- Post added at 06:04 AM ---------- Previous post was at 05:58 AM ----------
drzplaya1121 said:
Coming from my nexus one, we needed specidifc kernels built to support wifi calling. Maybe this new wifi calling is implemented different
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Nexus one was my first Android too. Bought it the first day of availability to the public, direct from Google back in Jan. 2010. The current Wifi calling is totally a different animal WRT our SGS2 phones. It's more or less based on the Network, itself, the proper Sim Card etc. Unlike the older WiFi calling that uses the Gans lib files and Build.prop edits, this doesn't rely on any of that stuff. And it's also a required Android 2.3.6 min. source. So yes...a totally different implementation.
I know this is an 'older' post but it helped me so here you go:
BeastMOD 5.0 (build Test13)
Sinergy kernel
no mods
The only way I can send mms over wifi is running Handcent. GO and stock wouldn't work. What ever zombie was doing made it's way into Melvins Rom
This issue is fixed in the ics leaks. Rom reconnects.to 4g momentarily to send or receive mms
Sent from my SGH-T989 using XDA
xUnreachablex said:
I know this is an 'older' post but it helped me so here you go:
BeastMOD 5.0 (build Test13)
Sinergy kernel
no mods
The only way I can send mms over wifi is running Handcent. GO and stock wouldn't work. What ever zombie was doing made it's way into Melvins Rom
Click to expand...
Click to collapse
I have the beastMOD 5.1 testbuild13 ROM also, but i could receive MMS and send MMS thru wifi in stock sms app. The only difference is that i have the darkside kernel.
Sent from my SGH-T989 using XDA
I'm using darkside rom with the included kernel, no mods or tweaks. WIFI calling and mms works fine, never experienced blurry mms.
Sent from my SGH-T989 using XDA