| 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,513
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: PinePhoneProUser
07-07-2026, 04:47 PM
» Replies: 16
» Views: 11,061
|
pinecil v2 dosent negotia...
Forum: General Discussion on Pinecil
Last Post: moses
07-07-2026, 07:28 AM
» Replies: 0
» Views: 74
|
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
07-06-2026, 05:22 PM
» Replies: 2
» Views: 231
|
Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
07-05-2026, 11:02 AM
» Replies: 0
» Views: 118
|
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
07-04-2026, 04:41 PM
» Replies: 6
» Views: 4,079
|
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 310
|
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 172
|
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,629
|
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,246
|
|
|
| strange keyboard behaviour, is it faulty? |
|
Posted by: rdmarsh - 08-27-2020, 06:57 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (10)
|
 |
Hey All, Spent ages trying to solve this one and still no closer to getting it solved.
Bought PinebookPro, ansi keyboard at the end of 2019. This problem has been happening for ages. Due to covid etc I haven't gotten to looking at this for ages.
Would appreciate if anyone knows what's going on, or if the keyboard is faulty.
* On boot using an external keyboard everything is fine
* As soon as any key is pressed on the internal keyboard, it goes to uppercase and gets stuck there. Numbers only type the shifted items (!@#$% etc)
* Running showkey (https://linux.die.net/man/1/showkey) and pressing left shift once keeps saying that 'keycode 42 press', which is left shift key. It's not physically stuck though and pressing it shows press and release for it as well.
Pressing any other key stops the constant stream of 'keycode 42 press', but still behaves as if it's stuck.
Only a reboot fixes it and lets me type normally on the external kb again.
I've updated using jackhumbert firmware updater from github, tried this several times and still no joy. In desperation I tried the ISO keyboard version, that doesn't show the shift stuck behaviour. Going back to ansi and it reverts to the shift stuck behaviour.
Would really appreciate any tips on how to solve this, or even if it's possible.
|
|
|
|
| Proximity sensor always active - screen turns off randomly? |
|
Posted by: bitnick - 08-27-2020, 02:45 PM - Forum: Mobian on PinePhone
- Replies (10)
|
 |
I first thought there was some problem with my Pinephone's screen or its driver since it turns off randomly, e.g. while web browsing. After a while I realised that this happens when I have my fingers close to the top front of the phone - i.e. this is caused by the proximity sensor.
Has anyone else noticed this? Shouldn't the proximity sensor only be active during a phone call?
|
|
|
|
| Please help me troubleshoot strange network performance |
|
Posted by: UnoqueVa - 08-27-2020, 02:15 PM - Forum: Linux on RockPro64
- Replies (1)
|
|
Hi, first post here!
My big project this summer was to build a NAS with a RockPro64 at its heart, making use of its PCIe connector to connect an LSI SAS HBA and a SAS expander to connect much more than 4 drives. On top of that, I was able to install ZFS quite easily and use it as a remote backup server for my main NAS. I don't thinks there's many other SBCs than can handle all of that.
After a lot of reading around here and Github, I only tried installing ayufan's pre-release from April, because it added the neccessary support for the LSI card. I chose the OMV version buster-openmediavault-rockpro64-0.10.12-1184-arm64.img.xz and things have been more or less smooth (my gripes are about OMV more than the RP64).
Now, the problem is that I'm trying to send backups between my servers and I'm hitting a strange 300 KByte/s bottleneck when sending from the remote RP64 to my local proxmox Ryzen server. The same test in the other direction achieves about 30 MByte/s (both locations have 300 Mbit fiber internet connections).
Next I've tried with iperf and a Mac Mini that is in the same location as the RockPro64 and the results stump me again:
Code: Proxmox 22 MBytes/s ----(cloud)---> Mac Mini
10~20 MBytes/s <--(_______)---
Proxmox 35 MBytes/s -----(cloud)---> RockPro64
0.37 MBytes/s <---(_______)---
RockPro64 ~30 MBytes/s -----LAN---> Mac Mini
20~40 MBytes/s <----------
So it seems like the RockPro is capable of sending 30 MByte/s upsteam its network port, just not towards my Proxmox server.
And the router can send me a reasonably fast stream, just not from my RockPro64 
I've tested raw iperf3, zfs sends through ssh, zfs sends through Wireguard... the 300 Kb/s limit is consistent.
Please help me, what is it that I'm missing? 
|
|
|
|
| Accessing UART4 on RockPro64 (Armbian) |
|
Posted by: antonlyap - 08-27-2020, 01:36 PM - Forum: Linux on RockPro64
- Replies (1)
|
|
Hi there! I am trying to set up communication between an Attiny85 and my RockPro64 over UART (running Armbian, kernel `Linux rockpro64 5.7.15-rockchip64 #20.08 SMP PREEMPT Mon Aug 17 00:26:28 CEST 2020 aarch64 aarch64 aarch64 GNU/Linux`). The issue is that I can't connect to the serial port:
Code: rock64@rockpro64:~$ sudo picocom -b 115200 /dev/ttyS4
[sudo] password for rock64:
picocom v3.1
port is : /dev/ttyS4
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
hangup is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
logfile is : none
initstring : none
exit_after is : not set
exit is : no
FATAL: failed to add port: Filedes is not a tty
I can see that UART4 is not initialized on boot:
Code: rock64@rockpro64:~$ dmesg | grep tty
[ 0.000000] Kernel command line: mmc_cmdqueue=0 earlycon=uart8250,mmio32,0xff1a0000 root=UUID=73fac48d-4f73-4ac1-b899-e67dc98b5794 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=f499ef85-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[ 0.001600] printk: console [tty1] enabled
[ 4.089584] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 38, base_baud = 1500000) is a 16550A
[ 4.089974] serial serial0: tty port ttyS0 registered
[ 4.091686] ff1a0000.serial: ttyS2 at MMIO 0xff1a0000 (irq = 39, base_baud = 1500000) is a 16550A
[ 4.092153] printk: console [ttyS2] enabled
[ 10.755654] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 14.723780] systemd[1]: Found device /dev/ttyS2.
Code: rock64@rockpro64:~$ cat /boot/armbianEnv.txt
verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=73fac48d-4f73-4ac1-b899-e67dc98b5794
rootfstype=ext4
overlays=uart4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
If this is helpful - here are some details about my setup:
An Attiny85 is powered from a 3V coin cell. Here is the wiring:
- Battery positive - Attiny85 pin 8
- Battery negative - Attiny85 pin 4 - RockPro64 ground on GPIO pin 6
- Attiny85 pin 6 (PB1) - RockPro64 UART4_RX on GPIO pin 21 (connected through a 1K current-limiting resistor)
- UART4_TX is not connected because currently I only need unidirectional communication
I used Arduino IDE with a USBtinyISP programmer to program my Attiny85 with the following test code:
Code: #include <SoftwareSerial.h>
#define RX 0
#define TX 1
SoftwareSerial serial(RX, TX);
void setup() {
// put your setup code here, to run once:
serial.begin(115200);
}
void loop() {
// put your main code here, to run repeatedly:
serial.println("ping");
}
Is there any way I can fix this issue? Are there any other easy-to-use alternatives to UART for establishing bidirectional communication? Any help is appreciated!
Thanks,
Anton
|
|
|
|
| info on touch screen APIs? |
|
Posted by: Rich_Morin - 08-27-2020, 12:18 PM - Forum: PinePhone Software
- No Replies
|
|
I'm interested in supporting braille input on a PinePhone. The datasheet contains a lot of useful-looking information on the hardware, but (of course) it says nothing about software APIs for the touch screen. Assuming that I'm running Linux (e.g., Mobian, pmOS), where should I look for this information?
|
|
|
|
| My Daily QA - 2020-08-27 |
|
Posted by: AmazingNutria - 08-27-2020, 11:58 AM - Forum: Mobian on PinePhone
- Replies (3)
|
|
Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating, SIM installation, Wifi Configuration, and Power Cycling the devices.
Results: mobian/2020-08-27-Verizon.html
mobian/2020-08-27-TMobile.html
[b]Conclusion: OS is not Ready for pinephone to be daily driver.
Notes: Today was an interesting testing day. MMS is still not working. The camera is still lagging. Call quality varied between TMobile and Verizon. Call quality of the microphone on TMobile was great. Clear, no echo, no problems. Call quality of the microphone on Verizon is very sensitive. Louder then necessary. It made the call experience very poor.
|
|
|
|
| My Daily Manual QA |
|
Posted by: plainenough - 08-27-2020, 11:42 AM - Forum: PostmarketOS on PinePhone
- Replies (1)
|
|
Now that I have recruited some help with Mobain from @AmazingNutria I am considering beginning some daily manual QA on this OS.
First I have a few questions:
- Is this OS ready to even consider for a Release Candidate yet?
- Has anyone seen any progress on this OS since they started tinkering with it?
- How many features are available on the dev builds?
- Is this something people might look forward to?
Let me know your thoughts.
|
|
|
|
| My Daily QA - 2020-08-27 |
|
Posted by: plainenough - 08-27-2020, 11:31 AM - Forum: UBPorts on PinePhone
- Replies (1)
|
|
Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating, SIM installation, Wifi Configuration, and Power Cycling the devices.
Results: ubports/2020-08-27-TMobile
ubports/2020-08-27-Verizon
Conclusion: This OS is not ready for the pinephone to become a daily driver.
Notes: Inbound texting still not working on Verizon. Issues with outbound 3G texts in TMobile. I have noticed that I am unable to change the MP rating of the camera. Since this feature is so new I don't think it is appropriate to introduce a test case around this. Didn't even attempt MMS. Speakerphone still not an option.
Known Issues: 4G calling is broken.
Locking issues.
If you want to help contribute I suggest logging into gitlab and commenting on these issues. Also, ubports has forums that they read from separately. I find them hard to navigate personally. But you have the information to help influence a change. That is all.
|
|
|
|
|
