The Following User Says Thank You to sbock For This Useful Post: | ||
|
2010-04-20
, 23:16
|
|
Posts: 1,455 |
Thanked: 3,309 times |
Joined on Dec 2009
@ Rochester, NY
|
#1382
|
0.9.6 aka "The config dialog redesign seemed like a good idea..." released. Hopefully that god forsaken dialog is now fixed, for real.
The Following User Says Thank You to woody14619 For This Useful Post: | ||
|
2010-04-20
, 23:26
|
Posts: 547 |
Thanked: 1,383 times |
Joined on Sep 2009
@ Stockholm, Sweden
|
#1383
|
Hate to tell you this, but I also can't save proxy port with this version either. Keeps coming up blank. I ran the gconftool command you noted and it saved and worked fine after that. So, the work around works, but the config dialog is still busted.
I also had a launch issue after the initial update. I was one of those that took the advice to link the ~/.fmms/mms folder into MyDocs, so I could access the files from MMS on the shared folder. Turns out that breaks fMMS in this version if you did that. The error I was getting by running the command line in xterm was something along the lines of "mkdir(): directory already exists". I'm betting you're checking for if it's a directory, and finding it's a link, and trying to do a mkdir. Once I unlinked and moved it back it launched fine.
I also noted that when I first configed it made a new MMS access point, which breaks things for me a little. Since the settings are 100% identical to my existing connection, I have two identical cell APNs. This means if I try to run Havoc mode, even if I'm already connected to my normal APN, it spins up another connection (grps2) to use for the mms. This seems to not work and causes it to not work in Havoc mode on my device (Rude mode works ok though). Maybe you should check for that (existing APN = MMS APN) and not set one up in that case?
The Following 2 Users Say Thank You to frals For This Useful Post: | ||
|
2010-04-21
, 00:34
|
|
Posts: 1,455 |
Thanked: 3,309 times |
Joined on Dec 2009
@ Rochester, NY
|
#1384
|
Embarassing, forgot to updated the code before building package so it was built with same code as 0.9.5...
I have the same configuration here but fMMS just keeps going and fetches the MMS just fine. Could you email me your log?
|
2010-04-21
, 01:28
|
Posts: 10 |
Thanked: 0 times |
Joined on Jun 2007
|
#1385
|
|
2010-04-21
, 01:31
|
Posts: 14 |
Thanked: 4 times |
Joined on Oct 2009
|
#1386
|
|
2010-04-21
, 02:12
|
Posts: 143 |
Thanked: 4 times |
Joined on Jan 2010
|
#1387
|
|
2010-04-21
, 03:37
|
Posts: 446 |
Thanked: 79 times |
Joined on Mar 2010
|
#1388
|
|
2010-04-21
, 03:59
|
|
Posts: 1,312 |
Thanked: 736 times |
Joined on Sep 2009
|
#1389
|
k, this may seem crazy but i just did the update for maemo 5 fw and now i can not find fmms with the app manager or transmission. any ideas on this anyone?
The Following User Says Thank You to somedude For This Useful Post: | ||
|
2010-04-21
, 04:44
|
Posts: 36 |
Thanked: 12 times |
Joined on Apr 2010
|
#1390
|
Tags |
application, community win, fmms, frals rocks, fralsvsnokia1-0, fremantle, maemo, maemo 5, mms, n900, python |
Thread Tools | |
|
I found a possible other bug fiddling with fmms opening over the console:
The MMS and the address are correctly shown in the viewer. But in the overview address, description and date are wrong (from a different MMS)
Last edited by sbock; 2010-04-20 at 22:31.