[Announce] fMMS - MMS on the N900 - Page 101 - maemo.org

Active Topics

Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 1 day, 7 hrs ago
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 2 days, 4 hrs ago
more...

Page 101 of 104

101

Thread Tools

	peterleinchen	2015-07-03 , 19:31
	Posts: 4,117 \| Thanked: 8,901 times \| Joined on Aug 2010 @ Ruhrgebiet, Germany	#1001

xes, which version are you using?

I grepped through the sources and did not find occurences of 'impossible to retrieve'!
Do you get this in fMMS GUI when touching that MMS?
Since when do you have this behaviour?

Do you have a file named 'headers' in that directory? What is the status of 'Retrieve-Status'?

I had that once (long before) that MMS was downloaded correctly but somehow not marked as downloaded (in mms.db). I guess it had to do with a wrong header decoding at the end (some ending char missing) so decoding took place but it was not entered into db as downloaded/received.

__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature

Quote & Reply |

The Following 3 Users Say Thank You to peterleinchen For This Useful Post:
mrsellout, Wikiwide, xes

xes	2015-07-03 , 21:20
Posts: 638 \| Thanked: 1,692 times \| Joined on Aug 2009	#1002

@peterleichen
fmms version is 1.3.6-1

Sorry, the exact error is "Failed to retrieve" and is inside the file "message" of mms folder.
But... images and text_0.txt are there and perfectly readable.
The "headers" file contains:
Transaction-Id 99905
MMS-Version 1.3
Message-Type m-retrieve-conf
Date Tue Jun 30 17:43:00 2015
Message-ID mS5R8-ZkUZf1DbTFkZvF00
Content-Type ('text/plain', {'Charset': 'utf-8'})

I don't receive mms so often, but all the mms received in the last 2 months behave in this way.

Do you think that this (maybe decode) error could be cross checked verifying the presence of not empty attachments/parts in the mms folder? In this way we could at least see the attachments succesfully decoded... something is better than nothing..
A message like "something went wrong but part of the message has been received. Do you want to retry or open the parts already decoded?"

Quote & Reply |

The Following User Says Thank You to xes For This Useful Post:
Wikiwide

	peterleinchen	2015-07-03 , 21:49
	Posts: 4,117 \| Thanked: 8,901 times \| Joined on Aug 2010 @ Ruhrgebiet, Germany	#1003

Originally Posted by xes

@peterleichen
fmms version is 1.3.6-1

okay

Sorry, the exact error is "Failed to retrieve" and is inside the file "message" of mms folder.

going to check tomorrow

The "headers" file contains:
MMS-Version 1.3

Uh, oh.
I think this could be the culprit.
fMMS was created using 1.0. I added one addigtonal header item of 1.2 spec to enable receiving here on my network in Germany.
Possibly there is now another header item used which is nit known to fMMS?
Could you grep through your sub dirs and find a message that was retrieved correctly to see the MMS version?
Blaiming/contacting operator support to tell them to send you only in 1.0 specification? (not really a successful approach

)

About the other question, no idea. It is more than a year that I was successfully fixing fMMS (after a year of total darkness).

Quote & Reply |

The Following 2 Users Say Thank You to peterleinchen For This Useful Post:
Wikiwide, xes

xes	2015-07-03 , 22:51
Posts: 638 \| Thanked: 1,692 times \| Joined on Aug 2009	#1004

At the moment seems a little bit hard to debug since the mms is impossible to download again and original raw message was overwritten during the following downloads...to debug the issue, add a timestamp to the message file would be better instead using .bak

So, until now i may suppose that first download went fine but decode failed forcing fmms to try again and again the download overwriting original raw message.

Concerning MMS-1.3, in october 2013 i received an mms of the same version without errors.

Quote & Reply |

The Following User Says Thank You to xes For This Useful Post:
Wikiwide

Ilew	2015-07-03 , 22:54
Posts: 75 \| Thanked: 269 times \| Joined on Aug 2012	#1005

Originally Posted by peterleinchen

okay
I think this could be the culprit.
fMMS was created using 1.0. I added one addigtonal header item of 1.2 spec to enable receiving here on my network in Germany.
Possibly there is now another header item used which is nit known to fMMS?

Check the Header Field Names and Assigned section (7.3 for 1.1 & 1.2) (7.4 for 1.3)
1.3 -
http://technical.openmobilealliance....20080128-C.pdf
1.2 -
http://www.miniware.net/mobile/docs/...20050301-A.pdf
1.1 -
http://www.openmms.org/download/OMA-WAP-MMS.pdf

1.3 added the following headers

