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?
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 have an xt1033 16GB Dual SIM Moto G. One day, it suddenly starting making strange high pitch noises (while on stand by).
Pressing volume up/down to get the phone to make the confirmation sounds sometime helped, or sometimes the issue disappeared after a restart.
However, in a few days, it got more and more often. The phone would either make high pitch noises or not make any sound at all.
Nothing related to sound worked any more.
So not even the camera, or watching a video on youtube or recorded by the camera. (This video cannot be played).
Of course calling also doesn't work.
I am wondering if maybe there will be some driver errors in the log ? But I don't know how to see the log.
What I tried so far:
- changed to a different ROM and/or resetted to factory defaults to eliminate any software issues.
- changed the 2 speakers
- removed the top right screw (this helped a lot, sometimes pressing and depressing that area made the phone to work). This last step seems to indicate the issue is related to something being loose, a cold contact somewhere on the motherboard. I inspected the motherboard but can't see a lot since the various chips are covered with metal.
Maybe the audio chip has a problem?
Any ideas? If I remove the screws now, play with the phone a bit and put it back except the top right screw it will probably work again for a few hours or days.
But maybe when the issue comes back, something is recorded in the log, like on a PC when you remove a hardware device?
Thank you!
Hello. It's my first time here and I need your help.
I've had this low budget tablet Colorovo CityTab Supreme 10.1'' for a while but Windows 8.1 were previously installed on it. Tablet was laggy, it would crash and it usually just lay arround in my drawer. It was literally unusable. But yesterday I decided to bring it back to life. I've installed android-x86-4.4-r3. And everything works just fine. But there is one problem, when I plug headphones, speakers do not turn off. Headphones and speakers work both at the same time. And it's really annoying. Personally, speakers are unnecessary for me completely, so I tried disabling those on boot menu but it disabled headphone jack as well. The only closest thing I was able to find on google that relates to my problem is here: groups[dot]google[dot]com/forum/#!topic/android-x86/Um50bmBFp7k but I don't know how to apply it. Do you have any ideas? Can you help me?
Edit. And volume up and down buttons seems to be in-active. I cannot change volume of speakers (or headphones).
OK here goes - if someone could help I'd really appreicate it...
Galaxy S7 Edge - light drop resulted in smashed screen. Did a screen/frame replacement myself... which worked a treat.
However have noticed that the loudspeaker now no longer works... So no ringtone, music on media play or alarm etc. Also did the *#o*# speaker test - again no sound on speaker (Receiver test on internal speaker is fine)... just the main external loudspeaker which has packed up.
Wondered if I'd blown/damaged during my screen install/phone drop - so I bought a new loudspeaker - but to no avail, still no sound.
So then I checked both my original & the freshly bought new speaker in both a multimeter and via hooking them up to another phone - BOTH UNITS WORKED! - So at least I know that the speaker units that I'm using are both fine. But put either back into my phone and no sound! ARRRGHHH
Have flashed (via Odin) G935FXXU1BPLB_G935FBTU1BPK3_BTU (v6.0.1 UK) - again no sound. Have additionally since let phone auto-update to 7.0 via OTA update - but again still no sound.
All other functions on phone are perfect (including listening to media/music via headphones).
Looking on web, I see a few people experiencing no sound since screen replacement and or flashing and I have tried the host of suggestions offered - everything from pause music and reboot, reboot with headphones in/out, toggle Power Save mode on/off, toggle Bluetooth on/off, clean out the headphone jack (sound works fine coming through headphone jack BTW just main speaker that wont play anything) and ensured speaker pads are definately contacting the mainboard pins etc.
The only thing I've not been able to yet try is "Emergency Software Recovery and initialization" via Smart Switch as Smart Switch simply freezes whenever I select this option (no follow up pop up window) - though phone is recogniosed.
Anyone else expericence this kind of no sound issue? or know of a sensible (cheap!) solution.
Regards
Mike
Think I've managed to find problem myself - if not solved it... sadly.
Used an old loudspeaker from a long since unused phone - soldered up a couple of wires to the terminals for ease of handling and turned on my phone - ran the speaker test (*#0*#) so continuous sound playing (if not heard!)... touching the wires from the bodged loudspeaker on the main PCB mainboard terminals got nothing, though then grounding one wire elsewhere and hey presto - sound once more from my phone!
So looking like a cold solder on the main PCB mainboard!... Reflowing is beyond me, so I now need to hunt around for a decent company who do PCB repairs!
Not quite the 'Have you tried wiping the cache' fix I was hoping for unfortunately... Not sure if PCB damaged in the drop or in the screen repair - but thought would post findings in case someone with exact same circumstances etc.
Regards
Mike