I think legally the LICENSE.MD is what counts, but yeah, better to stay safe, especially since as you said
There’s still an nc clause in the notice, fdroid wouldn’t have it, and even if it couldn’t be enforced regardless, I still don’t want to put that clause in. I want everyone to be free to use it in all ROMs and such without issues.
Btw, I completely respect your decision and wasn’t trying to say anything other than it’s not compatible.
1 Like
@Creed I understand where you’re coming from, it would obviously hurt a little if someone profits off of it while you get nothing, but I don’t think a library like this is really profitable anyways.
Your choice, I’m not sure what I would do if it was me.
A post was merged into an existing topic: Finally - A solution for kosher and dpad compatible Google Maps?
M3 works beautifully on my Kyocera.
The only thing is that the apps UI doesn’t work great with dark mode, but that doesn’t really make a difference, because that doesn’t have to do with the library itself.
Which phones did you optimize for?
Which phones has this been tested on?
His is actually better in some cases than to use official, causes less issues from my research though like I said I haven’t tried it.
There are also the cases of adding support to phones with a small touchscreen too. It’s cool
sorry, was just by maariv, the noncommercial thing is just my default from my other stuff, I don’t mind doing free. I’m fixing the readme, and pushing a few more things (option to listen to all keycodes by default, instead of having to set it up per phone, some phones will still need setup, and the option in build to leave softkey bar off by default, if you only need it for a few screens) give me a few minutes
2 Likes
Nice. When you’re done say so, and I’ll check it out tomorrow/next week.
done
1 Like
I tested it on a broken screen tcl flip 2 using scrcpy, and some chinese timmkoo-like mp3 player (needed something with actual navbar keys to test my conditional)