Add documentation to the ubports docs!
Videos and podcasts are flashy, but good documentation is invaluable.
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.
- Download the rootfs image from https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/
- Extract and write the image to an SD card
- Plug SD card into phone
- Boot phone
That should do it.
Download latest rootfs, flash to sd card.
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.
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.
@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.
@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...
@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.