| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,118
» Latest member: Samiha
» Forum threads: 16,363
» Forum posts: 117,536
Full Statistics
|
| Latest Threads |
Weatherproof case build
Forum: Enclosures
Last Post: ltorsini
07-07-2026, 07:01 PM
» Replies: 12
» Views: 38,514
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: PinePhoneProUser
07-07-2026, 04:47 PM
» Replies: 16
» Views: 11,063
|
pinecil v2 dosent negotia...
Forum: General Discussion on Pinecil
Last Post: moses
07-07-2026, 07:28 AM
» Replies: 0
» Views: 76
|
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
07-06-2026, 05:22 PM
» Replies: 2
» Views: 232
|
Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
07-05-2026, 11:02 AM
» Replies: 0
» Views: 119
|
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
07-04-2026, 04:41 PM
» Replies: 6
» Views: 4,083
|
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 311
|
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 175
|
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,630
|
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,247
|
|
|
| pinecil v2 dosent negotiate power |
|
Posted by: moses - 07-07-2026, 07:28 AM - Forum: General Discussion on Pinecil
- No Replies
|
 |
hello i recently got my pinecil v2 did the usual stuff checked if its real updated firmware it all worked, then the next day, for some reason it just dosent negotiate, im pretty good with smd soldering so im thinking to replace the cc resistors with some new ones and pray, what should i do?
|
|
|
|
| Rock64 v2.0 u-boot SPI issues |
|
Posted by: ju0n - 07-05-2026, 11:02 AM - Forum: General Discussion on ROCK64
- No Replies
|
 |
Hi,
I've some rock64 V2.0 boards . All of them flashed SPI u-boot long time ago with Ayufan script. They worked flawlessly until now that i've tried to update to debian 13. No way to boot installer neither sd card or usb i had to erase spi u-boot to be able boot debian 13 installer. Now i've installed debian 13 but no way to burn any working SPI u-boot. The last ones dont do nothing, any output from serial console and older ones dont let boot debian 13 from sd card with a kernel panic message show in serial console.
I guess there is some issue with SPI u-boot and rock64 V2.0. Any working updated SPI u-boot in rock64 v2.0 available?
Thanks in avance
|
|
|
|
| Pinephone software |
|
Posted by: Csanderson0313 - 07-04-2026, 08:23 AM - Forum: General Discussion on PinePhone
- Replies (2)
|
 |
