Every time I press a call, I and the person I am talking to hear loud static noises. It sounds a bit like a radio and it's very hard to understand each other.

Is this normal or a specific hardware problem.

Thanks

Any new info on when I would be able to order a pinephone? thx...

When I go to System Settings > Accounts > Nextcloud, I get an endlessly spinning circle to the right but nothing ever happens. Has anyone else been able to setup a Nextcloud account or any other account? I just tried and none of the account options work. Just spins forever.

Before replacing the battery, internet and texting were working on Verizon's network (I hadn't tried making a call). After the 3500mAh replacement[0] the bottom half of the screen started flickering. I immediately turned the phone off and put the stock battery in, but now I don't seem to have any cellular network access (though the phone can see my SIM card). I've already double checked that it wasn't a result of me accidentally flipping the kill-switches when I did the swap. I recognise that this was the result of me playing with fire to see what would happen, and while I'm open to advice I'm sort of assuming I'll need to wait for more main boards to come available -- replacing the modem specifically is probably above of my level of solder competency. I just wanted to warn anybody googling for pinephone battery upgrade information related to v1.2 CE that my personal experience is 3500mAh kills modems.

[0]: https://www.amazon.com/6-7-8-Battery-Cas...07F7R4HLM/

Upgraded from PinePhone Devel Image #52 to #58 this morning over OTA, rebooted and now have an utterly unresponsive touchscreen

It boots up fine, Volume Up and Down buttons and Power button work (as evidenced by OSD responses) and I can still ssh in, but touchscreen not working.

If I revert back to Image #52, touchscreen works again - OTA update to #58 breaks it again. I see from System Image Changes page (https://ci.ubports.com/job/rootfs/job/ro...ge/changes) that #58 and #59 have not changed since #57, so assuming this is a #57 problem?

Hello,

After a hardware failure on my primary laptop last week (display backlight failure), I was looking forward to more time using my PBP, which has had minimal use to date.

This morning, the screen started displaying various horizontal lines and obviously corrupt data, and the device became unresponsive. Was booted off SD (Manjaro, i3wm) at the time.

Power-off worked. Power-on did not. I've tried leaving to charge, and battery bypass, with no success.

I am using an Apple USB-C charger, which continues to work correctly with other Apple / Dell devices. I have not tried the PSU which came with it as it didn't come with a UK adaptor and I do not have one.

My PBP is from the second batch, I believe, has the 128GB eMMC, and arrived in mid-November.

From looking over other posts, it looks like the options to explore are:
- Removing the eMMC / toggling the switch;
- Connecting a serial cable (I do not think I have a compatible one) to check whether uBoot is loading.

Any other suggestions I have missed?

Thank you!

Hey all,

I flashed the 16/06 build (and later the nightly) on a 32GB SanDisk microSD card. Sadly, in both cases Mobian is stuck during the plymouth boot screen (circle keeps circling indefinitely).

PostmarketOS works with this card, so I guess the microSD is not the problem. UBports is on the internal flash.

Any clue what the problem might be? Thanks.

Since I am a new Linux user this was not apparent to me before. If you are booting from the micro SD port your PBP computer will only run as fast as the installed card can read+write. I wrote a few different versions of Manjaro to some old slow cards and one version to a new fast card. It is like night and day. Fast computer=fast SD card. Running Manjaro-Arm64-KDE-Plasma 20.06 fixed all my PBP problems I had with the Manjaro version shipped on the computer. No audio, no battery icon, crazy screen flicker, battery depletion during sleep, inability to read USB devices on ports A 2.0 and 3.0, are all resolved when using 20.06

I received my PBP about a week ago. It's running the default Manjaro OS.

I'm wondering if anyone else has the same problem I do as I haven't heard anyone mention it.

When I put the screen all the way down it stays on.

When the screen is about 1 to 2 inches from being closed it turns off but when I shut it all the way it turns back on.

When I open the screen it turns off during the first 1 to 2 inches then comes back on when I open it on further.

It acts like it's a hardware issue? I haven't taken it apart yet. Just wondering if anyone else is having this issue?

I have set it to only turn the screen off when the screen is closed not to sleep or power down the computer.

Seems like this issue is also keeping it from being able to sleep/suspend (which I prefer to do manually).

Evening, Pine64 community.

I've been doing builds of the Signal Desktop client for Manjaro/aarch64 for myself for a while now.  They've proven stable enough for my daily use that I've decided to start posting them here in case anybody else can benefit from them.

I'll try to keep this post updated within a couple of weeks of new releases.  This is a best-effort project and the packages are distributed as-is, without any warranty, express or implied, including the implied warranties of merchantability and fitness for a particular purpose, etc. etc. etc. ad nauseam.  These are NOT official Signal builds, and I am not in any way affiliated with the Signal project or Open Whisper Systems.  TL;DR use at your own risk.  Distributed under the GPLv3, source code and detailed license are available at https://github.com/signalapp/Signal-Desktop 

These are Manjaro/aarch64 packages.  Install with pacman -U directly, or create a local repo for use with pacman -S, whichever suits you.

Current stable versions (Google Drive download links)

• Standard build, for X11 or Xwayland: signal-desktop-1.34.2-1-aarch64.pkg.tar.xz
  
• Ozone build, for native Wayland: signal-desktop-ozone-1.34.2-2-aarch64.pkg.tar.xz [EXPERIMENTAL]
  

• Minor modifications to some of the build scripts may be required, and often vary from one version to the next, usually because of the Node community's love of bundling pre-compiled x86-only binaries into their git repos.  I do not under any circumstances alter the source code of Signal Desktop itself, nor of any of its dependencies.  If you're curious about the modified build files for a given version, and/or would like instructions to reproduce these builds yourself, send me a message.
  

• The Ozone build provides native Wayland support, no Xwayland required.  Ozone is the name in the Chromium project (and thus in Electron, which Signal Desktop is built on) of a relatively new abstraction layer which modularizes GUI support.  This is highly experimental, requires on my end an Electron build with custom build configuration, and is not in any way supported by upstream Signal Desktop.  I'd very much like feedback on these builds, but do not be surprised if there are major bugs!