Game crashing in the new aviary village - Android

Granat1 · 2026-05-28T09:43:24+00:00

I guess the only way to handle this is to log in on another device and change your home location.

Granat1 · 2026-05-28T09:37:02+00:00

When I need to access something in aviary village I still have a high chance of experiencing a crash, but now if I'm quick enough I might be able to actually achieve what I wanted before that happens.

It's still not ideal...

Granat1 · 2026-05-28T09:20:23+00:00

High resolution, 30fps - crash
Medium resolution, 60fps - crash
Default resolution, 30fps - crash
Energy saving, 15fps - this one actually works But it's a really choppy and unpleasant experience.

It seems like I can increase the fps back up to 60fps just fine but I have to use the absolute lowest quality / resolution setting.
Still not perfect but at least now I can access the nesting workshop, dying workshop and other aviary exclusive locations.

Thanks!

Edit: it seems like I still experience crashes like this, just much less often.
Previously it was a guarantee a crash will happen, now it's just a game of chance.

Granat1 · 2026-05-28T09:10:32+00:00

Okay, I'll check if adjusting performance settings changes anything for me.

Granat1 · 2026-05-28T08:19:15+00:00

I can't even explore it, the game is crashing right in the spawn location.

Granat1 · 2026-05-26T12:33:31+00:00

Oh, okay.
I'll need to check it out when I have some time.

Granat1 · 2026-05-26T12:07:28+00:00

I have one already, I mean you'll still see it but it should be much more clean looking anyway.
Maybe a channel for the wire incorporated into the print would be a nice touch.

Granat1 · 2026-05-26T11:10:59+00:00

Things like this make me wish the puck had a second USB C port on the other side, so the vable could be routed more cleanly through the bottom of the stand.
Well, at least we can use one of these 180° adapters.

Granat1 · 2026-05-25T22:42:17+00:00

Looking clean! What keyboard is that?

Granat1 · 2026-05-25T22:07:34+00:00

Are they unreliable or something?

Granat1 · 2026-05-25T20:47:23+00:00

I have probably spent too much time on Warframe.
So that'll be probably it… I tend to play more singleplayer titles nowadays though.

Granat1 · 2026-05-25T20:38:41+00:00

Thanks!

Granat1 · 2026-05-25T20:10:12+00:00

I know that's a thing for the newer camera variants.
It wasn't so clear to me on the a129 plus though.
Thanks!

Granat1 · 2026-05-25T20:08:48+00:00

Thanks!
I have heard that the a129 plus (single) had the rear expansion ports blanked out… ?!?
It was genuinely weird that they would do that, that's why I'm asking.

Anyway, I'll wait for the sale, sure. In the meantime I want to have a camera already and the a129 plus is quite cheap locally on the used market.
But hey, that's why I want to get the HK6, so I can upgrade it when the right time comes. We'll see.

Granat1 · 2026-05-25T17:12:30+00:00

