[Announce] fMMS for N900 - Page 47 - maemo.org

Active Topics

The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 13 hrs, 1 min ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 9 hrs ago
more...

Page 47 of 159

Thread Tools

matrim	2010-01-23 , 19:29
Posts: 121 \| Thanked: 75 times \| Joined on Oct 2009	#461

0.2.8 allowed me to download full size messages on O2 Ireland too.

frals	2010-01-23 , 20:09
Posts: 547 \| Thanked: 1,383 times \| Joined on Sep 2009 @ Stockholm, Sweden	#462

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 ;-)

__________________

Problem with fMMS? Run in x-terminal: cp /tmp/fmms.log /home/user/MyDocs/
After that you'll see fmms.log in filemanager or when you connect the device to your desktop as a mass storage device.
E-mail the log to me, if you don't have the email address, drop me a PM. Thanks!

fMMS - MMS for your N900
fAPN - GUI for adding a new GPRS APN
If you like this post, don't be shy to thank me -->

dinz	2010-01-23 , 21:31
Posts: 12 \| Thanked: 0 times \| Joined on Jan 2010	#463

i m getting this..

$ /opt/fmms/fmms_gui.py
(1,)
http://172.16.74.100:10021/mmsc/1_2?AsGwLtrVizpgtrQ--
AsGwLtrVizpgtrQ--
creating dir
getting file: http://172.16.74.100:10021/mmsc/1_2?AsGwLtrVizpgtrQ--
setting up notify sender
GOT SENDER: None
customMMS: True
sending notify...
using custom mms
connecting without proxy
mmschost: Http: path: //172.16.74.100:10021/mmsc pathlen: 26
notify sending failed...
connecting without proxy
<urlopen error timed out> (timeout('timed out',),)
removing dir...
connection_cb(<conic.Connection object at 0x4122a0d0 (ConIcConnection at 0x45f310)>, <conic.ConnectionEvent object at 0x41229e68 (ConIcConnectionEvent at 0x42c5c0)>, acdcacdc)

wierdo	2010-01-23 , 21:42
Posts: 118 \| Thanked: 26 times \| Joined on Jun 2008	#464

Originally Posted by woody14619

For my carrier (AT&T US) all settings are identical except for the proxy.

at&t doesn't actually require that you use the proxy, FWIW. You can connect directly to the MMSC as long as you are using the wap.cingular APN.

benaranguren	2010-01-23 , 21:49
Posts: 17 \| Thanked: 13 times \| Joined on Dec 2009	#465

@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.

The Following User Says Thank You to benaranguren For This Useful Post:
frals

frals	2010-01-23 , 22:13
Posts: 547 \| Thanked: 1,383 times \| Joined on Sep 2009 @ Stockholm, Sweden	#466

Originally Posted by dinz

i m getting this..

Uh yeah, I see a bug in my code there, try changing your mmsc setting to "http://url" instead of "Http", I got it fixed in the next version :P

romanianusa	2010-01-23 , 23:49
Posts: 739 \| Thanked: 114 times \| Joined on Sep 2009	#467

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 #.

Last edited by romanianusa; 2010-01-24 at 02:18.

frals	2010-01-24 , 00:03
Posts: 547 \| Thanked: 1,383 times \| Joined on Sep 2009 @ Stockholm, Sweden	#468

Originally Posted by romanianusa

Hey Frals....I am able to received 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 #.

Weird, according to the UAProf supplied by the N95 it should be good upto 2048x1536 and 300kB - but seems like your carrier... well, to be frank, sucks donkey balls

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?

The Following User Says Thank You to frals For This Useful Post:
daperl

romanianusa	2010-01-24 , 00:12
Posts: 739 \| Thanked: 114 times \| Joined on Sep 2009	#469

Originally Posted by frals

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?

Yes all messages appear from the same sender. I sent messages from email and phones under different email addresses and yet it displays as the same sender in the title message.

romanianusa	2010-01-24 , 00:20
Posts: 739 \| Thanked: 114 times \| Joined on Sep 2009	#470

Originally Posted by frals

Weird, according to the UAProf supplied by the N95 it should be good upto 2048x1536 and 300kB

You say 2048x1536?? And i say the max is 1028x768. Have you notice that's HALF of your size?? That can not be coincidence...something must be going on that can probably be easily fixed. And i am guessing the max MB that i can received is half of 300Kb..which is 150kb.

Page 47 of 159

Active Topics

The N900 is now 15 years old! (8)

Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)

Notices