Re: QtMoko v48 neofreerunner
dmatthews.org m...@dmatthews.org writes: I gave this another go after reading Robin's report of success and (embarassed face) I managed to send an email using the fastmail smtp service That's good news. No idea what was different; all I can think is I hit on some permutation I didn't try before - I am using different encryption type and authentication methods. Apologies to Neil if I diverted much energy away from something more productive, I'm trying to find a palatable hat (to eat) Hey, not at all! I think I learned some useful stuff, about both encryption and QtMoko, while looking into things. Also, amusingly, my own email has now _stopped_ working for no apparent reason. Apparently there's a fundamental physical law of conservation of non-working email :-). (I'm hoping it'll come back to life again as soon as I can have a successful QtMoko build again...) Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
As a side note. When i select TLS, i'm not sure it's being saved. If i recall correctly, the qtopiamail config file just said I believe it does get saved - you have to watch out when you edit via the gui, the encryption setting for IMAP does not get loaded from the file, so you have to set that each time. encryption type = 2, whatever that means. When i edit account information it just shows up blank. When i select SSL, and save, then edit account info, the form appears with SSL picked. ah - I think this is what I described above - maybe it is just a TLS setting the gui does not load from file. i download Firefox and it comes with n cert signing certificates, how do i know they are secure? But i digress. You digress, but indeed the whole cert signing business by large corporate bodies sucks. -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
hi, just as it was mentioned in this thread before I can confirm that with the web.de server which stores my mail only certain combinations of the login worked to give me the option to actually send my message (I think it took me about 20mins to figure out which ones...) br robin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Hi Brian GTA04 over wifi, connecting to my IMAP server with TLS. Thunderbird on my laptop works, and Mutt on the gta04 works, but qtopiamail doesn't. I get this error message: new Qtopia: socketError: 13 : Error during SSL handshake: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure My misadventures with this have left me perplexed; I don't really understand why it works now after so very may fails - and this against the earlier experience of it never having caused a second thought on v35 for instance. I conclude that is a generic error message that doesn't really point to the problem and I *think* in my case the fix must have been to select the appropriate login method. I believe desktop clients do that automatically ( at least sylpheed does) so I'd no prior reason to engage with this issue. I do think that the lack of ca-certificates was part of the problem. I probably confused things by trying against 3 different smtp servers - maybe each one needs a different method setting and I previously failed to hit on a winning combo. If you like, I can post a copy of my qtopiamail.conf, which works with a fastmail smtp account. Regards -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Dave and all, If qtopiamail uses libssl, we should brace ourselves for crappy error messages :) I forgot to mention that my IMAP server uses a certificate signed by cacert.org. The signing certificate cert is in the ca-certificates package. I verified the certificate using a command like openssl verify -cafile /etc/ssl/certs/ca-certificates.crt my-imap-cert.pem. I did that on my imap server. I should try again on the freerunner. I can dive into some source code. Can someone point me to some directions on getting a qtmoko environment set up to compile packages? If qtmoko follows normal debian conventions, i should be able to diagnose some stuff. As a side note. When i select TLS, i'm not sure it's being saved. If i recall correctly, the qtopiamail config file just said encryption type = 2, whatever that means. When i edit account information it just shows up blank. When i select SSL, and save, then edit account info, the form appears with SSL picked. The lack of ca-certificates package may be intentional. After all, how do we know it is securely delivered to us. On the other hand, if i download Firefox and it comes with n cert signing certificates, how do i know they are secure? But i digress. I haven't tried SMTP yet, but when i do, i'll post results here. Brian -- Brian DeRocher http://brian.derocher.org http://mappingdc.org http://about.me/brian.derocher ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
On Wednesday, October 31, 2012 03:58:33 AM Brian DeRocher wrote: I can dive into some source code. Can someone point me to some directions on getting a qtmoko environment set up to compile packages? If qtmoko follows normal debian conventions, i should be able to diagnose some stuff. Hi, the build instructions are in README file on github repo: https://github.com/radekp/qtmoko/blob/master/README Currently i am working on upgrading to latest Qt so you might have to try checkout v48 tag instead of master. It would be easiest to build just qtopiamail - e.g. create QtCreator project for it, but unfortunately qtopiamail is quite big and tight to rest of QtMoko, so it's not easy to separate it like that. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Neil, I wanted to share my email issues, even if they are semi-related to this thread. On 10/24/2012 08:05 AM, Neil Jerram wrote: It would be good to have some more data points. Can anyone else report success/failure with QtMoko v48 email, on - Freerunner - GTA04 on 2G-only (the default) - GTA04 on 3G (requires patching to change AT_OPSYS=0,2 to AT_OPSYS=3,2) GTA04 over wifi, connecting to my IMAP server with TLS. Thunderbird on my laptop works, and Mutt on the gta04 works, but qtopiamail doesn't. I get this error message: new Qtopia: socketError: 13 : Error during SSL handshake: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure I've install ca-certificates, but that doesn't help. Brian -- Brian DeRocher http://brian.derocher.org http://mappingdc.org http://about.me/brian.derocher ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
I gave this another go after reading Robin's report of success and (embarassed face) I managed to send an email using the fastmail smtp service No idea what was different; all I can think is I hit on some permutation I didn't try before - I am using different encryption type and authentication methods. Apologies to Neil if I diverted much energy away from something more productive, I'm trying to find a palatable hat (to eat) -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Hi Boudewijn From memory the config file is /home/root/Trolltech/qtopiamail.conf - something like that any way. The issue I have is not with imap - which works fine, rather with sending mail - I have no GTAO4, so this is on a freerunner. I beleive Neil does not have the problem on the GTAO4 - so you should be good on that, it would be more interesting to hear how you got on with th neo. Regards -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
this is qtmoko v48, freerunner, email via encrypted WPA wifi: imap acount (imap.web.de) with port 993 and encryption ssl and smtp (smtp.web.de) with port 25 and encryption none + auth = plain Retrieving is straight forward. sending somehow only works if I go to the message in my outbox and then press send message again. otherwise it wont leave the phone. br robin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
the message in my outbox and then press send message again. otherwise it wont leave the phone. Interesting - it sounds like you've been a bit more persistent than me - at least tangentially. I do believe I've always given up at the first fail - I'll give it another look. Would you agree the the sending procedure you describe was not necessary on earlier versions? -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
I haven't tried earlier versions so I have no idea if there is a change in how the mail program behaves. all in all I am not using it that often as it is quite cumbersome to use. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
David Matthews m...@dmatthews.org writes: You say that you can't duplicate the issue - by that do you mean you *can* send email from a freerunner on qtmoko v48? - I had the impression you were more involved on the GTA04 and may not have a freerunner any longer. FYI I was running my GTA04 on 2G-only yesterday and found that email didn't work properly for me - whereas normally I'm on 3G, and email works fine. I didn't investigate the details very closely, but perhaps this is a clue - i.e. that the email problem you see with v48 on Freerunner is to do with the low 2G data rate. It would be good to have some more data points. Can anyone else report success/failure with QtMoko v48 email, on - Freerunner - GTA04 on 2G-only (the default) - GTA04 on 3G (requires patching to change AT_OPSYS=0,2 to AT_OPSYS=3,2) ? Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
I didn't investigate the details very closely, but perhaps this is a clue - i.e. that the email problem you see with v48 on Freerunner is to do with the low 2G data rate. Neil, nope. all the testing I did was using my home adsl either by wifi or routing through the desktop machine over usb However on earlier versions (ie up to v35 at least) it definitely worked over 2G as well for me. It would be good to have some more data points. Can anyone else report success/failure with QtMoko v48 email, on - Freerunner - GTA04 on 2G-only (the default) - GTA04 on 3G (requires patching to change AT_OPSYS=0,2 Yes :-) I'd particularly like to hear if other neo users have found the same as me. -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
David Matthews m...@dmatthews.org writes: I didn't investigate the details very closely, but perhaps this is a clue - i.e. that the email problem you see with v48 on Freerunner is to do with the low 2G data rate. Neil, nope. all the testing I did was using my home adsl either by wifi or routing through the desktop machine over usb Ah, OK, thanks for eliminating that possibility. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
On Wednesday 24 October 2012 14:21:23 David Matthews wrote: It would be good to have some more data points. Can anyone else report success/failure with QtMoko v48 email, on - Freerunner - GTA04 on 2G-only (the default) - GTA04 on 3G (requires patching to change AT_OPSYS=0,2 Yes :-) I'd particularly like to hear if other neo users have found the same as me. I was also wondering, but hadn't found the mail application till now. Thanks to you two persevering, I got mail on my phone now. Thanks :-) Setting up the account was straightforward thanks to all fields having labels that say clear enough what they mean. I first started the initial get folder structure before realizing I had no connection whatsoever. I canceled that, connected some-G network and started initial download. It seems to work immediately: after a couple of seconds the directory structure was copied, and the first headers came in. After a couple of minutes it is at some 800 message headers. I actually have no idea which generation of network I'm using at the moment. The network-cell-status got a GSM- and a UMTS-cell code. Energy usage is at switching between 25mA and 96-to-104mA. Is the location of the config file mentioned in the thread? I searched the file system, found some configs that got mail in it, but nothing that resembles an account configuration. Or are those settings in some database file? I tested with an xs4all.nl-account, imap on port 993, with SSL. I'll give Yahoo a try later, so we can exchange settings for a service that's available to all of us (Yahoo Asia includes IMAP, as opposed to default Yahoo, in case you're about to try). Time allowing I'll install QtMoko 48 on my Freerunner to give that a run as well. Best regards, Boudewijn signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Boudewijn wankelwan...@yahoo.com writes: On Wednesday 24 October 2012 14:21:23 David Matthews wrote: It would be good to have some more data points. Can anyone else report success/failure with QtMoko v48 email, on - Freerunner - GTA04 on 2G-only (the default) - GTA04 on 3G (requires patching to change AT_OPSYS=0,2 Yes :-) I'd particularly like to hear if other neo users have found the same as me. I was also wondering, but hadn't found the mail application till now. Thanks to you two persevering, I got mail on my phone now. Thanks :-) Setting up the account was straightforward thanks to all fields having labels that say clear enough what they mean. I first started the initial get folder structure before realizing I had no connection whatsoever. I canceled that, connected some-G network and started initial download. It seems to work immediately: after a couple of seconds the directory structure was copied, and the first headers came in. After a couple of minutes it is at some 800 message headers. I actually have no idea which generation of network I'm using at the moment. The network-cell-status got a GSM- and a UMTS-cell code. Energy usage is at switching between 25mA and 96-to-104mA. It sounds like the GSM/UMTS difference is a red herring anyway, but if you're on 2G (GSM) you'll have a G at the left hand side of your title bar, whereas with 3G (UMTS) you'll have a 3. Is the location of the config file mentioned in the thread? I searched the file system, found some configs that got mail in it, but nothing that resembles an account configuration. Or are those settings in some database file? It's at /home/root/Settings/Trolltech/qtopiamail.conf I tested with an xs4all.nl-account, imap on port 993, with SSL. I'll give Yahoo a try later, so we can exchange settings for a service that's available to all of us (Yahoo Asia includes IMAP, as opposed to default Yahoo, in case you're about to try). Time allowing I'll install QtMoko 48 on my Freerunner to give that a run as well. Thanks! Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
On Wednesday 24 October 2012 23:07:37 Neil Jerram wrote: Boudewijn wankelwan...@yahoo.com writes: On Wednesday 24 October 2012 14:21:23 David Matthews wrote: It would be good to have some more data points. Can anyone else report success/failure with QtMoko v48 email, on - Freerunner - GTA04 on 2G-only (the default) - GTA04 on 3G (requires patching to change AT_OPSYS=0,2 I actually have no idea which generation of network I'm using at the moment. The network-cell-status got a GSM- and a UMTS-cell code. Energy usage is at switching between 25mA and 96-to-104mA. Sorry any confusion: I thought those values to be too low for any charging taking place (as charging via USB often stops in my case). I thought it really low for an active connection as well, but I only found out after connecting it to a wall charger that energy usage was arount 500mA. It sounds like the GSM/UMTS difference is a red herring anyway, but if you're on 2G (GSM) you'll have a G at the left hand side of your title bar, whereas with 3G (UMTS) you'll have a 3. Too bad... Never saw a 3 there :-( I really start doubting my objectivity now: I thought to have a much faster internetexperience :-P Is the location of the config file mentioned in the thread? I searched the file system, found some configs that got mail in it, but nothing that resembles an account configuration. Or are those settings in some database file? It's at /home/root/Settings/Trolltech/qtopiamail.conf Ah, thanks: [account_5] accountname=k@xs autoDownload=true basefolder= checkinterval=-60 deletemail=false email=ma...@xs4all.nl intervalCheckRoamingEnabled=true mailEncryption=1 mailpasswordobs=DelkWEFed= mailport=993 mailserver=imap.xs4all.nl mailuser=maijoeser maxmailsize=20 name=Boudewijn networkConfig= pushEnabled=false smtpAuthentication=3 smtpEncryption=2 smtpPasswordObs= smtpUsername= smtpport=587 smtpserver=smtp.xs4all.nl synchronize=true type=1 usesig=true Best regards, Boudewijn signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Hi Neil Try next? To be honest I've given up - I'm only mentioning the issue on the basis someone might want to fix it. You say that you can't duplicate the issue - by that do you mean you *can* send email from a freerunner on qtmoko v48? - I had the impression you were more involved on the GTA04 and may not have a freerunner any longer. Do you for instance have an account at either fastmail or inbox.lv that works? If so please let me have the exact settings you use - the qtopiamail.conf file with your account details removed would be great - and I'll prepare to eat my hat. -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Prompted by David Matthews' reports, I've improved my understanding of SMTP authentication mechanisms. Little of this is specific to QtMoko or even smartphones, but I think it's worth covering anyway in the context of this thread. When you want to send email via an SMTP server that isn't in your own immediate network, the client needs to authenticate itself to the server. Otherwise that server would be an open relay, which is a big no-no. So the client (e.g. on your GTA0x) has to send something involving your ID and password to the server - and obviously that raises the questions of (1) whether the server is really the right server, and (2) whether something else can sniff the communication and work out your ID and password. The available SMTP auth mechanisms in QtMoko are LOGIN and PLAIN, and both of those are basically plaintext - i.e. anyone sniffing the communication can see your ID and password. Therefore you really need to be using encryption - either SSL or TLS - as well, for sending email from a QtMoko phone. (There is a non-plaintext SMTP auth mechanism, CRAM-MD5, but it appears that QtMoko does't support that.) TLS and SSL are largely the same. In this context (SMTP), the difference is that SSL encrypts the TCP connection before _any_ SMTP protocol is exchanged (and requires a distinct port number from unencrypted SMTP), whereas a TLS connection starts off unencrypted and becomes encrypted once both the client and the server have agreed that (and so can operate within the normal SMTP port 25). Crucially, in the TLS case, both the client and the server can ensure that they don't exchange any authentication information until the connection has become encrypted. There's still question (1), whether the server you're connecting to is really the server that you trust to know your ID/password and to see your outgoing email. SSL and TLS both address this by the server having a certificate that uniquely identifies itself. That certificate is passed to the client, as part of the process of the connection becoming encrypted, and the client must decide if it trusts that certificate. In QtMoko (and I think in general) this is done by the client having a pre-installed set of certificates that it trusts. Then, when the client sees the SMTP server's certificate, it must either exactly match one of the pre-installed ones, or have been signed by one of the pre-installed ones. Some certificate-handling applications, like Firefox, also allow the user to inspect an untrusted certificate and make it trusted, but QtMoko doesn't do that. Therefore... - If you're using a public SMTP server, that server's certificate should be signed by a recognised certificate authority (CA), and that CA's certificate should be pre-installed in your QtMoko. apt-get install ca-certificates does this. - If you're using your own SMTP server, you can: (a) create your own self-signed CA certificate (b) create a certificate for your SMTP server, signed by your CA certificate (c) configure your SMTP server to support TLS, using the newly created certificate (d) install your own CA certificate in QtMoko by copying it to /usr/local/share/ca-certificates/something.crt, running update-ca-certificates, and restarting QtMoko. In other words, you're telling your QtMoko to trust your own CA. There are good instructions for (a), (b) and (c) at http://www.postfix.org/TLS_README.html. There are probably other variants on the own SMTP server procedure described here, but this is what I've just successfully tested for my own SMTP setup. Now, with all that as background... dmatthews.org m...@dmatthews.org writes: Here's some more smtp debugging - I'm now using the mail.inbox.lv server which supports unencrypted and TLS access Trying port 587 with TLS:- Sep 24 20:01:37 neo Qtopia: 250-STARTTLS^M Sep 24 20:01:37 neo Qtopia: 250-AUTH LOGIN PLAIN^M Sep 24 20:01:37 neo Qtopia: 250-ENHANCEDSTATUSCODES^M Sep 24 20:01:37 neo Qtopia: 250-8BITMIME^M Sep 24 20:01:37 neo Qtopia: 250 DSN Sep 24 20:01:37 neo Qtopia: SMTP : StartTLS: sent: STARTTLS Sep 24 20:01:37 neo Qtopia: SMTP : response: 220 2.0.0 Ready to start TLS Sep 24 20:01:38 neo Qtopia: Encrypted connect warnings: 'The root certificate of the certificate chain is self-signed, and untrusted' Sep 24 20:01:38 neo Qtopia: SMTP : Closed connection Sep 24 20:01:38 neo Qtopia: socketError: 13 : The root certificate of the certificate chain is self-signed, and untrusted I think this means that the mail.inbox.lv server provided a self-signed certificate (or a chain of certificates rooted in a self-signed certificate), and that QtMoko doesn't have that certificate installed. If I run swaks -s mail.inbox.lv -t nos...@gmail.com -tls -a LOGIN from a laptop, with Wireshark running at the same time, I see that mail.inbox.lv provides a chain of 3 certificates, of which the root certificate looks similar to
Re: QtMoko v48 neofreerunner
dmatthews.org m...@dmatthews.org writes: Sep 24 20:26:18 neo Qtopia: SMTP : Auth: sent: AUTH LOGIN Sep 24 20:26:18 neo Qtopia: SMTP : response: 334 VXNlcm5hbWU6 Sep 24 20:26:18 neo Qtopia: SMTP : AuthUser: sent: ZG1hdHRoZXdzQGluYm94Lmx2 I notice (by decoding this) that you've configured your ID as dmatth...@inbox.lv. But http://help.inbox.lv/help/question/100/37 says: Inbox users must set an authorization to outgoing mail server. - In the next window “Account name” You must write in your username, for example, if your e-mail address is supp...@inbox.lv then Your “Account name” will be “support”. Could that be the problem? I.e. your ID should be just dmatthews? Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Hi Neal I pretty much agree with what you say When you want to send email via an SMTP server that isn't in your own immediate network, the client needs to authenticate itself to the server. Otherwise that server would be an open relay, which is a big but you neglected the option to allow relaying from a particular ip address. I've done that in the past and afaik it's quite satisfactory if you have a static ip address on your adsl line. And to specifics . -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Hi Neal - In the next window “Account name” You must write in your username, for example, if your e-mail address is supp...@inbox.lv then Your “Account name” will be “support”. Could that be the problem? I.e. your ID should be just dmatthews? No - although I'm pretty sure that is wrong; I tried dmatth...@inbox.lv in desperation after trying dmatthews. Since I'm hazy about the difference between PLAIN and LOGIN, I've basically tried every conceivable combination against 3 different SMTP servers. Everything fails on v48; on V35 I can definitely still use the fastmail SMTP service (at least), with minimal fiddling. The nub is that from v2x up to v35 - that's all it ever required - minimal fiddling at the most. I'm pretty sure this is not a PEBKAC - there's some change somtime since v35 that has introduced a problem :-) Best 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: The nub is that from v2x up to v35 - that's all it ever required - minimal fiddling at the most. I'm pretty sure this is not a PEBKAC - there's some change somtime since v35 that has introduced a problem :-) Fair enough. What would you like to try next? Since I can't reproduce any of these problems myself, I guess we can only proceed by trying things step by step on your FR; but that might be time-consuming. What do you think? Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
On Wed, 03 Oct 2012 00:07:32 +0100 Neil Jerram n...@ossau.homelinux.net wrote: Thanks - interesting thought, but it doesn't do the trick, although I suspect it was part of the problem - the errors no longer include moans about certifcates. Not sure if v35 included the ca-certificates - but I wasn't using TLS then anyway (to recap at that time I used unencrypted login against a different smtp server and that does not work in version 48) I tried every conceivable TLS setting against 2 servers, one of which is my own and that I know works with desktop email clients. here's a sample reject from the server:- 2012-10-03 17:55:41 TLS error on connection from [81.187.28.181] (recv): A TLS packet with unexpected length was received. 2012-10-03 17:55:41 TLS error on connection from [81.187.28.181] (send): The specified session has been invalidated for some reason. -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
On 10/1/12, Radek Polak pson...@seznam.cz wrote: On Sunday, September 30, 2012 05:21:43 PM Flemming Richter Mikkelsen wrote: I have big problems starting booting up proper. After finally attaching the debug cable, I noticed that the kernel is 3.4.0-gta04 but under /lib/modules/ there is only 2.6.34-qtmoko-v48. Do I need to first boot with 2.6.34 and then upgrade to the new kernel? It is strange that I didn't see any other reporting this problem. Have you downloaded the right tarball? The download url for GTA04 is http://sourceforge.net/projects/qtmoko/files/GTA04/ Thank you very much. I used the correct url, but clicked on the link on the top (for the lastest version) without noticing that the filename said it was for gta02. Sorry for the noise, and thank you for the help! Looking forward to finally test the correct image:) 2.6.34 is kernel for Freerunner (GTA02). So this looks like you have kernel for GTA04 and rootfs for GTA02. I have checked the qtmoko-debian-gta04-v48.tar.gz tarball and it looks all fine (3.5 kernel in boot, 3.5 modules in /var/lib) Regards Radek ___ 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: Here's some more smtp debugging - I'm now using the mail.inbox.lv server which supports unencrypted and TLS access Trying port 587 with TLS:- Sep 24 20:01:37 neo Qtopia: 250-STARTTLS^M Sep 24 20:01:37 neo Qtopia: 250-AUTH LOGIN PLAIN^M Sep 24 20:01:37 neo Qtopia: 250-ENHANCEDSTATUSCODES^M Sep 24 20:01:37 neo Qtopia: 250-8BITMIME^M Sep 24 20:01:37 neo Qtopia: 250 DSN Sep 24 20:01:37 neo Qtopia: SMTP : StartTLS: sent: STARTTLS Sep 24 20:01:37 neo Qtopia: SMTP : response: 220 2.0.0 Ready to start TLS Sep 24 20:01:38 neo Qtopia: Encrypted connect warnings: 'The root certificate of the certificate chain is self-signed, and untrusted' Sep 24 20:01:38 neo Qtopia: SMTP : Closed connection Sep 24 20:01:38 neo Qtopia: socketError: 13 : The root certificate of the certificate chain is self-signed, and untrusted Hi David, I was just looking again at your reports about SMTP. I think there are several different factors for the different cases, and I haven't understood most of them yet. But I wonder if one relevant factor, for some of the untrusted cases, is that the QtMoko v48 rootfs doesn't include any CA certificates. I suddenly remembered that I also get lots of SSL error popups when using Arora. But after doing an apt-get install ca-certificates, I don't see those anymore, so presumably they were caused by the lack of any CA certificates. Also an odd thing about about those popups is that they don't indicate the actual problem, i.e. that the root certificate is untrusted. Instead they typically just say No Error No Error No Error :-) That could just be an Arora-specific problem, but it could be a more general problem with how certificate-related errors are propagated up through Qt. Anyway, you may like to: - try apt-get install ca-certificates, restart QtMoko, and see if any of your SMTP cases succeed after that - see if your working v35 rootfs has CA certificates in it (at /etc/ssl/certs). Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
On Sunday, September 30, 2012 05:21:43 PM Flemming Richter Mikkelsen wrote: I have big problems starting booting up proper. After finally attaching the debug cable, I noticed that the kernel is 3.4.0-gta04 but under /lib/modules/ there is only 2.6.34-qtmoko-v48. Do I need to first boot with 2.6.34 and then upgrade to the new kernel? It is strange that I didn't see any other reporting this problem. Have you downloaded the right tarball? The download url for GTA04 is http://sourceforge.net/projects/qtmoko/files/GTA04/ 2.6.34 is kernel for Freerunner (GTA02). So this looks like you have kernel for GTA04 and rootfs for GTA02. I have checked the qtmoko-debian-gta04-v48.tar.gz tarball and it looks all fine (3.5 kernel in boot, 3.5 modules in /var/lib) Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Here's some more smtp debugging - I'm now using the mail.inbox.lv server which supports unencrypted and TLS access Trying port 587 with TLS:- Sep 24 20:01:37 neo Qtopia: 250-STARTTLS^M Sep 24 20:01:37 neo Qtopia: 250-AUTH LOGIN PLAIN^M Sep 24 20:01:37 neo Qtopia: 250-ENHANCEDSTATUSCODES^M Sep 24 20:01:37 neo Qtopia: 250-8BITMIME^M Sep 24 20:01:37 neo Qtopia: 250 DSN Sep 24 20:01:37 neo Qtopia: SMTP : StartTLS: sent: STARTTLS Sep 24 20:01:37 neo Qtopia: SMTP : response: 220 2.0.0 Ready to start TLS Sep 24 20:01:38 neo Qtopia: Encrypted connect warnings: 'The root certificate of the certificate chain is self-signed, and untrusted' Sep 24 20:01:38 neo Qtopia: SMTP : Closed connection Sep 24 20:01:38 neo Qtopia: socketError: 13 : The root certificate of the certificate chain is self-signed, and untrusted I get the same message whether I set authentication to login or plain (I'm uncertain which would be correct), but also to none and imap (which I'd expect to be wrong. This makes me think I was too hasty to blame my own mail server's self-signed certificate. Changing to port 25 which is also supported by the server gives the same error Sep 24 20:26:18 neo Qtopia: SMTP : Init: sent: EHLO qtopia-messageserver Sep 24 20:26:18 neo Qtopia: SMTP : response: 250-mail.inbox.lv^M Sep 24 20:26:18 neo Qtopia: 250-PIPELINING^M Sep 24 20:26:18 neo Qtopia: 250-SIZE 5990^M Sep 24 20:26:18 neo Qtopia: 250-VRFY^M Sep 24 20:26:18 neo Qtopia: 250-ETRN^M Sep 24 20:26:18 neo Qtopia: 250-STARTTLS^M Sep 24 20:26:18 neo Qtopia: 250-AUTH LOGIN PLAIN^M Sep 24 20:26:18 neo Qtopia: 250-ENHANCEDSTATUSCODES^M Sep 24 20:26:18 neo Qtopia: 250-8BITMIME^M Sep 24 20:26:18 neo Qtopia: 250 DSN Sep 24 20:26:18 neo Qtopia: SMTP : Auth: sent: AUTH LOGIN Sep 24 20:26:18 neo Qtopia: SMTP : response: 334 VXNlcm5hbWU6 Sep 24 20:26:18 neo Qtopia: SMTP : AuthUser: sent: ZG1hdHRoZXdzQGluYm94Lmx2 Sep 24 20:26:18 neo Qtopia: SMTP : response: 334 UGFzc3dvcmQ6 Sep 24 20:26:18 neo Qtopia: SMTP : AuthPass: sent: Base64 password hidden Sep 24 20:26:22 neo Qtopia: SMTP : response: 535 5.7.8 Error: authentication failed: authentication failure Sep 24 20:26:22 neo Qtopia: SMTP : Closed connection With no encryption on port 25:- Sep 24 20:28:50 neo Qtopia: SMTP : Init: sent: EHLO qtopia-messageserver Sep 24 20:28:50 neo Qtopia: SMTP : response: 250-mail.inbox.lv^M Sep 24 20:28:50 neo Qtopia: 250-PIPELINING^M Sep 24 20:28:50 neo Qtopia: 250-SIZE 5990^M Sep 24 20:28:50 neo Qtopia: 250-VRFY^M Sep 24 20:28:50 neo Qtopia: 250-ETRN^M Sep 24 20:28:50 neo Qtopia: 250-STARTTLS^M Sep 24 20:28:50 neo Qtopia: 250-AUTH LOGIN PLAIN^M Sep 24 20:28:50 neo Qtopia: 250-ENHANCEDSTATUSCODES^M Sep 24 20:28:50 neo Qtopia: 250-8BITMIME^M Sep 24 20:28:50 neo Qtopia: 250 DSN Sep 24 20:28:50 neo Qtopia: SMTP : Auth: sent: AUTH PLAIN Base64 username/password hidden Sep 24 20:28:54 neo Qtopia: SMTP : response: 535 5.7.8 Error: authentication failed: authentication failure Sep 24 20:28:54 neo Qtopia: SMTP : Closed connection Similar result if I try login authentication except the difference does get logged. I'm *definitely* configuring the gui with the correct username and password and that shows up correctly to the qtopiamail.conf. Why do the logs report STARTTLS when I've not configured that? I need to stop thinking about this, I'm resigned to v48 not being able to send email anyway I know how - sad as for me there was no problem with v35. Hope this info is of use to someone. Does anyone suceed in doing this? -- David Matthews m...@dmatthews.org ___ 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
Re: QtMoko v48 neofreerunner
Hi Neil Thanks - I will give that a try. It occurred to me also that since the fastmail smtp server offers a choice of ssl, tls and unencrypted logins on various ports, it will be easy to try the options other than ssl. I'll also do that. Regards More likely errorOccurred, I guess. That's as far as I can get for now; the next step seems to involve a QtopiaIpcAdaptor, which I'm not familiar with. 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. With fingers crossed, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Hi Neil 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.) I'm not going to get around to trying that tonight, but here's an update on further pokings, more interesting than successful. First, still using the fastmail smtp server - I tried unencrypted and TLS access, the first fails on port 25 in the same way as SSL, but the second gives an error from the remote server - so with TLS set, packets are actually leaving the neo although the connection fails. That seemed fair enough as I think I was wrong about TLS support at fastmail - I seemed to have been looking at an old page. Ah - but my own mail server does support TLS. Damn - I get the original error message again, but after a long enough gap to suggest things are happening beyond the phone. Sure enough - in the mail servers logs now there is something (dunno why I did not see this a couple of days ago):- 2012-09-20 19:23:59 TLS error on connection from [x.x.x.x] (recv): A TLS packet with unexpected length was received. 2012-09-20 19:23:59 TLS error on connection from [x.x.x.x] (send): The specified session has been invalidated for some reason. So why don't I see the Remote server closed the session error on the phone as I do with a TLS attempt at fastmail? I guess that could be different server behaviour rather than inconsistency with qtmoko Enough for one night - will try Neils suggestion for further info over the weekend. -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Hi Neil For the mail sending problem, what exactly are the diagnostics? For example, what is it that makes you write Socket error above? That's part of the error the neo reports when I try to send mail. I've had a further thought though - that I'm running the original flawed version of v48 with the updated qtmoko Radek produced installed over the top. I guess most people just grabbed the fixed image and reflashed - maybe there's a difference and that's why no one else has reported or confirmed this. I'll reflash with the updated image tonight and see if that makes this go away - if not I'll supply the exact error message. Regards -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
On Wednesday, September 19, 2012 09:55:11 AM David Matthews wrote: Hi Neil For the mail sending problem, what exactly are the diagnostics? For example, what is it that makes you write Socket error above? That's part of the error the neo reports when I try to send mail. I've had a further thought though - that I'm running the original flawed version of v48 with the updated qtmoko Radek produced installed over the top. I guess most people just grabbed the fixed image and reflashed - maybe there's a difference and that's why no one else has reported or confirmed this. It should not be the problem, but you can try anyways. If this is really regression (worked in previous version and not working now) then it's most likely because of Qt upgrade. The qtopia mail program has last significant commit from year 2009... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Hi Neil, Radek I spent some time on what I believe are the email issues. First thing I did to ensure I'm not going mad is the flash back to v35. As I remembered, I can create an account without bothering with correct settings, put the qtopiamail.conf in place and everything works. Next I flashed the 2nd v48 image - the situation has improved - the problem with the Get all mail entry disappearing has ... well disappeared - it does work fine. Despite what you thought - a difference in v48-1 with the upgraded qtmoko package installed on top as against the good v48-2? Can't be sure, but at least it's gone away for me. Trying to send mail though, that problem is as I reported already; I'm using the same qtopiamail.conf I just used in v35 which specifies the fastmail SMTP server (which I can ping) - sending a test mail to myself at dmatthews.org gives this rather generic looking error:- dmatthews.org -Error sending Email:Error occurred [Unknown error] If this is the real problem that I think it to be, since I jumped from v37 to v48 without ever trying the in between offerings, I'm not much help at pinning down when it was introduced Regards -- 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: Hi Neil, Radek I spent some time on what I believe are the email issues. First thing I did to ensure I'm not going mad is the flash back to v35. As I remembered, I can create an account without bothering with correct settings, put the qtopiamail.conf in place and everything works. Next I flashed the 2nd v48 image - the situation has improved - the problem with the Get all mail entry disappearing has ... well disappeared - it does work fine. Despite what you thought - a difference in v48-1 with the upgraded qtmoko package installed on top as against the good v48-2? Can't be sure, but at least it's gone away for me. Well that's good news! Trying to send mail though, that problem is as I reported already; I'm using the same qtopiamail.conf I just used in v35 which specifies the fastmail SMTP server (which I can ping) - sending a test mail to myself at dmatthews.org gives this rather generic looking error:- dmatthews.org -Error sending Email:Error occurred [Unknown error] That comes from EmailClient::transferFailure() in src/applications/qtmail/emailclient.cpp. Tracking back from there, I see: - EmailClient::activityChanged(QMailServiceAction::Failed) - QMailTransmitAction::activityChanged(QMailServiceAction::Failed) - QMailServiceActionPrivate::emitChanges() following something that set _activityChanged to TRUE - QMailServiceActionPrivate::setActivity(QMailServiceAction::Failed) (which is the only place that sets _activityChanged to TRUE) - QMailServiceActionPrivate::errorOccurred() or (QMailTransmitActionPrivate::sendCompleted with !_ids.isEmpty()). More likely errorOccurred, I guess. That's as far as I can get for now; the next step seems to involve a QtopiaIpcAdaptor, which I'm not familiar with. 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. With fingers crossed, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
For me, on GTA04, email is working almost perfectly; I'm also using IMAP. maybe this is just a problem on GTA02? anyone else confirm? For sending, can you ping your SMTP server from the Freerunner? yes For Get all mail, note that this is visible only on the Email page, not on the parent page for all messages (including SMS), or on the more specific pages for each email account. When I did a Get all mail, with several thousand messages to download, it did take around a minute (I think) before the application even started showing a progress bar; and it took a few hours to complete that initial download. On the Freerunner, with 2G instead of 3G, I imagine those operations would probably take even longer. well I will look at this again, but this is never something I struggled with on v2x and v3x - the option to fetch mail was always where I'd expect. This time when I did see it, it was rather a surprise as I'd been struggling to make sense of this for 30mins. After that one time when I fetched the mail, I never saw the option to do it again. If you're sure you have IP-level connectivity to your IMAP and SMTP servers, and still things aren't working, perhaps you could use tcpdump to capture the IMAP and SMTP exchanges, then look at that on another computer with Wireshark? there is definitely connectivity that I checked. As I said - the account creation to me is rather tedious, so I just create the account with any old settings and then move the known good qtopiamail.conf into place. I did this with several upgrades before without problem. This time I also tried an alternative smtp server - same error message. I also confirmed I was using the mail settings I thought I was by editing after the file had been swapped in and checking what was there. In summary - although I doubt it, one issue maybe my pebkac, the other is surely a real problem. -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
thanks as always for the work! I have one issue with the new alarm turning into vibrate only after 60 secs: If I put an alarm and turn the phone completely oft (GTA02 SD-card version) the phone starts nicely to boot at the right time, but now the boot time is about 75 secs, so once everything has been initiated the phone starts to vibrate for the alarm but there is now place to turn the alarm off. in my opinion the alarm should only start once the interface to press snooze or cancel the alarm is present, and maybe we give it even two seconds of silence before it starts (eg you sit somewhere where everyone else is quite, you see the alarm go off but it doesn't ring yet and you can still press cancel before the alarm goes off properly). a very very advanced version of the alarm could have a box to type in the delay seconds for booting until the alarm is actually present which would be taken into account so that the alarm would actually ring at the right time and not one to two minutes later. robin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
On Tuesday, September 18, 2012 12:33:46 PM robin wrote: thanks as always for the work! I have one issue with the new alarm turning into vibrate only after 60 secs: If I put an alarm and turn the phone completely oft (GTA02 SD-card version) the phone starts nicely to boot at the right time, but now the boot time is about 75 secs, so once everything has been initiated the phone starts to vibrate for the alarm but there is now place to turn the alarm off. Interesting - i didnt know that rtc alarm can power on the device. I just tested the alarm with suspend to ram, which seems to be working perfectly now... in my opinion the alarm should only start once the interface to press snooze or cancel the alarm is present, and maybe we give it even two seconds of silence before it starts (eg you sit somewhere where everyone else is quite, you see the alarm go off but it doesn't ring yet and you can still press cancel before the alarm goes off properly). Sure this would be nice... a very very advanced version of the alarm could have a box to type in the delay seconds for booting until the alarm is actually present which would be taken into account so that the alarm would actually ring at the right time and not one to two minutes later. This could be done. Maybe pressing Power off could reschedule the RTC a bit. But this is really advanced, i wonder if other phones could do something like this... Btw dont count very much with me on implementing these. I got some other tasks on my list. I have QtMoko with Qt 4.8.3 working now, but it displays .pic icons with wrongs sizes - if anyone has idea what could be wrong it would be welcome. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
hi radek, thanks for the quick answer. Can one easily manually edit the file where you put in the ringing timeout after 60 secs? regards robin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
On Tuesday, September 18, 2012 01:57:15 PM robin wrote: hi radek, thanks for the quick answer. Can one easily manually edit the file where you put in the ringing timeout after 60 secs? It's not configurable yet... It has to be implemented. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
Hi I found a single area with (what appears to me to be) regressions - email I have a copy of a known good qtopiamail.conf which I just put into place after a slapdash account creation. I can retrieve the folder list, but the Fetch all mail option only sporadically appears so the imap inbox is not really usable. I never managed to send mail, getting socket errors every time. I've just spent another couple of hours checking over this 1. it's actually Get all mail and you should see that if you highlight your email inbox. After fetching mail once it reliably disappears from the menu. I found two ways to bring it back - a reboot and weirdly, a sms message arriving! (new email arriving makes no difference) 2. Socket error on trying to send mail - I was pretty certain this was failing too quickly to actually be going out and trying to authenticate. I have generally used the fastmail.fm smtp server on the phone - not sure why, although possibly because it used to just work without too much fiddling. So I sacrificed the previously known good config in the copied qtopiamail.conf file that served me through several versions of qtmoko and entered details of my own mail server. I can then look at it's logs for information about a failed smtp connection - as I suspected, there is nothing there. In summary I'm pretty sure these are real problems on the neo that did not exist, in for instance versions 26 and 35. That's a pity as in much else there have been very noticeable improvements. -- 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: 2. Socket error on trying to send mail - I was pretty certain this was failing too quickly to actually be going out and trying to authenticate. I have generally used the fastmail.fm smtp server on the phone - not sure why, although possibly because it used to just work without too much fiddling. So I sacrificed the previously known good config in the copied qtopiamail.conf file that served me through several versions of qtmoko and entered details of my own mail server. I can then look at it's logs for information about a failed smtp connection - as I suspected, there is nothing there. In summary I'm pretty sure these are real problems on the neo that did not exist, in for instance versions 26 and 35. I'd like to do what I can to help debug this, as I've been looking a bit at the qtmail program, and finding it very useful. For the mail sending problem, what exactly are the diagnostics? For example, what is it that makes you write Socket error above? Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 - fixed SMS sending
On Sat, 15 Sep 2012 09:42:59 +0200 Radek Polak pson...@seznam.cz wrote: Thanks a lot!! Regards. Hi, you can download new tarbals with fixed SMS sending bug, or you can install just the updated packages: For freerunner: http://qtmoko.sourceforge.net/debian/qtmoko-neo_48-1_armel.deb for GTA04: http://qtmoko.sourceforge.net/debian/gta04/qtmoko-gta04_48-1_armel.deb Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
On Sunday, September 16, 2012 08:41:14 PM francesco.dev...@mailoo.org wrote: FBreader doesn't work properly, when I launch it I see two messages on screen: Upgrading to the new version and then Loading book, Please wait. After that, the FBreader main screen appears for less then a second and it disappears to the QtMoko homescreen. FBreader does not close but remains in background, I have to quit it using the AUX button. I also tryed it with QX but the application seems to crash on start. I have noticed too - it's probably after the Qt 4.7 upgrade. I'll have to rebuild it (same with navit). Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48 neofreerunner
I've not used qtmoko or the neo for some while, maybe this feedback is helpful. Overall v48 seems pretty good, stable, reasonable battery life and most of the core stuff works pretty well (great work Radek!):- *send and receive phone calls - call quality ok *send and receive sms *connect to home wifi (open with MAC filtering) *connect to GPRS *GPS quick fix :-) I'd not used the new keyboard before - I found it pretty cranky at first, but actually it works pretty good once you get used to it. I found a single area with (what appears to me to be) regressions - email I have a copy of a known good qtopiamail.conf which I just put into place after a slapdash account creation. I can retrieve the folder list, but the Fetch all mail option only sporadically appears so the imap inbox is not really usable. I never managed to send mail, getting socket errors everytime. -- 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: I found a single area with (what appears to me to be) regressions - email I have a copy of a known good qtopiamail.conf which I just put into place after a slapdash account creation. I can retrieve the folder list, but the Fetch all mail option only sporadically appears so the imap inbox is not really usable. I never managed to send mail, getting socket errors everytime. For me, on GTA04, email is working almost perfectly; I'm also using IMAP. For sending, can you ping your SMTP server from the Freerunner? For Get all mail, note that this is visible only on the Email page, not on the parent page for all messages (including SMS), or on the more specific pages for each email account. When I did a Get all mail, with several thousand messages to download, it did take around a minute (I think) before the application even started showing a progress bar; and it took a few hours to complete that initial download. On the Freerunner, with 2G instead of 3G, I imagine those operations would probably take even longer. If you're sure you have IP-level connectivity to your IMAP and SMTP servers, and still things aren't working, perhaps you could use tcpdump to capture the IMAP and SMTP exchanges, then look at that on another computer with Wireshark? Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
Hi FBreader doesn't work properly, when I launch it I see two messages on screen: Upgrading to the new version and then Loading book, Please wait. After that, the FBreader main screen appears for less then a second and it disappears to the QtMoko homescreen. FBreader does not close but remains in background, I have to quit it using the AUX button. I also tryed it with QX but the application seems to crash on start. Regards Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
Am 12.09.2012 20:38, schrieb Radek Polak: Hi, QtMoko v48 is out now, ... * mokofaen is now default theme (credits to Joif for this nice theme) Hi, many thanks to Radek. I just updated my GTA02 from V47 to V48-1. Maybe I found a little bug: - click house (left, second from top) - click help open (bottom left, arrow up) - click help close (bottom left, arrow down) - try to click back (bottom right) Back don't work. Help is always opend. After opening any App and closing it, back is working again. -- Frank ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
Hello Joif, all, Hi I upgraded from v47 to v48 on my GTA02 and now I'm experiencing a grave problem. if I send a sms, it does not arrive to the recipient. Also, after sending the sms I lose all the phone functionalities, i.e. I can't even make or receive a call. I had to restart the neo but the issue persists if I try to send another sms. The problem seems to be around the sms, because if I do not send a sms everything works well. Can someone else confirm this behaviour or is it just me? Thanks. Regards Joif I tried to reproduce the bug and, after sending one SMS (never received) I received a phone call, but I've not been able to answer and, when I tried to call back, it tried to call, but no sound came from the hearphone and no one answered, so I think phone functionalities were not working. I will try again. By the way, what does the four symbols below he calendar on the home of mokofaen stand for? * provider * ?/? (number over number) * consumption * ? (empty) Thanks and best regards, Giacomo -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
Hi Radek I just installed the v48 (not upgraded from v47) on the uSD, I confirm the problem with the sms. Hi, i have reverted commit that made the problem [1]. You can download rebuilt libraries to fix the problem here [2]. I'm guessing those are for GTA04? Is there somewhere we can get the version 47 tarball for freerunner? I guess we can just use the files from there? Regards -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
On Friday, September 14, 2012 11:55:59 AM David Matthews wrote: I'm guessing those are for GTA04? They should be quite the same, but maybe not... Is there somewhere we can get the version 47 tarball for freerunner? I guess we can just use the files from there? I am now rebuilding the packages, it should take some hours. I had to delete old files from sourceforge, because it seems that if there are too many data the downloads stop working... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
By the way, what does the four symbols below he calendar on the home of mokofaen stand for? * provider * ?/? (number over number) * consumption * ? (empty) * provider * GSM cell location, the number has to be correlated to some name, it is a function not yet developed * consumption * pressure in mb, only availble if you have a barometer sensor Regards Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
On Wed, 12 Sep 2012 20:38:38 +0200 Radek Polak pson...@seznam.cz wrote: Hi, QtMoko v48 is out now, you can download images for Freerunner and GTA04 from here [1][2]. For more info about QtMoko please visit our homepage [3]. Thanks!!! This release is mainly bug fix release. Here is list of changes since v47: * working alarm * mokofaen is now default theme (credits to Joif for this nice theme) * working USSD on gta04 (Stefan Rupp) * handling of long USSD (Stefan Rupp) * fixed sound in calls on A3 (Neil Jerram) * better sound volume on A3 (Neil Jerram) * make gsm location working (Neil Jerram) * updated mokofaen theme (Joif) * fix DTMF on gta04 (Neil Jerram) * using /dev/input/incoming for leds signaling of SMS/call on gta04 * race free suspend on gta04 * custom tones for alarm - either ogg or wav * added some alarm tones from android * removed bundled atd * not holding /dev/rtc0 anymore and hwclock now works * alarm now vibrates after 60s to avoid getting shocked in the morning * fixed bluetooth so that it now works again * turing off bluetooth after startup to save power * headset jack detection on gta04 * changes for 3.5 kernel on gta04 * turning of gps antena on gta04 during startup to save power * computing average suspend current from charge_now * removed init of bmp085 - 3.5 kernel handles this now * added qReadFile and qWriteFile api * using qReadFile and qWriteFile where possible * RTC clock info in NeoControl * QtMaze now vibrates even on gta04 * merged master and master_gta04 branches, master_gta04 is now obsolete * debian now uses multipackage Probably the biggest change was rework of alarms. It should work reliably now. I have been using it daily and it always worked. GTA04 users should enjoy improved battery life. In suspend it's now in range 21..26mA according to the current moon phase. Thanks everyone who helped with the release and enjoy it! Radek [1] https://sourceforge.net/projects/qtmoko/files/GTA02/ [2] https://sourceforge.net/projects/qtmoko/files/GTA04/ [3] http://qtmoko.sourceforge.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
Hi I upgraded from v47 to v48 on my GTA02 and now I'm experiencing a grave problem. if I send a sms, it does not arrive to the recipient. Also, after sending the sms I lose all the phone functionalities, i.e. I can't even make or receive a call. I had to restart the neo but the issue persists if I try to send another sms. The problem seems to be around the sms, because if I do not send a sms everything works well. Can someone else confirm this behaviour or is it just me? Thanks. Regards Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
Hi I upgraded from v47 to v48 on my GTA02 and now I'm experiencing a grave problem. if I send a sms, it does not arrive to the recipient. Also, after sending the sms I lose all the phone functionalities, i.e. I can't even make or receive a call. I had to restart the neo but the issue persists if I try to send another sms. The problem seems to be around the sms, because if I do not send a sms everything works well. Can someone else confirm this behaviour or is it just me? Thanks. Regards Joif I just installed the v48 (not upgraded from v47) on the uSD, I confirm the problem with the sms. Regards Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
On Thu, 13 Sep 2012 15:49:44 +0200 francesco.dev...@mailoo.org wrote: Hi I upgraded from v47 to v48 on my GTA02 and now I'm experiencing a grave problem. if I send a sms, it does not arrive to the recipient. Also, after sending the sms I lose all the phone functionalities, i.e. I can't even make or receive a call. I had to restart the neo but the issue persists if I try to send another sms. The problem seems to be around the sms, because if I do not send a sms everything works well. Can someone else confirm this behaviour or is it just me? Thanks. Regards Joif I just installed the v48 (not upgraded from v47) on the uSD, I confirm the problem with the sms. Thanks for this information. Regards Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
On Thursday, September 13, 2012 03:49:44 PM francesco.dev...@mailoo.org wrote: I just installed the v48 (not upgraded from v47) on the uSD, I confirm the problem with the sms. The problem is also present on GTA04. In v47 it is working so it will be probably one of v48 commits... Trying to find which now... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
On Thursday, September 13, 2012 03:49:44 PM francesco.dev...@mailoo.org wrote: I just installed the v48 (not upgraded from v47) on the uSD, I confirm the problem with the sms. Hi, i have reverted commit that made the problem [1]. You can download rebuilt libraries to fix the problem here [2]. Regards Radek [1] https://github.com/radekp/qtmoko/commit/b98287747b785bb72954edc76105592d6c9404d4 [2] http://activationrecord.net/radekp/pub/v48_sms/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
Hi Radek scp-ing those two replacement libs into /opt/qtmoko/lib/ reliably breaks an install onto freerunner nand - qtmoko immediately freezes and if you reboot will not restart. I tried this 3 times - reflashing the rootfs, then I realized that the system is up (you can ssh in) but no graphical interface. I tried to start qpe directly:- /opt/qtmoko/qpe. qpe.env qpe.sh root@neo:~# /opt/qtmoko/qpe.sh Cannot create semaphore /tmp/qtembedded-0/QtEmbedded-0 'd' Error 22 Invalid argument Cannot get display lock Aborted Regards -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
I just did the same and I'm stuck with frozen device. Would be probably good to make v47 available for downloading. Hopefully I have v47 on my laptop -- Peter On 09/13/2012 11:24 PM, dmatthews.org wrote: Hi Radek scp-ing those two replacement libs into /opt/qtmoko/lib/ reliably breaks an install onto freerunner nand - qtmoko immediately freezes and if you reboot will not restart. I tried this 3 times - reflashing the rootfs, then I realized that the system is up (you can ssh in) but no graphical interface. I tried to start qpe directly:- /opt/qtmoko/qpe. qpe.env qpe.sh root@neo:~# /opt/qtmoko/qpe.sh Cannot create semaphore /tmp/qtembedded-0/QtEmbedded-0 'd' Error 22 Invalid argument Cannot get display lock Aborted Regards ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
Radek Polak pson...@seznam.cz writes: i have reverted commit that made the problem [1]. [1] https://github.com/radekp/qtmoko/commit/b98287747b785bb72954edc76105592d6c9404d4 Well, sorry everyone if it was my DTMF-related change that caused this regression. But, Radek, did you notice that there were some other QSerialPort changes that got included somehow in that commit? I'm pretty sure those changes weren't in my patch, and I wonder if they might be related to the SMS issue. Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
On Thursday, September 13, 2012 11:54:40 PM Neil Jerram wrote: Well, sorry everyone if it was my DTMF-related change that caused this regression. No problem, everyone makes bugs. But, Radek, did you notice that there were some other QSerialPort changes that got included somehow in that commit? I'm pretty sure those changes weren't in my patch, and I wonder if they might be related to the SMS issue. I was just in the middle of redoing the debian packages and i accidently commited stuff that should not be commited. But still i think the problems must be in the DTMF code - but it's something not obvious - the code looks quite harmless to me... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v48
Il 12/09/2012 20:38, Radek Polak ha scritto: Hi, QtMoko v48 is out now, you can download images for Freerunner and GTA04 from here [1][2]. For more info about QtMoko please visit our homepage [3]. This release is mainly bug fix release. Here is list of changes since v47: * working alarm * mokofaen is now default theme (credits to Joif for this nice theme) * working USSD on gta04 (Stefan Rupp) * handling of long USSD (Stefan Rupp) * fixed sound in calls on A3 (Neil Jerram) * better sound volume on A3 (Neil Jerram) * make gsm location working (Neil Jerram) * updated mokofaen theme (Joif) * fix DTMF on gta04 (Neil Jerram) * using /dev/input/incoming for leds signaling of SMS/call on gta04 * race free suspend on gta04 * custom tones for alarm - either ogg or wav * added some alarm tones from android * removed bundled atd * not holding /dev/rtc0 anymore and hwclock now works * alarm now vibrates after 60s to avoid getting shocked in the morning * fixed bluetooth so that it now works again * turing off bluetooth after startup to save power * headset jack detection on gta04 * changes for 3.5 kernel on gta04 * turning of gps antena on gta04 during startup to save power * computing average suspend current from charge_now * removed init of bmp085 - 3.5 kernel handles this now * added qReadFile and qWriteFile api * using qReadFile and qWriteFile where possible * RTC clock info in NeoControl * QtMaze now vibrates even on gta04 * merged master and master_gta04 branches, master_gta04 is now obsolete * debian now uses multipackage Probably the biggest change was rework of alarms. It should work reliably now. I have been using it daily and it always worked. GTA04 users should enjoy improved battery life. In suspend it's now in range 21..26mA according to the current moon phase. Thanks everyone who helped with the release and enjoy it! Radek [1] https://sourceforge.net/projects/qtmoko/files/GTA02/ [2] https://sourceforge.net/projects/qtmoko/files/GTA04/ [3] http://qtmoko.sourceforge.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Really awesome! Thanks to all the developers! Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
