Greetings,

I'm running Mobian on a v1.1 Pinephone. Unfortunately, every time I enable the hardware switch for the 3G modem it becomes a small convection oven and it goes very hot indeed. I've noticed the same issue happen on my phone with Ubports and Postmarket OS, so the blame doesn't rest with any particular distro.

This is a source of concern. I'm worried that this will wear down my hardware due to the excessive heat.

So, has anyone else noticed the same happen with their modems? Is it a known issue and is a fix planned? I'm hoping it is a driver or power saving problem, and thus solvable through software. If anyone needs more details from my phone, or details of my mobile network to see if it is particular to a certain UK mobile provider, I'll be willing to share.

Regards, R.T.G.

Does anybody have an advice about activating the wifi network discovery on fresh manjaro installation (or when running from SD card)?
When I got the PBP the wifi worked on manjaro but soon after started to show no networks and failure in activating the wifi network interface. I reinstalled manjaro and separately ran from SD card and it's all the same. I also made sure the wifi hardware switch is not activated. When running fedora on an SD card the network discovery works fine.

What can I do to resolve this?

Thanks

Greetings,

I was wondering if anyone has successfully adjusted the trackpad acceleration? The pointer moves a bit too slow for my liking.

A command exists for the synclient on Linux: https://wiki.pine64.org/wiki/Pinebook_Pr...d_settings. But that's a different driver on a different OS, of course.

A quick look at sysctl didn't bring up anything that looked to do with the trackpad.

I'd appreciate any help.

Regards,
RTG.

Hi!

I have a pinebook pro, and I'm running manjaro ARM with sway window manager and it's great

...except the latest update broke the battery indicator, and I've no idea how to fix it. It now shows 100% all the time, occasionally flipping to 0% now and then.

Sway seems to use WayBar for the status indicators, and I found the manual for that here: https://github.com/Alexays/Waybar/wiki/Module:-Battery. This seems to indicate it uses the values in /sys/class/power_supply/cw2015-battery/ to read the battery level. Doing that myself seems to give me a sensible looking answer (laptop has been on for a couple of hours)

[martin@martin-pinebook ~]$ cat /sys/class/power_supply/cw2015-battery/capacity
88

Is anyone else experiencing the same? anyone know how to fix it..?

Hi,

I find advertising the Pinephone as "Linux-only" on the main website a bit irritating. I mean. it's a relatively open device and capable of running any systems that get ported to it. And it is supported by SailfishOS, Android to some degree as well. Suggestion: Change it to "Linux-first".

I can't access any MicroSD inserted into my KDE-Plasma Community Edition PinePhone. I'm not trying to boot off them, I just want to access them as storage. I've tried two cards, a 64G and 128G. Both were formatted as ext4 from my laptop. They do not appear in the results of `lsblk` from the terminal in my PinePhone. I've also tried booting from a Mobian install but that seems futile if I can't access an SD card as storage. Does anyone have any suggestions?

EDIT: Cards are inserted in the upper slot.

While I opened a ticket to get an official answer to this issue, I'm also posting here in case there is a quick fix / known issue.

I received today my Pinecil from the 2nd batch. When plugging it to any power source (tried a few PD USB-C, and 12V DC barrel, or from the computer) the screen either stays black, or for about 1 out of 3 plugging events I'm getting a "random dots" pattern



Reading around in the forum / wiki:
- I updated the firmware to the most recent one (following http://forum.pine64.org/showthread.php?tid=12803 as the MASS_ERASE error was present for me too)
Same issue after successful update. Pinecil is detected in DFU mode as you would expect.
- I can also confirm that this device is making an annoying rattling noise http://forum.pine64.org/showthread.php?tid=12859 that seem to be coming from the DC barrel / USB-C side of the device. Opening it up did not reveal anything loose there, but confirmed the location of the noise. Not sure if normal (but slightly annoying to say the least) and unlikely to be linked to my issue as both DC barel or USB-C powering seems to result in random dots pattern.

I will update that topic when I'm hearing some news from the ticket, but hopefully someone else got the same issue and have a fix for it.

A few months ago, I dropped my Pinebook Pro.  Not from very high, about desk level.  The system continued operating as normal, but I found that the power cord had snapped.  I have tried ordering replacements based on the specs of the DC cord listed on the website, but none of the replacements have fit in.

Does anyone have any power cord replacement recommendations?  I'd greatly appreciate it.

Finally got tired of trying to fix the autorotate on Arch, so I decided to go with PostmarketOS. Installed Jumpdrive on an SDCARD and mounted it on my Linux box. Got a strange error the first time I ran pmbootstrap -- but not sure why. Running it again seemed to fix. There were error messages about qemu-arm64-static.  

However, once I got past that I got locked into a death spiral where it tried to set up my password but it had not set up my user. I went into the chroot and edited /etc/passwd to add my ID as user 1000 (this was a mistake). This let me get through setup.

However, all was not well. I couldn't get KDE to start. Turns out my home directory wasn't set up for user 1000 but 10000. So a quick reboot into Jumpdrive to edit that did wonders. I also added a group 10000 with the same ID and added myself to /etc/sudoers because I was locked out of root otherwise.

That did the trick. All works well but no autorotate. However, manual rotation works fine. The Vivaldi arm64 build does not work  But otherwise seems good and also seems snappier than arch did. Network ok, sound ok, touchscreen ok. Did have to unmute and twiddle the mouse settings for sanity, but nothing major.

As a sway user on desktop, I've been trying to use it on my pinephone. One of the shortcomings is that on mobian, most of the phone related functions are (well) integrated into phosh and I didn't want to loose that. 

Sway use on the pinephone is mostly interesting in docked mode or when a keyboard is plugged in ...

I've identified 3 ways to achieve sway integration 

 1 - run sway on a tty
 2 - run sway inside phosh
 3 - replace phoc with sway as phosh compositor

1 is trivial, you switch to a tty (Ctrl+Alt+F1 on the keyboard), log in and launch sway. It works well but is not really integrated. For instance, when you receive a call you need to switch to phosh terminal, and so I quickly abandoned this solution

3 seems to need some work and might not be feasible due to the way phoc and phosh seems to be tight together through D-Bus things ...

2 has always had my preference, and I didn't know why it never worked when I tried it, since as sway can be used as a wayland client, it should be as easy as typing sway in a terminal. Today I gave it another try and figured out what was wrong. Before launching phoc it restricts WLR_BACKENDS to drm and libinput. And sway was using this variable. So to run sway this way all you have to do is type WLR_BACKENDS=wayland sway ... and it magically works.

Then to use it fullscreen I associated toggle-fullscreen command to Alt+F11

There are still some issues, one is that sway don't get the good keys from the squeekboard that runs in phosh. But this way, you can keep a full desktop in a corner, pop it up when connected to a screen or just to a keyboard, and I find this quite interesting ...

Hope it will be of some help to some of you

Regards,
--
FdL