Ubuntu Touch
Free as in yours

@Macadam About the Sturm Reader margin issue, the size of the margin is a setting you can adjust in the book style settings (the button at the bottom of the book page swiping up). Maybe it has been set to a too big value?

If your goal is to read e-books on Ubuntu Touch, have you tried the native reader applications in the Open Store such as Sturm Reader or EPubViewer?

@AppLee thank you!

Hi all!
Looks like my app Sturm Reader crashes on start on arm64 devices... Maybe it is because I still use the old com.canonical.Oxide API. If someone with a arm64 device could download it from the Open Store and send me logs would be amazing!!! Thanks

Just followed the procedure on my OPO and it has gone flawlessly! Apps don't launch always, thought. I once opened the settings app successfully, but now every app crashes right after lauching.

@Stefano said in Can't install Ubuntu Touch/Ubports on Nexus 7 flo.:

block

Have you tried to change the usb cable?

@ControlledCorpse
Just install the Desktop App Scope from the Canonical scope, and you will see your installed apps there

@UniSuperBox
If we are going to move to ReadTheDoc and remove the current wiki, I think is better to go with ReStructuredText straight to RTD.

I think you are right planning to reorganize the wiki. I think I will help if you like.
Your sheme is the more logical solution as far as I can say. Anyway, I would add a section like "Daily Use" or something like that, oriented to non-developer users where is explained how to use non-obvious features of ubuntu touch (like for example the already existent guides about CalDav and Libertine). Maybe that is supposed to be the "Documentation" section?

Check out the wiki article I written about it:
here

@happyzenith
at the moment there are some problems with Loqui, but there are also some workaround solutions.
Join the telegram group of Loqui https://telegram.me/joinchat/BlpqfQk1L0l0PJTnM02yxQ and ask there if you want real time support.

I translate to Italian, very short post just to say this.

1-2-3-4) The answer will cover all the four points.
I would leave outside my post the need of the File Manager app by hackers, coders, testers, developers, computer enthusiasts, ... this is an actually important point but I won't cover it here. So, speaking about standard users:
In a perfect containerized ecosystem there is no need for a File Manager. Each app should be perfectly capable to handle their data in a fast and transparent way, the user should not even know about single file operations at the bottom of the hierarchy pyramid of abstraction provided by a perfectly isolated system. For example, when downloading a file, he shouldn't care about where physically is stored the file, but he just cares about accessing it with others apps. Anyway, a perfectly isolated system would be the heaven, and we are on the Earth. Even a perfectly isolated system would deal sometimes with external data which cannot parse (a old backup USB key filled with tons of mess) and apps would not always provide all the functionality to accomplish everything a user wants to do with the data, or an app could not be containerized at all !! For example current apps for desktop running on ut are not containerized, Libertine can provide some containerizationish, but not complete at all. Another example is the gallery app which still can't move photo from and to the SD card ( yet ). To fill these holes, here the file manager comes. It put the user a level below the abstraction stage he should be when he uses a containerized system, where it can manually do what the apps miss to do, bypassing and working below all the container and limitation infrastructure. (this not in the meaning of security threat: the goal is to do what apps miss to do, not what the container framework prevents to do. Security is a very long topic, and I won't consider security implications now). Basically he can behave in the same way he would do in a non containerized system, like classic desktop/server ones. For this reason, the file manager app should ignore limits due to containerization and being just a normal file manager, like every FM else. Surely, thought the convergent goal of ut, it should have an UI working on both desktop and phones, but this is speaking about how it should look like, not how it should work like.
What I said here also apply to the terminal app.
I hope I explained how I see the topic cleary, but as I am not a native speaker, I would answer if someone miss some meanings.

I know I could just install some package, in fact my request is to make these little packages already installled by default in future OTAs.

There is any hope to see FUSE support in future OTAs? In OTA 1 there is no such support as far as I have tested. This is an issue when dealing for example with AppImage apps; they could be a good way to use programs on ubuntu touch without containers until better solutions are implemented, but without FUSE support they can't work. The only drawback will be just a little increasing of the image size, but we can have many more advantages with it installed.

Good guide . Would be nice to have it in the ubports wiki...

@mikhael
Cordova uses very old components, and as far as I read who tried to use Cordova to create HTML5 app found problems, and in most cases headed back to standard HTML5 template app. HTML5 apps can use content-hub to import files, but not to export them.

There are many good HTML5 apps for ubuntu touch. Examples I use daily are: Turtl UT and LoquiIM, but I am sure there are more. But they have a great limitation in their functionalities: they can't export data to the internal storage. For example in Loqui when someone send me a media I can't save it in the gallery, same for Turtl or any HTML5 app. A good solution is to make a new permission option, like camera, microphone or position access, capable of enable content-hub export access like normal apps.