back
Sunday, December 7 2014
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.
[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.
Monday, January 6 2014
Ubuntu 13.10 and Darktable
[15:15:31] matt [wronka.org]/Trip Unfortunately, the Darktable developers package the latest versions for Ubuntu, which means it's simply easiest to use that distro. Installing 13.10 at home at least avoided the issues 13.04 had at work with filesystems not being mounted during init (like /tmp), but oddly switching from 12.10 to 13.10 30-bit dual-head became unstable and lost acceleration. 13.10 seems to work alright (or at lesat with accelration) when connected do one output to the Haswell card, but connecting two leads to instability and a lots of acceleration. The same computer, swaping the boot drive, works fine with dual-head 30-bit on 12.10 so this appears to be a software regression as opposed to a lack of general support for the configuation.
Otherwise, upgrading to Darktable 1.4 from 1.2.x has been positive. (Back on 12.10), it feels much faster, especially when turning-on level and curve controls (it seems to have already calculated the luminosity distribution which used to take an annoyingly long time to appear), and more controls can be instanced—this is particularly useful for levels to be used like an ND grad (better than the default ND grad control) and spot removal which can now blend to just affect spots when cloning dust.
[15:15:31] matt [wronka.org]/Trip Unfortunately, the Darktable developers package the latest versions for Ubuntu, which means it's simply easiest to use that distro. Installing 13.10 at home at least avoided the issues 13.04 had at work with filesystems not being mounted during init (like /tmp), but oddly switching from 12.10 to 13.10 30-bit dual-head became unstable and lost acceleration. 13.10 seems to work alright (or at lesat with accelration) when connected do one output to the Haswell card, but connecting two leads to instability and a lots of acceleration. The same computer, swaping the boot drive, works fine with dual-head 30-bit on 12.10 so this appears to be a software regression as opposed to a lack of general support for the configuation.
Otherwise, upgrading to Darktable 1.4 from 1.2.x has been positive. (Back on 12.10), it feels much faster, especially when turning-on level and curve controls (it seems to have already calculated the luminosity distribution which used to take an annoyingly long time to appear), and more controls can be instanced—this is particularly useful for levels to be used like an ND grad (better than the default ND grad control) and spot removal which can now blend to just affect spots when cloning dust.