Another update: Tried anbox on my desktop first, and there are lots of issues with the apps. So most likely I'll leave Android installed on the tablet directly.

ha-ha, your right, i mixed it up with the oneplus 3T I have. I have the 64 GB, so everything is OK. Slightly wobbly start on this forum, but I will do better

I'm having similar problems in my Nexus 5 running 16.04rc - I tried using a different charger - the one from my Huawei p9 (checked that it had same output voltage) - and now it seems to be better.

@domubpkm said in BUG IN 16.04 NOTIFICATIONS: So what i said is always valid for my phones.. To be corroborated I can corroborate this bug on my M10 FHD tablet on 16.04/devel

@halucigenia ah, I see

FYI I have been here before - See https://forums.ubports.com/post/4741 I just thought that this thread might have something that I have not yet tried.

@stefano sure, can you PM your Telegram or Matrix handle?

@themoose007 can you please tell which version of the installer you were using?

@ali461 you're welcome!

@alan_g said in How to launch GUI apps from CLI?: @nikalon you have to "trick" Unity8 into allowing the application to connect. I have not tried it recently, but something like this... https://lists.ubuntu.com/archives/mir-devel/2015-September/001267.html Yes! That works, thank you! For anyone who wants the answer you have to append the paremeter --desktop_file_hint=unity8 or -- --desktop_file_hint=unity8 to a regular binary you want to open. This is the syntax: ./application -- --desktop_file_hint=unity8 Unfortunately the game crashes because of some OpenGL problem that I don't know how to solve yet: library "/vendor/lib/egl/libGLESv2S3D_adreno.so" not found ----- Initializing OpenGL ----- Initializing OpenGL subsystem Using 8 color bits, 24 depth, 8 stencil display shutting down: Unable to initialize OpenGL (glAccum) idRenderSystem::Shutdown() Shutting down OpenGL subsystem Sys_Error: Unable to initialize OpenGL (glAccum) shutdown terminal support But that's an unrelated question that I should ask elsewhere.

@bq10_user can you try putting your device in bootloader mode and adding --bootstrap parameter to the command you're already using?

Nexus5 also ok on 532

@alexander Xda forum has info on how they unlocked the bootloader for pro5. Maybe there is more info on there. Also it depends on your comfort level.

Today I tried to listen to the latest Wayne and Joe audiocast using my M10 vivid tablet. Again the audio was distorted by a terrible vibrato. I then tried listening via the UT browser on the tablet. Still the distortion persisted. I then tried listening via firefox on my netbook and the audio was fine. Do other UT M10 tablet users also have this problem? Someone previously suggested that this may be an android audio driver problem. BTW, I don't have this problem with ogg, mp3, mp4, youtube, etc. If it is an android audio driver issue, is it likely to be updated in the future?

@dtarrant : Yesss ! Happy for you Best regards Pulsar33

@ziggutas you can follow the ongoing effort to compile Dekko2 for xenial here https://forums.ubports.com/topic/1477/dekko2-developer-community-thread/25 and here https://gitlab.com/dekkoproject/dekko/issues/ P.S. I'm using webmail until Dekko2 is ready

@markalexa What this means for you, if you really don't want to go back to Android, and the camera function is important to you, is to "downgrade" back to 15.04 until OTA-5 comes out.

@ayenack you're welcome. The necessary first step to port UT is to port it to Halium, and there's some WIP on some Motorola models as you can see here https://github.com/Halium/projectmanagement/issues?utf8=✓&q=is%3Aissue+is%3Aopen+motorola but if you want a UT device now, yes it's better to buy a supported device.