Related
OK, so for some reason our builds happen to be hardcoded with a UserAgent Profile pointing to http://www.google.com/oha/rdf/ua-profile-kila.xml. This is reported to the MMS server whenever our MMS client tries to download something, it's stuck in the x-wap-profile: header of the HTTP request.
If you read thru that file you'll see that it's the spec for a Samsung SGH-T429 with 320x480 screen. While looking into MMS receive issues on Sprint we discovered that the MMS server actually reads these profiles, and sizes the output that it sends you based on these profiles. So even if your buddy sends you a nice high-rez photo by MMS, when you receive it, it will be scaled down to 320x480.
[edit: that's not quite true. I think this only affects the size of the image as presented in the Messaging app. The actual attachment is whatever size was originally sent. Of course, most media is scaled down for sending anyway.]
We checked to see what profile the Sprint RHOD400 was sending under Winmo and found this http://device.sprintpcs.com/HTC/PPCTP7380SP/2046514.rdf which seems to have the correct screen dimensions. (I can't seem to download it now though.)
I also checked to see what my phone was using with T-Mobile, and got this
http://www.htcmms.com.tw/gen/RhodiumMR-1.0.xml which also has the right stuff, but a lot of winmo-specific details too. It seems to me that we're going to need to patch the framework to make this profile URL a settable property instead of hardcoding it like it's currently done, to get the most out of MMS.
We should probably start taking an inventory of profiles that are in use on all the MSM devices. In Winmo you can find them in the registry at HKLM\Software\Jataayu\MMS\SP - according to this thread: http://forum.xda-developers.com/showthread.php?t=795343
For example, here's the request for a Sprint RHOD400:
Code:
GET /?msgid=XXX&userId=YYY HTTP/1.1
Accept: */*, application/vnd.wap.mms-message, application/vnd.wap.sic
x-wap-profile: http://device.sprintpcs.com/HTC/PPCTP7380SP/2046514.rdf
Accept-Language: en-US
Host: mms.sprintpcs.com:80
Connection: Keep-Alive
User-Agent: T7380
Here's the request all of our phones are currently using to retrieve MMSs:
Code:
GET /?msgid=XXX&userId=YYY HTTP/1.1
Accept: */*, application/vnd.wap.mms-message, application/vnd.wap.sic
x-wap-profile: http://www.google.com/oha/rdf/ua-profile-kila.xml
Accept-Language: en-US
Host: mms.sprintpcs.com:80
Connection: Keep-Alive
User-Agent: Android-Mms/2.0
I've got this one in the registry:
http://www.htcmms.com.tw/gen/HTC_Touch_Pro2_T7373-1.0.xml
( Rhod100 / AUO )
Mine reads:
http://www.htcmms.com.tw/gen/HTC_Touch_Pro2_T7381-1.0.xml
Also worth noting it was in the registry key:
HKLM\Software\SIE\AutoVer\Opera\User Prefs
and HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings
Raa_1 said:
Mine reads:
http://www.htcmms.com.tw/gen/HTC_Touch_Pro2_T7381-1.0.xml
Also worth noting it was in the registry key:
HKLM\Software\SIE\AutoVer\Opera\User Prefs
and HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings
Click to expand...
Click to collapse
What model RHOD is that?
This was a setup.xml I made for people running custom roms on boost mobile. Everything should be the same for sprint except the "pcs-boost-mmsc" server address. Maybe helpful?
I changed it to .txt for posting. It seems to be the same that you have.
I know this is probably way to early to be asking this, but I have a Rhod400, where can I input this info (into what file or terminal emulator?) so that I can get MMS working on my phone so I can test it until the patch is ready for the public?
slickdaddy96 said:
I know this is probably way to early to be asking this, but I have a Rhod400, where can I input this info (into what file or terminal emulator?) so that I can get MMS working on my phone so I can test it until the patch is ready for the public?
Click to expand...
Click to collapse
Kinks are being worked out, to my knowledge nothing usable has surfaced yet. Sending works like a champ with the new RIL, and reception works - just gives a useless download link. Trying to make that link work, is what we're trying to do!
We checked to see what profile the Sprint RHOD400 was sending under Winmo and found this http://device.sprintpcs.com/HTC/PPCTP7380SP/2046514.rdf which seems to have the correct screen dimensions. (I can't seem to download it now though.)
Click to expand...
Click to collapse
I appreciate all the work that you've been doing, and especially for Sprint (even though you're on a GSM device ).
That site doesn't hit (I was hoping it was user-agent dependent, but it didn't work on my phone either).
Also, this thread (http://forum.ppcgeeks.com/htc-touch-pro-2/101286-native-htc-messaging-mms-fix-collaboration-31.html) says that there's no 1st P in the PPCT7380SP string, so it looks like http://device.sprintpcs.com/HTC/PPCT7380SP/%CDMA_ROM_VERSION%.rdf. Is anyone else able to download this .rdf file?
edit: and the 2046514 corresponds to the ROM version (found in Device Information/Software), which (for me at least) is 2.04.651.4
I don't get the download button on my RHOD500. Well it's there for a split second then downloads on it's own. Originally set the APN before all the ril changes so after setting the carrier ID it just worked with the new ril.
eww245 said:
I don't get the download button on my RHOD500. Well it's there for a split second then downloads on it's own. Originally set the APN before all the ril changes so after setting the carrier ID it just worked with the new ril.
Click to expand...
Click to collapse
Wait so Verizon CDMA MMS works?
rpierce99 said:
Wait so Verizon CDMA MMS works?
Click to expand...
Click to collapse
If I'm not mistaken, Verizon has been working ever since highlandsun's amazing work on the RIL originally.
manekineko said:
If I'm not mistaken, Verizon has been working ever since highlandsun's amazing work on the RIL originally.
Click to expand...
Click to collapse
If that's the case I really need a kind verizon user to provide me a download link for a MMS attachment. It's in mmssms.db, probably easiest for that person to hop on IRC so we can chat about it. Basically I need to figure out what is different about the Sprint payload than the Verizon payload to see why Sprint doesn't work.
rpierce99 said:
Wait so Verizon CDMA MMS works?
Click to expand...
Click to collapse
For me yes, no issues at all
rpierce99: you didn't get my note on IRC I guess. I'm pretty sure the attachment isn't the problem; pretty sure the problem is the original SMS PDU. You can grab that from the radio logcat when the MMS arrives. Decoding it is a bit more of a hassle; my code in the RIL only decodes the first 6 headers then passes the rest to Android to decode. Get me a sample PDU from your radio log...
I take that back. Now I see what the parser is doing...
Is this what you need?
The pdu table has some other info but connectbot isn't being nice
GSM_PDU=000002100402070295EA216506000601FC087600031257E0016703280010099199897B9B2B93B3632BA3997B6B6B99FB6B2B9B9B0B3B296B4B21E9820A19CA099989C9899A21C9818181821A19A1818181818981880448B401A9B981C1C1A9C9A189C17AA2CA8229EA82626A7004B233BB21D10233BB21D102A32B9BA34B7338000306110516223640
Click to expand...
Click to collapse
Sprint MMS receive is now working.
Yes, thanks. But I don't need it now, already got a copy.
We actually identified the problem several days ago, there's even a fix for it already in the Gingerbread source tree. But backporting the fix to Froyo was messy. I've now made a new fix that applies cleanly to Froyo and doesn't rely on the stupid compile-time settings that Google's fix uses. rpierce99 helped to verify that it works.
Basically the MMS server software that Sprint uses is mis-formatting what it sends out. The official specification for MMS/WAP says to do one thing, Sprint's MMS server does something completely different / wrong. The Android MMS parser would just die with an exception when trying to parse these things. The fix makes it ignore the improper header. There are other things that Sprint's server does that are also questionable. Even with this fix, if you want someone to send you an image or video in an MMS, make sure they don't type any text into the message body, otherwise it will still arrive messed up.
OK, the issues with displaying MMS image+text messages are resolved now too. And I've made the uaProfURL a settable property in case you want to override the compiled-in setting. set the ro.product.uaprofurl property to the URL you want to use.
Of course, you need to be running my patches to the Mms.apk for this to work. The source code is here https://gitorious.org/hycdroid/packages_apps_mms/commits/froyo
Full description of the Sprint bugs and the fixes: http://lists.xdandroid.com/pipermail/xdandroid-dev/2011-May/000288.html
So what was the initial problem here?
*scratches head*
MMS always physically worked fine for me. (your RIL)
Was it just an issue displaying the contents I never picked up on or...?
ryannathans said:
So what was the initial problem here?
*scratches head*
MMS always physically worked fine for me. (your RIL)
Was it just an issue displaying the contents I never picked up on or...?
Click to expand...
Click to collapse
Did you read his post? It's a Sprint-only issue. Always was (after his RIL).
Might want to look at this section of his post...
highlandsun said:
Full description of the Sprint bugs and the fixes: http://lists.xdandroid.com/pipermail...ay/000288.html
Click to expand...
Click to collapse
/facepalm...
Had a few late nights and unknowingly started reading from page 2.
I carrier unlocked (and rooted) the INC2 using on TMOUSA.
I've searched high and low before deciding to post to the XDA community about the following:
INC2 can get 3G on tmo data network (my settings are on gsm only) and i've seen the 3G logo come on and off for 5 seconds...maybe twice a day.
I am wondering if the User Agent (UA string) for the DEvice needs to be changed in lets say a mytouch 4g to get tmo to recognizae the device name and access 3g data.
Also...mms pics come in at less than 20kb. Horrible. I've looked and did all the various settings (epc.tmobile.com and wap.voicestream.com mms settings). None of them allow the pics to come in at larger scale because once again, the user agent or user profile needs to be changed to a tmobile phone.
Does or has anyone encountered these 2 issues and if so, what strings specifically can be modified for 3g / true mms pics.
Thank you!
From what I gather, the inc 2 can only use the edge frequency, 1900mhz on t mobile.
The spec sheet states that it can use 850, 900, 1800 & 1900 mhz.
T mobile's 3g operates at 1700 & 2100mhz. Therefore the inc 2 should not be capable of 3g on t mobile. Sorry but it looks like you're s.o.l.
EDIT: looks like I was mistaken, the vzw website shows that it is capable of 2100mhz. I would be interested to see what happens with this.
Ok thank you. If I see the G logo in my data again ill screenshot it.
So what about the mms and editing the ua string so the pics come out correctly.
I'm rooted but on stock froyo. I've heard of Mms.all but I think there are UA string edits that can be done.
Any help would be appreciated
As far as I know the UA string only affects the web browser and how the web perceives the device. I'm not familiar with gsm networks at all so I don't know if mms would be determined by a UA string.
to change your UA string you can go into the browser and put in about:debug then go into settings and toward the bottom you can change it to whatever you would like. I'm not sure if this would be a global setting though.
have you looked at the settings in the htc messaging app for the mms settings at all? Or looked at the mms settings in epst? Sounds like you may need to manually enter t-mobile's mms apn in epst. Also the messaging app "go sms" allows you to do that in the settings of the app.
G was probably for GPRS, not for 3G
pcmedics911 said:
Ok thank you. If I see the G logo in my data again ill screenshot it.
So what about the mms and editing the ua string so the pics come out correctly.
I'm rooted but on stock froyo. I've heard of Mms.all but I think there are UA string edits that can be done.
Any help would be appreciated
Click to expand...
Click to collapse
pcmedics911 said:
Ok thank you. If I see the G logo in my data again ill screenshot it.
So what about the mms and editing the ua string so the pics come out correctly.
I'm rooted but on stock froyo. I've heard of Mms.all but I think there are UA string edits that can be done.
Any help would be appreciated
Click to expand...
Click to collapse
Here make this edit
<!-- MMS UA string -->
<module name="MMS">
<function name="ua_string">
<set name="single">
<item name="value">Nexusone</item>
</set>
Wonderful thank you
Which file do I edit to change the string?
Also, do upper / lowercase for NexusOne play at all into getting mms to work correctly?
pcmedics911 said:
Wonderful thank you
Which file do I edit to change the string?
Also, do upper / lowercase for NexusOne play at all into getting mms to work correctly?
Click to expand...
Click to collapse
I guess just do "Nexusone" to be safe go into /system/customize/MNS/default.xml
edit it in there
Just install APN Backup & Restore from Market.
Open it.
Delete APNs.
Backup APNs.
Name the file whatever you like (apn.xml).
Dl the tmobile_apns.xml.ZIP remove the .ZIP at the end of the file.
Place the tmobile_apns.xml file inside the ApnBackupRestore folder that is now on your sd card.
Restore APNs (select tmobile_apns.xml).
Make sure that you have Data enabled.
Turn off WiFi and Reboot your device (not needed but, that's what I do, just to make sure everything is working over Tmo's network).
Enjoy!
Moved to proper forum.
Ok Thank you for the APN info.
I had the APN's..the pics still come out tiny (in handecent as 19k) and in the Android messaging app come out bigger but blurry (17k)
I read somewhere that if tmo does not recognize the phone as tmo branded phone, it will reduce the mms pic size.
I know the iphone is not a tmo phone and does not suffer from the same mms small pics.
I don't know if there is a user agent string to edit (i changed the user agent string us mms per above to nexusone and its still bringing in small pics.
Oddly enough...there is a ua profile url:
http://uaprof.text.com/pcd/adr6350/adr6350.xml
ard6350 is the name of the incredible 2 so i changed anything that was ard6350 to nexusone in the /system/customize/mns/default.xml file.
still getting same small pics
any ideas what else to edit in the incredible 2 to get hte mms pics to come through in the correct size?
pcmedics911 said:
Ok Thank you for the APN info.
I had the APN's..the pics still come out tiny (in handecent as 19k) and in the Android messaging app come out bigger but blurry (17k)
I read somewhere that if tmo does not recognize the phone as tmo branded phone, it will reduce the mms pic size.
I know the iphone is not a tmo phone and does not suffer from the same mms small pics.
I don't know if there is a user agent string to edit (i changed the user agent string us mms per above to nexusone and its still bringing in small pics.
Oddly enough...there is a ua profile url:
http://uaprof.text.com/pcd/adr6350/adr6350.xml
ard6350 is the name of the incredible 2 so i changed anything that was ard6350 to nexusone in the /system/customize/mns/default.xml file.
still getting same small pics
any ideas what else to edit in the incredible 2 to get hte mms pics to come through in the correct size?
Click to expand...
Click to collapse
yea youll need to do a fresh installation of the rom if you changed the ua string
I have an issue with photos taken in dark conditions, they are all messed up, or broken if you will, looking like corrupted JPG. In slightly better light conditions everything is fine. Reboot did not help. It happens now with default camera in sebaastian15's AIO 2.5 but I have also noticed it in AIO 2.2. Is there a way to upgrade/replace stock (sense 3.5) camera? Did anyone experienced such an issue?
I could insert image of screwed up photo but "noobs" like me have no access rights, so to look at it, make up and URL from this "img43.imageshack.us/img43/3977/imag0616d.jpg" or that one "img838.imageshack.us/img838/5885/imag0610g.jpg".
Also do not ask me to ask this question on the ROM thread... again, I am just a dumb "noob" so I cannot comment on super-duper-exclusive dev threads.
-andy.
jedreg said:
...make up and URL from this "img43.imageshack.us/img43/3977/imag0616d.jpg" or that one "img838.imageshack.us/img838/5885/imag0610g.jpg".
-andy.
Click to expand...
Click to collapse
Unable to see these images.
same here
the same happened with me too
but on older versions of runnymede and runnymedemod007
mine even used to restart the whole phone
i suggest using market apps like camera 360 or others if you prefer
I was trying to avoid non-sense (hehe) cameras, but I will give it a try to be able to take night picture despite low quality... what I have noticed (but have to prove tonight) is that after I changed preferred ISO to 800 the picture taken is ok, and even when I set it back to "auto" - this sounds like ISO property is not really set and may mess up when pixel brightness computation in low light conditions (just a theorem).
ckpv5, I copied&pasted address to URL bar of web browser and it works for me, maybe you do not have access to imageshack server. When I reach "10 mails level" I will just embed it here.
-andy.
jedreg said:
ckpv5, I copied&pasted address to URL bar of web browser and it works for me, maybe you do not have access to imageshack server. When I reach "10 mails level" I will just embed it here.
-andy.
Click to expand...
Click to collapse
Yeah.. I guess it is no access as this is what I got http://imageshack.us/img/blocked_login.jpg
Anyway... your workaround on the problem is good.
Night test done... default camera screws up pictures unless you manually set ISO. Re-checking "auto" does not help, but setting 400 or 800 helped me to make couple souvenir pictures.
-andy.
Hey guys,
So I'm enjoying my note 10+ so far, but I'm having an issue when trying to send live messages. The messages come out very compressed and after doing some research, it was advised to send them as mp4s instead of gifs. So I tried that, but it was even worse.
So I said forget it and that I would just send gifs like I did on my lg v30. But the same issue persists, even with tiny gifs. The gifs are severely compressed and washed out. I tried using the stock messenger, signal and textra, but they all seem to be exhibiting the same issue. Whereas on my v30, textra never gave me any issues and I could send very large gifs even with no problem.
My phone is an n975u1 us model that I purchased and imported into Canada, running xaa firmware and not xac. My apn settings are all fine, I can send and receive calls, etc. Does anyone know what's going on or have the same issue?
Here is a screenshot of the issue:
https://ibb.co/qd6zhgB
crushdancexz said:
Hey guys,
So I'm enjoying my note 10+ so far, but I'm having an issue when trying to send live messages. The messages come out very compressed and after doing some research, it was advised to send them as mp4s instead of gifs. So I tried that, but it was even worse.
So I said forget it and that I would just send gifs like I did on my lg v30. But the same issue persists, even with tiny gifs. The gifs are severely compressed and washed out. I tried using the stock messenger, signal and textra, but they all seem to be exhibiting the same issue. Whereas on my v30, textra never gave me any issues and I could send very large gifs even with no problem.
My phone is an n975u1 us model that I purchased and imported into Canada, running xaa firmware and not xac. My apn settings are all fine, I can send and receive calls, etc. Does anyone know what's going on or have the same issue?
Here is a screenshot of the issue:
https://ibb.co/qd6zhgB
Click to expand...
Click to collapse
There are limits to how big of a file you can send via MMS (or via RCS)... If the messaging application is compressing the image then the size of the file you tried to send exceeds the limit. With larger sized images/files the compression will probably be more aggressive (and more noticeable).
On my phone looks like the limit is 105mb file size for RCS messaging
I know that there are file limits. But I've never had an issue with this using the lg v30.
crushdancexz said:
I know that there are file limits. But I've never had an issue with this using the lg v30.
Click to expand...
Click to collapse
I can't tell you why brand X works and brand Y doesn't. Also in the same token it's not really conducive to finding out why your having (solving and/or identifying the cause of) image quality issues on a Note 10+ using a Note 10+ to send a mms image.
Try this to see if the file size limit is being enforced:
Reduce your image size to less then 105 megabytes and try again. Save the file and compare file size (refer to note 1 below)
Create an image file a little larger then 105 megabytes.. If the image appears normally then save it and compare file sizes (refer to note 2 below)
Create an image file like what you had before and send it. Save the file and view the file size (refer to note 3)
~Notes~
Compare the file size of what you received (with that of what you had sent) to see if it is the same size.
You are trying to see if anything a little over 105mb gets reduced in both quality and file size. Compare what you sent with what you received. If the file size of what you received is smaller then what you sent, then file size limits are being enforced
Again like above you are trying to see if the file size is reduced to 105mb or less. If the file size of what you received is smaller then what you sent file size limits are being enforced.
If file size limits are being enforced I am not aware of any method or way to remove or disable said limit set by the carrier. If you have a larger image you wish to send then you may want to consider alternative file transfer methods (Facebook messenger, email, etc)
scottusa2008 said:
I can't tell you why brand X works and brand Y doesn't. Also in the same token it's not really conducive to finding out why your having (solving and/or identifying the cause of) image quality issues on a Note 10+ using a Note 10+ to send a mms image.
Try this to see if the file size limit is being enforced:
Reduce your image size to less then 105 megabytes and try again. Save the file and compare file size (refer to note 1 below)
Create an image file a little larger then 105 megabytes.. If the image appears normally then save it and compare file sizes (refer to note 2 below)
Create an image file like what you had before and send it. Save the file and view the file size (refer to note 3)
~Notes~
Compare the file size of what you received (with that of what you had sent) to see if it is the same size.
You are trying to see if anything a little over 105mb gets reduced in both quality and file size. Compare what you sent with what you received. If the file size of what you received is smaller then what you sent, then file size limits are being enforced
Again like above you are trying to see if the file size is reduced to 105mb or less. If the file size of what you received is smaller then what you sent file size limits are being enforced.
If file size limits are being enforced I am not aware of any method or way to remove or disable said limit set by the carrier. If you have a larger image you wish to send then you may want to consider alternative file transfer methods (Facebook messenger, email, etc)
Click to expand...
Click to collapse
I sent a static jpeg and it went from 881Kb to 351Kb on the Note. On the V30 it was still 881Kb.
I really don't think this has anything to do with my network because the v30 on the same network does not do this. With *any* text program.
crushdancexz said:
I sent a static jpeg and it went from 881Kb to 351Kb on the Note. On the V30 it was still 881Kb.
I really don't think this has anything to do with my network because the v30 on the same network does not do this. With *any* text program.
Click to expand...
Click to collapse
What your LG can or can not do is not conducive nor helpful for what the Note 10+ is or isn't doing (and why). For example here's why it doesn't help...
What if a toggle exists on the LG phone that doesn't exist on the Note 10+? - You can't root the Note 10+ variant you have so you can't make a toggle appear without either the carrier enabling it (or an app that has it added).
What if the LG phone was provisioned differently then the Note 10+? - You can't make changes to the Note 10+ variant your using within regards to carrier provisioning...
What if an LG app allows larger files? - That's not gonna be of any help with a Samsung Note 10+
I did some research today on the subject and what I found across different providers support forums as well as Samsung support forums is that the issue is related to MMS limitations on image size. Yes some people mentioned that there "LG phone could do it" but it isn't exactly as simple as that. In some cases (whether phone, stock applications or within 3rd party apps) a setting exists which allows one to choose the quality of the image being sent. In your stock apps or 3rd party apps your gonna want to see if you can find this setting. If you can't find the setting then this means it isn't something you can change, and if this is the case then nothing can be done.
In my Note 10+ case I don't see this on Google Messages app nor my stock messaging app, so when I send a MMS of 240kb in size (or a test image that was over 2mb in size) it gets compressed. Again this isn't a phone issue, it is something that is set and controlled by my carrier... Which in your case I imagine your being effected by the same limitations.
Thank you for looking deeper into it. I read the same thing on the Samsung boards and across reddit as well during my research. It's just very frustrating because I really enjoy mms and sharing content with my friends. I was going to sell the v30 and keep the note, but now I'm not sure what to do. Even the edge lighting for the phone is broken and there's no real solution for that either based on my research. Yes they're different phones, but using the range app didn't even resolve the issue, on the same carrier. So what's the difference if not the phones? It just seems like Samsung likes saying this and that, but the features are half baked. I'd even trade gifs for live messages, but that's even more broken. Thanks again though for trying to help. You're a pretty cool person.
Hey, Crush. Just curious - what app were you using on the LG? If the same one on Samsung, was it the same version? If not, you could try exporting the APK from the LG and installing it on the Samsung.
After doing hours of searching and reading I found I'm not the only person that faces this issue, but many have solved this issue by editing the mms_config.xml inside res/xml/.
I've changed the "maxMessageSize" and also "maxImageHeight" and "maxImageWidth" to a variety of different numbers (up from stock 640x480), and it HAS made some difference, however neither max image size nor image resolution is being reached and my resulting MMS is still somewhat blurry. I recall fixing this issue fully for my S4 back in the day with 0 resulting blur but I must be missing something else in the apk here.
I'm thinking the uaProf and UserAgent strings may have something to do with it, but any strings I've managed to find via google make no difference at all to the size/quality of the outgoing MMS.
Looking for a native solution and not "use handscent/gosms instead" alternatives, seen these suggestions as "fixes" in almost every thread related to this.
If anyone is aware of anything else I can test or a different xml file in the apk that can be tweaked would appreciate it.
Carriers max MMS is 1.2MB but even 300-400kb images are being compressed to 70kb but like I said it has made a difference, just that the numbers I'm entering aren't being respected fully
Thanks
Meanwhile a friend of mine on the same carrier can send me a crystal clear image in almost 2k resolution from an iphone. Just standard MMS nothing 3rd party, if they can do it why should Google's official Android messaging app be so terrible to such an extreme degree. 640x480 found in the stock mms_config.xml is almost unbelievable when the network is capable of transmitting over 3x that resolution