@UniSuperBox said in Porting Ubuntu Touch on Samsung Nexus 10 Tablet:
The Tegra chipset's drivers just had too many issues. This isn't strictly to discourage you, just to let you know of the history.
Isn't Nexus 10 Exynos though?
2012 Nexus 7 (grouper) is Tegra, but there's only mention of Exynos on https://en.wikipedia.org/wiki/Nexus_10
@3arn0wl said in What's the situation with blue light filtering on Ubuntu Touch?:
I just saw this: http://jonls.dk/redshift/
I don't know if it would be of any use...
It doesn't support Mir/Wayland, and Mir/Wayland don't allow arbitrary apps access to the screen like that, so no, it's not really.
This is something that really needs to get baked into the system.
@3arn0wl said in Spreading Ubuntu Touch to the world:
To be honest, I don't think Jo/e average really cares about the technicalities of convergence... just the powerful outworking of it.
It doesn't matter whether they care or not. If we can't explain it in a way that makes them understand it, then when they talk about it in a way which does not include all the other parts, it undermines the goals.
Saying "this is convergence" for a thing that is not convergence, but rather is simply the windowed mode of unity8 shell, makes it more difficult to actually build a fully convergent system.
@gimenez Right, that can work, but I think "here is my phone plugged into a screen and I have windows" as the means of showing convergence, contributes too much to the false idea that that is in fact what convergence is, when in reality it is but a very small part of it.
@pparent I think you will be somewhat disappointed by that too, because no matter what, the phone is still not a PC.
There is a huge difference between Android and UT. The way UT works is because it has to run on top of Android kernels, and because it is meant to provide a more secure alternative to Android, that does provide the ability to run legacy linux apps in a container too.
There are a whole lot of things about traditional PC Linux distros that just do not make sense to keep doing in the modern world, regardless of device. And pureOS isn't going to change that on their phone.
@gimenez said in Spreading Ubuntu Touch to the world:
No clear idea of what is convergence. There are no demo for it, which is a pity, because it's cool and it works! The dedicated convergence page is too long Each paragraph almost re-says the same content. They are like 5 or 6 different (and graphically unconsistent) illustrations, but no demo, and no actual picture of what is it. It is not clear if it is a whished or a working feature... Still the image of safe in the header
Simply put, convergence means shell and apps are usable across a wide range of devices, including phones, tablets, and PCs, with the same security constraints.
Given this, convergence is still therefore not complete, and there are a few related points to make:
So, as you can see, it can be difficult to clearly present that in a very shiny way with demos and such, when it's still not yet all there.
@pparent This is not a good idea to do.
However, if one really needs to install debs in rootfs for some reason, such as using ubports-qa to test changes to system components from PRs, one can bind mount a directory in user writable partition on top of /var/cache/apt/archives
mkdir -p ~/aptcache
sudo mount --bind /home/phablet/aptcache /var/cache/apt
However, there will still be plenty of other issues if one wants to try to install from apt in rootfs, which is not supported, and it is strongly advised against doing so.
Hi. When you say "earpiece" here, do you mean a bluetooth headset? Or do you mean the speaker on the phone above the screen?
Is this a theoretical question, or a "what can we do today?" type of thing?
@Krille said in Binary apps/Flutter:
Flutter for desktop is based on GLFW, right?
Not exactly. See https://github.com/flutter/flutter/wiki/Desktop-shells :
The current Linux shell is a GLFW placeholder, to allow early experimentation. We would like to create a library that lets you embed Flutter regardless of whether you're using GTK+, Qt, wxWidgets, Motif, or another arbitrary toolkit for other parts of your application, but have not yet determined a good way to do that. Our current plan is to support GTK+ out of the box, in a way where adding support for other toolkits is straightforward.
Expect the APIs for the final shell to be radically different from the current implementation.
Looking deeper, it also seems that targets other than Android/iOS are not particularly well supported/documented. So, I think Flutter is not really an option at this time.
@jld3103 said in Binary apps/Flutter:
Is it possible to run binary apps on UT?
I don't quite understand the question. Yes, of course any armhf binary compiled against the appropriate ABIs of Ubuntu 16.04 + UBports repository if using Qt, can be run.
However, in the case of Flutter, you would not build a native application. I'm not 100% sure how it would work, but you'd need to use either the Web or React Native targets, and treat them sort of if they were HTML5 apps instead.
@trainailleur said in Security of data and passwords when phone is lost/stolen:
Older Android phones with bootloaders unlockable without authorization will always be vulnerable to having encrypted data pulled off-device for attack.
This is only true if the bootloader is already unlocked, or the device has a bug where unlocking the bootloader does not perform a system reset and destroy all data. Newer devices do not necessarily require "authorization" either, but just have a more complex process where you have to also set an option from within the booted Android system.
@3arn0wl said in Ok to leave apps open or should I close them when finished using them?:
This is one of the best design features of the OS, @Opolork - apps open in the background don't use any resources: They shouldn't drain your battery or slow your device down.
Not quite true. They do still take up space in RAM, even if they aren't actively using CPU, and that can slow the device down.
There's no "SIM Toolkit" support at all on UT, so I think there is no way to delete any contacts on SIM from UT currently.
@Opolork said in I don't see any 'OEM unlock' option in 'Developer options' on Fairphone 2.:
Hi dobey. What's the difference between recover mode and fastboot mode?
In recovery the kernel is up and adb is available. In fastboot it is only the bootloader, and adb will not work.
Think of fastboot like the BIOS stage of booting a PC.
@zubozrout Sure, it could be Morph, but then we'd still get the same demands of people wanting to run Firefox. If we can't ship a Firefox branded browser, then there really isn't much incentive to shipping something based on Firefox, when it's much easier to build something on an already existing engine that works fine on the platform.
If we built a browser based on Firefox engine we wouldn't be allowed to call it Firefox anyway. If you want to see a native Firefox like is on Android, for UT, the best way to get that is to work with the upstream Firefox for Android devs, and get a click built for UT from it as well.
Of course, there's also the problem that Firefox doesn't support Mir client protocol, so it would have to run under Xmir for now (which would be a pretty poor experience), or wait until new Mir/Unity8 is in so it can work via Wayland client protocol (assuming Firefox has wayland support already).
@Opolork said in I don't see any 'OEM unlock' option in 'Developer options' on Fairphone 2.:
I'm now in Team Win Recovery Project - do I just select Install?
If you are in recovery mode, you should be able to run adb reboot bootloader on your PC to put the phone in fastboot mode.
@Opolork said in I don't see any 'OEM unlock' option in 'Developer options' on Fairphone 2.:
Do I need to install the packages adb fastboot in Debian?
Yes, these are required.
@Okkie said in Ubuntu Touch Q&A 53 Saturday 29th June At 19:00 UTC:
Is there a build of ubports he can get his hands on?
Lukasz is in our community and I'm pretty sure is well aware of the status. My understanding is that there are still some issues with graphics with mir/unity8, but it's being worked on. The rootfs for the PinePhone is also built from edge channel, so it's using new unity8/mir already. I think it's also using the arm64 rootfs, so there may be some additional hindrances from that, as Canonical never released a fully working 16.04 arm64 image on anything.