Bluetooth pairing not persistent between reboots

nuwonda

tried with build from 15th and 17th April. Bluetooth pairings don't get saved between reboots or restarts, so need to pair controllers each time you start batocera.

joinski

nuwonda

which controllers?

nuwonda

have only tried with ps3 controllers
, can try with some 8bitdo ones too

hmm apparently ps3 controller doesn"t get saved even when connected with cable.

[deleted]

@nuwonda your filesystem is broken

nuwonda

Hmm possible, I can do a full reinstall ...

nuwonda

same after complete reinstall, ps3 controllers need to be reconfigured each time you reboot, whether they are connected via cable or via bluetooth. 8bitdo sn30 pro bluetooth profile stays. maybe that's WAI, the ps3 controller is recognized after I press the PS button,

also, the build from the 17th did not connect to WIFI even after putting credentials, same with the build from 18th. I had wifi with the build from the 15th.

since i did a complete reinstall (with etcher this time) i think we can rule out a broken file system.

I installed build from 18th with PINN along with another OS on a second partition (manajro) and since I configure WIFI through PINN it was working during install and also was working in Batocera afterwards. If I only install Batocera via Etcher as single OS on the 128GB SD, Wifi is not working.

[deleted]

@nuwonda Afaik the internal installer does not expand the partition properly (only RPi4!)
So a fix would be to edit batocera-boot.conf and disable file expansion. And do the resize manually. It seems that some data could not be properly written to /userdata. Because as you said with PINN it works :)

@nadenislamarre What do you think?

nuwonda

that may be it.

here's the PINN jsons for partition setup (PINN uses the boot tarball) just in case

https://github.com/matthuisman/pinn-os/blob/master/batocera_RPi4/partitions.json
https://github.com/matthuisman/pinn-os/blob/master/batocera_RPi4/partition_setup.sh

Also after doing an internal update from Batocera and rebooting, the screen stays black each time, I think this may be related as well.

In PINN when doing a filesystem check afterwards it says:
fatCP437: Invalid argument
for the batocera_RPi4 partition

the Share partition checks out fine.

It can be fixed in PINN by applying the partition sh again and then batocera will boot once more, but then again, it may not really fix it properly.

[deleted]

Also after doing an internal update from Batocera and rebooting, the screen stays black each time, I think this may be related as well.

How long do you wait? The copy of the partition files can take sometimes several minutes but ES will show up in the end. If you switch off during the init phase your filesystem is broken. You can delete all content of userdata and then the files will be copied again (this takes a while)

nuwonda

I left it alone for about 20 mins one time before pulling the cord. In general, may be best to put up a simple message if possible to avoid an all black screen.

I also have the problem when using winscp that the connection drops after transferring some data at random and i can't reconnect afterwards. i had that problem with all versions so far though. although this time, the wifi goes down on the rpi4 in batocera and i cannot reconnect unless I reboot and then I even have to re-enter the Wifi info in PINN. maybe I got a borked RPI4, I have a second one to test with, will see if it has the same issues.

edit: as others stated, ssh transfer via wifi is spotty and connection goes down frequently. at least its not my raspberry.