Hi,
My N6 speakers stopped working. Headset jack still works. I'm running a rooted Purenexus with Franco Kernel. Android 7.1.1. Kernel Franco 3.10.40, Pure Nexus version 7.1.1.20170215 OFFICIAL.
I've tried :
rebooting
updating Franco to latest version
rebooting in Safe mode
Nothing helps. No sound out of either speaker using music app or youtube.
Phone is in good shape, used to work fine, has no sim currently but is used as wifi surfer.
Any ideas of how to fix? Seems like it might be a software issue, since it worked fine until recently. But safe mode didn't help, so I'm wondering if it might be hardware?
Related
Automatelt doesn't seem to change the sound mode on my HTC One. Is this a Sense 5.0 issue?
I'm running ARHD 12.1, ElementalX.
I'm running ARHD 10.3 with stock kernel and AutomateIt works fine for me. My main sound rule is everything silent after 11pm.
Been working well since I installed it. The only hitch was when the app updated and I didn't run the app to accept the changes. My silent rule didn't kick in until I acknowledge the new changes.
icepixie said:
I'm running ARHD 10.3 with stock kernel and AutomateIt works fine for me. My main sound rule is everything silent after 11pm.
Been working well since I installed it. The only hitch was when the app updated and I didn't run the app to accept the changes. My silent rule didn't kick in until I acknowledge the new changes.
Click to expand...
Click to collapse
Thanks! It works now. I found that the problem was automatelt greenified. After ungreenifying it,, everything runs smoothly.
I had a very strange issue with my earphones today noon, all of a sudden it stopped working can't hear anything through it, but Loudspeaker is working fine for both incoming and out going calls.
I tried all the solutions posted on the Motorola thread and XDA still no luck, I am running Paranoid android 5.1.1 version. I have a stock ROM backup in my twrp as I am out of town and no WiFi around me I don't feel like restoring back to it.
Does anyone running custom ROM faced the same issue? What was the work around?
device hasn't fallen from me not a single time through out last 4 months of using it. I have seen posts on similar issue for stock 5.1 noting for custom ROMs.
Tried restart, clearing cache and cleaning the headphone Jack no luck so far.
Solution mentioned to turn off hearing aid is not present in the dialer app of PA.
Help needed here plz.
Sent from my victara using Tapatalk
I don't know if this has been answered anywhere and I am sincerely sorry if it has been.
I am faced with a peculiar problem with my 18K Mi Mix. The phone came with 8.2.5.0. When no updates were forthcoming I decided to root and install a custom ROM. Everything went fine and the phone booted up and I installed my apps. I was using 7.8.31 version of the Beta ROM. However I was faced with a problem of a crackling or static like noise in the background while making calls. The speakerphone and headphone or Bluetooth headset has no problems. Only the call speaker. So I imagined it to be a hardware problem and went back to stock. To my surprise, the problem vanished in stock ROM and any ROM based on Android 6.0. It is only present in Android 7.0. So I guess it might have something to do with the Android 7 ROMs themselves.
Has anybody here faced such issues. If you have kindly help me. I am kinda addicted to the 7.0 ROMs and wish to stay on them if I can get rid of this issue. I was using the Global stable ROM earlier.
Thanks for any help.
shantanil said:
I don't know if this has been answered anywhere and I am sincerely sorry if it has been.
I am faced with a peculiar problem with my 18K Mi Mix. The phone came with 8.2.5.0. When no updates were forthcoming I decided to root and install a custom ROM. Everything went fine and the phone booted up and I installed my apps. I was using 7.8.31 version of the Beta ROM. However I was faced with a problem of a crackling or static like noise in the background while making calls. The speakerphone and headphone or Bluetooth headset has no problems. Only the call speaker. So I imagined it to be a hardware problem and went back to stock. To my surprise, the problem vanished in stock ROM and any ROM based on Android 6.0. It is only present in Android 7.0. So I guess it might have something to do with the Android 7 ROMs themselves.
Has anybody here faced such issues. If you have kindly help me. I am kinda addicted to the 7.0 ROMs and wish to stay on them if I can get rid of this issue. I was using the Global stable ROM earlier.
Thanks for any help.
Click to expand...
Click to collapse
Well you've already done the hard work so may as well stick RR rom on the phone. All problems have been ironed out and think you will be happy, I went back to miui awhile ago had crackling in calls although mainly on Bluetooth.
james1089 said:
Well you've already done the hard work so may as well stick RR rom on the phone. All problems have been ironed out and think you will be happy, I went back to miui awhile ago had crackling in calls although mainly on Bluetooth.
Click to expand...
Click to collapse
Thanks. Will give it a try.
Finally cracked the problem. As I had suspected, this is a software flaw. The whole issue was being caused by the proximity sensor. The moment I turned the proximity sensor off all problems have vanished. Have replicated the problem a number of times, so am pretty sure that is the cause. Thanks everyone for your help and suggestions.
you don't fix the problem we need the sensor
fred1311 said:
you don't fix the problem we need the sensor
Click to expand...
Click to collapse
You do need the sensor.
But since the problem is not happening with any of the stable version ROMs (I have tried Global stable 8.2.5 and China Stable 8.5.4), I am very sure its not related to hardware. So for the time being I am more than happy keeping the proximity sensor off and using Nougat 7.0 on my Mix. I am pretty sure this has something to do with drivers or firmware and will be taken care of, once the stable versions of 7.0 are released.
james1089 said:
Well you've already done the hard work so may as well stick RR rom on the phone. All problems have been ironed out and think you will be happy, I went back to miui awhile ago had crackling in calls although mainly on Bluetooth.
Click to expand...
Click to collapse
Even my Redmi Note 4 has that cracking or scattering sound when bluetooth calls are made. I found temporary solution that is Turn off the WiFi. Looking for permanent solution.
I've recently updated my device to Oreo after making up my mind. Now I'm suffering from a slight issue where when I pay using my watch the plug in on my phone crashes (payment still goes through though). I can't open the app at all as it crashes. Having xposed on/off still reproduces the same issue. Its seems as if the latest version of s pay isn't somehow compatible Oreo in a way. Have even tested the same s pay plugin on my stock pixel xl 2 running oreo also.and crashes also when attempting to open.
Currently running weta (8.0) but the plugin worked just fine back in nougat. Is anyone suffering from similar issues by any chance? Would absolutely love to hear your thoughts and opinions on the matter
As the title of the post says, I'm encountering this extremely infuriating audio bug in Oreo based custom ROMs (OOS works fine) where the audio from most games comes out "dragged" and distorted once every few seconds. It's driving me nuts and I can't figure out what on Earth is causing it.
I have V4A installed, but that seemed to work just fine on OOS without any issues whatsoever, so it may not be causing the issue. Can anyone else please tell me whether they're facing a similar issue or not? I'm currently on Resurrection Remix 6.1 2019/07/15. This issue has been driving me insane for the past few months (during which I've only been on RR, but have encountered this issue on other ROMs including LOS).
#1 Update to the post:
Viper seems to be the issue, contrary to my belief. I tried it with Viper uninstalled via a dirty flash of my ROM, and the glitch didn't exist anymore. Just to be sure I got another version of V4A (this time a magisk one) and the bug is back. Is there any way to workaround this thing? I'd really like to keep my Viper
I'm using Dolby Atmos without any issues.