Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] [Issue] Sound bug

OP pierro642

25th March 2014, 12:04 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Apr 2010
Hello,

Since I updated to 4.4.2-20140324-yuga, I face an annoying sound bug... (I skipped some updates so it was maybe from earlier).

When listening to music (spotify, appolo,...) the sound makes a sort of "metallic bzzz".

Checking on another forum (I already faced this problem on CM11 and that's why I came to Omni) I found that bumping the min cpu frequency from 384 to 486 seems to solve the problem.

It seems ok, but I don't like things I don't understand...

So does anyone have an explanation on ;
* Why does it appear now and not with the previous releases ?
* How does the cpu freq influence that sound glitch ?
* Is there another way to solve this problem ?

Thanks by advance !


Pierre
25th March 2014, 06:13 PM   |  #2  
Senior Recognized Developer
Flag Owego, NY
Thanks Meter: 24,801
 
13,532 posts
Join Date:Joined: Aug 2007
Donate to Me
More
Quote:
Originally Posted by pierro642

Hello,

Since I updated to 4.4.2-20140324-yuga, I face an annoying sound bug... (I skipped some updates so it was maybe from earlier).

When listening to music (spotify, appolo,...) the sound makes a sort of "metallic bzzz".

Checking on another forum (I already faced this problem on CM11 and that's why I came to Omni) I found that bumping the min cpu frequency from 384 to 486 seems to solve the problem.

It seems ok, but I don't like things I don't understand...

So does anyone have an explanation on ;
* Why does it appear now and not with the previous releases ?
* How does the cpu freq influence that sound glitch ?
* Is there another way to solve this problem ?

Thanks by advance !


Pierre

We pushed a pretty big kernel update Sunday.

The squashed commit for the update was on Gerrit https://gerrit.omnirom.org/#/c/5392/ and no one complained about this issue.

I'll look through the commits to see if maybe some codec commit caused an issue.
26th March 2014, 11:47 AM   |  #3  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Apr 2010
Thanks a lot for your feedback.

If it can help...
* I confirm that increasing min cpu freq to 486 solved the issue
* I had the same issue with CM11 with a big update at the early start of 2014.

Thks
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes