Thanks for that pointer, applying it to my Hammerhead tree did permit a build. What would have been my "hands on" Nexus 5 is busy with some highly interesting notification experiments, but I'll see if my built images boot RSN.
since a young developer provided a Lineage OS 13.0 version for BQ Aquarius E4.5 maybe one could use this as a base to get a newer kernel?
I am not exactly sure what kernel version and what else is needed to get 16.04 working on Krillin but any insight in the requirements for porting to 16.04 would be heartily appreciated.
When I read the title of this post, I started to get concerned. Was something going on, that I was not aware of, was the tablet going? Thankfully the answer to that is no. For me, the os on the tablet is the main thing. That being because it is all I use now, but to lose the os/support would be out of the question
I have a similar issue with one of my M10 tablets. When I reboot it on restart it does not seem to be able to pick up the Wi-Fi. Everything else I have connects easy to it, but for some reason not this one tablet. The other Ubuntu Touch tablet that I have connects all OK. How strange, it is affecting just one of them.
The only thing I can do is go into Wi-Fi settings, like I am going to add it again. Then before I have chance to add it, it shows as connected in the Settings list. Then it will appear in the notifications bar. I tried waiting for it to connect, thinking that it was taking a long time to auto connect, but this did not work. Only going into settings connects it for me.
@nfsprodriver I can't speak for the webbrowser-app, but I recall that many dirty things have been done in filemanager-app, especially with the color palette. To be honest, filemanager-app needs to be re-written almost from scratch, since there are many strange things in the code.
Just a call to action: if there's someone in the community who would like to address its issues, I guess that any help would be very appreciated from the UBports' guys 🙂
@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