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.
flashing OS to emmc
Go to: Settings -> Updates
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.
@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.
Having read the promotional material for that app... Doesn't it just encourage people to have gatherings indoors, exactly where they shouldn't?
There's a bad marketing vibe going on; want to party at the club? Go ahead, you've got an app for that! I'm not criticising your choices, but your government seems out to lunch if they think this app will encourage safe social gatherings...
@dobey I couldn't (nor would) hold back progress, and your additions to my list of one item are exactly the sort of thing I hoped to draw out.
For the record, I am fully in support of continued development of Morph , and being on a Pinephone now I have stepped past oxide whether I wanted to or not.
@TotalSonic but can it keep a lock and update as your location changes?
I ask honestly as the last time I tried in Morph 4 months ago, it did not work. I understand Oxide containers are old and have to go, but we should be sure the replacement functions fully. This is the only use case I had for an Oxide base app, everything else is handled very nicely by Morph.
Oxide is the only one that works properly with the location service...
I have not tested since I crushed my OPO and started using a Pinephone though.
There is (was?) an oxide based webapp for google maps and it was the only one that properly locked location and tracked along. Morph (before the recent engine change) would lock location then freeze the location service and not update again, often requiring a reboot. It was the same for all web-based maps I tried.
Can the current morph maintain a location lock on a webpage?
It is not like a global back command would suddenly solve this problem; every app would need to implement what 'back' means to it. The inconsistent nature of what back means on an Android system is always a frustration to me, and I think it solves fewer problems than it causes.
Sure in Morph it would be very obvious what back does, but I'd argue that an option to move the navigation bar to the bottom edge would be more useful. Half of the apps I regularly use don't have an obvious 'back' action; what should 'back' do when I'm viewing maps in Pure Maps, or when typing into the calculator? I agree with others that each app should consider this as oppsed to forcing a global option.
Back and Home are UI hangovers that have been improved away by the Lomiri UI.