PinePhone



  • Is anything known already about flashing Ubuntu Touch from the SD card to the eMMC storage? When I receive my Brave Heart, I would not be comfortable with a factory (probably blob-ridden Android) ROM being present. Right now, the PINE64 wiki page states that installation to eMMC requires a magic script yet to be written.

    Is anybody working on writing said magic script?



  • This post is deleted!


  • @the7thstranger Two things: 1) Brave Heart will likely ship with a Linux factory test image and 2) I'll put together a 'rough' SD->eMMC image in time for when phones are delivered later this month.



  • It seems that BraveHeart is sold out.
    I heard about someone who tried to order one and got this notice :

    Sorry, we do not have enough "PINEPHONE - “BraveHeart” Limited Edition Linux SmartPhone for early adopters" in stock to fulfill your order right now



  • @AppLee Yes

    screenshot20200109_214415285.png

    That said, after a skillful mathematical calculation:
    (4320/60)/24, it might be possible to try that chance again after three days!



  • I really thought it will sell out in just days after launch. I wonder if only 3k were really sold for BraveHeart Edition.



  • @kugiigi I have thought the same but lets hope for the best and the PP will be a big success!



  • Answering the question regarding pace of PinePhone BH sales. There are two ways to look at it - a positive way and a less positive way.

    A positive way to look at it is that people (potential end-users) understood that at this point in time the phone is meant for technically capable enthusiasts, who can contribute to the development and testing processes. So, in other words, people correctly held back from getting a PinePhone until the software matures a bit, reviews come out, and we (PINE64 + Developers) tell them that it now good for the average end-user to have as a daily driver.

    A less positive view to take is that people say that they want a Linux phone, but in reality are not quite able to let go of their Android for iOS phones. There may be other reasons too: they don't think that PinePhone will deliverer the performance they want; they believe in some of the misconceptions which are floating around online; or simply that interest in a device doesn't mean putting down money to buy it. Whatever the case, there may be fewer people actually interested in purchasing one than we all anticipated.

    I choose to believe that its the prior rather than the latter option. I think we did a good job communicating about the BH batch and people listened. Still, this remains to be seen.



  • @PINE64 I'm SURE people will buy the finished product because the development potential is great.
    As far as the BH batch is concerned, even if peophe understood what was BH, human nature always has doubt in it by nature : In my opinion these two questions: is the BH telephone the finished product from a material point of view? From the software point of view, will the upgrade to the first stable edition be easy? which is why there may have been some hesitation to purchase BH.



  • @PINE64 I'm waiting for the final version of Pinephone. I'm very excited. I want to buy Ubuntu Touch version for me and my girlfriend. She wants Linux phone too because Google is spying us more and more. I've used Linux laptop with Ubuntu for personal use and for work more than 10 years. And I have Bq Aquaris 10 FHD with Ubuntu Touch. I'm a Linux guy but I want to buy a stable version of Linux phone. And for my girlfriend, I need a stable version, it's necessary. I believe I'm not alone who's waiting for a stable version. I hope it will be soon ready.



  • @kugiigi
    I heard the braveheart "run" was only 3,000 devices.



  • @PINE64 said in PinePhone:

    Answering the question regarding pace of PinePhone BH sales. There are two ways to look at it - a positive way and a less positive way.

    The BH edition took a little more time to sell than I initially thought, but hey, it did get sold out, right? So I think this is really good news, and encouraging for the next phase. The more so if you guys manage to have the
    attachable keyboard ready by then. I'm sure it's going to be a huge inticement!

    Fact is, I had the PinePhone product page opened up in a tab of my phone's browser for a few days, when I finally decided to take the plunge it was too late 😄 (I wouldn't have hesitated if the keyboard had been available as well!)

    What has me most concerned is not the hardware, but the software. As far as I understand it, UT is the FOSS OS the most ready, and already in use (it's been my daily driver for the past 3-4 months). But it's riddled with annoyances and missing important stuff that means one must really, really be dedicated to use it. Not unlike the state of desktop Linux 12 years ago. I fear it may deter a lot of potential buyers once the final PinePhone is released.



  • @PINE64 said in PinePhone:

    A positive way to look at it is that people (potential end-users) understood that at this point in time the phone is meant for technically capable enthusiasts, who can contribute to the development and testing processes.

    All things considered, I think it's good sign that you've sold as many "“BraveHeart” edition phones as you have. Congratulations!

    @PINE64 said in PinePhone:

    A less positive view to take is that people say that they want a Linux phone, but in reality are not quite able to let go of their Android for iOS phones.

    Although it's a good sign that you've sold as many as many "BraveHeart” edition phones as you have, I think that you'd be wise to hedge your bets by offering a way to dual boot between a pure Linux OS and Android from internal storage.

    In my case, as I mentioned before, I'd be more likely to buy a Pinephone if I could install, and dual boot between, 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, at least until Anbox is better supported by UT.

    I realize that you have plenty of other priorities, but I hope that offering a way to install at least two operating systems, and dual boot between them, is among your priorities.



  • @GizmoChicken, all software is up to the community. We get support from Pine64 through specifications or (limited) access to engineers from component manufacturers, but Pine64 does not make software.

    So if you'd like to see a dual-boot option, it's time to jump in!



  • @UniSuperBox said in PinePhone:

    all software is up to the community. We get support from Pine64 through specifications or (limited) access to engineers from component manufacturers, but Pine64 does not make software.

    You aren't seriously suggesting that Pine64 relies on "the community" for every aspect of the boot process, are you?

    In any case, in a post asking about a whether @PINE64 would be providing a script for installing to eMMC, @PINE64 stated: "I'll put together a 'rough' SD->eMMC image in time for when phones are delivered later this month." So @PINE64 seems to have more control over what will ship on the PinePhone than you seem realize.

    @UniSuperBox said in PinePhone:

    So if you'd like to see a dual-boot option, it's time to jump in!

    I'm suggesting here, to @PINE64 (not to the UT devs), a feature that I feel would be welcomed by potential customers of his company. By doing so, I've jumped. 🙂



  • I agree that the dual boot to Android option should be probably advertised to hedge with people unsure if they want to make the leap.

    I am guessing, but it seems likely that you can already dual boot by swapping in a SD card with another system image and images for the Pine A64 should be reasonably close to get at least WiFi connectivity (cellular modem might be another story). For the A64 there are Android7 images: https://wiki.pine64.org/index.php/SOPINE_Software_Release



  • @GizmoChicken said in PinePhone:

    You aren't seriously suggesting that Pine64 relies on "the community" for every aspect of the boot process, are you?

    [...] in a post asking about a whether @PINE64 would be providing a script for installing to eMMC, @PINE64 stated: "I'll put together a 'rough' SD->eMMC image in time for when phones are delivered later this month." So @PINE64 seems to have more control over what will ship on the PinePhone than you seem realize.

    I'm not suggesting, I'm telling. The Pine64 Store makes hardware, we make software. We are a community. Our community includes PostMarketOS, the KDE Plasma Mobile developers, Manjaro, LuneOS, SailfishOS's community porters, Nemo Mobile... the list goes on and on. The Store itself is a member of our community.

    We're on the same side here, man. The @PINE64 account is a collaboration among four long-standing Pine64 community members: TL, Lukasz, 'Gamiee', and 'fire219'. Any one of them could be putting the script together. That does make the "I'm" a bit confusing in this case. We can do better in the future.

    I've been involved in the PinePhone project from the first time that Lukasz joined our IRC and asked if we wanted in. Yes, in a group with 2000 people, he implicitly announced the PinePhone before we even knew its specs. From the beginning, it's been clear: The Pine64 Store's staff members are making the hardware they can manage, with the features we request, at a price they believe is fair. They do not hire software engineers.

    The Store has, however, allocated no-cost hardware to people that we've requested to receive it. Marius, NotKit, and I have received each revision of the PinePhone hardware. We're able to grow that with the Braveheart batch. It's a (capitalist/existential) win for the Pine64 Store, their hardware is far less expensive than our paid developers' salaries. It's a win for us (the community), we get made-for-us hardware.

    Because of this, you are indeed requesting that we create a dual-boot option, not that they create a dual-boot option. You are requesting that we create an Android image.

    The Pine64 Store has Veto Power in our community, they need to make the numbers work. I'm telling you now, though, the numbers don't work if they hire developers. Napkin math can tell me that.



  • @poVoq I cannot imagine Android would make any sense to boot since it probably cannot interface with any of the hardware onboard the Pinephone.



  • @Flohack, there is movement in that direction. Replicant, the Free and Open Source Android ROM, seems like the best possible bet. However, like all of us, they're a small team and need all the help they can get. Just to get a single-boot setup running.



  • @UniSuperBox said in PinePhone:

    @GizmoChicken said in PinePhone:

    You aren't seriously suggesting that Pine64 relies on "the community" for every aspect of the boot process, are you?

    [...] in a post asking about a whether @PINE64 would be providing a script for installing to eMMC, @PINE64 stated: "I'll put together a 'rough' SD->eMMC image in time for when phones are delivered later this month." So @PINE64 seems to have more control over what will ship on the PinePhone than you seem realize.

    I'm not suggesting, I'm telling. The Pine64 Store makes hardware, we make software. We are a community. Our community includes PostMarketOS, the KDE Plasma Mobile developers, Manjaro, LuneOS, SailfishOS's community porters, Nemo Mobile... the list goes on and on. The Store itself is a member of our community.

    We're on the same side here, man. The @PINE64 account is a collaboration among four long-standing Pine64 community members: TL, Lukasz, 'Gamiee', and 'fire219'. Any one of them could be putting the script together. That does make the "I'm" a bit confusing in this case. We can do better in the future.

    I've been involved in the PinePhone project from the first time that Lukasz joined our IRC and asked if we wanted in. Yes, in a group with 2000 people, he implicitly announced the PinePhone before we even knew its specs. From the beginning, it's been clear: The Pine64 Store's staff members are making the hardware they can manage, with the features we request, at a price they believe is fair. They do not hire software engineers.

    The Store has, however, allocated no-cost hardware to people that we've requested to receive it. Marius, NotKit, and I have received each revision of the PinePhone hardware. We're able to grow that with the Braveheart batch. It's a (capitalist/existential) win for the Pine64 Store, their hardware is far less expensive than our paid developers' salaries. It's a win for us (the community), we get made-for-us hardware.

    Because of this, you are indeed requesting that we create a dual-boot option, not that they create a dual-boot option. You are requesting that we create an Android image.

    The Pine64 Store has Veto Power in our community, they need to make the numbers work. I'm telling you now, though, the numbers don't work if they hire developers. Napkin math can tell me that.

    This is accurate 🙂 When I - Lukasz - wrote "I'll put together a SD->eMMC" that actually meant that that is something which I can do (Martjin Braam from PMOS ended up doing it, and most certainly better than I would). As for what Dalton wrote, we do indeed rely entirely on the partner-projects community devs for software.


Log in to reply