I have installed both HPLIP and cups. Pinebook pro is able to the see the printer both usb and wireless network goes through the motions but then restarts I do not what I am doing wrong if anything anyone else  experience this.

Hello,

Something strange is going on with this forum...  I've never had any issues with the forum alerts for the replies to my subscribed threads, but today two of those alerts simply disappeared from the list of alerts.  I didn't delete them, but they simply disappeared, while the associated replies still exist.

What's going on?  Needless to say, this is really concerning.

Until recently, my PBP was working absolutely fine. However when I turned it on the day, after some confusion I realized that some of the keys simply don't work. Quite a lot in fact. I'm using an external USB keyboard at the moment which does work. So far I've has no luck in diagnosing the problem or whether it's simply a hardware failure. The last thing I did before powering off was to do a full update on Manjaro but I find that hard to believe that would cause this, who knows.

Couple of points

1. I have the ANSI keyboard
2. I've tried booting archlinux from an SD card to check that it wasn't something in Manjaro. It exhibits the same behaviour
3. Tried re-flashing the keyboard firmware (only once) to see if something had gone awry there. No change
4. Popped the bottom of visually inspect the cables. As far as I can tell, everything looks connected properly

Is there anything I can do to confirm if it's a hardware, firmware or software issue? I'm I out of luck and the keyboard is toast?

Thanls.

General

[11 April 2021] This is the PinePhone BETA Edition and Pinebook Pro shipping thread. It will be updated with details once shipping begins. Any delays, if they happen, will also be reported in this thread.

Please refrain from emailing info and/or support for shipping details, as they don't have additional information to what is relayed in this thread - it just adds to their workload.

To be notified of new posts in this thread by click "Subscribe to this thread" at the bottom of the page.

Shipping update edits and entries will also be Tweeted, Tooted, posted in the announcements channel on Discord and in the dedicated News Channel on Telegram.

[19 April 2021] General notice: both PinePhone BE and Pinebook Pro have been split into two (or potentially more) shipping sub-batches. What this means, in practice, is that if you ordered a PinePhone BE or Pinebook Pro prior to April , then your order will dispatch at end of this month. If you ordered after the 12th, however, then your order will ship 2-3 weeks later, once shipping of the first sub-batch is completed.

Stay tuned for updates when shipping begins.

[30 April] China will be celebrating Labour Day May 1st. next week, and as a result of this no shipping will be taking place between May 1-9.

[5 May 2021] Orders placed after April 18th will ship out mid-May.

[May 21] All remaining Pinebook Pro and PinePhone orders will ship next week. See individual device-sections below for details.

PinePhone

[20 April 2021] Shipping of the first portion of BE PinePhone's has now started. Those of you who pre-ordered prior to April 12 will receive their shipping information from DHL within the next 4 days.

As a side-note, we are looking to have one more batch ship out prior to May 1st, for people who pre-ordered April 12-18.

[25 April 2021] There are delays at the Hong Kong airport caused by a pallet of Vivo phones catching fire just over a week ago. Shipments are going out albeit at a slower rate than usual due to additional safety procedures for battery operated devices at Hong Kong airport.

EU specific: good news, PinePhones destined for EU countries should be received on April 30th / May 1st at the EU warehouse, and dispatch to customers should start on May 3rd. So, many in the EU will receive their PinePhone BE between May 4-9th. I'll let you know if anything changes

[30 April 2021] The shipping progress is ongoing. We are aware that the shipping pace is slower than usual - this is due to DHL's Hong Kong shipping circumstances (see previous update entry). 
PinePhones destined for the EU should start arriving in end-users hands next week, but in some cases may first arrive the following week, 10-16th May.

[6 May 2021] There is a few days delay, but PinePhone shipments for EU countries will begin this week. Apologies for the delay - its related to DHL's issues.

[10 May 2021] PinePhones for destined for EU countries have started shipping. The delay in shipment was caused by paperwork shenanigans we sadly had no control over. Regardless, we apologies for the delayed dispatch. The vast majority of you awaiting your phone in the EU (and ordered prior to April 15th) will receive your unit by end of this week.

[21 May 2021] PinePhones ordered after Arpil 18th will start shipping Monday, may 24th. Shipment is scheduled for two dispatch days - the 24th and 27th.
Following the 27th, all remaining PinePhone would have shipped out. We know that we're some week or so behind schedule, apologies for the delay.

Pinebook Pro

[20 April 2021] I have gotten word that the PBP production is proceeding well, without any hiccups. We currently scheduled to start shipping on April 29th.

[30 April 2021] Pinebook Pros have started shipping today. The laptops were delivered late from the factory, which usually wouldn't be a huge issue, but unfortunately (at least from a shipping standpoint) China will be celebrating a May 1st holiday next week. Pinebook Pros that do not get processed until the end of the day today will first ship out on Monday May 10th, or soon thereafter. Apologies if any of you are forced to wait a little longer.

