Glad we are on the same page ![]()
To be clear, if you do integrate this, your users with browsers installed will never see a difference.
@TripleU psheeeee
Glad we are on the same page ![]()
To be clear, if you do integrate this, your users with browsers installed will never see a difference.
@TripleU psheeeee
Did you turn the entire app into a default browser?
No
Only change is if you ONLY have system webview, no links will open. If you have a browser installed they will open in the browser, not webview.
meaning Velo becomes the browser when no other browser is installed
No
Bro i was kidding ![]()
I know I know. I only brought it up because ars18 did. Not everyone is an edgelord like us lmfao.
I had to check up what an edgelord is lol
I’m more of a dark humor kinda guy but usually about my life
And memes? I don’t know any of them I’m too busy with vela ![]()
Amazing work @keepitkosher on Vela in general and @ars18 on the d-pad, small screen and kashering! I am really enjoying using it.
On my Sonim x320, the app displays nicely, and d-pad navigation works well throughout the app. I briefly checked it out at the default 225dp before switching back to 320dp which is what i keep my screen set at in general. If you want, I could do some more testing at 225dp when I get a chance. I would suggest that you make the d-pad map scrolling only move around half to a quarter of the amount it does now per click, because at the current amount it is hard to select a specific building in an urban area. I would also suggest that you make the upper right and upper left physical buttons zoom because with the current setup it takes at least 4 key presses to zoom and continue moving the map.
A few things I noticed:
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
Probably not.
The x320 has a very weird screen shape, which is probably why it has an uncommon DPI.
13 posts were split to a new topic: Yapchik: dumbphone UI integration for Android apps
225dp is the default, and it can only be changed in developer options. The only other person I know who has the x320 also has it changed, although I’m not sure to what. The issue with it being different than the default is that it slightly breaks some of the system apps, so I definitely see why someone would keep it at the default.
Basically, IDK.
A post was merged into an existing topic: Yapchik: dumbphone UI integration for Android apps
Can’t test the update button yet, because the fix is only on the latest update ![]()
Focus while downloading works.
Vibration-on-turn wraps.
Dropped pins still move the map. It seems that the map moves to the last named place that was selected (ex. home or a store) when clicking a random address.
Place descriptions scroll.
I noticed another thing that might be related to the update button issue: by the downloaded voices, where there is a use button and a delete button side by side, I cannot move from one to the other directly; instead, coming from above them gets me to delete, and coming from below them gets me to use.
Also, I’m not sure if this is for you or @keepitkosher, but for some reason by the routing regions in offline settings it says no regions available yet instead of listing areas to download.
@ars18 is your post playing hide and seek with me?
Things seem to have been split into different topics
Right. But your post about the bug fixes belongs here, not by the Toameha.
Sorry about that, I just deleted it. Your app took off nicely and my repository was redundant at best. Thanks for all your work!