Hi All,
I know this is a fairly new device, but I was super keen to get it specifically to put cyanogenmod 11 on. After having some trouble with the current version of TWRP posted in another thread here on XDA (which only worked when the phone was in an "out of the box" state, requiring me to do a factory reset due to a mini android update that was automatically applied between reboots - resolved), I got the nightly release of CM11 which is listed as not having any issues, flashed it, and am having some issues.
The main problem I am experiencing is that regardless of which player I am using, if I open "Settings" from the status bar, whatever media I am playing goes silent. The player appears to still be playing, changing tracks, removing and reinserting headphones, clearing the playlist, re-opening the player...nothing fixes it. And then randomly some time later it will start making sound again if I leave the player running. Is there anyone else that can provide insight into this one? I have heard the problem is addressed for some in CM12, but that is not yet stable for our device.
Cheers.
I know this is a fairly new device, but I was super keen to get it specifically to put cyanogenmod 11 on. After having some trouble with the current version of TWRP posted in another thread here on XDA (which only worked when the phone was in an "out of the box" state, requiring me to do a factory reset due to a mini android update that was automatically applied between reboots - resolved), I got the nightly release of CM11 which is listed as not having any issues, flashed it, and am having some issues.
The main problem I am experiencing is that regardless of which player I am using, if I open "Settings" from the status bar, whatever media I am playing goes silent. The player appears to still be playing, changing tracks, removing and reinserting headphones, clearing the playlist, re-opening the player...nothing fixes it. And then randomly some time later it will start making sound again if I leave the player running. Is there anyone else that can provide insight into this one? I have heard the problem is addressed for some in CM12, but that is not yet stable for our device.
Cheers.
Aucun commentaire:
Enregistrer un commentaire