YHacker News
points by Aachen 2 days ago | hide | 0 comments
Huh? I get 500 Hz here on a Samsung from 2019 and make use of it regularly. Sensor frequency is one of the things I check before buying a new phone, surely newer Android versions haven't killed that with new api restrictions?!

Edit: no, it can't have. Then the phone sensor database would show that since it is built from submissions within Phyphox: https://phyphox.org/sensordb/

I'm not sure what problem you're running into (perhaps a very unusual phone that has only a 50 Hz accelerometer) but Android/Phyphox can do way more than 50 Hz

slow_typist2 days ago | | | parent | | on: 47740567
It is a Samsung a16 and it is just an observation I made, not a problem at all. If it was, I would try another installation source or even switch to a degoogled OS first to get more control over the hardware. Only thing I tried to get more samples was fiddling with the App restrictions. But it really doesn’t matter at all.
Aachen2 days ago | | | parent | | on: 47741577
The A16 gets 250~500 Hz according to Phyphox' database (depending on which A16 model you've got)

But I see Google indeed introduced another permission for this: https://developer.android.google.cn/develop/sensors-and-loca...

Curious that the database shows good rates but you're not seeing it in your instance. The device is from 2024 so it'll have shipped with this new restriction; the database submissions can't be from an older android version. Phyphox must declare that permission or else it shouldn't be in the database like that, but then you should also see higher rates in the app. So I don't get it but Android still can do more it seems, if an app is granted the new permission

slow_typist2 days ago | | | parent | | on: 47746967
Thanks for researching. Maybe I failed to give microphone access to phyphox which in my understanding of the source you pointed to limits sensor update rate. Sounds like me because I never grant access for anything I don’t plan to use.