gh-streetpea/chiaki-ng
Watch
1
0
Fork
You've already forked chiaki-ng
 0
Code Issues 37 Pull requests 21 Releases Activity

Remote play on console has crashed #38

New issue
Closed
opened 2023-01-18 00:53:52 -06:00 by khalara84 · 40 comments
khalara84 commented 2023-01-18 00:53:52 -06:00 (Migrated from github.com)

Was using chiaki4deck since Christmas, and just a day or two ago it starts giving me this error when trying to connect to my ps5. I haven't seen anyone else talking about the issue, so I thought I'd see if there was anything up here. I've tried uninstalling it from the deck, restarting the ps5, router, and pc. I hope I can get this sorted out!

EDIT
Okay, so I tested remote play from my PC with the official app and it worked just fine. Went back to my steam deck and chiaki worked just fine. No idea what is goin on with that.

Was using chiaki4deck since Christmas, and just a day or two ago it starts giving me this error when trying to connect to my ps5. I haven't seen anyone else talking about the issue, so I thought I'd see if there was anything up here. I've tried uninstalling it from the deck, restarting the ps5, router, and pc. I hope I can get this sorted out! *EDIT* Okay, so I tested remote play from my PC with the official app and it worked just fine. Went back to my steam deck and chiaki worked just fine. No idea what is goin on with that.
streetpea commented 2023-01-18 14:30:34 -06:00 (Migrated from github.com)

@jbaiter have you seen anything like / have an idea what would cause this from reverse engineering the protocol to support haptics?

@jbaiter have you seen anything like / have an idea what would cause this from reverse engineering the protocol to support haptics?
jbaiter commented 2023-01-18 14:56:42 -06:00 (Migrated from github.com)

I've been getting this two or three times when reversing the haptics protocol, but I could never reliably reproduce it. Putting the console manually into rest mode and then powering it on again always fixed it for me, but this is ofc not always possible.
This is probably going to be pretty hard to debug without a reliable way of reproducing it 😬

@khalara84 If you can find a way to reliably trigger this crash, could you maybe enable debug logging before triggering another crash and upload that somewhere? Maybe we can find something in there that gives us a clue to what is happening.

I've been getting this two or three times when reversing the haptics protocol, but I could never reliably reproduce it. Putting the console manually into rest mode and then powering it on again always fixed it for me, but this is ofc not always possible. This is probably going to be pretty hard to debug without a reliable way of reproducing it 😬 @khalara84 If you can find a way to reliably trigger this crash, could you maybe enable debug logging before triggering another crash and upload that somewhere? Maybe we can find something in there that gives us a clue to what is happening.
cgarst commented 2023-01-24 19:09:16 -06:00 (Migrated from github.com)

I'm getting this error a ton this week with Chiaki4deck too. It seems that once I get it with Chiaki4deck, I'm unable to connect with official iOS app until the PS5 rests. Otherwise, the iOS app is still working.

I'm getting this error a ton this week with Chiaki4deck too. It seems that once I get it with Chiaki4deck, I'm unable to connect with official iOS app until the PS5 rests. Otherwise, the iOS app is still working.
streetpea commented 2023-01-24 19:35:42 -06:00 (Migrated from github.com)

@cgarst you have described 2 things

  1. Launching chiaki4deck is causing remote play on the console to crash
  2. Once the remote play server on the console crashes, remote play can’t be used until you reset the console

Afaik (2) is unavoidable bc once the remote play server on the console crashes, it doesn’t reset automatically. Chiaki, the official PlayStation app, etc. are all clients for that server so if the server isn’t working they are sol.

Based on the reports in this issue, the remote play server crashing in the 1st place (1) seems to be due to an issue with Chiaki (most likely related to the upgrades to add haptics in chiaki/chiaki4deck).

Unfortunately, I am not able to currently replicate the issue. @cgarst since you can semi-reliably replicate the issue it would be very helpful if you could enable debug logging (clicking the check mark in the gui) and post a log of when the remote play server crashes (logs should be in the directory: /home/deck/.var/app/re.chiaki.Chiaki4deck/data/Chiaki/Chiaki/log). This would need to be when the crash happens instead of after the crash when you can’t connect. This would help us figure out the cause of the issue and fix it.

@cgarst you have described 2 things 1. Launching chiaki4deck is causing remote play on the console to crash 2. Once the remote play server on the console crashes, remote play can’t be used until you reset the console Afaik (2) is unavoidable bc once the remote play server on the console crashes, it doesn’t reset automatically. Chiaki, the official PlayStation app, etc. are all clients for that server so if the server isn’t working they are sol. Based on the reports in this issue, the remote play server crashing in the 1st place (1) seems to be due to an issue with Chiaki (most likely related to the upgrades to add haptics in chiaki/chiaki4deck). Unfortunately, I am not able to currently replicate the issue. @cgarst since you can semi-reliably replicate the issue it would be very helpful if you could enable debug logging (clicking the check mark in the gui) and post a log of when the remote play server crashes (logs should be in the directory: `/home/deck/.var/app/re.chiaki.Chiaki4deck/data/Chiaki/Chiaki/log`). This would need to be when the crash happens instead of after the crash when you can’t connect. This would help us figure out the cause of the issue and fix it.
cgarst commented 2023-01-24 19:53:43 -06:00 (Migrated from github.com)

Naturally I turned on logging after hours of crashing the server and now it's worked several times in a row haha.

I'll keep this on and watch for it.

Naturally I turned on logging after hours of crashing the server and now it's worked several times in a row haha. I'll keep this on and watch for it.
👍 1
khalara84 commented 2023-01-29 01:00:50 -06:00 (Migrated from github.com)

chiaki_session_2023-01-29_01-53-14-121121.log

