UWB Beacons Azimuth and Elevation Measurements on Android

[cheryl]

According to the Android UWB SDK, I should be able to see something like the below after connecting the beacons.

Device address prefix: 02:39:… Distance 0.99 m, Azimuth: -40.240578, Elevation angle: 18.97932
Device address prefix: 02:39:… Distance 0.86 m, Azimuth: -33.938553, Elevation angle: 57.48887
Device address prefix: 02:39:… Distance 0.49 m, Azimuth: -25.906908, Elevation angle: 29.65366

However, I’m constantly getting null for both Azimuth and Elevation angles (Distance is retrieving fine), provided that the beacon is “in front of the phone” with it being visible to the phone’s camera. I’m using a Samsung Galaxy S24+ for testing. Why is this the case?

[sdetweil]

you did update the firmware on the beacons with the newer android compliant version, right?

[jimiasty]

Cheryl,

can you share which Android version you are testing with?

Maybe you can also post the log content, so that we can see the distance measurements.
If you are getting distance computed then the only reason azimuth is not computed would be the orientation of the phone.

Ideal orientation is then UWB Beacons is in front of the phone as you would try to take a picture of it and have it visible in the camera viewport.

[cheryl]

Hi, thanks for getting back!

I ordered the beacons at the end of April this year, and I’m testing them with a Samsung Galaxy S24+ running Android 14 API 34. Below is my Logcat result.

Device address prefix: 10:4F:…, Distance: 0.89 m, Azimuth: null, Elevation angle: null

This is how I’m placing my phone. I’m using the camera as a reference here, but I had the app open in the foreground when I took the measurements.