@altr0n I managed to get my own kernel compiled, the issue was that I did not have a console argument specified that I needed (I founded it on another post here) console=tty0 Needed to be added to my kernel command line args. Hope this is useful to someone in the future!

@sverzegnassi , one problem i have after trying this development version of the file manager is that both *.mp4 and *.MOV files are played back heavily in pink color after installing it, and the problem does not go away when i uninstalling it either. I posted about it here as well, https://forums.ubports.com/topic/600/cannot-play-the-old-mov-made-by-the-canonical-image/4 , but did not get any suggestions on how to fix it. Do you have any ideas what went wrong and how to fix it?

@Galaxia said in Daily usable ?: The only thing not working consistently is mobile data on ATT network. Once the phones manages to establish a mobile data connection it works great, but as soon as the phone stops using data, the connection silently drops. I have to toggle Cellular data on/off a bunch of times to get it working again. Weird. I'm on AT&T (well, Red Pocket, AT&T network) and I believe I've seen what you're seeing, but only rarely--under the hood it appears to be an issue with the default network metric. But I can go for days jumping to cell and back to wifi at various locations without seeing it, whereas it sounds like it's biting you every time.

@Math Hello, we did not yet commit anything to the stable updates. Probably it will be done with a configuration option, but not decided yet. BR

Ok, dug through the source to obports-installer, looks like most of the goodies hang off of: https://system-image.ubports.com In particular: https://system-image.ubports.com/ubports-touch/16.04/devel/hammerhead/index.json which tells you where to get bits for various versions. The latest, currently 72, says that there's bits at : /pool/device-e34756d822387fa9371568fa42292f8baf76d79ec7f2cee0f5c002b909dc08f5.delta-device-cc610cfc131187e182588a0f9c7c5c23ba769679708a4ba08b16878f4e93c101.tar.xz which, once you pull it and "xzcat device-e3* | tar -xvf -" will give you boot, recovery, and system img files. I booted just to the bootloader and fastboot flash'ed those partitions, and my phone still boots OK. So I guess I'm at least sorta on the right track....

Hmmm its quite funny that our nexus 5 is a bluetooth speaker for other phones xd. But ive have send a file. Just turn off on other phone music streamming to your nexus, an then use program, bluetooth file transfer. In this way i could send files to other phone. Not tested it in back way, i mean send file to nexus 5. U can do this and inform us :D. It should work, you can read this feature in app.

@grepo I thought I'd installed UBPorts using the magic-device-tool method - but if I see OS build number: OTA-15, does that mean it didn't work? I'm also using a BQ E4.5 EDIT: I used the system-image server method and it has now installed correctly. The magic-device-tool doesn't seem to work properly?

Update the phone to OTA2 through automatic update, and the phone's operation has improved a lot.

If you go to Github.com you can create an account there and then go to issues and raise another. When creating it gives you the option to ađdo issue or new feature.

Same here for both my M10 and E5. I did however have to go into settings and manually force the download, even though I had download update to do automatically on wi-fi.

That pointer to their developer documentation on Oxide is very useful! If anybody with connections back to Ubuntu can pass the word, the "Updating the Chromium version" text just has "TBD". For the long-term viability of UBports, it would be amazingly helpful if a Ubuntu wizard could fill in some details there!

It doesn't exist, at the moment.

Man! You just made me soo happy... Perfekt! Many thanks!