PinePhone
-
@PINE64 ah yes, that makes sense.
-
@PINE64 It's a great flashback to see screw holes. User-repairable devices have become so old-school, but I love it. Nice to see a phone you'll be able to fix yourself. You might want to send one of these to ifixit once it's done.
-
@visiblink Yes and it goes together like a puzzle
Think anyone will be able to fix it by themselves.
-
-
@domubpkm interesting find. The world is full of surprises
-
Here is the PCB
in a few days we'll know if we've got a PinePhone or not yet 
-
@PINE64 in the august update, it was said that
we’re going back on what we initially said, namely that “the PinePhone will first ship when software is ready”. The reality of the situation, however, is that advanced users want to get their hands the PinePhone, and we don’t want it sitting in a warehouse until end-user level performance is achieved.
Will the hardware be finalized before advanced users/early adopters are allowed to order? i.e. if I buy an early adopter phone, will the hardware I get will be the same as someone who orders after the release?
-
@B2288 The pictured boards will be used in the prototypes. Granted the prototypes work then, after a few minor tweaks (there are always tweaks regardless of if everything works or not), the first production run for enthusiasts should be no different to units that will ship later.
-
@PINE64 Great, thanks. I look forward to getting one and helping with software development!
-
@Photojoe4 said in PinePhone:
Is there a way to confirm that the Pinephone will work as well "out of the box" as my Nexus 5 running Ubuntu Touch? In other words, would I be losing any functionality by switching to it when it comes out?
Particularly I'm hoping WiFi Display will be working since it's presently broken on Nexus 5.
-
Following an Android custom ROM group, I've seen the maintainers add VOLTE by picking commits from carriers that have it.
-
-
I'm told it works
a lot of testing ahead to determine if its all OK, but for now it looks like we're at least on schedule
-
Hurrah! Very nice to see the steady progress.
-
@B2288 The pictured boards will be used in the prototypes. Granted the prototypes work then, after a few minor tweaks (there are always tweaks regardless of if everything works or not), the first production run for enthusiasts should be no different to units that will ship later.
Please put a revision number somewhere on the device anyway, you never know when you discover a previously invisible hardware bug.
-
@Djhg2000 Of course.
-
Our commitment to donating to PinePhone Linux projects: https://www.pine64.org/2019/08/19/its-time-to-start-giving-back/
-
@PINE64 It's really good to see that initiative directed toward closing the digital gap. It's going to be great to support a company with a social conscience.
-
So we have many information about the PinePhone hardware on this thread, but as we are on the UT forum, I was expecting some UT devs to indicate and keep us up-to-date with the status of UT on the PinePhone.
I saw some pictures, but can we have more details on what's currently working on the dev kit and what's not? And maybe a target date of when it will be considered stable enough?
Btw:
Ameridroid kind-of stole our thunder for the upcoming Community update. Oh well
https://ameridroid.com/blogs/ameriblogs/upcoming-product-more-pinephone-details-from-tl-limIt said there:
If at least one OS distribution is not ready by February, this will delay general availability production
I'm quite curious about that. Why if one OS isn't ready, you should not deliver the other ones? Especially if I understand correctly what's said in "It's time to start to give back" that batches of phone should be OS specific...
-
Why if one OS isn't ready, you should not deliver the other ones?
I think you misread the statement. "If at least one OS distribution is not ready by February, this will delay general availability production" means that if there is not at least one OS (in other words: if there are zero available OS).
