Hello all,

in case anybody is interested I have successfully bootstrapped pkgsrc-current (www.pkgsrc.org) on the PostmarketOS Pinephone.
I have built some tools that seems to be missing from the official Alpine apk repository

- mingw-w64 (http://www.mingw.org/)  for both the x86_64 and i686 targets

So now you can compile natively code on the Pinephone for Winows x86_64 and i686


You can find my packages (more are on the way) on my repo @ http://45.76.81.249/pkgsrc/pinephone/  
As usual you can track my progress on Twitter @ https://twitter.com/astr0baby

- I have finished a custom build of hyperion hercules - so in short time I will try to run MVS (http://wotho.ethz.ch/tk4-/) on the Pinephone; yes that is
correct - a mainframe on the Pinephone.

Hello,

  Sorry for naive question, but how will developing for PinePhone look like? (I don't have it right now). Is it like regular Linux, so the screen is treated as monitor, I have to use Gtk, etc? Or there is needed extra framework for it?

  I have in mind such tasks as:

• building and showing screen/windows with button, labels, textboxes,
  
• subscribing for GPS position update
  
• waking up phone and showing my screen
  
• forcing phone to turn off the screen
  
• running some processing in the background (like a service in Android)
  
• querying battery status and charge level
  

In order to be able to boot from SD card I used "the U-Boot update script from the mrfixit2001 Debian" mentioned in the Pinebook Pro wiki, so I guess I have that U-Boot loader on my eMMC now. The strange thing now is: in at least a dozen attempts I could always boot the kernel, but often it does not find the eMMC anymore, and drops me to a shell:

Quote:I can confirm that my PBP has the same behaviour. I had the impression that the PBP boot succeeds more often when attached to the power supply.

I've attempted putting:

The PinePhone features a wonderful back cover, especially if you get a community edition.

The PinePhone's back cover can be taken off, and you can buy a new back cover in the store, however this will be much the same, without the CE logo on it.

One thing I think is special about replaceable back covers, is how you can make a phone more your own, and I think OnePlus did a great job of this back in the OPO, and OP2 days.

You had your default back (Sandstone for the OPO, and I'm not aware of what it was for the OP2), but you could go to the store, and buy a different styled back cover (Black Apricot, Kevlar, Bamboo, Rosewood)

It would be really nice to see different choices of backs, that change the PinePhones look and feel a bit, depending on your tastes.

Video of the OP2 covers

Just jotting down some notes, and a question after going through a painful process of trying to get a non-debian derivative Linux OS on my cluster.   

After some twists and turns I finally came back around to a post I saw regarding the arm-image-installer and a F30 image.  

I run Fedora on my workstation, so  all of the instructions assume a fedora build box.

1. sudo dnf install arm-image-installer
   
2. downloaded the raw image file from the Fedora download site and selected Fedora 32: Raw image for aarch64
   
3. Write the F32 aarch64 image to an SD card using the following command
   sudo arm-image-installer --addconsole --addkey ~/.ssh/id_rsa.pub --relabel --resizefs --image=Fedora-Minimal-32-1.6.aarch64.raw.xz --media=/dev/sdc --target=sopine_baseboard
   
4. Move card to sopine board
   
5. Insert sopine into clusterboard
   
6. Connect serial console to pins 6,7,8
   extracted from https://forum.pine64.org/attachment.php?aid=1111 and somewhere else
   
7. Connect to serial console via
   screen /dev/ttyUSB0 115200
   
8. Apply power to clusterboard - and prepare to press a key to "stop autoboot"
   
9. Press the space bar until
   Hit any key to stop autoboot:  0
   appears and you are presented with a prompt `->`
10. At this prompt execute this command and hit enter 
    mi w 1c30000 1f 7; mi w 1c30000 1e a4 ; mi w 1c30000 1c b573 ; mi w 1c30000 1f 0
    found at https://forum.pine64.org/showthread.php?tid=6036
11. Reset the board, either by typing reset or power cycling or the reset button.
    This often does not work the first time.
    
12. Wait for the kernel to load and Fedora 32 to finish initializing
    
13. Answer the remaining installation questions
    
14. Finish and log in.  
    
15. nmcli` should show an active eth0 device
    
16. ip addr should show an IP address from your DHCP server
    
17. Never remove power or reset the clusterboard. 
    

(06-10-2020, 12:09 PM)revoman Wrote: ...
Question to the community.  How do I make `mi w 1c30000 1f 7; mi w 1c30000 1e a4 ; mi w 1c30000 1c b573 ; mi w 1c30000 1f 0` persistent?  Is this u-boot?  is this EFI?  I am a bit out of my league here.

Thanks in advance,
-Nate R

When I suspend my PBP, the device won't wake up.

I get only a black screen with a cursor - it never progresses beyond that. Any ideas?

I'm running the default Manjaru image if that helps.

I seem to not have any haptic feedback when typing on the digital keyboard in Ubuntu Touch. Is this normal behavior? I haven't felt vibration in the phone at all except at one point the phone got stuck vibrating randomly until I rebooted it.

Is the keyboard supposed to give haptic feedback or is there something wrong with my vibration motor?

I'd like to preorder a Pinebook Pro from the next batch but when I try to add it to my cart it says "You cannot add "14″ PINEBOOK Pro LINUX LAPTOP (ANSI, US Keyboard)" to the cart because the product is out of stock." 

How do I go about getting it ordered?

Thanks!

I seem to not have any haptic feedback when typing on the digital keyboard in Ubuntu Touch. Is this normal behavior? I haven't felt vibration in the phone at all except at one point the phone got stuck vibrating randomly until I rebooted it.

Is the keyboard supposed to give haptic feedback or is there something wrong with my vibration motor?