Hello Forum,

I had to change my screen and apparently lost the approximity sensor. Simultaneously I fired up Mobian on the internal storage.
When booting into it, the screen dims down after a couple seconds.

I would like to keep Mobian and found out that I have to disable the proximity sensor in the config files. Problem: I don't know how I can gain root access to the mounted phones storage (under Ubuntu).

Alternatively, I could also reinstall mobian having the proximity sensor disabled before. Unfortunately I also don't know how to do that.

If this is not mobian-specific enough, please let me know and I will delete the thread. Anyway, I would be very glad for any hint to solve this problem.
Thank you in advance

Hello,

I purchased my PinePhone Braveheart edition (v1.1) first time when they were launched (ordered in November 2019, received it in February 2020).
The microphone has never worked. At the beginning, I couldn't test it; when the first alpha distros became available and I was able to test the microphone, it was too late to send it back under warranty. Eventually I got a new Side Board, on which the microphone is soldered, and I replaced the original one, but the microphone still doesn't work.


Currently the installed OS is Manjaro with KDE Plasma Mobile. Just after the full OS is loaded, under Settings -> Audio, in "Recording Devices" section, the Internal Microphone is shown:


   


After tapping on the button and sellecting the "Headset Microphone" there is no option to go back to the "Internal Microphone" (see the image below):
   
In my opinion this looks like a software issue. If I use a headset, the microphone on the headset works fine and, if I make a phone-call, I can have a bi-directional conversation.


Any feedback? The next step would be to replace the main board. Or sell the phone on eBay and put a stop to my misery

Howdy Piners:

My pinebook pro didn't have bluetooth, wifi, audio, or display functioning properly, until I installed the blobs.  I'm running slarm64, so it was natural to download the blobs from the sndwvs repository:  https://gitlab.com/sndwvs/images_build_k...s/firmware. 

However, what if something happened to this repository and it went down?  I would feel safer having an additional source.

What other repositories contain pinebook pro blobs, and which repository is "most upstream" and likely to have the most up-to-date firmware?

Since source code is not shared with blobs, then these are certainly something we can't compile ourselves.  Does pine64 have an "official" repository from which it releases these nuisances (sorry I don't like blobs, and would prefer a totally open device with poor non-proprietary resolution on its display and camera).   Nevertheless, since forced to use the blobs if I want full functionality in my pinebook, it would be nice to know from where they can be retrieved?  

Also, will the pbp blobs eventually find themselves in linux kernel's mainline firmware:  git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git?

Hi!

After updating to the latest version of Manjaro ([ARM Stable Update] 2021-07-23) my PBP's splash boot image does not appear anymore.
Only a black screen until the logging page appears.

I think this happens because the kernel boots plash was not added.
It should be like that? Is this a new feature?


Also there is one more annoying thing that happens after this update, my PBP freezes randomly and only a hard restart resolves this. Does this happen to anyone else?

Thanks

Here we compile and run the LVGL library demos on Arch Linux Barebone to show that we can create useful graphics through the Frame Buffer.

https://lvgl.io/

1) Install the basic dependencies for program development
------------------------------------------------------------
`sudo pacman -Syu base-devel`

2) Clone the relevant repositories
------------------------------------------------------------
`git clone --recursive https://github.com/lvgl/lv_port_linux_frame_buffer`

3) Adjust to Pinephone's screen resolution
------------------------------------------------------------
Edit the file "main.c" in "lv_port_linux_frame_buffer" and change Line 31 from 800 to 720 and Line 32 from 480 to 1440,

disp_drv.hor_res    = 720;
disp_drv.ver_res    = 1440;

4) Enable Touchscreen
------------------------------------------------------------
We use the "evdev" event driver, the raw data from the touchscreen for Arch Barebone are output at "/dev/input/event1", the rest of the events in the folder are the the physical buttons and the sense of USB, headphone and vibration.

We need to edit 2 files, "lv_drv_conf.h" and "main.c"

-------- lv_drv_conf.h ----------

Line 389 should be changed to

# define USE_EVDEV 1

Line 397 should be changed to

# define EVDEV_NAME "/dev/input/event1"

--------- main.c -----------

At the beginning of the file we should include the header

#include "lv_drivers/indev/evdev.h"

Right before Line 36 where we call the demo function we should initialise the touchscreen by adding the following code

/* enable event input*/
evdev_init();

