Hi everyone!

I've been searching for a solution to fan related issues for my RockPro64 including this site, Armbian stuff, and OMV. I've found a couple of related issues in sites outside this one but haven't posted there yet. 

Based on the cadence of posts & responses found in the RockPro64 sub-forum on this site, I'm not very optimistic my inquiry will have any response. 

Could anyone recommend any active forums where there might be some better hope at engaging a user base for this hardware? 

If it helps, I'm running the Armbian variant of Bookworm on my RockPro. 

I'm not here to say I'm disappointed with my RockPro setup. Quite the opposite in fact. That being said more recently have had some thoughts about maybe I should have chosen a device with a more robust support system (if not from the user base, then at least from the manufacturer).  

I very much appreciate anyone's insight!

I have what seems like a hardware problem and am trying to diagnose it. Most likely, it is the PMIC (Power Management IC) or something else on the motherboard that is bad and would have to be replaced, but maybe I am missing something.

First, I have a Convergence Edition PinePhone (1.2b board) which I got about 2 years ago.

Second, the lead up. PinePhone spontaneously rebooted like it sometimes does and was sitting at the screen for providing the decryption password for the storage for a long time, draining the battery and producing a lot of heat and getting decently warm. I finally noticed and logged in and the phone claimed that there was just 5% battery left. I plugged it into my computer as quickly as I could (USB A to C cable). My OS (Mobian Trixie) didn't indicate that it was plugged in so I tried the usual unplug, replug, unplug, plug in a different way, etc.

Then finally went to the power section of the settings program (I use Phosh) to see what was wrong. It indicated the battery health was good and was registering that the USB was there but not its voltage or current. Based on the discharge rate with the USB cable plugged and unplugged, not enough current was being drawn from the USB so the battery was steadily draining further just at a slower rate. I tried other chargers including the one I used every day, plugging into the USB C cable on my computer, a steamdeck charger, and an old pre USB-PD charger I still have, as well as trying some of these through the USB dock. Same result including not being able to read the USB voltage.

I turned it off and let it sit for several hours with the charger plugged in before turning it on again. No change in battery charge and continuing to drain.

So, I just unplugged it and removed the battery (to really really turn the whole thing off long enough that none of the capacitors and inductors would have any energy left in them) and let it sit.

Later, I put the battery back in and powered it up again. Same result as before. Though now it was registering the battery as 10%. I did not remember the battery voltage from before, so I do not know if it was higher or lower. Then, I flipped all the switches to turn off everything I could (modem, wifi, cameras, microphone) and the discharge rate dropped to nearly but not quite zero. But still no charging. Again, it was reporting that the battery health was good. I tested it again but this time with the modem on but not the rest. Battery was discharging despite being connected to an overkill USB power source.

From this, it was clear that at least one of the following was true

1. USB circuitry was bad and not enough current could be sourced
2. Battery was bad but in a way that the PMIC could tell but the rest of the system couldn't
3. PMIC or other power circuitry had gone bad (whether hardware or firmware)

I hooked the phone up into the PinePhone keyboard to see if I could eliminate possibilities (I had been intending to buy one for some time and decided to go ahead and do it since it could help diagnose). Same exact pattern. Can't charge the battery. The modem being on causes the battery to discharge even though the keyboard can supply more than enough power.

This seems to eliminate possibility 1 above, leaving only

1. Battery was bad but in a way that the PMIC could tell but the rest of the system couldn't
2. PMIC or other power circuitry had gone bad (whether hardware or firmware)

Based on what the battery diagnostics and its voltage, I am inclined to think that the battery itself is probably OK. It definitely wasn't at a low enough voltage to be unrecoverable -- 3.5 V or so (very drained and likely its lifespan reduced by it, but still should be OK).

This makes me think it is the PMIC or its support circuitry.

Am I missing a possibility, or is this the best guess that can be made?

If it is the PMIC, is it possible it is just a firmware issue (maybe firmware got corrupted)?

Otherwise, I am looking at having to replace the motherboard if I want to get my PinePhone working again, or replacing the phone outright (would go to the PinePhone Pro).

I've been playing with new and different OS images on SD cards on my pinephone pro since I got it. I noticed about 6 months ago the latest Mobian release I imaged would show random but very regular volume changes to the internal speaker. Looked like a hardware issue at first, but the problem followed the software I was using as going back to an earlier release or a totally different OS made the problem go away. Today, all the well supported releases seem to have the same bug. The strange part being that I can't find any other posts with the problem. Is there some combination of things on my system causing this?

Since no other phone manufacture does this as far as i know of, Is there any tool that you can download that allows you to create a whitelist of phone numbers that can be accepted and the rest rejected including texts, example I go to create a whitelist of numbers that i will allow to call or text me and it automatically rejects the rest. Even if i can get something to play around with like if a number calls i can ask it to send me a text of who called or even just a block all, like i can decide if i want texts and calls to come through on this as an option or just not get anything from anybody except what is on the approved list.

in case businesses call i want the option to have a text sent saying somebody called.

