Following the instructions here on an archlinux:

https://wiki.pine64.org/wiki/U-Boot

For arm-trusted-firmware v2.4 I am getting:

I see the pinecil can be ordered from Amazon. Is this a real pinecil or is this a fake?

Thanks-

I'm trying to install Mobian on my PP64, but it won'T work without tow boot (tried it with jumpdrive regardless but failed). Can someone give me a detailed guide on how to install tow boot? I'm sick and tired of reading "tow boot is made to make the booting process boring" for like a million times without any proper instructions.

Pinebookers,

I ordered my PBP in late 2019 and have enjoyed it since. I call him bob. I don't use bob daily for work but use often. Bob has traveled to 5 countries so far with me.  Now I want to do something I've never gotten to work.  Hook to an external display. I would really like to play videos on a bigger screen.

I've seen a couple other posts but all are from 3 years ago or so.  I just thought there might some newer thoughts.  For hardware I've tried with a USB-C to HDMI adapter I had around and I also bought the Pinebook Pro Docking Station (PBP-DOCK11) years ago and had no luck with it either.

I played with a couple Linux dists when I first got it but decided to stick with Manjaro.  I've applied all the updates.
[thorson@bob ~]$ uname -a
Linux bob 6.7.9-1-MANJARO-ARM #1 SMP PREEMPT Sat Mar  9 21:00:40 UTC 2024 aarch64 GNU/Linux
[thorson@bob ~]$

The special keys have never been correct.
  Fn F1-F2 and F4-F8 work
  Fn F3 seems to only produce the letter "p"
  Fn F9-F12 are mapped wrong but I figured out years ago how to get by.

 
It's Fn+F3 that I think I need.  I can find no description on what it's supposed to do but the picture looks like the laptop with another screen behind.  That's probably what I need fixed somehow.

Any idea out there?

Bill

Greetings everyone, just got a used Pinephone Pro (and a pinephone but haven't used that yet) and am trying to dredge up years-old pre-brain surgery Linux knowledge to make this thing work as a palmtop full time. Currently I am running Mobian with XFCE and I am working on getting the keyboard and the screen rotation working correctly. With regards to the screen, I have two lines in /etc/lightdm/lightdm.conf (which may be the wrong place but one tutorial mentioned it so I'm using it for now)

[Seat Defaults]
display-setup-script = xinput set-prop "pointer:Goodix Capacitive TouchScreen" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
display-setup-script = xrandr --output DP-1 --off --output DSI-1 --primary --mode 720x1440 --pos 0x0 --rotate right

The first line fixes the touchscreen so I can use it in landscape mode from within the OS. The second makes the greeter landscape, but now the touchscreen is equally broken (swipe to the right, cursor going up) in both the greeter and the OS itself because the first line is "cancelled out." If I comment out the second line, the first works.

I've barely managed to scrape these solutions together from tutorials and I have no idea why one would mess with the other and I'm completely lost. Any ideas? Ask me anything and I'll answer what I can.

(Also I'm doing my best to follow the rules but my reading comprehension is not the best so please if I am breaking any I swear it's an accident and will correct it asap)

Hello all, 

I was wondering if anyone had a fix to the following problem I ran into when setting up WIFI and Bluetooth functionality on the PineTab. I got through the WIFI setup without issue and it works great, but when running the following to setup Bluetooth:

Hello,



I have been using and loving my PineTime for almost 2 years, and it has suddenly developed a hardware issue. The touchscreen will not respond to touch, and the battery drain has gone from 16 days on a single charge to 2 days. I have rebooted the PineTime twice, flashed it from 1.13 to 1.14, allowed it to drain completely to shut it off, and nothing has helped. I'm not sure what could have caused this, I didn't drop or hit or soak it, from the battery drain it looks like it started at 5am when I was sleeping. Is there a way to repair it? All the other functions such as the step counter, bluetooth pairing, the physical button, notifications display etc all work.



Video:

https://imgur.com/Y7MA8Xq



Gadgetbridge showing it started at about 5am:

https://i.imgur.com/evRUXXr.jpeg

There are at least eight threads in the PINE64 forum discussing security of the OS used on the PinePhone... :

id=13214 - "Firejail: Sandbox Pinephone/Pinetab Apps"
id=16110 - "Most secure option for phinephone"
id=13179 - "PinePhone Security"
id=14709 - "Security/Musl Question"
id=12457 - "Secure Mobile OS"
id=12303 - "Securing / Hardening The PinePhone"
id=12210 - "Can internal PinePhone firmware be compromised?"
id=11430 - "Security Based OS ?"

...but none of them mention Kicksecure.

According to three threads on the whonix forums:
https://forums.whonix.org/t/whonix-for-a...pi/723/209
https://forums.whonix.org/t/cross-buildi...md64/11607
https://forums.whonix.org/t/whonix-on-ma...g/11310/40
it is possible to use Kicksecure on ARM, including Raspberry Pis and Apple Silicon.

I can't find the Github link right now but I did see that SkewedZeppelin is already using at least one Kicksecure component in DivestOS, so it's not unprecedented that Kicksecure might be applied to a #MobileLinux ARM device.

So my question is, what would the PINE64 community think of converting a Mobian install to Mobian-Kicksecure ("Sneakernic"*, anyone?) on the PinePhone?
*nod to Sonic the Hedgehog

Pinetab is an excellent product.

I'm working on getting the Bluetooth connected. The page Wifi and Bluetooth on PineTab 2 mentions the command

I had Armbian running from a MicroSD card for a while and it worked pretty well. I did an "apt dist-upgrade" the other day and now it won't boot into a graphical desktop. And it doesn't come up on the network because I can't ping it.

I installed the latest Armbian onto another MicroSD and it doesn't work either.

So their image for the Pinebook became broken probably in the last few months.

I tried an earlier image from 2023 and did an "apt dist-upgrade" on it and it broke too.

Sucks. That is a nice OS.