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
Quote:OpenGL ES 3.1 most notably adds compute shaders, indirect draw commands, and other additions. Meanwhile OpenGL ES 3.2 is the latest upstream spec for this mobile-focused graphics API. Arm's Midgard 2nd Gen taps out at OpenGL ES 3.1 while Midgard 3rd/4th Gen and Bifrost are ultimately capable of OpenGL ES 3.2 once this open-source driver support has been wired up.
Just what it says. Manjaro Phosh Beta 10 is excellent. Approaching daily driver levels. I've been messing with it all day (instead of doing my work). The only times that I've had any problems is when I got over-enthusiastic with "customization" and broke it a few times. Totally not the system's fault, and besides, it's fun going in with JumpDrive and fixing it. Always boots right up and is super stable as well. It's come a long way since I got my PinePhone back in January.
My biggest complaint is that the selection of browsers leaves a lot to be desired.
Firefox is very full-featured and works well, but it's a battery hog. Not viable for full-time use. It would be nice to have a fully functional lightweight browser for light browsing and only have to use Firefox for heavy duty stuff.
Today, I tried the following:
Gnome browser (slow as ****, can't open links in new tab, dealbreaker)
Otter browser (same, UI is bad)
Falkon (Fast, works, but UI is awful)
Midori (Oh, so slow.)
Qutebrowser (Keyboard oriented, so forget that)
Luakit (wouldn't even start)
Probably a couple of others too that I don't remember.
Anywho, remembered from my time with Plasma using the Angelfish browser. Once I got it set up to my liking, it was really lightweight, fast, and easy to use.
So, just to see if it could be done, I decided to install it on Phosh. And lo and behold, it worked. But, none of the buttons (forward, back, home, etc.) have labels on them. Just squares at the bottom, except for the tabs button. I have to try to remember what the buttons do and sometimes I get it wrong. But, it's SO close to being 100% what I want.
So, what do I install to get button labels on Angelfish?
I had my clusterboard run for about two months and today i've turned it of to add new modules. but when i turned it back on, within a minute, one of the bateries exploded. Well started to bubble and sprayed some juice out.
Is this a common thing for normal batteries explode in cluster board, or was it just a rare case? Just a general AA alkaline batteries.
so 20 minutes later, another set of batteries - another explosion
and the think i've did today was: adding 3 SOEdge boards next to 3 SOPINE boards
The support for the video console is currently in form of a 
![[Image: Screenshot-from-2021-06-10-19-08-53.png]](https://i.postimg.cc/fLQVn7xY/Screenshot-from-2021-06-10-19-08-53.png)