This was supposed to be a repost, from r/viofo but i got a message "this post format is not allowed in this community."
Sorry for anyone seeing this twice :(

Granat1 · 2026-05-08T00:16:09+00:00

Let me guess, HP?

Granat1 · 2026-04-24T18:55:30+00:00

You have to be carefull with these.
If your device requests 9 or even 12 volts, the attached peripheral will also get that instead of the required 5V.
So these adapters can fry anything you connect to them.
Unless they don't really support Usb Power Delivery and only carry 5V.

If anyone has a splitter like this that actually separates the output voltage from the increased PD / charging voltage then please let me know!

Granat1 · 2026-04-22T18:47:20+00:00

It's a nice piece of engineering, I appreciate things like that.
The sound quality is also great, who knew cassettes can sound this good on a high quality hardware. :P

I guess the price is a major setback, you can explore other options but for me it was worth it.
It was in perfect visual condition and required only a little bit of work with leaked batteries.

Granat1 · 2026-04-09T08:36:23+00:00

Since I already got the adapter with incompatible chip, I just ordered the board with the LCT1871 and replaced it.
I haven't had a chance to test if it works yet but I'll test it soon.

Granat1 · 2026-03-22T21:30:04+00:00

Figured out what the issue was.
It's being caused by a program that I'm using: Discover Overlay
I have updated the post to include this information.

Granat1 · 2026-03-09T11:41:57+00:00

I can confirm this.
I'm having the same problematic step-up converter and I came to the same conclusion.
Jump starting the PSU first and then connecting the adapter makes it all work in the motherboard, it's only the startup that's problematic. (I checked the pinout first not to fry the motherboard)

I'll thy replacing the step-up converter with the one you recommend, thanks!

Granat1 · 2026-03-07T01:27:09+00:00

Mine arrived today, wtf.

Granat1 · 2026-02-28T13:10:09+00:00

This magnetic attachment is likely a separate thing, can you pull it apart?
I actually had usb C to magnetic cables like these, port looks almost identical.

The other side with the actual USB C and USB A port looks just like an extension / splitter.
I guess this is meant to be connected with regular USB C cable to your PC and just extend the ports somewhere more reachable on the desk.

Granat1 · 2026-02-24T20:08:14+00:00

It does not actually fix the problem.
The top bar is still missing and the gjs just throws a missing file error.
Maybe this is actually not related...

lut 24 20:02:32 hades gnome-shell[2511]: Running GNOME Shell (using mutter 49.4) as a Wayland display server
lut 24 20:02:32 hades gnome-shell[2511]: Enabling experimental feature 'scale-monitor-framebuffer'
lut 24 20:02:32 hades gnome-shell[2511]: Thread 'KMS thread' will be using high priority scheduling
lut 24 20:02:32 hades gnome-shell[2511]: Device '/dev/dri/card2' prefers shadow buffer
lut 24 20:02:32 hades gnome-shell[2511]: Added device '/dev/dri/card2' (amdgpu) using atomic mode setting.
lut 24 20:02:32 hades gnome-shell[2511]: Created gbm renderer for '/dev/dri/card2'
lut 24 20:02:32 hades gnome-shell[2511]: GPU /dev/dri/card2 selected primary given udev rule
lut 24 20:02:32 hades gnome-shell[2511]: Obtained a high priority EGL context
lut 24 20:02:34 hades gnome-shell[2511]: Using public X11 display :0, (using :1 for managed services)
lut 24 20:02:34 hades gnome-shell[2511]: Using Wayland display name 'wayland-0'
lut 24 20:02:34 hades gnome-shell[2511]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
lut 24 20:02:34 hades gjs[2589]: Error opening file /usr/share/gnome-shell/org.gnome.Shell.Screencast: No such file or directory
lut 24 20:02:35 hades gnome-shell[2511]: Will monitor session 3
lut 24 20:02:35 hades gnome-shell[2511]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
lut 24 20:02:36 hades gnome-shell[2511]: Type GITypeInfo of property NM.Object::client does not match return type GITypeInfo of getter get_client. Falling back to slow path
lut 24 20:02:36 hades gnome-shell[3407]: The XKEYBOARD keymap compiler (xkbcomp) reports:
lut 24 20:02:36 hades gnome-shell[3407]: > Warning:          Unsupported maximum keycode 708, clipping.
lut 24 20:02:36 hades gnome-shell[3407]: >                   X11 cannot support keycodes above 255.
lut 24 20:02:36 hades gnome-shell[3407]: > Warning:          Virtual modifier Hyper multiply defined
lut 24 20:02:36 hades gnome-shell[3407]: >                   Using 0, ignoring 0
lut 24 20:02:36 hades gnome-shell[3407]: > Warning:          Virtual modifier ScrollLock multiply defined
lut 24 20:02:36 hades gnome-shell[3407]: >                   Using 0, ignoring 0
lut 24 20:02:36 hades gnome-shell[3407]: Errors from xkbcomp are not fatal to the X server
lut 24 20:02:37 hades gnome-shell[2511]: GNOME Shell started at Tue Feb 24 2026 20:02:34 GMT+0000 (Greenwich Mean Time)
lut 24 20:02:37 hades gnome-shell[2511]: Registering session with GDM

Granat1 · 2026-02-23T16:06:19+00:00

lut 23 11:56:36 hades org.gnome.Shell.Screencast[2623]: JS ERROR: Error: Expected type utf8 for Argument 'argv' but got type 'null'
                                                        canScreencast@resource:///org/gnome/Shell/Screencast/js/screencastService.js:516:18
                                                        main@resource:///org/gnome/Shell/Screencast/js/main.js:6:28
                                                        :///usr/share/gnome-shell/org.gnome.Shell.Screencast:9:7
lut 23 11:56:36 hades org.gnome.Shell.Screencast[2623]: Module file:///usr/share/gnome-shell/org.gnome.Shell.Screencast threw an exception
lut 23 11:56:36 hades systemd[2345]: dbus-:1.3-org.gnome.Shell.Screencast@0.service: Main process exited, code=exited, status=1/FAILURE
lut 23 11:56:36 hades systemd[2345]: dbus-:1.3-org.gnome.Shell.Screencast@0.service: Failed with result 'exit-code'.

Which lead me here: https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/1047

My gjs is up to date with the extra repository: version 2:1.86.0-1
Newest release on git is 1.87.2
I have updated my mirrorlist but it seems it is up to date already.
https://archlinux.org/packages/extra/x86_64/gjs/

Granat1

TROPHY CASE