While using my pbp, it displayed vertical wide grey and white bars covering the screen for a few seconds, display went black and it shut down. It had been pretty stable for quite a while.
Now when i power it on, green light on the keyboard comes on for maybe 10 seconds then goes out, the screen remains black. Anyone dealt with this? I hate to take it apart to blindly start seating cables or whatever since i understand this thing is easy to break and i am somewhat of a klutz. But i would like to get it working again, any suggestion is appreciated.

Hello everone!
I bought a pinecil v2 a few months ago, but I have only needed to use it once since I own it.
Yesterday I wanted to use it again, but I had to found out it don’t power on.
I tried with both barrel jack, and USB-C via 5-12-20V, also from two different cables.
While I hoped its firmware can be updated at least, from my PC, it doesn’t even recognised my device.
When I opened it up, everything looked normal, the joints were fine, nothing blown up.
Personally I’m a plain user not an engineer, though my assumption is that it is completely dead.

I would like to ask, what can I do in this case? Is there anything my attention passed on?
If it’s dead, I have any chance to repair?

Hello everyone,

first I want to phrase the question:
Is it possible to somehow reset the userpassword via setting a boot parameter in uboot to drop into a root shell (without disk encryption this should (?!) be possible in linux via the init=/bin/sh "trick"). I connected via UART and to my pinenote and tried some combinations, setting the bootcmd and others (see https://isc.sans.edu/forums/diary/Resett...ers/28564/).

now the why:

What was bugging me, since I have the pinenote for 2-3 weeks now, is that it crash-reboots at least once in a using session (no heavy actions done (?!): a bit browsing and configuring koreader, xournaling some pdfs, and stuff). I thought, this is because the system is not meant to be stable by now (as far as I understood what I read)  and wasn't yet able to investigate further

Now 2 days ago I apt-upgraded via terminal and the update seemed relatively big (but it was NOT my first time running the os update). The screen froze at 55% - no reaction. I was already fearful because it happened after the downloading/unpacking part and still I powercycled it after 1-2 hours. It didn't boot anymore (it showed a dark version of the image with the squares and it said "booting ...").

I connected UART (thanks so much for delivering the dongle with it!!) and was presented a login.
Ok, what was my root password again? I've set it up a week ago and used it some times. But although I'm 98% sure that I got it right, I was not able to log in.
Ok, I created another user with sudo permissions and because of the many reboots of the pinenote I had to put it in very frequently, so I'm 99,999% sure that I have it right (still there was a slight uncertainty, because the password is somehow bound to the layout of the on-screen-keyboard) - NO, not able to login.
Ok, what was the password of ther originals "user" ... yeah, I'm able to log in ... BUT ... as I created another user I removed sudo group from "user" -.-
Now I'm confused even more - I can see that the user I created really exists in /etc/passwd ... so once again my reality is questioned - why wasn't I able to login?
Did I tried to much and some new PAM restriction is active by default in Trixie? Seems not so. But I remembered the workaround of dropping to a root shell in grub, maybe/hopefully this also works here? But I'm not very proficient with uboot and UART yet.
Alternatively: can I copy the bootmenu file from the pine, change it and put it back?
Maybe there is an even easier option I didn't think of yet, before I have to flash it(?!)

I was looking at the chip in the Ox64 and I think it is kind of interesting that it can do video output. Anyone tried building a watch around it? I like the idea of having a little more hardware capabilities in a watch but I don't care for the "modern" watches. Right now I have a BangleJS 2 and it works ok but the software is unpolished and buggy. Also the battery life isn't great since Javascript adds a lot of overhead. I think it would be cool if there was a watch that could utilize something a little more mainstream like Linux to speed up development. Since the chip has Wifi you could control it via a web server and it could pull down apps and install updates.

This is really just a random thought I had the other day so it is probably flawed. However, I wish we had a watch with a open ecosystem.

is anyone successfully running postmarketOS on a Pine Note?
if yes, do you think i could run sxmo on it (sway, wayland?)

Merhaba, yaşadığım sorundan bahsetmek istiyorum. 100 veya daha fazla sahip olduğum bu modülde IMEI sorunu yaşıyorum. Ülkemizde 1 yıl boyunca sinyal alamayan cihazlar bakanlık tarafından otomatik olarak kapatılıyor. Ve bunu açmak için ithalatçı olmanız gerekiyor ancak biz bu ürünleri ikinci el aldık. Şimdi IMEI'yi değiştirmem gerekiyor. Bunu nasıl ve hangi uygulamalarla kullanıma açabilirim?

This article explains how we ported Apache NuttX RTOS from QEMU Arm64 to Yuzuki Avaota-A1 SBC based on Allwinner A527 SoC ... Completed within 24 Hours!

We're ready for volunteers to build NuttX Drivers for Avaota-A1 / Allwinner A527 (GPIO, SPI, I2C, MIPI CSI / DSI, Ethernet, WiFi, ...) Please lemme know, maybe we can draw something on the Onboard LCD! ?

Check out the article: https://lupyuen.org/articles/avaota.html



Lup

Hello Everybody,

Please don't get mad, but exactly how do I flash my PineTime? I have it here with my Linux computer and my Volla X23 Ubuntu phone and I can't figure out how to flash it. Please help.

Chris

so i have always had problems with the micro sd card in my pinebook pro.
the micro sd card is now stuck and i wanna switch distros.
i tried the old knife method, etc. but ended up screwing up the outer part of the card.
is my next bet to the case off and get it out that way?
not sure its even safe to use the card at this point.

thanks

Hi together,

here comes a solution for a problem I had with the PinePhone Pro, hoping that it helps someone else. When I started installing different distributions, there was the same problem all over again. The volume buttons were randomly sending signals to the phone although I didn't press them, constantly changing the volume. This was very annoying as the pop-up message interrupted anything I wanted to do on the phone. After some research I found the following work around. Tested it on Arch with Phosh and on Manjaro with Plasma Mobile, but should work on other distros too. The solution works by unbinding the volume keys from the driver. The volume keys will stop working then, but the power key can still be used normally. Up to now I didn't miss the volume keys, as it can easily be adjusted in the settings. You can find more information about driver unbinding in this article: https://lwn.net/Articles/143397/

First open a terminal and issue the following command to stop the nuisance: