Unreliable sounds on Android 10+ #62

New Issue

2019-09-30T17:31:17Z

b65535 commented

2019-09-30 17:31:17 +00:00

(Migrated from gitlab.com)

Edit: This issue has been resolved on versions of Android less than 10.

The start sound and the interval notification sounds don't work properly. These sounds are often delayed (from about half a minute, up to several minutes) or often not played at all. I can e.g. always reproduce the problems with 25 min sessions, 1 min intervals, and 10 seconds start delay. Usually, a missing interval notification sound is played instantly when I re-enable the display (if it was disabled), or if I actively use the smartphone.

I tried every combination of Android settings concerning battery optimizations, notifications, sounds and display I could think of (also hidden developer settings and hidden System UI tuner settings). I tried tons of combinations of settings in Meditation Assistant (e.g. length of intervals). I also tried cleaning the data and cache of Meditation Assistant and reinstalling the app. I also disabled or uninstalled each app which, in my opinion, could interfere with Meditation Assistant (e.g. bloatware apps).

Further things I tried:

Display on or off.
WLAN enabled or disabled.
With and without a connected recharger.
Silent mode or Do-not-disturb on or off.

Further things which might be worth mentioning:

Google Play Services and Google Services Framework are disabled.
The device runs without Google account.
Mobile data is disabled, i.e. access to the internet is only possible via WLAN.
Meditation Assistant runs without MediNET account.
Emerald Launcher is used as Android launcher app.

The sounds in a different meditation app (called Meditation Timer) work correctly. That's why I assume that the problem is a bug in Meditation Assistent itself.

Specs:

App: Mediation Assistant 1.5.6, installed via F-Droid. The sounds didn't work correctly in several previous versions, either.
OS: Android 7.0 (Nougat)
Device: Wiko Lenny 4, not rooted

The sounds in Meditation Assistant do work correctly on a different device (Sony Xperia X Compact, with Android 8.0, not rooted) which has enabled Google Play Services and Google Services Framework, which runs with Google account, which has enabled mobile data and which uses the default Android launcher app.

Edit: I also tried Meditation Assistant with a HUAWEI MediaPad T3 10 with Android 7.0. With that device, I hear the start sound (start delay 10 seconds) and the first two intervals (1 minute intervals) but no further interval notification sounds after that. Google Play Services and Google Services Framework are enabled on the HUAWEI device. Possibly, the sound problems may have something to do with Android 7.0, or with some app which affects Meditation Assistant which is installed on both the Wiko device and the HUAWEI device.

Edit2: Disabling Android's Doze feature via ADB shell until the next reboot (command: adb shell dumpsys deviceidle disable) doesn't help.

**Edit:** This issue has been resolved on versions of Android less than 10. The start sound and the interval notification sounds don't work properly. These sounds are often delayed (from about half a minute, up to several minutes) or often not played at all. I can e.g. always reproduce the problems with 25 min sessions, 1 min intervals, and 10 seconds start delay. Usually, a missing interval notification sound is played instantly when I re-enable the display (if it was disabled), or if I actively use the smartphone. I tried every combination of Android settings concerning battery optimizations, notifications, sounds and display I could think of (also hidden developer settings and hidden System UI tuner settings). I tried tons of combinations of settings in Meditation Assistant (e.g. length of intervals). I also tried cleaning the data and cache of Meditation Assistant and reinstalling the app. I also disabled or uninstalled each app which, in my opinion, could interfere with Meditation Assistant (e.g. bloatware apps). Further things I tried: * Display on or off. * WLAN enabled or disabled. * With and without a connected recharger. * Silent mode or Do-not-disturb on or off. Further things which might be worth mentioning: * *Google Play Services* and *Google Services Framework* are disabled. * The device runs without Google account. * Mobile data is disabled, i.e. access to the internet is only possible via WLAN. * Meditation Assistant runs without MediNET account. * *Emerald Launcher* is used as Android launcher app. The sounds in a different meditation app (called Meditation Timer) work correctly. That's why I assume that the problem is a bug in Meditation Assistent itself. **Specs:** - App: Mediation Assistant 1.5.6, installed via F-Droid. The sounds didn't work correctly in several previous versions, either. - OS: Android 7.0 (Nougat) - Device: Wiko Lenny 4, not rooted The sounds in Meditation Assistant *do* work correctly on a different device (Sony Xperia X Compact, with Android 8.0, not rooted) which has enabled *Google Play Services* and *Google Services Framework*, which runs with Google account, which has enabled mobile data and which uses the default Android launcher app. Edit: I also tried Meditation Assistant with a HUAWEI MediaPad T3 10 with Android 7.0. With that device, I hear the start sound (start delay 10 seconds) and the first two intervals (1 minute intervals) but no further interval notification sounds after that. *Google Play Services* and *Google Services Framework* are enabled on the HUAWEI device. Possibly, the sound problems may have something to do with Android 7.0, or with some app which affects Meditation Assistant which is installed on both the Wiko device and the HUAWEI device. Edit2: Disabling Android's Doze feature via ADB shell until the next reboot (command: *adb shell dumpsys deviceidle disable*) doesn't help.

