Hello,

I am Matthias, a long time C developer and FreeBSD enthusiast. More about me at http://www.unixarea.de/
I own a bunch of BQ E4.5 devices (all my family use them, we have no other smartphones) and a BQ FHD M10. I am (o was) an active member of the Ubuntu Touch community, beta tester of BQ's M10 and wrote a small booklet about the E4.5, it's here in English and Spanish. I'm short before flashing one of my E4.5 to UBports.

CU, Matthias

I ended up installing ubuntu touch stable today to my nexus 5 (hammerhead) with
https://github.com/MariusQuabeck/magic-device-tool

and I got ubuntu 15.04 (r13) (20170127-093441 / 20160603- )

and if I start the browser in phone it crashes at once. That is pretty bad.

I have noticed that the there is OTA-15 out, but I guess that the magic-device-tool did not give me that version. Or did it, how I can check it ?

And does anyone know if magic-device-tool images will be updated in near future ?

The most important thing to me is privacy. Not to be in the hand of Google or apple or windows or anyone else.
It haven't to be mainstream, but it have to respect me.
It is also important to me to use my device as long as I want, secure. And not have to by a new device. (I know this is kind of not realistic because it is in the nature of the things that operating systems need more powered devices when the develloping is going on)

In this context a verry huge thank you to the people of ubports and halium.

@sverzegnassi The new UX default Scope / screen mockup looks very nice.
Nonetheless, even though that the Scopes idea will be dumped, I would expect that we would like to show at least same information as before on the UX default screen. Meaning we will keep the function code of the Scopes and will throw away the UX parts.
So, when would you expect to get the new UX default screen running? How would we migrate from the Scopes to the new screen causing as less as possible loss of functionality (since at least IMHO some of the functionality of the scopes is really helpful)?

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

Hi
I need this app OpenVpn editor APP
http://news.softpedia.com/news/ubuntu-touch-openvpn-support-gets-a-prototype-ui-here-s-how-to-install-it-498543.shtml

@Flohack Well, I'm not worried by Qt itself: it's generally well-documented (property and method deprecations too), so anything can easily (in general) be set up to prevent issues.

The problem comes when we take in account UT-specific code, which makes usage of Qt private imports. I see, running 'grep' on my local folder where I keep all the UT code, that more than 10 components depend on them - including Unity8, the web browser, the Ubuntu UI Toolkit, the Ubuntu keyboard, and some Mir helper.

It means this software should be heavily tested in order to check if there's any regression. This is what Canonical used to do anytime they were moving to a newer version - IIRC they had to fix a few things when they moved to Xenial which uses Qt5.6.

A (partially) good news is that everything should have been already tested on Qt 5.6 and it should just work "out-of-the-box". Anyway I don't think there's any value in moving from the current patched version of Qt 5.4.x to another - as long as we stay on vivid, Qt 5.4 is not the problem.

I think this should be one of the main discussions after we've started to work on Xenial. Qt version, UITK, Unity8, Mir, and the package format are things extremely related each other. The only thing that I can say for sure is that it wouldn't be a problem if we were on Snaps, Flatpaks or Appimages, since they bundle a specific version of the required libraries... :/

If it needs one how about Utouch.

@SGCMarkus Welcome back!

You've missed a lot since you were last here. And by a lot, I mean a lot. Canonical dropped Ubuntu Touch about two months ago and we have taken over the OS. If you'd like a quick summary of what's happened since then, you might want to check out the blog starting on April 8th.

Yes, no access to sdcard and also no access to usb-drive on M10 FHD. I have no solution...

@Flohack, I could log in with my Ubuntu account in https://translate.ubports.com/ finally. Thank you.

@Andreas-Pokorny

Thank you for providing further informations about Mir. I wasn't aware that Canonical dropped the libhybris integration. And thanks for taking care of that!

Snaps
Point by point:

It's probably easier for me to explain with an example. The LibreOffice snap in the U.Store uses the "Home" interface, which was meant to be transitional. Now that Canonical has no plan for Ubuntu Personal, could we expect similar interfaces to be "standard"? Could they break (in terms of UX and security) the current UT/UP security model, which relies on ContentHub for content sharing?

Huh, when I used "content" I was referring to files, document, or more generically data. I wasn't aware of such interface.

Yeah, that was my fear. The only example I found for adding new interfaces is this one. My impression is that Snaps have been designed with a strong centralization, afaiu.

@walidham Hello, sorry no but you could ask on Telegram, maybe some of the devs are listening. I have not enough insight on these really specific problems...

@Flohack said in building for Nexus 7 deb:

@doniks Are those message causing trouble, why do you think?

The display is all garbled. It's not usable. The colors are off and the display scaling seems to be off - let me attach a foto:

I was just fishing in the dark for hints and stumbled over these log messages. I do not know whether they are related. The display is the actual problem.

@Flohack I know that any DBus call - except for some - is by default denied by AppArmor, therefore we should for sure update the confinement AA templates.
I think we'd probably need to define a new AppArmor profile for headless apps, in order to prevent e.g. usage of the UriHandler service

Thanks for the good news. Enjoy! :)

So I'm using this as a notebook to keep track and also share progress.

Today I tried out the rootfs of 9-20-2016 has the display corruption.
So backing off to 7-28-2016 works fine as far as the display goes.

Now to do some testing on it I need to set the rootfs writable to be able to install more packages but I struggle to remember the utility to do it with.

To be continued....

@zubozrout said in Installing Ubuntu on Nexus 7 2013 deb (LTE):

@doniks There is no way I know of. You are either stuck with not really functional flo's image or you flash the deb stuff on it again but you'll have to say good bye to the bluetooth and camera.

Yeah, seems like. I have switched back now by replacing the android lxc system.img inside the ubuntu system image in the new flo installation with the one from the ubports device.tar.xz . Camera and bluetooth gone, sound and video back, but ota13 remained.

Also, judging from the kernel configs, it seems that in the flo image there is a newer kernel, but I cant see any difference in the running system.

The only way to fix this is either to somehow compile the whole image on your own

I wouldnt mind doing it, Im just stuck. I was staring at repo manifests, Makefiles and lunch, brunch scripts, but I couldnt figure out what I would have to do to get the source tree I got with repo from either ubports or canonical to change it such that it builds a flo image. Also, I would suspect, that 'just' building it would only bring you to the point without bluetooth.

or ask the owner of this server for some help - if he would be kind enough to talk to you.

Didnt get very far there. Dont wanna put words in his mouth, but seems he doesnt have an N7, so he cant really test.

In any case, good luck - I was stuck at that point long enough to lose interest :(, that is the only reason why I got rid of my N7.

Thanks! Your tips where most helpful!

@DanChapman said in Dekko as click?:

@bq4.5 You just need to delete the ~/.cache/dekko.dekkoproject, ~/.config/dekko.dekkoproject and ~/.local/share/dekko.dekkoproject directories to reset to default.

And thanks! :-)

The website has links to the issue tracker and forum. :-)