PS3 Bluetooth generic controller unpairs after 10 minutes playing

[countertop]

Hi all.

I am using Recalbox 7.2.2 over my RPI4. As I understand, my generic PS3 controller is using BT 4.0 as the rpi4 is doing.

I am using "Bluez" driver on the recalbox.config as this is the one working on the controllers. ERT is enabled as well (I don't get what the purpose of this parameter is).

I am playing fine with all the games but the controller suddenly freezes and it doesn't work no longer until a hard reset on the system. Ther is no message like "controller disconnected" or something when one of the controllers goes out of battery.

I alwasy play with fully charged controllers, but they keep unpairing from time to time without any notice.

Any suggestion? Anyone with the same issue? Any clue to proceed?

Thanks

[Zing]

@countertop

• Reset the controller (there is a small button for this on the joystick).
• In the Recalbox control settings, go to "forget all controls" (or whatever the correct English term is).
• I remapped the joystick
• Test again

If does not work:

• Test with other drivers
• Test change the ert option

[countertop]

@zing Thanks for your help first of all.

I did reset controllers and still the same issue from time to time (its happening without any trackable time).

What is the ERTM option for?

I did try all the drivers, but none seems to work perfect but bluez.

Is there anyway to activate log file so I can track any error on the Bluetooth behavior?

If I use dmesg I don't get the driver from the controller. I can't know if other drivers will work, but only bluez seems to do anything.

Thanks!

PD: These controllers were working perfectly until update to 7.2

[Zing]

@countertop said in PS3 Bluetooth generic controller unpairs after 10 minutes playing:

What is the ERTM option for?

ERTM = Enhanced Re-Transmission Mode, this mode is an update to the original retransmission mode and gives improved performance. (Sorry, I'm not a developer and I don't have the technical knowledge to go into more than that, do some research if you want more detailed information.)

Is there anyway to activate log file so I can track any error on the Bluetooth behavior?

Logs can be found on /recalbox/share/system/logs

PD: These controllers were working perfectly until update to 7.2

See if this helps:
https://forum.recalbox.com/topic/24453/how-to-delete-or-clean-reset-all-found-controllers

[countertop]

@zing Thanks a lot for your help, will try everything.

On the other hand, I am also trying to optimize N64 and PSX.

Do you know if overcloking does it and its safe with all the other games? Any other suggestion for N64 lag or PSX better graphics?

Thanks.

[Zing]

@countertop I don't have an Rpi4 and I can't give details about it.
Overclocking is a procedure that should always be done with caution and with a good cooling system, as it pushes the hardware beyond the safety limit.

I can say that many users overclock and like the performance, but, as it is a relatively "dangerous" procedure because, when poorly executed/not taken the proper precautions that can damage the hardware, I cannot be held responsible for this procedure, this is at the discretion of the user.

If you want to overclock as most people do, and take the necessary steps such as using heat sinks and fans, you might find it useful to check this topic:
https://forum.recalbox.com/topic/21649/overclocking-pi4-with-recalbox-7

Many users report significant improvements on the N64 and Dreamcast (which are the heaviest consoles to emulate), so yes, overall performance improves.

[countertop]

@zing Thanks mate, it seems that ERTM=0 did marvel on the Bluetooth issue.

I will open up another thread realted to N64 emulator.

Thanks!