I'm using my RockPro64 as a NAS with open media vault. I'd like it to shutdown or standby at a particular time (this I can do with OMV) and then boot up again the next day at a particular time. 

How can I get the boot up to happen on schedule? I tried using WOL but the board wasn't responding to it. I also tried using OMV to put the system into standby and then trigger a reboot at a set time but nothing happened.

I've found that since there is still 3G service for now, my Pinephone running Mobian/Phosh will sometimes jump back and forth between 3G and 4G. Calling seems to be more reliable with 4G so I went into "Settings/Mobile/Network Mode" and changed that to "4G Only". A checkmark appears next to that, so then I tap the blue "Set" button and it changes and takes effect. However, that setting does not survive a reboot. The next time the phone is turned on the setting reverts to "2G, 3G, 4G (Preferred)".

Is this a bug or a feature, or am I missing something? Is there a way to retain this setting across reboots?

Hi Pinephone team,

Each Pinephone, the Pinephone UBPorts and Pinephone for Mobian editions over the months,

their batteries deplete really quickly and don't hold good charge, and I'm still using a backup Android for most things because of this.

I'm wondering if it's a hardware concern of power usage or it's about the software and how much energy it would take to run a laptop or desktop kernel with all the GUI and classic higher energy usage software on the smaller hardware .

Not sure! I'm only a user .

wellwishes,
food

Hi Mobian team,

I've been using Mobian as my daily driver on Pinephone and it's been working every day.

I'm noticing the battery degrades really quickly over time, and I'm wondering if there's anyone working on increasing the energy efficiency of the operating system

I know I can buy a new battery for not that much money, though I'm concerned about the long-term cost of having a pile of dead batteries whereas Apple and Google have no piles of dead batteries.

wellwishes,
food

Hello PINE friends,

as you may have heard, the Quartz64 has an eInk interface. This allows for high-speed (relatively speaking) operation of a 10.3 inch eInk panel. The controller for this is referred to as "EBC".

The problem, however, is that the downstream driver for this is... a GPL-2.0 licensed assembly dump. Yeah. Thankfully it comes with debug symbols though, so we're actually very lucky in that regard.

Here's where you can come in and help: we need to reverse engineer the driver struct by struct, function by function, allowing us to write an upstream-ready EBC driver. Not only will this allow us to run the driver on mainline kernels (or rather, at all, since it currently doesn't build even on the downstream kernel), but we can also then make it faster, as there seemingly are some math heavy functions.

For more information, check the wiki article on the matter, which includes links to the repositories and some further information. People have also reported good results from assembling the .S into a binary and then running Ghidra on it.

Thank you for your attention and your interest.

Hello,
I can't connect any extern HDMI output over the Dock:
 The DP state is always between:

Sad to announce that both the hinges have completely failed on my Pinebook Pro. The plastic holding the brass inserts have broken into numerous tiny pieces. The plastic bits feel oily to the touch and extremely brittle. I guess I will repurpose my PBP into a headless machine.

Attached Files

Thumbnail(s)
                   

Hello!

Like many before me, I did not buy the USB wifi adapter in the PineStore because I thought that I should be able to use any RTL8812AU chip that I could find. Obviously I'm out of luck and feeling pretty frustrated.

So far, I've been unable to use any android image successfully except for Ayufan's 7.1, and the stock 7.1.2 SD image. The 8.1 SD image is missing partitions on boot (something I read led me to believe this is because the img labeled for SD is actually for EMMC), and the 9.0 image doesn't boot at all. Both the standby and power on lights turn on and stay on any time I've tried to use that image. I read elsewhere that the only working image for 9.0 is the 64 GB one, and I do have an extra 128GB SD card lying around, so I'll try that one later.

At any rate, 7.1.2 works perfectly for my use case with a few tweaks, except I can't get any RTL8812AU chips to work. I have tried 5 different ones just today. I can see the RTL8812au.ko module exists in /system/lib/modules, and DMESG shows that my wifi adapter is recognized, VID/PID and all. When I try turning on wifi through network settings, DMESG says that rfkill-wifi driver failed to initialize successfully, and states that it failed to turn on the generic adapter. Basically there is a missing piece in there somewhere but I'm not sure where.

On ODROID's forums I found this thread: https://forum.odroid.com/viewtopic.php?t=24326 which seems super promising, but I'm not sure how I would go about applying the principles found there to android 7.1.2 on my Rock64. I don't see /etc/modprobe.d or a wifi_list.txt or anything of the sort. Can anyone point me in the right direction?

When I try to have a call on speaker, the other person hear loud noises (noise, not echo or reverb).
Is it the same for you ?

im using an os based on arch.
If you want to replicate the bug, make a call and in alsamixer mute earphone, unmute speaker, enable mic1 boost, and see if the other side hear noise.
Thanks.

I've done several searches and there is one SPI package that appears to enable NVMe boot, but the repo was archived by the developer.

Is there any way to set this up so NVMe is the default boot drive? Without using the emmc at all?

Thanks