I’m having an issue with wired headphones.
I’m having an issue with wired headphones. If I start listening to something (DoggCatcher, Play Music, white noise app), then navigate to the home screen, then away from the home screen the sound is muted.
From then on sound will only play if on the home screen (LL) and the screen is on. On the sound-generating app, time continues to elapse as if it were playing, and pressing the Home button will result in sound immediately being generated again.
I have verified through experimentation that this only happens when LL is running (i.e. merely switching to another default home screen will not fix the problem until I also reboot).
I don’t know what other information to provide, but will gladly do so. This is 100% repeatable for me with wired headphones, but I don’t think it has ever happened with bluetooth. I am on CM11 Nightlies (4.4.4) and this has been going on for a long time.
]]>« NINJA (Previous Post)
(Next Post) In v10.5b1 there was a specific feature added: “when creating shortcut to scripts, optional data can now be passed… »
D5 Creation
< ![CDATA[
Can you look under LLX’s settings-General, and report how Keep Lightning Running and Minimize Memory Usage is set?
I was thinking that maybe you could uncheck the KLR and check MMU and see if that makes any difference.
]]>
< ![CDATA[
Current settings:
Keep Lightning Running: checked
Minimize mem: unchecked.
I inverted them; no change immediately or after reboot.
I wonder if maybe the ‘Ok Google’ setting could be playing a part? Since it’s sound related. Will test and report back.
]]>
< ![CDATA[
Agreed, the only related thing is the “Ok Google” voice recognition. If this setting is off then you should consider looking at your CM nighties to see whether other have hit this issue. It looks a bit like the platform was handling audio focus incorrectly.
]]>
< ![CDATA[
So far it’s working great without “Ok Google” detection, which is fine by me; I don’t use it anyway. I’ll keep an eye on different versions of my ROM. It is worth noting that I haven’t encountered this issue on other homescreens (Apex or Trebuchet) but I’m up and running now so all good. 😀
]]>