Related
Hello all,
I've been using CM7.1 and 7.2 Temasek's KANG for quite some time now, and it's working great.
I do have one annoying problem: when I use Navigon and enter a route, I get voice directions. After the voice stops speaking, you can hear the speaker being for a few seconds (hissing noise) and then the speaker shuts off. No problem there.
However, at random the speaker starts making (quite loud) 'popping sounds' at random intervals. The voice isn't trying to say anything at that time. Often it pops 3-4 times in a row, then it's quiet for several minutes.
If I use DSP Manger and select either option (enhance bass or the equalizer), then the 'popping'-sounds changes into a soft (old dial-up) modem-kind of sound. It's not very loud but you can hear it. It usually stops by itself, or it stops after so turn the volume up/down - and then it stops because of the 'beep' the speaker makes when changing the volume, not because of the volume change itself.
This does not happen on stock firmware. So it seems Navigon is 'leaking' sound somehow and with stock firmware that 'leaking' is just ignored and with CM it is turned into one sound (popping) or the other (modem-like). Since it can be affected with the DSP Manager, I'm also hoping there is some solution that can be applied or some work-around. Any suggestions would be greatly appreciated.
Do you still have the problem - or found a solution for it?
Im using mapfactor navigator and get all 3-4seconds a noisy sound, sometimes also in other apps. Somewhere i read its because 2 apps are using the sound chip, but i don't know if the problem is caused by cyanogenmod 7.2 or hardware issue :/ Im using android since 6 days and the first i did was flashing cyanogenmod
No, I'm sorry, I haven't found a solution. It does seem to be related to CM 7.2 however, I didn't have this on stock.
I'm running xron cm7 on my touchpad. I've noticed a few things about sounds that I wonder if it's just a fact of life or something that's fixable. 1-I can't seem to get sound to come from the headphone jack. If I plug something in, sound stops from the speakers but nothing comes out via the jack. 2-If I have an app that plays sounds even with the screen off, it gets this kind of high pitched squeal/feedback. This is happening with music apps and the AmbiSci sound apps. Are both of these facts of life on a touchpad running Android?
Do any ROMS currently allow the front facing camera to work?
NapalmDawn said:
I'm running xron cm7 on my touchpad. I've noticed a few things about sounds that I wonder if it's just a fact of life or something that's fixable. 1-I can't seem to get sound to come from the headphone jack. If I plug something in, sound stops from the speakers but nothing comes out via the jack. 2-If I have an app that plays sounds even with the screen off, it gets this kind of high pitched squeal/feedback. This is happening with music apps and the AmbiSci sound apps. Are both of these facts of life on a touchpad running Android?
Do any ROMS currently allow the front facing camera to work?
Click to expand...
Click to collapse
Camera still does not work.
To get sound on earphones, plug them in before starting the app you want to listen to. That works for me.
The distorted sounds have been reported by many, I guess I'm lucky, I don't have that problem.
chicle_11 said:
Camera still does not work.
To get sound on earphones, plug them in before starting the app you want to listen to. That works for me.
The distorted sounds have been reported by many, I guess I'm lucky, I don't have that problem.
Click to expand...
Click to collapse
Thanks Chicle I'll try that out. Maybe it's a rom thing for the distorted sound. Which one are you using?
NapalmDawn said:
Thanks Chicle I'll try that out. Maybe it's a rom thing for the distorted sound. Which one are you using?
Click to expand...
Click to collapse
I'm using Cherry Kang, with kupdate kernel. Oc to 1.7 max and 384 min.
Sometimes I use the unofficial cyanogenmod nightlies, when cherry has not been updated for a while.
Unfortunately, the distorted sound has been reported on a bunch of different roms.
I use the nightlies, and before that Alpha2, and haven't had a problem with sound - I watch stuff with MXPlayer, listen to Spotify, and everything, with and without headphones, no problems at all. Currently on the 20120402 nightly, still working great for sound.
As for Camera, well, we gotta wait for HP to release the sources for it, unfortunately. It's not something that's fixable until then. If you need a camera, you gotta use WebOS.
Earphone trick worked great. The sound thing is odd. I didn't get the scratchy sounds when I would plug the headphones in, turn on the AmbiSci app, pull up a sound and then turn off the screen. If I do the same with just the speakers running though, scratchy sounds. Makes me think it could be more hardware related than software.
Well . . this is even weirder. I have the volume down a little low. If I raise up the volume, I hit a part where the squeal starts. That seems strange.
I bought an HTC One a few months ago and am quite enjoying it, I recently installed CM10.2 and have come across this problem. Whenever the speaker turns on to play a sound, it makes a popping sound when the speaker turns off. It does this every time I press something like a menu on the device. People have suggested turning off beats audio but I cannot seem to find the menu for it in settings (but I could when I was on stock).
Any help would be appreciated
I don't think that CM has a beats audio option. I've only seen it in GPe based ROMs.
bump
I updated to the latest nightly and it still isn't fixed
I would like to know how audio processing in Android works.
For the last three months I've tried out many different ROMs for the Xiaomi Mi 3. One of the most important aspects of a ROM for me is the headphone sound quality, since I use my device most for listening music on my Shure SE215's. I have noticed that there is a huge different in headphone sound between ROMs. MIUI kitkat sounds nothing like Cyanogenmod 12.1, which sounds nothing like Cyanogenmod 13.0, which sounds nothing like Mokee 6.0.1. In my opinion my headphones sound best with Mokee 6.0.1. No muddy lows or an unpleasant harsh sound, but a nicely balanced sound with especially the mids and highs sounding gorgeous and way better than CM13.0 which is my daily driver at the moment. What does a ROM do to an audio file before sending a direct signal to the earphone? Does the kernel play a role? I'm not interested in speaker sound, only headphones. And is it possible to export whatever makes Mokee 6.0.1 sound so good to Cyanogenmod 13.0?
Help me out here!
why not just use viperfx and tweak it how you like?
Tried that first thing, but it somehow heavily increased ambient noise. Everything worked properly in Viper, but no matter how much I tweaked it, I wasn't able to get the sound Mokee produces. There was also a profile for my particular in-ear monitors that's supposed to make it compensate and sound flat, but that really decreased the sound stage a lot. Might be that Viper4Android induces a phase shift or increases audio latency. I'm not familiar with the terms that audiophiles use, so I have no idea how to describe the change in sound (even if the frequency response is similar). I also tried using AudioFX which is built into Cyanogenmod to equalize it to a sound signature I prefer, but whatever I do. I can't get it to sound similar to Mokee. Cyanogenmod sounded the same as Mokee about a month ago, but then the sound drivers for the Mi 3 got all messed up when they imported the Dirac profiles from MIUI, which probably just adds a huge load of post processing to the audio and adds some bass and whatever most people like, but it annoys me a lot. So I guess my last option to get a nice headphone experience is to unpack Cyanogenmod, replace the audio files and libraries with those from Mokee and repack the zip. But which files?
I'm pretty frustrated trying to figure this out. I have rooted my US Verizon - variant of the Galaxy S8 (G950U) with SamPWND.
Step 1) After root, I tried installing Viper mod. In the past with other phones, I always just installed the ARISE sound AROMA 2.94 installer as it does a lot of the work for you like installing the audio effects conf file in the right folder (/system/vendor/etc). So I ran the installer, and on next reboot, noticed Spotify Eq was using Samsung's built in SoundAlive equalizer. I forgot to freeze it first but did it anyhow in Titanium. Now spotify is using Viper. Sound quality sounds like crap.
Step 2) Factory reset and start over, this time using the method mentioned in the SamPWND thread which can be found here:
https://forum.xda-developers.com/galaxy-s8/development/samsung-galaxy-s8-root-snapdragon-t3659305
- That thread points to this Viper install guide for the S8: https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
As the guide mentions, I followed the steps by first freezing SoundAlive, copying the zip's audio conf file to /system/vendor/etc, then installing viper apk. Since our bootloader is locked, as I expected, the step to install Magisk fails, so then I simply restarted and opened viper. Sound quality is still crap.
So in either case, I know that Spotify is now using Viper mod for sound eq. I even went into Samsung's audio settings in Settings and it gave me a popup to use viper. I can listen to bluetooth and while the song is playing, change the viper eq and here a difference.
I noticed by default, Viper comes with Dolby, which is ON. I always turn this to off and notice that the sound is better. Dolby seems to overload the sound for me (sounds overpowered and almost at times like it's cutting out). Still, I'm noticing that the bass is solid when mids/highs don't have much activity but gets distorted when guitar really kicks in. Mids sound muddied and tunnel - like . Highs are tinny.
Normally, Viper mod with stock eq settings with all my other phones *always* sounds better than stock. Even with the eq at default and turning off any gains or gain controls / volume normalization, sound quality is still poor.
On bluetooth (I'm using my Sennheiser momentum wireless which are upper tier), when turning off Dolby, Spotify's normalize volume setting, the quality is near where it should be. But, in my Audi with Android Auto over USB, sound continues to be really horrible...I think the bass in the car and larger speakers are pointing out the distortion more. I have to also manually set my volume before running it in the car or else the head unit sound level is too low and I have to blast the volume knob which makes it sound worse.
Any ideas? What am I missing and are you experiencing the same?
So I have a SM-G955U, and I just installed Viper4Arise. I used the latest ZIP from the official V4Arise thread and flashed it using FlashFire. Make sure to check mount /system read/write and leave reboot enabled.
Also, I used the installer to remove SoundAlive.
universeman said:
So I have a SM-G955U, and I just installed Viper4Arise. I used the latest ZIP from the official V4Arise thread and flashed it using FlashFire. Make sure to check mount /system read/write and leave reboot enabled.
Also, I used the installer to remove SoundAlive.
Click to expand...
Click to collapse
Thanks man.
I noticed dolby was on by default. Turned that off and also turned off normalize volume in spotify. Sound is a lot better and no longer over loaded, though I think it might need more tuning. Now I'm wondering if install method matters at all
davidisflash said:
Thanks man.
I noticed dolby was on by default. Turned that off and also turned off normalize volume in spotify. Sound is a lot better and no longer over loaded, though I think it might need more tuning. Now I'm wondering if install method matters at all
Click to expand...
Click to collapse
Good to hear! Yea, I turned off volume normalization as well. I don't normally install Dolby, so I haven't had to do that one.
universeman said:
Good to hear! Yea, I turned off volume normalization as well. I don't normally install Dolby, so I haven't had to do that one.
Click to expand...
Click to collapse
Installing the apk from the recommended zip installed dolby atmos
davidisflash said:
Installing the apk from the recommended zip installed dolby atmos
Click to expand...
Click to collapse
APK? I flashed this zip in the FlashFire "recovery" mode. I didn't have to install any APKs.
Link: https://www.androidfilehost.com/?fid=889764386195922231
universeman said:
APK? I flashed this zip in the FlashFire "recovery" mode. I didn't have to install any APKs.
Link: https://www.androidfilehost.com/?fid=889764386195922231
Click to expand...
Click to collapse
Yeah, there is a separate 18th thread with an install zip which contains the audio effects conf and viper apk inside
davidisflash said:
Yeah, there is a separate 18th thread with an install zip which contains the audio effects conf and viper apk inside
Click to expand...
Click to collapse
Ahhh. I didn't go through any of that.
universeman said:
Ahhh. I didn't go through any of that.
Click to expand...
Click to collapse
How are you testing sound quality? I'm fine with the sound over Bluetooth headphones (sennheiser momentum, pretty good ones). But in my Audi, over android auto using usb, the vocals are still a bit harsh. Sub is cleaner now after a ton of adjustments. Vocals still are harsh on the "s" sound. With my previous pixel phone in this car, sound was way better and didn't need so much work
davidisflash said:
How are you testing sound quality? I'm fine with the sound over Bluetooth headphones (sennheiser momentum, pretty good ones). But in my Audi, over android auto using usb, the vocals are still a bit harsh. Sub is cleaner now after a ton of adjustments. Vocals still are harsh on the "s" sound. With my previous pixel phone in this car, sound was way better and didn't need so much work
Click to expand...
Click to collapse
You can open the status menu in the Viper4Arise app to see if it is processing, other than that, I am listening to it. I know what my Pixel sounded like with V4Ar, and it sounds the same to me. All that being said, I have to use BT to connect to the Sync in my Mustang since I only have Sync 2, which doesn't support Android Auto.
How does Android Auto work? Is the music playing from your phone, or is the car stereo controlling? I know you can connect an Android phone as a USB drive.
universeman said:
You can open the status menu in the Viper4Arise app to see if it is processing, other than that, I am listening to it. I know what my Pixel sounded like with V4Ar, and it sounds the same to me. All that being said, I have to use BT to connect to the Sync in my Mustang since I only have Sync 2, which doesn't support Android Auto.
How does Android Auto work? Is the music playing from your phone, or is the car stereo controlling? I know you can connect an Android phone as a USB drive.
Click to expand...
Click to collapse
Yeah, processing wasn't the issue, and that's why I don't know if the install method matters. I definitely know it's doing something because I move the knobs with bluetooth stream and hear the sound act differently.
With Android Auto, I hook up my phone to the USB port built into the car. Then the phone says Android auto in black and white, and the car display shows the interface for music players, maps, etc.
When auto is up, I can't change the sound settings dynamically since the screen is black. I think if I open viper before the car and have the notification always show, I can load it...but then it's loading a separate instance of the app, not the main one.
I had to really change the bass settings on my phone *and* the car (normally don't have to) to make the bass not distort. The audi's stock sound is junk. I got a nice JL Audio amp installed and a 600W JL Audio woofer.
With the pixel, in the car, I had the bass dial in the audi set to one two notches above mid way and the treble down 4 notches. Now, with the rooted s8, I'm having to dial its bass setting down 2 notches from mid (instead of up) and instead turn up the bass knob on the JL Audio woofer just a hair. Anything else and it distorts.
Out of the box, the Pixel just sounded great to me. I don't know why the S8 is taking all this work. Even with my note 4, I didn't have this issue of having to tweak the hell out of it.