b65535 commented

2019-09-30 17:34:19 +00:00

(Migrated from gitlab.com)

changed the description

b65535 commented

2019-09-30 20:46:27 +00:00

(Migrated from gitlab.com)

changed the description

b65535 commented

2019-10-01 17:26:35 +00:00

(Migrated from gitlab.com)

changed the description

tslocum commented

2019-10-30 00:46:28 +00:00

(Migrated from gitlab.com)

changed milestone to %1

tslocum commented

2019-10-30 00:48:05 +00:00

(Migrated from gitlab.com)

Thanks for including so much detail with your issue. It's helpful to know another app works properly. 1.5.6 includes every fix available to stop these issues except a method which may show an alarm clock icon in the status bar during the session. I avoided this in hopes that methods such as "setExactAndAllowWhileIdle" would work, but this appears to be the only remaining solution. Please let me know if this issue is resolved once 1.5.7 is released.

b65535 commented

2019-11-12 09:02:48 +00:00

(Migrated from gitlab.com)

Thank you for looking into this issue.

I tested it again with version 1.5.7 with my Wiko Lenny 4. I tested it with 1 and 5 minutes intervals. Here are the results:

There aren't any lost notification sounds anymore, as far as I can tell. That's a huge improvement compared to 1.5.6!
Unfortunately, the sounds are still often delayed. However, the delays seem to have become shorter, varying between about 2 to 10 seconds.
The sounds seem to be not delayed (i.e. the sounds are played reliably at the exact times) if I prevent the display from turning off in the Android display settings. Unfortunately, this is no permanent workaround because that would draw the battery quickly.

Concluding, 1.5.7 solved the problems partially.

Could you please look into the notification delays again? The notification sounds are 100% reliable in the other app I mentioned, i.e. this definitely must be an issue of Meditation Assistant, not a general problem of my phone.

Thank you for looking into this issue. I tested it again with version 1.5.7 with my Wiko Lenny 4. I tested it with 1 and 5 minutes intervals. Here are the results: * There aren't any lost notification sounds anymore, as far as I can tell. That's a huge improvement compared to 1.5.6! * Unfortunately, the sounds are still often delayed. However, the delays seem to have become shorter, varying between about 2 to 10 seconds. * The sounds seem to be not delayed (i.e. the sounds are played reliably at the exact times) if I prevent the display from turning off in the Android display settings. Unfortunately, this is no permanent workaround because that would draw the battery quickly. Concluding, 1.5.7 solved the problems partially. Could you please look into the notification delays again? The notification sounds are 100% reliable in the other app I mentioned, i.e. this definitely must be an issue of Meditation Assistant, not a general problem of my phone.

tslocum commented

2019-11-12 16:56:28 +00:00

(Migrated from gitlab.com)

Thanks again for providing so much detail, @b65535. I will look into the remaining sound delay issue.

