I recently ordered pinetime with pinebook screw, and i see alert status on 17track now.

What happened? What should i do?

image - https://ibb.co/5Lr4Kh1

If there's ever a major revision to the PBP's design, it might be nice to have a "disk" (really bus) activity light. That would make it easier to detect problems prior to the OS loading, (Might cost too much to revise the case and board.)

The other suggestion would probably be easier to implement; put the socket (USB, audio, &c) silkscreen labels on the keyboard top rather than the sides, (obviously, pointing to the locations). The text could be a little larger (hence more legible). Generally, one inserts cables and jacks while above the keyboard, rather than peering at the side.

I've had the PBPro for some months, and am generally pleased with it. The quality of the audio was unexpected, and it's now become my domestic audio streaming device.
However, when restarting, e.g. following an OS update, it frequently hangs, very early in the reloading process. (Blank screen, not even the circling indicator.) It seems to require one or more physical off/on cycles with the power switch before it will start to load the OS.
It would be easier to see what's going on with a "disk" (really bus) activity light, but that might be too expensive to implement.
Is this a known problem? Is there a fix?

Everything is working accept modem. all connections seem fine. The modem gets warm so I'm assuming its getting power. What am I missing?

I want to test an NVMe SSD drive in the Pinebook Pro that isn't yet in the wiki Hardware Accessory Compatibility list. can someone please write a noob-friendly guide on how to do it? I want to find out the following:

• whether the system can remain stable while the drive is in sustained heavy use
  
• APST default setting
  
• whether the power settings are saved across reboots, and if not, is there a workaround
  

Linssid would be a useful tool for wireless network survey (at least 2.4 GHz) but although it installs it aborts on an error when run, apparently a problem with connecting to the display. This then precipitates additional errors, however the inability to connect to the display seems to be the actual issue. (Linssid uses pkexec to run with root privileges.) This appears to be a generic problem running any program as root via pkexec or sudo , for example a similar error occurs running "pkexec nemo" or "sudo nemo". I'm really not very familiar with Wayland, is there a way around this?

Two manuals

1) T-mobile certification

2) MMS configuration

Attached Files

  EG25-T-mobile-certification.pdf (Size: 102.07 KB / Downloads: 1839)
  EG25-MMS.pdf (Size: 185.91 KB / Downloads: 947)

Hi!

I just received my delivery with two Pinetimes. One of them is acting up. When I first started it up it got stuck in a bootloop with white/green pinecone logo. I noticed that if I held down the button it would start with green, go to blue pinecone and finally red. I was not able to turn it off.

I let it sit for a few hours until the battery went dead and when I started it up it goes to a splash screen saying infinity time and then freezes. It is possible to hold the button to restart it, but it again hangs on the splash screen...

Suggestions? The other unit seems to be working fine...

Hi, love my pbp, Manjaro KDE plasma (last month download) on emmi. Cannot get it to boot from sd. I took off the back cover, switched the emmi off, and was able to boot an sd with Armbian Debian xfce 5. When I replaced cover and rebooted with the emmi switched back on, the sd was ignored again. So, the boot order does not begin with the spi, and then the sd, as stated in the documentation. I suppose that if the spi is blank, the system tries first the emmi and then the sd.
How do I get the sd first order? Isn't that how it is supposed to work? Install what you want on the fast memory and then try out different os's with the sd card, always able to revert to the emmi when the sd card is removed?
This should have an easy fix, but it seems to be a source of confusion to noobies (that's me). Thanks for advice.

I had a RockPro64 running on microSD just fine and forgot it was still turned on and tried to connect the eMMC to it. After popping out the microSD I noticed it wasn't booting on eMMC so plugged back in the microSD, however it no longer seems to boot fully on microSD anymore as well (e.g. my keyboard LEDs don't flash, no video output detected to TV).

Is it possible to brick the RockPro64 somehow by connecting a flashed eMMC while actively running off of microSD?