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.

I'm running Mobian on my Pinephone CE and every so often a notification will pop up for "phone shell" and there is no option to dismiss it, just to open it. When I tap open it opens the file manager. Is there a way to disable this or to dismiss ntoifications without opening them ?

Has anybody tired Heart Rate OS on Wasp-os using PineTime or InfiniteTime I run into problem here is a screen shot Either way the Heart Rate does not show
Youtube video  So when the new 1.0 Infinite Time came out on April 23 I tried that but Still NO Heart Rate How do I make sure there is no Hardware issue https://pasteboard.co/JZPaRSh.png

Hello everyone;

I finally managed to get my hands on a KDE plasma pinephone, I switched it on for first time three days ago, I updated it and everything was going well. Then yesterday I tried to use the docking bar for first time and the phone crashed, now when I start the phone it will stay on the logging command page and the only error I can see is this one:

at command 'at+QCFG="fast/poweroff"' returned error

The phone won't let me do anything at that point. Anyone has got any suggestions as to what I can do now? Do I need to install a new image?

Thank you for your help!

I can open Gimp, but as soon as I open any image in it, KDE or X11 (don't know) starts blacking out, screen goes black, parts of screen go black, cursor does whatever it wants... Basically have to hard restart.

Is there a package missing or something? Thanks!!