Ok, I just got my new ANSI Pinebook Pro today, I have one stupid question..
The trackpad is described at matte everywhere I looked, on mine it's shiny and maybe has a film attached. Is there a film I should remove? I don't want to damage it by trying when I shouldn't...
I would like to be able to receive calls without using a SIM.
Is there an easy way to setup VOIP over Pine so that it will ring and I can accept calls if I have Internet? I'd prefer something where I don't have to manualy refresh to see if there are incoming calls.
I would also like a real number that goes to the VOIP.
Hello again,
Is there any way to configure suspend? My alarm didn't go off yesterday, I found a missed call, and I have my perennial problem of not being able to play more than 1 song before manjaro-arm phosh beta 11 goes into suspend mode. Thanks.
I recently flashed Mobian to my emmc and running it as my daily driver for about a week now.
Love it but I am unable to play video files I download (mp4) - I receive "An Error Occured - Driver did not accept the bitstream paramters".
I've upgraded and updated to the latest release, even ran apt-get on gstreamer plugins but they say they are already at the latest version. Any thoughts?
applications like gvncviewer dont offer visible options to open the on-screen keyboard.
is there a way to open it?
maybe through the bar at the bottom?
I have the KDE edition pinephone, and after an update, I've seen that when it wasn't plugged, it wouldn't stay unlocked more than a few seconds. Nothing special seems to be happening, just the session getting locked again. I kept making updates, but nothing's changed (well, lots changed, but not this specific issue).
I checked out what happened with journalctl, when unlocking the phone while unplugged:
Code:
-- Journal begins at Sun 2021-06-06 02:39:45 CEST. --
Jun 11 19:23:01 plasma-mobile mtp-probe[7231]: checking bus 1, device 15: "/sys/devices/platform/soc/1c1a000.usb/usb1/1-1/1-1.3"
Jun 11 19:23:01 plasma-mobile mtp-probe[7231]: bus: 1, device: 15 was not an MTP device
Jun 11 19:23:02 plasma-mobile upowerd[4309]: treating change event as add on /sys/devices/platform/soc/1c1a000.usb/usb1/1-1/1-1.3
Jun 11 19:23:02 plasma-mobile systemd-logind[3705]: Watching system buttons on /dev/input/event7 (SEM USB Keyboard Consumer Control)
Jun 11 19:23:02 plasma-mobile systemd-logind[3705]: Watching system buttons on /dev/input/event6 (SEM USB Keyboard)
Jun 11 19:23:02 plasma-mobile systemd-logind[3705]: Watching system buttons on /dev/input/event8 (SEM USB Keyboard System Control)
Jun 11 19:23:02 plasma-mobile mtp-probe[7261]: checking bus 1, device 15: "/sys/devices/platform/soc/1c1a000.usb/usb1/1-1/1-1.3"
Jun 11 19:23:02 plasma-mobile mtp-probe[7261]: bus: 1, device: 15 was not an MTP device
Jun 11 19:23:04 plasma-mobile xdg-desktop-portal-kde[4529]: xdp-kde-background: GetAppState called: no parameters
Jun 11 19:23:34 plasma-mobile xdg-desktop-portal-kde[4529]: xdp-kde-background: GetAppState called: no parameters
Jun 11 19:23:50 plasma-mobile dbus-daemon[3694]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.39' (uid=1000 pid=4342 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
Jun 11 19:23:51 plasma-mobile dbus-daemon[3694]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Jun 11 19:23:54 plasma-mobile dbus-daemon[3694]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.137' (uid=1000 pid=7269 comm="/usr/lib/kscreenlocker_greet --immediateLock --gra")
Jun 11 19:23:54 plasma-mobile dbus-daemon[3694]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
Jun 11 19:23:54 plasma-mobile dbus-daemon[3694]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.137' (uid=1000 pid=7269 comm="/usr/lib/kscreenlocker_greet --immediateLock --gra")
Jun 11 19:23:54 plasma-mobile dbus-daemon[3694]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
Nothing really stands out to me... I see something related with kscreenlocker, but I don't know what happens there.
As probably already known, support for the PineBook Pro's video console has recently been included in the U-Boot packaged by Manjaro ARM. That's awesome and, for someone coming from the x86 world, makes the PineBook Pro feel much more like a "real" computer that isn't silent early in the boot process. The support for the video console is currently in form of a patch, but the patch should be merged into one of the next releases of U-Boot.
However, this new U-Boot feature isn't issue free. In the first couple of seconds after powering up the PineBook Pro, before any text is displayed, there are some weird screen artifacts that last for a split second. After the U-Boot messages are displayed and right after the kernel image is loaded and started, the same screen artifacts become visible again, this time much better and lasting for a bit longer. These artifacts are probably caused by some mode switching and the old, gargabe contents of the framebuffer memory.
Before digging a bit deeper into this, I'd like to ask if anyone else sees the same visual artifacts? The attached pictures show the screen contents right after the kernel image is started, with the very start of the artifacts in the first picture and the "fully developed" artifacts in the second.
Today's Plasma Mobile image Manjaro-ARM-plasma-mobile-pinephone-20210610.img does not boot past KDE logo with mouse cursor.
Also - when you update your current working setup to todays latest software, then the result is the same - KDE logo with mouse cursor.
So - be warned
Ironically - Plasma Mobile Dev image boots OK
The support for the video console is currently in form of a 
