Ainur Audio - OnePlus 6T Questions & Answers

Does anyone here use the Ainur Audio mods at all? If so which versions do you prefer? I currently run V4Arise that was installed with the XXXNoLimits rom and was looking for a little extra something.

I have it running on OOS OB14. I'm running stock though, so no custom ROM/Magisk-based ROM. I am using it with Dolby Digital Plus, V4A FX 2.7.1.0 and the stereo mod. You have to install it in a particular order to get everything running properly. This is what I did:
1. Install Dolby Digital Plus and reboot.
2. Start Dolby Digital Plus and make sure it runs.
3. Install V4A and reboot.
4. Start V4A and install the driver. Reboot when prompted.
5. Install stereo mod and reboot.
6. Install Ainur Sauron, then Audio Compatibility Patch, then Audio Modification Library. Reboot after all 3 installed.
Everything appears to work fine with no audio issues. I did have V4A 2.4.0.4 running previously and used the same procedure to install. Only difference I noticed is the audio seemed a bit louder using the same profile on the older V4A. I had the same setup running when I had HavocOS running too.
I did try Ainur Sauron when I had xXxNoLimits running on OOS with Dolby and V4A installed but I couldn't get it to work. It might be because I had both Dolby and V4A installed. It might work if only one is installed but I can't guarantee that as I never tried just one mod. In the end, I settled for just running the 2 mods and stereo sound without Ainur Sauron installed.

dj_ooms said:
I have it running on OOS OB14. I'm running stock though, so no custom ROM/Magisk-based ROM. I am using it with Dolby Digital Plus, V4A FX 2.7.1.0 and the stereo mod. You have to install it in a particular order to get everything running properly. This is what I did:
<snap>
Click to expand...
Click to collapse
Hi, can you test whether bluetooth audio is working with this setup?

Okay. Gave it a try on OB14 using my Bluetooth headphones. DDP does not appear to work. Audio sounds exactly the same whether it is switched on or off and trying to change the mode. V4A does work though. I am quite positive that both worked fine when I was running HavocOS. To be honest, I find the RAM management annoying on OOS as V4A and DDP would regularly get killed off even though they were installed as system apps. I might go back to HavocOS as surprisingly, I got better battery life on that compared to stock, though OOS was a tad bit smoother overall. This seems to be contrary to what I have mostly on this forum.

I removed all the audio mods I had and then reinstalled everything using an older version of Dolby Digital Plus. Everything seems to be working fine now.

Related

Customizing stock ROM

Hi guys, I'm getting bugs while trying to customize my stock ROM.
It uses to get stuck when flashing things like: Magisk, XTREMEMusic, etc.
After rooting with SuperSU fix, sometimes boot, sometimes don't. Depends on how many changes I've made in the system partition before rebooting.
Any hints on this? In custom ROMs it works perfectly, but audio quality is really horrible. I can even hear little clicks and delays in the output, not forgetting the noise and weird sounds coming from the CPU directly to the output.
Maybe because of dm-verity? If yes, how can I disable it or get a custom kernel to work in the stock ROM? Squid kernel works but gets the video card laggy and the audio output stuttered all the time.
Thanks in advance for your help.

[ROM] LineageOS 14.1 w/ SonyLOS 7.1 binaries, AOSP Kernel, Viper4Android, Apollo