Code:

0x34 : 'X-Mms-Recommended-RetrievalMode'
0x35 : 'X-Mms-Recommended-RetrievalMode-Text'
0x36 : 'X-Mms-Status-Text'
0x37 : 'X-Mms-Applic-ID'
0x38 : 'X-Mms-Reply-Applic-ID'
0x39 : 'X-Mms-Aux-Applic-Info'
0x3A : 'X-Mms-Content-Class'
0x3B : 'X-Mms-DRM-Content'
0x3C : 'X-Mms-Adaptation-Allowed'
0x3D : 'X-Mms-Replace-ID'
0x3E : 'X-Mms-Cancel-ID'
0x3F : 'X-Mms-Cancel-Status'

and the following are missing from FMMS:

Code:

0x1A : 'X-Mms-Retrieve-Text'
0x1B : 'X-Mms-Read-Status'
0x1C : 'X-Mms-Reply-Charging'
0x1D : 'X-Mms-Reply-Charging-Deadline'
0x1E : 'X-Mms-Reply-Charging-ID'
0x1F : 'X-Mms-Reply-Charging-Size'
0x20 : 'X-Mms-Previously-Sent-By'
0x21 : 'X-Mms-Previously-Sent-Date'
0x22 : 'X-Mms-Store'
0x23 : 'X-Mms-MM-State'
0x24 : 'X-Mms-MM-Flags'
0x25 : 'X-Mms-Store-Status'
0x26 : 'X-Mms-Store-Status-Text'
0x27 : 'X-Mms-Stored'
0x28 : 'X-Mms-Attributes'
0x29 : 'X-Mms-Totals'
0x2A : 'X-Mms-Mbox-Totals'
0x2B : 'X-Mms-Quotas'
0x2C : 'X-Mms-Mbox-Quotas'
0x2D : 'X-Mms-Message-Count'
0x2E : 'Content'
0x2F : 'X-Mms-Start'
0x30 : 'Additional-headers'
0x31 : 'X-Mms-Distribution-Indicator'
0x32 : 'X-Mms-Element-Descriptor'
0x33 : 'X-Mms-Limit'
0x34 : 'X-Mms-Recommended-RetrievalMode'
0x35 : 'X-Mms-Recommended-RetrievalMode-Text'
0x36 : 'X-Mms-Status-Text'
0x37 : 'X-Mms-Applic-ID'
0x38 : 'X-Mms-Reply-Applic-ID'
0x39 : 'X-Mms-Aux-Applic-Info'
0x3A : 'X-Mms-Content-Class'
0x3B : 'X-Mms-DRM-Content'
0x3C : 'X-Mms-Adaptation-Allowed'
0x3D : 'X-Mms-Replace-ID'
0x3E : 'X-Mms-Cancel-ID'
0x3F : 'X-Mms-Cancel-Status'

Quote & Reply |

The Following 7 Users Say Thank You to Ilew For This Useful Post:
freemangordon, misiak, nokiabot, peterleinchen, Swordfish II, Wikiwide, xes

	peterleinchen	2015-07-04 , 19:13
	Posts: 4,117 \| Thanked: 8,901 times \| Joined on Aug 2010 @ Ruhrgebiet, Germany	#1006

@xes
I am using that ".bak" as this is the original first downloaded message (always, as it does not get overwritten if there is already a bak file).
It will not get overwritten (never) but only deleted after successful decoding:

Code:

		os.system("if [ ! -f /home/user/.fmms/mms/" + trans_id + "/message.bak ]; then cp /home/user/.fmms/mms/" + trans_id + "/message /home/user/.fmms/mms/" + trans_id + "/message.bak; fi")
		message = self.decode_binary_mms(path)
		os.system("if [ -f /home/user/.fmms/mms/" + trans_id + "/message.bak ]; then diff /home/user/.fmms/mms/" + trans_id + "/message /home/user/.fmms/mms/" + trans_id + "/message.bak; if [ \"$?\" == \"0\" ]; then rm /home/user/.fmms/mms/" + trans_id + "/message.bak; fi; fi")

So when you say it is 'overwritten', only thing I can think of is:
the message is download
a confirmation is sent (so server deletes)
decoding takes place perfectly (as you see the contents in subdir)
but then in store_mms_message something goes wild

That would explain your contents, the deleted bak file, the new bak file with the "empty-already-deleted message from server".

I have atm no idea what goes wrong but check status of database file /home/user/.fmms/mms.db
It is sqlite format. Possibly read-only or some other rights problem? (e.g. started fmms from terminal as root?)

