Problem audio system and vibration (CM11) - Nexus 4 Q&A, Help & Troubleshooting

Boys suddenly I had this problem, there is no precedent and no operations strange that I made...
In practice, the audio system of my Nexus 4 (OS: Cyanogenmod 11 last nightly 14sept14) will not start: first when the screen was stuck giving audio feedback, now nothing. I do not feel even the incoming calls.
It is not a problem of speaker, if I play a song I can feel it ... the problem is only for the channel "audio system".
Identical problem as regards the vibration (problems manifested simultaneously apparently), only that in this case do not receive the vibration anywhere, even installing app apposite to vibrate.
I tryed to reboot the phone, I reinstalled (reflash) the latest nightly, I checked the settings, I changed the kernel (at the time of mixup was AK Kernel with Synapse, now that the CyanogenMod Kernel)...
What to do?!?!
Thank you all

dix93 said:
Boys suddenly I had this problem, there is no precedent and no operations strange that I made...
In practice, the audio system of my Nexus 4 (OS: Cyanogenmod 11 last nightly 14sept14) will not start: first when the screen was stuck giving audio feedback, now nothing. I do not feel even the incoming calls.
It is not a problem of speaker, if I play a song I can feel it ... the problem is only for the channel "audio system".
Identical problem as regards the vibration (problems manifested simultaneously apparently), only that in this case do not receive the vibration anywhere, even installing app apposite to vibrate.
I tryed to reboot the phone, I reinstalled (reflash) the latest nightly, I checked the settings, I changed the kernel (at the time of mixup was AK Kernel with Synapse, now that the CyanogenMod Kernel)...
What to do?!?!
Thank you all
Click to expand...
Click to collapse
Try changing the ROM completely, with a full wipe (after you backup of course). Does it still do it?

I was looking for a solution without dat loss...
If by tomorrow I don't find other solution, I will do as you say

dix93 said:
I was looking for a solution without dat loss...
If by tomorrow I don't find other solution, I will do as you say
Click to expand...
Click to collapse
There's no loss if you do a backup from recovery.
You just backup, then wipe and install a ROM.
And then, you just restore, and you would have lost nothing

Related

Sound completely gone (not even factory reset works)

EDIT: I actually have a galaxy nexus and not nexus 4, I reposted this here: http://forum.xda-developers.com/showthread.php?p=38624019
Sorry for this topic, delete if possible, thanks!
It happened after testing/installing the popular "GO Launcher EX" my sound is completely gone. Of course I uninstalled that GO Launcher EX asap but it didn't help.
My problems:
- No sound during music, media, alarm, calling people, etc. The sound is completely gone while the sound volume bars all are maxed.
- I keep hearing small buzz sounds and from time to time "tik tik" sound.
I tried factory reset, didn't work. I tried to update my rom from 4.1 aokp to 4.2.2 , didn't work either.
Is this problem fixable?
ragnaroks said:
EDIT: I actually have a galaxy nexus and not nexus 4, I reposted this here: http://forum.xda-developers.com/showthread.php?p=38624019
Sorry for this topic, delete if possible, thanks!
It happened after testing/installing the popular "GO Launcher EX" my sound is completely gone. Of course I uninstalled that GO Launcher EX asap but it didn't help.
My problems:
- No sound during music, media, alarm, calling people, etc. The sound is completely gone while the sound volume bars all are maxed.
- I keep hearing small buzz sounds and from time to time "tik tik" sound.
I tried factory reset, didn't work. I tried to update my rom from 4.1 aokp to 4.2.2 , didn't work either.
Is this problem fixable?
Click to expand...
Click to collapse
try flashing another rom
also check your sound settings :good:
manu4204 said:
try flashing another rom
also check your sound settings :good:
Click to expand...
Click to collapse
Hey!
Didn't work, I tried fac reset/wipe cache etc to install cm10 , same results.
What do you mean by check sound settings? Everything is at max or close to max, I even downloaded some sound manager t make sure all sounds are active.

[Q] Lost phone sounds on ReVolt and other roms

