PinePhone



  • @PINE64 You are indeed right when i consider the data you provided me: my reasoning was based on the fact that a large part of the tests had already been done, whether at the hardware or software level, concerning a special 3 GB RAM edition.
    I extrapolate but maybe later for this special edition?!



  • @domubpkm There will be multiple 'special' editions - for each partner project.



  • @Flohack said in PinePhone:

    @B2288 That will happen very late, as currently we do not have final dev builds. But we will keep you posted ;)

    I'm sorry if I'm not understanding, but does "that will happen very late" mean that it will take a long time for Ubuntu Touch to be available (even as beta release) even after the PinePhone BraveHeart release? Even longer than the mass production release? Just curious if there are estimates...



  • @orthocube Fully working devices with OS versions should be ready for March next year as things stand



  • @Lakotaubp But I intend to help in testing. If even beta versions of OSes are not released during the BraveHeart release, how can I even help test and submit bug reports?





  • @orthocube,
    Quick answer : the installer is a convenience for end users to facilitate flashing a device.

    For "more advanced" users who wants to debug and help testing the method will be closer to development methods.
    But in case of the PinePhone it will be quite easy first steps are the same as installing an OS for the raspberry pi ; flashing a SD card with dd command. Then I guess there will be something like a bootloader allowing to boot from the SD card or to flash the device using the image on SD card.



  • UniSuperBox 4 days ago

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

    That should do it.

    Copied from @Universalsuperbox post in the other thread, how to get OS on to PinePhone

    https://forums.ubports.com/topic/3334/pinephone-tutorial/3



  • @AppLee @Lakotaubp

    Thanks for the reply, and I'm sorry for the dumb question XD

    I was wandering around the UBPorts website looking for a download link to the image so I thought it isn't available to the public. Tried searching Google too, but didn't find that information.

    (Download link seems to be down at the moment but I imagine it'll be up again anytime soon.)
    Thanks again!



  • @orthocube There is no such thing as a dumb question ;)



  • @PINE64 said in PinePhone:

    The following is just my guess: most users will end up using either UT or SailfishOS. At least initially.

    UT or SailfishOS? I know that the Pinephone already allows for booting a secondary system from an SD card, which is cool. But how about offering a way to multi-boot from internal storage? That would be super cool. :smiling_face_with_sunglasses:

    Down the road I think that Replicant will have a big install base.

    Yep. And although I won't score many upvotes for saying so, if I owned a Pinephone, provided I had an easy way to install and boot both, I'd probably install Ubuntu Touch and Replicant (Android) to the internal storage. I'd use UT whenever practical. But I'd likely need to boot into Replicant at least occasionally until Anbox is better supported.



  • @GizmoChicken I would assume though that this will be easier to do but I don't know the technicalities so I might be wrong. But I agree that it would be cool to multi-boot. 16GB of internal storage can be a little low though.
    My 32GB Nexus 5 has Android, Sailfish OS and 3 UT and it's almost full 😅



  • @kugiigi 16GB for android is a very narrow storage.
    System requires at least 5GB and apps take a huge lot, for few apps you can count 6GB for your data and alternative OS that's not enough.
    Moving apps to SD card is not always possible on android and there's still data stored on the main internal storage.

    But I agree multiboot would be a cool feature, but I guess for later "special edition".



  • @AppLee said in PinePhone:

    @kugiigi 16GB for android is a very narrow storage.

    I think that's the point that @kugiigi was making. And I agree with both of you. :)

    Even so, I think that a way to multi-boot from internal storage (even if only 16GB at present) should be offered in the initial model, or as soon as possible, as a proof-of-concept. If successful, PinePhone will have more incentive to offer upgraded models with larger internal storage.



  • I have thought that you can boot a system from the SD Card as well.



  • @makeixo said in PinePhone:

    I have thought that you can boot a system from the SD Card as well.

    Yes, you can boot the PinePhone from an SD card. But SD cards are typically slower, and less reliable, than internal storage.



  • Question: Will libhybris be required for running UT on the PinePhone?

    I'm under the impression that libhybris will not be required for running UT on the PinePhone, but maybe I'm wrong. I hope someone will confirm here with certainty.

    EDIT: According to this post, libhybris is, indeed, not required for running UT on the PinePhone. Yippie! :relieved_face:



  • Hi all,
    For those of you happy to help with development and testing, the PinePhone early batch (Brave Heart) edition are now available on our store. Do note: if you want an end-user ready phone DO NOT buy it.



  • @PINE64 Please, can you give more details or clarify this:

    « Small numbers (1-3) of stuck or dead pixels are a characteristic of LCD screens. These are normal and should not be considered a defect. »

    You mean: every third pixel?

    Is it all about the phones or is it just the «fruit of chance » ?

    Does this defective pixel characteristic only concern this edition or will it also concern the completed edition in March?

    Thank you.



  • @domubpkm honestly, it doesn't mean anything. I am yet to see a single person complain about dead pixels on the Pinebook / Pro or any other LCD display we've shipped. But its a 1-1000 chance (actual stats) that there will be a dead pixel on a shipped unit, and we cannot control this, and we won't replace units with a dead pixel.


Log in to reply