![]() |
Re: [Announce] fMMS for N900
Quote:
I was able to receive full size image of: 114Kb 768x1024 116Kb 1024x768 but not 30.3kb 640x480 510kb 900x668 215kb 1600x1200 636kb 2576x1448 137kb 1280x960 112kb 1280x960 73.3kb 1072x804 47.5kb 640x480 The thing that puzzle me is the 30.3kb 640x480 or 47.5kb 640x480...why coudn't it display full size? Also...the ones that received full size show in the header mms version 1.2. And the ones in small thumbnail size show mms version 1.0. |
Re: [Announce] fMMS for N900
Im still getting the same problems I had in 2.7 in 2.8
But thanks for the constant updates and all the work you are putting into this :) |
Re: [Announce] fMMS for N900
Great work frals, loving this program. I just update the new version, picture is still a small :D
|
Re: [Announce] fMMS for N900
does anyone how to flash n900 please?
i got suck wit loop reboot |
Re: [Announce] fMMS for N900
fmms was working for me at version 2.7. i did an apt-get update it upgrad to 2.8 and it upgraded some python library, now when i try to send something it hangs up at compressing the image. i downgraded the fmms 2.7 it still doea the same thing. does anybosy know which python package upgraded so i can roll it back?
|
Re: [Announce] fMMS for N900
Quote:
Only thing I miss from older versions is that I now need to press a button below the message to see the attached picture. I think it was better when the image was seen on the same page with text. Less clicks is better imho :) But anyway, thanks frals (again)! |
Re: [Announce] fMMS for N900
Fmms: Attempting to download mms from server..
then it goes fail.. |
Re: [Announce] fMMS for N900
Quote:
Quote:
Quote:
Quote:
Quote:
Thanks everyone for testing! |
Re: [Announce] fMMS for N900
|
Re: [Announce] fMMS for N900
Haven't been able to send an MMS yet.
I get the load of yellow text... MMSC REPLIED:200_OK BODY: .................................. <TITLE>Error pag</TITLE> ..................................... URL not in active profile .............................. I guess thats the only important stuff. Haven't seen anyone with this issue yet. Any ideas? I'm not 100% on my settings, but pretty confident, noone else has got optus australia working yet as far as i know. Thanks |
Re: [Announce] fMMS for N900
Quote:
|
Re: [Announce] fMMS for N900
Nah haven't got anything... sent a few too... maybe its the receiving that i need to fix.
|
Re: [Announce] fMMS for N900
Quote:
|
Re: [Announce] fMMS for N900
Thanks a lot for getting all numbers to show, but was wondering if you could somehow still add tags for the numbers. As in this day and age remembering someones number just doesn't work :P
Logically thinking I'm guessing top number is main number, then second phone then business then .. ? But would be awesome if it would show to what the number corresponds to. cheers! |
Re: [Announce] fMMS for N900
Quote:
I'm not sure actually, depends on which order the vcard stores them as my algorithm just reads it from the top and adds them to a list :D |
Re: [Announce] fMMS for N900
Quote:
/opt/fmms/fmms_sender_ui.py:174: Warning: IA__g_object_get_valist: object class `HildonFileSystemSettings' has no property named `hour24' ret = fcd.run() /opt/fmms/fmms_sender_ui.py:317: Warning: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed gtk.main() /opt/fmms/fmms_sender_ui.py:317: Warning: g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed gtk.main() /opt/fmms/fmms_sender_ui.py:317: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed gtk.main() /media/mmc1/DCIM/20100108_001.jpg 300 True height 1448 width 2576 resizing Resizing image: 300 * 168 /home/user/.fmms/temp/20100108_001.jpg Test GOT SENDER: customMMS: None connecting via proxy 203.92.128.160:80 mmschost: mms.digi.com.my/servlets/mms MMSC STATUS: 403 Forbidden MMSC RESPONDED: <?xml version='1.0'?> <!DOCTYPE html PUBLIC '-//WAPFORUM//DTD XHTML Mobile 1.0//EN' 'http://www.wapforum.org/DTD/xhtml-mobile10.dtd'> <html xmlns='http://www.w3.org/1999/xhtml'> <head> <title>The request failed</title> </head> <body> <p><big>Access denied.</big></p> <p> <i>Technical description:</i><br/>403 Forbidden - You are not allowed to communicate with the requested resource.</p> </body> </html> () Removing temporary image... ^CTraceback (most recent call last): File "/opt/fmms/fmms_sender_ui.py", line 321, in <module> app.run() File "/opt/fmms/fmms_sender_ui.py", line 317, in run |
Re: [Announce] fMMS for N900
Quote:
Anyway, seems like you are not allowed to send MMS through the specified MMSC, so (most likely) its either A) Wrong settings or B) you are not allowed to send MMS for your carrier EDIT: 0.2.9 uploaded on garage, will submit to repos whenver extras-assistant decides to not time out... changelog: 0.2.9: * removed fake UA-string again as it seems pointless * contactslist should show what type of number it is * gui no longer freezes when launched from the mms notification * message is sent as mms version1.2 |
Re: [Announce] fMMS for N900
Dear frals
I am currently running version 0.2.8 and this morning amazingly I received a full size picture from my gf :D, loving it. Thank you so much |
Re: [Announce] fMMS for N900
Quote:
|
Re: [Announce] fMMS for N900
Quote:
|
Re: [Announce] fMMS for N900
0.2.8 allowed me to download full size messages on O2 Ireland too.
|
Re: [Announce] fMMS for N900
Great! I have reverted back to 0.2.8 behavior in 0.2.10, and since repos have been down all day the only place to get the 0.2.9 is garage so I won't push 0.2.10 yet ;-)
|
Re: [Announce] fMMS for N900
i m getting this..
Quote:
|
Re: [Announce] fMMS for N900
Quote:
|
Re: [Announce] fMMS for N900
@dinz
I don't think 172.16.74.100 is a publicly accessible address which means you'd need to set a proxy. According to your log your connection is without a proxy. @wierdo I believe it is also the case for AT&T but then again I haven't tried w/o going through proxy. |
Re: [Announce] fMMS for N900
Quote:
|
Re: [Announce] fMMS for N900
Hey Frals....I am able to receive all image size now and this is still version 2.8. But it seems like the max image size that can display is 1024x768. So if i send one that is greater than that size...it will reduce to that size. Also the MB SIZE is about 115kb MAX and even though the bytesize says 115kb or lower...i don't see image quality being reduced?? Kind of weird. Anyway, i think it's all good now!
Another thing is i am not sure you notice this....for example if person 1 send me the first image with his name display. Then every other image sent after by anybody else will be titled under his name and phone #. |
Re: [Announce] fMMS for N900
Quote:
Not sure I understand you, does all the messages appear to be from the same sender? Could you provide a screenshot? Are the messages sent from a phone or email? |
Re: [Announce] fMMS for N900
Quote:
|
Re: [Announce] fMMS for N900
Quote:
|
Re: [Announce] fMMS for N900
Quote:
Yes, obviously your carrier ignores x-wap-profile and does not care what the standard says about content-adaption (the way I've understood the purpose of x-wap-profile anyway, but I've been wrong before :P). I'm afraid the best workaround so far is sending N95 UA, which gives you 1024x768 and 150kb pictures - if you have any idea how to solve this please do share. Regarding your problem with senders looking like they come from the same person, it's probably because there is no code at all dealing with e-mail addresses yet, and the phone matching algorithm is just a quick placeholder for now. It's on the todo ;) Thanks for testing. |
Re: [Announce] fMMS for N900
Don't know if this has been mentioned and if it's network specific (OS specific perhaps?), but I wanted to say ending the proxy in .030 as it was reported in my old phone didn't work with fMMS until I changed it to .30 (fMMS just sat there and after a long while delivered an error message). Now it works like a charm.
Oh and thanks for a great app! |
Re: [Announce] fMMS for N900
Just a quick thought. What if fmms uses a new and unique User-Agent? Wouldn't that force some carriers to respect x-wap-profile value since they won't have a clue what the target device's capabilities are?
Maybe add a way in fmms to set different user-agent and profile? |
Re: [Announce] fMMS for N900
Quote:
Setting a unique User-Agent made TMO go stoneage on us and resize to min. allowed size, even if profile header was set like it should be :( The thing is, it seems only TMO USA has this problem (don't think anyone outside TMO USA has encountered this?), I see a few hits on my webserver from MMSCs that actually do respect the x-wap-profile header and fetches the UAProf document :) |
Re: [Announce] fMMS for N900
Quote:
|
Re: [Announce] fMMS for N900
Hello Frals, here is my new observation, If the picture is sent as a horizontal picture then it will arrive as a thumbnail, however, if the picture is sent as vertical, then it will be alrite. Not sure why though :D
|
Re: [Announce] fMMS for N900
Dear Frals, another observation, it seems that I was only able received 1 picture full size that I mention before. Later on, everything is thumbnail. I am using 0.2.8 :D
|
Re: [Announce] fMMS for N900
So can anyone that has FMMS fully working with TMobile USA please post their info/setup (APN).
I can receive MMS, but not send them. And when I receive them their small thumbnails. I just really need to be able to send them. Sorry if this has been answered already. Thanks |
Re: [Announce] fMMS for N900
Cant there be made a plugin? so that you receive them in the conversation menu?
|
Re: [Announce] fMMS for N900
I've noticed that coming from T-Mobile USA I'm unable to send any MMS to a user on Verizon Wireless. Every other carrier they go through fine, tested it out on 4 different users in different regions of the US(Arizona, Florida, New Mexico, North Carolina) over the past 2 weeks and none of them received it, or even a notification. They receive them just fine if they're sent from my BlackBerries, HTC Win-Mo phones, or the Nexus One so I know it's a fMMS issue somewhere. No idea what it would be though.
|
| All times are GMT. The time now is 20:54. |
vBulletin® Version 3.8.8