Do not disturb is not a relly good option for what i want, the only closest thing that was available to what i need was Sprint when they were a company and they had the option but it wasnt fully there but close.
 
I dont know if this is something that would have to be made as open source through the modem itself meaning bjtork would have to implement it or it can be a tool to download through the internet and can control what the modem recieves and rejects.

I recently purchased an 80mm Noctua NF-A8 ULN fan for the Rock NAS case along with a Noctua 2pin to 3pin adaptor. Fan is indeed 12v.

Plugging it in I get nothing...no fan movement at all. I'm using a recent version of Armbian if that matters.

I believe I see this device under /sys/class/hwmon/hwmon4/ since is see pwm1 as well as pwm1_enable. 

I tried installing flatpak (which I will then use to install Thunderbird), but when I try to run flatpak I get
"error while loading shared libraries: libsodium.so.26: cannot open shared object file: no such file or directory"

Any comments are appreciated.

Should I check the battery by joining the two internal battery leads in my PBP? Are there any cautions to be aware of by using this technique?

Just got my PBP yesterday. It doesn't seem to matter whether I use the barrel charger or usb the red light goes out after being on for 1-2 hours. If the battery is not charged completely and I have power supplied to the unit should it boot? Press the start button and will not turn on. Any ideas on issues? Any help is appreciated. Thanks

Last week I got my sealed PineTime. I could connect to it using GadgetBridge from my Android Phone and flash it with InfiniTime 1.14.0.

It seems to work fine in general - but only while it's in the charging cradle!

The moment I remove it from the cradle, ...

• I can no longer wake the watch by tapping the screen.
  
  
• I can no longer wake the watch by pressing the physical button. It doesn't matter how long I press - I tried short, a few seconds, 10 seconds, 20 seconds
  
  
• GadgetBridge says that the watch is no longer connected.
  
  
• Re-running the bluetooth device search in GadgetBridge does not find the watch either.
  I also tried removing the device from GadgetBridge first. In that case, the device shows up in the search results. When I do not connect but remove the watch from its cradle, the device disappears from the search results page instantly.
  

I have a custom PCIe x4 lane card that I'm trying to integrate with a RockPro64 SBC. This custom card has been tested with many users on different platforms including a linux x86 system. When I try this card in a RK3399 system, I get a strange result when I view the assigned address space with the lspci command. It appears the address assigned is the exact value of the BAR address size for each BAR. If I change the BAR size the assigned address changes to that value. Below is a dmesg dump along with a lspci output for my device. Device is  [ad00:001e]. Any guidance?
 
dmesg:
[    2.395091] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[    2.395148] rockchip-pcie f8000000.pcie:      MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[    2.395175] rockchip-pcie f8000000.pcie:       IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[    2.396226] rockchip-pcie f8000000.pcie: supply vpcie1v8 not found, using dummy regulator
[    2.396376] rockchip-pcie f8000000.pcie: supply vpcie0v9 not found, using dummy regulator
[    2.571466] rockchip-pcie f8000000.pcie: wait 1000 ms (from device tree) before bus scan
[    3.582289] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[    3.582303] pci_bus 0000:00: root bus resource [bus 00-1f]
[    3.582316] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[    3.582330] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[    3.582387] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[    3.582547] pci 0000:00:00.0: supports D1
[    3.582557] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    3.588072] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    3.588301] pci 0000:01:00.0: [ad00:001e] type 00 class 0x000000
[    3.588382] pci 0000:01:00.0: reg 0x10: [mem 0xfffffe00-0xffffffff]
[    3.588455] pci 0000:01:00.0: reg 0x18: [mem 0xffe00000-0xffffffff]
[    3.588606] pci 0000:01:00.0: Upstream bridge's Max Payload Size set to 128 (was 256, max 256)
[    3.588632] pci 0000:01:00.0: Max Payload Size set to 128 (was 128, max 128)
[    3.589238] pci_bus 0000:01: busn_res: [bus 01-1f] end is updated to 01
[    3.589272] pci 0000:00:00.0: BAR 14: assigned [mem 0xfa000000-0xfa2fffff]
[    3.589287] pci 0000:00:00.0: PCI bridge to [bus 01]
[    3.589302] pci 0000:00:00.0:   bridge window [mem 0xfa000000-0xfa2fffff]
[    3.589497] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[    3.589853] pcieport 0000:00:00.0: PME: Signaling with IRQ 37
[    3.590302] pcieport 0000:00:00.0: AER: enabled with IRQ 37
 
lspci -v:
00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3399 PCI Express Root Port (prog-if 00 [Normal decode])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 37
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: fa000000-fa2fffff [size=3M] [32-bit]
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport

01:00.0 Non-VGA unclassified device: Alta Data Technologies LLC Device 001e
Subsystem: Alta Data Technologies LLC Device 001e
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 0
Region 0: Memory at fffffe00 (32-bit, non-prefetchable) [disabled] [size=512]
Region 2: Memory at ffe00000 (32-bit, non-prefetchable) [disabled] [size=2M]
Capabilities: <access denied>