tslocum commented

2019-11-14 01:29:52 +00:00

(Migrated from gitlab.com)

Could you please test whether long/large sound files cause a longer delay than shorter sounds? From what I can tell the only remaining delay could be the time it takes the device to load the sound. If it's inconsistent this may not be the issue.

b65535 commented

2019-11-16 08:25:15 +00:00

(Migrated from gitlab.com)

I tried it with a bigger sound file (1 minute, 5 MB, .wav) as interval sound. In my tests, the delay of the first interval sound was inconsistent. On one try it was about 2s, on the next one it was about 5s (with display turned off when the sound started). In my previous tests with a standard sound (which probably is smaller and maybe has a different sound format than WAV?) of Meditation Assistant, the delays were about between 2s and 10s.

Unfortunately, this doesn't prove much. The sound delay could be caused by the time the device needs to load the sound (which could be inconsistent because of current CPU usage, Android services running in the background, etc.). However, the sound delay could also be caused by delayed processing of notifications by Android if the displayed is turned off. Such delays could also behave inconsistently.

I haven't looked into the source code. Maybe it's already the case: Could the sounds be loaded only once (at some point before the user can start a session, maybe when the app is initialized) and only be played (and be reused) after that? If that solved the delays, the delays had been caused by the loading.

I tried it with a bigger sound file (1 minute, 5 MB, .wav) as interval sound. In my tests, the delay of the first interval sound was inconsistent. On one try it was about 2s, on the next one it was about 5s (with display turned off when the sound started). In my previous tests with a standard sound (which probably is smaller and maybe has a different sound format than WAV?) of Meditation Assistant, the delays were about between 2s and 10s. Unfortunately, this doesn't prove much. The sound delay could be caused by the time the device needs to load the sound (which could be inconsistent because of current CPU usage, Android services running in the background, etc.). However, the sound delay could also be caused by delayed processing of notifications by Android if the displayed is turned off. Such delays could also behave inconsistently. I haven't looked into the source code. Maybe it's already the case: Could the sounds be loaded only once (at some point before the user can start a session, maybe when the app is initialized) and only be played (and be reused) after that? If that solved the delays, the delays had been caused by the loading.

ghost1 commented

2019-12-08 16:08:22 +00:00

(Migrated from gitlab.com)

I am using a Samsung Galaxy S10e with Android 10 and version 1.5.7 of the app and would like to add that stop-sounds do not work at all if the display is turned off (which usually happens automatically after 30 seconds). Once the timer runs out, nothing happens. The moment I unlock the phone the stop-sound start to play.

tslocum commented

2019-12-09 00:14:03 +00:00

(Migrated from gitlab.com)

Thank you both.

@b65535 Yes that's possible. The next version will preload the sounds in case this is the issue.

@fwuestner It sounds like the app is being "optimized" even though the wake-up alarm is supposedly the type which will always fire on time. Please see this page for instructions on disabling the optimizations entirely for Meditation Assistant. Let me know if you are still running into this issue with battery optimizations disabled.

Thank you both. @b65535 Yes that's possible. The next version will preload the sounds in case this is the issue. @fwuestner It sounds like the app is being "optimized" even though the wake-up alarm is supposedly the type which will always fire on time. Please see [this page](https://blog.jasonantman.com/2019/04/galaxy-s10--android-9-alarm-app-broken-by-battery-optimization/) for instructions on disabling the optimizations entirely for Meditation Assistant. Let me know if you are still running into this issue with battery optimizations disabled.

ghost1 commented

2019-12-09 14:10:31 +00:00

(Migrated from gitlab.com)

@tslocum Sorry, I should have mentioned before that I have turned off all the battery optimizations (including the one that you have linked) for Meditation Assistant aleady.

tslocum commented

2019-12-12 04:25:05 +00:00

(Migrated from gitlab.com)

changed milestone to %2

shanemd commented

2019-12-18 21:12:15 +00:00

(Migrated from gitlab.com)

