Since VLC is currently my best working media player on the pinephone, at least in Mobian repos, I wanted to post a little hack if you can get the UI sized right to use the prefrencees window, it might also be possible to edit a .conf file which is far easier with the limited UI size.
If you don't like the VLC red winter cap which appears in and on the orange pylon in December it is now easy to remove on any current Linux and other desktop OSs, no more hassle commenting-out and recompiling VLC to keep the standard year round appearance.

1. Open VLC Player,

2. Click on Tools and select ‘Preferences’

3. Now at the bottom of the window select “All” under ‘Show settings’

4. Select Interface > expand Main interfaces, select ‘Qt’

5. Scroll down in the right pane and remove tick mark for “Allow automatic icon changes”,

6. Click the save button and close the preferences dialog popup

Hey everyone, I just replaced my screen. Why will my touch part of the screen not working?
Thank you for your help

I have been using "chkrootkit" on my Ubuntu desktop for awhile. I saw that it was available for Arch Linux desktop, but not for Arch Linux for PinePhone. When I tried "sudo pacman -S chkrootkit" an error message appeared and said that it was not found. I didn't see it on the Arch Linux wiki or on chkrootkit.org for "ARM". Is there a recommendation for something similar?

I have a RockPro64 booting 5.10.0-7-arm64 #1 SMP Debian 5.10.40-1 (2021-05-28) aarch64 GNU/Linux from microSD.

USB-flash drive does mount in the USB-C port, but I need to do ethernet-over-USB, so I need the USB-C port in peripheral mode.

But the kernel is configured with:

• CONFIG_USB_OTG not set
  
• CONFIG_OF_OVERLAY not set 
  
• device-tree dr_mode="host"
  

I'm super excited about the PineNote but read things from the announcement months ago like "expect to write software for it, not to write notes." On the current store page it says "Most of the device’s functionality, including the e-paper display, do not work at this time." This made me think I just need to wait but then I saw that someone (@pgwipeout) already had something working on screen almost immediately after getting their device.

Months have passed since then but I'm not sure of the current status or where I'd start if I just bought one and tried to learn what I need to enable bootup with working e-ink screen and basic note-taking functionality. I'm a developer, but not an embedded/mobile developer so I'm wondering how I know things have progressed to where I can at least boot the thing and see something on screen. How hard would it be to get it to just let me write notes? Could a super simple temporary solution be to just create a webpage that enables note-taking and use that from a browser on the device? Anyone know any status updates (or where to look out for them) or have pointers in the right direction for a newbie?

***
Please Give us a date that sales will open for the Pinephone Pro "Explorer Edition"  ?

Hi everyone,

for some weeks now I keep missing calls because my pp is not ringing anymore
What I tried:
1) checked the system settings, also for audio output etc
2) called myself and plugged in/out my headphones while the phone was vibrating

How can I fix this?

My only idea for now is to switch to e.g. Mobian, but I would really like to keep my arch/phosh setup.

Dear all,

do you think this following tandem will work via USB-C only?: Eizo FlexScan EV3895 <-- USB-C --> RockPro64

The USB-C connectivity should do the following:

• power
  
• LAN
  
• Monitor
  
• peripherals (Mouse, Keyboard, USB)
  

I've been looking at getting one of the similar devices (Remarkable, Boox, etc) that's e-paper with pen support for a while, but they all seem to have pretty big downsides ecosystem-wise, and I was so excited to see Pine64 launching this. I know KOReader is supposed to be quite good as a reader, and has good options for reading an A4 document on a smaller screen. However, it doesn't have drawing support. So, I figured I'd take a look at what it would take to adapt Xournal++ for smaller, slow-refresh screens.

Is there any indication on how inputs will be handled? For example, how do we distinguish between touch and pen input? Palm rejection? It'd be nice to have an API over (I assume?) libinput, so that we can have more uniform drawing options in many different applications. I guess something like that will be needed for the UI, whether it's plasma mobile or a modified plasma desktop.

(A dream is to be able to use something like this for presentations: load the slideshow as a PDF, annotate in real time and use the built-in damage tracking of e-paper drivers to send high-quality updates to a buffer on a computer)

I was listening to music with audacious when after about five minutes my bluetooth headphones disconnected.
This also happened when the speaker was playing music, as the music simply turned off on the phone.