Hello,

My problem is similar to thread https://forum.pine64.org/showthread.php?tid=8993 but I create this thread to add details specific to my case:

I was able to power up the phone when it arrived and I tested Ubuntu touch and postmarketOS which both are looking promising.
The battery indicator was showing around 20% I think.
I used a raspberry pi to connect to the UART using the headphone jack and I was able to communicate with postmarketOS.
While doing this the phone was plugged in (2A charger)  to let it charge but it did not seem to charge (I do not remember seeing a red light or a charging indicators in the OSes). I though maybe this as a OS bug and maybe it was actually charging.
Then I switched the phone off by typing "sudo poweroff" in the serial terminal, and let off to  charge for a while (still no red light though).

A few hours later the phone does not power up and does not seem to charge (led not turning on).
I also tried to power up without the battery but that does not work either. I know a 3A charger is advised but someone in the chat said 1A is sufficient to boot without the battery, so my 2A charger should work  ?


I will not be able to get a multimeter until a few days, but then I will look at the battery voltage and the power drawn from the usb cable. In the meantime any idea is welcome

Could it be a PMIC problem similar to what can happen on the pinebook when the battery is totally drained ? (https://forum.pine64.org/showthread.php?tid=4632)

Hi,

Any hardware devs able to answer this?

Basically, does the display on the PinePhone use PWM to control brightness?
I hope not! But if so, what's the duty cycle?

Looking at the DTS, it seems it uses Linux kernel's PWM driver(?) to adjust brightness, does that imply PMW at the hardware level or not neccessarly?

Thanks.

PS: Whilst at it, how about the PineTab?

I've changed resolution on pinebook pro debian to 1024x768.
The screen become black.
How can I return resolution 1920x1080 from the CLI?

Hi everyone!

I've been fooling around with my Pinephone for a couple of days and I love it. But I can't manage to use the modem.

My SIM is recognized, I can see all the operators, but when trying to connect to mine (or any other, even ater enabling roaming) I get a `registration denied` from the operator. I have tried with two SIM cards from two different operators, they work well on other phones but I get the same issue with the pinephone.

I have tried from UBports, PostmarketOS and Manjaro, with both ofono (I get a `GPRS is not attached` message) and ModemManager (In debug mode I see the modem state going from `not-registered` to `registration`denied`).


From what I saw on IRC, I'm not the only one having this kind of issue. Is anyone else having trouble? Does someone have an idea of how to fix this?

greetings,

sway is an i3wm replacement window manager for wayland, and my preferred ui. here's a build script for sway-git. working on debian sid arm64.

providing these build scripts as how-tos. the combination of linux 5.5, mesa-git and sway-git works exceptionally well on the pbp, which leverages the latest panfrost graphics and wayland.

after installing sway-git, consider these post-install recommendations:

• copy sway/config.in to ~/.config/sway/config if you are starting from scratch
  
• change $term to your preferred terminal (i use termit)
  
• choose your background image
  
• uncomment the swayidle block and configure to your liking
  
• use the example trackpad input block below
  
• comment/disable swaybar and "exec waybar" at the bottom of the config to use waybar instead
  
• consider adding the included custom settings at the bottom of your file
  
• (additional software referenced is grim light waybar blueman network-manager-gnome pasystray)
  

Quote:input "9610:30:HAILUCK_CO.,LTD_USB_KEYBOARD_Touchpad" {
       dwt enabled
       tap enabled
       natural_scroll enabled
       middle_emulation enabled
   }

Quote:# DEFAULT MOD BINDINGS FOR REFERENCE
# mod+a focus parent
# mod+b splith
# mod+d menu
# mod+e layout toggle split
# mod+f fullscreen
# mod+h focus left
# mod+j focus down
# mod+k focus up
# mod+l focus right
# mod+r resize
# mod+s layout stacking
# mod+v slitv
# mod+w layout tabbed
# mod+Shift+c reload config
# mod+Shift+e exit
# mod+Shift+q kill
 
# CUSTOM KEYBINDS
bindsym $mod+g exec grim -t png ~/Screenshots/screenshot-`date +%Y%m%d.%H%M%S`.png
bindsym $mod+Shift+s exec systemctl suspend
bindsym XF86AudioRaiseVolume exec pactl set-sink-volume @DEFAULT_SINK@ +5%
bindsym XF86AudioLowerVolume exec pactl set-sink-volume @DEFAULT_SINK@ -5%
bindsym XF86AudioMute exec pactl set-sink-mute @DEFAULT_SINK@ toggle
bindsym XF86AudioMicMute exec pactl set-source-mute @DEFAULT_SOURCE@ toggle
bindsym XF86MonBrightnessDown exec light -A 5%
bindsym XF86MonBrightnessUp exec light -U 5%
bindsym XF86AudioPlay exec playerctl play-pause
bindsym XF86AudioNext exec playerctl next
bindsym XF86AudioPrev exec playerctl previous
 
# LAUNCH AT STARTUP 
exec waybar
exec blueman-applet
exec nm-applet --indicator
exec pasystray

Quote:sudo apt-get -y install build-essential ccache meson cmake git \
wayland-protocols libwayland-dev libwayland-egl-backend-dev \
libgles2-mesa-dev libegl1-mesa-dev libdrm-dev libgbm-dev \
libinput-dev libxkbcommon-dev libudev-dev libpixman-1-dev \
libx11-xcb-dev libxcb-xinput-dev libxcb-xfixes0-dev \
libxcb-composite0-dev libxcb-xrender0-dev libpcap-dev \ 
libsystemd-dev libxcb-icccm4-dev libpng-dev libavutil-dev \
libavcodec-dev libavformat-dev \
libjson-c-dev libpcre3-dev libcairo2-dev libpango1.0-dev \
libgdk-pixbuf2.0-dev libevdev-dev libinput-dev \
bash-completion fish scdoc \
libpam-dev libcrypt-dev

Quote:#!/bin/sh
 
### v0.20200205.2251
## BUILD SWAY FROM GIT
 
# VARS
DEVDIR=~/Development/UPSTREAM/SWAY
 
# PREP
mkdir -p $DEVDIR &&\
cd $DEVDIR &&\
 
# GIT
for dir in wlroots sway swaybg swayidle swaylock;do \
test -d $dir || git clone --depth=1 https://github.com/swaywm/$dir.git;
done &&\
 
# UPDATE (RERUN)
for dir in wlroots sway swaybg swayidle swaylock;do \
cd $dir && git clean -f && git reset --hard && git pull && cd ..;
done &&\
 
# BUILD AND INSTALL
for dir in wlroots sway swaybg swayidle swaylock;do \
cd $dir &&\
rm -Rf pbp-build &&\
meson pbp-build -Dprefix=/usr/local -Dbuildtype=release &&\
ninja -C pbp-build &&\
sudo ninja -C pbp-build install &&\
cd ..;
done &&\
sudo ldconfig;
 
# EXIT
exit
 
# ENJOY

I am using the latest stable ayufan bionic

I need to use a few of the gpio pins as input interrupts.   In an RPI that is a simple is setting a line the the /boot/firmware/config.txt file.
ex.  gpio=9,10,24,4=pd   to set pins 0.10,24,4 as pulldowns

But I guess that method has not been copied in the ayufan image.

That leaves me to rebuild the kernel (not wanting to do that) or use a DTO which I understand is a way to add functionality to the kernel without a complete recompile.

So I gotta believe someone has had a need of pins as interrupts on the rock64 and already has a working dts file.

Besides being some pretty arcane syntax I can find no docs on this that pertain specifically to the rock64 let alone a sample dts file.

Can anyone help out here with a working dts file and some details about how to compile/register it so it gets picked up at boot.

here for example is a beagle black dts file about all I could find.

I have received the PinePhone today and, I must say, I'm impressed with it. I'm not sure what I expected, exactly, but I like what I see. 

I have tried the Manjaro image and the UBports image and the latter seems to be the most polished. Not so sure I like Plasma...

First major issue so is that I can't the SIM to be recognized... Didn't see if this was part of the standing issues with phones. But man, is it cool to have a full Linux distro on a phone!

See pic. I can push the SIM card further even until it's almost completely hidden by the metal. Either the way in the pic or completely inserted, the SIM card is not recognized by Ubuntu Touch or by postmarketOS.

Is this the correct way?

Is there an easy way to pull the SIM card out aside from using a sticky tape?



  IMG_0821.jpg (Size: 483.25 KB / Downloads: 857)

I know that Gnome isn't the most popular environment on the Pinebook Pro, with lighter alternatives like Mate and XFCE being default options on most of the popular system images.

I find that I'm very happy with it, running Debian Bullseye, per @danielt Debian installer. Many of the unmodified Ubuntu images will use this as the Canonical desktop as well.

The screen on every one of the distros looks very small for daily use - and Gnome is no exception here. My solution has been to enable the Gnome experimental capability for "Fractional Scaling". The Settings app, gnome-control-center, normally allows only two scaling options under "Devices -> Displays", 100% and 200%. These were designed for users on HiDPI screens, like that in MacbookPro and high-end Dell XPS laptops.

Since at least Gnome 3.2 it's been possible to add a range of 125%-150%-175% as additional scaling options, which are very suitable for other classes of machine, like our PBPs.

This can be enabled within your gnome session by opening a terminal, and entering:

gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']"

The control center "Settings" can now be opened with the new preference choices, without logging out of your running session. You needn't worry about putting your desktop in an unusable state. The settings will test adjustment, and revert to previous working configuration if not confirmed.

On the PBP, I find that 125% is a perfect scaling - not losing too much real estate, but keeping me from hitting <CTL-SHIFT-+> on every other page in Firefox!
It keeps me from also doing a bunch of "no-squint" customization on my terminal profiles, too.

The framebuffer text fonts are also small enough by default, to make your eyeballs feel like you've been scouring them with fiberglass, after an hour or so.
On Debian you can get a reasonable sized-typeface by switching to one of the TTYs and running:

sudo dpkg-reconfigure console-setup

The options are pretty simple. I choose UTF-8 as my encoding, because the 90's were a long time ago! Pick Latin1 & Latin5 option for most users, and here's the important part: In font selection choose "Terminus" and move to the next option, picking font size - 16x32 (framebuffer only). Now you can tell the "o" and "c" apart.

These settings will be added to the console setup by init, and be default on all new local TTYs.

Apologies if this has already been posted - I did a search without finding anything relevant.

I have a Raspberry Pi 4 4GB running Manjaro ARM, so I have a good idea of the performance of that SBC. The Raspberry Pi Foundation have said it can replace your PC.. While it's amazing for the money, I don't know that I could use it as an everyday computer. It's close, but I think I'd find it a bit frustrating.

I'm hoping one of you has both an RPi4 and a Pinebook Pro and know how they perform relative to each other. I'm just trying to get a sense of if it would work well for my uses.

My use case is:

• Replace Asus C302 Chromebook Flip - Core m3-7Y30, 4 GB ram
  
• Might also replace Dell Latitude 7370 with Core M7-6Y75, 8 GB ram, alternating Linux Mint, Fedora, Manjaro..
  
• The C302 feels super fast and battery life is great - I'm creeped out by Google's privacy issues, but they know how to build an optimized OS. The 7370 performs ok but feels a bit borderline and battery life is disappointing. They both get Octane scores in the low 20,000s.
  
• Web browsing
  
• Documents, presentations, spreadsheets
  
• No games
  
• Ideally 8+ hours battery
  
• USB-C DisplayPort a must (which the Pinebook has!)