Amazon Luna controller does not work with bluetooth

[expertblink]

Hi all,

I'm trying to get my Amazon Luna controller to work with Lakka over bluetooth. The controller is connected, but nothing happens when setting up the controller as an input device, keys aren't recognized.

Lakka:~ # uname -r
6.1.84
Lakka:~ # lsmod | grep luna
Lakka:~ # modprobe hid-amazon-luna
modprobe: FATAL: Module hid-amazon-luna not found in directory /lib/modules/6.1.84

Is there a way to get this to work, or will this be supported in the future? Thanks.

[gouchi]

This controller should be supported since Linux kernel version 5.1.3 per this commit. And we enabled xpad module.

Can you provide some log ?

Thank you.

[ShigeakiAsai]

I got this controller today.
Although I was able to connect using the RPi4's built-in BT, I was unable to operate it on Lakka-v6.x(2025-05-09 nightly) retroarch.

I could get log.

Input device logs
lsusb lists all devices attached via USB
dmesg displays all messages from the kernel ring buffer which typically is holding the messages generated by Lakka’s Linux kernel from the boot process. The dmesg log lists each hardware device that the kernel detected along with information on how the device was configured by the system.

lsusb (I also connected wireless KB and mouse via USB receiver, no other GAME controller)

###########################################
# Lakka - The DIY retro emulation console #
# ...... visit http://www.lakka.tv ...... #
###########################################

Lakka (official): devel-20250509145159-efa398f (RPi4.aarch64)
Lakka:~ # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 003: ID 25a7:fa61 Areson Technology Corp Elecom Co., Ltd MR-K013 Multicard Reader
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lakka:~ # lsusb -t
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 004: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 004: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 5000M
Lakka:~ #

dmesg

dmesg-RPi4-Lakka-v6_x.log

and more

systemctl status bluetooth

systemctl_status_bluetooth.log

hciconfig

Lakka:~ # hciconfig
hci0:   Type: Primary  Bus: UART
        BD Address: 2C:CF:67:35:30:5F  ACL MTU: 1021:8  SCO MTU: 64:1
        UP RUNNING
        RX bytes:6253 acl:32 sco:0 events:470 errors:0
        TX bytes:66674 acl:34 sco:0 commands:409 errors:0

Lakka:~ #

Please let me what to do.

Thanks
ASAI, Shigeaki

[ShigeakiAsai]

More 1 info.
This is caused not only internal BT but also external USB BT dongle.

dtoverlay=disable-bt (disable internal BT) in /flash/config.txt

# SPDX-License-Identifier: GPL-2.0-or-later
# Copyright (C) 2009-2014 Stephan Raue (stephan@openelec.tv)
# Copyright (C) 2016-present Team LibreELEC (https://libreelec.tv)
################################################################################
# Bootloader configuration
# config.txt version v1 (do not remove or change this line!)
################################################################################
# For more options and information see
# http://rpf.io/configtxt
################################################################################

# Default GPU memory split, 76MB are needed for H264 decoder
gpu_mem=76

# Don't send initial active source message.
# Avoids bringing CEC (enabled TV) out of standby and channel switch when
# rebooting.
hdmi_ignore_cec_init=1

# Enable 4kp60 output on the first HDMI connector
hdmi_enable_4kp60=1

[all]
################################################################################
# Use distroconfig-composite.txt instead of distroconfig.txt to enable
# composite video output.
# The composite video mode needs to be configured in cmdline.txt:
# For PAL add: video=Composite-1:720x576@50ie
# For NTSC add: video=Composite-1:720x480@60ie
################################################################################
include distroconfig.txt
#include distroconfig-composite.txt

# uncomment to enable analog audio output
#dtparam=audio=on
#audio_pwm_mode=1

# uncomment to enable infrared remote receiver connected to GPIO 18
#dtoverlay=gpio-ir,gpio_pin=18

dtoverlay=disable-bt

force_turbo=0
Lakka:~ #

and use external USB BT dongle tp-link UB4A

###########################################
# Lakka - The DIY retro emulation console #
# ...... visit http://www.lakka.tv ...... #
###########################################

Lakka (official): devel-20250509145159-efa398f (RPi4.aarch64)
Lakka:~ # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 003: ID 25a7:fa61 Areson Technology Corp Elecom Co., Ltd MR-K013 Multicard Reader
Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lakka:~ # lsusb -t
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 001: Dev 005, If 0, Class=Wireless, Driver=btusb, 12M
        |__ Port 001: Dev 005, If 1, Class=Wireless, Driver=btusb, 12M
        |__ Port 004: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 004: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 5000M
Lakka:~ #

[gouchi]

@ShigeakiAsai Thank you for the detailed report. Did you try to check if it is working with USB cable ? If it works via USB, the issue might be specifically Bluetooth.

Thank you.

[ShigeakiAsai]

I tested it connected with USB cable.

• No joypad cfg: don't work, it can't control, but connection is detected.
  

• With joypad cfg: It is working.
  Amazon Game Controller.cfg.txt
  

• After add joypad cfg, tried to BT connect.
  don't work, it can't control, connection isn't detected.

Note:

According to https://www.lakka.tv/doc/Contributing-your-joypad-config/
I will contribute "Amazon Game Controller.cfg" into retroarch-joypad-autoconfig later.
-> done. libretro/retroarch-joypad-autoconfig#1287

[ShigeakiAsai]

additional info. (just information sorry)

I tried Official Raspberry Pi OS + sudo apt install xboxdrv + sudo apt install joystick

• Release date | 4 Dec 2025
• System | 64-bit
• Kernel version | 6.12
• Debian version | 13 (trixie)

