Real question, do we care about 225dp? Is it widely used?
And thanks for the detailed report 
Maybe it’s time to add soft key support but it’s a headache.
@Creed any chance you wanna share what you got?
Edit - forgot I can also look at @PodLP Quickly reverse engineer hidden Android APIs with Gemini and OpenCode - Tom Barrasso
All tested, verified?
Fine for when you’re fleishigs, but what if you’re not?
Can we have a sample app using this library, to test it out?
I used similar version for my apps, this is tweaked to avoid some issues I had, didn’t test this specific version yet. Let me know if it works for you
First I’m just taking all device specific softkey guides with fallback to standard but I’m checking it out.
@SILB can you try those 5 again? 225 like you said
7 posts were split to a new topic: Shkiah is coming: Can you make a minyan in time?
Tested and verified (had to fix an issue where the system navbar would show even when the sofkey bar was on)
here’s a test app
Parve yapchick… So… Kugel? Or with tofu
read the package name. btw still fixing the navbar issue
Figured out the navbar issue, seems you can’t hide navbar in Theme.DeviceDefault, what my test app is running (or at least I can’t), but I could in Theme.Material3 . I’m seeing if I could make the .NoActionBar conditional to only apply when the softkey bar is on (for smart phones)
I figured out the navbar issue,
Yapchik now looks out for material (m), material3 (m3), and device default(dd).
In all 3 it applies a conditional to show the navbar when the softkey bar is off (for touchscreen users).
In dd, not all phones have the ability to hide the navbar, which left me with a conundrum: the softkey will be hidden by the navbar, if the navbar is set to hidden but is still showing, or to always show the navbar and display the sofkey bar above it.
So I made a display size setting for the softkey bar if yapchik detects dd, that way, if the navbar is blocking the sofkey bar, you just make the softkey bar taller. (this setting only applies to dd, m and m3 remain the normal height.)
I also made the option to make a device profile xml so you could apply settings automatically to known devices.
here are 3 test apps with all 3 themes, it has demo screens and a toast popup whenever a softkey is pressed
the pareve yapchik is ready
Looks nice, can’t add to vela because of the license
whats the license doing? could you not add because of my license or his?
Your license would add restrictions on top of gpl, maybe you can look into granting an exception or something. A written grant for vela and vela-dpad (mine is a hard fork).
Btw, I haven’t tried it yet, so I can’t guarantee it would work well in Vela, but I’ll put time into it only when I know I can really use it.
I now have apache 2.0, should be good
Don’t change it for me but the notice still says non commercial, build.gradle still pfnc and id need a new tag published after changes. Not compatible with gplv3.
The only reason I care is because upstream will not be able to benefit at all, as @keepitkosher mentions that he plans on an fdroid publish.
Fdroid would never allow it.
I also don’t want to force non commercial on even just my fork.
