My pinetab 2 keeps on moving sporadically without any sort of input. I have tried removing packages and configuration with the -Rn option. So far I have removed xorg, wayland, libinput, and qt5. I even tried running clamscan, but I didn't get any hits. Please assist.

I love KDE Plasma it's beautiful and functional but it is fairly resource intensive and tends to bog down on the PineTab2. If you don't need the features, switching to LXQt can make things feel a lot snappier. The installation is pretty straight forward but it doesn't work exactly as the documentation suggests it should. So, let me lay it out for you.

First install LXQt with the command :

Hello, I installed pmos on my pp yesterday, the phone recognizes battery empty at 15% and sutsdown, tested on 3 cycles. What can i do to fix it?

Hi,
I want to run my own hobby bootloader/ kernel on the A64. Sadly I couldn't find any information about the new boards LTS variant boot sequence.
There ist he non A64 LTS version of the linux-sunix wiki but the new one doesn't have a section for the boot sequence so I'm wondering wether it's the same.

Next to that, I was also wondering where excatly and in what EL the BROM bootloader is loading my binary from the SD Card to. My assumption would be that I would endup in EL3 somewhere (0x8000 maybe) in DRAM, does that come close?

regards robert

I'm thinking of getting a Star64 to do some practical learning about operating system development and I haven't been able to find some clear/simple information about compatible equipment and the process for setting up a jtag debugging environment. Please note that my experience is mostly with software and I am really, really new to working so close to the hardware.

The Star64 schematics show GPIO pins 0 to 4 for debug trace and pins 9 to 13 for jtag HIFI4 (audio DSP). From the very little that I know about jtag this is the minimum number of pins - so minimum amount of jtag functionality.

I have been looking at the Segger J-Link Edu because it has support for the U74 and E24 SiFive cores in the Star64, but I'm not sure if it is a good choice.

Has anyone setup jtag debugging for the Star64? What hardware/software are you using and can you recommend a beginners guide that can get me started?

I just pushed an experimental update to My Waydroid Manager that added a Gtk 4.0 / libadwaita ui, along with options to install on Mobian, ubuntu, and manjaro currently.

I'm not a senior developer, so it's kinda hacky, and any help polishing it would be definitely appreciated!


https://github.com/MadameMalady/My-Waydroid-Manager

Has anyone tried to replace stock eMMC (16Gb or 32Gb) with a bigger eMMC (in a phone repair shop for example)? Is it possible? What models are compatible?

I got my pinebuds yesterday and out of the box they didn't work correctly. They continuously cut out making them unusable. I tried resetting them and they wouldn't even reset. I hit the reset button in the middle, the charging LEDs flash, close the lid and nothing.  

I tried flashing new firmware in a docker on my pinebook pro and couldn't because its not arch64. Which I find ironic that I have to have a windows machine or a different type of computer other than a pine64 product but I digress. 

I'll try it on my desktop later but has anyone else been able to successfully reset them?

Right after I got my PineTab2 one of the first things I did was to run a sudo pacman -Syu to update the system. But after that I bricked the thing. Luckily it comes with the UART board and I saw that the kernel wasn't working (I think it was not finding it? Don't remember exactly).

I reinstalled the factory image and it's all good. But now I'm afraid of updating the system again. Is updating everything with pacman like this not recommended? Anyone had the same issue or I just got unlucky that time?

I've started developing an app for the Pinephone, my app would be deployed with a flatpak.
My application needs access to system directories to read the device camera.
Doing some testing I've discovered that a native Pinephone application called megapixels doesn't launch if I package it into a flatpak. The error is related to not being able to read a system directory `/sys/firmware/devicetree/base`
In order to diagnose the problem I've run a python terminal inside the container and I've verified that neither `/sys/firmware` nor `/dev/video*` are visible from within the container: