Title: Where should I post a PineBuds Pro repair and battery replacement guide?

Hi everyone,
I'm new to the forum, and I'd like to thank the Pine64 community for creating such a welcoming place. I've been following Pine64 products for a long time.
There isn't much information about the PineBuds Pro online, so I thought it might be useful to share what I've learned about repairing them, including how to replace the battery.
Could someone point me to the right section to post this in? Thanks in advance, and best wishes to all.

Hi all,

Flashed the latest danctnix yesterday because I kept getting errors when I connected my phone to the USB-port. I need to transfer (really big) files from my Pinetab to my phone, which works without any problems from my desktop computer.
Unfortunately the update did not help; I'm getting the same errors ("an unknown error occured"/"KIO Client stopped working"). After plugging in the cable I sometimes get the option to open the device with the filemanager. If I do, I get incomplete directory listings, or errors as I try to descend into a directory. During the procedure sometimes the connection is lost and I get a new popup in my screen if I want to open the device with the filemanager.

The kde-cli-tools are at the latest version and I already replaced the USB-C cable a few times to no avail.

Has anybody noticed the same behaviour, or am I missing something here?

Any suggestions more than welcome!

I've spent a lot of time thinking about the friction of using a modern phone and I think it comes down to one thing: every device today stands alone, closed and fixed, telling you exactly what it is and how you're allowed to use it. Little to no expandability, in hardware or software.

I think it's time to challenge that. That belief led me to write a hacker phone manifesto — an attempt to revisit the values behind devices like the N900, and sketch what a phone that's open and hardware-expandable could actually look like.

I'd love to hear whether people think this is technically viable today, or whether the market killed that idea for good reasons. And if this is off-topic here, I apologize in advance, you can point me some place better.

https://beyondframe.ink/hacker-phone-the...-hardware/

Hello. Ordering from Pine64 has been hands down the worst experience ever. I have encountered many terrible websites but by far this is horrendous. I get hit with the captcha verification every thirty or so seconds. I do the annoying "mark the bicycle" captcha which eventually says is wrong followed by "tap the bus" captcha. And this verification expires every 20 or so seconds? i open my phone to open the banking app and my card details and it is expired and I have to do the captcha again. 

Worst of all, after all this, when I finally hit pay, I get this wonderful error: "Field Billing address 1 should have only English letters, digits, spaces and , / @ . ( ) - characters."

Great, ascii is the only character set in the world. For Once I decided to spend more money on a company with values I respect, I am barred from buying. It is like you do not want anyone in Europe to buy from you. 

I corrected the address and the error still exists. Only after two tries I realised it is talking about the main billing and shipping address not the billing address it asks AGAIN after entering card details.

I don't need any resolution for this until you fix this terrible website. Even AI can make a better payment experience than Pine64. I still have not placed the large order I wanted and am now considering going back to buying cheaper ones from other sources. Thank you very much guys.

Hello,

I had my Rockpro64 V2.1 board running fine with Debian bookworm and U-Boot built from sources written to SPI. The board was run only occasionally so did not have a lot of stress so far (I believe less than 100 operating hours total). In normal usage the CPU temperature reported by the internal sensor was around 48°C.

Some days ago I had problems booting: the white led would not come on. I tried shorting 23-25 to bypass SPI and I was able to boot from the SD card I originally used to flash U-Boot. Even if the jumper was removed during boot, trying "sf probe" resulted in an error message saying "unrecognised jedec_spi_nor flash".

After this, every further attempt to reboot to reboot with the same SD card resulted in the following:

• HDMI completely dead
  
• white led comes on, no matter if the 23-25 jumper is installed or not (seems like the SPI is dead, so it skips to SD anyway)
  
• U-Boot boots fine as reported by serial terminal
  
• the following error is reported by U-boot:
  Loading Environment from SPIFlash... jedec_spi_nor flash@0: unrecognized JEDEC id bytes: 00, 00, 00*** Warning - spi_flash_probe_bus_cs() failed, using default environment

• after some minutes the board self-reboots
  
• after this, the board keeps rebooting over and over every few minutes
  

Is there a browsable source code repository for the PINE64 Android sources. I would like to avoid doing a full 111 GiB SDK download, just to have a look at the Quartz64 Zero device tree  .

Friends, how does one activate vibration motor in bash script?

I received my Pinetime on Saturday, July 11.  It currently has InfiniTime 1.14.1 installed and I am trying to update it to 1.16.1.

I can pair the watch to my Pixel 10 Pro that is running Android 17 both via normal pairing and via Gadgetbridge without issue, but the watch constantly disconnects and reconnects.

When I try to update the firmware via Gadgetbridge, it will get to a random percentage and then disconnect, failing to update the firmware.

I removed Gadgetbridge, deleted the Pinetime from my phone, installed NRF Connect, then tried the update again through that.  The watch screen will change to FW update screen and stay at 0% while NRF Connect will get to a random percentage of the upload before the watch reboots.

I tried https://infinitimeexplorer.netlify.app/ through the current version of Chrome on my Windows 11 25H2 laptop and I get the same behavior as NRF Connect.

I have charged the watch fully, tried the update both on and off the charger, rebooted the watch as well as my phone and laptop multiple times and the behavior is the same.

Does anyone know what else I can try?

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?

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