Hi Everyone,
Hope everyone is doing well. I have been away from pinephone for quite a while but starting back with it again. What is the most stable Software out for it? I have noticed that the Pinephone pro is no longer being made. It does not seems like they made it very long. What is everyone thoughts on the future of PinePhone? Does everyone think it has a long and bright future?
Thank You
Chris
|
|
|
|
| PineNote v1.2 - Charges Never Enter "Charging" State (Factory OS, RK817 Below Minimum |
|
Posted by: ttsp - 07-02-2026, 02:52 AM - Forum: General Discussion on Pinebook Pro
- No Replies
|
 |
I'm looking for help determining whether this is a software issue (kernel/device tree/RK817 driver) or a hardware failure before pursuing an RMA.
Hardware - PineNote v1.2 (Community Edition)
- Original factory-installed OS (never replaced or reinstalled)
- Current kernel:
Code: 6.12.11-pinenote-202501281646-00249-g211ba27556cc
- Installed kernel package:
Code: linux-image-pinenote-stable 1.7
Timeline
The device arrived with approximately 40% battery.
I never installed an alternate operating system. The charging problem occurred on the factory-installed OS within the first day after unboxing.
The device operated normally from its initial battery charge but never successfully charged from any charger.
Eventually the battery discharged to 0%.
The interesting part is that the PineNote still boots and runs normally when external USB power is connected. I can SSH into it and run diagnostics. The only failure appears to be that the battery never actually charges.
Chargers Tested
I tested all of the following:- OEM USB-A ↔ USB-C cable
- USB-A wall charger
- USB-A laptop port
- 65 W USB-C PD laptop charger
Behavior is identical with every charger.
When powered off and connected to power, the charging animation appears on the display.
I also left it connected overnight while powered off.
Battery level remained at 0%.
USB Issue
Initially the device was affected by the USB issue described in PNDeb Issue #106.
After applying the recommended fix:
works normally.
USB connectivity appears completely functional now.
Charging behavior did not change.
This makes me think the USB problem and the charging problem are unrelated.
Diagnostics
Battery state:
Code: cat /sys/class/power_supply/rk-bat/uevent
Relevant output:
Code: POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_CAPACITY=0
POWER_SUPPLY_CURRENT_AVG=-168560
POWER_SUPPLY_VOLTAGE_AVG=346xxxx
The important point is that the battery never transitions to:
Code: POWER_SUPPLY_STATUS=Charging
even while external power is connected.
Charger state:
Code: cat /sys/class/power_supply/usb/uevent
Relevant output:
Code: POWER_SUPPLY_ONLINE=1
POWER_SUPPLY_USB_TYPE=Unknown [DCP]
POWER_SUPPLY_VOLTAGE_AVG=452xxxx
So Linux clearly detects external power.
Kernel messages:
Code: dmesg | grep -i rk817
produces repeated messages similar to:
Code: rk817-charger: Battery voltage 3465880 below minimum voltage 3500000
rk817-charger: Battery voltage 3477640 below minimum voltage 3500000
rk817-charger: Battery voltage 3483240 below minimum voltage 3500000
I do not see any other charger-related or battery-related errors.
Package Status
Kernel package is already current:
Code: apt update
apt list --upgradable
apt policy linux-image-pinenote-stable
No newer PineNote kernel is available.
What Seems to Be Happening
From everything I've observed:- USB is functioning.
- External power is detected.
- Charger is detected (
).
- Battery is detected.
- The device boots and runs on external power.
- The battery never enters the
state.
- Battery voltage remains below the RK817 minimum threshold (~3.5 V).
- The battery never recovers, even after being connected overnight.
Questions
- Has anyone seen the RK817 refuse to perform pre-charge when the battery falls below approximately 3.5 V?
- Is there a known device-tree or kernel configuration issue that could prevent pre-charging?
- Is there a way to determine from software whether the battery protection circuit has tripped?
- Are there any additional diagnostics I should collect (debugfs, I2C register dumps, RK817 register reads, etc.)?
- Does this behavior point more toward a failed battery or charging hardware than a software problem?
Any guidance from people familiar with the RK817 charger implementation or PineNote power management would be greatly appreciated.
Here are various diagnostic commands and their return values:
===== DATE =====
$ date
Thu Jul 2 08:50:52 UTC 2026
===== KERNEL =====
$ uname -a
Linux pinenote 6.12.11-pinenote-202501281646-00249-g211ba27556cc #1 SMP Tue Jan 28 17:04:28 CST 2025 aarch64 GNU/Linux
===== OS RELEASE =====
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux trixie/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=trixie
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
===== KERNEL PACKAGE =====
$ dpkg -l | grep linux-image-pinenote || true
ii linux-image-pinenote-stable 1.7 all Linux for the PineNote (meta-package)
===== POWER SUPPLY DEVICES =====
$ ls -l /sys/class/power_supply/
total 0
lrwxrwxrwx 1 root root 0 Jul 12 2026 rk817-battery -> ../../devices/platform/fdd40000.i2c/i2c-0/0-0020/rk817-charger.7.auto/power_supply/rk817-battery
lrwxrwxrwx 1 root root 0 Jul 12 2026 rk817-charger -> ../../devices/platform/fdd40000.i2c/i2c-0/0-0020/rk817-charger.7.auto/power_supply/rk817-charger
===== BATTERY SUMMARY =====
$ grep -E 'POWER_SUPPLY_(PRESENT|STATUS|CAPACITY|VOLTAGE_AVG|CURRENT_AVG|VOLTAGE_MIN_DESIGN|VOLTAGE_MAX_DESIGN|CHARGE_NOW|CHARGE_FULL|CHARGE_TYPE)' /sys/class/power_supply/rk817-battery/uevent
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_CHARGE_TYPE=Standard
POWER_SUPPLY_CHARGE_FULL=4000000
POWER_SUPPLY_CHARGE_FULL_DESIGN=4000000
POWER_SUPPLY_CHARGE_NOW=1237024
POWER_SUPPLY_VOLTAGE_AVG=3750360
POWER_SUPPLY_CURRENT_AVG=-179912
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=3500000
POWER_SUPPLY_CAPACITY=31
POWER_SUPPLY_VOLTAGE_MAX_DESIGN=4200000
===== CHARGER SUMMARY =====
$ grep -E 'POWER_SUPPLY_(ONLINE|USB_TYPE|VOLTAGE_AVG|VOLTAGE_MIN_DESIGN|VOLTAGE_MAX_DESIGN)' /sys/class/power_supply/rk817-charger/uevent
POWER_SUPPLY_ONLINE=1
POWER_SUPPLY_USB_TYPE=Unknown [DCP]
POWER_SUPPLY_VOLTAGE_MAX_DESIGN=5500000
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=3800000
POWER_SUPPLY_VOLTAGE_AVG=4516000
===== FULL BATTERY UEVENT =====
$ cat /sys/class/power_supply/rk817-battery/uevent
DEVTYPE=power_supply
OF_NAME=charger
OF_FULLNAME=/i2c@fdd40000/pmic@20/charger
OF_COMPATIBLE_N=0
POWER_SUPPLY_NAME=rk817-battery
POWER_SUPPLY_TYPE=Battery
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_CHARGE_TYPE=Standard
POWER_SUPPLY_CHARGE_FULL=4000000
POWER_SUPPLY_CHARGE_FULL_DESIGN=4000000
POWER_SUPPLY_CHARGE_EMPTY_DESIGN=0
POWER_SUPPLY_CHARGE_NOW=1237024
POWER_SUPPLY_CONSTANT_CHARGE_VOLTAGE_MAX=4200000
POWER_SUPPLY_VOLTAGE_AVG=3750360
POWER_SUPPLY_CONSTANT_CHARGE_CURRENT_MAX=2000000
POWER_SUPPLY_CURRENT_AVG=-179912
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=3500000
POWER_SUPPLY_CAPACITY=31
POWER_SUPPLY_VOLTAGE_MAX_DESIGN=4200000
POWER_SUPPLY_CHARGE_TERM_CURRENT=300000
===== FULL CHARGER UEVENT =====
$ cat /sys/class/power_supply/rk817-charger/uevent
DEVTYPE=power_supply
OF_NAME=charger
OF_FULLNAME=/i2c@fdd40000/pmic@20/charger
OF_COMPATIBLE_N=0
POWER_SUPPLY_NAME=rk817-charger
POWER_SUPPLY_TYPE=USB
POWER_SUPPLY_ONLINE=1
POWER_SUPPLY_USB_TYPE=Unknown [DCP]
POWER_SUPPLY_VOLTAGE_MAX_DESIGN=5500000
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=3800000
POWER_SUPPLY_VOLTAGE_AVG=4516000
===== POWER-RELATED DMESG =====
$ dmesg | grep -Ei 'rk817|battery|charger|charge|power_supply' || true
|
|
|
|
| Fix Bricked SPI Flash, Pinephone Pro |
|
Posted by: FR_IV - 06-27-2026, 05:00 PM - Forum: PinePhone Pro Hardware
- No Replies
|
 |
Hi!
A couple weeks ago I was trying to write Tow-Boot to my Pinephone Pro's SPI Flash. It worked once, so I know that the SPI device is connected and functional. However, (unrelated to the Tow-Boot install) I messed up the Manjaro-Phosh installation I had previously installed on the Pinephone pro, so I reinstalled Manjaro-Phosh which removed Tow-Boot from the SPI flash. I tried to rewrite Tow-Boot in the same way as before, but it got stuck and I forced the Pinephone Pro to power-off. I then tried to write Tow-Boot again and I got the following error:
Code: Checks failed... [ret = 4]
Nothing was done.
Details:
Error: /dev/mtdblock0 not found
$ dmesg | grep -i spi
---
[ 1.176820] spi-nor spi0.0: unrecognized JEDEC id bytes: ff ff ff ff ff ff
[ 1.184548] spi-nor: probe of spi0.0 failed with error -2
---
I booted the Pinephone Pro to the Manjaro-Phosh installation I put on it and I used fdisk -l and ls /dev/ but I did not find the SPI Flash nor any mtd or mtdblock devices.
I have reinstalled Manjaro to the Pinephone Pro through booting on an SD card and through connecting my Pinephone Pro to my computer as an external drive using the Tow-Boot installer booted on an SD card.
I have tried to write the Tow-Boot.spi.bin binary to the SPI through putting my phone in MaskRom mode and using the rkdeveloptool through the command line on my linux laptop.
I have tried to zero everything out with rkdeveloptool by writing zeros.
I booted the factory android image with the hardware test app on an SD card and the SPI Flash failed its test.
I tried all of these at least twice each and they have all returned no errors, but I still get the same error from the Tow-Boot installer and I still cannot find the SPI Flash device or any mtd or mtdblock devices.
Is there any way to revive the SPI device? Would it require wiring to it directly since nothing has been able to read it?
Thank you in advance!
I should note, that my Pinephone Pro boots to the internal emmc and to SD cards without a problem, so fixing the SPI is not vital to using my pinephone pro, but I don't like to loose available hardware and it would be nice to install Tow-Boot.
|
|
|
|
| Big thanks for the documentation! |
|
Posted by: alchemist - 06-25-2026, 12:58 PM - Forum: General Discussion on Pinebook Pro
- No Replies
|
 |
Hi,
I am a happy and daily Pinebook Pro user since may 2021. The last years, I broke the USB-C port, then the keyboard panel at the left hinge.
I decided to replace the motherboard and keyboard panel, ordered the pieces and received them3 days after.
Then I had some free hours yesterday to fix my loved laptop. And I was really pleased by the well written documentation. I followed the section describing the different steps with very clear illustrations.
And in some minutes, I have a almost new shiny laptop.
Everything was immediately working except wifi and bluetooth, because the chips changed (BCM43456 to BCm43455) the new chip is supported by official linux firnware and same for bluetooth.
Very happy user
|
|
|
|
| Pinecil low temp mods? |
|
Posted by: davidcoley - 06-21-2026, 02:53 AM - Forum: General Discussion on Pinecil
- No Replies
|
 |
Hello,
I'm a complete beginner to this area, but I'm interested in using a Pinecil V2 with wax for jewellery modelling. Before I buy one, I'm wondering whether it's possible to modify it to operate at around 60°C or lower while still maintaining accurate temperature control.
Has anyone tried this, or does anyone have experience using a Pinecil for wax work? I'd be interested to hear your thoughts, recommendations, or any potential limitations before I make a purchase.
|
|
|
|
|