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.
Related
I have experienced Bluetooth backward compatibility problems with my note 8 on devices having early bluetooth versions. For instance I have a monster rocking roller speaker that worked flawlessly with the s7 and with my N8 I would have audio distortion and crackling.
With the delivery of Oreo there are a bunch of Bluetooth settings to play with in developer options (attached) and I was wondering if anyone has had success tweaking these settings to solve an issue like I have been having.
I never used any of the settings and no BT issues here (Speakers, car audio, smart watches, wireless headphones/earbuts).
Maybe your speaker has a problem...
jwrlaw said:
I have experienced Bluetooth backward compatibility problems with my note 8 on devices having early bluetooth versions. For instance I have a monster rocking roller speaker that worked flawlessly with the s7 and with my N8 I would have audio distortion and crackling.
With the delivery of Oreo there are a bunch of Bluetooth settings to play with in developer options (attached) and I was wondering if anyone has had success tweaking these settings to solve an issue like I have been having.
Click to expand...
Click to collapse
Have you tried messing with the sound-alive settings the phone uses? The drivers it uses suck! Ive noticed in some cars it was the issue, ive moved away from samsung drivers all together and use viper for a solution but being unrooted your stuck with using what you got
Team DevDigitel said:
Have you tried messing with the sound-alive settings the phone uses? The drivers it uses suck! Ive noticed in some cars it was the issue, ive moved away from samsung drivers all together and use viper for a solution but being unrooted your stuck with using what you got
Click to expand...
Click to collapse
I didn't but I changed the codec setting from acc to sbc and messed with the sample rates and I now don't have a worthless $200 speaker. This seemed to solve my previous problems.
I've been having a similar issue my stereo in my truck is supposed to launch my Bluetooth music players and allow me to control the music player from the stereo in the truck but it does not now since the update any idea on what settings I should use for what they were before the update?
I use the aptX codec on my Bluetooth headset. What's up??
This is a long shot.
I have a pair of Bluetooth 4.1 Minirig speakers that can be set in stereo mode. However when in stereo mode one channel experiences dropouts. Running in mono mode is fine.
The issue is with the Nokia 7+'s Bluetooth transmission as when using other Bluetooth enabled devices to power the speakers the issue does not occur.
Anyone else had this issue when connecting stereo speakers or headphones and know of a solution?
I have checked: System > Developer Options > Bluetooth Audio Codecs and tried changing these setting but the changes did not "stick" and problem remained.
Maybe there is an alternative setting somewhere that can be tweaked.
Thanks in advance.
doowoppa65 said:
I have checked: System > Developer Options > Bluetooth Audio Codecs and tried changing these setting but the changes did not "stick" and problem remained.
.
Click to expand...
Click to collapse
I'm also having this issue: whenever I'm connecting my N7+ onto the car's audio system via Bluetooth I have to change the codecs to the correct one every single time to make it properly work (have sound/audio at all). The settings also don't stick or are not being saved. Also looking for a solution for this, unless an update miraculously fixes it.
Same problem here when connected to my car by bluetooth. Occasionally there is a dropout. This does not happen when my friends connect with their phones (oneplus 5, samsung, allview. or my old lg g4).
Changing the bluetooth audio codecs does not work as it does not remain selected and it switches to default. This, as i understood, happens on android 8 and has been resolved in the Pie beta and should be ok in the final Pie release.
When I raised the issue with the superbly talented nokia tech support they either act surprised as if its an unique issue to you or send you a list of compatible bluetooth protocols. Are we expected to change our cars and speakers to make the phone work?
I had this issue after installing garmin connect. Theres a thread over in the garmin forums (forums.garmin.com/forum/into-sports/garmin-connect-mobile-application/garmin-connect-mobile-android/1375800-audio-streaming-issues) about it. Also on the nokia forums (community.phones.nokia.com/support/discussions/topics/7000022239/). Seems to affect some phones on 8.1
Anyway, I'm on Pie beta now and the problem has gone away.
after updating to androide 9 on note 9
Dolby is used to turn off automatically without any reason
try to format and reset the mobile but the issue still as it
any suggestion plz
I ran into this issue many times while plugging in headphones. Very irritating. May have recently stopped. Still keeping an eye on it.
ME TOO.
Enable dolby atmos for gaming in sound settings, or from game tools. Otherwise it turns it off open a game and does not turn on back.
Contact support and report the bug, there are also issues WITH DSD and Flac playback and bluetooth codecs defaulting to SBC like when Motorola had bluetooth headsets.
Same here.
Mine used to turn off by itself when I was on android 9 beta. But when I updated to final release of android 9 it now stays on all the time.
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.
I have V4A Magisk 2.5.0.5 installed in a ONN TV box..but only the first 2 V4A options work..I cant slide right the other tabs, even if I disable or enable Legacy and/or Compatibility modes..as is, it does work for my BT earbuds, but I wish to enable Bass, Clarity, and the FIR equalizer..any help?