I hope you can debug that and provide patch or solution.
Did you check the /tmp/fmms.log for "Something went wrong when inserting"?

Possible approach for you to start:
change controller.py
from

Code:

		os.system("if [ ! -f /home/user/.fmms/mms/" + trans_id + "/message.bak ]; then cp /home/user/.fmms/mms/" + trans_id + "/message /home/user/.fmms/mms/" + trans_id + "/message.bak; fi")
		message = self.decode_binary_mms(path)
		os.system("if [ -f /home/user/.fmms/mms/" + trans_id + "/message.bak ]; then diff /home/user/.fmms/mms/" + trans_id + "/message /home/user/.fmms/mms/" + trans_id + "/message.bak; if [ \"$?\" == \"0\" ]; then rm /home/user/.fmms/mms/" + trans_id + "/message.bak; fi; fi")
		log.info("storing mms...%s", trans_id)
		mmsid = self.store_mms_message(pushid, message)

Code:

		os.system("if [ ! -f /home/user/.fmms/mms/" + trans_id + "/message.bak ]; then cp /home/user/.fmms/mms/" + trans_id + "/message /home/user/.fmms/mms/" + trans_id + "/message.bak; fi")
		message = self.decode_binary_mms(path)
		log.info("storing mms...%s", trans_id)
		mmsid = self.store_mms_message(pushid, message)
		os.system("if [ -f /home/user/.fmms/mms/" + trans_id + "/message.bak ]; then diff /home/user/.fmms/mms/" + trans_id + "/message /home/user/.fmms/mms/" + trans_id + "/message.bak; if [ \"$?\" == \"0\" ]; then rm /home/user/.fmms/mms/" + trans_id + "/message.bak; fi; fi")

That way the first downloaded original raw message should not get deleted.

--edit
regarding the MMS version: it does not matter which version number they put in there, as long as they are not using header fields other than v1.0 ( as Ilew pointed out). So that is not the culprit.

Quote & Reply |

The Following 2 Users Say Thank You to peterleinchen For This Useful Post:
Wikiwide, xes

Swordfish II	2015-07-04 , 21:00
Posts: 68 \| Thanked: 113 times \| Joined on Sep 2014	#1007

Man....MMS is the one thing holding me back from still using the N900

. I would even pay/ join a fund to have someone build or update mms on the N900

Quote & Reply |

The Following 2 Users Say Thank You to Swordfish II For This Useful Post:
peterleinchen, Wikiwide

	peterleinchen	2015-07-05 , 21:56
	Posts: 4,117 \| Thanked: 8,901 times \| Joined on Aug 2010 @ Ruhrgebiet, Germany	#1008

@Swordfish II
do you still have other issues beside that strange 'home-network-receiving-works-but-not-in-roaming-network'?

@xes
if my above assumptions are right I have one (clueless) idea what might go wrong. Could you send me output of 'ls -l /home/user/.fmms/mms' via PM? (PM as I have no idea what kind of private data you might give with that)

Quote & Reply |

The Following 2 Users Say Thank You to peterleinchen For This Useful Post:
Wikiwide, xes

Swordfish II	2015-07-12 , 02:33
Posts: 68 \| Thanked: 113 times \| Joined on Sep 2014	#1009

Yep, sending doesn't work at all on tmobile

Quote & Reply |

	peterleinchen	2015-07-12 , 14:05
	Posts: 4,117 \| Thanked: 8,901 times \| Joined on Aug 2010 @ Ruhrgebiet, Germany	#1010

Originally Posted by Swordfish II

Yep, sending doesn't work at all on tmobile

Oh!

And I thought this was your problem?

You cannot send at all?

Could you please try to run fmms from console (as user)
python /opt/fmms/fmms_gui.py
create a new (simple text) MMS and send me the out put in terminal. As well as the file /tmp/fmms.log?
And also the content of the newest folder (ls -el /home/user/.fmms/sent) from /home/user/.fmms/sent.

It could be your provider switched to MMS version > 1.0?
And refuses messages with version number == 1.0. It sounds absurd to me, as this will (and does) lock out a lot of devices. But hey, it is t-mobile! (similar happened to me here in germany for receiving, my provider uses now 1.1 and that specific header. Could be the reason why my wife's phone, a 6310, does not receive MMS anymore, too)
That should not be the case, as the versions are backward compatible. But being asked, I see this as most probable cause.
I will later attach two files, where I push up to 1.2 (not latest 1.3).
Just backup original ones under /opt/fmms/mms/message.py and mms_pdu.py, replace with attached (of course as root) and restart fmms.

Attached Files