Hi,
in my spare free time I compiled a new unofficial LineageOS 14.1 ROM on my beloved Phenom II system with ECC RAM and made it available to you for 90 days from
https://www.filefactory.com/file/5fqmz223n9gx/lineage-14.1-20170403-UNOFFICIAL-SonyLOS-kugo.zip
https://www.filefactory.com/file/121p40o8v8gb/lineage-14.1-20170403-UNOFFICIAL-SonyLOS-kugo.zip.md5sum
The ROM can be installed through a recovery like TWRP. I also applied some modifications, in particular:
- the SonyLOS kernel has been replaced with the Sony AOSP version which seemed to be more up to date
- using some 7.1 binaries of Sony AOSP instead of the 7.0 binaries used earlier enabling some more features (?)
- replaced the LineageOS camera with the Simple Camera app
- integrated Total Commander, Apollo music player v2, SELinux permission changer and Viper4Android apps since I need them
Consequently,
- patchlevel now is March 5th, 2017
- the fingerprint sensor now seems to be usable to unlock your device
- the FM radio works (however, you have to manually scan through the stations once because automatically finding the stations initially still does not seem to work completely)
- the selfie camera image no longer will be upside down (seemed to be an issue with the LineageOS camera app, also will work correctly with i.e. Focal if you prefer a sophisticated app instead of Simple Camera)
- I can now use Apollo again as I did on the Z1 compact with CM 12
- the bass boost and equalizer are back with Viper, you just need to invoke the SELinux changer on the rooted device and install the drivers initially through Viper itself
Thanks fly out to Sony AOSP, SonyLOS and the app providers. Feedback is also very welcome.
Regards,
jtk_de
@admin: Could we please move this thread and my previous one to the ROM section ? I'm still not allowed to post something there
Great to see you're still updating your ROM. Don't understand why you upload at filefactory (sloooow download) instead of androidfilehost for example. Will flash your ROM tomorrow.
- should I flash a stock ROM first or does it not matter which version I'm coming from
- what do I need the .md5sum file for?
- gapps are not included, right?
I tried to use androidfilehost but my uploads got interrupted so I had to stick with filefactory for now. You don't need to flash the stock ROM first, just wipe the system, cache etc. partitions in your recovery and flash the .zip.
The md5sum checksum file is there to ensure the ROM integrity and is not needed for the flash, however, TWRP optionally can read it and veryify that the ROM has been correctly downloaded and copied to your phone's storage. Gapps is not included since I use alternative apps, hence it must be installed separately.
Root access is integrated already and can be controlled via the developer settings. The only issue I experienced so far is that the volume cannot be altered yet during phone calls
I don't get viper4android to work. I install the drivers, reboot my device and then viper4android prompts me to install the drivers again. Am I doing something wrong?
Micka84 said:
I don't get viper4android to work. I install the drivers, reboot my device and then viper4android prompts me to install the drivers again. Am I doing something wrong?
Click to expand...
Click to collapse
You need to enable root first and start the SELinuxModeChanger installed with the ROM and set SELinux to "Permissive". Then the Viper drivers can be installed which can take quite long (a minute or so). If an Android dialog pops up because of this confirm that you would like to wait longer. Then reboot as indicated and enjoy the bass
That worked for me thank you
Hey,
many thanks for that ROM. Unfortunately i end up in a never ending boot animation. If i get in recovery (TWRP) and tell him to reboot, it tells me that no OS is installed. Any hints how this can be solved?
Thanks for any advice!
dreadavi said:
Hey,
many thanks for that ROM. Unfortunately i end up in a never ending boot animation. If i get in recovery (TWRP) and tell him to reboot, it tells me that no OS is installed. Any hints how this can be solved?
Thanks for any advice!
Click to expand...
Click to collapse
Hi!
I think there aren't any os on your device, thats wha twrp sad that... because, your systems encrypted. You could remove it. Try to flash again twrp from fastboot, than clear cache ( fastboot format cache ) and userdata ( fastboot format userdata ) from flashtools too. After that boot to twrp, than you could mount system, than flash the whole cm rom again. After that, i think it will boot correctly.
lba810701 said:
Hi!
I think there aren't any os on your device, thats wha twrp sad that... because, your systems encrypted. You could remove it. Try to flash again twrp from fastboot, than clear cache ( fastboot format cache ) and userdata ( fastboot format userdata ) from flashtools too. After that boot to twrp, than you could mount system, than flash the whole cm rom again. After that, i think it will boot correctly.
Click to expand...
Click to collapse
Thanks for the hint. Did what you said, but i cant mount system in recovery. It cant be selected in the list. Any other suggestions? Ok solved it. had to flash stock rom and boot.img before the steps you asked me to try. Thank you!
Thank you for putting this ROM together! There are the following problems on the OmniROM:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
Is this still the case for your Lineage ROM?
avion540 said:
Thank you for putting this ROM together! There are the following problems on the OmniROM:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
Is this still the case for your Lineage ROM?
Click to expand...
Click to collapse
1. Yes, the volume can't be changed during phonecalls
2. Didn't notice any echos so far
3. True
Could you try uploading to mega.nz? FileFactory is so slow
minimum Brightness
Hey!
i was just wondering if its possible to lower the minimal brightness a bit more. because minimal brightness is quite bright still. Im using this ROM for a few days now. Everything works pretty fine, but the battery life is a bit short for what i was expecting. If i dont use extreme battery saving mode its always around 24 hours. i barely do phone calls and i use it not very intensively... Highest Consumer is standby with 5%, which i think is wierd, isnĀ“t it?
:good: Kudos. Everything seems to work well aside from the Bluetooth Audio cutting out after a few minutes. Overall I am really happy with it - happy enough that it's my daily driver.
Hi!
ROM will be better and better. Thanks.
Battery charging speed a bit slow, and if I'm using a mobil net, it's draining a little fast, plus in the evening, with wifi on, it goes down nearly 5%>. Camera is good. But, im using open cam software from google play. Fingerprint sensor working good, just a little hard to configure it. I'm using substratum theme engine, and i can theme most of the base and google apps. ( Except fingerprint sensor, with themed settings, the fingerprint setup screen cracked... but inthinknits theme problem ) And about bluethooth.. yes, it's dropping the connection after a few secs. But, if you left it, then reconnect automatically and just after that, it goes good. Until you turn it off. I used a sony sbh70 wireless headset with power amp.
And echo sound in calling. I can't hear echo, but other peoples in line, they sad it. They hear onselfs twice.. :/
If you would like it, maybe i can upload a logfile ( with matlog ) about the bluethooth problem.
Anyway, thanks foe thiese rom for our x compact.
It's good to see some other people are using the ROM and testing things that I can't test
According to my own experience battery lifetime is around 2-3 days when surfing via wi-fi, listening to music and calling from time to time. Battery charging with the Sony AC adapter coming with the phone is quite quick compared to the Z1C although the battery capacity is higher.
If I make another build I'll upload it to some faster provider though.
hello all,
give it some news there? Last entry April 2017.....
Hi all, are there some updates? I love Lineage OS
I'm wondering why there isn't an official build for the Xperia X Compact yet ? If I google "kugo lineageos" I get a hit for a stats page:
https://stats.lineageos.org/model/kugo
Which just says the page isn't rendered yet, but obviously someone has been devoting his/her time to the kugo. What could be the hold up? Same goes for the lack of other roms btw. It seems Sony is quite open towards the community but somehow this hasn't resulted in the overwhelming amount of roms I was hoping for ... It's quite underwhelming in fact. Could it be not enough (knowledgable) people own an Xperia X Compact ?
harryharryharry said:
It seems Sony is quite open towards the community but somehow this hasn't resulted in the overwhelming amount of roms I was hoping for ... It's quite underwhelming in fact. Could it be not enough (knowledgable) people own an Xperia X Compact ?
Click to expand...
Click to collapse
Sony gives us a sliver of what is needed for AOSP to run, camera, bluetooth, wifi, and radio band stuff all has to be manually made to work. The z3 line was the ONLY xperia line to ever get mainstream AOSP support from devs. If you bought your xperia thinking Sony's AOSP program was good you were sadly mistaken.