[21 May 2021] All remaining Pinebook Pros will ship by Thursday next week, May 27th. We know that some of you had to wait an extended period of time for this shipment - our apologies.

Is there any way to set battery charge threshold to something like 80% or so?

For example, ThinkPads have such option to set battery charge threshold:

Just got my new sealed watches.  Not going to program on them so going to try to do good testing.

Minor issues I found with the directions. 

The easy to find firmware update directions all seemed to be for amazingfish.  Under android Nrf Connect was slick and easy (did take six tries).
Good directions I somehow had trouble finding:
https://github.com/JF002/InfiniTime/blob...Started.md

Every version of the companion app directions I found says:
"You can download gadgetbridge from fdroid."

That's misleading.

You MUST download gadgetbridge from fdroid to get a new enough version to pair with pinetime/infinitime.

Hello all together,

Since I have not been using my Pinebook Pro as much as I expected, I have decided to sell it to someone who will have more fun with it than I have at the moment.
The Pinebook is from the first batch and therefore has the 128Gb eMMC. The laptop is in good shape (images attached) but on the screen edges the plastic has broken. However, this does not impair using the device. 
I am selling the laptop for €200 plus DHL shipping. I live in Germany, so obviously for German people it will be cheaper to get it. 

Photos: https://photos.app.goo.gl/DkTMZ9N9nw1jzy516

Hello, I have a problem unlocking the cycle counter register on Pinebook Pro (or, even, rk3399 in general, from what I've gathered).

A common way to unlock it is to load a kernel module that executes an unlock command from the inside, however, the modules that I tried do not work (for example this one https://code.videolan.org/janne/arm64-cycle-cnt, which works on Raspberry Pi 4). I can only access the register inside the module that unlocked it, printing the value to dmesg for example.

One way of unlocking it is building a custom kernel that enables the register on startup, however, this is less than ideal for me, so I was wondering if anybody else encountered this issue.

I am new to Linux and computers in general. I have a Pinebook Pro ARM Manjaro with a plasma system j believe but I can't connect to the wifi. My killswitch Is good and I can see my wifi I can connect to it I type in password but then it tells me it's deactivated and can't find the device. I've asked Reddit and other places but there's nothing. Also it says waln0 no secrets were provided. Sorry if I don't know much I was handed this computer down and need it for courses.

Do not clutter this thread with criticisms of Signal. Take that discussion elsewhere please.

Hi,
I've been following the issue of getting Signal working on Linux smartphones for a while and I've come to the conclusion that it is probably best if we start a new client application. The Signal developers are uninterested in making their clients work for our use case. The Signal "Desktop" (Electron) client does not and will not support registering an account, is not designed for small screens, and does not build on ARM. The latter two issues may be fixed upstream (eventually), but they've specifically said they do not want to make the Electron client have feature parity with the Android and iOS clients. I doubt using the Android client in Anbox would be a good long term solution for battery or RAM usage.

So I think we need a native Linux client. I do not think Axolotl is a viable long term solution because it uses its own implementation of the Signal network protocol (written in Go). Reimplementing the cryptography and network protocol is a ton of work and will continue to be a ton of work as upstream adds more features. Axolotl has only just started reimplementing the new Signal groups protocol which was introduced Also, the security of a reimplementation is dubious.

Fortunately, the Signal developers are now using a new Rust library with bindings to C, Java, Swift, and TypeScript for their own clients. Currently this is undocumented and does not yet implement all the logic necessary to write a complete client. However, upstream has advised that using this new library would be the best option for starting a new client. Considering there is a C FFI (which I presume they implemented to implement the S, it may be possible to add Signal support to libpurple which is used by Chatty. However, I am doubtful that would work out well. libpurple was made in a different era when messaging didn't include audio and video calls, emoji reactions, or disappearing messages. Trying to cram those into the libpurple API may be more trouble than it is worth. I would also be concerned about starting a new project using such an old code base which I am guessing has quite a bit of legacy cruft.

So, I think the best way forward would be a new client using the Rust bindings for GTK so the upstream libsignal-client, zkgroup, and ringrtc Rust libraries can be used directly. I don't have much experience developing with Rust or GTK and I barely know anything about cryptography, plus I already maintain another very complex application, so I couldn't lead development of this but I'd be happy to test and contribute code where I can. I am starting this thread to try to organize people who are interested in working on this.

I propose this roadmap for implementing features:

1. Device registration
2. Sending and receiving text messages
3. Import contacts
4. Use the WebSocket API for notifications like the Android client does on Android with neither Google Play nor microG
5. File attachments
6. Voice calls
7. Video calls
8. Device linking. If we could get this application to link to itself, that could be an awesome way to have the primary installation on a PinePhone and use the same application on a Linux laptop.
9. Figure out a way to do notifications in a more battery friendly way. This will require cooperation with the Signal Foundation and we may need to write the changes for the server software ourselves. Maybe OpenPush? Or perhaps get Firebase push notifications working on Linux without Android?
10. SMS support
11. MMS support

I think the GUI design could largely copy the Android client.