Does anybody know what is causing this? It happened today after booting back to eMMC from SD. Both have the same system image flashed: Manjaro Plasma 22.08 generic

https://imgur.com/a/5Ts2UWc

Hello,

I have issue to boot postmarketOS on pinetab.

I flashed postmarketos on eMMC and µSD card but the pinetab cannot  boot the os (the camera make "clic" noise).

I think that is linked to the use of tow-boot bootloader by postmarketos & mobian (tow-boot github issue)

I successufully install old postmarketos version (before tow-boot) on the pinetab.

I am wondering if some try to mixe new postmarketos image with old bootloder?

Thanks


Ivaylo

See our PinephoneEs(no oficial). Telegram
And download our program noblank.sh and tell us if you like it
Yo need to install yad
But I am preparing a new one with notify-send. So, we Will have two flav
ors. It is already,19th September, on PinephoneES(No oficial). H
ope you, the mobians, like it
It is already on MiPinePhonePro and PinephoneES(n oficial)

https://meetfranz.com/

the only issue....they provide only amd64 architecture .deb file and we need arm....
they also provide appimage, I assume amd64bit as well

Hello Pine64 Fans: Coming up next weekend is the Apache NuttX RTOS Online Workshop, I shall talk about my projects on NuttX RTOS (Real-Time OS) on PineDio Stack BL604 and PineCone BL602 (plus a little PinePhone)...

1. “Visual Programming with Zig and NuttX Sensors”

2. “NuttX on a RISC-V IoT Gadget: PineDio Stack BL604”

3. “Simpler, safer LVGL Touchscreen Apps with Zig and NuttX”

I hope you'll join me next weekend, 24-25 Sep! Registration is free...

https://nuttx.events/

Thanks and see you next weekend! :-)

Lup

Hey all. I'm not sure if this is an issue with Verizon being asses, Verizon's coverage in my area, or the Phone itself. I have a PinePhone Beta running Postmarket. Aside from this, I maintain an Android phone for those family members that refused to leave Facebook Messenger (baby ducks are more stubborn than mules). I tether this Android phone off of the PinePhone most of the time, at least until I get to some other WiFi. Now, the coverage in my area is spotty, with all major carriers having miles of dead spots with tiny slivers of coverage between them and I have always attributed this to poor connection on my Android phone while tethering, but I've noticed that I can get perfect performance on the PinePhone, even when the Android phone is saying that I can't get a connection. I've confirmed that this isn't my VPN, as the issues are there whether or not it's turned on.


There are three possibilities that I can think of. One, Verizon is throttling tethering on my "unsupported" device. I doubt this. It hasn't always been that way and I don't know why they'd just throttle tethering without throttling the phone itself. Two, there may be an issue with either something in software or hardware on the PinePhone bottlenecking the connection. The issue is intermittent, so I don't know about that one. I'd expect to have the issue either all the time or never if it were an issue with the PinePhone bottlenecking it. Three, I may have been in a poor coverage area while using the Android device, but when I switched to the PinePhone, I had just so happened to have moved into an area with coverage...every time that I had this issue. This seems really unlikely because I don't walk that fast and it's not the same place every time.

I'm really kind of stumped on this one. Please let me know if anyone has any suggestions as to what this might be.

I have downloaded the TwisterOS image located here: Pinebook Pro Software Release - PINE64 and flashed it to a microSD on using DD under the included Manjaro Plasma installation. I followed the instructions and changed the armbianEnv.txt file to point at the rk3399-pinebook-pro.dtb file. I shutdown the computer and restarted with the card inserted (in the external microSD slot) and the machine will not post. The green power indicator slowly turns off and on in a continuous loop suggesting the machine is restarting after failing to boot.

Is this image not compatible with the latest release of the pinebook pro? Is there another version of the image I can/should use in its place? If this is all a moot point is there a similar flavor of linux to TwisterOS which includes wine and other arm specific versions of x86 emulation software?

Hello,

maybe it is time to create a forum section for the new rk3588 board, or do we share the quartz64 space ?

Hi,

I have a recent Pinebook Pro from September 2022 (motherboard bears a 2022/07 QC sticker)

It has an NVME (low power WD) SSD for /home and data only, and Manjaro Linux KDE runs from the eMMC, with latest updates applied.

When running from mains power, the system is perfectly stable. But the power cable is so short !

OTOH when running on battery, even fully charged, it happens very often (twice attempting to write this post) that the system completely freezes with the power LED blinking red/green.

At this point I can only perform a hardware poweroff.

Any clue ?

Kind regards.

In the last two weeks, since I played with Mobian for a while and a few others and eventually settled on Manjaro Phosh, things began working more or less fine, except two weird things (and more came as I was writing).
- if I don't close all apps, the phone may need to be rebooted. Doesn't happen every time, but does often.
- when I boot it, it sometimes takes two or three reboots until it shows the desktop
- today when I tried to call someone, it reported that she was calling me (three tries, did so each time); worked around it by sending a SMS and then she called me, which went fine. On next boot, called someone else, that went fine
- just now someone called me, and during the call the screen went black (as I assume should be normal), but then when I turned it on and tried to enter the passcode, after three digits the digit buttons just flowed away to the right, as did the indicators on top, leaving me with just the background picture with nothing on it. On next suspend/resume it shows the top row controls, and they work, but the passcode digits and the bottom arrow to show them didn't appear.
- one reboot later it's back to normal.