I recently bought a no-brand foldable Bluetooth keyboard (picture) for use with my PinePhone (running Mobian). The basic keys work fine, and I got deadkeys/lv3/compose to work by firing up dconf-editor and editing /org/gnome/desktop/input-sources/sources and /org/gnome/desktop/input-sources/xkb-options.

Unfortunately, though, some of the special keys don't work as expected. Fn+[top row keys] always produces the keysym of the "upper" blue function instead of the "lower" one, e.g. Fn+` produces XF86HomePage instead of Escape, and similar for the other top-row keys. wev reveals that Fn+` produces keycode 180, and indeed, in the output of xkbcomp, I see:

I ordered an upgrade board to swap into a UBPorts edition I have. Swap was successful and the phone could detect all hardware when using factory test but I experienced odd behavior when I put a SIM in it.

The phone would detect the SIM was inserted and even show signal strength and type ("bar meter" and 2G/3G/4G notifications in top left of phosh) but the modem would never register with the network. Specifically the modem details would show signal type as "lte" and provide a signal strength metric but the network status would be "unregistered."

I swapped the 2GB ram board back in and the phone works now...

Really at a loss here, has anyone ever seen this behavior? Was I supposed to do something with the modem after swapping the board in? I was so close to USB-C!!! 

Some things:

• No, the SIM doesn't have a pin
  
• Yes, the SIM is activated
  
• SIM is an AT&T BYOD straight talk
  

would it be possible to use my old Nokia n800 to connect to the pinetime 64

It is not physically damaged in anyway. I totasted the set up. It will no longer boot via eMMc or USB mini drive flash card. I tried to reflash the internal eMMC and placed the boot in the second spot. Then tried deleting the mistake. You could still boot from the flashdrive a week ago but I let the computer sit for a week turned off. If anything happens now I get either a blinking cursor in the upper left hand screen or nothing but a red light and them it dies. Sometimes it goes to green and then dies. Sometimes no light at all. I am totally still a noob at this after one year. I totally messed up before I tried to reflash the eMMC.  Any advice? 

Hello !

I have a V3 Rock64. No PSU or HDMI issues : i have XU4, RPI-1, RPI-2, BPI-M5 without problems.

- rock64-debian-mrfixit-190531.img.xz >> SD Card  :  it lags very much, when moving windows with LXDE.
- rock64-debian-mrfixit-190531.img.xz >> mmc Card (Foresee 16 Go) : i can't start X, xorg doesn't find /usr/lib/dri/rockchip_dri.so. Can't find this file on my disk.

- Armbian >> black lines on screen when moving windows in XFCE.
- Armbian >> dashboard moving up an down quickly when i move some windows (ex : PCManFM, but not galculator (?))

- Slackware XFCE : works great, but no dependencies supported by this OS (?).

- Ubuntu : i don't want.

- FreeBSD .img for Rock64 doesn't boot.

What distros work on your V3 board, please ?

Hello.

The Quartz64 model A I purchased should be here in a few days. I would like to connect a JTAG/SWD debugger to it. 

Where could I find documentation where this is described? In the schematics for the board, I see mention of JTAG in few places, but I am not sure where physically the pins are on the board. 

Can anyone provide specifics? Also, aside from the RK3566 datasheet are there any reference manuals/guides for the board? Where can I find these? Also, the same for the Quartz64.

For any users of Standard Notes (https://standardnotes.org), a developer is looking for some help testing ARM builds of the desktop app: https://github.com/standardnotes/forum/i...-887475953

I ordered my device around the 26th. Should I expect to see it during this batch? I've yet to receive a tracing number or anything even remotely resembling an update on the order.

Thanks shelldweller,
this board has been added to the assembly slarm64_build_kit

kernel
slarm64-current-aarch64-server-sopine-5.13.5-build-20210727.img.zst
slarm64-current-aarch64-server-sopine-5.13.5-build-20210727.img.zst.sha256

Hi, I can see usb device in the manage disks utility, but I can't access the device through dolphin. I can manually mount & access through console. 
Has anyone had this problem? Any suggestions appreciated. Thanks, straightwalker
SOLVED
more or less. The Disks utility recognizes a hot plugged usb and allows mounting and/or unmounting and offers options that can be edited.
If the drive is in when the PBP is booted, the Disk utility will mount it in /ROOT/mnt/usbname. If the drive is put in after the boot, the Disk utility mounts it in /ROOT/media/usrname/usbname (or maybe it has a "/run" in that path, I don't remember). In any case, Disks lists the path to the mounted usb drive, and you can access the contents using Dolphin (by beginning the path with ROOT).
There is probably a way to automate this, or make it less manual, but I couldn't figure it out. At least, you can access any drive you put in. If you are using the same usb drive each time (and you get the settings right), the process is automatic. It seems that you have to set up options for each new drive that you use.
I'm sure others can explain better ways. But it does work, even though an added device never appears on the Dolphin sidebar.