I have started the process of getting OpenWRT working on the Rock64.

I have a working image alongside a custom repo for packages which can be found here, download links for the SD Card images are front and centre: https://openwrt.cdnbcn.net/

When installing the SD Card image, you will have to manually configure /etc/opkg/distfeeds.conf with my custom repo, however I'll fix this in a later build.

The main issues currently are as follows:
    - USB3 port isn't working
    - Onboard Ethernet doesn't reset correctly 100% of the time

The source code can be found at https://github.com/CanadianBaconBoi/openwrt/tree/rock64.
It is based on the work of lucize however it has been updated for a modern version of OpenWRT.

There is a thread with some fixes for the aforementioned issues below, however I have been short on time recently and haven't been able to get around to implementing them yet.
https://forum.pine64.org/showthread.php?tid=11012

Any help would be greatly appreciated in pulling these in, I'll continue to host the package repo for free until this is pulled into upstream.

Hello all.

As of about two weeks ago, my SMS messages have stopped coming in on my PPP. MMS messages, including multimedia and plaintext multiperson messages work fine, as do outgoing SMS messages, but incoming messages seem to go into a void. mmcli shows no pending messages, so it is not just the front end GUI application. Has anyone else seen this?

For the record, I am using a PPP loaded with the latest Danctnix/Arch, running Phosh, and am on a Verizon contract.

Thanks for any ideas or insight

-tch

My phone will just go dead for days at a time, and it will not update. I think that my software is corrupted. How can I safely reflash the emmc?

Order a pine phone pro Feb 9th.
It shipped quickly, but got stuck in Los Angeles.

From DHL:
Shipment is on hold
February, 26 2022 10:07 Local time | LOS ANGELES GATEWAY, CA - USA

I've emailed sales. No response.


I submitted at ticket at:
https://desk.zoho.com/portal/pine64/en/home


I've contacted DHL. They initiated an investigation. Their finding is that the shipment has been lost.
I will try to file a claim.

Has anyone gotten DHL to pay a claim on a pine64 shipment?

Attached Files

Thumbnail(s)
   

Hi all!

I've recieved a new Pinephone Pro explorer edition and am about to fire it up. I've been following pinephone development closely over the past couple of years and excited to try it out.

I have a fair amount of linux experience with multiple different distros over the years. That being said, I'm not a hard core programmer but more of a tinkerer.

I had two main questions before getting started.

#1
Tow-boot vs u-boot?

Seems like the big show-stopper bug for now with the PPP is power managment. It seems like many people have installed Tow-boot to help deal with this, but there are others that seem to be making progress using the u-boot that came by default. Should I just switch over to Tow Boot right off the bat? Are there disadvantages to doing this?

#2 
Best distro to get started with at the moment

I know that people are asking this all the time, but this seems pretty fluid and changes frequently. I know that any of them will have problems and need work in development. I just was trying to get started on a reasonably good footing.

I have read that Manjaro Plasma unstable branch has made some real progress with power managment. However, it seems like people have had some significant trouble trying to update the pre-installed image of manjaro plasma on the explorer edition. Should I just flash a new image to an SD and try out that? Or has anybody sucessfully updated from the Manjaro Plasma using the unstable branch from the preflashed image.

Thanks so much for the help! Looking forward to trying this out and contributing back what I can.

Welp; I might've bricked things. I'd followed instruction at https://wiki.pine64.org/index.php/PinePh...microSD_OS, thinking it was talking about the PinePhone Pro (maybe I got to it from a thread regarding the PPP; I don't remember, at this point), and missed the message in red at https://wiki.pine64.org/wiki/PinePhone_P...o_the_eMMC.

Now, it won't boot at all (as far as I can tell) with a full battery or plugged into a PC. I thought I was following instructions to the letter but this one's clearly my fault. Hoping I didn't just brick my just-bought phone but thought I'd, at least, ask if there was any kind of hope for recovery, at this point.

I'm unsure if this is only affecting the PPP but I'm unable to do anything but connect to the network. Searching for anything just crashes the tab.

I know there are a few threads about carriers already, but I thought I'd open one up specifically for the UK:

I have two SIM cards, both use the EE network, but only one of them works on Ubuntu Touch:

- The PAYG card from 1p mobile works as expected.

- An old pay monthly SIM from T-Mobile, later taken over by EE, causes problems: bad voice reception and no mobile data - a shame, because this SIM has unlimited data. It is also my main number that I had for over 20 years.

This is the only reason I have not ditched my old Android phone altogether!

Hey all,

I tried both the Arch Phosh and Plasma and one item that got me stumped is what is the sudo password on a stock version? I tried 123456 and root but nothing.

TIA!

(03-11-2022, 05:58 PM)LPIZ Wrote: Hey all,

I tried both the Arch Phosh and Plasma and one item that got me stumped is what is the sudo password on a stock version? I tried 123456 and root but nothing.

TIA!

Hello

I can set recipient and subject, but it's not possible to write any text (it's not possible to bring the focus/corsor to the mail body).
If I click cancel, click the "undo" button, then I'm able to write the mail as expected.
If I click cancel, click the "undo" button, click in the recipient of subject field, then I'm not able to jump to the text field.

This issue happens with and without a signature. This issue happens with "plain text" and "rich text".

Version: 40.0-2mobian1
The only log entry I can find is: "org.gnome.Geary[...]: *[wrn] ... Gdk:Event with type 4 not holding a GdkSeat. It is most likely synthesized outside Gdk/GTK+"