Active Topics
-
Maemo repository (9)
to Community by nokiafemboy - 6 hrs, 59 mins ago -
Error after installing Leste on sdcard (18)
to Maemo 7 / Leste by Maemish - 22 hrs, 23 mins ago -
Maemo 20th Anniversary (4)
to Brainstorm by teroyk - 2 days, 17 hrs ago -
Nokia Booklet 3G (RX-75) Drivers (64)
to Alternatives by teroyk - 2 days, 17 hrs ago -
Porting apps to Leste (46)
to Maemo 7 / Leste by teroyk - 4 days, 21 hrs ago - more...
| The Following User Says Thank You to flya320 For This Useful Post: | ||
|
2010-02-08
, 11:37
|
|
Posts: 515 |
Thanked: 266 times |
Joined on Nov 2009
@ Oelsted, Denmark
|
#12
|
Maybe I should give Funambol a go again... Guess I could use port forwarding (in SSH) to display the Java GUI on my laptop during setup... 
|
|
2010-02-08
, 12:55
|
|
Posts: 287 |
Thanked: 165 times |
Joined on Oct 2009
@ The Netherlands
|
#13
|
I tried Zarafa (great system) with z-push but ran into some issues. I had some exhaustive irc sessions with one of the developers and it seems that there are some bugs in the Mfe software from Nokia. There are (at least) three issues:
1) on an initial sync, the N900 creates a second connection during the sync where it tries to sync the exact same items as the first connection. So you end up with a lot of duplicates. An ugly patch in z-push can prevent that but has to be disabled after initial sync.
2) the N900 doesn't follow the Activesync specifications with timezones. Full day events are not synced correct. An ugly patch in z-push can help but not when you travel across timezones.
3) Some pictures from N900 contacts aren't synced so they are empty on Zarafa. On the next sync they are removed some N900 too. The N900 doesn't see the pictures when syncing. I checked that in the N900 synclog.
These issues are reported to Vitaly of Nokia.
So unfortunaty the combination of Zarafa with N900 doesn't work well in firmware 1.0 and 1.1. This is not a problem of Zarafa but the Mfe implementation of the N900. The Zarafa developer was really helpfull and spent a couple of hours debugging the syncing.
1) on an initial sync, the N900 creates a second connection during the sync where it tries to sync the exact same items as the first connection. So you end up with a lot of duplicates. An ugly patch in z-push can prevent that but has to be disabled after initial sync.
2) the N900 doesn't follow the Activesync specifications with timezones. Full day events are not synced correct. An ugly patch in z-push can help but not when you travel across timezones.
3) Some pictures from N900 contacts aren't synced so they are empty on Zarafa. On the next sync they are removed some N900 too. The N900 doesn't see the pictures when syncing. I checked that in the N900 synclog.
These issues are reported to Vitaly of Nokia.
So unfortunaty the combination of Zarafa with N900 doesn't work well in firmware 1.0 and 1.1. This is not a problem of Zarafa but the Mfe implementation of the N900. The Zarafa developer was really helpfull and spent a couple of hours debugging the syncing.
| The Following User Says Thank You to robbie For This Useful Post: | ||
|
|
2010-02-08
, 15:01
|
|
Posts: 9 |
Thanked: 4 times |
Joined on Feb 2010
|
#14
|
Originally Posted by DrWilken
I have not tried it yet, but the funamboladmin tool *should* work from another computer via network. This will be an issue in my setup, too, since the server where I would like to run funambol is a non X, non monitor, no nothing server ;-)
Maybe I should give Funambol a go again... Guess I could use port forwarding (in SSH) to display the Java GUI on my laptop during setup...
I will play a bit and report back...
Well, I just installed funamboladmin on my windoofs laptop, and it is smoothly possible to setup my test funambol server on my debian box via network ! This is looking more and mor promising here...
Last edited by flya320; 2010-02-08 at 15:09.
| The Following User Says Thank You to flya320 For This Useful Post: | ||
|
|
2010-02-08
, 15:08
|
|
Posts: 515 |
Thanked: 266 times |
Joined on Nov 2009
@ Oelsted, Denmark
|
#15
|
Originally Posted by flya320
Same goes for my server except it does have a nice little 7-8'ish " monitor...
I have not tried it yet, but the funamboladmin tool *should* work from another computer via network. This will be an issue in my setup, too, since the server where I would like to run funambol is a non X, non monitor, no nothing server ;-)
I will play a bit and report back...
|
|
2010-02-08
, 15:12
|
|
Posts: 9 |
Thanked: 4 times |
Joined on Feb 2010
|
#16
|
config via network works for funambol, see my edited earlier post!
|
|
2010-02-08
, 15:45
|
|
Posts: 9 |
Thanked: 4 times |
Joined on Feb 2010
|
#17
|
In case someone is interested in setting up a funambol server on a linux box, some notes, what I did:
download funambol:
http://download.forge.objectweb.org/...mbol-8.0.2.bin
as root:
chmod +x funambol-8.0.2.bin
./funambol-8.0.2.bin
accept the license, install to somewere you like, /opt seems fine to me
do not start the server yet.
My suggestion here is to run the server as a dedicated user, so add a group funambol and a user funambol:
groupadd -g [some GID free you like] funambol
useradd -c 'Funambol Server User' -d /var/empty -g funambol -s /bin/bash -u [some free UID] funambol
chown -R funambol.funambol /opt/Funambol
change to user funambol:
su - funambol
and start the bugger:
/opt/Funambol/bin/funambol start
check with your browser:
http://localhost:8080/funambol/
if the server is responding.
you also can use the browser of another machine, substiuting localhost with the ip of the funambol server
Now with a user having access to a running X server, you can start the admin tool:
/opt/Funambol/admin/bin/funamboladmin
if nothing happens, try again with the user which you used for login on that box.
Now, create a testuser with the admintool and install syncevolution on n900:
install syncevolution via extras-devel repo on the n900, then open a console on n900
and configure like described here:
http://wiki.maemo.org/Sync#funambol
then try to sync with
syncevolution funambol
this worked for me quite nicely. Now I have to find out, how to get funambol to work on my real server... lets see
Hope, this helps someone. In case something does not work as I said, I wrote this from memory, so there might be mistakes... tell me, I will try to correct this little HOWTO...
download funambol:
http://download.forge.objectweb.org/...mbol-8.0.2.bin
as root:
chmod +x funambol-8.0.2.bin
./funambol-8.0.2.bin
accept the license, install to somewere you like, /opt seems fine to me
do not start the server yet.
My suggestion here is to run the server as a dedicated user, so add a group funambol and a user funambol:
groupadd -g [some GID free you like] funambol
useradd -c 'Funambol Server User' -d /var/empty -g funambol -s /bin/bash -u [some free UID] funambol
chown -R funambol.funambol /opt/Funambol
change to user funambol:
su - funambol
and start the bugger:
/opt/Funambol/bin/funambol start
check with your browser:
http://localhost:8080/funambol/
if the server is responding.
you also can use the browser of another machine, substiuting localhost with the ip of the funambol server
Now with a user having access to a running X server, you can start the admin tool:
/opt/Funambol/admin/bin/funamboladmin
if nothing happens, try again with the user which you used for login on that box.
Now, create a testuser with the admintool and install syncevolution on n900:
install syncevolution via extras-devel repo on the n900, then open a console on n900
and configure like described here:
http://wiki.maemo.org/Sync#funambol
then try to sync with
syncevolution funambol
this worked for me quite nicely. Now I have to find out, how to get funambol to work on my real server... lets see
Hope, this helps someone. In case something does not work as I said, I wrote this from memory, so there might be mistakes... tell me, I will try to correct this little HOWTO...
| The Following User Says Thank You to flya320 For This Useful Post: | ||
 |
