All,
I noticed a couple possible defects after upgrading to 3.1 manually.
1. When playing audio from certain applications (XMP for Android for instance) The Audio cuts out shortly after the screen turns off, and then halts for a period of time before coming back shortly, then cuts out again.
2. Once you turn the screen back on, there is a distinct crackling in the audio.
Workaround:
1. Turn screen back on (get the crackling)
2. Unplug the 3.5mm audio jack
3. Play music from the speakers
4. Plug back in the 3.5mm audio jack
Anyone else seeing these issues with other audio applications?
Yep, I had the crackling and long pauses start happening today after the FOTA update.
Seems to happen (more often?) when applications interrupt an audio stream. For instance, listening to music and get an IM or email.
Yeah I had issues with this as well afer updating to 3.1...I saw in another thread that doing a "hard reboot" will fix the issue and has seemed to work for me so far. Hold the power button down for 10-15 sec until the unit reboots.
same problem
I have the same problem as well. The audio stops functioning properly when the screen times out or when I lock the device with the power button. The weird thing is that this behaviour is not consistent for all apps.
For example, "Music" stops only at the end of the song. From the "3.1 ROM issues" thread, other users are experiencing this as well. In contrast, in the apps "Listen" and "Audible", almost as soon as the screen goes off or I lock it, the audio stops, starting after some 30 seconds, halting again after 10 seconds. It repeats this cycle a few times and then stops completely. If I lit the screen by hitting the power button, the audio resumes with crackling noises as mentioned in the original posts.
Also, hard reset didn't work. I am tempted to do a factory reset except that I don't really know what's going on and I don't know if that'd fix it!
UPDATE: I found the following workaround solutions:
1- Winamp works flawlessly for songs, not a peep or hitch!
2- BeyondPod is working fairly well for podcasts. (It has paused once after 11 minutes so far.)
I did the fota update.
and I've the the crackling. Sucky.
me too. Hope they get an update out to fix this asap. Extremely annoying bug.
Would like to add I am also experiencing this issue although mine didn't start till a couple days after the update to 3.1. A hard reset works for a little while but the issue eventually presents itself again. Might be due to a caching issue with the music player?
Anyone try another music player?
I discovered the crackling noise problem last night.
At first I thought the FLAC songs were recorded from a dirty vinyl record.
I also discovered the problem where the Music app does not continue to the next song when listening with the screen turned off. How stupid is that.
These are two big problems that ASUS needs to address ASAP.
I am already annoyed by the pop sound when turning the Transformer on and whenever any sound to the speaker (Headphones are fine) is played after a long pause.
They must have used a really cheap sound chip in the Transformer.
Yes I can confirm the same problems with google listen. Have tried the hard reset but it doesn't really help very much. Things worked fine after the restart, but as soon as the screen turned off, then the audio paused, and began to crackle, then more pauses. It is almost as if some part of the system is in some sort of low power mode and is not able to feed the data at the required data rate...
gloomyandy said:
... It is almost as if some part of the system is in some sort of low power mode and is not able to feed the data at the required data rate...
Click to expand...
Click to collapse
I believe this could be exactly the problem. I have not yet gotten my TF, but looking forward to one greatly. However, I get exactly this problem on my Galaxy Tab 7" WHEN using setCPU to add a profile that scales the CPU down when screen is off. It sounds to me as if ASUS has added some sort of governer/scaling that does this. I could be wrong of course This is just based on reading, and personal experience
corodius said:
I believe this could be exactly the problem. I have not yet gotten my TF, but looking forward to one greatly. However, I get exactly this problem on my Galaxy Tab 7" WHEN using setCPU to add a profile that scales the CPU down when screen is off. It sounds to me as if ASUS has added some sort of governer/scaling that does this. I could be wrong of course This is just based on reading, and personal experience
Click to expand...
Click to collapse
Yes. I get a lot of weird little problems with the Tab 7'' when setCPU scales clock speed down too far, including random reboots. I guess that's the sacrifice Asus made to give the TF such a tremendous battery life.
grainysand said:
I guess that's the sacrifice Asus made to give the TF such a tremendous battery life.
Click to expand...
Click to collapse
I don't know about "tremendous"
More like pretty good...
i can confirm that i have this issue using google music app. I previously purchased PowerAMP (arguably the best android music app) and no problems whatsoever when the screen goes off.
I do like the google music app as it seems like a truly lightweight player but its still in beta stage and needs a bit of work.
I just discovered something. The problem does not occur for my Transformer when the unit is plugged in!
So it must be power management problem, the question is how to fix it?
Hey guys, loving the xda forums btw, much love. I have a acer iconia a500 16gb, and same problem here:
Using Acer_a500_4.010.13_com_gen2
The default Music player is buggy and crashed fairly often, the audio stopping when screen turns off and stopping intermittently is also present on iconia with the default music player and the others as well.
The audio crackling is also present under same conditions.
To add insult to injury, sometimes when i connect a headphones the speakers dont turn off. And if i play with he "dolby mobile" settings, the sound on my headphones get really tinny untill i unplug the headphones and plug them back in, or i reboot the sys in some cases.
I just thought I should add to this thread that I have the same problems on my Acer Iconia A500. It consistently only finishes the song after I turn the screen off then it waits MINUTES to start the next song. I only occasionally have problems with the crackle sound. I had the crackling a lot when I first got it but it doesn't seem to happen as often any more. It doesn't seem to happen when I use doubleTwist but I really wish that the STOCK APPLICATION (which I like the best) would work...
Is there ANY way to fix this stuff? I mean even downgrading to like 3.0 or something. I like to use my tablet to play on my stereo system and I don't enjoy having to effing go back every time I want to play the next song. I also don't want to leave the screen on all the time and murder the battery.
I have the same thing happening on my A500 (running the ASUS PRIME ROM, though). When the screen turns off, anything audio related gets really skippy.
apparently there's some sort of setting build in for the cpu to underclock to the point of not being able to continue running the music application when the screen turns off. (that's me guessing it could be wrong) It always happens with stock music app though it didnt happen when in 3.0.
I installed winamp and doubletwist and both played nonstop.
Also i noticed that if you had music in your external sd and you open music app (also happened with winamp) and remove the sd the applications wont work anymore (thy always fc)unless you install the sd back (that is if you had your music library in the sd even if you also have it internally)
I tried moving the music to the internal storage but the error persist. the only way to get rid of it is formatting the tablet and passing the music to the tablet before running the apps. However if you install the sd and you happen to have music and music app open, youre screw again.
thats the error ive been having and im stuck with a 16gb sd in the tablet to hear music, (which i find it sucking cause my tablet is 32gb)
any suggestions?
I am having issues with my audio, as in audio playback music, youtube, etc.. it seems to simply not work for some reason on and off, a reboot fixes it or just waiting til the next time you want to use audio. i am trying to link it with an another event.. 2 things i am noticing it may be, after the phone switches networks HSPA to LTE the other event is maybe it only happens when i start the audio from the new lock screen controls..
Haven't noticed anything yet, I streamed music on the 30 minutes to work and had no issues this morning.
Also having some insane issues using Play Music and usually the lock screen controls. Say I hit the next button on the lock screen, it will change and just sit there. Unlocking the phone shows that the playback seems to be taking place (a few moments later) because the button changes to pause and song time starts moving. No audio though. Switching songs sometimes fixes it, but I had an issue this morning where not even system audio worked until I rebooted the phone.
Hi folks. I have a 16GB US GSM Moto G, and yesterday, the character of my device's external speaker changed.
Formerly, to get a good average sound level in apps, the volume needed to be near the high end, I'd say about 60-80% of max. Now, that same volume level corresponds to about 20-40% on the slider. At the same time, I started to get weird sound artefacts in one app (Tiny Death Star). I hear a light popping sound in the speaker about once per second, and every couple of seconds the sound stutters. Not terrible, but enough to be distracting. It doesn't affect all apps, but I haven't tested extensively to see if it's the only app affected.
There are a couple of variables:
1. Yesterday I installed the KitKat OTA update. I'm about 80% sure that the issue didn't start immediately after that, but I can't be positive.
2. I played with a couple of music player apps: WinAmp and PowerAmp. In the latter, I did mess around with some EQ/volume/balance settings, but I left everything where I found it. Once I noticed the new issue, I uninstalled both and rebooted the device, but the problem persists.
I also noticed the "Audio Effects" setting in the Sound settings. Tried turning that off, but it didn't change anything. I also tried wiping the cache partition; no change.
Anyone have any idea what may have caused this (and more importantly, how to fix it)? I could live with the volume range change, but not so much the stutter/pop.
I know Pixel 2 bluetooth problems have been discussed here and elsewhere ad nauseam, but I honestly haven't found anyone else experiencing the problem I'm having. Or really even close. None of this was an issue with my Nexus 6P, which I just replaced.
First problem: Audio programs mute between tracks. The phone thinks it's playing them, but it isn't. Take Pandora. A few songs will play fine, then one will end, and suddenly it'll go mute when the next song starts. I'll notice no sounds playing, and I'll look down to see it think it's playing, but with no sound. If I pause and hit play again, the sounds start up until the next song, when it does the same thing. This happens with every audio program I've tried EXCEPT Google Play Music, which works fine. It also sometimes works for 4-5 songs before tanking.
Second problem: notification noises suffer the same fate. I'll have Google Play Music going (which works), and it'll just cut out for a second). That's the notification buzz, which silences the music but doesn't actually play anything. Obviously I can't use the play/pause test to see if that fixes this.
I'm using Soundpeats Q16 true wireless. I unfortunately don't have much else with which to test this. I'd blame Soundpeats, but they worked great on my 6P, and the bluetooth problems with the P2 make me think it's not on Soundpeats here.
I've messed around with the Developer options, and I THINK that setting the Playback Quality to anything steady (330kbps, 660kpbs, or 990 kbps) fixes it. The problem is that that, and the other Bluetooth developer options, all reset on me almost immediately, so that's tough to prove. I have also tried messing around with Tasker, whose sounds also wind up muted.
So one question I'd have would be: is there a way to make those developer options stick?
Second question would be: anybody else in this boat?
I have tried both re-pairing and factory resetting the headphones, several times.
Anyone having audio issues with bluetooth?
It constantly cuts out, stops playing, disconnects, etc.
I've turned off battery optimiser for YoutTube Music and bluetooth. I've tried a few speakers, they all have the same issue.
Someone with a similar issue on reddit suggested turning off wifi. Doesn't work.
It's a strange bug, in that it is inconsistent.
Sometimes the music player will pause, other times it will just keep playing the track, but no sound will come out of the speaker. Other times, it'll stop playing, then when it starts again, the volume will be re-set to a lower setting.
It's doing my head in. I wish I could flash a custom ROM and be done with MIUI, but they all look buggy.
cubic25 said:
Anyone having audio issues with bluetooth?
It constantly cuts out, stops playing, disconnects, etc.
I've turned off battery optimiser for YoutTube Music and bluetooth. I've tried a few speakers, they all have the same issue.
Someone with a similar issue on reddit suggested turning off wifi. Doesn't work.
It's a strange bug, in that it is inconsistent.
Sometimes the music player will pause, other times it will just keep playing the track, but no sound will come out of the speaker. Other times, it'll stop playing, then when it starts again, the volume will be re-set to a lower setting.
It's doing my head in. I wish I could flash a custom ROM and be done with MIUI, but they all look buggy.
Click to expand...
Click to collapse
Yes I am facing this problem when I connect to my Bluetooth speaker
It's only doing it with certain apps.
YT music is worst, followed by Radioapp. It doesn't do it with the triple J app, (another Radio station here in Aus). In saying that, the triple J app consumes the most battery, so maybe it has something to do with MIUI's ****ty battery optimising, even though I have disabled it for those apps.