I have a Nexus 6 running 7.1.1 rooted with magisk. When I make phone calls or an incoming call no one can hear me and I can't hear them. I have audio on everything else. I can make phone calls on FB messenger. Hadlby Atmos installed through magisk. I have no idea what to do. I was thinking doing a factory reset, but not to sure. Any help would be greatly appreciated.
First disable all system mods: all Magisk modules, and all apps using root. (I assume you haven't installed Xposed since you don't mention it, but otherwise that is always a prime suspect). Reboot and see if it is any better.
Does it work with a headset? (Wired and/or Bluetooth).
But yes, the obvious next step is a factory reset. And while you're at it, you may as well try a custom rom - they are clearly better than stock these days.
The modules I have installed are, magisk hide props config , YouTube vanced, greenify, emoji one, tethering enabler, pixel 2 experience. I thought I had Xposed installed but I guess not. Well I had no sound during phone calls with a headset or Bluetooth headset. I reinstalled Dolby atmos and it's working again. I've been looking at different ROMs, any particular one you would recommend for daily use runekock?
I run Nitrogen Pie, and it suits me fine. But it still has a few bugs. If you want the best possible stability, I suggest LineageOS Oreo.
Related
Had this issue on all Lollipop ROMs I've tried. My earpiece (+headphone jack) is faulty, so I set all my calls to the loudspeaker. Worked fine on KK and on my first days of Lollipop, but then even speaker stopped working. Being unable to make calls, reverted back to KK, working fine (considering I have de earpiece HW issue). Now switched back to Lollipop and it happened again. Tried routing all audio to speaker with SoundAbout, no results except for the first time after installing the app. Speaker works great for everything else, so I'm suspecting of something about how LP routes HW-related audio (calls coming from the network and, I think, FM radio - never used it in my phones, so I have no clue) and SW-related audio (everything else, which comes from file reading, handled by apps, like music, whatsapp audio and notifications) or some issue with the apps and libs (and whatever else) related to calls.
So I'd like help in the following points:
1. Is it possible to revert everything system-wise related to calls to their KK counterparts? Is there a good reason for it not to work well, theoretically, so I shouldn't even bother trying?
2. In case 1 isn't possible, is there a way for me to check everything that should be working about call audio, see what outputs and stuff like that I was supposed to get, and compare these to the ones I get, on testing? I can provide logcat with SoundAbout on and off, if needed;
3. Since it's only happening in LP, should I suppose that this is something related to the earpiece+P2 jack issue that KK ignored, but LP isn't dealing well with? I'm going for a new jack (I think the earpiece issue is caused by it, because it stopped working about the same time my jack was broken beyond repair) in a couple of weeks and this might be solved, but this issue is driving me crazy already. I could live without the earpiece. I could even live without being able to listen to music on my way to work. But it's really sad to need to revert to KK in order to be able to make calls, with the amazing work devs are doing on LP (tried 3 LP ROMs and fell in love with all of them, visual, speed, functionality and stability-wise).
In case nothing works, I considered multi-boot with safestrap, my current LP as "stock" (I don't know if there is a limitation to actual stock FWs in the stock slot at safestrap, could somebody point me this?) and a KK FW (stock or custom, really don't care in this case) for calling. I make few calls a day, but those are very important, so I could spend some time in KK to make calls if I could reboot to LP and enjoy the best of it. Is it possible?
Thanks in advance for any input. Sorry for the long post (I like to give al the details I can and explain my resolution tries and thoughs on the OP to prevent the need to comment a hundred times) and for the awful english.
If your earpiece and 3.5 mm jack are damaged why don't repair your phone?
Safestrap hasn't been compatible since Android 4.4.
And unfortunately you can't downgrade either, not without likely bricking.
But if you're flashing roms, you must have an unlocked bootloader, so why would you need safestrap?
Oh, There's no way to "multi boot" on the moto X.
CM12 call audio updates seem to fix the issue. Will report back after I get my earpiece replaced.
Sent from my ghost using XDA Free mobile app
Update: the issue seems to happen if one has a damaged earpiece and installs the whatsapp mic fix. So if anyone out there has this issue, you have to choose: call audio on speakers or recording audio on whatsapp. Will report back, but I have been running for a couple days without issues.
Hi!
I was wondering if its possible by any way (app tweak mod whatever) to get bluetooth permissions on stock miui?
I noticed this is available on custom roms but i have other bugs / things i miss on custom rom.
So is it possible? (if you don't understand, on stock if i connect to my bluetooth earphone i can change nothing and i sometimes call people by accident. as a nightshift worked people don't like this , on Resurrection remix i could deselect phone permission on my bluetooth earphone and it worked a sharm. but as i said battery life, performance and bugs keep me away from custom roms)
Thanks!
I have Magisk and EdXposed. I'm sure there is a way to enable aptX on this phone, since it's possible on pretty much every other phone including RP1, has anyone found a solution yet? Stock bluetooth audio is so bad it's unusable.
Have you ever thought that your headset does not support aptx? In one step, buy an iron triangle dsr9bt and enjoy the ultimate hifi.
Currently on Android 11 with Android Auto v 7.0.614134 and V4A v 2.7.1.6. When connected via bluetooth music is processed via V4A and sounds fantastic. When connected with Android Auto via USB, music does not get processed via V4A even though there is a USB setting in V4A. Music also does not get processed via the Speaker tab, which it defaults to when plugged in with Android Auto. I have researched this extensively and found it's a limitation for whatever reason. Also odd that I can't find any recent topics on it. The newest discussions are from 2019 to mid 2020.
I have tried disabling USB audio routing in Developer Settings to no avail. My solution is to use the EQ settings on Rocket Player to compensate, and it helps...but it's not the same as V4A.
However, I read somewhere that Android 12 "fixed" this issue. Or perhaps I misunderstood what I read. Any any case, can anyone on Android 12 using V4A and Android Auto confirm if audio is processed with V4A while connected to AA? FWIW, I have a PIxel 4a 5G and have been putting off the upgrade to 12 (hate setting up phones) but if A12 will "fix" this issue I will bite the bullet.
Thanks!
I accidentally stumbled for a solution to this just a few days ago.
If you check the "disable bluetooth auto connect" from AA AIO tweaker, v4a works with android auto too. Atleast in my case, i use AAwireless but i dont think it has anything to do with it.
Im on Android 10 and rooted stock oneplus 7 pro, and v4a wont work without the aa aio
Limpperi said:
I accidentally stumbled for a solution to this just a few days ago.
If you check the "disable bluetooth auto connect" from AA AIO tweaker, v4a works with android auto too. Atleast in my case, i use AAwireless but i dont think it has anything to do with it.
Im on Android 10 and rooted stock oneplus 7 pro, and v4a wont work without the aa aio
Click to expand...
Click to collapse
Thanks! I tried AA AIO Tweaker but, unfortunately, it did not work for/with V4A. I did use it to tweak other aspects of AA though, so it is still a useful app.
Part 1
I have gotten v4a to work with Android Auto. In settings I toggled on BOTH "Attach audio effects (All sessions but 0)" and "Compatibility mode". The sound enhancements, unfortunately, come thru the "Speaker" settings...but it's better than nothing.
Part 2
I have experimented more with v4a and Android Auto. On the phone in Developer Settings I toggled on "Disable USB audio routing". I kept v4a settings toggled on for "Attach audio effects" & "Compatibility mode". I then connected to Android Auto and voila...v4a was processing through the bluetooth settings. I was able to tweak settings and could hear the differences. It was definitely processed via bluetooth settings. This worked for Spotify & Musicolet. When I tried Muzecast , v4a didn't process any audio tweaks. Nor does it work for TuneIn Radio or Audacy.
What's weird though, is now Spotify and Musicolet have reverted back to processing thru the "Speaker" settings - not bluetooth anymore. Even after rebooting the phone and re-starting the car.
Not sure why the bluetooth settings don't process any longer when connected to Android Auto, and why some apps don't work while others do. Very weird.
FWIW - v4a does process bluetooth settings for all apps when connected solely to the car's bluetooth WITHOUT Android Auto, but I have to disable v4a setting "Attach audio effects".
Just to give a final update...
I re-read the post by Limpperi and re-checked "Disable Bluetooth Auto Connect". The v4a settings I mentioned above remain the same. Now after I connect to Android Auto I need to manually turn on bluetooth from the phone, but I have been successfully getting music processed through v4a bluetooth settings. Spotify and Musicolet work perfectly this way. Muzecast does not process thru v4a until I disable "Attach audio effects". Audacy and TuneIn Radio do not process thru v4a no matter what settings I try...but I don't use those much in the car. They're more like a back-up for if I travel out of state and want to listen to my local stations.
I still don't know why some apps work this way and other don't. They all work as intended when I simply connect to a bluetooth speaker or ear-buds but not Android Auto.
If you don't have AA AIO Tweaker installed you MAY be able to achieve the same results by simply going into the Android Auto app on the phone and disabling "Use Bluetooth". However, I have not experimented with that so it may or may not work as intended...but I don't see why it wouldn't.
Hope this helps someone.
Hello all,
I'm still on Android 11 and I am trying to get Viper4android to work over Bluetooth but can't seem to get it to process. I've used Magisk, Viper4android and poweramp (my audio app) for years over multiple Android versions and never had an issue I couldn't figure out like this one.
I've done all of the obvious stuff like enabling compatibility mode in the viper app, enabling legacy mode, changing selinux mode to permissive, changing the Bluetooth codec to aac and even sbc and changing the audio bitrate to 44k and below and nothing seems to work.
Anyone else use Viper4android on the ROG 3 and got it to actuslly work over Bluetooth? Thanks
Works fine for me (on A11 & A12).
Is V4A working fine otherwise/ processing for you in terms of media playback sáns bluetooth?
Have you tried it in conjunction with the AML/ ACP Magisk modules? May need to fiddle with these for V4A bluetooth to work....
I think there's also a Bluetooth stability Magisk module as well (though I don't use it).
In case anyone has a similar issue for whatever reason I finally figured this out. Turns out the audio player I was using which is Poweramp I had set to force Bluetooth to use a different output type, the standard is OpenSL ES and I had set it to use Hi-res. Once I switched it back everything is now working.