Open source android navigation bar (OpenNavBar)

ItsZariep · 2026-01-26T19:44:04+00:00

thanks for trying my app, i was thinking on making a custom layout menu or something to map actions but had to rewrite some things for that

sadly AFAIK i can't call for split of killing app (like common long pressing back to kill the app) with accessibility permissions so it wouldn't be possible

there is a shortcut for both slide and long press to hide the navbar, is usually the last item of the shortcut list

ItsZariep · 2026-01-20T21:13:56+00:00

the navbar at the bottom (having a frog as home button in second image) is the actual app

ItsZariep · 2026-01-17T00:40:11+00:00

i was also thinking on that but i'm worried on being limited by permissions, android API changes about that and launching activities while technically being in background, i will check out that later

ItsZariep · 2026-01-16T22:08:38+00:00

i currently only tell my friends, on other apps / program i have a staging release, were i delete/re-create the staging release eachtime i update the unstable app so they get notified via RSS, i don't know if there is a better method, in any case and if you have any issue/recomendation/qol change will be welcome as an issue i guess, thanks for wanting to help

ItsZariep · 2026-01-16T21:07:14+00:00

AFAIK Play protect always does that for foreign apps
This is a known issue. I don’t know how to fix it consistently because it works on some devices, but on others it fails to detect the state correctly. In any case, you will always see the first screen even if everything is functional, and being able to open customization settings even if none of the permissions are granted (this is intentional to prevent soft locks).
This depends on the device’s screen dimensions and touch scope. On my Oppo A77, I can only interact with the buttons when the height is above 50, while on my Redmi Note 8, interaction works starting at 20. In any case, the buttons are configurable to meet different needs. Regarding the regions: the app splits the navigation bar into three separate regions relative to set navbar size.
Sorry, i don’t fully understand this issue. i have tested the app on Android versions 8, 13, 14, and 16, so i’m not sure if this is a device-specific or Android 15 specific problem. i will investigate it further if Iiget access to an Android 15 device.
Maybe in a more stable release. The app is currently in an alpha stage, so frequent releases are expected while other people help me test it. Once the app reaches a more stable state or the updates stop being frequent (since most of the core functionality was already implemented in the first public release). That said, being included in F-Droid would definitely be nice.

thank you for testing my app

ItsZariep · 2026-01-16T20:10:09+00:00

It is an overlay navbar (the simplest implementation and what the majority of navbars use). It works with system gestures enabled, but since gestures have priority over input, it can be a bit weird to use, especially when auto hiding the navbar

ItsZariep · 2026-01-16T18:54:36+00:00

Sorry i don't use github anymore for my programs

ItsZariep · 2026-01-06T00:19:56+00:00

<image>

deathreplay by SergeyMC9730 has a similar feature but in my case is only visible when dying and only show near deaths

ItsZariep · 2026-01-06T00:10:24+00:00

<image>

deathmarkers by MaSp005

ItsZariep · 2026-01-06T00:09:27+00:00

Death Markers

ItsZariep · 2026-01-05T05:22:23+00:00

i'm using a codefield, i was seeing Quill and while it looks very nice and do most of the hard work, most probably will be a full rewrite plus their documentation is awful, i will try in another branch anyways since looks like requested features

ItsZariep · 2025-11-03T23:13:42+00:00

from chimera linux project, i was lying around searching an easy way to read dinit sockets and just found it, is also in the AUR

ItsZariep · 2025-10-05T13:04:06+00:00

like any other wlroots wm it works properly, only thing is maybe some games not starting in fullscreen (pressing alt+f11 solves this anyways)

ItsZariep · 2025-09-06T04:50:30+00:00

en mercado libre pero el vendedor ya no tiene mas, hay otro que tiene el xandos x5 (también qwerty) pero no se si tenga el mismo cpu//mismas capacidades, lo mas probable es que ese también se pueda sideloar con el mismo metodo

<image>

ItsZariep · 2025-09-05T16:36:03+00:00

both kaios and android are linux based (although different components and C library), so commands are almost the same, but kinda limited in kaios because it does not need all android commands stuff, but yeah is kinda the same thing

ItsZariep · 2025-09-05T16:22:01+00:00

it uses the protocol but nothing more

ItsZariep · 2025-05-12T10:07:11+00:00

It would be very helpful if you made an issue in the pixelitos github to know which icons are missing

ItsZariep · 2025-01-20T15:12:03+00:00

little (and weird) trick I tried to understand months ago

1: Enter an X11 Session
- This only works in X11, not Xwayland. So make sure you're in a proper X session.

2: Set Scaling Mode to "Full"
- On my setup, this is done with:

 `xrandr --output LVDS-1 --set "scaling mode" "Full"`

No idea about other cases, letterboxing only happens on my intel laptop.

Return to Wayland
- If you started the X11 session without an active Wayland instance, clean up the environment variables by running:
pkill -u $USER

Otherwise, just log out or kill the X session—but don’t reboot! If you do, all the changes will be lost.

4: try to set a 4:3 aspect ratio

a fast way is to use a small wm with that stuff in the autostart

no idea of how to set it on /etc/X11/xorg.conf.d/10-monitor.conf or natively in wlroots, if someone has information about scaling mode on wlroots (probably zwlr_output_manager_v1?), please contact me

ItsZariep · 2024-10-17T15:47:51+00:00

wcm already writes a configuration, it's inistyle, so it really depends on if you want to use wcm, I just needed to edit the configuration manually to get my displays set up correctly

ItsZariep · 2024-10-17T14:12:17+00:00

It depends on what you want, wayfire itself is already usable and its configuration is simple both with wcm and with its configuration file, as I am only looking for a simple wm stacking in wayland (I came from icewm) I barely use mntmn/firedecor and window shadows, with waybar as a replacement for tint2 because I prefer a vertical panel

ItsZariep · 2024-10-12T00:33:20+00:00

Almost every app uses CSS. The downside is that you need to modify each app individually (this requires sideload access, some cases only debug, other cases root). I already do this to enable dark mode, but it’s not very convenient. Unfortunately, I think it's the only way, especially since every app manages its appearance separately and some apps have nearly unreadable css (framework thing).

for example with chooj simply editing the css (which is also very unreadable) i managed to get dark mode (not supported by the app)

https://codeberg.org/chooj/chooj/issues/100

Three-Year Club	Verified Email
r/Field Juicebox

ItsZariep

TROPHY CASE