On page 11, grid ref 3A, PD18-LED-R signal is shown connecting to the blue part of the LED, PD19-LED-G connects to the red part, and PD20-LED-B connects to the green part.
However, I also tried controlling the LED on my actual hardware (Beta Edition) and found that in reality, PD18 is green, PD19 is red, and PD20 is blue.
---
Attached is a small test program you can upload and run over FEL to try this on your hardware. The program will light up the LED colour connected to PD18, then PD19, then PD20, then return back to FEL mode. On my phone I see green, red, blue.
I wanted to report this documentation bug but couldn't find anywhere to contact the Pine64 team except for sales, so I'm posting this on the forum instead. Hopefully someone reads this and fixes the schematic.
Posted by: daubsi - 07-10-2021, 05:16 AM - Forum: General
- No Replies
Dear forum,
I recently stumbled over the PineCone/Nutcracker challenge when I was trying to flash a custom firmware on my "Magic Home" Wifi LED controller. Those controllers had an ESP based chip in the past but recently switched to BL602. Curious I read about recent developments and decided to play around with the chip as well. I used blflash to dump the existing firmware but apparently I did not recognize that by default blflash only dumps 1 MB, whereas that particular controller seemed to have 2 MB.
Does anyone here have such a Magic Home controller and is able to provide me a dump of the original firmware please? Thank you in advance
thank you for your interests. Advertised laptop was sold today.
With kind regards,
P.
#######################################
Hi,
I am planning to sell my Pinebook Pro ANSI. It was purchased on May 2nd this year. As addition I add M.2/NGFF NVMe SSD adapter (it's already installed).
It has no signs of usage, I opened it only to install SSD adapter. I will flash clean Manjaro distribution (please let me know if you want any special version like KDE or Gnome). If you choose I can try NetBSD or OpenBSD.
I live in Netherlands but I can ship it anywhere in EU.
Let me know if you are interested, I will send photos on request or later in this post.
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.
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:
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?
so I applied some oil to the hinges at the same time, to see what would be the results.