I can confirm some of these behaviors. End of session sounds do not play on my device when the screen is off, even after disabling battery optimization. The sound plays as soon as I unlock my device.

Funny story actually: I ended up having my longest meditation session in a while because the end of session sound didn't go off. Sat for 20 minutes after setting a 10 minutes session timer.

I'm happy to try other settings if that would be helpful in solving this issue. Right now I'm using a different timer but still recording sessions in this App.

Device info: Google Pixel running Android 10
App version: 1.5.7 installed from f-droid

I can confirm some of these behaviors. End of session sounds do not play on my device when the screen is off, even after disabling battery optimization. The sound plays as soon as I unlock my device. Funny story actually: I ended up having my longest meditation session in a while because the end of session sound didn't go off. Sat for 20 minutes after setting a 10 minutes session timer. I'm happy to try other settings if that would be helpful in solving this issue. Right now I'm using a different timer but still recording sessions in this App. Device info: Google Pixel running Android 10 App version: 1.5.7 installed from f-droid

tslocum commented

2019-12-20 16:35:42 +00:00

(Migrated from gitlab.com)

A possible fix for the ongoing issues with waking the device up is in place. Please let me know if you are still experiencing these issues with version 1.5.8 of the app.

ghost1 commented

2019-12-21 15:28:20 +00:00

(Migrated from gitlab.com)

I have just updated the app to version 1.5.8 but unfortunately, the issues remain (using a Galaxy S10e with Android 10).

b65535 commented

2019-12-28 17:24:27 +00:00

(Migrated from gitlab.com)

I tested 1.5.8. The delays have become shorter. I tested it with four 5 minute intervals:

Start sound: No delay. Played after 1min 30s as intended.
First interval sound: No delay, i.e. the interval took 5min.
Second interval sound: 2s delay, i.e. the interval took 5min 2s instead of 5min.
Third interval sound: 2s delay, i.e. the interval took 5min 2s instead of 5min.
Fourth interval sound: 2s delay, i.e. the interval took 5min 2s instead of 5min.
End sound: No delay. Played after 25 min as intended.

The app now works good enough on my Wiko Lenny 4 (Android 7.0). So I'd say, you can close this issue. If you do so, you should move the Android 10 problems to a different issue.

Thank you for the fixes.

I tested 1.5.8. The delays have become shorter. I tested it with four 5 minute intervals: * Start sound: No delay. Played after 1min 30s as intended. * First interval sound: No delay, i.e. the interval took 5min. * Second interval sound: 2s delay, i.e. the interval took 5min 2s instead of 5min. * Third interval sound: 2s delay, i.e. the interval took 5min 2s instead of 5min. * Fourth interval sound: 2s delay, i.e. the interval took 5min 2s instead of 5min. * End sound: No delay. Played after 25 min as intended. The app now works good enough on my Wiko Lenny 4 (Android 7.0). So I'd say, you can close this issue. If you do so, you should move the Android 10 problems to a different issue. Thank you for the fixes.

tslocum commented

2019-12-29 16:30:50 +00:00

(Migrated from gitlab.com)

Thanks @b65535, I am really glad to hear that. I will rename this issue to Unreliable sounds on Android 10+.

tslocum commented

2019-12-29 16:30:50 +00:00

(Migrated from gitlab.com)

closed

tslocum commented

2019-12-29 16:31:30 +00:00

(Migrated from gitlab.com)

changed title from Unreliable sounds to Unreliable sounds{+ on Android 10++}

changed title from **Unreliable sounds** to **Unreliable sounds{+ on Android 10++}**

tslocum commented

2019-12-29 16:31:30 +00:00

(Migrated from gitlab.com)

changed the description

b65535 commented

2020-01-03 07:10:58 +00:00

(Migrated from gitlab.com)

You should either have renamed the issue to "Unreliable sounds on Android 7" or you shouldn't have closed it.

tslocum commented

2020-01-03 15:12:54 +00:00

(Migrated from gitlab.com)

Thanks, I didn't mean to close this issue. Reopened.

