Hello,

I would like to know if there is something planned for quality assurance for Mobian ?

Thanks

Hi,

I noticed that the tiny red light next to the barrel jack flashes/blinks red with about an interval of 1 second. Searching around the internet, blinking red light seems to indicate something is wrong.

Just got my pinebook pro yesterday, used it the entire day and accidentally totally drained the battery to 0%. I thought that maybe the flashing light was indicating that the battery was under-powered, but even after many hours of charging it is still flashing.

The pinebook seems to work fine as far as I know but I'm worried something will get damaged if I keep using it in this state.

Does someone possibly know what this blinking light means?

Edit: Only charging using the barrel-port with the charger provided with the pinebook.

Update: Leaved the pinebook charging 10+ hours (yesterday) and 12+ hours (today) - the battery couldn't go beyond 21% each day. It seems to be charging but abnormally slow. Will try to leave the pinebook charging for at least 24h to see if it can bypass 21%.

FINAL UPDATE: Turns out my power supply that came with the pinebook and or the barrel-port is damaged/faulty. However, I managed to fix my symptoms - read "SOLUTION" below. My pinebook stopped charging completely and was dead after 24+ hours of charge from the barrel-port. Won't even boot by removing the battery and connecting the bypass cables.

SOLUTION:  Using a USB-C power supply (5V 3.4A) solved all my symptoms. I got a non-flashing solid red light the moment I inserted the USB-C power supply and battery charged to 100% in about 6h. I could also boot using the bypass cables without the battery. I tried to use the barrel-port again now that my machine is restored but as I feared, blinking red light and no charge.

Thanks to everyone who joined this thread. All the information you shared is much appreciated.

Best regards,
Carl

Exercise caution when employing this change; adding the Kali repository to Debian is not endorsed by Offensive Security, the Debian Project, or the Mobian project

Hi
I've had my Pinebook Pro for three days and I like it a lot.  I like the keyboard and I love the battery life.
I just wondered why it was decided to put KDE on by default?
I haven't used KDE for years and years, in my mind KDE and Gnome are both "heavy weight" desktop environments and so for years I used XFCE and more recently I have been playing with LXQT.  For someone who started with Windows 3.1 and Windows 95 I actually feel more comfortable with these "simple" desktop environments.
So is my understanding of KDE / Gnome outdated?  Would the battery last longer and the disk have more space with LXQT?
The KDE Manjaro on the Pinebook Pro seems to maybe prove me wrong but I'm curious to learn.
thanks DNJ

Hi.

After a few weeks of usage with UBports, modem stopped working.
My suspicion is that it might have been broken by crust, since it doesn't work with other images either, and it was having issues for more than a week now (not starting after deep sleep). The other possibility is that it was faulty from the start, and it just died now.
I tried a factory test, and the modem test fails with a boot timeut.
Anyone else having these issues?

FAIR WARNING: After I followed these steps and then updated Manjaro it failed to boot. Until the image itself is updated, I do not recommend installing this variant of Manjaro!
The current Manjaro Gnome image is very old. Manjaro has changed how it updates, so in order to make it update I ran the below command from this comment (https://forum.manjaro.org/t/all-mirrors-.../123901/17) in the Manjaro forums:

1. Edit your
   /etc/pacman.d/mirrorlist
   
2. file, so only this line is present:
   

Hi,

I played around with the H64 on the mainline kernel in Debian unstable (5.7) and the latest uboot (v2020.07). Unfortunately, it seems that neither eMMC storage nor the networking are supported in Linux. They get both detected in uboot and booting from eMMC starts successfully.

I guess this board is not supported yet in mainline, isn't it?

My Pinebook Pro arrived two days ago and it's great, however I have noticed that if I want to move the mouse pointer just a couple of pixels away from where it is that it's basically impossible.

Small movements don't move the pointer at all.

If I put my finger on the trackpad and very slowly move it in any direction it's like, nothing, nothing, nothing, it's moving!

Is this a configuration thing with Manjaro?  does it need a firmware update?

thanks DNJ

Greetings,

I was planning to try my phone as a USB host. I read here that the 1.2a revision fixes the USB CC pin issue. Is there any way to check the PinePhone hardware revision, either by inspecting the hardware or using software? I'd like to check whether I have revision 1.2 or 1.2a before I attempt a hardware fix, or (very unlikely but still) accidentally damage it by connecting a USB3 adapter.

My PP is the UBports community edition.

Regards,
R.T.G.

I have been reading about the new SMS replacement called Rich Communication Services (RCS), but I cannot find any projects working on implementing the standard for the various Linux-based phones. Does anyone know of a project working on it?

Additionally, I am not knowledgeable enough to figure out if the telecommunication providers will translate between the two message types if the receiving end does not have RCS enabled or implemented. Is it possible that as more people start using RCS instead of SMS, Pinephone users will not be able to receive  messages from them (excluding platforms like signal or telegram)?

Is anyone else thinking about this? I am desperately hoping group MMS messages will be implemented in Ubuntu Touch or Mobian sometime soon, but if the world is moving to RCS it seems like a lot of work for something that is going away soon. Not sure when or if the telecommunication companies will stop routing SMS/MMS. Does anyone know more or have thoughts about this?