Re: QtMoko v48 neofreerunner
"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
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
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: Bye SHR, hello QTMoko (and battery life)
O Domingo, 7 de Outubro de 2012, David Garabana Barro escribiu: > O Xoves, 4 de Outubro de 2012, Timo Juhani Lindfors escribiu: > > David Garabana Barro writes: > > > Any clue on this? > > > > Can you measure the power consumption please? With and without GSM. > > Now, I want to do tests with GSM powered off. For this, is it enough if I > boot without inserted SIM card? I answer myself. Booting without SIM card does no change power consumption at all, so it seems qtmoko powers on GSM with or without SIM inserted. So I've made as suggested by gennady in bug report: cd /sys/bus/platform/devices echo 1 > gta02-pm-gsm.0/power_on echo 0 > gta02-pm-gsm.0/power_on And now I can see a difference in power consumption, BUT it seems qtmoko won't suspend if you poweroff GSM :( GSM off: On battery and display at 80% [1] brightness: 197 mA On battery and display dimmed: 123 mA On battery and display off: 117 mA On resume: ?? mA There are almost not deviations in power consumption with GSM powered off, which I suppose is normal. Being timeouts configured as: Dim:1 m Display off:3 m Suspend:5 m And using the same script as before This is the output of script in a full cycle (only pasting changes in current_now values) Sun Oct 7 13:55:22 CEST 2012 199875 [..] Sun Oct 7 13:56:08 CEST 2012 199875 Sun Oct 7 13:56:13 CEST 2012 124687 [..] Sun Oct 7 13:57:49 CEST 2012 124687 Sun Oct 7 13:57:54 CEST 2012 118500 -- David Garabana Barro jabber & google talk ID:da...@garabana.com Clave pública PGP/GPG: http://davide.garabana.com/pgp.html 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
> "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: Bye SHR, hello QTMoko (and battery life)
O Domingo, 7 de Outubro de 2012, Radek Polak escribiu: > On Sunday, October 07, 2012 06:52:42 AM David Garabana Barro wrote: > Maybe stupid questions - but do you have USB cable connected? In this case > it will not suspend. On battery it should suspend after configured > interval. You can try lock the home screen - the preconfigured interval in > this case is 10s. I asked this before Timo's answer. Now I know I can read it from current_now just after waking up. As you say, it would be better to have "charge_now", but by the moment this is an acceptable approximation... -- David Garabana Barro jabber & google talk ID:da...@garabana.com Clave pública PGP/GPG: http://davide.garabana.com/pgp.html 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
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/.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" 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 /etc/ssl/certs/Ad
Re: Bye SHR, hello QTMoko (and battery life)
O Xoves, 4 de Outubro de 2012, Timo Juhani Lindfors escribiu: > David Garabana Barro writes: > > Any clue on this? > > Can you measure the power consumption please? With and without GSM. For these tests I flashed Qi from qtmoko repositories, so we can discard any problem with u-boot. GSM on: On battery and display at 80% [1] brightness: ~200-210 mA On battery and display dimmed: ~130-135 mA On battery and display off: ~120-130 mA On resume: ~12-18 mA Being timeouts configured as: Dim:1 m Display off:3 m Suspend:5 m And using this script: while true; do echo "`date` `cat /sys/class/power_supply/battery/current_now`" >>/var/log/power.log; sleep 5; done This is the output of script in a full cycle (only pasting changes in current_now values) Sun Oct 7 10:39:59 CEST 2012 200250 [..] Sun Oct 7 10:40:45 CEST 2012 200250 Sun Oct 7 10:40:50 CEST 2012 134062 [..] Sun Oct 7 10:41:35 CEST 2012 134062 Sun Oct 7 10:41:40 CEST 2012 131437 [..] Sun Oct 7 10:42:26 CEST 2012 131437 Sun Oct 7 10:42:31 CEST 2012 128250 [..] Sun Oct 7 10:43:16 CEST 2012 128250 Sun Oct 7 10:43:22 CEST 2012 123375 [..] Sun Oct 7 10:44:07 CEST 2012 123375 Sun Oct 7 10:44:12 CEST 2012 122250 [..] Sun Oct 7 10:44:32 CEST 2012 122250 Sun Oct 7 10:54:16 CEST 2012 12750 Does these valules seem ok for you? Is it normal so little difference (~10mA) between dimmed display and powered off display? Now, I want to do tests with GSM powered off. For this, is it enough if I boot without inserted SIM card? [1] Default qtmoko on-battery max brightness -- David Garabana Barro jabber & google talk ID:da...@garabana.com Clave pública PGP/GPG: http://davide.garabana.com/pgp.html 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: Bye SHR, hello QTMoko (and battery life)
David Garabana Barro writes: > And I'm wondering, if suspended, it won't log anything, won't it? current_now has a lag of about 20 seconds. If you read it right after resume you can get suspend consumption. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
