Since I've got my Pinebook Pro this problem keeps haunting me. WiFi gets really bad on negligible distances and obstacles.

Here are some speedtests I've just did:

Hi,

I am looking to use the Pine64 as the ‘brains’ to make a ‘dumb’ speaker ‘smart’. 

I have limited coding skills so I want to use proprietary software and hardware to do this. 

The theory I have is to use an inexpensive Bluetooth speaker with built in mic (like this one: Bluetooth Speaker) pair it via BT with Pine64 and then use the google assistant app from Play store. 

Any reason why this might not work? Anybody tried this already?

Hi!

I recently created an SD card to test Mobian on the PinePhone.

I would like to SSH onto it but I am not able to do it from another device in the same network.

I am trying to connect to the mobian user with stock password: 1234
I have already installed open ssh-server, the service is running, and can even SSH onto it locally 
$ ssh mobian@localhost

But if I try to SSH from another device it fails.
$ ssh mobian@ipaddress

Am I missing something?

I am getting this really blurry video as depicted in this image for some operating systems when I try to use them with my PBP.



This occurs with the following operating systems:



chromiumos-rockpro64-R77-12371.7.104.g78f88d6.img

pinebookpro-debian-desktop-mrfixit191226.img

pine64-installer-2.0.0-beta.3-darwin-x64.dmg





But this works fine:



focal-gnome-pinebookpro-0.10.12-1184-arm64.img



I'm assuming this is a driver issue since it works with Ubuntu but not with others?  Any idea why this is happening?

I searched through the forums and was not able to get my problems fixed. I checked out the arch/manjaro forums.

I want to mount my nvme (nvme0n1) drive (adapter purchased through pine64) it is recognized in in the system but I am unable to save it or view it in the file manager. I purchased the nvme based on the Wiki with working nvme drives.

I am getting super block errors and it is refusing to mount. Does anyone have any suggestions or can help me walk through? I have been going at this for about 3 hours on and off.

$ lsblk

NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
nvme0n1      259:0    0  477G  0 disk
└─nvme0n1p1  259:1    0  477G  0 part


Sudo parted -l

odel: INTEL SSDPEKNW512G8 (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
-------------------------------------------------------------------------------------------------------------------------------------------
fsck -r /dev/nvme0n1

$sudo fsck -r /dev/nvme0n1
fsck from util-linux 2.35.2
e2fsck 1.45.6 (20-Mar-2020)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/nvme0n1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
or
    e2fsck -b 32768 <device>

/dev/nvme0n1 contains `DOS/MBR boot sector; partition 1 : ID=0x83, start-CHS (0x1,0,1), end-CHS (0x3c2,21,16), startsector 2048, 1000213168 sectors, extended partition table (last)' data
/dev/nvme0n1: status 8, rss 5136, real 0.127420, user 0.013870, sys 0.026418

Number  Start  End    Size  Type    File system  Flags
1      1049kB  512GB  512GB  primary

Trying to compile and install Anbox on Pinebook Pro (ARM) running Manjaro Arch Linux,

Kernel Version:  5.7.0-1-MANJARO-ARM

Upon attempting to compile the kernel modules ashmem and binder, get the error message:


kallsyms_lookup_name undefined

This is a function in a file:  kallsyms.c , which ships with manjaro linux on the Pinebook pro, according to

https://gitlab.manjaro.org/tsys/linux-pi...kallsyms.c

Possible reason for the error is that the function kallsyms_lookup_name() is now unexported, according to:

https://gitlab.manjaro.org/tsys/linux-pi...ff61103281

Any ideas how to fix this or work around this?  Were it not for this problem, I feel that I am pretty close to getting Anbox compiled with dependencies and up and running on the Pinebook Pro.  I would love to be able to do that.  It would enable me to run Zoom on my laptop, which I do a lot of these days.

Thanks,
Tsvi

I tried the Mobian 20200615 image on my pinephone CE and it's very impressive - I was able to use calls, texts and data immediately after booting. There are a bunch of features that I like a lot more than UT - including the UI (phosh), the update system being more alike standard debian, and for me, it's been generally more stable than UT at the moment.

I have a couple of questions though:
- Since a recent UT update (I believe now including the Crust firmware), battery life under UT has extended by about 4 hours over Mobian (from about 7 hours to about 11 hours for me). It looks like there are a couple of commits that reference Crust - so I was wondering if it is something that can be enabled currently? Or is it something that still needs more work?

- Is there a way to change between booting from MMC and booting from SD card without removing the card? Using the Mobian image also prevents the volume up + power key combination. I have an sd card writer now, but when I didn't I used the phone to flash to the SD card - unfortunately once the sd card is bootable it prevents this option.

Thanks for all the great work so far - I am hoping to become involved in some capacity with the project eventually - but for now I am just learning.

If you are seeing a bunch of 404 errors when using command-line 'pacman', you might be able to fix it in 2 easy steps:


1. Edit your /etc/pacman.d/mirrorlist file, so only this line is present:
  Server = https://manjaro.moson.eu/arm-stable/$repo/$arch

2. Now run a complete update and mirror sync with this command:
sudo pacman-mirrors -g && sudo pacman -Syyu



I am sharing this because I struggled for about a week.  One day, pacman just decided to quit, and I spend a lot of time working with mirrors trying to fix it.  Finally, I found this post by strit:

https://forum.manjaro.org/t/another-mirr...red/132302


Along the way, I came across related info, that may or may not be relevant or useful, but here it is anyway:

https://forum.manjaro.org/t/repos-mirror...404/135113
"Manjaro ARM is transitioning to a Boxit Server, which requires a new mirror structure" - April 2020

Hi, 
after running the default Debian my pbp shipped with I now installed Manjaro 20.04 xfce. 
As I use the pbp while travelling the power settings are pretty important. 

On Debian I could simply set the cpu to powersafe via the battery icon. 
On manjaro xfce I can not find such an option. xfce4-cpufreq-plugin is only displaying but won't let me change the settings.

Any ideas? Or on powersaving in general? I choose xfce as I though it should be less power consuming.

After receiving my PBP and tinkering with Manjaro (including fully updating the system) I decided I'd rather try out a more familiar distro so flashed @mrjay 's Ubuntu image; details here:
https://forum.pine64.org/showthread.php?...0#pid68220

The battery was showing 20% when flashing completed however once the system powered down it will no longer power up. The power button does not appear to have any effect at all.

I've tried searching the forums here for similar issues and so far have tried:

• Booting with / without A/C adapter plugged in
  
• Booting with / without SD card inserted
  
• Verified that A/C adapter is charging (light comes on, charges then turns off)
  
• Verified the A/C adapters are working by charging a 2nd PBP that is still working
  
• Removed the battery, connected the power bypass cable and attempted to power on with A/C adapter
  
• Reseated the eMMC
  
• Booting with / without eMMC hardware switch toggled