Find out below if your phone supports sonar.
The list is just general guidance. On your phone, sonar may behave differently. Please try it and let us know if it works (support@urbandroid.org, ideally send a debug log [Menu > Report a bug])!
Explanation:
- supported: A lot of Android phones are able to track sleep using ultrasound (sonar). The ones in the table below are confirmed to be working.
- partially – small signal strength: The device has been repeatedly used by a sufficiently large number of users, so it means that it a kind of works. But the signal strength that we measured is not very big so the sensitivity might be poor.
- partially – large average offset: The device has been repeatedly used by a sufficiently large number of users, so it means that it a kind of works. But many users set large volume offset which indicates that the device tends to produce audible artifacts.
- unsupported: The device has been tested by a sufficiently large number of users, and the signal strength tends to be very small. We are not certain that these devices do not work at all, but it is very likely that they perform poorly at the best.
Support | Device | Users Count | Median Signal Strength | Mean Volume Offset |
---|---|---|---|---|
Supported | Asus: ZenFone 2 Laser (ZE500KL) | 4 | 132.5 | 1.2 |
Supported | Sony: Xperia Z3 | 6 | 62 | 2 |
Supported | OnePlus: 3, OnePlus3 | 10 | 167.5 | 1 |
Supported | OnePlus: OnePlus 6 | 4 | 58.5 | 1.8 |
Supported | Samsung: Galaxy A3(2016) | 4 | 1150 | 0.5 |
Supported | Motorola: Moto G(4) | 4 | 314 | 1.5 |
Supported | Blackshark, LGE: Nexus 5X, Shark 1S | 41 | 749 | 1.2 |
Supported | Samsung: Galaxy Note9 | 10 | 1443.5 | 1.1 |
Supported | Samsung: Galaxy Note9 | 5 | 256 | 1 |
Supported | Samsung: Galaxy S8+ | 32 | 2292.5 | 1.4 |
Supported | Samsung: Galaxy S8+ | 19 | 2392 | 1.8 |
Supported | Samsung: Galaxy S8 | 55 | 2666 | 1.2 |
Supported | Samsung: Galaxy S8 | 16 | 1668.5 | 1.1 |
Supported | Asus: Nexus 7 (2013) | 5 | 118 | 1 |
Supported | Samsung: Galaxy Note8 | 21 | 2279 | 1 |
Supported | Samsung: Galaxy Note8 | 15 | 1638 | 1.7 |
Supported | LGE: LG G5 | 15 | 379 | 1.4 |
Supported | LGE: Nexus 5 | 21 | 502 | 1.4 |
Supported | Samsung: Galaxy S7 Edge, Galaxy S7 edge | 100 | 813 | 1.8 |
Supported | Samsung: Galaxy S7 Edge | 5 | 726 | 1 |
Supported | Samsung: Galaxy S7 Edge | 7 | 1732 | 1.9 |
Supported | Samsung: Galaxy S7 Edge | 7 | 1387 | 1.7 |
Supported | Samsung: Galaxy S7 Edge | 17 | 1894 | 1.8 |
Supported | Samsung: Galaxy S7 | 8 | 1192.5 | 1.9 |
Supported | Samsung: Galaxy S7 | 6 | 1794.5 | 1.7 |
Supported | Samsung: Galaxy S7 | 16 | 1010 | 1.3 |
Supported | Samsung: Galaxy J3(2016) | 5 | 180 | 1.4 |
Supported | Samsung: Galaxy S4 | 11 | 685 | 1.6 |
Supported | Motorola: DROID Turbo 2, Moto X Force | 4 | 566 | 1.8 |
Supported | Samsung: Galaxy S5 Dual SIM, Galaxy S5 | 27 | 760 | 1.2 |
Supported | Samsung: Galaxy S5 | 4 | 364.5 | 0.5 |
Supported | Samsung: Galaxy S5 | 8 | 463 | 1.2 |
Supported | Essential Products: PH-1 | 9 | 302 | 1 |
Supported | Samsung: Galaxy Note5 | 4 | 650 | 1 |
Supported | Samsung: Galaxy S7 Active | 5 | 2062 | 1.4 |
Supported | Motorola: Moto G Plus (5th Gen) | 7 | 96 | 0.7 |
Supported | Samsung: Galaxy S5 Neo | 4 | 119.5 | 1 |
Supported | Samsung: Galaxy S9+ | 17 | 3144 | 0.8 |
Supported | Xiaomi: Mi A1 | 13 | 195 | 2 |
Supported | Samsung: Galaxy Note4 | 10 | 994 | 1.3 |
Supported | Samsung: Galaxy Note4 | 7 | 381 | 1.6 |
Supported | Motorola: Moto X (2nd Gen) | 6 | 3588 | 0.7 |
Supported | Google: Pixel 2 | 15 | 374 | 1.9 |
Supported | Xiaomi: Redmi Note 5 Pro, Redmi Note 5 | 6 | 371.5 | 2 |
Supported | Samsung: Galaxy S6 Edge+, Galaxy S6 edge+ | 7 | 184 | 1.3 |
Supported | Samsung: Galaxy S6 | 4 | 365.5 | 1 |
Supported | Samsung: Galaxy S6 | 4 | 1054 | 1 |
Supported | Samsung: Galaxy S6 Edge, Galaxy S6 edge | 25 | 814 | 1.6 |
Partially – small signal strength | Sony: Xperia Z3 Compact | 7 | 32 | 1.3 |
Partially – small signal strength | OnePlus: OnePlus3T | 6 | 16.5 | 4.3 |
Partially – small signal strength | OnePlus: OnePlus5T | 6 | 37 | 2.3 |
Partially – small signal strength | LGE: V20 | 6 | 32.5 | 1 |
Partially – small signal strength | Samsung: Galaxy J5 Pro, Galaxy J5 | 4 | 21.5 | 3.8 |
Partially – small signal strength | LGE: LG G6, G6Fit | 4 | 41.5 | 1 |
Partially – small signal strength | Google: Pixel XL | 31 | 43 | 1.4 |
Partially – small signal strength | Xiaomi: Redmi Note 4 | 10 | 49.5 | 1.2 |
Partially – small signal strength | Google: Pixel | 27 | 39 | 1.6 |
Partially – small signal strength | Google: Pixel 2 XL | 38 | 24.5 | 2.7 |
Partially – large average offset | OnePlus: One | 35 | 1179 | 5.7 |
Partially – large average offset | Sony: Xperia Z1 Compact | 7 | 186 | 4.1 |
Partially – large average offset | Sony: Xperia Z5 Compact | 4 | 424 | 2.8 |
Partially – large average offset | Sony: Xperia Z5 | 8 | 288 | 3.1 |
Partially – large average offset | OnePlus: OnePlus3T | 6 | 16.5 | 4.3 |
Partially – large average offset | OnePlus: OnePlus5T | 6 | 37 | 2.3 |
Partially – large average offset | Samsung: Galaxy A5(2016) | 8 | 1629.5 | 3.6 |
Partially – large average offset | Samsung: Galaxy A5(2017) | 7 | 247 | 3.3 |
Partially – large average offset | Motorola: Moto Z Play, Moto Z Play Droid | 12 | 182.5 | 4 |
Partially – large average offset | Motorola: Moto Z (2) Play | 11 | 172 | 3.3 |
Partially – large average offset | LGE: LG G5 SE | 4 | 918.5 | 3 |
Partially – large average offset | Huawei: Nexus 6P | 62 | 454 | 3 |
Partially – large average offset | Motorola: Moto G(4) Plus | 15 | 139 | 3.9 |
Partially – large average offset | Motorola: Moto X Style, Moto X Pure Edition | 9 | 1129 | 2.3 |
Partially – large average offset | Google: Pixel 3 XL | 6 | 1295.5 | 7.5 |
Partially – large average offset | LGE: LG Stylo 4, QStylus | 4 | 93.5 | 3.5 |
Partially – large average offset | LGE: LG G3 | 10 | 552.5 | 2.2 |
Partially – large average offset | Xiaomi: Mi 5 | 10 | 62.5 | 2.8 |
Partially – large average offset | Motorola: Moto Z Droid, Moto Z | 10 | 355 | 2.8 |
Partially – large average offset | Motorola: Moto G4 Play | 8 | 361.5 | 2.6 |
Partially – large average offset | Samsung: Galaxy Note3, Galaxy Note3 Duos | 10 | 528 | 2.1 |
Partially – large average offset | Samsung: Galaxy J5 Pro, Galaxy J5 | 4 | 21.5 | 3.8 |
Partially – large average offset | Xiaomi: Mi A2 | 4 | 157 | 3.5 |
Partially – large average offset | Xiaomi: Redmi Note 3 | 10 | 78 | 3.5 |
Partially – large average offset | Xiaomi: Redmi 3S | 5 | 171 | 3.4 |
Partially – large average offset | Xiaomi: Redmi Note 4 | 5 | 103 | 3.6 |
Partially – large average offset | LGE: LG G4 | 25 | 193 | 3.3 |
Partially – large average offset | Motorola: Moto G (5) Plus | 4 | 161.5 | 3.8 |
Partially – large average offset | Xiaomi: Redmi 4X | 8 | 1288.5 | 3.4 |
Partially – large average offset | Motorola: Nexus 6 | 15 | 1725 | 3.3 |
Partially – large average offset | Samsung: Galaxy S9 | 9 | 2209 | 2.4 |
Partially – large average offset | Google: Pixel 2 XL | 38 | 24.5 | 2.7 |
Partially – large average offset | Xiaomi: Redmi 5 Plus | 5 | 197 | 2.2 |
Not supported | Asus: ZenFone 3 Max (ZC520TL) | 4 | 35 | 1.2 |
Not supported | Samsung: Galaxy S2 | 5 | 27 | 4.4 |
Not supported | Sony: Xperia XA2 | 5 | 27 | 3.8 |
Not supported | OnePlus: OnePlus5 | 45 | 29 | 3.2 |
Not supported | Samsung: Galaxy A3 | 7 | 31 | 4 |
Not supported | Samsung: Galaxy A5 | 6 | 7.5 | 1.7 |
Not supported | BlackBerry: KEYone, BlackBerry KEYone, Blackberry Keyone | 10 | 26.5 | 1.4 |
Not supported | Motorola: Moto G Google Play edition, Moto G (1st Gen) | 5 | 28 | 2.2 |
Not supported | Motorola: Moto X (1st Gen) | 5 | 33 | 0.8 |
Not supported | HTC: 10 | 5 | 35 | 0.6 |
Not supported | Samsung: Galaxy J1(2016), Galaxy J1 (2016), Galaxy J1 | 5 | 25 | 3.2 |
Not supported | Samsung: Galaxy J3(2017), Galaxy J3 Pro | 6 | 36.5 | 0.8 |
Not supported | Samsung: Galaxy J5(2016) | 34 | 31.5 | 2.3 |
Not supported | Samsung: Galaxy J7, Galaxy J7 V | 6 | 20 | 3.5 |
Not supported | Samsung: Galaxy J7 Pop | 4 | 36.5 | 1 |
Not supported | Samsung: Galaxy J7(2016) | 21 | 26 | 2.5 |
Not supported | Samsung: Galaxy A8+(2018) | 5 | 32 | 3.8 |
Not supported | Motorola: moto e5 play, moto e(5) play, moto e(5) cruise | 7 | 19 | 4.9 |
Not supported | Motorola: Moto E (4) Plus | 4 | 22.5 | 0.8 |
Not supported | Motorola: Moto E (4), Moto E4 | 4 | 8.5 | 1.2 |
26 thoughts on “Sonar – compatible devices”
Sonar works absolutely great on my Samsung Galaxy S7. There is just a slight issue which is that if I activate the Noise recording / Snore detection, the recording is composed mostly of the sonar continuous blips, and very little of the actual sound recording can be heard over that. Unlike operational sonar sound which is not heard as expected. Maybe in the future you could process the recording to digitally remove these continuous blips of fixed frequency, that would be great 🙂
Many thanks. We are working on a sonar redesign which will address mainly this issue. Hopefully we will be able to not get the artifact in the recordings in the first place 🙂
I have the S7 as well but the sleep record charts are off… (95% deep sleep… euh… I don’t think so!)
Does the orientation of the phone has anything to do with it…?
I also wireless charge… could that be the issue?
Says unsupported on my HTC 10
Sonar worked very well on my Samsung S5 (SM-G900I) but says not supported on my LG G6 (LG-H870K). Bug report sent as this is I’ve of the best features of this app.
Same here, HTC 10 reporting as not supported yet is on your list of supported devices.
Says unsupported on my galaxy s8+ ☹
Sonar works on my Doogee X5-max-pro. But I would like to know the best sonar setting. On 18-20 I get a signal of 50 but on 19 I get 150. Does 18-20 vary the setting automatically or is it better to specify a value that gives the biggest signal?
The best is to choose a setting that gives the least hearable artifacts. Regarding detection, they should all work, but some of them may be hearable on your hardware and some not.
It is supported on meizu mx4pro. There is the following idea: my device has a built-in audio chip, which has the ability to reproduce a frequency of 192,000 Hz. Operating system Flyme on the basis of Android. Not all players can use the output of sound through this chip. A vertex can use an audio chip. I thought maybe you could use this feature of the device to watch for breathing during sleep? (There are other devices with audio chips)
Hi Alexey, thanks for the idea. We are unable to implement such hardware specific features as that will quickly lead to maintenance hell on our side. Sorry about that but since the vast majority of phones do not have such capabilities, we don’t want to go this way.
It is supported on meizu mx4pro. There is the following idea: my device has a built-in audio chip, which has the ability to reproduce a frequency of 192,000 Hz. Operating system Flyme on the basis of Android. Not all players can use the output of sound through this chip. A PowerAmp can use an audio chip. I thought maybe you could use this feature of the device to watch for breathing during sleep? (There are other devices with audio chips)
Sonar appears to work well on my Google Pixel
Doesn’t work well for me. I try to test it and it says “Sonar NOT supported” “Signal strength: 12-48” even though it sometimes occasionally gets “Sonar is supported”
Hi, this signal strength is pretty low so the sonar would not work even if it sometimes says that sonar is supported…sorry about that.
Hello,
I have a fan in the room… would this affects the snoring detection?
P.S
I’m using SAA with galaxy note 4
We are making great improvements in the snoring detection, but every fan, every room and every snoring is different, so the easiest way to find out would be to try. Just one night of trying will tell you pretty much how it works for you.
睡眠噪音录下来的都是声纳的噪声,😯
Hello Zero,
many thanks for reporting the issue. On some devices the sonar sound which we produce can also get recorded through some feedback loop or may produce audible artifacts in lullabies or normal use.
We should have a workaround for this with our Sonar version 2 we are currently working on. The new method should not produce this kind of artifacts in recordings or playback. Would you be willing to test this out?
Please make sure to install the latest BETA version. If you are no already in the BETA group please opt-in here:
https://play.google.com/apps/testing/com.urbandroid.sleep
or install the APK from:
https://sleep.urbandroid.org/more/download/
Please go to Settings – Sleep tracking – Sensor: Sonar – Test sensor. After your signal strength gets detected, please use the switch right to the volume bar and choose F20 instead of F18-20, wait until signal strength gets detected again and see if sonar reacts ok to your movement. If there are any issues, please or you feel sonar is not that sensitive, please try F19 and than F18. Please let me know if this new setup does not produce any artifacts.
Reported compatible with the LG G3 (european version, D855)
I don’t understand, my blackview bv5000 worked fine with the solar until a month ago. Since then, it suddenly gave a flat line. When tried to test it, it suddenly says the device is not supported, although it already took records very well for about a year that I have this phone..
Hi, could you please try to restart the phone? Also make sure to test sonar at the highest volume. Also try to clean the mic/speakers, it’s a long shot but dust might have accumulated there, blocking some volume?
En las pruebas de la aplicación si funciona el sonar en mi ZTE Axon Mini, pero luego al monitorear el sueño sólo recoge los datos de MIBAND 2. Antes de tener la pulsera MIBAND 2 si funcionaba el sonar.
The app supports measuring with only 1 device at a time. It is not possible to use Miband and sonar at the same time.
Sonar is working perfectly with my Pixel 2 XL. Love to know how it works and if it can detect sleep apnoea. Is there a link you can point me to?
https://sleep.urbandroid.org/documentation/extended-features/apnoe/
Comments are closed.