apparently

Lollipop/ART issues; Firefox Weave
[18:37:08] matt [wronka.org]/Psi.cor I've switched back to Android 4.4 (CM-11, "Kitkat"). The following were issues I found with Android 5.0 ("Lollipop"):
* fdroid repos don't work, which is annoying (https://gitlab.com/fdroid/fdroidclient/issues/111)
* some Activesync servers don't work—I've only seen this reported with Horde (and I had the issue with both 5.0 and 5.2; https://bugs.horde.org/ticket/13702)

Back on CM-11, using the ART runtime, Firefox Sync (Weave/"Deprecated") also fails, apparently with a Unicode string error. It works fine with Dalvik. I don't know if this would have been an issue on Lollipop as well which uses ART by default. I didn't look for a specific bug for this, but was surprised that this sync was still supported since it was supposed to go away several versions ago (https://bugs.horde.org/ticket/13702). Apparently work on making the new service easy to use by third parties is either hard or just not a priority—the whole issue seems to have been bungled and now everyone's stuck with a mess. (https://bugzilla.mozilla.org/show_bug.cgi?id=989756#c14)

I also missed some of the UI elements from CM-11, like the circular battery indicator (is this a theme added by CM?) The settings menu was also more usable on CM-11. In general, Lollipop seemed to waste space, although I had mixed feelings about the task switching interface (it did seem to show more options at once, but made the active surface a bit small on a phone screen). A lot of Lollipop was flat, and Apple-like, looking pretty without giving the user any indication of whether interfaces were scrollable or otherwise how to interact with the device.

Unlike other reports, I did not run into any issues with WiFi or battery life on Lollipop—in fact, both seemed to be at least as good if not more reliable than on CM-11 and CM-10.2 but I don't have any objective tests for that. Specifically, I thnk my worst battery behaviour was in part to K9 synching my mail, and I haven't set that back up.

Welcome to Android.
[05:00:47] matt [wronka.org]/navic I got an Android device because I got fed-up with the broken WPA2 support in Nokia Belle on the E6-00.

Apparently I should have searched through the Android issue tracker first:

https://code.google.com/p/android/issues/detail?id=40065
https://code.google.com/p/android/issues/detail?id=51221
https://code.google.com/p/android/issues/detail?id=34212

Basically, the current version of openssl added new versions of TLS (new being used liberally) and many routers, technically broken, won't work with it.
This bug dates back to mid-2012, looks to have been fixed in later versiosn of 4.1 and broken again in 4.2. It's broken in the latest Nexus 4 (Mako) Cyanogen RC.

It's annoying.

Comcast Installation
[17:59:56] matt [wronka.org]/Psi.dementia We just transferred Comcast to a new address. Initially, we scheduled a move of an existing account, and they configured us for a self-installation, and when we called to explain there wasn't actually a coaxial connection coming into the house they got confused and it proved quicker and possibly cheaper to just cancel and schedule a new service.

After some initial issues scheduling the service, we got a weekday afternoon scheduled installation, and had Internet and television, for two hours or so. After this, the Internet dropped-out. Calling Comcast, the scheduled someone to come out the next day (Saturday), which was actually very convenient.

Apparently, the most economical option was the Comcast Tripple Play, which included Television, Internet, and Telephony hook-ups. This cost the same as just Television, but had the discounted rate for a full year; our Comcast representative woudn't sell us Television and Internet without the Telephony. The issue we appeared to be having, as explained when the service agent came out Saturday, is that the contracted installer who came on Friday hadn't completed the telephony set-up which confused (either the Comcast system or) the provided modem, and reset the service.

Following this correction, I had some issues with the Arris Touchstone DOCIS 2.0 modem. Apparently, after several minutes of running (somewhere between fifteen minutes and ninety minutes) the Arris modem will refuse to respond to DHCP offer requests (it might actually be that it'll only do this once per session, even when the same device requests a renewal). This has caused my Internet connection to routinely drop until I restart the modem. I've fixed this by adding static routes to the gateway device based on the initial response from the modem so that it won't try to renew and drop the connection because the modem doesn't respond.

Another thing I noted is that Comcast provided a DOCIS 2.0 modem. This was surprising on two levels, a) they were supposed to use my provided modem: the installer who came on Saturday said that they would have to charge me a *higher* tariff to use my own modem; and b) the modem they provided was a DOCIS 2.0 modem ("Our best modem!" said the Saturday installer), although this should be sufficient for the maximal bandwidth in the plan sold to me, 30Mbps down. It turns out it's definitely able to handle the 10Mbps down, 2Mbps up that I'm actually seeing between Comcast-based hosts.

Updating Symbian Devices is Easy!
[23:12:47] matt [wronka.org]/Trip I got my E8 updated. Apparently, it's a rather easy process:

a) Find somebody who works for Nokia.
b) Drive to their office.
c) Ask them nicely to flash your phone.

Apparently the Ovi suite didn't like my phone, nor did it there. The Nokite had to resort to stronger measures.

Debian Stable
[01:32:06] matt [wronka.org]/Psi.generay It's a running joke that Debian Stable (currently Squeeze) is often behind on features.

It used to be a running joke about how Linux distros couldn't find your CD-drive (optical drive, for you newbies with your Blu-Rays).

Apparently that running joke just made its way to Debian Stable.

http://forums.debian.net/viewtopic.php?f=5&t=50716&start=0