So, I have been using my Pinephone, in a wallet case not designed for it, on a temporary basis. Was working well, but had to pop the Pinephone out of the case to press the power button.

Suddenly, a very soft "ping". The little dish-shaped aluminium plate came off the power button, revealing the two contacts (the inner copper dot and outer copper ring).

Power button still works if I short across the contacts with a conductive object.

Fixing the little aluminium plate back in place with a touch of cyanoacrylate glue did not restore the power button's function, had to remove it again.

Spoke to a friend we all call "MacGyver", he doesn't like even his chances of repairing a little momentary power button, says he's succeeded twice on about fifty devices attempted.

I need a replacement power button for the Pinephone. I've searched the datasheets and component list hoping for a component ID for the little momentary power button, but it only lists the larger modules.

Does anyone know what a suitable replacement button would be? Digikey component number or a link to eBay / Aliexpress would be most welcome!

Hi All,

I just wondered if there was anyone out there wanting to buy my Pinebook Pro?
It is one of the original 1000 from the community batch, released after the initial testers batch.

It all works fine, and includes the NVMe adaptor (not yet fitted).
The reason I am selling it is because I've been simply too busy to use it. My total use of it has been to format a few SD cards, watch 3 movies on it and used it to backup a hard drive to a different hard drive. That's it!

I am in the UK but the power cord has a 2 pin plug as standard. I just used an adaptor and can include one when I send it if needed, 
I would prefer to ship to the UK as it'll be cheaper and easier but I could be open to sending abroad (I'd need to look into costs).
The buyer would need to cover shipping.

If you're interested, please send me a message or reply on the thread.

Thanks
VoT 

Hi all, Is it possible to play turn based game on the Pinephone? I only use Email and PlayStation emulator on my device.

Thanks!

Hello,

While attempting to perform a performance comparison of A1-rated and non-A1-rated Micro SD cards, with additonal emphasis on using F2FS instead of ext4, I've encountered a major issue with the PineBook Pro's SD card interface.  Here are more details.

In a few words, attempting to write about 14.5 GiB to a Kingston A1-rated 16 GB UHS-I Micro SD card (SDCS2/16GB) resulted in a failure and the following Linux kernel messages, after writing about 700 MiB to the card:

I would like to use my Pinephone in a project where I need to take gyroscope and accelerometer readings. I can't find any information on how to access these sensors though. I tried lm-sensors but it only displays battery status and thermal sensors. There doesn't seem to be any info on the wiki either about accessing these. How can I log readings from these sensors?

Hi

Is it okay to order the US version of the PineBook Pro for use in the UK? The different keyboard layout doesn't bother me, I just wanted to know if there's anything else I should be aware of? For instance maybe voltage issues?

Thanks

Hello,

This thread is a fork from another thread, as requested by the OP.  First, here's a sum-up of what's been already discussed:

(03-09-2021, 11:15 AM)dsimic Wrote: When the phone is connected to the official dock, and a charger is plugged into the dock, shutting down the operating system causes the phone to power off and, unexpectedly, power back on immediately.  I've tested it more than a few times, and it always (mis)behaves like that.

(03-09-2021, 11:15 AM)dsimic Wrote:

(03-01-2021, 12:24 AM)GregH Wrote: Another side effect is that the device will not stay off with DCIN powered - no charging while switched off, it keeps booting up again :-(

This is pretty much the same behavior as with the official dock connected to the phone, which I've described earlier in this post.

After reviewing the relevant part of the available documentation for AXP803 (i.e. the PMIC), it's clear why this happens with 5 V applied to the DCIN pogo pin.  Basically, the PMIC detects the presence of valid input power voltage, which is satisfied in this case, and automatically begins the power-on procedure.  However, this doesn't explain the same behavior with the official dock plugged into the phone.

(03-14-2021, 08:29 PM)bokomaru Wrote: Phone -> USB C to A cable -> old "dumb" power brick -> AC wall outlet: Connecting the first time causes the phone to power on. But I can power the phone off from software, and then it stays "off".

Phone -> convergence dock -> USB C to a cable -> old "dumb" power brick -> AC wall outlet: Connecting the first time causes the phone to power on. After powering off the phone from software, the phone powers back on; won't stay "off".

(03-14-2021, 08:29 PM)bokomaru Wrote:

(03-14-2021, 07:42 AM)megous Wrote: anx7688 doesn't do anything unless the pinephone is powered on, so there's some fun to be had when charging via USB-PD chargers when the phone is off.

Maybe that's related to this, i.e., maybe the phone powers on by design, so that USB-PD can be negotiated if applicable.

I also remember reading that, for similar reasons, while charging, Android phones tend to be booted up. At least into the bootloader, and then the bootloader maybe knows to enter a different "charging indication" mode or to "stop here" until X or Y event happens.

Anyways, my point is that either of the two conflicting observations can happen, depending on which hardware you connect. If you want to reproduce my "off" test cases, try using a "dumb" brick without USB-PD.

If you follow the Mobian blog you may know there is an unstable branch now for those who want to test the cutting edge.

https://blog.mobian-project.org/posts/20...le-distro/

Some of you may be afraid to switch because you needs your phones to work and can't take the risk of something unstable upsetting that.

You can have your cake and eat it too. You can clone your drive via Balena Etcher onto an SD card or create an ISO image of it (back up) using Disks in Linux and burn it to an SD card. Even an encrypted drive. You should have a back up anyway. Use Jumpdrive on an SD to allow your computer to see the Emmc and don't decrypt it before cloning. Then you can use the SD card image for unstable and leave the Emmc alone. If things break you can just remove the SD card and still have a working phone in a pinch just by removing it. Make a change in the order of your favorite apps so you know what you are booted into. (exaple, put your phone on the left on the SD card image) The reason why is sometimes after an update on the Emmc your phone will only boot to the newer boot Image (the Emmc) but you can over ride that temporarily because some type of temporary FEL mode must be activated. Power and volume down will boot back into the SD card. Power and volume up will boot into the Emmc until the next update on the SD card. Then it will be normal boot priority with the SD card.

I'm trying to run OpenTTD on mobian pinephone and it doesn't work. I see that error above when starting it from the terminal. Trying to set a resolution manually with the -r flag didn't helped.

However if I run it with:

Video for Pinephone/Pinetab operating systems covering default pin numbers and showing why it is important to change them. 
[starting with small nmap/Hydra demo] Includes most common pin list.

Afterwards make some basic sshd_config file/pin recommendations to prevent it. 


Suitable for beginners and doesn't go into further key options: https://youtu.be/GAvGKlvKouY

Given so many are using SSH and not all familiar, thought it could be helpful.