Sleep as Android > Knowledge base > FAQ > Sonar – compatible devices

Sonar – compatible devices

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.
SupportDeviceUsers CountMedian Signal StrengthMean Volume Offset
SupportedAsus: ZenFone 2 Laser (ZE500KL)4132.51.2
SupportedSony: Xperia Z36622
SupportedOnePlus: 3, OnePlus310167.51
SupportedOnePlus: OnePlus 6458.51.8
SupportedSamsung: Galaxy A3(2016)411500.5
SupportedMotorola: Moto G(4)43141.5
SupportedBlackshark, LGE: Nexus 5X, Shark 1S417491.2
SupportedSamsung: Galaxy Note9101443.51.1
SupportedSamsung: Galaxy Note952561
SupportedSamsung: Galaxy S8+322292.51.4
SupportedSamsung: Galaxy S8+1923921.8
SupportedSamsung: Galaxy S85526661.2
SupportedSamsung: Galaxy S8161668.51.1
SupportedAsus: Nexus 7 (2013)51181
SupportedSamsung: Galaxy Note82122791
SupportedSamsung: Galaxy Note81516381.7
SupportedLGE: LG G5153791.4
SupportedLGE: Nexus 5215021.4
SupportedSamsung: Galaxy S7 Edge, Galaxy S7 edge1008131.8
SupportedSamsung: Galaxy S7 Edge57261
SupportedSamsung: Galaxy S7 Edge717321.9
SupportedSamsung: Galaxy S7 Edge713871.7
SupportedSamsung: Galaxy S7 Edge1718941.8
SupportedSamsung: Galaxy S781192.51.9
SupportedSamsung: Galaxy S761794.51.7
SupportedSamsung: Galaxy S71610101.3
SupportedSamsung: Galaxy J3(2016)51801.4
SupportedSamsung: Galaxy S4116851.6
SupportedMotorola: DROID Turbo 2, Moto X Force45661.8
SupportedSamsung: Galaxy S5 Dual SIM, Galaxy S5277601.2
SupportedSamsung: Galaxy S54364.50.5
SupportedSamsung: Galaxy S584631.2
SupportedEssential Products: PH-193021
SupportedSamsung: Galaxy Note546501
SupportedSamsung: Galaxy S7 Active520621.4
SupportedMotorola: Moto G Plus (5th Gen)7960.7
SupportedSamsung: Galaxy S5 Neo4119.51
SupportedSamsung: Galaxy S9+1731440.8
SupportedXiaomi: Mi A1131952
SupportedSamsung: Galaxy Note4109941.3
SupportedSamsung: Galaxy Note473811.6
SupportedMotorola: Moto X (2nd Gen)635880.7
SupportedGoogle: Pixel 2153741.9
SupportedXiaomi: Redmi Note 5 Pro, Redmi Note 56371.52
SupportedSamsung: Galaxy S6 Edge+, Galaxy S6 edge+71841.3
SupportedSamsung: Galaxy S64365.51
SupportedSamsung: Galaxy S6410541
SupportedSamsung: Galaxy S6 Edge, Galaxy S6 edge258141.6
Partially – small signal strengthSony: Xperia Z3 Compact7321.3
Partially – small signal strengthOnePlus: OnePlus3T616.54.3
Partially – small signal strengthOnePlus: OnePlus5T6372.3
Partially – small signal strengthLGE: V20632.51
Partially – small signal strengthSamsung: Galaxy J5 Pro, Galaxy J5421.53.8
Partially – small signal strengthLGE: LG G6, G6Fit441.51
Partially – small signal strengthGoogle: Pixel XL31431.4
Partially – small signal strengthXiaomi: Redmi Note 41049.51.2
Partially – small signal strengthGoogle: Pixel27391.6
Partially – small signal strengthGoogle: Pixel 2 XL3824.52.7
Partially – large average offsetOnePlus: One3511795.7
Partially – large average offsetSony: Xperia Z1 Compact71864.1
Partially – large average offsetSony: Xperia Z5 Compact44242.8
Partially – large average offsetSony: Xperia Z582883.1
Partially – large average offsetOnePlus: OnePlus3T616.54.3
Partially – large average offsetOnePlus: OnePlus5T6372.3
Partially – large average offsetSamsung: Galaxy A5(2016)81629.53.6
Partially – large average offsetSamsung: Galaxy A5(2017)72473.3
Partially – large average offsetMotorola: Moto Z Play, Moto Z Play Droid12182.54
Partially – large average offsetMotorola: Moto Z (2) Play111723.3
Partially – large average offsetLGE: LG G5 SE4918.53
Partially – large average offsetHuawei: Nexus 6P624543
Partially – large average offsetMotorola: Moto G(4) Plus151393.9
Partially – large average offsetMotorola: Moto X Style, Moto X Pure Edition911292.3
Partially – large average offsetGoogle: Pixel 3 XL61295.57.5
Partially – large average offsetLGE: LG Stylo 4, QStylus493.53.5
Partially – large average offsetLGE: LG G310552.52.2
Partially – large average offsetXiaomi: Mi 51062.52.8
Partially – large average offsetMotorola: Moto Z Droid, Moto Z103552.8
Partially – large average offsetMotorola: Moto G4 Play8361.52.6
Partially – large average offsetSamsung: Galaxy Note3, Galaxy Note3 Duos105282.1
Partially – large average offsetSamsung: Galaxy J5 Pro, Galaxy J5421.53.8
Partially – large average offsetXiaomi: Mi A241573.5
Partially – large average offsetXiaomi: Redmi Note 310783.5
Partially – large average offsetXiaomi: Redmi 3S51713.4
Partially – large average offsetXiaomi: Redmi Note 451033.6
Partially – large average offsetLGE: LG G4251933.3
Partially – large average offsetMotorola: Moto G (5) Plus4161.53.8
Partially – large average offsetXiaomi: Redmi 4X81288.53.4
Partially – large average offsetMotorola: Nexus 61517253.3
Partially – large average offsetSamsung: Galaxy S9922092.4
Partially – large average offsetGoogle: Pixel 2 XL3824.52.7
Partially – large average offsetXiaomi: Redmi 5 Plus51972.2
Not supportedAsus: ZenFone 3 Max (ZC520TL)4351.2
Not supportedSamsung: Galaxy S25274.4
Not supportedSony: Xperia XA25273.8
Not supportedOnePlus: OnePlus545293.2
Not supportedSamsung: Galaxy A37314
Not supportedSamsung: Galaxy A567.51.7
Not supportedBlackBerry: KEYone, BlackBerry KEYone, Blackberry Keyone1026.51.4
Not supportedMotorola: Moto G Google Play edition, Moto G (1st Gen)5282.2
Not supportedMotorola: Moto X (1st Gen)5330.8
Not supportedHTC: 105350.6
Not supportedSamsung: Galaxy J1(2016), Galaxy J1 (2016), Galaxy J15253.2
Not supportedSamsung: Galaxy J3(2017), Galaxy J3 Pro636.50.8
Not supportedSamsung: Galaxy J5(2016)3431.52.3
Not supportedSamsung: Galaxy J7, Galaxy J7 V6203.5
Not supportedSamsung: Galaxy J7 Pop436.51
Not supportedSamsung: Galaxy J7(2016)21262.5
Not supportedSamsung: Galaxy A8+(2018)5323.8
Not supportedMotorola: moto e5 play, moto e(5) play, moto e(5) cruise7194.9
Not supportedMotorola: Moto E (4) Plus422.50.8
Not supportedMotorola: Moto E (4), Moto E448.51.2

26 thoughts on “Sonar – compatible devices”

  1. 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 🙂

    1. 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 🙂

    2. 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?

  3. 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.

  6. 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?

    1. 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.

  7. 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)

    1. 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.

  8. 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)

    1. 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”

    1. 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.

    1. 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.

  13. 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..

    1. 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?

  14. 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.

Comments are closed.