I have a setup running 4 Pine 1 boards (the first board developed by Pine).  Earlier this year I purchased a Rock64-2G as well as the power supply listed in the Pine website to use for the Rock64.  I also downloaded the Armbian software listed for the Rock64 on the Pine website.  Using the Etcher executable on Windows I installed Armbian on a micro sdcard.  Then after plugging a ethernet plug, an HDMI plug, a keyboard and mouse and finally the power cord.  A red light on the card turns on but nothing appears on the HDMI terminal.  Again, this setup works fine for my Pine 1 boards.  Does anyone have any idea what I am doing wrong?

Looking at selling my Pinebook Pro, it's a later 2022/4GB RAM/64GB EMMC model with the standard Manjaro install with uboot. Flashed with the updated keyboard and trackpad firmware. I'm thinking since I'm in Canada I could help save someone the shipping costs of buying new if there's interest. I have tow-boot ready on an SD card if the potential buyer would like to have tow-boot flashed to the SPI, since I recently removed it.

I'm not sure if there's a standard format for selling through here, but I have a paypal account setup that I've sold hardware over on Reddit's hardware swaps through so I'm familiar with that process and the associated buyer protection. Pick up is available if you're in Western Canadad and up for a drive but I live in a relatively small city, PM me if you're interested!

Presently I have 2 Pinephones.  I'd like to pack some custom electronics into the phone rather than rely on the USB connector.  The USB is nice, but basically I'm searching for some kind of customized back case that is large enough to pack in an additional circuit board or sensor.

Alternatively, if there are any CAD files for the official case, then I could use them to try and 3D-print what I have in mind.

Any thoughts on where to start?

My PineTime talk was accepted to FOSDEM.

https://fosstodon.org/@jmlich/111578248247468571
https://pretalx.fosdem.org/fosdem-2024/t...GBNJETUGDC

The topic of the talk is more for beginners, but this will be compensated with discussion after the talk and by personal contact. Feel free to reach me for some small talk or a beer.

The monthly updates are still pop up. I just forgot to post it here:

http://nemomobile.net/pages/nemomobile-in-august-2023/
http://nemomobile.net/pages/nemomobile-i...mber-2023/
http://nemomobile.net/pages/nemomobile-in-october-2023/
http://nemomobile.net/pages/nemomobile-i...mber-2023/

December update will show up by the end of the year.

Unfortunately, everything is going slowly. Qt6 porting is still in progress. Biggest achievement is probably Qt6 port of Maliit keyboard.

Hi,

I am selling a pinebook pro and can deliver in the EU. I am a windows guy, and ambitiously bought it with great intentions of tinkering etc. but I did not end up doing much with it.

Price: €90 + €20 shipping in the EU. I am based in Ireland, so if someone local wants to collect that's fine, or delivery should be cheaper.

• US keyboard
  
• 64gb flash
  
• Default Manjaro install
  
• Barrel Charger
  

Pine64 Ox64 BL808 (64-bit RISC-V SBC) is now officially supported in Apache NuttX RTOS! (Real-Time Operating System)

Ox64 BL808 is an affordable $8 SBC with:
- 3 x RISC-V Cores (T-Head 64-bit / 32-bit)
- Networking: Ethernet, WiFi, Bluetooth LE, Zigbee
- Peripheral Interfaces: UART (Serial), I2C, SPI, USB, MIPI CSI
- Interrupt Controller: CLINT and PLIC
- Memory Management: Sv39 MMU
- OpenSBI Supervisor Binary Interface and U-Boot Bootloader
- Bootable microSD: Boot Linux and NuttX

But there's a catch:
- Limited RAM (64 MB): It's not for gaming and servers
- Flash Memory is Empty: Needs a One-Time Flashing (via a USB Serial Adapter)
- Barebones Form Factor: Fits on a Breadboard, Ethernet is optional