tslocum commented

2020-01-03 15:12:55 +00:00

(Migrated from gitlab.com)

reopened

tslocum commented

2020-01-22 15:37:04 +00:00

(Migrated from gitlab.com)

I am fairly positive that anyone still experiencing issues is running a ROM which optimizes applications' battery usage even when the Android specification says not to. Meditation Assistant uses AlarmManager.setAlarmClock to set an alarm which wakes up the device, which clearly states it "will be allowed to trigger even if the system is in a low-power idle (a.k.a. doze) mode."

If you are experiencing these timer issues even on version 1.5.8+, you have a few options:

Set an alarm for the same time as your session just before starting it (this does not work around interval issues)
Write your device manufacturer complaining about this anti-specification behavior and hope for an update
Back everything up and flash an alternative ROM such as LineageOS/MicroG (if your device is supported and you may unlock its bootloader)
Buy or switch to another device running an alternative ROM

I'm sorry that there isn't more I can do/offer.

I am fairly positive that anyone still experiencing issues is running a ROM which optimizes applications' battery usage even when the Android specification says not to. Meditation Assistant uses [AlarmManager.setAlarmClock](https://developer.android.com/reference/android/app/AlarmManager#setAlarmClock(android.app.AlarmManager.AlarmClockInfo,%20android.app.PendingIntent)) to set an alarm which wakes up the device, which clearly states it "will be allowed to trigger even if the system is in a low-power idle (a.k.a. doze) mode." If you are experiencing these timer issues even on version 1.5.8+, you have a few options: - Set an alarm for the same time as your session just before starting it (this does not work around interval issues) - Write your device manufacturer complaining about this anti-specification behavior and hope for an update - Back everything up and flash an alternative ROM such as LineageOS/MicroG (if your device is supported and you may unlock its bootloader) - Buy or switch to another device running an alternative ROM I'm sorry that there isn't more I can do/offer.

tslocum commented

2020-01-22 15:38:42 +00:00

(Migrated from gitlab.com)

removed milestone

shanemd commented

2020-01-22 18:03:48 +00:00

(Migrated from gitlab.com)

Thanks for the update @tslocum.

Unfortunately this is still happening for me. I set a timer for 1 minute. Turned the screen off, and waited. The start sound went off at 15 seconds as expected, but the end sound didn't go off until I manually woke up the device, 3 minutes later.

I'm running 1.5.8 on incredibly stock hardware and software. Original Google Pixel with up-to-date Android 10 from Google via standard OTA update.