[chiaki_session_2023-01-29_01-53-14-121121.log](https://github.com/streetpea/chiaki4deck/files/10529217/chiaki_session_2023-01-29_01-53-14-121121.log)
khalara84 commented 2023-01-29 01:02:44 -06:00 (Migrated from github.com)

Not sure if my log will be any help. Sorry if it isn't. I hope this can be fixed!

Not sure if my log will be any help. Sorry if it isn't. I hope this can be fixed!
jbaiter commented 2023-01-29 05:04:58 -06:00 (Migrated from github.com)

@khalara84

  • Did you experience any crashes in the session before the one in which you couldn't connect due to the "Remote Play has crashed" error?
  • Can you try if starting the session with the official PS Remote Play and check if it also fails with an error?
  • Does putting the PS5 into rest mode and then waking it up again fix the issue for you?
  • When you restart the PS5 and try to connect with Chiaki again, do you still get the error?
  • If the above is the case, can you enable debug logging in the settings, restart your PS5, then connect with Chiaki and upload the resulting log somewhere in case it crashes again?
@khalara84 - Did you experience any crashes in the session before the one in which you couldn't connect due to the "Remote Play has crashed" error? - Can you try if starting the session with the official PS Remote Play and check if it also fails with an error? - Does putting the PS5 into rest mode and then waking it up again fix the issue for you? - When you restart the PS5 and try to connect with Chiaki again, do you still get the error? - If the above is the case, can you enable debug logging in the settings, restart your PS5, then connect with Chiaki and upload the resulting log somewhere in case it crashes again?
khalara84 commented 2023-01-29 18:40:10 -06:00 (Migrated from github.com)

Can you lead me through this process for debug? I only turned on logging and gave the log on what happens when I try to remote play. I'll see about the other conditions later when I can get to it.

Can you lead me through this process for debug? I only turned on logging and gave the log on what happens when I try to remote play. I'll see about the other conditions later when I can get to it.
charsu commented 2023-01-31 03:16:35 -06:00 (Migrated from github.com)

hi , I can confirm the above issue too on my PS5 . it started happening after version 1.2.x + (1.3.x) was released in mid December (including gyro...) .

As far I can tell , it is related to the PS5 automatically going to sleep due to power saving settings and afterwards trying to connect for remote play with chiaki4deck , leads to a brief connection the the PS5 ( eg i can see the screen showing the ps5 background) then an error message and afterwards unable to use remote play on that PS5 with no other client (eg chiaki, chiaki4deck , PS official remote client app , other android apps (probably based on chiaki code) ....) , so in other words it seems to kill the PS5 remote service ...

Important bits :

  • it started mid December with a chiaki4deck update (1.2.x something or 1.3) , initially I thought some other decencies have been updated but now I am more convinced that is the chiaki4deck update
  • my PS5 is completely up to date with latest fw
  • I connect using chiaki4deck and using the launch script that also wakes up the ps5 and logs in with pass code (i have my PS5 account / user password protected)
  • both client and PS5 sit in the same network ( but given the behaviour I am inclined to rule out the network connectivity as it has not changed and when this issue started to happen)
  • have tried to enable/disable the advanced haptics in the menu but same output , so it seem that something is not fully tied to the kill switch ( to be honest have not looked at the code to point out the issue yet )
  • when this crash happens no other remote connection can be established to the PS5 and the only solution is the fully reboot the PS5 , leading to some successful connections until it happens again ...

side note : really great work on getting this done and honestly am impressed by the high standard of setting it up (docs + release + feature implementation and dedication )

hi , I can confirm the above issue too on my PS5 . it started happening after version 1.2.x + (1.3.x) was released in mid December (including gyro...) . As far I can tell , it is related to the PS5 automatically going to sleep due to power saving settings and afterwards trying to connect for remote play with chiaki4deck , leads to a brief connection the the PS5 ( eg i can see the screen showing the ps5 background) then an error message and afterwards unable to use remote play on that PS5 with no other client (eg chiaki, chiaki4deck , PS official remote client app , other android apps (probably based on chiaki code) ....) , so in other words it seems to kill the PS5 remote service ... Important bits : - it started mid December with a chiaki4deck update (1.2.x something or 1.3) , initially I thought some other decencies have been updated but now I am more convinced that is the chiaki4deck update - my PS5 is completely up to date with latest fw - I connect using chiaki4deck and using the launch script that also wakes up the ps5 and logs in with pass code (i have my PS5 account / user password protected) - both client and PS5 sit in the same network ( but given the behaviour I am inclined to rule out the network connectivity as it has not changed and when this issue started to happen) - have tried to enable/disable the advanced haptics in the menu but same output , so it seem that something is not fully tied to the kill switch ( to be honest have not looked at the code to point out the issue yet ) - when this crash happens no other remote connection can be established to the PS5 and the only solution is the fully reboot the PS5 , leading to some successful connections until it happens again ... side note : really great work on getting this done and honestly am impressed by the high standard of setting it up (docs + release + feature implementation and dedication )
streetpea commented 2023-02-03 20:30:08 -06:00 (Migrated from github.com)

@khalara84 would it be possible to attach a log of it working to compare to on your system?

I noticed from the verbose messages that you already have debug logging on in your log and It seems like the only thing that could cause this crash that comes from chiaki itself would be the session request. Since ctrl hasn't even started when remote play crashes on the server (and it is remote play crashing on the PlayStation server not Chiaki) as the session request is rejected because of the crash causing a 403 server error, I don't think anything else can really come into play yet. It may be helpful to see if maybe something is changing in the session request from a good session to a bad session. Normally, the session requests should stay the same given the same connection which is why comparing a good / bad run of yours could make sure there isn't a change.

Note: I let my PS5 go into sleep mode via power saving and woke it up, based on the comment from @charsu but didn't get the crash.

Another possibility could be that something caused a crash and this error is just surfacing information about the crash so the previous session log (right before the crash) would be helpful to rule that out.

@khalara84 would it be possible to attach a log of it working to compare to on your system? I noticed from the verbose messages that you already have debug logging on in your log and It seems like the only thing that could cause this crash that comes from chiaki itself would be the session request. Since ctrl hasn't even started when remote play crashes on the server (and it is remote play crashing on the PlayStation server not Chiaki) as the session request is rejected because of the crash causing a 403 server error, I don't think anything else can really come into play yet. It may be helpful to see if maybe something is changing in the session request from a good session to a bad session. Normally, the session requests should stay the same given the same connection which is why comparing a good / bad run of yours could make sure there isn't a change. Note: I let my PS5 go into sleep mode via power saving and woke it up, based on the comment from @charsu but didn't get the crash. Another possibility could be that something caused a crash and this error is just surfacing information about the crash so the previous session log (right before the crash) would be helpful to rule that out.
streetpea commented 2023-02-05 14:56:11 -06:00 (Migrated from github.com)

@jbaiter I was able to reproduce this locally after many attempts and it does seem like the following:

Another possibility could be that something caused a crash and this error is just surfacing information about the crash so the previous session log (right before the crash) would be helpful to rule that out.
is indeed what is happening.

The crash actually seems to happen here:
chiaki failed log remote play crashes

You can see the connection refused in this log. After this occurs, I keep on getting the remote play has crashed (whether using Chiaki or official PS Remote Play) in any subsequent session attempts similar to the log posted by @khalara84 above. Then, after I put the console to sleep and wake it up (restarting the remote play server which crashed) it works again. Here is a successful log from a successful run after sleeping the console.

From the log it looks like the stream session never successfully launches (crashing instead) in the failed log. However, the stream launch spec is identical so I’m not sure what exactly is causing this (maybe it’s something to do with the ps console itself?) I also noticed in the spec that ps3 and ps4 (see log launchspec code and stream connection code) are mentioned but not ps5 but that’s also the case for the successful launch so it doesn’t explain the intermittent remote play server crash. However, I guess it could result in some fallback code that works sometimes but not other times or there is some sort of threading issue where a mutex isn't being properly locked and so bad/conflicting data is being sent at some point…

Additionally, I get the following error on the PlayStation console itself from the session that ends in session refused (the session I posted the error log titled “chiaki failed log remote play crashes”):

Error Code: CE-108262-9
Date: 2/5/2023 12:42 PM
App: NPXS40102
NAT type: Checking…
System Software: 22.02-06.50.00.10-00.00.00.0.1
Message: Something went wrong with the system software.

In other words, it does seem Chiaki is being disrupted by a failure from the remote play server on the PlayStation itself crashing on launch but I can’t seem to see exactly why it’s failing (Chiaki sending something wrong or a bug in remote play server) from my initial look at the log. I also tried changing the launch spec to be incorrect and that results in a different error saying the server failed to launch with “Nagare could not init” so it doesn’t seem to be that though I guess it could be something that’s allowed but not working properly.

@jbaiter I was able to reproduce this locally after many attempts and it does seem like the following: > Another possibility could be that something caused a crash and this error is just surfacing information about the crash so the previous session log (right before the crash) would be helpful to rule that out. is indeed what is happening. The crash actually seems to happen here: [chiaki failed log remote play crashes](https://github.com/streetpea/chiaki4deck/files/10613763/chiaki_session_2023-02-05_12-42-37-339339.log) You can see the connection refused in this log. After this occurs, I keep on getting the remote play has crashed (whether using Chiaki or official PS Remote Play) in any subsequent session attempts similar to the log posted by @khalara84 above. Then, after I put the console to sleep and wake it up (restarting the remote play server which crashed) it works again. Here is a [successful log](https://github.com/streetpea/chiaki4deck/files/10613787/chiaki_session_2023-02-05_12-49-52-397397.log) from a successful run after sleeping the console. From the log it looks like the stream session never successfully launches (crashing instead) in the failed log. However, the stream launch spec is identical so I’m not sure what exactly is causing this (maybe it’s something to do with the ps console itself?) I also noticed in the spec that ps3 and ps4 (see log [launchspec code](https://github.com/streetpea/chiaki4deck/blob/main/lib/src/launchspec.c) and [stream connection code](https://github.com/streetpea/chiaki4deck/blame/main/lib/src/streamconnection.c)) are mentioned but not ps5 but that’s also the case for the successful launch so it doesn’t explain the intermittent remote play server crash. However, I guess it could result in some fallback code that works sometimes but not other times or there is some sort of threading issue where a mutex isn't being properly locked and so bad/conflicting data is being sent at some point… Additionally, I get the following error on the PlayStation console itself from the session that ends in session refused (the session I posted the error log titled “chiaki failed log remote play crashes”): ``` Error Code: CE-108262-9 Date: 2/5/2023 12:42 PM App: NPXS40102 NAT type: Checking… System Software: 22.02-06.50.00.10-00.00.00.0.1 Message: Something went wrong with the system software. ``` In other words, it does seem Chiaki is being disrupted by a failure from the remote play server on the PlayStation itself crashing on launch but I can’t seem to see exactly why it’s failing (Chiaki sending something wrong or a bug in remote play server) from my initial look at the log. I also tried changing the launch spec to be incorrect and that results in a different error saying the server failed to launch with “Nagare could not init” so it doesn’t seem to be that though I guess it could be something that’s allowed but not working properly.
khalara84 commented 2023-02-07 13:41:13 -06:00 (Migrated from github.com)

This log is from a working session. I hope this helps in some way.
chiaki_session_2023-02-07_14-36-22-311311.log

This log is from a working session. I hope this helps in some way. [chiaki_session_2023-02-07_14-36-22-311311.log](https://github.com/streetpea/chiaki4deck/files/10678792/chiaki_session_2023-02-07_14-36-22-311311.log)
Geier97332 commented 2023-02-11 05:53:15 -06:00 (Migrated from github.com)

I had this problem today every time I used chiaki4deck in my home network.

I put my PS5 in rest mode and used the built in script in game mode to start the remote session. It didn't work. Every time I had to restart the PS5.

Usually I use it to play outside my home network, but at the moment it's not useable because I can't be certain that it does work. When the session crashes I have no opportunity to restart the PS5 outside my home network.

So, please solve this problem. I keep my fingers crossed and keep up your amazing work. You devs are absolute genius.

I had this problem today every time I used chiaki4deck in my home network. I put my PS5 in rest mode and used the built in script in game mode to start the remote session. It didn't work. Every time I had to restart the PS5. Usually I use it to play outside my home network, but at the moment it's not useable because I can't be certain that it does work. When the session crashes I have no opportunity to restart the PS5 outside my home network. So, please solve this problem. I keep my fingers crossed and keep up your amazing work. You devs are absolute genius.
streetpea commented 2023-02-12 15:42:19 -06:00 (Migrated from github.com)

@Geier97332 unfortunately based on the information above, the crash is actually happening on the PlayStation 5 itself. Something is triggering this bug on the server, so since we can't update the server directly to patch the bug we have to figure out what is potentially triggering the code path that is leading to the bug. This will likely require some reverse engineering. In general, it seems like the only things that could have caused this are either upgrades to the takion protocol / streamsession made to enable haptics/adaptive triggers or some change to the remote play server itself in a PlayStation firmware update (with the former seeming more likely atm).

As far as a temporary workaround (while waiting for the issue to be fixed) you could use a prior version of chiaki4deck such as v1.2.0 (obviously you will lose any features added for v1.3.0) but things like touchpad support and the automation will work fine (see features added by release here with everything up to 1.2.0 being included in version 1.2.0). If the issue is indeed related to the v1.3.0 changes this will avoid the issue.

In order to do that you can use the following command:

flatpak update --user --commit 45455a2634dd8537741d5b1f4f4d9b154c772018512b2ea397a215956eb42adc re.chiaki.Chiaki4deck

and then mask re.chiaki.Chiaki4deck so you aren't prompted to upgrade back to v1.3.0 in the discover gui with:

flatpak --user mask re.chiaki.Chiaki4deck

As an aside you can see all available commits to cherry pick one with:

flatpak remote-info --log chiaki4deck-origin re.chiaki.Chiaki4deck

The commit I used in the command above is for version 1.2.0. For more info see the flatpak documentation on this.

@Geier97332 unfortunately based on the information above, the crash is actually happening on the PlayStation 5 itself. Something is triggering this bug on the server, so since we can't update the server directly to patch the bug we have to figure out what is potentially triggering the code path that is leading to the bug. This will likely require some reverse engineering. In general, it seems like the only things that could have caused this are either upgrades to the takion protocol / streamsession made to enable haptics/adaptive triggers or some change to the remote play server itself in a PlayStation firmware update (with the former seeming more likely atm). As far as a temporary workaround (while waiting for the issue to be fixed) you could use a prior version of chiaki4deck such as v1.2.0 (obviously you will lose any features added for v1.3.0) but things like touchpad support and the automation will work fine (see features added by release [here](https://streetpea.github.io/chiaki4deck/updates/releases/#120) with everything up to 1.2.0 being included in version 1.2.0). If the issue is indeed related to the v1.3.0 changes this will avoid the issue. In order to do that you can use the following command: ``` flatpak update --user --commit 45455a2634dd8537741d5b1f4f4d9b154c772018512b2ea397a215956eb42adc re.chiaki.Chiaki4deck ``` and then mask `re.chiaki.Chiaki4deck` so you aren't prompted to upgrade back to v1.3.0 in the discover gui with: ``` flatpak --user mask re.chiaki.Chiaki4deck ``` As an aside you can see all available commits to cherry pick one with: ``` flatpak remote-info --log chiaki4deck-origin re.chiaki.Chiaki4deck ``` The commit I used in the command above is for version 1.2.0. For more info see the [flatpak documentation on this](https://docs.flatpak.org/en/latest/tips-and-tricks.html#downgrading).
👍 2
Geier97332 commented 2023-02-12 16:41:33 -06:00 (Migrated from github.com)

Thank you!

Now it's working again, except all the good new stuff of course. 😉

Thank you! Now it's working again, except all the good new stuff of course. 😉
khalara84 commented 2023-02-20 21:51:48 -06:00 (Migrated from github.com)

Every time I try to revert to the older version it just installs the newer version, not sure how to revert to 1.2.0

Every time I try to revert to the older version it just installs the newer version, not sure how to revert to 1.2.0
streetpea commented 2023-02-20 22:53:01 -06:00 (Migrated from github.com)

@khalara84 If you run the first 2 commands above it should work:

flatpak update --user --commit 45455a2634dd8537741d5b1f4f4d9b154c772018512b2ea397a215956eb42adc re.chiaki.Chiaki4deck

And then


flatpak --user mask re.chiaki.Chiaki4deck

(the first will install the older version and the second will hide updates so it doesn’t update to the newer version)

@khalara84 If you run the first 2 commands above it should work: ``` flatpak update --user --commit 45455a2634dd8537741d5b1f4f4d9b154c772018512b2ea397a215956eb42adc re.chiaki.Chiaki4deck ``` And then ``` flatpak --user mask re.chiaki.Chiaki4deck ``` (the first will install the older version and the second will hide updates so it doesn’t update to the newer version)
khalara84 commented 2023-02-20 23:00:15 -06:00 (Migrated from github.com)

When I try those commands, it says
Looking for updates…
error: re.chiaki.Chiaki4deck not installed
I've tried with and without it installed . Sorry for all the trouble!
with it installed I get
Looking for updates…
Nothing to do.

When I try those commands, it says Looking for updates… error: re.chiaki.Chiaki4deck not installed I've tried with and without it installed . Sorry for all the trouble! with it installed I get Looking for updates… Nothing to do.
streetpea commented 2023-02-20 23:11:48 -06:00 (Migrated from github.com)

Please try

flatpak remote-info --log chiaki4deck-origin re.chiaki.Chiaki4deck
Please try ``` flatpak remote-info --log chiaki4deck-origin re.chiaki.Chiaki4deck ```
streetpea commented 2023-02-20 23:18:31 -06:00 (Migrated from github.com)

Also if you have masked it already you will have to unmask with:

flatpak --user  --remove mask re.chiaki.Chiaki4deck

get to the right version and then mask

If it’s currently masked you won’t get updates because updates are masked

Check your version once done with

flatpak info re.chiaki.Chiaki4deck
Also if you have masked it already you will have to unmask with: ``` flatpak --user --remove mask re.chiaki.Chiaki4deck ``` get to the right version and then mask If it’s currently masked you won’t get updates because updates are masked Check your version once done with ``` flatpak info re.chiaki.Chiaki4deck ```
khalara84 commented 2023-02-20 23:27:35 -06:00 (Migrated from github.com)

For some reason, it wouldn't show me the app version in console, but I masked and it shows as 1.2.0 now. Thank you for so much help!

For some reason, it wouldn't show me the app version in console, but I masked and it shows as 1.2.0 now. Thank you for so much help!
👍 1
ApexAftermath commented 2023-03-20 15:00:26 -05:00 (Migrated from github.com)

Not that it helps any, but I seem to be able to get it to consistently work if I put the PS5 back in rest mode manually and bring it back out of rest mode manually. Then I am able to connect. If it has been woken up by Chiaki it does not like it.

Not that it helps any, but I seem to be able to get it to consistently work if I put the PS5 back in rest mode manually and bring it back out of rest mode manually. Then I am able to connect. If it has been woken up by Chiaki it does not like it.
Geier97332 commented 2023-03-26 06:12:44 -05:00 (Migrated from github.com)

Not that it helps any, but I seem to be able to get it to consistently work if I put the PS5 back in rest mode manually and bring it back out of rest mode manually. Then I am able to connect. If it has been woken up by Chiaki it does not like it.

I use Chiaki only if I'm away from home, so this approach isn't convenient.
But thanks for the info!

Edit: Is there a way to only wake up the console with the Steam Deck? Then this approach would be doable.

> Not that it helps any, but I seem to be able to get it to consistently work if I put the PS5 back in rest mode manually and bring it back out of rest mode manually. Then I am able to connect. If it has been woken up by Chiaki it does not like it. I use Chiaki only if I'm away from home, so this approach isn't convenient. But thanks for the info! Edit: Is there a way to only wake up the console with the Steam Deck? Then this approach would be doable.
AxelTerizaki commented 2023-07-12 11:02:44 -05:00 (Migrated from github.com)

Don't know if that'll help b ut I am consistently able to reproduce the issue.

Today I wanted to try out the experimental haptics feature so I checked it. I connected to my console but didn't pay attention if haptics worked (I suppose not or else I'd have noticed, I play FF16 lately.). I then put the console to sleep again and went to do other stuff. Then I tried to get the console out of rest mode via Chiaki and that didn't work but I didn't get the "crashed" message. Only when I tried it again.

Here are my logs.

  • First one I had haptics enabled and ended the session properly
  • Second one I tried to reconnect but it failed with an error message
  • Third one it said "Server has crashed"

Hope that helps. I can reproduce this anytime.

chiaki_logs.tar.gz

Don't know if that'll help b ut I am consistently able to reproduce the issue. Today I wanted to try out the experimental haptics feature so I checked it. I connected to my console but didn't pay attention if haptics worked (I suppose not or else I'd have noticed, I play FF16 lately.). I then put the console to sleep again and went to do other stuff. Then I tried to get the console out of rest mode via Chiaki and that didn't work but I didn't get the "crashed" message. Only when I tried it again. Here are my logs. - First one I had haptics enabled and ended the session properly - Second one I tried to reconnect but it failed with an error message - Third one it said "Server has crashed" Hope that helps. I can reproduce this anytime. [chiaki_logs.tar.gz](https://github.com/streetpea/chiaki4deck/files/12029992/chiaki_logs.tar.gz)
❤️ 2
Sn0wCrack commented 2023-07-21 06:11:35 -05:00 (Migrated from github.com)

This is unrelated to chiaki4deck specifically, but I've been playing around with a build of Chiaki Master with Qt6 on Windows and have faced the same problem when enabling Extended DualSense support.

Pretty always goes the same: send wake up packet, connect, screen stays black for a while then get an unknown error, attempt to connect again and get the message saying remote play has crashed on the console.
Until I restart the console fully I cannot access remote play again, and I can reproduce it 100% of the time.

The main thing I've noticed when DualSense support is enabled are three additional packets are sent over the control protocol from the PS5 back to Chiaki that are not handled:

  • 0x3
    • Only received this packet twice in my tests so far, had the content "80 fc 10 5a" both times
  • 0x16
    • Seems to be the most common, it gets sent a few times with a content of "01 ff", "00 00" and "01 01"
  • 0x41
    • Only received this packet once in my tests, had the content "00 00 00 00 02 01 00 00"

My only assumption is there's some kind of "acknowledgement" packet potentially not being sent to one of these that is directly causing that crash, the 0x16 one seems the most obvious.

Unfortunately out of my wheel house on reversing this sort of stuff, especially with all the layers of encryption in the way, so I've attached my log files from these attempts (some may not be entirely relevant)

chiaki.zip

This is unrelated to chiaki4deck specifically, but I've been playing around with a build of Chiaki Master with Qt6 on Windows and have faced the same problem when enabling Extended DualSense support. Pretty always goes the same: send wake up packet, connect, screen stays black for a while then get an unknown error, attempt to connect again and get the message saying remote play has crashed on the console. Until I restart the console fully I cannot access remote play again, and I can reproduce it 100% of the time. The main thing I've noticed when DualSense support is enabled are three additional packets are sent over the control protocol from the PS5 back to Chiaki that are not handled: - 0x3 - Only received this packet twice in my tests so far, had the content "80 fc 10 5a" both times - 0x16 - Seems to be the most common, it gets sent a few times with a content of "01 ff", "00 00" and "01 01" - 0x41 - Only received this packet once in my tests, had the content "00 00 00 00 02 01 00 00" My only assumption is there's some kind of "acknowledgement" packet potentially not being sent to one of these that is directly causing that crash, the 0x16 one _seems_ the most obvious. Unfortunately out of my wheel house on reversing this sort of stuff, especially with all the layers of encryption in the way, so I've attached my log files from these attempts (some may not be entirely relevant) [chiaki.zip](https://github.com/streetpea/chiaki4deck/files/12122929/chiaki.zip)
❤️ 2
MadHalaster commented 2023-08-26 17:32:48 -05:00 (Migrated from github.com)

Just wanted to confirm that I see the same thing as Sn0wCrack on the PC Build with the DualSense support, 100% of the time.

I found that if I wake up the console, and connect to it first with the official remote play application, then disconnect that one and connect with Chiaki after, it works. If I wake up the console and connect with Chiaki though it crashes.

Just wanted to confirm that I see the same thing as Sn0wCrack on the PC Build with the DualSense support, 100% of the time. I found that if I wake up the console, and connect to it first with the official remote play application, then disconnect that one and connect with Chiaki after, it works. If I wake up the console and connect with Chiaki though it crashes.
streetpea commented 2023-09-21 11:04:06 -05:00 (Migrated from github.com)

@AxelTerizaki do you have a specific method to cause this issue (you mentioned being able to reproduce)? If you do I would like to know it so I can use it to reproduce on my system for testing.

@AxelTerizaki do you have a specific method to cause this issue (you mentioned being able to reproduce)? If you do I would like to know it so I can use it to reproduce on my system for testing.
AxelTerizaki commented 2023-09-21 11:21:13 -05:00 (Migrated from github.com)

@streetpea As mentionned above, on July 12th, this is easy to reproduce :

  • Enable haptics support in the option
  • Start a session.
  • End the session
  • Start another session : this time it crashes with an error message
  • Start a third session : it says "Remote play on console has crashed"

I haven't tried in a while though.

@streetpea As mentionned above, on July 12th, this is easy to reproduce : - Enable haptics support in the option - Start a session. - End the session - Start another session : this time it crashes with an error message - Start a third session : it says "Remote play on console has crashed" I haven't tried in a while though.
streetpea commented 2023-09-21 12:08:42 -05:00 (Migrated from github.com)

@AxelTerizaki oh I saw that but I'm not able to reproduce like that so was wondering if there was something else to it. Since it sounds like there isn't, if you are able to consistently reproduce like that would you be willing to see if a change stopped the issue from occurring? It's hard for me to test this because the issue only occurs for me a very small percentage of the time. For example, while doing testing I launched the client over 100 times and it failed only once with this issue. Thus, if what I did fixed the issue it would be hard to confirm because it's possible the issue is just not occurring yet. Based on what was changed it seems there are only a few things that could be causing this so I would like to test out which one it is if possible. Hence my question about reproducibility.

@AxelTerizaki oh I saw that but I'm not able to reproduce like that so was wondering if there was something else to it. Since it sounds like there isn't, if you are able to consistently reproduce like that would you be willing to see if a change stopped the issue from occurring? It's hard for me to test this because the issue only occurs for me a very small percentage of the time. For example, while doing testing I launched the client over 100 times and it failed only once with this issue. Thus, if what I did fixed the issue it would be hard to confirm because it's possible the issue is just not occurring yet. Based on what was changed it seems there are only a few things that could be causing this so I would like to test out which one it is if possible. Hence my question about reproducibility.
AxelTerizaki commented 2023-09-21 12:20:52 -05:00 (Migrated from github.com)

I'll check that out this weekend, I'm not at my place at the moment (and didn't set up chiaki for real remote play :) )

I'll check that out this weekend, I'm not at my place at the moment (and didn't set up chiaki for *real* remote play :) )
👍 1
SteveMJones commented 2023-12-12 14:19:58 -06:00 (Migrated from github.com)

Can confirm when using the experimental features for haptics it messes up my ps5 remote play service and i need to turn it off on chiaki4deck and restart the ps5 to not crash.

Can confirm when using the experimental features for haptics it messes up my ps5 remote play service and i need to turn it off on chiaki4deck and restart the ps5 to not crash.
TsukikoChan commented 2024-01-05 07:50:18 -06:00 (Migrated from github.com)

Can confirm that this still happens with the experimental features but also mostly for me against my ps4 (ps5 remote play worked ok for me yesterday) - will follow suggestions here of trying without the haptic tickbox (after a ps4 restart) or using an earlier version.

(Latest chiaki4deck against ps4pro and ps5 latest firmwares using steamdeck lcd).

Can confirm that this still happens with the experimental features but also mostly for me against my ps4 (ps5 remote play worked ok for me yesterday) - will follow suggestions here of trying without the haptic tickbox (after a ps4 restart) or using an earlier version. (Latest chiaki4deck against ps4pro and ps5 latest firmwares using steamdeck lcd).
willnix86 commented 2024-01-07 13:35:19 -06:00 (Migrated from github.com)

+1 for @TsukikoChan - same for me

+1 for @TsukikoChan - same for me
r52 commented 2024-01-31 17:48:49 -06:00 (Migrated from github.com)

I just discovered this fork and thread and realized I may have independently investigated this exactly issue on mainline Chiaki desktop a while ago, which culminated in a workaround in github.com/r52/chiaki@1efc98a7ce.

My findings:

  • As stated in the commit's comments, the server crash is characterized by an ack packet received from the server for stream_connection_send_controller_connection that has an invalid GMAC, after which the server on the PS5 immediately crashes
  • The server crash is consistently reproducible when trying to connect to my PS5 over a LAN connection
  • The server crash is NOT consistently reproducible when connecting to my PS5 over the internet or a connection with some appreciable latency
  • Like others in the thread have mentioned, the server crash is no longer reproducible when connecting with the official client once, then using Chiaki
  • The crash was NOT reproducible on a debug build of Chiaki

To add to these findings:

  • stream_connection_send_controller_connection is called immediately after the Big Bang connection exchange is finished
  • I'm not an expert on this stuff so I can't be sure but it seems like Chiaki spins up the encryption threads which produces the GMAC values used in subsequent encrypted packets as part of the Big Bang's finalization process
  • The GMAC value is immediately used in stream_connection_send_controller_connection

Based on these findings, I theorize that the only logical reason as to why the PS5 does not produce a valid GMAC at that point in time in the handshake cycle is if its own encryption threads have not yet finished its initialization.

Since the the PS5 does not signal when it has finished initializing its internal processes, the only way I could think of testing out this theory is by inserting a small delay after Big Bang finalization but before stream_connection_send_controller_connection is called. And to my surprise, it actually works.

I wouldn't know how to go about fixing this 'properly', or if a proper fix is even possible, but with a just small 100ms delay the server crash has no longer been reproducible for me ever since.

Hope this helps

I just discovered this fork and thread and realized I may have independently investigated this exactly issue on mainline Chiaki desktop a while ago, which culminated in a workaround in https://github.com/r52/chiaki/commit/1efc98a7ced4adaf424851e08f10beb6ed26e825. My findings: - As stated in the commit's comments, the server crash is characterized by an ack packet received from the server for `stream_connection_send_controller_connection` that has an invalid GMAC, after which the server on the PS5 immediately crashes - The server crash is consistently reproducible when trying to connect to my PS5 over a LAN connection - The server crash is NOT consistently reproducible when connecting to my PS5 over the internet or a connection with some appreciable latency - Like others in the thread have mentioned, the server crash is no longer reproducible when connecting with the official client once, then using Chiaki - The crash was NOT reproducible on a debug build of Chiaki To add to these findings: - `stream_connection_send_controller_connection` is called immediately after the Big Bang connection exchange is finished - I'm not an expert on this stuff so I can't be sure but it seems like Chiaki spins up the encryption threads which produces the GMAC values used in subsequent encrypted packets as part of the Big Bang's finalization process - The GMAC value is immediately used in `stream_connection_send_controller_connection` Based on these findings, I theorize that the only logical reason as to why the PS5 does not produce a valid GMAC at that point in time in the handshake cycle is if _its own encryption threads have not yet finished its initialization_. Since the the PS5 does not signal when it has finished initializing its internal processes, the only way I could think of testing out this theory is by inserting a small delay after Big Bang finalization but before `stream_connection_send_controller_connection` is called. And to my surprise, it actually works. I wouldn't know how to go about fixing this 'properly', or if a proper fix is even possible, but with a just small 100ms delay the server crash has no longer been reproducible for me ever since. Hope this helps
👍 1 ❤️ 1 🚀 1
streetpea commented 2024-01-31 21:51:10 -06:00 (Migrated from github.com)

@r52 thanks for chiming in. Maybe it will be setup when the bang is received. Right now, we are sending potentially before bang. If we move to streaminfo function like #240 maybe this fixes it? I can't test to make sure because I can't reproduce on my system reliably (I tried directly connecting to ethernet but it didn't work. Maybe you could try?)

@r52 thanks for chiming in. Maybe it will be setup when the bang is received. Right now, we are sending potentially before bang. If we move to streaminfo function like #240 maybe this fixes it? I can't test to make sure because I can't reproduce on my system reliably (I tried directly connecting to ethernet but it didn't work. Maybe you could try?)
r52 commented 2024-01-31 23:38:32 -06:00 (Migrated from github.com)

@streetpea I just tested #240 on a local build and indeed it seems like moving the send to the streaminfo block works perfectly.

As a sanity check I made sure that the 1.6.2 release consistently crashes my PS5 server, and it does.

Looks good to me 👍

@streetpea I just tested #240 on a local build and indeed it seems like moving the send to the streaminfo block works perfectly. As a sanity check I made sure that the 1.6.2 release consistently crashes my PS5 server, and it does. Looks good to me 👍
👍 1
LucyDemooon commented 2024-08-07 12:47:51 -05:00 (Migrated from github.com)

chiaki 2.2 and chiaki-ng 1.8 i get this error every time.

installed the flatpak and appimage on arch linux

`0x80108b15

[2024-08-07 19:34:52:307307] [I] Starting session request for PS5
[2024-08-07 19:34:52:307307] [I] Trying to request session from 192.168.150.150:9295
[2024-08-07 19:34:52:307307] [I] Connected to 192.168.150.150:9295
[2024-08-07 19:34:52:307307] [I] Sending session request
[2024-08-07 19:34:52:307307] [E] Reported Application Reason: 0x80108b15 (Remote Play on Console crashed)
[2024-08-07 19:34:52:307307] [I] Session has quit
[2024-08-07 19:34:53:308308] [I] Starting session request for PS5
[2024-08-07 19:34:53:308308] [I] Trying to request session from 192.168.150.150:9295
[2024-08-07 19:34:53:309309] [I] Connected to 192.168.150.150:9295
[2024-08-07 19:34:53:309309] [I] Sending session request
[2024-08-07 19:34:53:309309] [E] Reported Application Reason: 0x80108b15 (Remote Play on Console crashed)
[2024-08-07 19:34:53:309309] [I] Session has quit
[2024-08-07 19:34:54:309309] [I] Starting session request for PS5
[2024-08-07 19:34:54:309309] [I] Trying to request session from 192.168.150.150:9295
[2024-08-07 19:34:54:309309] [I] Connected to 192.168.150.150:9295
[2024-08-07 19:34:54:309309] [I] Sending session request
[2024-08-07 19:34:54:310310] [E] Reported Application Reason: 0x80108b15 (Remote Play on Console crashed)
[2024-08-07 19:34:54:310310] [I] Session has quit
`

chiaki 2.2 and chiaki-ng 1.8 i get this error every time. installed the flatpak and appimage on arch linux `0x80108b15 [2024-08-07 19:34:52:307307] [I] Starting session request for PS5 [2024-08-07 19:34:52:307307] [I] Trying to request session from 192.168.150.150:9295 [2024-08-07 19:34:52:307307] [I] Connected to 192.168.150.150:9295 [2024-08-07 19:34:52:307307] [I] Sending session request [2024-08-07 19:34:52:307307] [E] Reported Application Reason: 0x80108b15 (Remote Play on Console crashed) [2024-08-07 19:34:52:307307] [I] Session has quit [2024-08-07 19:34:53:308308] [I] Starting session request for PS5 [2024-08-07 19:34:53:308308] [I] Trying to request session from 192.168.150.150:9295 [2024-08-07 19:34:53:309309] [I] Connected to 192.168.150.150:9295 [2024-08-07 19:34:53:309309] [I] Sending session request [2024-08-07 19:34:53:309309] [E] Reported Application Reason: 0x80108b15 (Remote Play on Console crashed) [2024-08-07 19:34:53:309309] [I] Session has quit [2024-08-07 19:34:54:309309] [I] Starting session request for PS5 [2024-08-07 19:34:54:309309] [I] Trying to request session from 192.168.150.150:9295 [2024-08-07 19:34:54:309309] [I] Connected to 192.168.150.150:9295 [2024-08-07 19:34:54:309309] [I] Sending session request [2024-08-07 19:34:54:310310] [E] Reported Application Reason: 0x80108b15 (Remote Play on Console crashed) [2024-08-07 19:34:54:310310] [I] Session has quit `
streetpea commented 2024-08-07 13:02:59 -05:00 (Migrated from github.com)

@LucyDemooon You likely got a crash using chiaki since the patch that fixed this in chiaki-ng is not in chiaki and need to reset remote play for it to work again by putting the console to sleep. Chiaki-ng should work again after that.

@LucyDemooon You likely got a crash using chiaki since the patch that fixed this in chiaki-ng is not in chiaki and need to reset remote play for it to work again by putting the console to sleep. Chiaki-ng should work again after that.
DarkLeXu commented 2025-09-24 14:58:12 -05:00 (Migrated from github.com)

even to this day on latest release this problem is still present and the only solution/fix I found was something talked above,
You need FIRST to pair with PSRemote app and connec it on windows and only after that you can connect with chiaki, any other way doesn't seem to work it only gives crash errors and connection problems and never actually connects to the PS

even to this day on latest release this problem is still present and the only solution/fix I found was something talked above, You need FIRST to pair with PSRemote app and connec it on windows and only after that you can connect with chiaki, any other way doesn't seem to work it only gives crash errors and connection problems and never actually connects to the PS
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feedback-history-event-count
fix-macos-opengl-stream-ui
fix-ci-macos-msys2-weekly
archive/20261007T215141Z-rescue/tags/android-1.10.0-ds.1
archive/20261007T215141Z-rescue/aoleg94/android-package-agnostic
archive/20261007T215141Z-rescue/aoleg94/android-fix-touch-input
archive/20261007T215141Z-rescue/aoleg94/lib-feedback-history-per-event
archive/20261007T215141Z-rescue/aoleg94/android-fix-touch-cancel
archive/20261007T215141Z-rescue/aoleg94/android-fix-pause
archive/20261007T215141Z-rescue/aoleg94/android-fix-overlay
archive/20261007T215141Z-rescue/aoleg94/android-dualsense-triggers
archive/20261007T215141Z-rescue/aoleg94/android-dualsense-output
archive/20261007T215141Z-rescue/aoleg94/android-controller-motion
archive/20261007T215141Z-rescue/MicheleLoiDWR/android-dual-screen-controls
archive/20261007T215141Z-rescue/MicheleLoiDWR/android-stream-menu-button
archive/20261007T215141Z-rescue/latifv/codex/videotoolbox-direct-mapping
archive/20261007T215141Z-rescue/CSystem77/main
archive/20261007T215141Z-rescue/whitestorm007/perf/low-latency-optimizations
aia-upstream
archive/20261007T215141Z-rescue/zalo/webbridge
archive/20261007T215141Z-rescue/Corzcode/pr/upstream/gyrosteer
archive/20261007T215141Z-rescue/Corzcode/pr/upstream/dualsense
archive/20261007T215141Z-rescue/Corzcode/pr/upstream/uaf
archive/20261007T215141Z-rescue/Corzcode/pr/upstream/hdr
archive/20261007T215141Z-rescue/opentreecz/feature/dependabot
archive/20261007T215141Z-rescue/opentreecz/feature/deb-package
gh-pages
archive/20261007T215141Z-rescue/tags/weekly-canary-release-6547d8aed03503646fe1043512616e26c03fa9db
archive/20261007T215141Z-rescue/tags/weekly-canary-release-a875aa08f98bde24d52c18d982612533c5bee804
enable_overflow
deferred_alloc_test
new-updates
fix_sdl2
mouse_keyboard_enable
d3d12-preview
v4l2m2m
chiaki4deck
use_steam_browser_gamescope
reopen-socket
weekly-canary-release-a9a2805884cfa83865fdfcc09ca3ddfcd628aa42
weekly-canary-release-b15d302f15d4c393f4a0b5d1546f690dde4c7667
weekly-canary-release-df55652cc507b6100339eb4bc862bf41bd7414ce
weekly-canary-release-0e16950165f06e5c3291537c2eeba6e852be7120
weekly-canary-release-ce123ea41d04516a5cac32cba914660019150ce5
v1.10.0
weekly-canary-release-8dd3ee7a8a71eaef5daf6fe1c4a484587f6c141d
weekly-canary-release-593551a70a7331e0653e936d2ee89401db607952
weekly-canary-release-539414ec4758ecd71f21d02ffe44b9dc75a2b01d
weekly-canary-release-6ea3fab862d4ff90db95926424e16d599d40d185
weekly-canary-release-b0ad412fb38439e7c633fbea2837dc33825132a2
weekly-canary-release-b9cd38d4967491724ae017952047abdc2f700525
v1.9.9
weekly-canary-release-178d942309d853908eda74817845d4687f3b3bfd
v1.9.8
v1.9.7
v1.9.6
v1.9.5
v1.9.4
weekly-canary-release-8c6e9b7d37a3d76bfdf0baa6f0cde28f02c6b8a8
weekly-canary-release-e683fcb5a75800ae5e674e86f69cab1a6fa91f22
weekly-canary-release-dee8e2232ae0906929a46b8b883f6bdcb0e7ea91
v1.9.3
v1.9.2
weekly-canary-release-e481bf0f4f4a97abff746d08a5ec9b4a7da5d350
weekly-canary-release-6063147ffdf64f882e40b652183c129bd4c7cd39
weekly-canary-release-0a11b7301e63786bb9fe04dcbd27191dfae17de2
v1.9.1
v1.9.0
v1.8.1
v1.8.0
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
psn_test
v1.6.6
v1.6.5
v1.6.4
v1.6.3
v1.6.2
v1.6.1
v1.6.0
v1.5.1
v1.5.0
v1.4.1
v1.4.0
v1.3.4
v1.3.3
v1.3.2
v1.3.1
v1.3.0
v1.2.0
v1.1.0
v1.0.0
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
stale

   
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
stale
wontfix
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-streetpea/chiaki-ng#38
No description provided.