/* enable touchscreen*/
lv_indev_drv_t indev_drv;
lv_indev_drv_init(&indev_drv);
indev_drv.type = LV_INDEV_TYPE_POINTER;
indev_drv.read_cb = evdev_read;
lv_indev_drv_register(&indev_drv);

5) Compile by running `make` in "lv_port_linux_frame_buffer"
------------------------------------------------------------
The command will generate an executable named "demo". If you want to change something and recompile then first remove all the object files of the edited files and the "demo" and `make` again.

`rm [edited-files].o`
`rm demo`
`make`

6) Run the program on Arch Linux Barebone
------------------------------------------------------------
`./demo`

7) Exit the program pressing CTRL+C
------------------------------------------------------------


Note :
------------

By default the code runs the `lv_demo_widgets` demo, you can test the rest of the 5 demos by changing line 36 in "main.c" to one of the following choices

lv_demo_widgets();
lv_demo_music();
lv_demo_keypad_encoder();
lv_demo_benchmark();
lv_demo_stress();

then remove "main.o" and "demo" and `make`

`rm main.o`
`rm demo`
`make`

Hi,

Another thread mentions the $1 "PINEPHONE SIDE KEYS FLEX PCB" https://forum.pine64.org/showthread.php?...3#pid91693

I just took apart the Pinephone to replace the earpiece speaker and the on/off button no longer works - or at least not very often, I have to plug in USB-C cable to turn it on. And I can't reliably turn the screen on / off with the power on/off button.

I have removed the back cover and the inner plastic cover that goes round the back - the volume / on / off flexi cable is fully inserted into the motherboard 'slot'.  Vol up / down works fine, still. Looking at the side where the black and white 'cover' is on the vol up/down and on/off keys with a torch, the top of the on/off key area seems to have lots of small creases / thin vertical lines across the top half - I don't know if that would be the issue or the flexi itself?

Standard shipping to Adelaide, Australia is US$12, so very expensive US$13 total. Is there anywhere else I can buy it with more reasonable shipping?

Any suggestions as to what I could try to 'fix' this? I'm starting to realise that a lot of parts seem very fragile and can apparently be easily damaged when taking apart / putting back together. I have been very careful but you have to bend the flexi to get it back into the motherboard 'slot'.

Thanks for any advice. Anyone in Australia ordering something please let me know - it would be great to be able to reduce shipping costs. Not quite sure if I can live with it as it is. I might just switch back to my Android phone with Lineageos and without google apps!

Following the latest update of chatty (chatty-0.3.3+16+g11c76c6-1-aarch64), the app no longer shows the messaging history. The database file home/manjaro/.purple/chatty/db/chatty-history.db remains and all the messages are still there, but chatty doesn't read them for some reason. I tried to downgrade chatty to an earlier version from the package cache, but same thing.

Messaging works and new chats are being displayed in chatty, but for some reason the old chats are not visible.

Any ideas?

Hi,

My earpiece speaker broke after my Pinephone fell out of my jacket pocket. I bought a replacement speaker from aliexpress based on a post identifying compatible models but, even though it works, the volume is very low even at 100%.

With pulseaudio I would use pavucontrol to boost to 150%. Manjaro Phosh uses pipewire and pavucontrol doesn't work. Does anyone know what I can use to achieve the same result. Speaker is unusable as there is a massive echo so callers hear themselves, and I would like to be able to use the earpiece rather than having to use an earpiece - though that is the best solution, I think, once you've managed to untangle it, push in the earpieces and plug it in!

Command line would be fine, ideally something that survives reboot.

Thanks.

I'm using a 1.5A USB charger, and that is barely able to charge the battery faster than I am discharging it. When I plug in that same charger through the docking bar, I see that the USB current limit is only 0.5A, and that is definitely NOT enough to keep ahead of the discharge.

Is this a known issue? Is there a fix?

This is a beta edition, convergence model,  running Mobian/Phosh from the SD.

Hello all:

When should I be satisfied with upgrading via the apt package manager, and when should I do a complete reinstall? Are there changes that occur in the updated Mobian images which are not implemented when an old installation upgrades via apt?

An example: When I installed Mobian in October 2020, full disk encryption (FDE) was not available so I had to hack together an encrypted /home/ partition using cryptsetup and LUKS. Then, some time in December, the Mobian images packaged a native FDE setup tool. If I were to reinstall now, I could set up FDE natively.

Is FDE an *exception* or the *rule*? Am I missing other important features and fixes by upgrading via apt?

Thanks again