I double checked and made sure the 'Endless session' check box is NOT checked. I also checked to make sure battery optimization is OFF for this app. (It wasn't, but now it is and has the same behaviour)

Perhaps there's some information I can provide or tests that I can perform that will help us figure out what's going on? I'm a developer. I can hook up to adb or Android studio a grab logs too if that helps. I'm not super familiar with all the tools, but I'm willing and able to learn.

Thanks for all your work on this. This one seems particularly frustrating.

Thanks for the update @tslocum. Unfortunately this is still happening for me. I set a timer for 1 minute. Turned the screen off, and waited. The start sound went off at 15 seconds as expected, but the end sound didn't go off until I manually woke up the device, 3 minutes later. I'm running 1.5.8 on incredibly stock hardware and software. Original Google Pixel with up-to-date Android 10 from Google via standard OTA update. I double checked and made sure the 'Endless session' check box is NOT checked. I also checked to make sure battery optimization is OFF for this app. (It wasn't, but now it is and has the same behaviour) Perhaps there's some information I can provide or tests that I can perform that will help us figure out what's going on? I'm a developer. I can hook up to adb or Android studio a grab logs too if that helps. I'm not super familiar with all the tools, but I'm willing and able to learn. Thanks for all your work on this. This one seems particularly frustrating.

b65535 commented

2020-01-31 06:31:59 +00:00

(Migrated from gitlab.com)

You could try the following ADB command to disable some hidden battery optimizations until the next reboot of the device:

adb shell dumpsys deviceidle disable

You could try the following ADB command to disable some hidden battery optimizations until the next reboot of the device: *adb shell dumpsys deviceidle disable*

tslocum commented

2020-02-27 01:40:56 +00:00

(Migrated from gitlab.com)

Please also see https://dontkillmyapp.com if you are having issues with Meditation Assistant's timer.

ghost1 commented

2020-03-01 16:55:06 +00:00

(Migrated from gitlab.com)

Thank you for the link!
I have one quick question though. There are other third party timer apps out there that do not have this issue. I am not a developer, so I do not know the specifics and therefore please excuse any false assumptions, but why would they not have those issues? (Maybe they are using some (dirty) workarounds, which of course would'nt be a desirable solution?) Or to phrase this in a different way: Since they don't have these issues, there could be another solution?

Thank you for the link! I have one quick question though. There are other third party timer apps out there that do not have this issue. I am not a developer, so I do not know the specifics and therefore please excuse any false assumptions, but why would they not have those issues? (Maybe they are using some (dirty) workarounds, which of course would'nt be a desirable solution?) Or to phrase this in a different way: Since they don't have these issues, there could be another solution?

micressor commented

2020-04-30 08:24:58 +00:00

(Migrated from gitlab.com)

I still have this problem on

LineageOS 17.1 (Android 10)
Version v1.5.9

To disable battery optimization setting did not help.

A working workaround is the function Leave the screen on and dim it.

If wanted, I will submit a logcat.

I still have this problem on * LineageOS 17.1 (Android 10) * Version v1.5.9 To disable **battery optimization** setting did not help. A working workaround is the function **Leave the screen on and dim it**. If wanted, I will submit a logcat.

tslocum commented

2020-05-01 15:59:22 +00:00

(Migrated from gitlab.com)

Hey @micressor, thanks for updating. I would be glad to look over a logcat if you submitted it.

projectgus commented

2020-09-24 11:29:30 +00:00

(Migrated from gitlab.com)

mentioned in merge request !5

tslocum commented

2020-09-24 16:03:33 +00:00

(Migrated from gitlab.com)

mentioned in commit fe9da0c854

mentioned in commit fe9da0c85446c3e2ec1b4890b610006b6b8df0f6

tslocum commented

2020-09-24 16:12:26 +00:00

(Migrated from gitlab.com)

This should be resolved in version 1.6.1, thanks to @projectgus.

sinaforkamva commented

2021-04-03 05:56:15 +00:00

(Migrated from gitlab.com)

Hello,
I'm expriencing this issue on OnePlus with Android / OxygenOS 10. Bodhi Timer (another open source meditation app with do not disturb access) works fine. The funny thing is that current app works if I leave the screen on (from app's settings).
Hope you find a solution, because I like that I can set interval notifications in your app.

Hello, I'm expriencing this issue on OnePlus with Android / OxygenOS 10. Bodhi Timer (another open source meditation app with do not disturb access) works fine. The funny thing is that current app works if I leave the screen on (from app's settings). Hope you find a solution, because I like that I can set interval notifications in your app.

tslocum commented

2021-04-03 15:26:33 +00:00

(Migrated from gitlab.com)

Thanks for reporting your experience @sinaforkamva. Which version of Meditation Assistant are you running? Have you tried disabling battery optimizations for the app?

sinaforkamva commented

2021-04-07 08:20:08 +00:00

(Migrated from gitlab.com)

I'm on 1.6.3 and actually I didn't disable optimizations (I wasn't a good sport and skipped parts of the thread). I'll let you know if it works.

Update: yep, disabling optimizations fixed the problem. And I don't need to leave screen on (which in a dark room is not really pleasent).

I'm on 1.6.3 and actually I didn't disable optimizations (I wasn't a good sport and skipped parts of the thread). I'll let you know if it works. Update: yep, disabling optimizations fixed the problem. And I don't need to leave screen on (which in a dark room is not really pleasent).

Sign in to join this conversation.