If I plug in the usb-c charger, the phone will automatically Boot ON.
I've tried different methods including cmd power off but as soon as the phone is off and detects "power" it starts

Is this a bug, because it's an inconvience.

Second problem
The battery life actually sucks. I've put the phone in air-plane mode, I don't have a SIM card inserted, and the batter will last 72 hours at best.

I think a better battery would be the first thing to look into, but I guess know I know why you sell "spare batteries" on your website.

I knew I should have purchased a giggle pixel and took a risk with a custom rom, but no, I wanted to support Linux on phones, and the ability to sync phone to tablet, to laptop and home PC, all running linux, with the need for online storage like Giggle and Apple does.

I want to learn the ARM architecture and migrate some of my computing to it, with the option to go all the way down to ARM assembly language and machine code for e.g. firmware (I'm already somewhat familiar with x86 asm and machine code,) and compatible with common ARM systems like phones, Pine64's SBCs and Raspberry Pis. I am under the impression that a strong ARM laptop would be the most flexible and convenient way to do this (so I don't have to cross-compile/emulate, etc) and the Pinebook Pro appears to be the best on the market for the purpose, especially since I could just run the laptop right next to any other ARM hardware I later acquire as a portable development system. Second opinions?

 I'd like to run a hypervisor like Xen so I can run multiple ARM-compatible OSes simultaneously for maximum flexibility. I see various other ARM laptops on the market but the PBP seems to be the most suited to the widest variety of software and hardware development? Would natively building and testing Android and iPhone code on this sort of setup be realistic, or only more open platforms like Armbian? A pair of A72s should produce quick compile times for small- to mid-sized software projects, right? I'm also looking to migrate away from Security-Through-Obscurity Black-Box Intrusion Systems like "Microsoft Pluton," "Intel Management Engine," and "AMD Secure Technology." The Rockchip RK3399 seems to have no ARM TrustZone or similar technologies in it and that is likely a positive for my purposes, unless it's the only performance-efficient way to get the necessary virtualization to support a FOSS hypervisor like Xen?

 The USB-C port is also a major draw most ARM systems lack. Seems like it's limited to 15W? - can the most recent batch run entirely off a 15 or 60W+ USB-C power source with a dead and/or disconnected battery? That would be highly desirable. If not, is there any way to run with a dead battery, like connecting both the included power brick and a USB-C power source at the same time? If still not, is there a viable way I could get 2 batteries and swap them as needed, charging one outside the laptop, short of buying 2 PBPs? And does the current batch USB-C port support any other USB alt-modes like Thunderbolt or HDMI?

 Recommendations of companion hardware, software and configurations towards these goals welcome.

I've just assembled my RocKPro64 with button battery backup in the ROCKPro64 PREMIUM ALUMINUM CASING.  There seems to be one problem.  The casing is very precise in all but one dimension.  The slot milled in the side to accept the microSD card is far too low.  There is no way that the card can be angled so as even to begin to enter the slot on the board.  I double checked everything carefully, and when assembled, all other openings are very precisely where they belong.  It's almost as if the circuit board supplied was on stock far thinner than the one used when it was designed, since the card socket mounts on the bottom of the board.

Anyway, I measured the difference with my mikes, then using a flat jeweller's file, filed the top of the slot more open by .5mm(.020 inch and now everything now fits as it should!  Just a heads-up to anyone else who might be having difficulty.

...because the when the time runs out, it doesn't know it when it's suspended. It does tell you when you wake it up... and it was supposed to wake you up.

C'mon guys, this worked on any Nokia twelve years ago. Or probably even before. These two functions should wake up the Pine.

Hi all!

It has occurred to me that when I turn my pinephone to landscape, the keyboard covers an enormous amount of space, as the keys become twice as wide as in portrait mode, -which is perhaps a huge waste of space on such a precious, small area of available screen?

I have calculated that every key currently visible in portrait mode could fit into 2 rows in landscape mode, and I think I would far prefer to spend a few days getting used to a different layout than covering up so much of my screen.

I suspect that the 2 row keyboard could be done simplest by just putting the characters in alphabetical order, mostly on the first line, and the few on the second line, followed by the normally visible symbols and numbers. The space bar could be reduced to just one and a half squares, as it does not need to be huge, just a little distinctive. Symbols etc. would be accessed in the same way as in portrait mode.

Perhaps this compact landscape keyboard could be a choose-able option for those who prefer the space?

Does anyone know how hard this would be to accomplish -or perhaps there are other comments too?

Alternative: -another way to make better use of the space in landscape mode would be to still use 4 rows, and move the portrait mode keyboard, at it's original, portrait size, to the middle, and then surround it on either side with the numbers, and a lot of the most common symbols, at slightly narrower sizes, so that typing in landscape mode becomes much faster for programming etc, as many more keys are always instantly available?

Regards!

Hi

I've just installed Linux Arch (for PineBook Pro) on a USB stick following the official guide https://wiki.pine64.org/wiki/Installing_...nebook_Pro

everything went well. However, when I tried to reboot the new installation from USB, it just went to the default Manjaro installation. That happens if I plug the USB stick on the left. I tried to plug it on the right port, and it works: I can boot it! So is it true that I cannot boot from the left port (the port works since I installed Linux Arch on the USB stick using that port)? I seem to understand that the left port is USB 3, while the right port is USB 2? Or am I wrong?

I have a problem with calls and I would like you to help me to solve it. Thanks in advance.
When I call from my mobile to another device, the call hangs up, directly. And when they call me, the call is busy all the time, although I have mobile data and receive SMS.
I use pinephone with postmarketos, but it has also happened to me with manjaro.
I don't know where the problem may lie...

what happened to geary?

 i don't find it on "software" and not in apt

 apt says

Hi,

I'd like to know how I could get pinephone ordered in volume? I am open source developer and thing I did with pinephone has gained some commercial traction and I was asked about availability of hardware. Any one I could talk with?

Just got my PinePhone (original) in the mail this week, there's so much I love about it but this one has me really scratching my head. If I plug in the Convergence dock with a USB keyboard, and then unplug it, and then lock the phone, when I go to unlock it it'll print some message about loginctl and needing to press Ctrl+Alt (the font size is very large so most of the text is not legible).

This is very consistent with the convergence dock+usb keyboard. Unplug keyboard, lock phone, then try to unlock it and it'll crash.

I was suspicious that this was some software issue with the default Manjaro Linux image so I booted up the postmarketOS Plasma Mobile live image and...the exact same thing happens!

What is especially weird is that sometimes this will even happen when I unplug a regular USB charging cable (not the dock). It is not 100% of the time like it is with the dock. Maybe 1 in 5 times.

Is it possible that something is up with my USB port, or has anyone experienced this issue with Plasma Mobile before?