PinePhone



  • @PINE64 said in PinePhone:

    @Djhg2000 Not really sure what artwork you have in mind exactly, but casting a cover in a different color (basically just different color plastic) would most certainly be less expensive. Also, we cannot use some of the artwork due to potential problems with trademarks -- that linked Ubuntu image being a good example of what we could not do πŸ™‚

    I only meant for the picture to be illustrative but now that I read my post again I see that I wasn't very clear about that, sorry for the confusion.

    Basically I wanted to have some recognizable UI element printed on the back so that you could tell what the phone shipped with. Trademarks/copyright could certainly be an issue for some of those. Then again, a solid color should be recognizable enough to the right people. πŸ™‚



  • @Djhg2000 Ah yes. Well, it would be ideal to have a logo of the project in question molded into the plastic. How much work and how expensive that would be is some we won't know for some time. Its just an idea.
    I truly hope that people will also 3D print custom back-covers (and cases) for the PinePhone.
    You can always make your own vinyl skin for the case if neither of the ideas materialize πŸ™‚


  • Infrastructure

    @PINE64 A transparent one would be cool πŸ˜‰ - ItΒ΄s a project where you should see whats inside, so also give transparency to the hardware hehe...



  • πŸ™‚ A great metaphor, @Flohack



  • @Flohack I really like the idea! Lets hope that the PCB is visible on the actual phone - the mockup has a plastic 'shield' over the fake PCB (probably holds heatsink in place), so all you'd see is black plastic + battery (not super exciting).





  • @trainailleur I wonder if bluetooth on PinePhone will be fully functional, e.g. handsfree calling, bluetooth transfer, as on current devices it doesn't work. Or is it a question for Ubports rather then for PinePhone vendor?



  • @Stefano said in PinePhone:

    @trainailleur I wonder if bluetooth on PinePhone will be fully functional, e.g. handsfree calling, bluetooth transfer, as on current devices it doesn't work. Or is it a question for Ubports rather then for PinePhone vendor?

    Sounds like a UBPorts question, but since it's a "status of porting" question, I'm not sure anyone would answer. It's probably best just to wait and see. Since @PINE64 have said they won't be taking any money on a widespread order until at least one OS is working on the phone (though I think they have now mentioned the possibility of a small "early adopter" batch), we should know more in plenty of time to make an informed purchase decision.



  • @Stefano - as @trainailleur correctly said, this is a question for UBPorts. The hardware can obviously do all the things you asked about.



  • OP updated with info that popped up on the PinePhone Wiki today:

    • Dimensions now 160.5mm x 76.6mm x 9.2mm (up from 157mm x 56mm x 8.9mm)
    • Base model fixed at 2 GB RAM, 16 GB eMMC, with a strong hint of a 3 GB / 64 GB version (@PINE64, can you confirm?)
    • BT included by the WiFi kill switch, addition of camera kill switch, demise of speaker and USB OTG kill switches. (Those who were looking forward to the OTG kill switch for chrarging at public USB chargers might look into USB power-only filters instead.)
    • $150 base price clarified to refer to 2 GB / 16 GB model.

    Of note, the PinePhone will support microSD, so even the base model should have access to greatly expanded (if slow) bulk storage on SD.



  • @trainailleur he he, I can neither confirm nor deny πŸ˜‰ Just kidding. This is something we've been talking about for a little while now. I am pretty sure it won't be a day one option, but yes, its coming down the line. I'll edit this comment for accuracy / additional info if need be.





  • @PINE64 said in PinePhone:

    Posted this month's news update https://www.pine64.org/2019/06/06/june-2019-news-pinephone-pinebook-pro-and-pinetab/

    Fantastic update. Thank you for posting.

    I updated the OP with the new render and the front motherboard layout. Also updated mention of the camera kill switch to include both front and back cameras, which I should have added earlier.



  • @PINE64 I have seen you have added SFOS as well as partner.

    There will be a pine phone batch with SFOS (with Alien Dalvik?) as well or is it just a community (port?) thing?



  • @makeixo The idea with OS-specific PinePhone batches is just a concept at this time. There are a couple of logistic issues (related to reliably getting the OS to the factory well ahead a schedule OS-specific batch release) that need to be ironed out first.

    As for support from Sailfish OS, please join the PinePhone chat (Discord, Telegram or IRC - your choice) or ask in the relevant forum.



  • @PINE64 thx! An easy way to flash the images would do it for me as well if that is possible.



  • Flashing images and testing new OS' images will be really very simple. Testing will be super easy - flash a SD card and take the new OS for a spin without erasing your existing OS and setup.

    I am currently exploring a way to install all OS' in a super simple way - but need to chat to devs about the implementation I that I have in mind, because they would have to upload up-to-date images to a designated server.



  • @PINE64 That sounds really promising. I might get one just to do some mobile OS-hopping πŸ˜„



  • Thanks @PINE64 πŸ™‚



  • @trainailleur I am currently not in the loop (traveling). If TL says that it will happen, then it will happen, if others say it will happen, then it may or may not happen πŸ˜‰ I'll find out in the next 24hrs for you.

    Here is a clarification: one of the reasons that the pogo pins were exposed is to allow for different types of expansion possibilites. Custom backplates may, and likely will, bring aditional functionality in time - NFC/ Wireless charging, are two examples of what can be achieved via the pogo pins. In fact, we're already looking into it. But to make it clear, this will not be a part of the stand-alone phone at the time of launch.


Log in to reply