The A72 and A53 core are each (according to Rockchip) optimized for, respectively, high-performance and low power.
How does our system (linux kernel maybe?) choose which processes to put into which core?

For example, if I'm running a single thread process that occupies 100% of one single core, I would like the system to choose the high-performance core in order to complete the task faster, rather than choosing the low power core to save power.

Do we (end users) have any control over this? Should we?

Hey group,

Switched my CE over to Mobian and i'm quite impressed by Phosh and by the Mobian underpinnings so well done. 

Quick question, if I install the nightly and run an apt upgrade, will this pull down the latest changes upstream from the mobian project? Or will it just upgrade the base Bullseye packages? Are there repos set up for Mobian yet is essentially my question.

Thanks!

My ANSI keyboard arrived recently (to replace ISO one) along with NVME controller and I thought I would share my experience after mostly gentle disassembly and reassembly. Let's start with effect right after assembly:

1. Both screw standoffs were broken (I guess that's what was making noises since receiving PBP)
2. New keyboard basically did not work -- more than a half of keys did not result in any code, the rest was acting funny ie: key '1' resulted in '1', key '2' resulted in nothing, key '3' resulted in '2', key '4' resulted in nothing, key '5' resulted in '3' etc
3. Daughter board is dead
4. Possibly related to 3. USB2 devices do not work when plugged into USB3 port (forget about external keyboard, mouse or YubiKey). USB3 devices work perfectly fine though.
5. Touchpad did not work

About keyboard:

I was struggling between two options, whether to raise complaint to support or try new firmware. I realized I did not know where keyboard firmware is actually located -- if it's on the main board then it's wrong since it was for ISO keyboard. If firmware is directly on the keyboard then newly arrived keyboard was completely broken. Fortunately installing new firmware helped (after few attempts out of which few ended up in errors). Note that installing firmware is extremely complex if 1) you cannot attach external keyboard (no USB2 devices),  2) your WiFi connects after logging in (no SSH) 3) you cannot login since you don't have any working keyboard.

About daughter board:

that was the only "non-gentle" operation. The cable going into daughter board would not come off no matter what. I used a little force and it turned out the port on daughter port was somewhat broken -- smashed pins on one side. Might be the reason why USB devices worked like 50% of the time in USB2 port. Anyway lesson learnt: if you don't have to unplug something -- don't. Chances of breaking something are too high.

Now not really sure if USB2 devices not working in USB3 port is in any way related to daughter board -- that would be peculiar. Perhaps it's just some shortcoming of device tree file which assumes USB2 availability only if port on daughter board is available? Can someone from Pine sched some light? Unfortunately my usage patterns are way too reliant on YubiKey (PGP, SSH, CR) which identifies as USB2 device. If it is related I'm looking forward to replacements parts availability.

About touchpad:

After replugging a hundred times I did inspect cable joining board and touchpad and turned out one of pins was skewed. After "straightening" it touchpad worked again.


As for good news NVME adapter worked fine from the start with WD Blue SN550.

One thing is for sure: if I every open up PBP again, that would be just for replacing daughter board. Everything inside is just way too fragile.

I noticed my PBP was very warm after having put it to sleep then plugging in the power (this happens with the plug as well as with usb-c charging), and noticed that after more than half a day charging, it wasn't fully charged.

Then I tested, and found that it will turn on when I plug or unplug the power.
Is there any way to change this behaviour?
Or are there good reasons for it? (In case the keyboard malfunctions, it would be a way to turn on the device and then a usb keyboard could help out... just making wild assumptions why this behaviour might be designed in...)

For now I have configured Manjaro KDE to shut down after several minutes of idling even when running on mains power (I only had that setting when on battery power), have yet to test the setting.

The reason I have issues is that I have a generic 4 port usb charger device with a power switch on the mains cable, and it's not all that uncommon that it gets switched.
This conflicts with me assuming that after several hours, my PBP will be fully charged...

