I just installed the Lineage OS released for Moto G4 Plus Athene from here
Phone Informations
* LineageOS version: 14.1
* Gapps version: 7.1 (released on 05 Feb 2017)
What you did:
* Wipe data: Y
* Upgrade from previous official cm build: N
* Restore with titanium backup: N
You're using (if yes write which one) :
* Task killer: N
* Phone cleaner / Battery enhancer apps : N
* Non-stock kernel: N
* Modified kernel settings N
* Other mods: N
Bug info: The phone has become incapable of detecting newer bluetooth devices (I have tested it on 3 separate Blutetooth 4.0 device), although it connected perfectly with older bluetooth devices.
P.S. I tried reporting the bug there as well, but I'm a low level member so could not.
Bluetooth not reconnecting
Same here, although my issue is that it doesn't reconnect to the devices just until I delete the current device, restart and pair again. Waiting for next build to try.
Remember that some thing are not open source to be used in custom roms. Also cm has always had bt issues and Los will as well. All that testing and your missing the most important and most basic. A logcat
In my case Bluetooth do connects, but no audio on speaker. Though WiFi disconnects 2-3 times a day, and never reconnects on its own. Need to manually reconnect.
Lineage os 14.1 build 20170320 cancro
Same problem with an LG G3 Beat jagnm. Bluetooth pairs OK, but then the audio is scrambled.
Lineage nightly build 20170315 jagnm
Too bad there is no way to report the bug
Same problem with my Xiaomi MI4, connected on my bluetooth speaker but no sound
is the bug still there? I want to switch frome MIUI to lineage and need Bluetooth 4.1!
Yes it continues and the developper didn't start the correction. If bluetooth is needed, stay on miui
Hey, I have the same issue on OnePlusOne with LOS v2017040424. I use running band app with BT 4.0 required. But the device only can be found in BT device scanner, not in app.
Hi, i solved all problems, disabling privacy guard. Now, it works fine
mine is already off. can you explain in more detail please? and exactly which probleam you had? bluetooth not connecting or connected but no audio.
I've managed to solve the issue on my Moto G4 by doing the following:
Go to Settings and select the search option (the magnifying glass in the top right). Search for Bluetooth and you should get an option that says 'Bluetooth Scanning'. Select this and on the next screen TURN OFF Bluetooth Scanning. Reboot the device and try pairing your Bluetooth device again.
Hope this helps!
Issue was somewhat solved but now it's back
An update which came couple weeks ago kind of solved this issue. I had to restart my phone everytime i want to connect it to Bluetooth speaker. But it was better than nothing but now the latest update brought back the issue
same on s7
Hello,
Running Lineage 14.1 on my s7, have seen this since my first install on 7-5-17.
Bluetooth connection and pairing works fine, media audio works fine, I can play music and hear my gps and other items of media through the headphones. Phone audio is distorted and I can't hear the other person, they can't hear me.
I would very much like this problem solved, it's kind of important for my work, I might have to go to a non-aosp rom, which I do not like touchwiz.
For reference my headset is a Philips SHB6250, it's audio range is between 8 and 22,000 hz.
Thanks.
Dave.
tech927 said:
Hello,
Running Lineage 14.1 on my s7, have seen this since my first install on 7-5-17.
Bluetooth connection and pairing works fine, media audio works fine, I can play music and hear my gps and other items of media through the headphones. Phone audio is distorted and I can't hear the other person, they can't hear me.
I would very much like this problem solved, it's kind of important for my work, I might have to go to a non-aosp rom, which I do not like touchwiz.
For reference my headset is a Philips SHB6250, it's audio range is between 8 and 22,000 hz.
Thanks.
Dave.
Click to expand...
Click to collapse
Me too on Samsung SM-G531H
hi, I've recently bought a pair of SONY's MDR-1RBT Bluetooth headphones. the sound over the bundled cable is very good, but when I connect them by bluetooth, things get much worse, it's like the FLAC files I listen to get compressed to some 128 or even 64 kbps... but on my friend's xperia z3 Compact they work just fine. so here's my question. is it possible that the custom rom that I use (existenz MM latest version) causes these problems? I also use Viper so that may be the case. if you don't have any solutions, I'll flash stock and see what happens.
I've no idea what the problem could be, sorry. You may find answers over at the eXistenZ thread. Even though the ROM is no longer being updated there's still many using it.
Probably the rom has no aptX and aptX HD support.
To check:
Start catlog (or an other logcat app)
Connect you Bluetooth device
Start playing music (probably not necessary)
Pause catlog
Search for aptX
If the libraries are missing you should fine some line that says so missing libraries.
Search for bt_btif_media
If the libraries are missing there will be a line that shows: Selected Codec SBC
If there libraries are not missing but the selected codec is still SBC I don't know what is wrong.
To fixed this on LineageOS I installed the aptX (and aptxHD) codec from here:
https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228
I used the Magisk module, but of course for that you need Magisk.
After that I also installed the aptX-HD module from here (again the magisk moduel):
https://forum.xda-developers.com/android/software/mod-aptx-hd-bluetooth-hi-res-audio-t3501991
Now do the same logcat procedure.
If there now is aptX support you should find something like Selected Codec aptX
Good luck!
Oww was this post that old... Still hope it helps (someone).
There's a Nougat Dolby port confirmed working on 8.1 ROMs. Thanks to @roisuke guide (and permission to repost for info) on the LOS15.1 thread summarising steps similar to the original Pixel 2XL guide, which uses the old ARISE N Dolby Atmos zip. In roisuke's post, his/her reason for trying this old Dolby is the newer Dolby boot loops on LOS15.1. In my case I was looking for a better compatible and audio quality Dolby when I found out about it. There's a few reasons i'll group into headings below. I know Dolby speakers that we paid for on stock for our device is a loved feature sought by more than just a few of us. I hope to help improve some people's speaker audio experience like I have, finally rivaling stock performance with V4A extra on top :laugh:
For installation instructions I'll just link roisuke's post, as mine has more to do with settings and usage explanation. I will just add that I had a different issue installing that Dolby zip on RR-O, the process would freeze without an error, requiring a force restart. The zip isn't detected by Magisk Manager and so can't be installed there. I couldn't install the zip when any Magisk version is installed. I ended up having to uninstall Magisk to allow the zip to install to system and then follow up with the other Magisk audio mods installed normally, Viper4Android (i'm on the old 2.3.4.0 for it's Super driver and better graphic equaliser), Ainur Sauron (optional maybe, it claims to improve audio in system and targets Axon 7 as well, I haven't tested this mod without it yet) and lastly Audio Media Library. Also thanks to @Oki for pointing out the hifi DAC patch is necessary with this particular Dolby mod.
Nougat Dolby sounds better
The reasoning is that I've recently been testing custom ROM N Dolby and it sounds just as good as stock N had. While I tested Oreo Dolby ports back when the B32+B10 bootstack was new also just recently too and found it didn't sound as good as N's. Therefore I understand it's not a custom port issue that the new O Dolby sounds worse than N but that it's the updated Dolby itself.
It can work together with V4A
A benefit of this old N Dolby is it is working with current V4A whereas I can't seem to get the new O Dolby to run with V4A, it did when I tested months ago but I can't recreate that either. A benefit to using V4A in combination is it's "Firequalizer" to preset "Small Speakers" accentuates bass and lessens the tinny treble, this is something I used to do back on stock N as well.
It can be configured to set and forget
A little talked about but great feature of stock Dolby is it remembered the settings separately for plugged/unplugged and for each individual app last playing audio too. That made it so good being only on for internal speakers as I preferred and would change settings mode automatically when you stopped audio and started in another app.
Custom ROMs with Dolby ports doesn't remember states, however with a bit of compromise it can be used as such on this N Dolby if you prefer Dolby to only affect internal speakers. The trick is to set no extra filters and EQ in Dolby but just have Dolby enabled. With all other settings off, it still positively affects speaker audio but has no affect on headphone jack audio, you can test this by listening either way while switching on and off. This works combined with the V4A equaliser settings as previously explained. Set rather simply as so, the speaker output has less harsh treble and increased bass to sound similar in presentation to listening on quality headphones.
Extra notes
A shortcoming bug with this N Dolby port however is the Surround Virtualisation feature doesn't work on speakers. It seems reversed and only works when plugged in, I find it best to leave it off as preferred and it will stay off. This bug is unfortunate as the surround was always nice in my opinion, but it's only one loss compared to all the other gains. For what it's worth I couldn't audibly hear a benefit of the surround feature on the O port in my limited testing. Also consider if using the O port where the effects are all somewhat changed for worse in my opinion, it also has to be manually switched off afterwards to not affect plugged audio unlike with the workaround available in the N port. In terms of comparing missing new features, the Oreo version has a bass boost toggle and a dynamic setting, overall though I couldn't settle on an audio setup I liked with any Oreo Dolby settings.
Conclusion
I hope my experience will help others to finally get the most out of their speakers with Dolby and V4A. Since moving from stock N to custom Oreo in early April left me disappointed in O Dolby quality usage issues, I'd stopped using it and relied only on V4A's Speaker Optimisation setting for improving the speakers as a compromise but it always left me wanting in comparison. However now recently finally figuring all this out, i'll be using this for the forseeable future. I really adore the loud unbeatable quality Dolby speaker output for general listening, I mean even a dozen meters away it sounds transformed like a good dedicated mini speaker is playing. This coming from someone who appreciates listening on premium headphones too.
Nice work ofcourse but i dont agree nougat dolby sounds better. In dolby oreo there is more to adjust also
Predatorhaze said:
Nice work ofcourse but i dont agree nougat dolby sounds better. In dolby oreo there is more to adjust also
Click to expand...
Click to collapse
It depends on your ears (or beliefs) I guess. Regardless if you've preference for O or N's Dolby, there's still good reason to use the N port. Mainly that it's able to be set and forget and also it's working with V4A aiding it too without issue.
So after reading your guide I liked the idea of a "set and forget" approach and chose certain presets for fireequalizer while in headset (bass booster) or speaker (small speakers) modes; also I changed v4a to the older version since I was unaware of its "super driver". However in the Dolby app I chose to leave on the "intelligent eq open" because to my ears the sound came across "fuller" if that makes sense.
roisuke said:
So after reading your guide I liked the idea of a "set and forget" approach and chose certain presets for fireequalizer while in headset (bass booster) or speaker (small speakers) modes; also I changed v4a to the older version since I was unaware of its "super driver". However in the Dolby app I chose to leave on the "intelligent eq open" because to my ears the sound came across "fuller" if that makes sense.
Click to expand...
Click to collapse
I'd recommend Dolby's extra customisations to be off because they remain active when plugged in. Unless of course you like any of its setting for both plugged and speaker. Relying on V4A for separated audio modifications fits well, you could try playing around trying to improve settings there if desired.
I used to prefer Rich in Dolby with Small Speakers in V4A together with Surround Virtualisation. Now with SV unavailable, I assume the EQ effects in Dolby are less pronounced because I can't notice much of positive difference with them on. When the issue being the setting will affect plugged too, it's a small worthwhile loss turning them off for the automated convenience.
Your headset preferences will totally depend on your headphone hardware and listening preferences. From my reading and understanding it's better to only use an EQ to reduce Frequency Response range positive peaks. Never to increase EQ as that introduces artificial noise. I'll attach two screenshots showing my hifi headphones FR graph and the V4A EQ I use to show what I mean (EQ graph doesn't match scale, zoom in to see the tiny DPI X Y values). The green line is the ideal neutral target FR with bass effect for headphones. Note when adjusting V4A's graphic equaliser the range of each frequency band is only shown on the old original 2.3.4.0 version.
Obviously mobile speakers are different in severely lacking bass, accuracy and need the bass EQ boost regardless of accuracy.
Sent from my ZTE Axon 7 using XDA Labs
@roisuke, It works as expected using Magisk 16.7. I did in another order and it also worked:
1. V2A FX 1.6.9 or later (I've tested old and current versions)
2. Sauron MK II.II 02.05.2018 or later (I've tested old and current versions)
3. BQ-E4 Dolby ATMOS (Dolby-Oreo.zip)
4. AML 1.7 or later (I've tested old and current versions).
I've noticed the flashing order is irrelevant as long as AML is the last one (It is intented to be always the last module to gather all the audio configs). It works with any install option of V2A (I prefer 2.5.0.5 traditional interface).
I believe the flashing of the ARISE module reroutes the audio paths and disables the hifi DAC when the BQ-E4 Dolby ATMOS is installed. I suspect it because the quality is vastly improved only if, at the end, I flash the Mixer_AK4490.zip to restore the HiFi DAC wiring paths.
These are great news since in Oreo I haven't found a way to have DA and V4A together.
Oki said:
It works with any install option of V2A (I prefer 2.5.0.5 traditional interface).
I believe the flashing of the ARISE module reroutes the audio paths and disables the hifi DAC when the BQ-E4 Dolby ATMOS is installed. I suspect it because the quality is vastly improved only if, at the end, I flash the Mixer_AK4490.zip to restore the HiFi DAC wiring paths.
These are great news since in Oreo I haven't found a way to have DA and V4A together.
Click to expand...
Click to collapse
I already listed why I prefer 2.3.4.0. I didn't mention in general UI the newer versions hide settings behind presses, makes it harder to use and see for example the selected EQ visual profile.
I was focused on speakers so actually hadn't tested jacked audio expecting it to just continue hifi as always on newer bootstacks. I thought Ainur Sauron is supposed to include the DAC patch as @Skrem339 added Axon 7 mods to it, he's also the author of the AK4490 DAC patch in question.
In any case I gave jacked audio some testing. I immediately found with the DAC patch there's static noise when booting jacked in and charging, but it phased out after replugging power, further testing for this may be necessary. After a few short install uninstall tests audio comparison, quality does sound improved. Thanks for mentioning that detail.
Here's the DAC patch thread with system and systemless. I updated the OP with this detail. Systemless only installs through TWRP still by the way. Small note worth mentioning though maybe unrelated is my fingerprint sensor stopped working after installing the Magisk patch, but worked again after uninstalling and reinstalling (a reset may have been enough).
Infy_AsiX said:
I already listed why I prefer 2.3.4.0. I didn't mention in general UI the newer versions hide settings behind presses, makes it harder to use and see for example the selected EQ visual profile.
I was focused on speakers so actually hadn't tested jacked audio expecting it to just continue hifi as always on newer bootstacks. I thought Ainur Sauron is supposed to include the DAC patch as @Skrem339 added Axon 7 mods to it, he's also the author of the AK4490 DAC patch in question.
In any case I gave jacked audio some testing. I immediately found with the DAC patch there's static noise when booting jacked in and charging, but it phased out after replugging power, further testing for this may be necessary. After a few short install uninstall tests audio comparison, quality does sound improved. Thanks for mentioning that detail.
Here's the DAC patch thread with system and systemless. I updated the OP with this detail. Systemless only installs through TWRP still by the way. Small note worth mentioning though maybe unrelated is my fingerprint sensor stopped working after installing the Magisk patch, but worked again after uninstalling and reinstalling (a reset may have been enough).
Click to expand...
Click to collapse
This patch is useless for Roms based on Android 8 because DAC works on them without patch. Also, this DAC patch was remove from Ainur by my request to Ultra8
Skrem339 said:
This patch is useless for Roms based on Android 8 because DAC works on them without patch. Also, this DAC patch was remove from Ainur by my request to Ultra8
Click to expand...
Click to collapse
For some reason the DAC patch is required after installing the Dolby Atmos patch mentioned in the OP, even in Oreo ROMs.
Hi @Infy_AsiX, can you give a link to the exact Nougat dolby port module which you are using on Oreo together with the 2.3.4.0 v4a? I tried all Oreo versions but they give me bootloop on S8 device, thanks
paradoxxman said:
Hi @Infy_AsiX, can you give a link to the exact Nougat dolby port module which you are using on Oreo together with the 2.3.4.0 v4a? I tried all Oreo versions but they give me bootloop on S8 device, thanks
Click to expand...
Click to collapse
Following the installation links brings you to Pixel 2 XL guide with the download. But here's a link to that Pixel2XL guide anyway https://forum.xda-developers.com/pixel-2-xl/how-to/viper-dd-atom-t3724096
Sent from my ZTE Axon 7 using XDA Labs
Great [emoji3] works fine on Havoc Treble Oreo
Oki said:
For some reason the DAC patch is required after installing the Dolby Atmos patch mentioned in the OP, even in Oreo ROMs.
Click to expand...
Click to collapse
did you made Dolby working on treble ROM ? (I m on latest Havoc) because I've followed the OP (not the patch that did not install) but Dolby app quit, w/o message, after 1s. Just the nice logo
dwnoel said:
did you made Dolby working on treble ROM ? (I m on latest Havoc) because I've followed the OP (not the patch that did not install) but Dolby app quit, w/o message, after 1s. Just the nice logo
Click to expand...
Click to collapse
Well, I havent tried it in a Treble ROM. I don't play games or watch ATMOS movies. For Youtube, music and general audio, Viper4Android provides more features and richness to the sound so I don't use ATMOS at all. For external speakers I only notice more volume and some equalization, and I also have that configured in V4A in the speakers section. Treble roms are tricky. V4A is awesome when used properly.
Oki said:
Well, I havent tried it in a Treble ROM. I don't play games or watch ATMOS movies. For Youtube, music and general audio, Viper4Android provides more features and richness to the sound so I don't use ATMOS at all. For external speakers I only notice more volume and some equalization, and I also have that configured in V4A in the speakers section. Treble roms are tricky. V4A is awesome when used properly.
Click to expand...
Click to collapse
Do you mind sharing your settings? I used Atmos on dynamic setting in my car with Android Auto and Spotify. Car never sounded better. I'm now on treble with PixelExperience P and stuck with Viper. Sounds ok, but the dynamic system makes the sound go in and out.
kyuza said:
Do you mind sharing your settings? I used Atmos on dynamic setting in my car with Android Auto and Spotify. Car never sounded better. I'm now on treble with PixelExperience P and stuck with Viper. Sounds ok, but the dynamic system makes the sound go in and out.
Click to expand...
Click to collapse
I use V4A 2.5.0.5 with the classic interface with these settings:
Master Pwr ON
Playback Gain Control: ON
Extreme
4x
-1.9 dB
Spectrum Extension: ON
0.37
Dynamic System: ON
Common Earphone v2
25%
Viper Clarity: ON
Natural
6.0 dB
The rest is off, even the EQ
Been meaning to ask, @Oki. Your settings above are for headphones, right?
The Axon 7 isn't my daily driver so I don't use headphones with it much as I don't carry it around. Been trying to get some good speaker settings, mostly for locally stored music and occasional streaming video.
On this Nougat ROM Dolby Atmos and Viper 2.6.0.5 are working well together. In AEX 5.4 Oreo the two are also working but not necessarily together. A long time ago someone posted custom FireEQ settings which I still use but the other stuff not too sure about.
ZTE Axon 7 A2017U, Dark ROM, LlamaSweet 0.5 Kernel, Multiboot, XDA Legacy
Has anyone got Dolby to work on LOS 15.1?
EDIT: Never mind, got it working by going to the pixel 2xl forum for it
troy5890 said:
Has anyone got Dolby to work on LOS 15.1?
EDIT: Never mind, got it working by going to the pixel 2xl forum for it
Click to expand...
Click to collapse
Are you on the latest nightly los 15.1? Dolby just crashes for me now on latest
roisuke said:
Are you on the latest nightly los 15.1? Dolby just crashes for me now on latest
Click to expand...
Click to collapse
I'm on the latest LOS official 15.1 . I used the zip called "Dolby-Oreo.zip" the one for BQ.
Hi, aptX bluetooth audio codec is now widely available on android, both devices (smartphone and headphone) must support aptx so that it can use the codec, however , there is no way to tell if the codec is actually in use But I searched a lot to find something and finally got my hand on an apk I extracted from sony xz3 stock pie rom , it shows a brief toast notification when the aptx codec is being used over bluetooth.
so I tried to copy the apk to my device (LG V30 stock pie) to this location >> system/app/AptxNotifier/ which was the original location on sony xz3 device (stock pie)
and changed permissions to 0644 and reboot
but it did not work it and I could no longer turn bluetooth on/off , but it can be reverted by simply deleteing the apk and everything back to normal
I can play around easily with apktool but I don't know what to edit
Is there a way to mod this apk so that it could work on my device ? any help would be appreciated
@Bronnel
AptX is an alternate Bluetooth audio codec from Qualcomm which aims to feature higher audio quality. You need a Bluetooth enabled device to pair with., what have a driver installed that sits on top of its Bluetooth stack. The mentioned APK - as it name implies - doesn't enable AptX: it simply notifies you whether AptX is in use or not. Just about all phones with the Android Oreo OS and higher support aptX HD which is really easy to activate.:
In Android -> Settings -> Developer Options select Audio Codec’. You will get a list of all the codecs your phone supports (including aptX HD). Now, simply select aptX HD, connect your (aptX HD-enabled) headphone and enjoy high-quality audio in no time.
jwoegerbauer said:
@Bronnel
AptX is an alternate Bluetooth audio codec from Qualcomm which aims to feature higher audio quality. You need a Bluetooth enabled device to pair with., what have a driver installed that sits on top of its Bluetooth stack. The mentioned APK - as it name implies - doesn't enable AptX: it simply notifies you whether AptX is in use or not. Just about all phones with the Android Oreo OS and higher support aptX HD which is really easy to activate.:
In Android -> Settings -> Developer Options select Audio Codec’. You will get a list of all the codecs your phone supports (including aptX HD). Now, simply select aptX HD, connect your (aptX HD-enabled) headphone and enjoy high-quality audio in no time.
Click to expand...
Click to collapse
thanks
I think you misunderstood me , I do not need to enable aptx , both my devices already support aptx , (LG V30 and my headphoone iDeadusa s204) and I already know that aptx is being used (because I easily notice the difference in sound quality) , what I want is toast notification to tell me that aptx is being used , this apk is doing just that but it needs to be modded so that it work on my V30, I hope I'm clear.
anyone out there to help with this?
KarlaPatton said:
I also need something like you
Click to expand...
Click to collapse
you can test the file and see if it works, but you need root, root explorer, which device do you have? which firmware version?