Steam Link

Steam Link

Steam Link se cierra en Galaxy A51 (Android 13) - Warframe
Hola, necesito ayuda. Steam Link se congela y crashea constantemente mientras juego Warframe.
​
Problemas:
​La app se cierra sola y el sistema me avisa de "bloqueos frecuentes".
​Al intentar volver, sale "Steam no disponible" o el PC aparece desconectado.
​He llegado a transmitir 16.4M de paquetes en 3 horas antes del fallo total.
​
:steamthumbsdown::steamthumbsdown:Hardware:
​Dispositivo: Samsung Galaxy A51 (SM-A515F)
​SO: Android 13 / One UI 5.1
​Red: Wi-Fi (Uso intenso de paquetes detectado)
​
Ya desactivé los límites de uso en segundo plano, pero el problema persiste. ¿Es un problema de decodificación de hardware con el procesador Exynos o hay algún ajuste de bitrate recomendado para evitar estos cierres?
< >
Showing 1-14 of 14 comments
I don't speak Spanish particularly well, so I'm going to have to rely on machine translation to try to reply here. Sorry about that! I'm posting the English version as well, just in case machine translation mangles anything.

As an LR4 Tenno myself I haven't actually had a lot of trouble streaming Warframe, though I admit lately when I've had a need to pop on to do a quick trade or tinker with dojo stuff on-the-go I've been using the actual mobile version of the game, so I haven't been really testing the streaming recently.

Even when I did, I will admit I didn't usually keep the stream going for three hours.

I'll try a bit of streaming to Android from Windows later tonight, but if you can get ahold of the crash log from the device that would be very useful.

I've got a couple of questions for you, beyond that:

  1. Does it always take multiple hours before it crashes?
  2. Did this crashing just start recently (with one of the more recent builds of the Android Steam Link app, for instance), or has it been going on for a while?
  3. If you happen to have any other Android device you can test with, does the crash happen there as well, or is it unique to the A51?

Hopefully that info will help track down what's going on with the crashes!

----

No hablo español muy bien, así que tendré que usar la traducción automática para intentar responder. ¡Disculpen! También publico la versión en inglés, por si acaso la traducción automática falla.

Como Tenno de LR4, no he tenido muchos problemas para retransmitir Warframe, aunque admito que últimamente, cuando he tenido que entrar para hacer un intercambio rápido o trastear con cosas del dojo sobre la marcha, he estado usando la versión móvil del juego, así que no he estado probando mucho la retransmisión últimamente.

Incluso cuando lo hacía, admito que no solía mantener la retransmisión durante tres horas.

Intentaré retransmitir un poco a Android desde Windows más tarde esta noche, pero si puedes conseguir el registro de fallos del dispositivo, me sería muy útil.

Tengo un par de preguntas para ti, además de eso:

  1. ¿Siempre tarda varias horas en fallar?
  2. ¿Este fallo empezó hace poco (con una de las versiones más recientes de la app Steam Link para Android, por ejemplo) o lleva ocurriendo un tiempo?
  3. Si tienes otro dispositivo Android con el que puedas hacer pruebas, ¿el fallo también ocurre ahí o es exclusivo del A51?

¡Espero que esta información te ayude a averiguar qué está pasando con los fallos!
Hi Packetdancer, thanks for the help!
​I'm currently unable to provide the remote_play_debug.txt file because I am on Android 13. Due to the "Scoped Storage" restrictions on this version, the Android/data/ folder appears empty when using mobile file managers. I am looking for a PC to connect my phone via USB and extract the logs properly.
​In the meantime, here are the technical details from my device and the crashes:
​Device: Samsung Galaxy A51 (SM-A515F).
​OS: Android 13 / One UI 5.1.
​Problem progression: It worked fine for the first week. Then, it started kicking me out occasionally. For the last two days, it has become unplayable, freezing and crashing constantly.
​Session Data: My most recent crash happened after 3 hours and 22 minutes of gameplay.
​Network/Performance: During that session, I transmitted over 16.4 million Wi-Fi packets. Interestingly, the battery stats show 0 min of CPU usage, which suggests the app process is freezing or hanging before it can report usage to the OS.
​System Warnings: My Android system is officially flagging the app for "Frequent Crashes" and suggests putting it into Deep Sleep.
​I will try to get that debug log as soon as I can access a PC. Thank you for your patience!

