Sounds turn off about android-app

[crogonint]

APPEARS to be fixed in 3.4. I.note that notification sounds share the sound device with Noice now, instead of interrupting it.

I'll let you know tomorrow if it fails overnight.

[crogonint]

I jumped the gun. Exact same issue this morning. I can't hear the sounds, even though they're still 'on' in the app. If I turn a sound off and back on, the audio turns back on.

[crogonint]

I think the volume is lowering over time. Every once in a while the volume... well, it wobbles around like someone is playing with the volume knob on a radio.

I had two repeatable effects happen this morning. I got a phone call before my alarm went off. Both the phone call and the alarm killed the volume of Noice, and didn't turn it back on. After the event, Noice remains muted. All of the individual sounds appear to be playing. I can click on/off for any one sound, and that sound appears to turn off, while the volumes of all of the other songs are instantly unmuted. Then I can click to turn the individual sound back on.

[crogonint]

Ok, now I can't repeat it. Now the sounds continue under the alarm going off, and they don't mute at all when the alarm goes off.

I think some event must be happening while the app is playing all night.

[ashutoshgngwr]

@crogonint Thanks for the details. I'll look into this.

[crogonint]

Happened again this morning. I was pleased to hear the sounds were still playing when I woke up, then after I got a phone call, they stayed off.

Say, I wonder if the mute function in Noice is timing out during extended operations.. Like me sleeping through my alarm. 🤣

[ashutoshgngwr]

@crogonint I missed this earlier. There may be two reasons for this.

1. Your alarm takes audio focus and Noice pauses itself. In this case the notification should show a resume button.
2. The device CPU goes to sleep because Noice doesn't hold wake locks. This was by design.

The former case is a design recommendation from Google to avoid clutter in audio playback by multiple apps. The latter should be solved in 0.8.x where introducing Google Cast forces us to device wake locks.

[crogonint]

That's amazing. So how does it keep the device awake all night if it's not using a wake lock? They really SHOULD have a low power setting which leaves the audio channel and etc. open. One of the main uses for these devices is as a music / mp3 player. - James T. Long

…

------------ There are 10 kinds of people in the world - those who understand binary, and those who don't.

On Tue, May 19, 2020 at 6:47 AM Ashutosh Gangwar ***@***.***> wrote: @crogonint <https://github.com/crogonint> I missed this earlier. There may be two reasons for this. 1. Your alarm takes audio focus and Noice pauses itself. In this case the notification should show a resume button. 2. The device CPU goes to sleep because Noice doesn't hold wake locks. This was by design. The former case is a design recommendation from Google to avoid clutter in audio playback by multiple apps. The latter should be solved in 0.8.x where introducing Google Cast forces us to device wake locks. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#112 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFSKADUZMOSIEU5FQRSSMNDRSJ5UJANCNFSM4LVUZGHA> .

[ashutoshgngwr]

@crogonint The documentation isn't clear on that. It is suggested that music players are required to acquire wake lock but Noice has been working fine until now (at least for me). I experimented with a few hours of continuous playback in earlier versions and it seemed to work without a hitch.

[crogonint]

Interesting

…

On Thu, May 21, 2020, 10:59 PM Ashutosh Gangwar ***@***.***> wrote: @crogonint <https://github.com/crogonint> The documentation <https://developer.android.com/topic/performance/vitals/wakelock#best_practices> isn't clear on that. It is suggested that music players are required to acquire wake lock but Noice has been working fine until now (at least for me). I experimented with a few hours of continuous playback in earlier versions and it seemed to work without a hitch. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#112 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFSKADUFM73DQSOYAQUZ3E3RSYBBZANCNFSM4LVUZGHA> .

[ashutoshgngwr]

#193 introduces use of WakeLocks to keep the device CPU awake during playback. Any potential problems related to this should resolved by that.

The issue will be automatically closed when #193 merges. If the issue persists after getting 0.8.0 updates, please re-open this.

[crogonint]

Not even gonna try to explain

Lol!