Active Topics
-
The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 12 hrs, 54 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 9 hrs ago - more...
 |
pr0xyfl00d3r |
2010-01-26
, 10:09
|
|
Posts: 93 |
Thanked: 22 times |
Joined on Oct 2009
@ Gainsborough, uk
|
#501
|
when i start fmms the program windows opens then after about 5-10secs the program quits.... can anyone help ..
|
|
2010-01-26
, 10:12
|
|
Posts: 547 |
Thanked: 1,383 times |
Joined on Sep 2009
@ Stockholm, Sweden
|
#502
|
Originally Posted by pr0xyfl00d3r
Run /opt/fmms/fmms_gui.py from the terminal and report back with any errors, thank you!
when i start fmms the program windows opens then after about 5-10secs the program quits.... can anyone help ..
__________________
Problem with fMMS? Run in x-terminal: cp /tmp/fmms.log /home/user/MyDocs/
After that you'll see fmms.log in filemanager or when you connect the device to your desktop as a mass storage device.
E-mail the log to me, if you don't have the email address, drop me a PM. Thanks!
fMMS - MMS for your N900
fAPN - GUI for adding a new GPRS APN
If you like this post, don't be shy to thank me -->
Problem with fMMS? Run in x-terminal: cp /tmp/fmms.log /home/user/MyDocs/
After that you'll see fmms.log in filemanager or when you connect the device to your desktop as a mass storage device.
E-mail the log to me, if you don't have the email address, drop me a PM. Thanks!
fMMS - MMS for your N900
fAPN - GUI for adding a new GPRS APN
If you like this post, don't be shy to thank me -->
|
|
2010-01-26
, 11:28
|
|
Posts: 143 |
Thanked: 4 times |
Joined on Jan 2010
|
#503
|
[QUOTE=frals;490538]You might want to edit out your numbers from that 
Anyway, seems like you are not allowed to send MMS through the specified MMSC, so (most likely) its either A) Wrong settings or B) you are not allowed to send MMS for your carrier
guess wat. strangest thing.... am able to send out now. here is the log
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso26+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.
~ $ /opt/fmms/fmms_sender_ui.py
/opt/fmms/fmms_sender_ui.py:174: GtkWarning: Invalid icon size 0
ret = fcd.run()
/opt/fmms/fmms_sender_ui.py:174: Warning: IA__g_object_get_valist: object class `HildonFileSystemSettings' has no property named `hour24'
ret = fcd.run()
/opt/fmms/fmms_sender_ui.py:317: Warning: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed
gtk.main()
/opt/fmms/fmms_sender_ui.py:317: Warning: g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed
gtk.main()
/opt/fmms/fmms_sender_ui.py:317: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
gtk.main()
/media/mmc1/DCIM/20100124_002.jpg
300
True
height 1936
width 2576
resizing
Resizing image: 300 * 225
/home/user/.fmms/temp/20100124_002.jpg Test
GOT SENDER:
customMMS: None
connecting via proxy 203.92.128.160:80
mmschost: http://mms.digi.com.my/servlets/mms
MMSC STATUS: 200 OK
MMSC RESPONDED: ���79359������Msg received successfully�mrmzolop21h9r41500@mms.digi.com.my
Removing temporary image...
Anyway, seems like you are not allowed to send MMS through the specified MMSC, so (most likely) its either A) Wrong settings or B) you are not allowed to send MMS for your carrier
guess wat. strangest thing.... am able to send out now. here is the log
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso26+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.
~ $ /opt/fmms/fmms_sender_ui.py
/opt/fmms/fmms_sender_ui.py:174: GtkWarning: Invalid icon size 0
ret = fcd.run()
/opt/fmms/fmms_sender_ui.py:174: Warning: IA__g_object_get_valist: object class `HildonFileSystemSettings' has no property named `hour24'
ret = fcd.run()
/opt/fmms/fmms_sender_ui.py:317: Warning: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed
gtk.main()
/opt/fmms/fmms_sender_ui.py:317: Warning: g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed
gtk.main()
/opt/fmms/fmms_sender_ui.py:317: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
gtk.main()
/media/mmc1/DCIM/20100124_002.jpg
300
True
height 1936
width 2576
resizing
Resizing image: 300 * 225
/home/user/.fmms/temp/20100124_002.jpg Test
GOT SENDER:
customMMS: None
connecting via proxy 203.92.128.160:80
mmschost: http://mms.digi.com.my/servlets/mms
MMSC STATUS: 200 OK
MMSC RESPONDED: ���79359������Msg received successfully�mrmzolop21h9r41500@mms.digi.com.my
Removing temporary image...
|
|
2010-01-26
, 12:10
|
|
Posts: 5 |
Thanked: 0 times |
Joined on Jan 2010
|
#504
|
Originally Posted by frals
You are a genious... between this and fAPN, its a perfect solution.
Yeah - I should make that more clear - added to todo list for the next version. It takes the name of an existing APN and gets the proxy settings from it
Yes, if you are confident in using the terminal and entering a bunch of mysterious potentially dangerous commands they are listed at https://bugs.maemo.org/show_bug.cgi?id=5791#c16
All I need is video calls and DTMF in voip would be nice... but I can live without.
|
|
2010-01-26
, 12:26
|
|
Posts: 93 |
Thanked: 22 times |
Joined on Oct 2009
@ Gainsborough, uk
|
#505
|
Originally Posted by frals
/home/user # /opt/fmms/fmms_gui.py
Run /opt/fmms/fmms_gui.py from the terminal and report back with any errors, thank you!
process 3129: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5757.
This is normally a bug in some application using the D-Bus library.
process 3129: arguments to dbus_connection_set_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5721.
This is normally a bug in some application using the D-Bus library.
Aborted
this is wot came bk cheers
|
|
2010-01-26
, 13:00
|
|
Posts: 547 |
Thanked: 1,383 times |
Joined on Sep 2009
@ Stockholm, Sweden
|
#506
|
Originally Posted by pr0xyfl00d3r
Run as user not root
/home/user # /opt/fmms/fmms_gui.py
process 3129: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5757.
This is normally a bug in some application using the D-Bus library.
process 3129: arguments to dbus_connection_set_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5721.
This is normally a bug in some application using the D-Bus library.
Aborted
this is wot came bk cheers
__________________
Problem with fMMS? Run in x-terminal: cp /tmp/fmms.log /home/user/MyDocs/
After that you'll see fmms.log in filemanager or when you connect the device to your desktop as a mass storage device.
E-mail the log to me, if you don't have the email address, drop me a PM. Thanks!
fMMS - MMS for your N900
fAPN - GUI for adding a new GPRS APN
If you like this post, don't be shy to thank me -->
Problem with fMMS? Run in x-terminal: cp /tmp/fmms.log /home/user/MyDocs/
After that you'll see fmms.log in filemanager or when you connect the device to your desktop as a mass storage device.
E-mail the log to me, if you don't have the email address, drop me a PM. Thanks!
fMMS - MMS for your N900
fAPN - GUI for adding a new GPRS APN
If you like this post, don't be shy to thank me -->
| The Following User Says Thank You to frals For This Useful Post: | ||
|
|
2010-01-26
, 18:55
|
|
Posts: 93 |
Thanked: 22 times |
Joined on Oct 2009
@ Gainsborough, uk
|
#507
|
Originally Posted by frals
ok here it is as user
Run as user not root
$ /opt/fmms/fmms_gui.py
/etc/hildon/theme/gtk-2.0/gtkrc:1: Unable to locate image file in pixmap_path: "../images/LockSliderTop.png"
/etc/hildon/theme/gtk-2.0/gtkrc:1: Background image options specified without filename
/etc/hildon/theme/gtk-2.0/gtkrc:1: Unable to locate image file in pixmap_path: "../images/LockSliderBottom.png"
/etc/hildon/theme/gtk-2.0/gtkrc:1: Background image options specified without filename
/etc/hildon/theme/gtk-2.0/gtkrc:1: Unable to locate image file in pixmap_path: "../images/LockSliderThumbPortrait.png"
/etc/hildon/theme/gtk-2.0/gtkrc:1: Background image options specified without filename
Traceback (most recent call last):
File "/opt/fmms/fmms_gui.py", line 710, in <module>
app = fMMS_GUI()
File "/opt/fmms/fmms_gui.py", line 78, in __init__
self.add_buttons_liststore()
File "/opt/fmms/fmms_gui.py", line 324, in add_buttons_liststore
phototest = self.ch.get_photo_from_name(sendername, 64)
File "/home/opt/fmms/contacts.py", line 96, in get_photo_from_name
img = res[0].get_photo(imgsize)
IndexError: list index out of range
| The Following User Says Thank You to pr0xyfl00d3r For This Useful Post: | ||
|
|
2010-01-26
, 19:03
|
|
Posts: 2,829 |
Thanked: 1,459 times |
Joined on Dec 2009
@ Finland
|
#508
|
Originally Posted by skalogre
So why dont' you use directly email client?
I had no idea this was available for AT&T. Your post made me research it; lo and behold it is available. Now I can send email to my gf on AT&T without having to use fMMS.
 |
|
2010-01-26
, 19:16
|
|
Posts: 327 |
Thanked: 249 times |
Joined on Sep 2009
@ Λεμεσιανός, ρε!
|
#509
|
Originally Posted by slender
She has some Samsung featurephone so MMS is more appropriate (email client and internet connectivity are basic to near non-existent). Using the #######@mms.att.net means that the email gets diverted to her phone by AT&T as an immediate MMS
So why dont' you use directly email client?
.
|
|
2010-01-26
, 20:31
|
|
Posts: 2,829 |
Thanked: 1,459 times |
Joined on Dec 2009
@ Finland
|
#510
|
Originally Posted by skalogre
Oh. I misunderstood. I thought that you are sending emails to her with MMS messages.
She has some Samsung featurephone so MMS is more appropriate (email client and internet connectivity are basic to near non-existent). Using the #######@mms.att.net means that the email gets diverted to her phone by AT&T as an immediate MMS
 |
| Tags |
| application, community win, fmms, frals rocks, fralsvsnokia1-0, fremantle, maemo, maemo 5, mms, n900, python |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 14:25.