Hi all, I really hope you can help me with this...
I can't stand TouchWiz, so I very quickly replaced it with CM 10.1, which sort of works. However, I find it very annoying that it lacks stuff like PIE (yes I know I have hardware buttons, but I still would like a proper menu, and LTM is just not quite there). I therefore tried Paranoid Android (had no phone, camera worked very badly) and then I discovered ReVolt! I must say ReVolt is a marvellous rom - but with one, massive caveat: I loose sound in the phone app, and indeed the phone seems to go rather bonkers (fails to actually call etc). I did see this somewhat on CM too (failed to place calls - timed out and hung up), but with ReVolt it's consistent.
This is what I did: I reloaded my nandroid backup of stock, checked that the phone worked (it did). I then flashed June 15th (or 14th - it doesn't quite agree) nightly of ReVolt. No sound in phone (but it could call). No ringer sound (on outgoing), no sound either way during the calls. Call in does ring, and it can be answered, but there is just no sound. No errors shown, no nothing. Putting it on speaker, adding headphones - nothing works.
I reloaded the stock rom, then installed latest CM10.1 nightly, and phone works as expected.
Both run on the same baseband (I9505XXUAME2), and they are both based on CM. Any ideas (I'm not allowed to post in the ReVolt thread - I don't have enough posts yet it seems).
Any help is greatly appreciated.
/R

[Q] CM11 half blacked out screen while getting incoming calls with latest

I get a half blacked out screen while getting incoming calls with the ROM from 20.01.2014 from quarx (look: quarx2k.ru/cm11.0-nightly-defy+/?C=M;O=A). Someone else too? What can I do about it? Maybe change an apk within the ROM?
x53 said:
I get a half blacked out screen while getting incoming calls with the ROM from 20.01.2014 from quarx (look: quarx2k.ru/cm11.0-nightly-defy+/?C=M;O=A). Someone else too? What can I do about it? Maybe change an apk within the ROM?
Click to expand...
Click to collapse
Me too. I have to say that I still experience call delay bug (possibly even worse) with this release.
I did a clean install of ROM 20140120 (wiped system and data, too), but with no luck. When I install the ROM 20140117 the square is transparent again, but back to ROM 20140120 it's black. I dont understand how other defy users haven't this problem? Are defy devices so different? OK, dont use GApps?!?
wolfie05 said:
Me too. I have to say that I still experience call delay bug (possibly even worse) with this release.
Click to expand...
Click to collapse
For 2 seconds or 2 times ringing and screen shows up. However you could use the power key to wake up your phone earlier, I know a bad and impractical workaround.
screen delay
x53 said:
I did a clean install of ROM 20140120 (wiped system and data, too), but with no luck. When I install the ROM 20140117 the square is transparent again, but back to ROM 20140120 it's black. I dont understand how other defy users haven't this problem? Are defy devices so different? OK, dont use GApps?!?
For 2 seconds or 2 times ringing and screen shows up. However you could use the power key to wake up your phone earlier, I know a bad and impractical workaround.
Click to expand...
Click to collapse
same here!! any solution yet for this??
I too am fighting with this bug, on the latest firmware of Quarx , 08/02/2014 , the firmware is satisfies me, but the response of the screen during incoming ringing still existents delayed , although the waiting time decreased, But this is not enough for full use of the device
I managed to slightly accelerate the reaction of the display by changing the frequency on the CPU
Four steps of processor : Vsel 300/17,600/35,900/50,1255/63
Also I replace the kernel in firmware of Quarx, I integrate SlimKat kernel , despite the fact that the kernel slim is almost copy of the Quarx kernel, operation of the device is improved .
You can try my steps and decide to test and decide own conclusions.
If someone tries to leave me your comment.

Crackling sound on AOSP Rom

Dear xda friends,
I've been trying few AOSP rom on my N9005 always have the noise and crackling sound problem.
I tried to search but couldn't find solution to fix that.
Alan_Hill said:
Dear xda friends,
I've been trying few AOSP rom on my N9005 always have the noise and crackling sound problem.
I tried to search but couldn't find solution to fix that.
Click to expand...
Click to collapse
I have n-900. I had the same crackling sound problem coming from the bottom of my phone. I gave it to Samsung Agency they changed the speaker first. Same problem persisted after a few days.
So i gave the phone again and asked for a replacement. Thankfully, they changed the chipset. Now its fine. *Touchwood*
jakhan86 said:
I have n-900. I had the same crackling sound problem coming from the bottom of my phone. I gave it to Samsung Agency they changed the speaker first. Same problem persisted after a few days.
So i gave the phone again and asked for a replacement. Thankfully, they changed the chipset. Now its fine. *Touchwood*
Click to expand...
Click to collapse
But mine work with Samsung based rom without any issue like this one .
You tried a few AOSP roms, well ain't that cute.
But not once did you read the first posts or a few last posts of the rom thread. If you would, I'm sure you'd found at least a hint on this bug.
And do learn how to Google search !
Sent from my N9005
Had the same problem too, this issue is for all AOSP roms as I see .. but after some restart and charges he go away .. No worries to have man
Same problem. Been having it ever since I installed cm12.1. Most sounds work like they should, but certain apps only crackle. Like, my gf got a vanilla note3,and we both have the game "just get 10". To her, the sound is as it should be. To me it's horrible.
I've been using it ever since the unofficial ports, and been updating nightlies ever since. The problem still persist. If this could be fixed, it would be amazing!
I've also tried the equalizer ports of dsp mamager and audiofx, but no changes whatever I do.
Headphones, and Bluetooth headset works fine.
I too have experienced that allot. And have noticed that it occurs mostly when you use different sound drivers. Like if even on TW you flash beats audio mod or maxx audio you can hear the same crackling.
I suggest you use temasek rom. Its a solid and very stable one.
Hey thanks man, I'll do that
Edit, I've done did it and now everything works flawlessly. It's also a great rom, good battery. Thanks man.
This problem exists in all AOSP based ROMs and after some research I found the solution:
Go to settings -> apps manager -> select google app -> permissions -> disable the microphone permission.
Done
Worked on Galaxy S7 Edge

[Q] Nexus 4 doesn't vibrate

Hi everyone,
I bought my nexus 4 about a year ago, and very recently I decided to give Cyanogenmod a try. I must say this was the first custom ROM I flashed on my device, and I'm quite fond of it. I also flashed a modified version of the latest franco.kernel for CM (http://forum.xda-developers.com/showpost.php?p=53707610&postcount=459)
The thing is that I noticed that my phone doesn't vibrate when it's supposed to. In fact, it doesn't vibrate at all; no matter what I try, it just doesn't. For the record, it had been working flawlessly until a few days ago.
So far I've tried:
- Disabling/Enabling vibration in keyboard, notifications and calls
- Rebooting my device several times
- Updating to 20140723 nightly (I was previously on M8)
- Disabling quiet hours
I've been doing some reading, and some old threads advise to perform a factory reset, but it's kind of a hassle for me to re-sync all the photos and stuff. So, is there anything I should try before I do a factory reset? Should I try and flash a different kernel/go back to stock kernel?
Thanks
It's most likely a hardware issue. I'd backup the phone and then flash the factory image. If it still doesn't vibrate it's a hardware issue. It doesn't cost much to replace the vibrator. Do it yourself or find a local cell repair shop.
Sent from my Nexus 5 using XDA Free mobile app
I would rather change the kernel first and see if there is any issues.
I flashed the latest CM nightly, which also changes the kernel to CM stock. This time you can hear the little buzz when you turn on the phone, but that's pretty much all the vibration I get. Phone calls and haptic feedback still don't work. At least, I know it's not a hardware issue.
ant_cc said:
I flashed the latest CM nightly, which also changes the kernel to CM stock. This time you can hear the little buzz when you turn on the phone, but that's pretty much all the vibration I get. Phone calls and haptic feedback still don't work. At least, I know it's not a hardware issue.
Click to expand...
Click to collapse
I still think it's hardware. Roms can change the force it vibrates at. But if it's still low the vibrator is bad.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I still think it's hardware. Roms can change the force it vibrates at. But if it's still low the vibrator is bad.
Click to expand...
Click to collapse
Maybe I wasn't very clear; the vibration force is OK, but the thing it that it only vibrates on startup, it doesn't buzz in incoming calls or any of that. So that's why I think the vibrator isn't broken

Categories

Resources