PinePhone
-
Here is an update to the general hardware development progress. A revised and final version of the dev kit PCB (v2.0) is now being laid out. It fixes a few issues with the first iteration of the PCB (like e.g. some GPIO mis-allocations) as well as adds community requested features, like the multi-color LED discussed in this thread few weeks back. If all features on this PCB work as intended - and devs are happy with it - then it will become the design to be shrunk down into the PCB that will go into the phone.
We're in talks with multiple factories to deliver the phone. This is good news because, well, they need to compete for our business and this translates to quality (as in any business they need to outdo one-another). I won't say more than this at this point - not because its a secret, but rather because I don't want to raise anyone's hopes for improvements to X or Y which may not happen in the end. Once we've got a deal you'll be the first to know. Regardless, this is good news for everyone.
Lastly, since 'battery' has now become a conversation point I'll learn more about it in coming days and see what is already known - perhaps we can add this information to the known feature-list by the end of next week.
-
@PINE64 thanks! what about the InfraRed LED?
-
@mymike Ah yes, will find out... sorry, absent minded and tired from travel
-
As far as I can tell, the A64 doesn't natively support an IR LED for general purpose use. It has a native CIR (Consumer IR) receiver (which is broken out on the devkit but not installed) and any of its six UART controllers can be configured to use IrDA. I assume you're looking for an IR transceiver for controlling a TV or similar @mymike... If it's possible to use GPIO to output fast enough for a TV then you might have a case, otherwise there might not be a compelling reason (or software support).
-
Off-topic somewhat, just wanted to let the community know that there is now a Telegram group linked our IRC and Discord that discusses the PinePhone. All welcome
-
This post is deleted! -
So, we don't have a definitive answer regarding the battery at this time.
Any and all suggestions regarding easily sourceable (is that a word?) 3000-3500mha batteries by end-users welcome. Happy to brainstorm any ideas you may have.
[edit] physical dimensions: 91.5mm x 63.5x 3.8mm
[edit 2] Thoughts about the Galaxy J7 battery as an option ? -
@UniSuperBox yeah, it was for those puropose.
if it's something more or less easy to add I'd be glad, otherwise doesn't matter, that's not a fundamental component... -
@PINE64 any easily sourced battery would make sense -- and of course Samsung produces a lot of phones. I wonder if that battery is the same as the one in the Galaxy J7 Duo, which was released in 2018? If so, it would be fairly promising because they've been using it for a while and it should remain in demand longer.
Here's a link to the 2018 version: https://www.gsmarena.com/samsung_galaxy_j7_duo-9153.php
-
@visiblink Seems to me like its the same battery yes.
-
Some points:
- 1 The lower border is too large (if it has no buttons).
- 2 Being a privacy oriented phone, it would be cool a physical switch to turn off the module, and maybe the cameras, microphone. I dont trust very much the module stand-by state.
- 3 The display manager should be i3 or lxde (kde or gnome would be f00l(no offence ubports)) and the OS arch or debian. All the always-running apps should be gtk2.
- 4 I hope that the pinephone 2 will use a mediatek or qualcomm soc. Not a surprise a battery of 3000 mAh.
- 5 USB host mode ? USB guest mode ?
- 6 A second USB ? mini hdmi ? But all those holes in the box could be a problem for water resistantce...
- 7 Some feature could be battery kiIIer, like sensors are always on ? And the rgb led is fun (less bright /efficent ?) but I hope it doesnt use 3 pwm! it would kiII the battery. Also there could be minor useless module features that are on by default, must verify that.
- 8 Is the modem chip on the main board ? Then why not to use directly the qualcomm 9x07 modem rather than the quectel based on it ?
- 9 Why there are more discussions on the phone here than on the pine64 forum ?
- 10 After the first launch you will need a period of testing to verify that the module doesnt spy. The threat can come from queltel qualc0m or andr0id small tools
update: - 11 Multi boot
-12 Recovery from brick(boot from sdcard?)
Sayd that, I love it! I want one as soon as possible!
-
2 Being a privacy oriented phone, it would be cool a physical switch to turn off the module, and maybe the cameras, microphone. I dont trust very much the module stand-by state.
It will have physical switched for all those
- 3 The display manager should be i3 or lxde (kde or gnome would be f00l(no offence ubports)) and the OS arch or debian. All the always-running apps should be gtk2.
gtk on phones is a bad idea. It's not designed for low end hardware nor is it designed to work on a phone form factor. Why do you want gtk?
Qt has superior performance on embedded, ARM based devices. Also LXDE is moving to LXQT which is qt based.UBports does not use kde or gnome, we use unity8 that's crafted specifically to work on phones and desktop alike, based on qt.
i3 would be hard to use? no keyboard?
But you can run whatever you want
there is debian builds already for it, and i know other project are working on it as well, like arch, plasma mobile, etc.4 I hope that the pinephone 2 will use a mediatek or qualcomm soc. Not a surprise a battery of 3000 mAh.
It will use the allwinner a64
-
@Jackl since you're not all that interested in Ubuntu Touch anyway, maybe you'd prefer to discuss at https://forum.pine64.org/. This forum has more discussions because there are a lot of people interested in Ubuntu Touch on the PinePhone, you'll probably find similar discussions at any other partner project's preferred meeting place.
-
Any specifics on the MALI-400? number of cores, speed?
-
@snailmail
The Mali-400 is part of the A64. Those are the specs you are looking for. -
- 9 Why there are more discussions on the phone here than on the pine64 forum ?
I think it is partly because there is no dedicated pinephone section in the Pine64 forum yet.
The other parts of the equation are that UB Touch looks like the most likely distribution to be device-ready by the release date (although that's just my perception based on superficial observation from a great distance) and the community here seems friendly and engaged.
-
@trainailleur we have tentatively decided on the Samsung J7 3000mha form-factor battery. The key word here is 'tentatively' - apparently one or more factories are happy to accommodate this request, but obviously we'll know more when the inside of the body starts getting worked on.
-
@mymike IR is a no.
-
I think this looks fantastic and for the price, I see no reason not to get one. In fact, I already convinced my wife I'll be grabbing one when it drops as well as one for our youngest as her first phone. Very excited to see how UT development goes on this.
-
@mariogrip said in PinePhone:
It will have physical switched for all those
Cool!
Qt has superior performance on embedded, ARM based devices.
This is new, didn't know that.
i3 would be hard to use? no keyboard?
With toolbars and gestures like android and UT does...
Notice that I sayd pinephone 2, i mean the next gen one
