this post was submitted on 16 Nov 2025

6 points (75.0% liked)

Voyager

7549 readers

52 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Rules

Be nice.
lemmy.world instance policy

Sponsor development! 👇

💙

founded 2 years ago

MODERATORS

aeharding@lemmy.world

aeharding@vger.social

Bug: Black borders / smaller window after posting (sopuli.xyz)

submitted 2 weeks ago by passenger@sopuli.xyz to c/voyagerapp@lemmy.world

27 comments fedilink hide all child comments

Voyager seems to have a bug that seemingly came with the new Voyager version: after posting a comment, screen space with rounded corners / camera notch are not fully utilized and black borders appear. This effect remains until app restart. App remains fully usable, just with a bit less screen space used.

Did a quick search of github issues but did not find this one reported.

Are others getting this?

Sorry for this low effort post instead of a real full bug report. I feel like this must be a known issue already but just didn't find it.

Thanks for the great app!

you are viewing a single comment's thread
view the rest of the comments

[–] passenger@sopuli.xyz 1 points 2 weeks ago (1 children)

A comment was made here in this post where a helpful person posted an actual screenshot: https://lemmy.dbzer0.com/comment/22643454

Thanks again, great app!!!

[–] aeharding@vger.social 2 points 1 week ago (1 children)

Ah thanks. Are you running the app from the store? Also what version of voyager, and what phone model?

[–] passenger@sopuli.xyz 1 points 1 week ago* (last edited 1 week ago) (1 children)

Pixel 9. GOS and using 2.40.4 updated today with Obtainium from github. I will see after posting this comment if the issue persists. Edit: did not get it from posting this comment! Seems fixed in todays release!

[–] aeharding@vger.social 2 points 1 week ago (2 children)

Thanks, let me know if it comes back. I’ve been trying to replicate on all my Android devices but no luck so far!

[–] passenger@sopuli.xyz 1 points 1 week ago (2 children)

Unfortunately, it still exists after all. I got it now when posting another comment in this thread. So it doesn't happen every time when posting it seems.

[–] aeharding@vger.social 2 points 9 hours ago (1 children)

Can you try the latest beta and let me know if it still happens?

[–] passenger@sopuli.xyz 1 points 3 hours ago* (last edited 3 hours ago)

Seems fixed, made two comments so far without issue. Edit: that was the third and still no issue. Thank you!

[–] passenger@sopuli.xyz 1 points 4 hours ago (2 children)

Testing...

[–] passenger@sopuli.xyz 1 points 3 hours ago* (last edited 3 hours ago)

Testing with beta... Edit

[–] passenger@sopuli.xyz 1 points 3 hours ago

Testing with beta 2

[–] theskyisfalling@lemmy.dbzer0.com 1 points 1 week ago (1 children)

Just to reply off the back of this comment chain I am on a Pixel 6a running Graphene with the app acquired via aurora. It will happen every single time I go into composing a reply, even if I dont actually post a reply and back out of the compose. It doesnt happen when submitting a post however.

[–] aeharding@vger.social 3 points 1 week ago (2 children)

Can you do a screen recording?

[–] theskyisfalling@lemmy.dbzer0.com 2 points 1 week ago

Heh.

So I have tried multiple times today and it isn't happening any more for any replies I have made. It was consistently happening for quite a while and as soon as I try to record it stops. Fucking weird.

I will screen record for you if it start happening again but it seems to be fixed now?

[–] theskyisfalling@lemmy.dbzer0.com 2 points 5 days ago (1 children)

Just as another update to this, the issue has definitely not been solved. It still happens but will never seem to do so when I am recording the screen.

I don't know if the process of starting the screen recorder interrupts whatever is causing the issue but I have made a shit ton of recordings these last few days and it will never happen whilst recording but will still happen most times when a screen recorder is not activated.

[–] aeharding@vger.social 3 points 4 days ago (1 children)

Interesting.. do you know how to try the beta? If I push a potential fix can you try to see if it fixes it with certainty after a couple days?

[–] theskyisfalling@lemmy.dbzer0.com 1 points 4 days ago

I do not, but happy to try it out and report back if you let me know how to :)