Add documentation to the ubports docs!

UBports Docs

Videos and podcasts are flashy, but good documentation is invaluable.

Once you start using the ui you will never see that empty space again.

Trust the developers, this is good.

I am feeling brave and my OPO has been dropped too many times for comfort, so I decided why the heck not...

It'll be my first new phone since I bought a Nexus 5 back in the stone ages!

It feels like there needs to be a consolidated thread to discuss the Pinephone Braveheart development and since it is tacked under 'Community Ports' on GitLab this seems the best place for now, so here goes. I am in no way an expert so don't expect me to know much, but I am willing to collate information and update this first post as things evolve.

Feel free to suggest information to add.

Installation:
Current Instructions:
@UniSuperBox said in Pinephone tutorial:

1. Download the rootfs image from https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/
2. Extract and write the image to an SD card
3. Plug SD card into phone
4. Boot phone

That should do it.

Updating:
Download latest rootfs, flash to sd card.

Sources:
Kernel
rootfs Download

Issue Tracking:
GitLab Repository

Other Threads:
Pinephone Tutorial
How can we help with the Pinephone?
How I am running ubports as a daily driver

Misc Links:
setting-the-record-straight-pinephone-misconceptions
Pinephone @ pine64.org

Status:
Pinephone Repository Readme

I hope this isn't out of place, but I'm curious if there is some sort of roadmap for UT development. Is there a strategic plan, so to say, that after 'x' we will work on 'y'?

What comes after Unity8+Mir for example?

I'd just like to know what the Foundation's vision is for where this ends up and how we might get there.

This is tangential, but I feel it relevant to the discussion of apps.

I feel this is what @3arn0wl was getting at:
I think the current app that best represents what the community at large is in need of is Pure Maps. It is well designed, runs natively, and has been portable to multiple OS's. If there is a gold standard, it involves these criteria. I know there are others, I just don't know them off-hand.

If the Linux mobile ecosystem had enough apps like that we wouldn't need Libertine and Anbox. At least in a philisophical way, to avoid derailing the discussion.

@Marathon2422
I would assume that is the plan, but I doubt it will happen until the port is past initial testing.

I wish you success!

When can I buy one! Lol.

Indeed! Morph just keeps getting better.

On my Android devices and a computer the map loads fine. On UT it is blank regardless of browser.

I had thought it was to do with a lack of WebGL in Morph, but have nothing to prove it.

@mito77 the best I can offer is to install Logviewer from the Open Store, then check the morph log after failing to log in. That may give you more info.

Out of curiousity I went and tested Morph, and it does surprisingly well:

So knowing nothing else, I suspect your trouble is a bug.

@Opolork as a non-programmer (like me) learning how to deal with Github, especially 'issues' is a great thing you can do and learn easily. I find 9/10 when I report a new bug, the maintainer has never encountered it themselves and are thankful for a heads up.

As a consumer in the open source software arena, this is I feel a minimum requirement skill for full participation. Definitely worth learning.

@poVoq I think qtwebengine is currently the trouble. Building a front-end for Jitsi using qtMultimedia might be more likely... I have been trying to learn using QML creator in free time, but I'd say I'm only currently at 1% progress

@AppLee I really feel the solution should be to fix the issue with Morph. But I'm speaking with no technical knowledge, just knowing that a general consmer would expect the system web-browser of any phone to have access to the cameras.

I recall seeing an issue regarding this on the Morph repository...
edit
found it:
morph #62

@Fla when the phone first started shipping those steps were necessary to make certain hardware function, and I think the information is relevant even if they have subsequently been fixed by updates. The low level command line stuff there might prove useful in troubleshooting.

I have been neck deep in school work so I really don't know if modem and sound are fixed in the latest builds.

@dobey
that makes more sense, I was confused by the alpine package thing. I might have to give it a try, and gtk be damned as I only use CL apps in a container anyways.

I found that there is a version of Firefox modded for small screens for postmarketOS, see:
Firefox - postmarketOS

But I have no idea how we would install an alpine package in a Libertine container.

@Fla yes, it is basically a factory reset. I assume this will be fixed when the Pinephone is transitioned to image based updates.