For those interested I would like to add these two links about the progress:
https://github.com/ubports/ubuntu-touch/issues/384
https://github.com/ubports/ubuntu-touch/issues/398

I think that's a good solution. Thanks to this UT community can have some influence on the next update packages.

@marathon2422 Oh, no at all. I understand that what I've installed is not recommended for daily use. I was just curious whether the issues I've mentioned are also present on other devices as well.

In any case the fact 16.04 is available for MX4 I haven't even hoped for is a good enough reason for me to at least play with it for a few days :). And since I've been mostly on Android after Canonical decided not to continue with the project I've found a really easy way to dualboot between both systems: https://iubuntu.cz/dualboot-mx4.html so I plan to keep 16.04 and add Android as another option once I install it again.

Oh... It seems I've assumed, that there was some kind of black magic switching channels for me... A compelling case of rtfm (respectively wiki) - I'm sorry... 😕

Hi,

sorry for OTA-3 its much too late to add any features, we are already late with it and cannot risk to postpone it longer.

Also from my point of view this needs a wider discussion since you propose to change the kernel only for one device. We don´t like to have such functions only on one piece of hardware, it creates confusion and additional QA problems etc.

If you propose such a change, file an issue on our ubports "ubuntu-touch" tracker in Github, but please be as specifica as possible, the best would be to suggest the kernel options that are missing. Then we can get into discussion about this.

BR

More updates today and the the m10 on RC channel is now really working smoothly and quick. Going to try nexus 5 and bq5 next. Well done to all involved for the continuing time and effort.

@Talkless Had forgotten mine are now on RC channel not stable and updated to r14 yesterday. Or am I getting mixed up with things and OTA's.

@demokrit said in Simulating a "Ubports" 16.04 on x86 hardware (or VM) - work in progress:

mhhmm ... when you say Unity 7 + X11 you mean .... without mir .... so which UT apps run without mir .... maybe I'm not understanding you right.

I meant that i build some apps that are currently only packaged as clicks for the phone from source in an 16.04.3 x86_64 on unity7 atop X11

As of yet i could successfully build and start OpenStore, Clock-App and InstantFX

I'm really surprised! I was quite convinced that a UT "phone" app, ie, an app developed and built against the ubuntu sdk would require mir. But you the way you describe it you have these apps running on 16.04, unity 7, ie, X! This is really blowing my mind.

I guess they work since they rely on Qt which also works on X11 not only on mir but i don't really know that stuff.

Seems like. I'm really, really surprised.

Ah one more thing; i tried building locally with Yunit installed and interestingly there seems to be a Problem with mir so i cannot start the OpenStore (the irony is somewhat bugging me). Haven't tried with another App, i will report as soon as there is more news.

Strange indeed. Do you have the error still at hand?

From Community Update 15:

People have been asking about the KRACK and BlueBorne vulnerabilities lately, and for good reason. These are highly public explots. Both have been fixed in the RC and Devel channels, with the fixes landing in Stable with the next OTA.

Yay!

Marking this thread as solved.

See https://github.com/ubports/ubuntu-touch/issues/327 - this is for the next OTA-3 and its already marked as done 😉

BR

Compatability has to be in the core in some form.

To me theres no realistic way without compatability.

I gave up on my ubuntu mx4 and now use the mx meizu flyme android because of............the money.

Not linux/Android/freedom, like/dislike discussions, but simply because I would have to have two phones: To operate with my banking, reading danish newspapers, see danish television, use the danish mobilePay, use the phone with online ticketing for bus/train - a lot of stuff that has nothing to do with "hobbyist" fiddling with philosophical linux/windows/android speculations but all to do with very everyday digitalizations of very soon everything in daily life.

And all those local institutions in all countries are NOT going to create linux compatible versions of their apps.
But they are going to be even more necessary to have access to.

That leaves the discussions with no choice - if the UBport is going to be anything else than a utopian/idealistic project, it will have to cooperate with a lot of android apps.

Only yesterday I visited the Ubuntu Store and downloaded a few apps. One I find great is the facebook app in there. It is so much better than the face book basic option in the Open Store. We really need to get all the apps in the Ubuntu Store over to the Open Store.

@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.