And so simple the fix! Thanks for spotting this!

A few questions that I'd be glad to see clarified (if that's possible today). Not to make a demand, but to know What's in it?:

1. weight: The wiki has 200-235 gram, whereas the initial post has between 168g and 177g. Can you confirm either value (and unit)?
2. sensors: Does the device have an ambient light sensor?
3. GNSS: Is GPS: Yes, with A-GPS, GLONASS a data point or an exhaustive enumeration of GNSS support? (Thinking about Beidou, Galileo. But also: What about SBAS support [WAAS, EGNOS]? Easiest answer would perhaps be some GNSS chip information.)
4. IP class: Any information regarding ingress protection marking?

@mihael Sorry, no idea for wifi problems.

@mihael According to the Arch Linux wiki, when a Device connects, then disconnects after a few moments it might be due a device already being paired (from within a different operating system). A fix is to remove the device and re-pair. The Arch Linux wiki shows how to do that on the command-line via the bluetoothctl command.

@tomoqv said in Its That Time Again! Q&A 31 This Saturday.:

Will there ever be an effort to bring a native email client as a core app to Ubuntu Touch?

Mailpile might be a good candidate.

So I got this Nexus 5 and updated to the latest Android 6.0.1 (including latest baseband M8974A-2.0.50.2.30). I do want to flash UT with the ubports installer, because that worked so seemlessly on a BQ E4.5. However, before flashing UT, I want to do some Lineage testing (for whatever reasons). Installing Lineage includes changing the bootloader(?) to TWRP.

My question is whether flashing UT via ubports installer coming from Lineage has the same result as coming from stock Android? Will TWRP be replaced again by ubports installer? By what?