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

oldnetdog | # 261 | 2010-05-29, 13:44 | Report

I am using PR1.2, since FMMS v1.0.8(even v1.1.1), I noticed that after i sent a MMS, i can't list all the MMS messages (sent or received) of inbox, the fmms statusbar always in the waiting/entering/starting? status.

I check the fmms.log, here is the log tail:

Code:

2010-05-29 21:21:31,823 fmms.fmms_viewer: filetype: text/plain
2010-05-29 21:21:31,828 fmms.fmms_viewer: filetype: image/jpeg
2010-05-29 21:21:31,850 fmms.fmms_viewer: filetype: image/jpeg
2010-05-29 21:21:31,867 fmms.fmms_viewer: filetype: text/plain
2010-05-29 21:21:31,870 fmms.fmms_viewer: filetype: text/plain
2010-05-29 21:21:31,873 fmms.fmms_viewer: filetype: text/plain
2010-05-29 21:21:31,876 fmms.fmms_viewer: filetype: text/plain
2010-05-29 21:21:31,878 fmms.fmms_viewer: filetype: image/jpeg
2010-05-29 21:21:31,895 fmms.fmms_viewer: filetype: text/plain
2010-05-29 21:23:24,518 fmms.contacts: loaded contacthandler in 0.06 s

If I removed fmms cache dir /home/user/.fmms using this command:

rm -fr /home/user/.fmms

surely, all the MMS sent or received was removed, the inbox can show now, but after i sent a MMS again, the inbox can't be list again.

FMMS version 1.0.7 and before did't have the problem.

Last edited by oldnetdog; 2010-05-29 at 13:51.

Astute | # 262 | 2010-05-29, 13:46 | Report

Originally Posted by frals View Post

No delivery notifications on MMS yet.

@duryard: Attach log file or email me the log. Thank you for reading the first post!

Not a major issue for me so just an enquiry. But if you manage to ge notificaions on at some point...good man. To date you've done some stirling work indeed, Nokia owe you bigtime i'd suggest.

frals | # 263 | 2010-05-29, 14:07 | Report

Originally Posted by oldnetdog View Post

I am using PR1.2, since FMMS v1.0.8(even v1.1.1), I noticed that after i sent a MMS, i can't list all the MMS messages (sent or received) of inbox, the fmms statusbar always in the waiting/entering/starting? status.

I check the fmms.log, here is the log tail:

Code:

2010-05-29 21:21:31,823 fmms.fmms_viewer: filetype: text/plain
2010-05-29 21:21:31,828 fmms.fmms_viewer: filetype: image/jpeg
2010-05-29 21:21:31,850 fmms.fmms_viewer: filetype: image/jpeg
2010-05-29 21:21:31,867 fmms.fmms_viewer: filetype: text/plain
2010-05-29 21:21:31,870 fmms.fmms_viewer: filetype: text/plain
2010-05-29 21:21:31,873 fmms.fmms_viewer: filetype: text/plain
2010-05-29 21:21:31,876 fmms.fmms_viewer: filetype: text/plain
2010-05-29 21:21:31,878 fmms.fmms_viewer: filetype: image/jpeg
2010-05-29 21:21:31,895 fmms.fmms_viewer: filetype: text/plain
2010-05-29 21:23:24,518 fmms.contacts: loaded contacthandler in 0.06 s

If I removed fmms cache dir /home/user/.fmms using this command:

rm -fr /home/user/.fmms

surely, all the MMS sent or received was removed, the inbox can show now, but after i sent a MMS again, the inbox can't be list again.

FMMS version 1.0.7 and before did't have the problem.

Open fMMS from the terminal by entering:
/opt/fmms/fmms_gui.py and paste any output you get after trying to view a message here please

The Following User Says Thank You to frals For This Useful Post:
oldnetdog

oldnetdog | # 264 | 2010-05-29, 14:20 | Report

Originally Posted by frals View Post

Open fMMS from the terminal by entering:
/opt/fmms/fmms_gui.py and paste any output you get after trying to view a message here please

v1.0.7, just tap the icon to start FMMS, i can list all the MMS of inbox, but entering /opt/fmms/fmms_gui.py to start FMMS, i can't list any the MMS of inbox, here is the output:

Code:

Nokia-N900:~# /opt/fmms/fmms_gui.py 
Traceback (most recent call last):
  File "/opt/fmms/fmms_gui.py", line 181, in cb_on_focus
    self.add_buttons_liststore()
  File "/opt/fmms/fmms_gui.py", line 280, in add_buttons_liststore
    senderuid = self.ch.get_uid_from_number(sender)
  File "/opt/fmms/contacts.py", line 82, in get_uid_from_number
    raise TypeError("Could not open ebook")
TypeError: Could not open ebook
Traceback (most recent call last):
  File "/opt/fmms/fmms_gui.py", line 181, in cb_on_focus
    self.add_buttons_liststore()
  File "/opt/fmms/fmms_gui.py", line 280, in add_buttons_liststore
    senderuid = self.ch.get_uid_from_number(sender)
  File "/opt/fmms/contacts.py", line 82, in get_uid_from_number
    raise TypeError("Could not open ebook")
TypeError: Could not open ebook

v1.1.1, neither tap the icon nor entering /opt/fmms/fmms_gui.py to start FMMS, , i CAN'T list any the MMS of inbox, here is the output:

Code:

