Hello,
I received my postmarket os today. I went through the installation process. After postmarket os was installed I entered the password, but the os doesn't boot. I see only a flashing cursor. (when the isntallation was finished I entered the encryption password rather than the numerical password. Can this be the problem?)
I hard rebooted the device several times. After reboot the login page comes up. I enter the password, then the massages says, postmarket os is loading then I get the flashing cursor.

I have no idea what to do next.

Any help would be appreciated.

Just unboxed my postmarket phone. Very nice install script. Allowed me to enable ssh immediately. Working through setup was easy. I may begin testing this device against Verizon soon.

I recently purchased a clusterboard and 7 compute modules. One of the 7 never retrieves an IP from my DHCP server.

Here's been my process thus far:

1. Download Arbian 20.08 Buster 5.7.15 (Pine64so version) and unxz the archive.
   
2. Mount the image, use dtc and vim to make the necessary modification to the device tree image for networking to work.
   
3. Copy the image to a microSD card with dd. (All cards are new and tested with f3. Class A1 cards were selected per the documentation.)
   
4. Insert the card in a compute module, insert module into first slot on clusterboard, connect cables.
   
5. Wait for my DHCP server to assign a lease.
   
6. Create a static IP assignment for the MAC address from the DHCP lease.
   
7. SSH to module and complete first login steps (root password, locale, user creation)
   
8. Issue shutdown, power off the board, and remove the module.
   
9. Repeat 3-8 successfully for five of the six other compute modules.
   

• Waiting a very long time (more than 40 minutes; others took less than 5)
  
• Reseating the module
  
• Reseating the microSD card
  
• Re-imaging the microSD card
  
• Using a microSD card verified to be working in one of the other modules
  
• An nmap scan of my local network (which turned up nothing unexpected)
  

• Serial Console debugging. I did not buy one.
  

those of us who previously purchased the PinePhone have been waiting expectantly to be able to purchase the USB-C Dongle that shipped with the latest community edition.

in the latest blog, devs announced yet another community edition, but we are still unable to purchase the USB-C Dongle. as of today there is still no option on the Pine64 store. do we need to purchase an entirely new phone to be able to receive it?

further, a couple months ago we were told we would be able to purchase different branded phone backs. I would love to purchase the Manjaro edition back, as I'm using Manjaro on my Pinephone 24/7, but there's no option to independently purchase them at all.

I don't mind that only a month after receiving my device a twice as good device came out. That device (or what ever revision there is) will likely just be my next purchase in the future when I feel the itch to "upgrade" again. I can still enjoy my current device. what I do mind is that we were promised we wouldn't be forgotten, but it seems as though we are.

Good morning

First of all sorry if this has been answered but all my searches on the forum related to the rock64 or pinebook, found noting for the A64-LTS

Recently i've got a Pine A64-LTS board and tried to perform a standard Debian install following the instructions on the wiki: https://wiki.debian.org/InstallingDebian...64/PINEA64

I've tried now with all the .dtb files for pine devices, sun50i-a64-pine64-lts.dtb, sun50i-a64-sopine-baseboard.dtb ... the board still looks dead, no HDMI output.

Any clue can I be doing wrong?. A64-LTS does work with standard Debian right?

I've succesfully booted the board with armbian, so it isn't dead, but really need to perform a Debian standard install...

Thanks in advance for the answers and sorry for the "engrish"

I have installed Android 9 on my RockPro64 so that we can use it to stream Netflix (since it is Android it allows downloading of content, if I had Linux which I would prefer then we could stream live from a browser but our internet is tooo sloooow to do that!). Everything works except there is significant "artifact / artifacting" in media playback (with Netflix only? Using "NewPipe" for YouTube streaming seems OK).

Is it possible there is some configuration option needed to enable GPU / Hardware Acceleration? I can't seem to find nearly anything on the situation. I will try alternative (older) Netflix versions to see if it helps, but I suspect not....

From what I have read here, I will not hear from anyone until my phone ships.

Will there eventually be somewhere on this website to check the status of an order?

Thanks.

Ive noticed at least when running UB Touch on my pinephone it often, and randomly, starts emitting a very high pitch and annoying sound, probably around 18-22kHz since its barely audible, but loud (high dB) and very irritating nonetheless. Its the same sort of sound you get out of a bad electrolytic capacitor in a RLC circuit when the inductor is off phase or the electrolyte in the capacitor is boiling off.

It kicks in like a laptop fan, so im guessing its the effect of some program/s or subroutines either causing some oscillation in a component or random noise to the speakers or amp gain. Im hoping it is the speakers, so the hardware isnt under stress, but i still hate the sound. 

I know it's been reported by others, i was wondering if we knew the exact source, whether it could be addressed, and also whether it is OS specific.

=============
P.S. i know we're all used to electronic noise, idle speakers, old chargers especially. But for a phone you regularly hold close to your head or other body parts, we really should get it addressed and not just accept it.

Oddly enough, this exact executable file I ran on the PinePhone works just fine on the PineBook Pro and it does not have all these glitches it does the PinePhone. Not sure why these devices aren't displaying it the same? My game is being rendered with OpenGL 1.1 and everything else I've tried reports unsupported GL version (also tried GL 3.3 GL ES 2, GL ES 3.3)

https://www.youtube.com/watch?v=q4ClLbvBJqY

Any ideas why it works perfect on Manjaro ARM for the Pinebook Pro and not the PinePhone running the mobile version of the same OS?

You can download the game here (FOSS):

https://samuel-venable.itch.io/key-to-success

Made with ENIGMA - www.enigma-dev.org

Since there are so many interfaces available for the PinePhone, I'm curious which ones people are using.

-----------

Edit: I think the way that the forum software reports poll percentages is confusing, because it reports as a percentage of total votes, rather than as a percentage of total voters. Here are the poll results as a percentage of total voters:

Which interface(s) do you use on the PinePhone?
● Phosh (postmarketOS, Mobian, Fedora, openSUSE, NixOS, Arch, Manjaro, Gentoo or PureOS): 70%
● Lomiri (Ubuntu Touch or Manjaro): 27%
● Plasma Mobile (postmarketOS, KDE Neon or Manjaro): 16%
● Hildon (Maemo Leste): 3%
● Silica (SailfishOS): 3%
● Glacier (Nemo Mobile): 0%
● Luna Next (LuneOS): 0%
● Mate (postmarketOS or AVMultiPhone): 0%
● Android (GloDroid): 5%
● Other (XFCE, LXDE, JWM, OpenBox, i3wm, Kodi, Sway, Sxmo, command line, etc.): 24%
● Total voters: 37