Related
Ok, this is going to sound like a crazy request....but..
I have a HTC EVO, and i used a ROM from AvalancheMod. It was a Froyo port from the HTC incredible. It had a, what i think, was a better messaging app then the EVO has on the official froyo release. So i want to know how i can port the Verizon Incredible MMS.apk to my EVO.
I downloaded a zip from adrynalyne @ androidforums. It has the MMS.apk in it and i flashed it to my EVO while running 2.2. The app does not work... its not in the app drawer or in the home screen. If i make a anycut short cut to a direct message, it says the app is not longer installed. If i use root explorer and try to install the MMS.apk it says it can not be installed.
How can i modify the MMS.apk to be used on the EVO??
THANX!!
I highly doubt this is possible due to the device-specific nature of that APK. Not only is it device-specific, but it is also carrier specific (probably including Verizon MMS settings and such)
Unfortunately I don't think this is going to ever happen but you'd be better off trying a 3rd party application for SMS/MMS like Handcent SMS or Chomp in the Android Marketplace.
trobb09 said:
I highly doubt this is possible due to the device-specific nature of that APK. Not only is it device-specific, but it is also carrier specific (probably including Verizon MMS settings and such)
Unfortunately I don't think this is going to ever happen but you'd be better off trying a 3rd party application for SMS/MMS like Handcent SMS or Chomp in the Android Marketplace.
Click to expand...
Click to collapse
But it was working on my EVO 100% in Ava's Froyo V2RC3 ROM... his rom was a port from the HTC Incredible to the EVO...it even had VZN apps...
xboxhacker said:
But it was working on my EVO 100% in Ava's Froyo V2RC3 ROM... his rom was a port from the HTC Incredible to the EVO...it even had VZN apps...
Click to expand...
Click to collapse
just extract it from that rom and push it to your current phone
The app does not work... its not in the app drawer or in the home screen. If i make a anycut short cut to a direct message, it says the app is not longer installed. If i use root explorer and try to install the MMS.apk it says it can not be installed.
Click to expand...
Click to collapse
This is what happens when i push it to the phone....
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...
Just wondering what interesting, useful and cool tweaks you guys have been able to make in the MIUI Rom. Im not talking about adding anything complicated. If it can't be done by installing a Zip from SD or an APK then I am most likely not willing to try it since I am such a noob at all this.
I am currently have a couple of issues.
1. I can't dial *228 to activate my phone on my carrier (not even sure that it matters since the phone is working) without the phone FCing.
2. Still can't send a sms over 160. My guess is that the MIUI has the same issues as Cyanogen since it won't work in that rom either.
3. Beautiful Widgets weather wont geolocate.
I love the Rom. It has a great quadrant score! Just wondering if y'all could share your tweaks and such.
eric_bean said:
Just wondering what interesting, useful and cool tweaks you guys have been able to make in the MIUI Rom. Im not talking about adding anything complicated. If it can't be done by installing a Zip from SD or an APK then I am most likely not willing to try it since I am such a noob at all this.
I am currently have a couple of issues.
1. I can't dial *228 to activate my phone on my carrier (not even sure that it matters since the phone is working) without the phone FCing.
2. Still can't send a sms over 160. My guess is that the MIUI has the same issues as Cyanogen since it won't work in that rom either.
3. Beautiful Widgets weather wont geolocate.
I love the Rom. It has a great quadrant score! Just wondering if y'all could share your tweaks and such.
Click to expand...
Click to collapse
I wonder who you are.. haha.
1 and 3 are known, well, spoken of problems. Hopefully they'll tweak it. The second can be fixed by going into handcent/sms app and selecting split messages. Splitting them will still send all of the message itself, but it just splits the characters by 160 for each message.. not really sure what the deal was there, but it works.
RE: MIUI ROM Tips
As far as OTA updates go, try dialing *228+. It does the same thing. (Found this tip on www .droidforums.com).
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
Is there an online version of the kitchen? I ask because it is the last resort to get a fully functional Rom on my evo before I allow my daughter to have it other than using my nandroid of my original and unrooting.
I use a 64-bit system Windows 7. Done research and it says a 32-bit Java will work but that is false. I have spent from 9am until an hour ago (3:30pm here now) formating my hard-drive and reinstalled my OS because it didn't work. Still the kitchen doesn't find Java although I tried to instal a 32-bit version. Online is the only way I can do anything or I need a step-by-step on what I need to do to an apk where I can do it on my phone or I am in need of someone building a Rom. So.....is there one online?
What are you doing? Making a fully functional ROM? Why not take a stock rooted or a working GB ROM like reloaded?
Yea just get a stock 5.07 rooted rom. Not really sure what you're trying to do
Sent from my PC36100 using xda app-developers app
I am letting my daughter have my Evo. She has been hardcore blackBerry but given their status she is wanting to try Android. I have flashed every Rom on the first 10 pages of Development and what she has settled on as far as wanting most is Energy Rom. There are 3 problems stopping her from being totally happy with it. First is the 9016. After a lot of searching all I can find is it is tied to the Phone.apk. I have been unsuccessful at changing it out. The carousel shows only a grey screen when looking in Personalize but have been unsuccessful at getting the one from Mik3D installed and working since I know the one from that Rom works. The browser not going to mobile view and being to wide unless in landscape has been the only thing I have fixed. i used Root Explorer and deleted it and moved a basic stock in. Somehow it worked although the other things haven't. I had decided to try my hand at the kitchen to see if I could make the changes that way but it doesn't work on my PC regardless of what i try and believe me when I say I have taken extreme measures to make it work. So my hopes are that either someone can point me in the right direction on how to exchange an apk using only what tools I can find for my phone or in the direction of a kitchen online. For my phone I have installed: Root Explorer,File Manager and ZipSign2.
Fangstien said:
I am letting my daughter have my Evo. She has been hardcore blackBerry but given their status she is wanting to try Android. I have flashed every Rom on the first 10 pages of Development and what she has settled on as far as wanting most is Energy Rom. There are 3 problems stopping her from being totally happy with it. First is the 9016. After a lot of searching all I can find is it is tied to the Phone.apk. I have been unsuccessful at changing it out. The carousel shows only a grey screen when looking in Personalize but have been unsuccessful at getting the one from Mik3D installed and working since I know the one from that Rom works. The browser not going to mobile view and being to wide unless in landscape has been the only thing I have fixed. i used Root Explorer and deleted it and moved a basic stock in. Somehow it worked although the other things haven't. I had decided to try my hand at the kitchen to see if I could make the changes that way but it doesn't work on my PC regardless of what i try and believe me when I say I have taken extreme measures to make it work. So my hopes are that either someone can point me in the right direction on how to exchange an apk using only what tools I can find for my phone or in the direction of a kitchen online. For my phone I have installed: Root Explorer,File Manager and ZipSign2.
Click to expand...
Click to collapse
She's that picky? Tell her to get an iPhone. LOL
Even she is smart enough to know the first flip phone I ever purchased from Sprint way back when they finally got small enough to fit in your pocket is still better than the best Apple ever released.
However,with a little help I think I can make my life easier. I flashed Derp3D again and only 2 small things needed. First is the keyboard. How do I get the HTC back on and with dictionary? Last is how do I get the weather widget with sound? Those are the only things needed. Themes will be easy enough to handle.
Have you tried MikG v3.11 ? Uber Stable. Has a lot of Themes, and Mods available.
prboy1969 said:
Have you tried MikG v3.11 ? Uber Stable. Has a lot of Themes, and Mods available.
Click to expand...
Click to collapse
The newest Jellybread has the 9016 number blocked, or you can use Go SMS and blacklist it, plus everything else you mentioned works
HipKat said:
The newest Jellybread has the 9016 number blocked, or you can use Go SMS and blacklist it, plus everything else you mentioned works
Click to expand...
Click to collapse
+1 on jellybread..its worth a flash..
Fangstien said:
I am letting my daughter have my Evo. She has been hardcore blackBerry but given their status she is wanting to try Android. I have flashed every Rom on the first 10 pages of Development and what she has settled on as far as wanting most is Energy Rom. There are 3 problems stopping her from being totally happy with it. First is the 9016. After a lot of searching all I can find is it is tied to the Phone.apk. I have been unsuccessful at changing it out. The carousel shows only a grey screen when looking in Personalize but have been unsuccessful at getting the one from Mik3D installed and working since I know the one from that Rom works. The browser not going to mobile view and being to wide unless in landscape has been the only thing I have fixed. i used Root Explorer and deleted it and moved a basic stock in. Somehow it worked although the other things haven't. I had decided to try my hand at the kitchen to see if I could make the changes that way but it doesn't work on my PC regardless of what i try and believe me when I say I have taken extreme measures to make it work. So my hopes are that either someone can point me in the right direction on how to exchange an apk using only what tools I can find for my phone or in the direction of a kitchen online. For my phone I have installed: Root Explorer,File Manager and ZipSign2.
Click to expand...
Click to collapse
The kitchen won't help you for fixing the things you want to fix )besides the fact that there isn't an online version). The kitchen just essentially makes it easier to do the things you're already doing. But EnergyROm is a Sense 3.5 ROM, which is not what the EVO natively comes with. So, there will ALWAYS be issues with it, like the VVM 9016 texts, no 4G, etc. And trying to swap things in from a Sense 3.0 ROM (Mik3D) will only cause more issues. I think you're going to have to "put your foot down" and let your daughter know she can either have a fully functional ROM that doesn't look exactly as she wants, or she can have the eye candy she wants without full functionality.
There are plenty of fully functional ROMs out there with a Sprint base that don't have the 9016 issue. Honestly, those all seem to be extremely minor issues to me. Sounds like you should just bite the bullet and get her an EVO LTE, lol.
I have seen a lot of good reviews of Kendall's ROM, though. But I'm going to assume that's not what your daughter is looking for. Sounds like she likes the look/widgets of Sense.
I remember back in the day I tried a sense 3.0 rom that didn't do the 9016 or whatever, but I don't see how that bugs her. Its just a text message that would only take 2 seconds to delete. When I ran those roms, it wasn't a big deal to me.
With the sense weather part, still didn't have a problem with that either. Just had to turn sound up.
--------------------------------------------------------
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.