Add documentation to the ubports docs!

UBports Docs

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

@Giiba and the ability to video chat/conference.

WebGL

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.

SD Card Installation:
@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.

Emmc Installation:
flashing OS to emmc

Updating:
Go to: Settings -> Updates

Sources:
Kernel
rootfs Download

Issue Tracking:
GitLab Repository

Other Threads:
Pinephone Tutorial
How can we help with the Pinephone?

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.

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

Trust the developers, this is good.

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

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!

I wish you success!

@domubpkm aw, come on. Having to stop and start ofono to make a call seems totally ready for daily driving

If you want the most from a Pinephone atm the development channel really is the place to be. In the past 3 weeks I have seen it go from hot all the time with no battery longevity and flakey connectivity, to actually cool to the touch sometimes and reliable connectivity if I handle the mobile/wifi switching myself. Progress is slow but steady, and I think the devs have a lot to be proud of. My BH edition was nigh unusable and had to be powered off to charge as the modem just sucked power all the time when I first got it.

Now, if dtmf codes would send while in a call, I could survive the Pinephone as a daily driver (survive, not flourish). Frankly I'm impressed with where we are at and it is only getting better.

Wouldn't it be possible for banks to do this the same way so many sites do? We have two authenticator apps on the store for UT, they work fine for Mozilla, Google, and other sites that do 2FA.

I'm able to use my bank's website through Morph to do my banking without issue.

@thepossessor Do you have a link to the instructions?

My Pinephone and new mainboard have been sitting in a drawer for the past month, and I came here because I was planning to do the swap tonight.

I'm having a hard time seeing the controversy here.

Anyone correct me if I'm wrong, but as I understand this there are two things the OS does to 'phone home':
1 - a connectivity check which would include a browser user-agent string
2 - phone model and os version/channel - because it needs this info get the right files to do OTA updates

I guess one isn't opt in, but is kinda necessary for a connected device OS, and two is opt-in. It sounds like Ubports keeps a simple record of the above info.

The website should not be confused with the phoning home. That's a separate issue.

Ordered one myself. Slightly pricey but for a project I'm happy to support.

There is also always the wonkiness of adb and fastboot, trying a different usb cable or another computer is sometimes a good bet.

@lduboeuf
MMS is extremely common in Canada too. I've switch a device back to Android for the next few weeks because I need to reliably recieve some MMS's.

By basic I mean expected minimum feature set for a simple user. In Canada it would be GSM/LTE, SMS, MMS, and a camera. No one in my sphere is interested in UT simply because they use MMS too much.

I certainly don't intend to imply anything is 'simple' to implement. Reminds me of the Captive Portal issue, where I've gotten good at figuring out the right address but sure have no idea how other systems guess at this... but they do get it right all the time.

@Tellina said in OTA-14 Call for Testing:

But for many entries I had no clue how to verify them. Maybe some are quite technical and I was even not aware of the existence of them at all.

Just doing your normal activities and pulling up less used apps is testing, no news, is good news. Then report any issues arising after the change.

As a novice techie most all of these things are over my head, and my experience has been RC channel is remarkably stable. These devs are good at that.

@mcappa2
I played with this a bit to compile Rust code. You can find my results here:
https://forums.ubports.com/topic/3581/compiling-rust-code-on-ut

The most important part was putting files in a directory that Libertine can access; ~/Documents is an easy choice for that as it is simple to locate in either system.

@Flohack
Thanks for the insight, it makes more sense now and would seem to justify @lduboeuf 's solution. A person should at least know something was missed.

@lduboeuf

I have to agree something is better than nothing... I'm hoping the efforts to update ofono bear fruit for this long standing issue.

Does anyone know why fixing this rather basic feature has been so long without resolution?

As for the error text, I feel the wording should properly place blame on the OS as opposed to making it sound as if the sender is at fault

Something like:

Oops, there has been an error with the MMS system and this message could not be retrieved.
Please ensure Cellular Data is ON and MMS settings are correct, then ask the sender to try again.