Hello,

A couple of PineBook Pro owners complained today on the #pinebook IRC channel about their lids no longer being able to close, leaving about a half-inch gap between the lid and the laptop body when the lid is in the closed position.  I already had to open my first-batch ISO PineBook Pro to recover from bricked U-Boot, so I applied some oil to the hinges at the same time, to see what would be the results.

I used sewing machine oil, which is very thin and penetrates very well into the hinges.  After removing the bottom cover of the laptop, I applied two very small droplets of oil to each of the hinges, at the point where the metal shaft gets into the metal hinge body.  I dipped the tip of a small knife into the oil and used it to apply the oil, so I can have better control and end up using as little oil as possible.  You can also use a toothpick to apply the oil, for example.

Not much oil is needed at all; maybe a bit more is needed if the hinges are in really bad condition.  Also, make sure that no oil gets on the display cable that's close to one of the hinges, because the oil woud degrade the insulation/jacket of the display cable over time.

Before applying the oil, the hinges on my PineBook Pro were somewhat stiff, and there was very little to no "snap" action when the lid was closed.  In other words, the hinges weren't bad, but they weren't something to write home about either.  After applying the oil, the hinges became noticeably smoother, and there's a surprisingly strong "snap" when the lid is closed.  The lid definitely "snaps shut" after applying the oil to the hinges.

So, I'd call this a success.

I have Manjaro COmmunity edition I bought a few months ago. Never used. Almost new. Paid $200 + Shipping etc. Make me an offer of $0+ and it's yours. You pay shipping.

PS: I know $1 is also $0+ but I'd appreciate a nicer offer. 

Hello! I have been trying to get signal on my pinephone without using anbox. I am really happy about postmarketos, it is incredibly snappy and the phone functionality works very well.

I have tried to build signal-cli on the pinephone with the latest stable postmarketos 21.06. Glibc is required within the rust modules to build, so I tried to install: sgerrand/alpine-pkg-glibc and changing the target of rust from musl to gnu.
I managed to get the libsignal-client and libzkgroup compiled and I followed the instructions to bundle the .so files back in signal-cli.

Unfortunately when I then tried to run the signal-cli I get:

Missing required native library dependency: libsignal-client.

I had a look through the signal-cli issues and saw that this can happen when compiled with an older version of glibc. Not sure how this happened has the glibc version installed with sgerrand/alpine-pkg-glibc seems recent, but clearly I am missing something here...

I now just tried to do the same build on the pinebook pro with Manjaro. Everything compiled fine, it has and uses glibc rather than musl. I tried the signal-cli and it worked.

I then, maybe ignorantly thought I could copy and paste my build signal-cli from my pinebook pro ( with manjaro ) to my pinephone with postmarketos. They are both aarch64 after all.
I tried to run the signal-cli and again I got: Missing required native library dependency: libsignal-client.

It makes me very sad, in my ignorance I tried what I could but I am a bit lost now.

Is there someone that could help me understand what I am doing wrong and help me?

Thanks in advance

Does anyone else have a jumper wire on the first slot?

I have a red wire that is connected to one of the pins on the socket and connected to another component on the top. 

I also have a problem where the first slot is not working, I have 7 slots and only 6 are working 1 being intermittent on the nic.

Some time ago, I set up an NVMe into my Pinebook Pro and installed Debian there.  Later, a couple months ago, I kept finding that my battery would stop getting charged at random times and the power LED would start blinking.  Sometimes this was temporary and the battery would start charging again after some time, but other times it reached 0%.

When the CPU load is high (say, compiling something non-trivial or playing a video, on disk or streamed), sometimes the part of the computer chassis next to the motherboard gets really hot, the battery stops charging for a longer time and this is usually followed by I/O errors trying to access the NVMe.  When booting from MicroSD, these errors happen trying to access the MicroSD instead.  For reference, cooling the computer by applying an ice bag to the bottom cover didn't help, even though both the bottom cover and the keyboard were cold, and changing the DTB so that it used NVMe at Gen1 speeds, as suggested in other threads, didn't help either.

When I reboot after an I/O failure, the computer succeds at booting from the same media but gets I/O errors soon afterwards, so I have to wait until it gets cold again (or as cold as it can get in this part of the world in summer).  When I disconnect the battery and connect the short-circuit cables (the ones used to power the computer directly from the plug), all of these problems disappear, but I want my laptop to be a laptop.

I honestly can't figure out where these errors come from or how to fix them, so any kind of help will be greatly appreciated.

How to disable Bluetooth either from the watch or entirely? from which OS?  Thanks!

Can someone help clear up my understanding of bluetooth services and attributes on Infinitime? I figured out how to set date and time using gatttool, but am confused as to why there are three different characteristics associated with the CurrentTime service, and how I could have found that out from the source code instead of trial and error with gatttool until I found something that looked like a time and date code.

In Infinitime/src/components/ble/CurrentTimeService.h, I can see that ctsId sets the UUID of the CurrentTime service to 0x1805. gatttool tells me this has three characteristics with handles 17, 18, and 19. Handle 19 has the date and time, and gatttool can set time on the watch with char-write-cmd. But what are handles 17 and 18 doing? And where in the source code are these characteristics defined?

Thanks,

What really bugs me a lot is the wake on touch feature on every device it comes with, 99% of the time it wakes on touch by accident, leaving the screen on while sucking the battery dry like a vampire.
So is there a way to turn that off for Plamo?

Hello,

I have recently changed the motherboard of my Pinephone Braveheart to switch to the 3GB version.
Since the change I have a problem: the phone crashes (instantly goes from running to powered-off) after a few minutes (between 10s. & 10 min).
If I leave the phone plugged to power (for example to a USB battery) it will not crash (not even if I use it to browse the web for 1 hour, or if I let it run idling during the night).

All other functions work fine.
The phone runs hot, but that was already the case with the original motherboard.
I am running up-to-date Mobian.
I am running from SD card, I will flash to the eMMC asap to see if it helps.
I had not this problem before changing the motherboard (crashes were rare, maybe once a month), but I was running from eMMC.

I tried logging dmesg -w to a file but this does not show anything conclusive.

Any idea for how to debug this ?
Should I try other distros ? How likely is it to be due to running from SD card ?

Thanks in advance

Hello everybody .
I was wondering if someone know or if it is some kind of wipe/delete function in Mobian,
Maybe if I enter the wrong password to many times then the phone automatically erase and shredd everything on it or Delete the encryption key,is this some function that I can get on my pine phone?
And if there is any program that clear all logs and stuff every time you reboot or turn of the phone?
I hope u guy’s understand what I mean and thank you so much for this forum it’s great 
Have a nice day!