N900: Full fMMS Walkthrough (20 min!) – Send & Receive MMS [Updated: 18/04/2010]

Update: The latest and final one stop shop for all your questions regarding fMMS can now be found at my new blog (thetekblogger.com), the post can be found here: http://thetekblogger.com/2010/05/27/fmms-1-x-for-nokia-n900-f-a-q/
Please direct any questions to the comments section on the above post

Hey all, it’s LLAADD again and this time I have for you a wopper of a video for your viewing pleasure!

Some of you may have seen my video back in January about fMMS, with a quick brief of how to use it, etc (if not see here: http://wp.me/p73J2-1mQ), but since then I have had quite a few comments and questions on that post and on YouTube about how to do specific things which I didn’t properly cover last time. As well as that in the last couple of months, the developer of fMMS (frals), has been working very very very hard and bought out some very nice updates so I thought this would be the perfect time to make a new video and this time make sure that I cover as much as I can.

I actually recorded the video a few days ago but because of the type of camera I’m using I had to do a lot of editing so have only just completed it, and as such, when I recorded it, the version available was 0.6.1, but the next day, the developer decided to add a couple of minor tweaks (see below) and also give it a version bump to 0.7.2 (So far).

Note: With version 0.7.2 and the latest 0.9.0 I was able to successfully send and receive a message in “havoc” mode, and also pictures with width 2048 without any issue!

Clarification about havoc mode from frals (the developer of fMMS):

It won’t physically break your phone, however – if it fails and the user keeps trying to send/get MMS with havoc enabled and it fails again – it might result in the modem not setting up any new GPRS connections until you reboot the device… Basically as of 0.7.2 this shouldn’t really happen unless someone really tries to break it, but it *might*.

For the record I’ve been running Havoc mode for ~2 months and not yet managed to break it

[dailymotion id=xcyvss]

(Uploaded onto DailyMotion as YouTube won’t let me submit one over 10 min)

Recent Updates

Version 0.6.1 (07/04/2010) now allows option to choose how the application manages connections to send and receive an MMS:

Polite (Default behavior <0.6): Only switch to MMS connection if no connection is active, otherwise do nothing (pretty much)

Rude: Force a disconnect of the active connection regardless of what it is, connect to MMS APN and then reconnect to the old one.

Havoc: Try to bring up a connection to the MMS APN in parallell with whatever is active, this is what most other phones do. Note that to get this functionality on the N900 there are a few ugly hacks active which might break stuff, but it *should* work 😉

Version 0.6.2 (09/04/2010):

viewer can now show messages even though ‘From’ header is missing

screenshot for showing while application is loading is now taken after each listview refresh

more logging to connectors

fixed bug where application would not launch after successfully sending a message

Version 0.6.3 (10/04/2010) a.k.a ZOMG CONTACTS ARE WORKING:

contacts should now match against any number in the phonebook

not redrawing listview all the time, should give a smoother experience

removed some duplicated code in viewer

added copyright notice to source files

moved the configuration dialog to its own class

Version 0.7.0 (10/04/2010) a.k.a. “It was time for a version bump anyway”:

Fixed installation of fmms_config_dialog

Viewer ‘to’ button now brings up a libosso-abook widget (aka normal contacts list view)

Version 0.7.1 (15/04/2010):

composer ‘to’ button works when launched via sharing service

looked up names/avatars are cached for better listview draw time

havoc connector now works with APN requiring user/pass

glist implemenation slightly less broken

user-agent configurable via gconf-key /apps/fmms/useragent

Version 0.7.2 (15/04/2010):

fixed wappushhandler to disconnect when bailing out of __get_mms

fixed fmms_magic so it should actually work properly now

delete in controller now defaults to mmsdir/pushdir if lookup in db fails

Version 0.9.0 (18/04/2010) aka “Getting really close now…”:

• redid configuration for apn
• automatically fetches operator settings from /etc/operator_settings if available
• border around interaction area in sender
• ‘forward’ option added in viewer
• only stores sent messages if mmsc responds it was successfully submitted
• fixed some issues where dbhandler would break when concatting strings
• delete function now uses os.listdir to get the list of files
• message time is converted to localtime when fetched from db
• sane defaults on first launch

Short FAQ (from frals)

Problem: “Name or service unknown”/”No route to host”/”Connection refused” or similar when sending
Solution: Make sure you are connected to the MMS APN  – if you still get the error, try pinging the mmsc host from the terminal. If it still fails, double check your connection settings. If your provider list a “MMS Proxy” or “MMS Gateway”, input this in the HTTP Proxy settings for the connection

DON’T FORGET TO SET THE PROXY IN INTERNET CONNECTIONS

Useful Links

Before Installing, please read: http://talk.maemo.org/showpost.php?p=343619&postcount=1

Developer’s Site: http://mms.frals.se

Maemo Forum: http://talk.maemo.org/showthread.php?t=39737

Wiki (with more network settings, etc): http://wiki.maemo.org/MMS

UPDATE: Application is out of beta so no longer requires the development catalogue.

Application Library’s

You will need to add the Extra’s Development and Extra’s Testing library’s to be able to download and install the fAPN and fMMS applications.

I would recommend that you disable BOTH of these library’s after you have installed fAPN and fMMS as many people have completely bricked their phones by installing applications from here, and a few day’s ago I joined them, it took me a long time to get my N900 back to life and I was lucky that I was able to but I lost everything from my phone (So do a backup of the phone and the Mass Memory before you start)….

YOU HAVE BEEN WARNED!

Maemo Extra Testing

Catalogue Name: maemo.org extras testing
Web Address: http://repository.maemo.org/extras-testing/
Distribution: fremantle
Components: free non-free

Maemo Extra Development

Catalogue Name: maemo.org extras devel
Web Address: http://repository.maemo.org/extras-devel/
Distribution: fremantle
Components: free non-free

Main Settings

When Required use the following settings regardless of which provider you are with or which country you are in

• Resize image: 300 (You can try higher – I found 500 work ok) Latest update has 4 preset modes: Small, medium, large and original (note: original does not work for a lot of people)
• Phone Number: (Your phone number in international format i.e. +447000000000)
• Connection Mode: Rude (you can try havoc but if things stop working, backup your device to a removable memory card and then restart your device) Havoc mode should be safe to use.

Network Specific Settings

The settings for some of the UK providers are below and some more for providers in other countries can be found in the official wiki here: http://wiki.maemo.org/MMS

o2 UK (Contract)

• Connection Name: O2 MMS
• Connection Type: GPRS (also works with Packet Data)
• Access Point Name: wap.o2.co.uk
• User Name: o2wap
• Password: password
• Prompt password at every login: No
• Use Proxy: Yes
• HTTP Proxy: 193.113.200.195
• Port Number: 8080
• MMSC: http://mmsc.mms.o2.co.uk:8002

o2 UK (Pay and go)

• Connection Name: O2 MMS
• Connection Type: GPRS (also works with Packet Data)
• Access Point Name: payandgo.o2.co.uk
• User Name: payandgo
• Password: password
• Prompt password at every login: No
• Use Proxy: Yes
• HTTP Proxy: 193.113.200.195
• Port Number: 8080
• MMSC: http://mmsc.mms.o2.co.uk:8002

Orange UK

• Connection Name: Orange MMS
• Connection Type: GPRS
• Access Point Name: orangemms
• User Name: (leave blank)
• Password: (leave blank)
• Prompt password at every login: No
• Use Proxy: Yes
• HTTP Proxy: 192.168.224.10
• Port Number: 8080
• MMSC: http://mms.orange.co.uk

T-Mobile UK

• Connection Name: T-Mobile MMS
• Connection Type: GPRS
• Access Point Name: general.t-mobile.uk
• User Name: user
• Password: pass
• Prompt password at every login: No
• Use Proxy: Yes
• HTTP Proxy: 149.254.201.135
• Port Number: 8080
• MMSC: http://mmsc.t-mobile.co.uk:8002

Vodafone UK

• Connection Name: Vodafone MMS
• Connection Type: Packet Data
• Access Point Name: wap.vodafone.co.uk
• User Name: wap
• Password: user
• Prompt password at every login: No
• Use Proxy: Yes
• HTTP Proxy: 212.183.137.12
• Port Number: 8799
• MMSC: http://mms.vodafone.co.uk/servlets/mms

Three UK

• Connection Name: Three MMS
• Connection Type: Packet Data
• Access Point Name: mms.three.co.uk
• User Name: (leave blank)
• Password: (leave blank)
• Prompt password at every login: No
• Use Proxy: Yes
• HTTP Proxy: 217.171.129.2
• Port Number: 8799
• MMSC: http://mms.um.three.co.uk:10021/mmsc

Virgin UK

Note: Virgin must enable MMS for your account. Contact Virgin Customer Services

• Connection Name: Virgin MMS
• Connection Type: Packet Data
• Access Point Name: goto.virginmobile.uk
• User Name: user
• Password: (leave blank)
• Prompt password at every login: No
• Use Proxy: Yes
• HTTP Proxy: 193.030.166.001
• Port Number: 8080
• MMSC: http://mms.virginmobile.co.uk:8002

Tesco Mobile UK

• Connection Name: Three MMS
• Connection Type: Packet Data
• Access Point Name: prepay.tesco-mobile.com
• User Name: tescowap
• Password: password
• Prompt password at every login: No
• Use Proxy: Yes
• HTTP Proxy: 193.113.200.195
• Port Number: 8080
• MMSC:http://mmsc.mms.o2.co.uk:8002

BT Mobile UK

• Connection Name: BT Mobile MMS
• Connection Type: Packet Data
• Access Point Name: mobile.bt.uk
• User Name: user
• Password: btmms
• Prompt password at every login: No
• Use Proxy: Yes
• HTTP Proxy: 212.183.137.012 or 62.239.21.123
• Port Number: 8799
• MMSC: http://mms.bt.com/servlets/mms or http://mmsc.btmms.co.uk:8002

ASDA Mobile UK

• Connection Name: ASDA Mobile MMS
• Connection Type: Packet Data
• Access Point Name: asdamobiles.co.uk
• User Name: wap
• Password: wap
• Prompt password at every login: No
• Use Proxy: Yes
• HTTP Proxy: 212.183.137.12
• Port Number: 8799
• MMSC: http://mms.asdamobiles.co.uk/servlets/mms

Category: Nokia