[GPi Case] Recalbox 6.1 Beta 4 (pre-release) - New Public Beta!

[Bernie-ran]

All was working fine then I spotted an update request.
I updated... and I’m back to 6.0.

Aoutch...

[paradadf]

@bernie-ran didn’t you read the warning?
UNTIL THE FINAL 6.1 IS AVAILABLE, DO NOT UPDATE YOUR BETA VERSION!

[Bernie-ran]

@paradadf, no I didn’t, but I also didn’t blame anybody so please no need to patronise.

But if you want to start a discussion, in my opinion UI and UX have to adapt to human and not the contrary.
It is well know in 2019 that people don't read more than 3 to 5 words before moving next line.

If it can improve communication, the warning should have said;
DON’T USE THE INTERNAL UPDATE option until the final 6.1 is available

Good luck with 6.1 final you are doing a great job.

PS : Is it the place to post issues and logs ?

[paradadf]

@bernie-ran I didn’t try to patronise anyone and I certainly didn’t want to start a discussion. But I’ll tell you something... no one on the team has english as his native tongue, so you can’t expect every formulation to be perfect. It is more than understandable though, and if someone takes the time to write something (on the first post, which anyone should read, always), the least I can expect is for someone else that tries to use the stuff there is to read it.
And yes, this is the place for anything related to the beta.
Have a good one.

[Bernie-ran]

@paradadf salut and all good, english is not my mother tongue but I have a little knowledge in UI/UX.
As guideline it is good practice to put the important meaning of a message in the 5 first words.

Par exemple: "Merci et bravo aux benevoles pour tout votre travail sur Recalbox".

[Bernie-ran]

Since I upgraded to beta 4 my connection (Wifi) is pretty instable.

I’ve setup Network settings and connect properly.
I can see the RECALBOXGPI on my Windows Network, I can connect FTPS, I can access to the shell through SSH. I start Skraper and at some point the connection turn to be instable and cut-off. Windows says there is problem (Diagnose?) or I got a blue spinning wheel, etc.

I had to re-run several time Skraper for the same system to have all the games scrapped.
It didn’t happen with Beta3.

My logs (/var/log/messages):
1 01:16:52 RECALBOX daemon.info connmand[210]: wlan0 {RX} 90909 packets 38625550 bytes Jan 1 01:16:52 RECALBOX daemon.info connmand[210]: wlan0 {TX} 131383 packets 185170238 bytes Jan 1 01:16:52 RECALBOX daemon.info connmand[210]: wlan0 {update} flags 36867 <UP> Jan 1 01:16:52 RECALBOX daemon.info connmand[210]: wlan0 {newlink} index 2 address B8:27:EB:BC:85:15 mtu 1500 Jan 1 01:16:52 RECALBOX daemon.info connmand[210]: wlan0 {newlink} index 2 operstate 2 <DOWN> Jan 1 02:16:52 RECALBOX daemon.info avahi-daemon[698]: Withdrawing address record for 10.0.0.107 on wlan0. Jan 1 02:16:52 RECALBOX daemon.info avahi-daemon[698]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.0.0.107. Jan 1 02:16:54 RECALBOX daemon.info ntpd[691]: Deleting interface #3 wlan0, 10.0.0.107#123, interface stats: received=4, sent=68, dropped=0, active_time=1000 secs Jan 1 02:16:54 RECALBOX daemon.info ntpd[691]: 212.26.18.41 local addr 10.0.0.107 -> <null> Jan 1 02:16:54 RECALBOX daemon.info ntpd[691]: 185.23.154.26 local addr 10.0.0.107 -> <null> Jan 1 02:16:54 RECALBOX daemon.info ntpd[691]: 118.189.138.5 local addr 10.0.0.107 -> <null> Jan 1 02:16:54 RECALBOX daemon.info ntpd[691]: 207.148.72.47 local addr 10.0.0.107 -> <null> Jan 1 02:16:54 RECALBOX daemon.info ntpd[691]: Deleting interface #5 wlan0, fe80::ba27:ebff:febc:8515%2#123, interface stats: received=0, sent=0, dropped=0, active_time=1000 secs Jan 1 02:16:54 RECALBOX daemon.info avahi-daemon[698]: Interface wlan0.IPv4 no longer relevant for mDNS. Jan 1 01:16:54 RECALBOX user.err kernel: [ 1016.482984] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110

[Tormentor667]

How do the rewind/save state functions work without a hotkey?

[Bkg2k]

Final release here: http://archive.recalbox.com