@frals: Apologies for not reading the entire thread, over 1500 posts and 150 pages is a tad too long (yes, I'm lazy :P).

I had fMMS up and running perfectly with fAPN for over two months. Since mms isn't something I usually use, I just kept fMMS up-to-date (btw, congrats on all the work you've put into it). I didn't have any problems sending or receiving before, when the mms apn connection had to be established manually. Receiving, especially, was a breeze.

After the last updates, and reading about the new connection modes, I decided to give it another go. After the 12 or 13 update the mms apn disappeared from the list, and the apn settings inside fMMS were gone, so I decided to follow an advice by another user and copy the newer operator_settings version from the SDK to my N900, uninstalled fAPN and rebooted the phone. After rebooting, fMMS "detected" and displayed the correct mms settings for my operator.

I'm assuming it is intentional (again, didn't read the whole thread) that when you choose Havoc mode, the MMS APN disappears from the connections list and those settings are only "stored" in fMMS. Going from Havoc to Rude or Polite, recreates the MMS APN on the connections list. Correct?

1st Issue for me: when I started having problems sending mms's I naturally switched from Havoc to the other two modes to see if I could make it work. In the process of doing this, I noticed that when fMMS recreates the APN in the connections list, regardless of whether the settings include a proxy or not, the corresponding checkbox for "Use Proxy" in the Connections Settings dialog (the one provided by the OS itself) is never enabled. The value for proxy and port are stored there, at first, but since it's not enabled, I'd wager the connection doesn't work.

Now, and again I'm assuming this is intentional, when on Polite or Rude, fMMS reads the APN configuration as stored in the OS connections list. Since this was created with the proxy checkbox unchecked, as soon as you switch out of Havoc, fMMS's internal settings for proxy go blank. Placing a check on that box results in fMMS obtaining all the settings correctly. Sorry for all this, but I didn't see it reported in the last few pages.

Sending woes: since I can't reproduce my testing for yesterday, I decided to start fresh today.

First test send on Rude failed with no discernable error message.

First test send on Polite was successful, but app crashed or closed shortly after (apparently, immediately after I manually closed the mms apn connection -- gave it a good few seconds between getting the "message sent" dialog and closing it). Log file shows some errors.

Follow-up to the above: can't get the app to receive said mms (sent it to myself). Push-for-mms came shortly after fMMS crashed, pressed it and fMMS opened without issue. Clicked on received message, get no error dialog, app just keeps on "working" (ie, get that "still processing/working" animation at the top). Doesn't crash, though, pressing to close closes app immediately (yesterday the app was hard crashing on me).

Another note.. Somehow between failing to send with Rude and sending successfully but not being able to receive with Polite, the dreaded Use Proxy checkbox got unset again.. Does fMMS recreate the APN even if you're switching between Polite and Rude?

Second attempt to send through Polite worked, again, log file seems to get less errors -- but this time I didn't close the APN at all (though there was a period there where it was "crossed out"). Reception was flawless this time. Tried receiving the other mms that had failed, asked me to disconnect current connection (odd, it was the MMS APN), clicked Yes, took a little longer than the other one, but eventually retrieved my mms.

I'm attaching a zip file with the logfiles.. I know it keeps incrementing, and that's what they are, but I wanted to be able to identify, through filename, what I was trying to do in the hopes it'll save you some time wading through the info (download here).

(didn't test Havoc as it's harder to see what's going on)

One last thing, no idea if it's related to fMMS or not: since the last few updates and the issues, I routinely unlock my N900 to find an open dialog for "Select Connection" -- something I've never had happen to me aside from using the Maps app (when it tries to get A-GPS data).

Feature request: (I know I'm pushing it, but hey, doesn't hurt to ask ) Something like File Manager has for deleting files on fMMS's main dialog. Ie, something that allows me to mark multiple messages for deletion at once, as opposed to deleting each one by one (testing in particular creates a lot of fluff).