Sorry for the ignorance, but what is "wireless display"? I think this device can connect to an external display through the slimport (with the appropriate cable adapter), I tried this and it works perfectly, but the 15.04 Unity 8 desktop is not too much developed. But it doesn't have as far as I know mirachast or whatever it is called like the Meizo Pro 5 to connect wirelessly, does it?

Commenting on these problems in the Nexus 5, as I see them using the 15.04/devel channel:

• No notification LED: I have LED notifications for any notifications I got (calendar events and SMS or Telegram new messages)

• Very low call volume: In my case the volume looks like a little lower than what it should be, but it is perfectly usable. Outgoing call volume seems to be OK, nobody has complained to me.

• Loud beep after hanging up call: I have never seen this bug, not even when I tried the 15.04/stable or 15.04/rc channels.

• WiFi disconnects and requires password with WiFi extender: My Wifi sometimes disconnects and asks again for the WiFi password (I haven't tried it on WiFi extenders though), but going to the upper setting area and clicking again on the entry for that WiFi, it connects again, without having to enter the password again (it doesn't even ask for it). This does not happen too often, but it happens.

In my experience in the 15.05/devel channel, and after using it for about 20 days, I don't have any problems to have it as my only phone. For Whatsapp, which my personal network pressure obliges me to have otherwise I would be perfectly happy to drop, I have an old Galaxy Nexus connected close with my Wifi at home with the acual Whasapp client (with Cyanogenmod) and I connect in my device with the webapp. Apart from not having notifications, I'm perfectly connected with Whatsapp everywhere I have data or wifi Internet connection.

The 15.04/devel channel gets daily updates but of course there is no need to update daily. I have updated two or three times since I'm in this channel, and as far as I know, there are no big changes or development going on on the 15.04 images, so there is not a high risk of breakage.

@RandomUser I'm moving this discussion to the Support forum on a new thread, as I think it got off topic here.

@RandomUser What are those bugs? I did exactly the same move and I don't have anything major. I'm in the devel channel.

@happyzenith Congratulations and welcome to the uBports ship!

@happyzenith If you get "Device not connected" something you can try is different cables. There is also different ways of installling the m-d-t tool (directly from github or with the snap), and both should be tried. There is also a specific Telegram group to get support with that tool:
https://t.me/joinchat/AAAAAAiC4TTYHRddjUbpXg

@vandys Of course andbox never can be come a mandatory part of the system, it is just a sandbox, if it ever works, to run non-native applications. Like Wine in Linux, it you need an Android app for your job and you can run it in andbox you may carry a UT phone around, otherwise maybe you can't, unless you run around with two phones. But I would never advocate to make apk executable files native in UT.

It looks like andbox could be a good solution to everybody. I don't think (and technically must be impossible) it would be necessary to run Android apps natively, but having them run in a container like andbox could be fine in most of the cases. In my case it would be good to run some apps provided by my municipality or other entities, I don't think they will never release a native app for UT, and they will not release access to their databases to write such an app ourselves.

Everything that could be developed as a native app for UT should be developed, of course.

@guru I agree that a mailing list provides a type of interaction different from the forum and the Telegram group, and that it would be good to have it, if posssible.

@UniSuperBox I've done it a couple of times with the terminal app installed from the Openstore. Sometimes I get the "Exception..." message when I don't have Internet connectivity.