I have two Rock64 boards:

• One is Version 2 (4GB).
  
• One is Version 3 (4GB).
  

• The first one appears to be related to an Intel PRO/1000 NIC.
  
• The second one appears to be a Realtek RTL8211 NIC.
  

1. When setting the MAC address: It should begin with 00:06:dc (i.e., The OUI of Syabas Technology [Amquest]). [ Reference ]
   
2. The accepted solution is to specify the MAC address manually in /etc/uEnv.txt using the macaddr= and/or the eth_addr= settings. I may be wrong - But I believe that these settings are now located in /boot/armbianEnv.txt. [ Reference ]
   

1. Have I overlooked something besides the solution proposed on the Wiki page? i.e., WNpctool.exe
   
2. Is there a solution for folks that don't have MS Windows in their environment? e.g., Linux "purists"
   

Hello,

Fairly new to the whole PinePhone experience (got my first phone about a week ago), but so far been really enjoying messing around with the phone. I have been customizing Mobian (Phosh) and currently have it on eMMC of a 2GB / 16GB Manjaro Pinephone. I went ahead and ordered another phone (3GB / 32GB Mobian version) and I was wondering what would be the easiest way to transfer this setup (if possible) of what I have currently over to the new phone, once it is shipped and delivered?

Make an image? using dd? Transfer over to SDCard? Another way? 


Thanks for any help!

I just received my PinePhone, but can't make calls and texts don't work.

I know I need to enable VoLTE because my provider is T-Mobile in the US, but following the instructions I found here has not worked.

Specifically, when first booting, the phone recognizes my SIM and finds an access point, but after performing the commands listed, those settings go blank.

How can I proceed from here?  


Additionally, the phone goes to sleep and locks the screen after far too short a period of time. How can I change or disable this? There is nothing under settings.

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.