Hacker News new | ask | show | jobs
by ddtaylor 114 days ago
Tried this on my moto g 128GB - 2025 (XT2513V) running Android 16. Here is some rapid fire feedback.

I opened this in a pretty heavily populated area in Baltimore. There wasn't anyone likely near using glasses and no detections were made, but the debug log flew by absurdly quickly likely because there are a ton of Bluetooth devices nearby.

The start scanning button doesn't change to stop scanning, but it does seem to toggle scanning.

The top bar is overlapping with the notification bar area.

The bottom is truncated slight by my 3 button gesture bar thing. I am old and use the very ancient back, home and multi task buttons that are always visible because I am old.

When I first granted permission the app seemed to just lock up and wouldn't do anything until I restarted it. I gave it both the permissions it wanted and tried fiddling with stuff, but it didn't seem to redraw and I couldn't get the settings to open until after I restarted.

When I first started I think I was connected to my headset, which then disconnected after the permission request?

2 comments

I second this ... using a Google Pixel 8 I have exactly the same issues.
Maybe the app doesn't work, but at least no humans wrote it (:
I don't get it. It seems to be a great start to an interesting idea. I don't care if he wrote it using punch cards or a fever dream he induced by huffing paint, the source code is there
Seems like GP spent more time testing this than the author did
These are fairly common problems for newer apps in Android which has been changing quite a bit in the recent years. There are multiple ways to do "safe area" viewport stuff. It's reasonable to make these kinds of mistakes.