Notices

Nice but I dont need MMS

Any help on this?

Gosh, I really wish romanianusa would setup fMMS, because I have an MMS I'm just dying to send him.

Oh well, I guess I'll just have to wait till Maemo 6.

Seems the package importer is dead, the .deb-file is available on garage for those who feel comfortable installing it that way.

Regarding full conversations integration: It's deffo something I *want* to do, but it's a long way off still I'm afraid

@daperl: lol, haven't seen goatse in a long time

Why the addressbook is not working ? when pushing "TO:" it's not open addressbook.

Are you running 0.1.10?

I just update the new version.

Start fMMS -> click the "app menu" (where it says fMMS) -> click about, does it say 0.1.10 or 0.1.9?

I'm not sure how common it is, but for O2 in the UK the APN string (wap.o2.co.uk and mobile.o2.co.uk .. ignoring iphone and other weird extra ones), all tend to work fine.

In fact I found rtsp udp/tcp streaming worked better with wap despite a few years ago, being filtered horrifically (couldn't even do ssh (tcp port 22). So I switched to it as my main apn even for ssh/web.

The extra APN for MMS only had a proxy configured as the difference.

So my question is. Would it be possible to have fMMS not use a system proxy via network configuration settings, requiring us to have extra/alternate network configurations, but instead to accept a proxy setting from us, then dial up using the details for the mobile provider network connection (whether already connected via wifi with a default gateway or not) and then set a host specific route to the proxy with the gprs0 interface and send the data out via that proxy.

This should mean you can be online already, be it wifi or 3G and when you try to send an MMS it just magically works even if you're on 3G without a proxy configured for the normal OS/browser.

As for receiving, well I certainly didn't need to have a network connection open on my older phones, and on the n900 I disconnect to save battery. There presumably is some magic mobile provider low level signal, like an SMS which makes the phone decide it needs to connect up and collect? The 1.1 firmward mentions MMS API additions, perhaps this is exactly what it'll help with?

Basically all this "connect secretly in the background while connected" isn't really something that should be done (since it may break stuff horribly), and confuse the ICD - but yes, I'm looking into doing it, but I suspect it's *a lot* of work, and really, is manually changing connection when getting the MMS such a major inconvience atm?

Regarding you only having a proxy on the MMS APN and not on the regular one, if you just fill in the field on your regular connection and then uncheck the box you should be able to use that connection to get MMS as fMMS doesn't currently respect the value of "use-proxy" or not, it only looks for a proxy configured and uses it

Yes, the "magic low level signal" is the SMS Push, which shows up as a notification on your N900 - after this fmmsd tries to connect to the MMS APN to fetch it, otherwise it fails and you can get it manually from fMMS GUI when connected to the MMS APN.

The "wappushd-dev" package contains the header files I've been using all along, so sorry, no new breakthroughs


Bottom line is, the ICD in the N900/fremantle doesn't currently allow more than one connection at a time which is the problem here, setting one up without ICDs knowledge seems to be possible but is really ugly and may confuse the hell out of current connections.