Re: GTA02 Setting time from phone network using NITZ ?
On 09/22/2012 10:26 AM, Adam Ward wrote: According to http://www.scribd.com/doc/30428306/54/AT-CTZU-Automatic-Time-Zone-Update I should be able to chat to the modem to get some information. But the following command does not return anything: root@neo:~# chat -vse '' 'AT+CTZU=?' '' '' /dev/ttySAC0 /dev/ttySAC0 send (AT+CTZU=?^M) send (^M) This is a gsm fw bug. I was not able to get time from operator, vodafone CZ supports this, but not calypso. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Shr-Devel] About the future of the freesmartphone.org middleware
On Sun, 23 Sep 2012 07:58:18 AM Radek Polak wrote: On Saturday, September 22, 2012 10:44:54 PM Neil Jerram wrote: Ah, thanks, I understand your question now: what version of fsogsmd does QtMoko build with, and isn't that now rather out of date? But I'm afraid I don't know the answers. I was using FSO from git at the time when i was implementing FSO backend. I am quite sure FSO from wheezy will work unless FSO api changed. However for now it makes no sence to use any dbus modem middleware as default. QtMoko's modem library is very stable and works IMO very good. I dont see any benefits in using FSO or oFono right now. But still if you want to use FSO or oFono the support is in every QtMoko installation - just change export QTOPIA_PHONE=oFono or export QTOPIA_PHONE=Fso in /opt/qtmoko/qpe.env and QtMoko will use the dbus backend for telephony. Regards Radek This is getting off topic now :) I came into this discussion because I want to check the version of the gsm firmware, to see if it needs to be upgraded. The wiki has a page on doing this via FSO with dbus [1]. Is there a different method available ? The reason I wanted to do this is to see if there is a bug dealing with NITZ that may have been resolved, but I am not sure at what level in the stack it is. According to [2] the AT+CTZU command is supported. To do this I need to talk to the modem, but nothing is being returned ? I have tried chat [3] and cu [4] without success. Trying cu, I typed AT and get no response. Is this a Calypso firmware bug as described by Alex [5] ? [1] http://wiki.openmoko.org/wiki/GSM/Flashing [2] http://wiki.openmoko.org/wiki/Hardware:AT_Commands [3] http://lists.openmoko.org/pipermail/community/2012-September/067496.html [4] http://wiki.openmoko.org/wiki/Neo_1973_and_Neo_FreeRunner_gsm_modem [5] http://lists.openmoko.org/pipermail/community/2012-September/067509.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Hi Neil, Radek However, I think that point is not far above the raw SMTP level, so I wonder if it would help to enable SMTP logging and see what that shows? To do that, go into Home, Settings, Logging; choose YES twice; then choose Categories... from the context menu, and check SMTP; then back all the way out. (You don't need to restart QtMoko, despite what it says.) Then repro the sending error. Then go back into Logging and see what it says. Ok - have tried this and I think I have some useful information. 1) Firstly - attempting TLS connection to my own mail server. The neo connects, sees the certificate and that it is self signed and backs off. That's almost fair enough, but not what I want. Desktop email clients give the option to accept the certificate anyway, either temporarily or permanently and that would be more useful behaviour. Incidentally this is *not* the problem I believe to be a regression, when I was using earlier versions I never tried to use my own mail server - at the time I didn't have it set up to authenticate, rather just to relay only from my home ip - not much use with the phone, hence historically why I used the fastmail smtp service. 2) On to trying the fastmail server; first using SSL - once again this is *not* what I used to do, so not what I'm reporting as a regression:- Encrypted connect warnings: 'The issuer certificate of a locally looked up certificate could not be found', 'The root CA certificate is not trusted for this purpose' Sep 23 13:38:19 neo Qtopia: SMTP : Closed connection Sep 23 13:38:19 neo Qtopia: socketError: 13 : The issuer certificate of a locally looked up certificate could not be found It does seem to be erroneous behaviour though, the remote server not being involved at all? 3) Finally I attempt unencrypted access to the fastmail server - this is what definitely works in v35 (I tried it just a few days ago):- Sep 23 13:47:09 neo Qtopia: SMTP : newConnection Sep 23 13:47:09 neo Qtopia: SMTP : Open SMTP connection Sep 23 13:47:09 neo Qtopia: socketError: 0 : Connection refused Sep 23 13:47:09 neo Qtopia: SMTP : Closed connection I'd be most interested in a work around to get 1) working if it's possible, but seems to me to be 3 seperate problems in this one area Bets wishes -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
dmatthews.org m...@dmatthews.org writes: 3) Finally I attempt unencrypted access to the fastmail server - this is what definitely works in v35 (I tried it just a few days ago):- Sep 23 13:47:09 neo Qtopia: SMTP : newConnection Sep 23 13:47:09 neo Qtopia: SMTP : Open SMTP connection Sep 23 13:47:09 neo Qtopia: socketError: 0 : Connection refused Sep 23 13:47:09 neo Qtopia: SMTP : Closed connection Regarding (3), I notice that https://www.fastmail.fm/help/remote_email_access_server_names_and_ports.html says that the right port number is 465, and here's what happens when I try to connect to ports 25 and 465: neil@neil-laptop:~$ telnet mail.messagingengine.com 25 Trying 66.111.4.52... Trying 66.111.4.51... telnet: Unable to connect to remote host: Connection refused neil@neil-laptop:~$ telnet mail.messagingengine.com 465 Trying 66.111.4.51... Connected to mail.messagingengine.com. Escape character is '^]'. ^C^C Connection closed by foreign host. neil@neil-laptop:~$ So perhaps the Connection refused you get is caused by QtMoko incorrectly using port 25? Did you set port 465 in the account configuration for sending? Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
