I thought I followed the instructions correctly and attempted to flash the emmc with an image and after I thought it was finished and I tried to start the phone it fails to start. I don't get a green light or anything.
What can I do?

Hi

ive read other posts and im trying to establish if my board has a HW issue.
ive flashed some raspberry pi (32 bit) previously so i believe im flashing my sd card ok.
i gave a green led on longside the power connector
i have a solid red and a while led on by the gpio pins.
the activity led on the nic port (on the usb side of the port) is solid amber regardless of cable in or out
the other nic led is always off.
the power button longside the white led turns all but the green led off.
there is no hdmi output .


what do i do next to determine if its a brick or not

Or was certification of the 1.2 boards "good enough"?

My package was (supposedly) sent on the 28th of February. I knew there could be delays because of COVID. But 3 months passed (June) and the tracking status still showed as "Departed", so I started to get worried.

I contacted support to get a status update on the package. They said they would check and get back to me, but they never did. So I contacted them again twice, both times they replied they were waiting for feedback from the post company (Asendia) and they would get back to me, but they never did.

I contacted them a fourth time 3 weeks ago demanding some sort of response. It's unacceptable that a post company takes more than 3 months to report the status of a package. I got no reply. I wrote again 1 week ago. Still got no reply.

I've been waiting 7 months for this package... What's going on? Are they ghosting me? Did somebody lose my package and no one wants to take responsibility?

In case it helps, the ticket number is #4476

What OS do you use as a daily driver and what apps do you have that make it a daily driver.

THanks

Would PINE64 consider choosing a free software licence (such as the GNU Affero General Public License) for scripts employed on their website?

• https://www.fsf.org/licensing
  
• https://choosealicense.com/licenses/
  

Somewhere, maybe it was a DOS TSR, I've seen little utility programs that would do things like beep on every keypress while the caps lock key was active.  Or deactivate it after a certain time or number of keypresses.  Not sure how to do that in Linux.

I don't use it often intentionally but it's a lazy way to type macros.  Mostly it's on when I don't want it.

Using my PBP more these days, doing audio recordings with it.  And I just went through a 2 day power outage and the PBP was the only thing that still had a couple hours of battery left.  As winter sets in I'll spend more time with it in my recliner.

-----------

I suppose the Linux equivalent of a TSR would be a kernel module.
https://duckduckgo.com/?q=linux+%22kerne...cal&ia=web

I'd like to redefine the power switch so it brings up a whiptail confirmation dialog or something like that before it actually shuts off.  Suspend could easily be added to that as another choice.

Is that possible?  I keep hitting it by accident.  I'm using the original Debian Stretch still.  Something like:

Hello everyone,

We’ll soon be starting work on the PineCom - a privacy-oriented handheld communicator that shares the PinePhone’s pedigree but offers a distinct and different feature set. We hope to achieve a high degree of software compatibility between the two devices - indeed, we expect the PineCom to run all existing PinePhone OS images out-of-the-box. Unlike the PinePhone however, the PineCom will not feature a modem but rather rely on WiFi, IoT LoRa and LoRaWan for communications. The device will also be smaller at (5” LCD panel or less), and will not feature a USB-C alt mode for video output. 

Everything else is still up in the air at this point, and we therefore invite you to brainstorm ideas with us regarding the remaining design features of the PineCom. More specifically, we’d like to know your opinion on the following:

1. Do we need both a front and back camera on the PineCom? In fact, do we need any cameras at all? 
   
2. Should we bring over all sensors present on the PinePhone? If so, which do you think we can do without?
   
3. Should we use the same single band/11n/BT4 WiFi module in the PinePhone (for compatibility sake) or change it out for a dual band/11ac/BT5?
   
4. Should the device feature a GPS (and compass) or are those features redundant in this type of device? 
   
5. Should we include SPI flash?
   
6. We are currently considering following the PinePhone’s general design and aesthetic for the PineCom, but if there is some sort of physical (within reason - also financially) that you think would fit this type of device well then make sure to let us know.  
   
7. We’re currently thinking of using a 5” LCD panel for the PineCom; what do you think about this - is there a reason to go bigger or smaller? 
   

Hello,

I set up minicom and the serial cable and watched the whole thing boot.

Everything looks fine otherwise, text input works as expected EXCEPT the enter key.
Pressing enter will echo back 'OM'

How? Why?

Ctrl+m works as a workaround.

Thanks.