Re: [Announce] fMMS - MMS on the N900
 

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.

Re: [Announce] fMMS - MMS on the N900
 

@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?"

Re: [Announce] fMMS - MMS on the N900
 

okay

going to check tomorrow


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

Re: [Announce] fMMS - MMS on the N900
 

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.

Re: [Announce] fMMS - MMS on the N900
 

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
and the following are missing from FMMS:

Re: [Announce] fMMS - MMS on the N900
 

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

Re: [Announce] fMMS - MMS on the N900
 

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

Re: [Announce] fMMS - MMS on the N900
 

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

Re: [Announce] fMMS - MMS on the N900
 

Yep, sending doesn't work at all on tmobile

Re: [Announce] fMMS - MMS on the N900
 

Oh! :eek:
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.