I'm still looking for a PC to extract the remote_play_debug.txt file due to the Android 13 folder restrictions. However, I managed to get these system specs:
​SDK Version: 33 (Android 13).
​OS Security Patch: 2023-08-01.
​Build Version: 330543000.
​Device: Samsung Galaxy A51 (SM-A515F).
​As I mentioned before, the app is being flagged for "Frequent Crashes" after long sessions (~3 hours). It seems the system reaches a limit where the app freezes, showing 0 min of CPU usage despite the high network traffic (16.4M packets).
Originally posted by Kronox:
Hi Packetdancer, thanks for the help!
​I'm currently unable to provide the remote_play_debug.txt file because I am on Android 13. Due to the "Scoped Storage" restrictions on this version, the Android/data/ folder appears empty when using mobile file managers. I am looking for a PC to connect my phone via USB and extract the logs properly.

Hm. I wonder if there's a memory leak of some sort happening that's so slow/small it only shows up after *really* long sessions.

You mention you need to look for a PC to connect the phone to -- I'm guessing that means you're not in the same building (or on the same network) as the computer you're streaming Warframe from? I ask because that would be another difference from how I usually have played Warframe when streaming; I'm usually in the living room, on the couch, watching something with family and just noodling around with dojo redesign on the phone when I've been doing it, with it streaming from my computer just down the hallway.

Since you say it's gotten worse lately, my other question would be if you were to roll back to an earlier build of the Steam Link app, does that improve things at all? If so, I *might* know what's happening and I can experiment with a fix.
Hi Packetdancer, thanks for the insight. Just to clarify, I am currently using the official stable version of Steam on my PC. As I mentioned before, because my physical monitor is broken, I haven't switched to the Beta branch yet. I am worried that if I trigger a Steam restart to change versions and the remote connection doesn't re-establish itself automatically, I will be completely locked out of my computer.
​I am still planning to get access to a second PC to pull the debug logs from my Galaxy A51 since Android 13 hides the data folders. I strongly suspect your "memory leak" theory is correct, given that the crashes consistently happen after long sessions (3h 22m in my last report).
​Thanks for your patience!
Ah, what I meant was the Steam *Link* app on the Android side. I was wondering if reverting to an older build made it more stable for you -- if so, it would be useful to know.
I'm not sure, but where do I download the APK from? Because there's always going to be malware.
Originally posted by Kronox:
I'm not sure, but where do I download the APK from? Because there's always going to be malware.

Actually, let's try with 1.3.19 -- you can grab it from the (unlinked but still live) older builds directly at https://media.steampowered.com/steamlink/android/steamlink-android-1.3.19.292.apk
Let me know if the 1.3.24 beta build works better for you. (It's linked in a pinned post here in this forum.)
The beta version does work because I exited the beta mode I had with Steam Link and it started working perfectly. However, there's a problem: there are too many errors when I connect the controller because it either doesn't recognize the camera joystick or the movement joystick. That's a problem that needs fixing.
Originally posted by Kronox:
The beta version does work because I exited the beta mode I had with Steam Link and it started working perfectly. However, there's a problem: there are too many errors when I connect the controller because it either doesn't recognize the camera joystick or the movement joystick. That's a problem that needs fixing.

Could you elaborate on what you mean by errors? Like, actual error messages popping up, or...?

Also, what controller are you connecting, specifically?
There are no errors, it's just that the game doesn't recognize my controller. It happens occasionally; my controller is a Nintendo Pro Controller, but the problem is that it only doesn't recognize it when it's connected to my phone.
Originally posted by Kronox:
There are no errors, it's just that the game doesn't recognize my controller. It happens occasionally; my controller is a Nintendo Pro Controller, but the problem is that it only doesn't recognize it when it's connected to my phone.

Does the controller work in the shell? And does the controller work in other games when it isn't working in Warframe?
The weird thing is, I've played Brawlhalla, The Forest, Terraria, and those games recognize my controller perfectly, but the problem is Warframe, and I don't understand why. I don't think it's Steam, because when I go to test the controller in the Steam controller section, it recognizes it completely, and that's what I don't understand.
Just out of curiosity, is this a Switch Pro controller or a Switch 2 Pro controller? Or, I suppose, a Switch-compatible 'pro' controller that isn't one of the official Nintendo ones. (If it's *not* an official Nintendo one, and you happen to have an Amazon link to the specific model, that'd also be helpful.)

That definitely is odd, though. If you connect a different controller -- any you happen to have laying around, really -- does that also have issues?

Or for that matter, does the on-screen virtual controller in Steam Link have issues?
< >
Showing 1-14 of 14 comments
Per page: 1530 50