This controller is able to connect via BT and jstest works fine.

pi@raspberrypi:~ $ dmesg | grep -i bluetooth
[    5.878229] Bluetooth: Core ver 2.22
[    5.878273] NET: Registered PF_BLUETOOTH protocol family
[    5.878277] Bluetooth: HCI device and connection manager initialized
[    5.878290] Bluetooth: HCI socket layer initialized
[    5.880425] Bluetooth: L2CAP socket layer initialized
[    5.880453] Bluetooth: SCO socket layer initialized
[    6.109258] Bluetooth: HCI UART driver ver 2.3
[    6.109280] Bluetooth: HCI UART protocol H4 registered
[    6.109341] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    6.109625] Bluetooth: HCI UART protocol Broadcom registered
[    6.481235] Bluetooth: hci0: BCM: chip id 107
[    6.481555] Bluetooth: hci0: BCM: features 0x2f
[    6.482804] Bluetooth: hci0: BCM4345C0
[    6.482821] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0000
[    6.485161] Bluetooth: hci0: BCM4345C0 'brcm/BCM4345C0.raspberrypi,4-model-b.hcd' Patch
[    7.212127] Bluetooth: hci0: BCM: features 0x2f
[    7.213452] Bluetooth: hci0: BCM43455 37.4MHz Raspberry Pi 3+-0190
[    7.213462] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0382
[    8.607253] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    8.607270] Bluetooth: BNEP filters: protocol multicast
[    8.607281] Bluetooth: BNEP socket layer initialized
[    8.613723] Bluetooth: MGMT ver 1.23
[    9.042717] Bluetooth: RFCOMM TTY layer initialized
[    9.042743] Bluetooth: RFCOMM socket layer initialized
[    9.042762] Bluetooth: RFCOMM ver 1.11
[   71.263012] hid-generic 0005:0171:0419.0003: input,hidraw2: BLUETOOTH HID v1.00 Gamepad [Luna Gamepad] on 2c:cf:67:35:30:5f
pi@raspberrypi:~ $ bluetoothctl -v
bluetoothctl: 5.82
pi@raspberrypi:~ $

[gouchi]

Thank you that is great news !

Will it be possible to make a test with Lakka 6.1 instead of Lakka 6.x as it seems Lakka 6.1 is using bluez version 5.83 instead of 5.75 ? Lakka 6.1 is using also kernel version 6.12.61 not 6.6.78.

[ShigeakiAsai]

It was same behavior in Lakka-v6.1, the version of bluez is 5.83.

###########################################
# Lakka - The DIY retro emulation console #
# ...... visit http://www.lakka.tv ...... #
###########################################

Lakka (community): devel-20260107113428-bee1753 (RPi4.aarch64)
Lakka:~ # bluetoothctl -v
bluetoothctl: 5.83
Lakka:~ # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 003: ID 25a7:fa61 Areson Technology Corp Elecom Co., Ltd MR-K013 Multicard Reader
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lakka:~ # lsusb -t
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 004: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 004: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 5000M
Lakka:~ #

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; preset: disabled)
     Active: active (running) since Thu 2025-06-26 17:44:16 JST; 6 months 17 days ago
   Main PID: 960 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 8763)
        CPU: 47ms
     CGroup: /system.slice/bluetooth.service
             mq960 /usr/lib/bluetooth/bluetoothd

Jun 26 17:44:16 Lakka bluetoothd[960]: Bluetooth daemon 5.83
Jun 26 17:44:16 Lakka bluetoothd[960]: Starting SDP server
Jun 26 17:44:16 Lakka systemd[1]: Started bluetooth.service.
Jun 26 17:44:16 Lakka bluetoothd[960]: profiles/network/bnep.c:bnep_init() kernel lacks bnep-protocol support
Jun 26 17:44:16 Lakka bluetoothd[960]: Bluetooth management interface 1.23 initialized
Jun 26 17:44:16 Lakka bluetoothd[960]: Battery Provider Manager created
Jun 26 17:44:16 Lakka bluetoothd[960]: Failed to set privacy: Rejected (0x0b)
Jan 12 22:55:35 Lakka bluetoothd[960]: src/service.c:service_accept() input-hog profile accept failed for 7C:63:05:8E:FC:0E
Jan 12 22:55:35 Lakka bluetoothd[960]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Attribute requires authentication before read/write
Jan 12 22:55:36 Lakka bluetoothd[960]: src/service.c:service_accept() input-hog profile accept failed for 7C:63:05:8E:FC:0E

~

[gouchi]

I am confused as we are using same kernel version and bluetooth stack.

I am not sure it will fix it using this comment as the mac address does not seem to be your gamepad controller.

Also there might be differences in bluetooth config files ?

[ShigeakiAsai]

I'v keep investigation this.

I am not sure it will fix it using this bluez/bluez#531 (comment) as the mac address does not seem to be your gamepad controller.

-> This method was not effective for this I confirmed.

Also there might be differences in bluetooth config files ?

-> Not confirm this yet. I will try tomorrow or later!

My investigation progress:

• RPi OS bluetooth debug log shows
  "bluetoothd: src/device.c:device_attach_att() Elevating security level since LTK is available"
  But Lakka bluetooth debug log have no this.
• It seems Lakka bluetooth recognizes device but can't read/write data by authentication reason maybe
  "bluetoothd: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Attribute requires authentication before read/write"

I will trace this point using debug build.

LakkaV61-journalctl-log-bluetooth-after-connect.log

RasPiOS-journalctl-log-bluetooth-after-connect.log