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...
Can anybody remove the HTC framework check from the version of Teeter included with the stock Froyo Desire ROM please?
I'm running CyanogenMod nightlies, but wanted to put Teeter on...
I've searched and found an older version from Android 2.1. But after installing, the graphics are offset and the ball doesn't line up with the walls and the holes properly.
I also found another version for non-htc roms, but that turned out to be for hvga phones and there is a large gap along one side of the screen because the images don't fit.
I've pulled the apk from a deodexed 2.2 Desire rom, but after resigning it to get it to install, it still checks for the HTC framework at startup and exits saying it's only for HTC phones.
I've also decompiled the apk, but have no idea what i'm looking at when reading the code, lol (i'm guessing it's something in the smali files under /htc/protection/api/ ?)
I've attached the froyo version of teeter to this post.
If someone could remove the check, I would be most grateful.
wow, you are the only one that find this game fun.
this is usually the first one to go on my roms.
Hey I like it too! I'd love to see this
Nobody?
I thought someone would be able to remove the check?
According to other posts and previous releases, it doesn't rely on the HTC framework, but just checks for it at startup
Tawm said:
Hey I like it too! I'd love to see this
Click to expand...
Click to collapse
hehe, yeah I like to have a quick game every now and then, but my lil nephew loves it and wants to play every time I see him.
sorry for the double post, but just wanted to say i found a copy of teeter as a flashable zip file here:
http://android.modaco.com/content/g...e-now-availabe-for-the-mcr-and-cyanogen-roms/
I have been running Uncommon Sense 1.1 for quite a while on my Incredible, and my absolute favorite aspect is the center Rose button being linked to a modified version of App Folders instead of the normal app drawer. Folder organization is pretty important for me due to a large quantity of apps.
Anyhow, I am now finding myself interested in changing ROMs (I used to test drive multiple ROMs a week, it's weird staying tied down). The problem is, I want the folder organization I've gotten used to mapped to Rosie.
The question is, how can I modify a ROM to achieve this? I have never modified a ROM before, and this sounds like a tough one to start with. My first inclination is to simply take the Rosie.apk from Uncommon Sense and plop it into a different ROM. But given than App Folders was modified in Uncommon Sense, would this work? And how would I do it? Or would I have better luck remapping Rosie to add the unmodified App Folders?
Sent from my ADR6300 using XDA App
This question belongs in Q&A not development.
That being said, start here:
http://forum.xda-developers.com/showthread.php?t=797688
Even though it is an EVO page, the theory still applies.
or this:
http://forum.xda-developers.com/showthread.php?t=764935
These are both easy to find utilizing the search function. Hope this helps.
kensikora said:
I have been running Uncommon Sense 1.1 for quite a while on my Incredible, and my absolute favorite aspect is the center Rose button being linked to a modified version of App Folders instead of the normal app drawer. Folder organization is pretty important for me due to a large quantity of apps.
Anyhow, I am now finding myself interested in changing ROMs (I used to test drive multiple ROMs a week, it's weird staying tied down). The problem is, I want the folder organization I've gotten used to mapped to Rosie.
The question is, how can I modify a ROM to achieve this? I have never modified a ROM before, and this sounds like a tough one to start with. My first inclination is to simply take the Rosie.apk from Uncommon Sense and plop it into a different ROM. But given than App Folders was modified in Uncommon Sense, would this work? And how would I do it? Or would I have better luck remapping Rosie to add the unmodified App Folders?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
MynWArm is a great ROM.. I prefer stock, I deodexed the most up to date Nov. OTA update completely rooted and busyboxed and deodexed. Which means you can run the stock ROM and add Modifications that you enjoyed such as the rosie modification. in mynswarm rom he has an app called rosie settings which you can choose the left and right buttons makes it sooo easy. lemme hook u up wit some links. I am uploading these things for you so I hope you use it.
step one, make sure your rooted S-OFF
download this stock ROM I deodexed, it's completely stock doesnt have any name or anything like that.
here is the ROM http://androidforums.com/incredible...dexed-added-root-nov-update-any-interest.html
or direct download link - http://www.multiupload.com/2KS0OS60DR
then you need to Flash this file from recovery once the ROM is up and running.
I'm uploading just for you so, I hope you use this.
flash from recovery, http://www.multiupload.com/5FLXLMGJHO
this will take a good ten minutes so boot, so don't panic and pull the battery it'll work.
once you have this flashed and phone is on and running you'll see something famililar to myns warm, rosie wise, you wont be able to use any of the buttons except the middle for all apps, this is were you take this .apk -
this part is really important download this .apk
http://www.multiupload.com/W4IX7D2423
and install your favorite way, I used astro to do it. but once this is instaleld open the app and you can change the left and right buttons to whatever..
all credit goes to the creators or mynwarm I just prefer to do the themeing myself, this is just an amazing mod that lets you change the rosie shortcuts in an easy to use app.
Awesome, man. That will probably do pretty much everything I need. Or probably pretty damn close to it. I'll try it out tonight and let you know how it goes.
Sent from my ADR6300 using XDA App
I tries using.virtuous and the buttons were all layer out on top of each other... In case anyone else had my bright idea
Sent from my Incredible using XDA App
I posted this on the CM Slide forum but I haven't gotten any actual help yet, I'm hoping someone here on XDA will be a bit more helpful
CM6/7 comes with the Gallery3D apk, which looks nice. However, it's slow. I hate opening it and sitting there waiting for the pictures to load, especially in folders with a lot of pictures.
It's even more annoying when I am trying to send an email/picture message and I have to sit there for a couple minutes waiting for them to load.
Does anyone have the stock gallery apk, or a good alternative? Or ANYTHING which will help whatsoever?
Thanks
So I don't know what this is, but the thread looked similar.
http://forum.xda-developers.com/showthread.php?t=775897&highlight=gallery
You could try that out, the file on mediafire there is Gallery.apk, but I haven't tried it out.
Thanks for the quick response
I actually did try doing that, it worked but it was very..unorganized, I guess. And no way to change it around to make it better
I'm currently using JustPictures...hoping to pull the stock gallery from my girlfriends Slide when I see her..but I was hoping maybe someone had a nandroid backup or something.
I looked in the stock Eclair ROM and it' says HTCAlbum.apk. I'll upload the .apk for ya, I hope it helps you out somewhat.
EDIT: AlbumStuffs.zip has 3 files, the .odex and 2 lib files. Lemme know if that helps out Now I'm interested in if this works.
Thank you!
I'm going to try it now, I'll edit this when I find out what happens.
*edit*
No good. I get Application Not Installed.
I'm currently trying to push to /system/app via ADB, hoping that helps.
Any ideas on what might work if this doesn't?
Thanks!
**edit 2**
ADB install gives me Install Failed Missing Shared Library, I'm guessing there's another file that goes with the HTCAlbum.apk, maybe an odex or whatever?
Would you mind maybe doing a quick search for anything associated with it, and upload if you find it? I'd appreciate it
Thanks again.
i would like the samething. i hate that the 3d gallery lags!!
well, I've tried pushing those files, fresh installs, and a few other unorthodox methods... can't seem to get the 2D gallery working from the HTC based Album. I'm not a dev at all, so I really can't do much else to help out here. Maybe a dev will glance over here while they are bored and looking for a project or something? Good Luck though, hope you are able to get this working.
You can't pull the stock gallery for several reasons. One, it's odexed, and our rom isn't, which might be why you get app not installed. Frameworks aren't compatible. Even if it was deodexed, it wouldn't work, since stock htc apps are tightly tied into com.htc.resources.apk and other htc and tmobile framework apk files which cm roms don't have. It is probably impossible to run htc system apps as standalone apps on other roms. Personally I don't have gallery issues running cm7, but if you do you will have to find a market alternative.
You can also select a tool like astro when attaching images when it asks you what you want to use to select an image, if you are having issues with the stock gallery from google.
Sent from my T-Mobile myTouch 3G Slide