I have a pinebook pro running the Manjaro KDE default install everything is working fine. I'm very pleased with the device. I had ordered an additional eMMC of 128GB to replace the 64GB eMMC with. So I installed an other OS, Manjaro I3 SD card image, on a micro SD card I owned (samsung micro sd hc card of 32 GB read and write speeds not known..) and I am experiencing some weird boot issues.

Here are the scenario's:
- If I shutdown the pinebook pro insert the SD Card and power it on, I get the orange light, turning green, but the device won't boot from the SD-card.
- If I boot from the eMMC, insert the SD Card, mount the boot partition of the SD-card and restart the device, it boots without any issues from the SD-card.

Now if I want to replace the eMMC with the 128GB one I am not able to boot from the SD-card as it won't boot from a 'cold' start.

Might this be an issue with the SD-card being to slow? or is this some other problem? I've done the above two scenario's many times over and over again and it always succeeds when first booting up from eMMC, inserting the SD Card, mounting the boot partition of the SD-card and reboot.

In this thread I will be posting a short changelog of the Panfrost changes in Mesa when they arrive in Manjaro stable mesa-git.

This changelog will be useful even if you don't use Manjaro, but it may be out of sync to when you get the changes - Manjaro is between one and three weeks behind upstream mesa git.

Hi! Brand new UBPorts CE user here (as of a couple days ago).

I've been browsing through the wiki / forum and found myself wondering what the best place is to receive updates regarding the state of UBPorts on the PinePhone right now. Some of the basic things I've done right off the bat:

1. Switched from "stable" to "development" under Settings > Updates. This got me on the latest OTA, with more updates to come.
   
2. Got GPS / Location services working for uNav, Clock, etc. Thread here
   

• Camera app is always blank / shows a black screen. I assume camera support is nothing right now?
  
• Encryption: Is there a way to enable disk encryption for the phone and/or any mounted microSD cards? Is it enabled by default and I can't tell?
  
• For that matter, is there a tutorial or any pointers for utilizing a microSD card with UBPorts? I assume I need to format it and set the filesystem myself, but that somewhat relates to the above question regarding encryption since I'd have to have LUKS set up before I figure out the filesystem. And how would one tell apps to use that SD card for storage instead of the eMMC flash?
  
• Touch-responsiveness is fairly low, although I have noticed improvements after changing to the development channel. Can we expect more fluid touch response or is Unity8 capping this out?
  
• Headphones don't seem to be detected? I've been having similar issues with my Pinebook Pro, but I'm not sure if the two are related to some upstream kernel thing or not.
  
• Is there a list of features UBPorts devs are currently working on, or a changelog of what is coming out with each release? I'm noticing on the Development channel there's typically an update once a day, which is a pretty solid pace, but it is very sparse on details.
  
• What's the best way to get started writing apps for UBPorts / Pinephone in general? I know something like libhandy exists, but I was wondering if there's anything in particular that makes development easier? SSHing in to deploy / install should be workable, but I'm not sure I understand how apps are sandboxed (if they are at all) or how once could develop on say stock Debian or Manjaro on a Pinebook Pro and deploy to UBPorts with the least amount of overhead.
  

 *
  Just-a-Thought :

An extra slot for a second SD card could sure come in handy !
  ( may be space to just tack another slot on top of the existing socket)  ?

Many of us like to run our Pine phones or our Pinebook Pros operating systems from the SD card.

But being able to take files easily from one O.S. to another is a bit of a problem.

Wonder if that could be a possibility on some next gen Pine Products ?
   (it may not be feasible, .. but I think it is a fair question to at least ask)

That could "One-Up" many of the more expensive products.

@Luke  ?
@tllim   ?

Hi All,

Does anyone know if the Quectel EG25-G modem is able to receive the new WEA or older CMAS alerts for tornados, amber alert, etc.?

Thanks,
Chris

I've had this issue on several versions of ubports (reflashed) and it's still there on the latest stable branch (v3). This may very well be a hardware problem, but i've yet to have any issues with mobian.

Video of the issue: 

It happens often (+-5min)
Can this be related to a high dram clock speed or would that have effected more than an isolated app? #noob