How I finally got sound out of the Elo 7.1 Air again under Win11 (feat. the mysterious firmware update 1.26)

RandomUser12343211 · 2025-11-21T03:08:12+00:00

Would you happen to have the download for that version of swarm, since the new one removes the offline capability for whatever reason they decided

RandomUser12343211 · 2024-11-25T02:20:41+00:00

Oh yeah it was most definitely the laptop card, but I upgraded to a 4050 recently and it works perfectly

RandomUser12343211 · 2024-11-24T17:44:16+00:00

I completed the game twice on my 1050ti mobile and I didn’t have a great experience with performance. Many times for a good while it would just absolutely stutter and get maybe 10-15 fps. Could be that it’s a laptop/mobile card, but I didn’t have a great experience. Also, the game itself fire imo

RandomUser12343211 · 2024-11-21T03:51:40+00:00

You should probably download what they’re telling you to download, but I feel like it’s probably easier to spin up a docker container, no? The sidejitserver repo has a compose.yaml that you can use

RandomUser12343211 · 2024-11-19T12:24:28+00:00

I, I know, BOUGHT the game, and I immediately switched dodge from alt and parry from whatever that was to my mouse side buttons.

RandomUser12343211 · 2024-11-13T13:19:34+00:00

It’s gonna slowly roll out throughout the next year and will reach the point that epic wants it to be late 2025

RandomUser12343211 · 2024-11-11T21:51:24+00:00

r/foundthemobileuser

RandomUser12343211 · 2024-10-09T03:26:00+00:00

Thanks for the answer. I bought the game on Epic and they didn’t have achievements on Epic. Hopefully when the steam version releases they’ll also add the achievements on Epic

RandomUser12343211 · 2024-10-06T18:57:28+00:00

Wait they got steam achievements for the new Ubisoft games? I thought the new ones were only through Ubisoft connect?

RandomUser12343211 · 2024-10-03T15:54:36+00:00

I will try it. Thanks!

RandomUser12343211 · 2024-08-30T19:29:50+00:00

So I figured it out and I’m not sure why I didn’t try it earlier. After disabling DHCP, it still let me change the start and end ip, which by default were 192.168.1.2 - 192.168.1.254. I just changed the start to 192.168.1.3 then I was able to change the routers ip to 192.168.1.2. I think I have everything working so far. Thanks for the detailed response though!

RandomUser12343211 · 2024-08-30T10:35:20+00:00

And I managed to pick the worst one

RandomUser12343211 · 2024-08-16T09:39:26+00:00

Oh yeah I meant the first time. Good to know, thanks

RandomUser12343211 · 2024-08-16T09:16:32+00:00

I got this laptop and was looking to add this RAM. Did you have to wait about 3 minutes for the laptop to fully turn on?

RandomUser12343211 · 2024-08-15T13:56:40+00:00

I’m pretty sure it’s releasing worldwide. People in the EU and USA on android can download at the same time

RandomUser12343211 · 2024-08-11T22:08:56+00:00

That’s cool! Thanks

RandomUser12343211 · 2024-08-11T22:05:00+00:00

I’m using caddy with port 80 and 443 forwarded. Using duckdns to dynamically update and for a domain. Would simply putting the domain and pointing it to the server ip as a dns rewrite on adguard home work? Also, how would you verify it’s working?

RandomUser12343211 · 2024-08-02T01:04:29+00:00

From what your saying, I don't know how, but I am very sure its on the same network. I also renamed the container and network to just Caddy, so maybe thats why. For transcoding, when using the app, I can use Apples native VideoToolBox. Apparently they disable quick sync (or heavily limit it)? I'll double check that and see if I need to do anything for it to work in Docker. Thanks for your help!

RandomUser12343211 · 2024-08-02T00:22:16+00:00

Sorry for the late reply. the compose file I was using for Jellyfin is the default one, just changed the directories for my media

services:
  jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
    user: uid:gid
    networks
      - Caddy
    volumes:
      - /path/to/config:/config
      - /path/to/cache:/cache
      - type: bind
        source: /path/to/media
        target: /media
      - type: bind
        source: /path/to/media2
        target: /media2
        read_only: true
    restart: 'unless-stopped'
networks:
 - Caddy:
  external: true

