this post was submitted on 07 Jun 2023
7 points (100.0% liked)
Jerboa
10295 readers
9 users here now
Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.
Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.
Built With
Features
- Open source, AGPL License.
Installation / Releases
Support / Donate
Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.
Crypto
- bitcoin:
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK - ethereum:
0x400c96c96acbC6E7B3B43B1dc1BB446540a88A01 - monero:
41taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuV - cardano:
addr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm
Contact
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I have an S22/Android 13/One UI 5.1 and i have the hidden status bar issue.
I have noticed, however, that it's there but very dark.
Update: the problem is that the font color doesn't change when using the dark theme. So it's black on [dark color].
Also running on a Samsung, although its Android 12 oneUi 4.1.... This issue of the status bar having black txt using the dark theme, was apparent in ver 0.0.29, but haven't noticed anything of the like, since ver 0.0.30..
Yeah that makes sense, my font color in the status bar ist white and i use an amoled black theme, therefore i don't see this bug.
You can open an Issue on Github if it's not already done so it can be fixed sooner or later.
Ah, that explains it, I'm running the AMOLED theme on Jerboa, but doing dark mode at the OS level (android 13 with one UI 5.1 also, btw) breaks a Galaxy Theme I've been using for a long time and really love, so I just go piecemeal app by app turning each of them to their dark modes, but sometimes that produces weird/unintended interactions like this one
At the moment it doesn't look like anyone else has had this issue, I need to make a new GitHub account to make a post there but I'll try to remember to do that later when I have a moment
I fixed this a couple days ago here
Nice, thanks! I've never had/made the time to learn any kind of programming, but anyone who does open source work is right up there with teachers librarians and firefighters in my book of "people I'm predisposed towards liking" (honestly more of a pamphlet than a book)
Anyway, speaking as someone who doesn't know much about any of this yet, where is that at in the development process? I'm guessing people send code ideas to dessalines/their team, the code is reviewed and approved by them, and then it's sent off to the Google people for a review before it gets to the play store? I'm not in any kind of rush for this fix, so I'm just curious if it'll get to me eventually on its own or if I will have to have a bit more initiative (sideloading apps is on my list of "things I really should have figured out by now" (honestly more of a book than a list))
Hahaha I'm definitely nowhere near close to a firefighter.
But yeah the process is pretty much how you described it, we just write some code and send it. Then there's usually a bit of back and forth of code reviews from the team and then it gets incorporated into the project.
Jerboa is available from a few different places, the fastest and easiest way to get updates is to use F-Droid with the Izzy repo, for which you do need side loading but it's really easy on Android so you shouldn't have a problem there. It will also get to the play store eventually but it usually takes more time because Google has to verify the app as you said.
What version of Jerboa are you using?, as this behaviour was evident in version 0.0.29, but fixed in subsequent versions, with the current version being 0.0.32.
When can the newest version be expected on F-Droid? Currently 0.0.29.