|
2010-02-08
, 15:58
|
|
Posts: 320 |
Thanked: 763 times |
Joined on Oct 2009
@ Espoo, FInland
|
#18
|
1) on an initial sync, the N900 creates a second connection during the sync where it tries to sync the exact same items as the first connection. So you end up with a lot of duplicates. An ugly patch in z-push can prevent that but has to be disabled after initial sync.
2) the N900 doesn't follow the Activesync specifications with timezones. Full day events are not synced correct. An ugly patch in z-push can help but not when you travel across timezones.
3) Some pictures from N900 contacts aren't synced so they are empty on Zarafa. On the next sync they are removed some N900 too. The N900 doesn't see the pictures when syncing. I checked that in the N900 synclog.
|
|
2010-02-08
, 18:22
|
|
Posts: 515 |
Thanked: 266 times |
Joined on Nov 2009
@ Oelsted, Denmark
|
#19
|
Wow... Funambol has a ALOT of listening ports...!
I have to open up the ones I need (only for my LAN)... Any idea which ones are needed?
Port 5001 is ps3mediaserver, but the rest are Funambol AFAIK...
I have to open up the ones I need (only for my LAN)... Any idea which ones are needed?
Code:
mainframe scripts # netstat -pan --tcp | grep LISTEN | grep java tcp 0 0 0.0.0.0:56804 0.0.0.0:* LISTEN 13651/java tcp 0 0 127.0.0.1:8005 0.0.0.0:* LISTEN 13676/java tcp 0 0 127.0.0.1:37381 0.0.0.0:* LISTEN 13651/java tcp 0 0 0.0.0.0:4101 0.0.0.0:* LISTEN 13689/java tcp 0 0 0.0.0.0:8101 0.0.0.0:* LISTEN 13676/java tcp 0 0 127.0.0.1:48582 0.0.0.0:* LISTEN 13689/java tcp 0 0 127.0.0.1:48359 0.0.0.0:* LISTEN 13699/java tcp 0 0 0.0.0.0:8009 0.0.0.0:* LISTEN 13676/java tcp 0 0 0.0.0.0:4745 0.0.0.0:* LISTEN 13651/java tcp 0 0 10.13.20.1:5001 0.0.0.0:* LISTEN 10627/java tcp 0 0 0.0.0.0:40237 0.0.0.0:* LISTEN 13651/java tcp 0 0 0.0.0.0:45455 0.0.0.0:* LISTEN 13676/java tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 13676/java tcp 0 0 0.0.0.0:51762 0.0.0.0:* LISTEN 13689/java tcp 0 0 0.0.0.0:44436 0.0.0.0:* LISTEN 13699/java tcp 0 0 0.0.0.0:38581 0.0.0.0:* LISTEN 13689/java tcp 0 0 0.0.0.0:56950 0.0.0.0:* LISTEN 13699/java tcp 0 0 127.0.0.1:45335 0.0.0.0:* LISTEN 13651/java tcp 0 0 0.0.0.0:54586 0.0.0.0:* LISTEN 13676/java tcp 0 0 0.0.0.0:7101 0.0.0.0:* LISTEN 13651/java tcp 0 0 0.0.0.0:3101 0.0.0.0:* LISTEN 13699/java tcp6 0 0 :::9001 :::* LISTEN 13646/java
|
|
2010-02-08
, 21:16
|
|
Posts: 287 |
Thanked: 165 times |
Joined on Oct 2009
@ The Netherlands
|
#20
|
Originally Posted by vitaly_repin
Well, i'm sorry if i offended you. Maybe it's Zarafa or the z-push component.
Not correct. The N900 establishes connection to the server. Waits 90 seconds to receive a response. If the response is not received in this amount of time, the connection is dropped and new request to the server is sent. As no response from the server was received for the previous sync attempt, no dupe appears.
All i know is what i see in the Zarafa logs and that is that it is still adding items to the (Zarafa) calendar while i get a new connection from my N900. So for one reason, the N900 thinks it isn't connected but it is sending calendar items anyway. And after the second connect, Zarafa gets the same items as on the first connect. This only happens on initial sync. I have about 2200 old appointments that needs to be synced to the server.
So maybe z-push should send a message back earlier that it connected ok and that it is receiving items. I really don't know.
If you want, i can create some logs for you to investigate. I really hope this issue gets fixed and want to help where i can.
I understand that you received some information from Andreas from the z-push component on the timezone issue. If you want, i can provide you more info on that too.
I read that you fixed the jpeg issue in an internal build. Thats nice. Can't wait to test the new version
Thanks for replying on the issues.
the EAS Protocol setting didn't help with egroupware, since egroupware is synced with the symcML Protocol.
I also tried a go with funambol, which as of now syncs with the N900 successfully! I now have to figure out, if just funambol is enough for what I need, or if I use funambol as a link between the n900 and a groupware server. Some work ahead!