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
QtMoko annoyance
Hi, I wonder if it is at all possible to prevent the screen from unlocking on an incoming call? As I happen to keep my phone in my pocket, the automatic unlocking leads to the call being answered or rejected before I even have a chance to take the phone out of the pocket. Most of the time I use a silent profile, and if I walk around, I won't notice the call at all. But it will wake the phone up and unlock the screen, so random touches of the screen will make it do whatever it likes, like calling someone, e.g. an ambulance, delete all my contacts, or break my highscore in snake game, and of course drain the battery. An incoming message will wake it up, but not unlock the screen, which I think is a much more reasonable behaviour. Considering that SHR does it right, QtMoko should also be able to, I think. Regards Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