Nokia-N900:/home/user/MyDocs/deb# /opt/fmms/fmms_gui.py 
Traceback (most recent call last):
  File "/opt/fmms/fmms_gui.py", line 182, in cb_on_focus
    self.add_buttons_liststore()
  File "/opt/fmms/fmms_gui.py", line 281, in add_buttons_liststore
    senderuid = self.ch.get_uid_from_number(sender)
  File "/opt/fmms/contacts.py", line 85, in get_uid_from_number
    raise TypeError("Could not open ebook")
TypeError: Could not open ebook

thanks.

Last edited by oldnetdog; 2010-05-29 at 14:23.

frals | # 265 | 2010-05-29, 14:23 | Report

Start it as user not root

The Following User Says Thank You to frals For This Useful Post:
oldnetdog

oldnetdog | # 266 | 2010-05-29, 14:25 | Report

Originally Posted by frals View Post

Start it as user not root

fMMS version 1.1.1:

Code:

Nokia-N900:/home/user/MyDocs/deb# su - user


BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ /opt/fmms/fmms_gui.py
Traceback (most recent call last):
  File "/opt/fmms/fmms_gui.py", line 182, in cb_on_focus
    self.add_buttons_liststore()
  File "/opt/fmms/fmms_gui.py", line 315, in add_buttons_liststore
    description = description.encode('utf-8', 'ignore')
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 9-11: invalid data

fMMS v1.0.7:

Code:

Nokia-N900:/home/user/MyDocs/deb# su - user


BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ /opt/fmms/fmms_gui.py

v1.0.7 seems fine.

Last edited by oldnetdog; 2010-05-29 at 14:29.

The Following User Says Thank You to oldnetdog For This Useful Post:
frals

frals | # 267 | 2010-05-29, 14:33 | Report

Originally Posted by oldnetdog View Post

fMMS version 1.1.1:

Code:

Nokia-N900:/home/user/MyDocs/deb# su - user


BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ /opt/fmms/fmms_gui.py
Traceback (most recent call last):
  File "/opt/fmms/fmms_gui.py", line 182, in cb_on_focus
    self.add_buttons_liststore()
  File "/opt/fmms/fmms_gui.py", line 315, in add_buttons_liststore
    description = description.encode('utf-8', 'ignore')
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 9-11: invalid data

Ah, thanks! I accidently changed that, will fix it in the next version. Thanks for reporting!

EDIT: Workaround is to edit fmms_gui.py
description = description.encode('utf-8', 'ignore')
to
description = description.decode('utf-8', 'ignore')

(I think)

The Following User Says Thank You to frals For This Useful Post:
oldnetdog

oldnetdog | # 268 | 2010-05-29, 14:41 | Report

Originally Posted by frals View Post

Ah, thanks! I accidently changed that, will fix it in the next version. Thanks for reporting!

EDIT: Workaround is to edit fmms_gui.py
description = description.encode('utf-8', 'ignore')
to
description = description.decode('utf-8', 'ignore')

(I think)

The workaround works with v1.1.1, and when i successfully open a MMS, i still found following warning log, i have no idea what impact it is.

Code:

~ $ /opt/fmms/fmms_gui.py
/usr/lib/python2.5/sre_parse.py:180: Warning: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed
  self.width = int(min(lo, sys.maxint)), int(min(hi, sys.maxint))
/usr/lib/python2.5/sre_parse.py:180: Warning: g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed
  self.width = int(min(lo, sys.maxint)), int(min(hi, sys.maxint))
~ $

The Following User Says Thank You to oldnetdog For This Useful Post:
frals

frals | # 269 | 2010-05-29, 14:51 | Report

Warnings can be ignored as long as everything seems to work ;-)

The Following User Says Thank You to frals For This Useful Post:
oldnetdog

sed8me | # 270 | 2010-05-29, 16:05 | Report

Originally Posted by frals View Post

Upgrade to 1.0.2 and try setting "Your phonenumber" to 0 and see if this helps please

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~

I've debugged this with another 3 Australia user and my suggestion is you give 3 a call and tell them MMS is not working on your phone and ask them to please enable it for you. Please let me know what they say and if it helps (google for 3 australia mms and there is a lot of similar problems on custom android roms from what I've gathered).

If you delete it, fMMS will stop working I'm afraid. If 'Havoc' mode works for you, the APN is hidden from the UI so you won't be bothered by it.

FRALS you are indeed amazing

I am On the Australian Vodafone network, and since I have been testing tis app, I can Recieve from any other network, but can only send to vodafone, I have even confirmed the apn settings with voda techs...

I re flashed with pr1.2 and installed hoping for auto configuration, this yielded a random carrier being set up ( soz i didnt take note )
**EDIT**
Crazy John's
* Connection Type: Packet Data
* Connection Name: Purtona.wap
* Access Point Name: Purtona.net
was the auto populated connection. *** ~~ this apn did not work ~~

I deleted all data via the command lines you posted and entered vodafone AU manually...

I am running FMMS 1.1.0 now and still the same error.

Does entering phone number as Zero work ?
I cannot see a place to enter this in 1.1.0

My sim can send mms to any carrier in my N95 and oldskool 7610 and when these access points are analyzed, the same information is present as per apn configuration.

I dont know if it helps, but when talking to some pretty high up tech support ppl at vodafone AU, we completely removed my phone from the system and re provisioned it. when I sent a test mms to myself, the phone came up as a N95 on their system.
(phone identifies to sim, sim relays info to telco)

I am more than happy to help in any way, in so far as testing and relaying info is concerned

~lol~

Thanx SO much for the work U have done for the community.

Last edited by sed8me; 2010-05-29 at 16:44.