I went to an AT&T store and purchased a sim and phone number for my PinePhone. The rep told me that when they input the IMEI, if it was not allowed on the network, it would have said so. There was no notification that the IMEI was not not approved for use on the network.

I insert the sim and the phone never registers with the carrier network, all settings are correct, APN, etc., but still no registration. Reviewing the posts on the forum, this is a known issue and multiple people are using MVNO's to be able to use their PinePhone. I have had the phone for some time and when I first received it, I put the sim from my S5 into the PinePhone and was able to make calls, something has changed.

I would like to purchase the Pro but if it is not possible to use the phone to make phone calls unless I play whack a mole with different MVNO's, I don' think it is worth it. Is there any conversations with the Pine64 and the carriers to remedy this or is the current state only going to get worse until the phone is obsolete?

I am not complaining, just disappointed if this is the case. I am a long time OSS user, not developer, and am used to things not working and waiting for it to get developed and lending any help I can, documentation, testing, or whatever I can do to help.

Let me know if what I am reading is the unfortunate truth,

Jon

Performed a screen replacement on my Pinetab (reusing and able to save all parts).

Wanted to document my own repair in case it helps others. - If you follow the steps/video closely you should be safe - be careful with screen.

*MOST IMPORTANT OPENING TIPS:* (many more tips/video/pictures at the link below)

Follow a process of "peeling the cover off the screen." idea. Instead of: "peel the screen off the cover" (ie: more risky/screen pressure inducing)

I found 'thumbnail' ideal as tiny speaker wires line directly inside the cover. Metal/sharp tools would be a bit more risky to the wires.

IMHO, not hard to open once you get the general idea/hang of it down. Save unsnapping corners and (metal keyboard connectors) on bottom for LAST (start in mid point of each side beginning with top side)

(embedded video where I demonstrate opening Pinetab in link below)

(Note: currently screens are not available on Pine64 website, but if you are able to find one on ali (or other places), be sure to only use the same screen model!)

Read/see the process (with many pictures) here:
https://politictech.wordpress.com/2022/0...s-pinetab/

If anything isn't clear on any part of the disassembly/replacement process, happy to answer any questions. 

I am curious if anyone who has deployed the RockPro64 as a NAS have any optimizations that has improved system performance. Especially if they are using a PCIe to SATA adapter. I would like to find/develop a script to reduce the burden of the initial portion of a data sync or even just listing files. Whether as a SAMBA server, local file listing, or during the initial portion of a data backup, the CPU seems to run at max until the file attributes list is populated. Although other optimizations that are useful to you would be of interest too, this doesn't have to be specific to one OS, or one particular filesystem, back up scheme, or system admin maintenance task. Basically what is useful to you that might benefit someone else.

I have 2 RockPro64 deployed as NAS, one hosting Debian 10 and the other FreeBSD 13.0. I have configured it many different ways but both are using 3rd party PCIe to SATA adapters each hosting 3 HDDs. One is a kludge of 1TB disks both 3.5" and 2.5" with RAIDz1 the other is 3 identical 2.5" HDDs in RAIDz1. Other than having SAMBA configured on them, they are currently backups of my main server, which is also my desktop workstation. I have recently been getting into ZFS send/recieve for backups, but have more experience with rsync. ZFS is an improvement but still tedious. Simple commands like ls to list files in a directory will consume CPU cycles to the point of nearly halting the system, and I'm thinking having a scheme of some sort will improve this, that is durable across reboots.

The only reference I found to NAS optimizations on this forum was from a user who appears to no longer be active and they only referenced caching, but did not describe in detail what they did.

Hi

I recently got a Pinecil. I was wondering if I can use the Artis 65W USB-C laptop charger to power it. The adapter specs is as follows-

Quote:Power Output: 5V/2.4A, 9V/3A, 12V/3A, 15V/3A, 18V/3A,20V/2.25A, and 20V/3.25A, Max Power Output: 65Watts
AC Input : 100V-240V( 50-60 Hz)
Compatible with all type C Laptops
Over Voltage / Over current Protection , Short Circuit/Overload protection, High Temperature Protection
Certifications: CE, FCC, ROHS, BIS (India) Certified.

So I just received the pro yesterday. I've only handled it a few times, and just downloaded the mega iso to try and test new distros. But I havn't actually made any changes, the phone won't boot anymore. Initially i thought it was the battery so O left it on the charger for several hours. No change there, still refuses to boot. After a quick search I discovered the recovery mode by hitting the power and volume up at the same time. This also does nothing. I get no indicators, no change in the display. No lights or leds. Nothing. Battery in or out, on a charger, nothing changes. It will not boot.

OK my PinePhone is in the keyboard case. I go into "Settings --> Accessibility" and disable the on screen keyboard. On reboot the on screen keyboard is re-enabled even though the phone is still in the keyboard case.

Is there a way to disable the on screen keyboard so that I can turn it on and off manually but if I turn it off it will be off when I reboot?

Trying to Make the pine64Keyboard userspace-driver on my Pinephone.

php keymaps/map-to-c.php keymaps/physical-map.txt keymaps/factory-keymap.txt build/kmap.h
make: php: No such file or directory
make: *** [Makefile:19: build/kmap.h] Error 127


Anybody know the appropriate php source?

I found a webpage where I discover-sorry for my low knowledge of manjaro- where they say Vivaldi is the replacement of Firefox in Manjaro. But Firefox works very well if you install with pacman mobile-config-firefox as I was told in the pine64 telegram

Last night (2022 Jan 28) the rolling arch updates break chatty.
I updated these apps:

Hello,

I was very happy yesterday to receive my Pinephone Pro Explorer Edition.

After playing around with the preinstalled Manjaro, I decided to flash the eMMC with mobian from the sdCard.

Everything was going well till an error message stopped the process (I unfortunately didn't screenshot the error page).

Since then, my device refuses to boot.

What should I try to get the device back to track?

Thank you for your help.

Best regards,

Jerome Lioret