Unofficial Xposed Module for Nougat on Lineage OS 14.2

Has anyone tried to flash the Xposed Module that came out earlier today/yesterday? If you don't know what I'm talking about, watch this video real quick: https://youtu.be/eADZK17N7rk
I understand it is unofficial and might be unstable with lots of bugs, & that some modules currently don't work, but would I be at (more) risk of bricking my phone if I flashed it?
I flashed it yesterday and everything went well. The bugs are the following that I've experienced:
1. In order to download a module, you must press save instead of download. After that, a toast notification will prompt you on where to go in your file manager to find the apk.
2. Some force closes such as kernel auditor and Google/services. Those were resolved later on for me.
3. I noticed the fingerprint scanner got a little sluggish after, but a reboot fixed that.
4. Sorta made the UI a little sluggish as well so be careful if you've already under clocked your processor.
There we go. I am currently on the latest version of Lineage OS. I uninstalled it today, but I plan on installing it again with a new ROM tonight.
It doesn't seem to work on AOSP or Extended AOSP, but apparently seems to work on other ROMs. Want to switch ROMs unless EAOSP fixes that because I really want Amplify again

On US996 Lineage 18.1 Rooted and can't get V4A to process

Edit: figured out 17.1 so went back and repeated on 18.1 and worked so no issues. Just took some tinkering
I'm on 18.1 (official) and I had no issue at all with v4a. Also using Jamesdsp without issue. Did you install android audio patch and audio modification library? You need to.
I got everything working after playing with it for a couple days. It was just a long time since I rooted and things changed a bit since. v4a alone works fine without those mods after i removed audiofx.
Yes but fyi, adding those magisk modules allows you to use more than 1 audio equilzer at the same time, in which case you wouldn't have had to find and delete audiofx which is why v4a wasn't woking. And you might wish to add JamesDSP as well. I filp between both, the crossfeed on jdsp is kinda cool. Just fyi : D
I

Adjust audio balance on MM

Hi all, I need some help to balance the audio on my nexus 7 android 6. One of my speakers sounds a bit louder than the other so I'm trying to solve that. I'm on stock android 6.0.1 and I can't install viper4android, I tried everything but it continue to ask me to install the driver and reboot (I did that but still ask me). So is there some method to adjust the audio balance? I'm rooted with magisk. Please I'm desperate

Categories

Resources