In this article we walk through the steps to:
(1) Flash into Ox64 the U-Boot Bootloader and OpenSBI
(2) Boot Linux on a microSD Card
(3) Do the same to boot NuttX RTOS
(4) Run some Bare Metal Experiments inside the NuttX Kernel

Check out the article here:
$8 RISC-V SBC on a Real-Time Operating System: Ox64 + NuttX

Lup
   

Does anybody know where or what package is used to control power management like what application get what power and how much from the battery, or what what chip gets assigned power and how much?

I can't boot my newly received Pinephone Pro into the Factory Test Build for Hardware Checking linked to by the phone's wiki page. I've verified the md5 hash of the downloaded image, and tried two SD cards. The accompanying instructions on that wiki page seem to be out of date, referring to an "RE button" that is only on phones sold between January and July 2022, according to other sections of the same page. Here's the procedure I've pieced together for my phone and attempted:

1. Download file and verify md5 hash.
   
2. Gunzip it.
   
3. sudo dd if=pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img of=/dev/sdb bs=1M status=progress conv=fsync
   
4. Put the SD card in the phone.
   
5. Power on / buzz once.
   
6. Hold volume down, wait for another buzz, and release.
   
7. LED changes to blue.
   
8. At this point it should boot from the SD card, but it buzzes and flashes red and yellow, and boots into the stock Manjaro with Plasma Mobile.
   

When I first got my Pinephone Pro a little over two weeks ago, I removed my T-Mobile SIM card from my old phone, and inserted it in my Pinephone Pro. I enabled mobile data by setting the APN to fast.t-mobile.com in the phone's settings, and I recall that it seemed to work until I also enabled MMS by setting MMSC to http://mms.msg.eng.t-mobile.com/mms/wapenc in the Spacebar texting program. I was able to send MMSs, but at some point thereafter, data stopped working. Editing/deleting/recreating the APN setting, rebooting, and removing/reinserting the SIM all did not help, so I put the SIM back in my old phone. I was also disappointed that YouTube videos in the Angelfish browser skipped (even over Wi-Fi), and were therefore basically unwatchable/unlistenable. I didn't get a chance to test the Pinephone Pro again until yesterday.

Well yesterday and today... data and MMS suddenly work fine. There are two reception symbols in the status bar, and one has a little "L" on it. I don't know what the "L" stands for, but I presume that symbol is for mobile data, because it gets replaced by a Wi-Fi symbol when Wi-Fi is enabled (which must mean the reception symbol without an L is for regular voice coverage). And YouTube videos suddenly play at 1080p in Angelfish over mobile data and Wi-Fi with no skipping now, which is great. However, on the phone's pull-down quick settings menu, the "Mobile Data" button usually says "Off", even when the "Mobile Data" switch is enabled deeper inside the "Cellular Network" settings, the symbol with the "L" is in the status bar, Wi-Fi is off, and data appears to be working. I'm inclined to chalk that up to Plasma Mobile being buggy (as it has plenty of other UI bugs).

Unfortunately, outgoing voice quality is awful. On a call between the Pinephone Pro with T-Mobile and an iPhone with Metro (which is owned by T-Mobile), the iPhone can be heard fine on the Pinephone Pro, but listening on the iPhone the Pinephone Pro sounds like it's at a harsh noise concert. Yes, this is with muting one microphone or going to separate locations to make sure there is no feedback loop. I'm worried there could be a hardware problem with the Pinephone Pro's microphone, and if so I don't know if the Factory Test Build for Hardware Checking would detect it since the mic technically "works", but I'm going to try running the FTB. Also, the phone died when it said the battery was 33% full.

1) Has anyone else used a Pinephone Pro with T-Mobile in the US, and can you comment on your experience?
2) Might upgrading to biktorgj's custom modem firmware alleviate any of the issues I've experienced?
3) Might changing out Manjaro + Plasma Mobile for Gentoo + Wayland + SXMO alleviate anything?
(My x86 laptop runs Gentoo + Wayland + Sway, and I already have experience cross-compiling for ARM for a Raspberry Pi).