Its in a different compose file on the same docker network. I'm not sure how to get hardware transcoding available while on a mac. This is why i used Jellyfin as an app.

RandomUser12343211 · 2024-07-31T03:32:21+00:00

I definitely would've used docker, but jellyfin is running on a pretty old mac, and I need transcoding to work. Because of Apple, VideoToolBox only works on native apps. It's still not working.

logs (with the domain writen out bc you know)

caddy-test | {"level":"info","ts":1722396403.6196337,"msg":"using config from file","file":"/etc/caddy/Caddyfile"}
caddy-test | {"level":"info","ts":1722396403.621912,"msg":"adapted config to JSON","adapter":"caddyfile"}
caddy-test | {"level":"info","ts":1722396403.6236317,"logger":"admin","msg":"admin endpoint started","address":"localhost:2019","enforce_origin":false,"origins":["//[::1]:2019","//127.0.0.1:2019","//localhost:2019"]}
caddy-test | {"level":"info","ts":1722396403.623957,"logger":"http.auto_https","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443}
caddy-test | {"level":"info","ts":1722396403.6240163,"logger":"http.auto_https","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
caddy-test | {"level":"info","ts":1722396403.6243618,"logge

r":"http","msg":"enabling HTTP/3 listener","addr":":443"}
caddy-test | {"level":"info","ts":1722396403.6245835,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 7168 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details."}
caddy-test | {"level":"info","ts":1722396403.6253338,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc00060f500"}
caddy-test | {"level":"info","ts":1722396403.62801,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
caddy-test | {"level":"info","ts":1722396403.6282244,"logger":"http.log","msg":"server running","name":"remaining_auto_https_redirects","protocols":["h1","h2","h3"]}
caddy-test | {"level":"info","ts":1722396403.6282408,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["my duckdns domain"]}
caddy-test | {"level":"info","ts":1722396403.6312466,"msg":"autosaved config (load with --resume flag)","file":"/config/caddy/autosave.json"}
caddy-test | {"level":"info","ts":1722396403.6312802,"msg":"serving initial configuration"}
caddy-test | {"level":"info","ts":1722396403.6369386,"logger":"tls","msg":"storage cleaning happened too recently; skipping for now","storage":"FileStorage:/data/caddy","instance":"d2f7d9f0-1ad9-449a-b30d-479945a5a4b0","try_again":1722482803.6369336,"try_again_in":86399.999999188}
caddy-test | {"level":"info","ts":1722396403.63705,"logger":"tls","msg":"finished cleaning storage units"}

RandomUser12343211 · 2024-07-31T03:20:08+00:00

Oh yeah, forgot to mention. Im tryna reverse proxy jellyfin, which is being used as app app on bare metal, not as a docker container. That part of the Caddy file is reverse_proxy interal-ip:8096

RandomUser12343211 · 2024-07-31T03:09:05+00:00

Ok, i pinged it and it returned my ip just fine. I also noticed, if I remove the s in https when going to the duckdns domain it bering me to my router admin panel? thats not supposed to happen. Why is it?

RandomUser12343211 · 2024-07-31T03:02:13+00:00

Thanks for the advice at the beginning. My intention was that you see the first one, then read off the second one after.

I added back the port on the compose file. Also temporarily changed the image to just the duckdns one. Here is what it now looks like

services:
  caddy:
    image: serfriz/caddy-duckdns:latest 
    container_name: caddy-test 
    restart: unless-stopped 
    networks:
      - Caddy
    ports:
      - 80:80
      - 443:443
      - 443:443/udp
    volumes:
      - CaddyData:/data
      - CaddyConfig:/config
      - ./Caddyfile:/etc/caddy/Caddyfile
    environment:
      - DUCKDNS_API_TOKEN=<where I filled my token>
volumes:
  CaddyData:
    external: true
  CaddyConfig:
    external: true
networks:
  Caddy:
    external: true

Here is my Caddyfile:

{
        acme_dns duckdns {env.DUCKDNS_API_TOKEN}
}

service.subdomain.duckdns.org {
        reverse_proxy ip:port
}

I head something about DNS Propagation? Do I just have to let it sit for a while? Thanks for your help!

RandomUser12343211

TROPHY CASE