yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Mervingio:
Bud in the case of OP6T custom kernel fix the issue at least for now tell Google not fu** up things trying to innovate as simply as that.

Take care and not take bad this is why LG, Samsung, Pixel phones will become shadow and dust
[Android Software Development] EstherTakumi:
Did you already disable built in Dolby Atmos in Pixel 4?
[Android Software Development] yyz71:
Pixel 4 doesn't come dolby. Only their generic eq which is already disabled..

---------- Post added at 06:37 PM ---------- Previous post was at 06:32 PM ----------

Naw I like new software.. I've always used the Google phones. The purity of Android what makes me stay with Google. I don't know about pixel becoming shadow and dust. But to each there own.
[Android Software Development] guitardedhero:
Lots of changes.
[Android Software Development] guitardedhero:
Sony Xperia 5
[Android Software Development] guitardedhero:
ZTE Axon 9 Pro
[Android Software Development] guitardedhero:
The current difference in size between Axon 9 Pro and Sony Xperia 5 ports is due to the Xperia 5 port content not yet bundled into the apk like found in the Axon 9 Pro apk. This bundling of the apk has no impact on the mod and is only done to provide the ability to construct the port installation even if only the apk inside the zip is found.
[Android Software Development] gyuuuu:
awesome pixel 3 app run

xperia flashing

but dolby not working
[Android Software Development] ramrastus:
Which one should I flash? Suggest me bro?
[Android Software Development] JakunTech1010:
OK so while attempting to install this, MagiskManager suddenly closed. I attempted to reinstall it 2-3 times before it finally said done. But when I reboot, my phone refused to boot: it stuck at boot animation about a few sec before the screen darken and completely reboot to recovery. Why is that happened, I've installed MagiskManager Canary build but still the same issues.

Well the DolbyAtmos_0.89-ACDB.zip file doesn't have this issues. I'm using LineageOS 17
[Android Software Development] guitardedhero:
Damn, you sure got my hopes up lol.

I believe your device prevents /vendor/etc/vintf/manifest.xml from editing. Check the top of the file for any sign of "dolby".

This one or this one.

Did any of the progress text appear in the console window? I'm wondering if it's the damn "√" wreaking havoc for a few...
[Android Software Development] gyuuuu:
manifest.xml not exist dolby but app run
[Android Software Development] JakunTech1010:
Well yes it does make some progress, it does show some text:

- First attempt: it says compatibility detected and then MagiskManager exit

- Second attempt: it says Dolby hwservice already registered ( huh I remembered that I've removed old DolbyAtmos)

- Last attempt: It done, but when I reboot, it stuck at boot animation and then darken and then reboot to recovery

Right now I'm using DolbyAtmos_0.89-ACDB.zip but I couldn't get it to work with Viper4android Legacy 2.5.0.5 although I've managed to get previous version to work with V4A Legacy. V4A driver version is 0.0.0.0.

UPDATE: So I install DolbyAtmos_0.89-ACDB.zip and then Viper Legacy and then restart and then DolbyAtmos and then restart. The phone then stuck in bootanimation and then darken and then restart into recovery. :crying:
[Android Software Development] gyuuuu:
su -c dumpsys media.audio_flinger

dolby no exist
[Android Software Development] Adamk102:
DolbyAtmos-axon9-0.89-ACDB installs without a problem. the application works only when it is enabled. when minimized for background operation, the Dolby sound effect disappears.
[Android Software Development] guitardedhero:
You might try disabling the sauron module. This might be the first I've heard this particular behavior. There doesn't appear to be anything but the two modules.
[Android Software Development] Lord Sithek:
Hi. Thanks for the new uploads! I flashed ViperAtmos 0.2 from your GDrive, but on my device behavior is pretty similar to the previous version. One additional thing I've observed meantime: After the first installation of Atmos, Dolby doesn't have an impact on audio. But when I clear the app's data and reboot, it starts to proccess the sound.
[Android Software Development] ramrastus:
ony Xperia 5 zip not booting bro..

And viper atoms 0.2 it's booting.. But when I close the recent app (v4a) suddenly the effect was turned off.. And app layout was not fit on ma device (op7pro)
[Android Software Development] ckanth12:
Any difference between these?

I didn't find any major differences.
[Android Software Development] UCHIHA:
Hi dev,,,

Long time silently follow your post.

And many many trial i do. All my action always based on your suggestion and answer to others.

Now,,, finally im sucessfully to make it fully working.

And you know what, i combine it with aml+ainur_nasril (till now, ainur is always the best audio in my point of view but it missing dsp - jamesdsp is not my choice)

What i learn is : some kernel device always prevent this module to make action in related file.

So, makesure you check all related file.

(You can read it by inspecting module file & script, one by one)

Now im very happy and took my time to post here. Respectly & proudly to say thanks to you.

Hope other not giveup like me.

If i dont bother you,

I have some question :

- sony or axon based , which one the better or you recommend?

- some last file you share

(DolbyAtmos-axon9-0.89-ACDB.zip, DolbyAtmos-xperia5-0.07-ACDB.zip, DolbyAtmos_0.89-ACDB.zip)

Which one the nearly clean port?

Thanks dev ??
[Android Software Development] ShadoV90:
[MENTION=4445176]guitardedhero[/MENTION]

Both zips are working for me.

I see that xperia apk have dialog enhancer slider :)

I see too that xperia atmos sounds distorted on LG G7.

I hear limiter (instant cutting volume, especially on bass) nearly all the time.

Probably because of aggressive volume leveler which boosts output digitally.

I know i know :D i can change this in dax_default.xml

But default settings are too aggressive for some phones.

Edit: i don't know how other phones behave, but LG G7 don't like any equalization except it's own equalizer (adjusting something normalizes sound output automatically).

Every boost in bass (easiest to hear) means distortion. I mean you can hear that bass is not natural. It have less attack than expected. It feels like something cuts bass in middle of his attack :P

That's why i think my phone have maximized digital output from start. I must drop down preamp to adjust equalizer by the same value.

Atmos have hard time here because everything wants boost sound here or there :D

But i love surround virtualizer from atmos.

Unfortunately virtualizer (in both zips) boosts digital output by ~6dB so unless i adjust global digital preamp, i am getting distorted sound.

I wanted to blame DAC but bluetooth headphones sounds similar.

It's only my phone with that behavior?

I hope everyone will understand what i am want to tell.

English isn't my primary language, but i'm trying to be as clear as possible.
[Android Software Development] iLee:
are there people who modded there dax-default to there liking and are willing to share here i would like to test some
[Android Software Development] Mervingio:
the difference of the zips is the audio quality? i`m reakky happy with the Redux on my OP6T

did you think can add to the Sony Xperia 5 zip the Sony Music app? latest version not work on A10 this music app is simply, powerful and great

take care :good:
[Android Software Development] marquelito:
So i was on no twrp stock rom rooted. Now ive flashed stock custom rom with twrp, installed viperatmos0.2. All registered and config in 2 files above, viper dont install driver, same. Dolby doesnt open, fc. Still. What files can i provide now? (After all i pushed viperfx to system/priv-app as when installed other versions, and got the same result. I didnt saw permissions xml in permission folder for app, not needed?)
[Android Software Development] MitchiePitchie:
A5 2017 los17 q

Testing in lineage os 17 AndroidQ, using Dolby Xperia 5

Can't turn on the dolby, viper cant install the drivers somehow. Any ideas whats happening?

Edit: can confirm that all three dolbys and the viper modules arent working for me.

Edit 2: the rom is currently in alpha stage and selinux is currently broken so yeah, my fault. Sorry
[Android Software Development] Adamk102:
[MENTION=4445176]guitardedhero[/MENTION], I am very impressed with your work. Viper Atmos works. Hassle-free installation. Viper works great, I only have a problem with Dolby Atmos. When the application is active it works. however, when I minimize or turn on other applications the sound effects fade away.
[Android Software Development] nespresiii9999:
Phillips

don't know
[Android Software Development] guitardedhero:
Dolby Audio™ courtesy of Motorola One Power's latest Android Pie firmware.
[Android Software Development] JakunTech1010:
Will it work on Android Q with Viper 2.5.0.5.
[Android Software Development] guitardedhero:
I think I experienced this earlier today. It seemed to be a borked update/installation. I deleted the dolbyatmos module folder, deleted the modules_update folder, su -c killall zygote, and tried again with success.

I must not be handling the update as well as the new installation in the script, apparently.
[Android Software Development] guitardedhero:
As long as you pass the compatibility check, chances are very, very good. :good:
[Android Software Development] JakunTech1010:
OK so I installed DolbyAudio-moto-onepower-0.01-ACDB.zip, great it worked ( Although at first I have to turn it off and on to make it truly work ). When I tried to install it, at first Magisk Manager show app keep stopping, second attempt I got compatibility check but when it says compatibility detected Magisk exit and got back to the app. Third time it got through everything and installed. Now it working perfectly. I will now tried to make it work with Viper. Wish me luck ;) :good:
[Android Software Development] guitardedhero:
You might try changing the value for LG's sound normalizer property to false in build.prop.

Your very detailed description led my directly to this thought. :good:
[Android Software Development] ShadoV90:
[MENTION=4445176]guitardedhero[/MENTION]

Can you tell me where that normlizer is in build.prop?

I sent both system and vendor.

I was looking for that normalizer thing, but i don't see anything like that.
[Android Software Development] guitardedhero:
Try this:

getprop > /sdcard/getprop.txt

Attach /sdcard/getprop.txt to a reply.

I promise no personal information or data will be revealed.
[Android Software Development] Lilcode:
Dolby atoms for 32bit pie plss.
[Android Software Development] Bogdans29:
dont force you can read it in near future there will be 32bit ver i wait too.. Pls let guys first finish 64bit..
[Android Software Development] whiplash1:
Flashed this on Beryllium, Evo X 4.0, magisk 20.3. Works well with Spotify, YouTube etc. Messes with 24bit processing in Poweramp. Also the effect disengages when you press back button when inside the Dolby app, however doesn't disengage when pressing home button to exit the app.

I checked with a 24bit FLAC file in Poweramp and same song on Spotify.
[Android Software Development] Skittles9823:
Ayyye Periphery :highfive:
[Android Software Development] whiplash1:
I do love me some good prog metal :silly:
[Android Software Development] ShadoV90:
[MENTION=4445176]guitardedhero[/MENTION]

Here it is.

EDIT: Motorola version is working, but changes in system.prop (i know these are necessary to work) disables AOD in my LG G7 xD
[Android Software Development] adi_cr_7:
I'm using DolbyAtmos_0.89-ACDB.zip . App is installed but not opening! What can i do?
[Android Software Development] Ceejay343:
Hmm trying the Dolby Audio 0.01 does install but complains about dolby services and stuff already registered. Upon reboot it then fails to boot goes straight to fastboot.

I had ViperAtmos redux on the phone which i firstly deleted from Magisk. Apparently the uninstall doesnt take out everything?

Weird thing is upon a dirty flash of my Rom + gapps + Magisk, phone will boot and Magisk shows Dolby Audio as installed, however the app will not open, crashlog.
[Android Software Development] guitardedhero:
Lennon:

ACDB stands for:

Audio Configuration Database

Sound familiar?

Alternative to AML since I'm unable to come up with a solution at this time that doesn't force the user or another dev to do anything.

It's very simple and easy to incorporate into existing mods ( simply adding some lines of code already included in the zip's instructions.txt ).

You guys don't have to do anything.

Except have ACDB installed.

ACDB will exterminate any and all configurations existing in all other modules (except those found in AML).

When installed, it copies the original device configurations to the ACDB module, so you'll basically start off with the stock configurations.

Mods with the ACDB code merely patch existing configurations found in the ACDB module instead of targeting, copying, and patching the device configurations - saving dev's a lot of time and effort trying to get to the correct ones on your device.

This module will break every mod relying on a configuration, forcing action on the dev to add the ACDB code or the user to delete the ACDB module.

But like I said, this actually is a convenience for the dev since there is no variable as to whether the relevant configurations exist.
[Android Software Development] Adamk102:
where can I find the Viper itself. with the module viper atmos? is a great application

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] marquelito:
Installed ACBD, then atmos 0.89-acbd. Still fc.

Attatched matlog on dolby
[Android Software Development] marquelito:
Sorry for double post. Forgot to put daxservice, dms and audioeffect
[Android Software Development] shantam3108:
None of the Dolby version work for me logs attached
[Android Software Development] shantam3108:
Logs
[Android Software Development] laugeek57:
Aosip Derpfest android Q no error during installation but no response from the Dolby application ??
[Android Software Development] Lord Sithek:
Can you open the app or can't you open it at all? If the first, try to turn Dolby off, then reboot and turn it on. I'm on the same ROM and this is the only way I'm able to get it work at the moment...
[Android Software Development] laugeek57:
Hello, bro

I can't open app no reponse... :(

tested with 0.64/0.83./0.89 an acdb 0.15
[Android Software Development] yyz71:
Have managed to get this working on you're pixel 3?
[Android Software Development] laugeek57:
DolbyAudio-moto-onepower-0.01-ACDB Works fine on AOSIP Derpfest Q OP7 :D

Thank's Guitardedhero good job :cowboy:
[Android Software Development] Disky5:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.dolby.dax2appUI/com.dolby.dax2appUI.MainActivity}: java.lang.RuntimeException: DolbyAudioEffect: set/get parameter error

at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2947)

at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3082)

at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)

at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)

at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1832)

at android.os.Handler.dispatchMessage(Handler.java:106)

at android.os.Looper.loop(Looper.java:201)

at android.app.ActivityThread.main(ActivityThread.java:6821)

at java.lang.reflect.Method.invoke(Native Method)

at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)

Caused by: java.lang.RuntimeException: DolbyAudioEffect: set/get parameter error

at com.dolby.dax.DolbyAudioEffect.checkReturnValue(DolbyAudioEffect.java:282)

at com.dolby.dax.DolbyAudioEffect.getIntParam(DolbyAudioEffect.java:266)

at com.dolby.dax.DolbyAudioEffect.getNumOfProfiles(DolbyAudioEffect.java:570)

at com.dolby.dax.DolbyAudioEffect.<init>(DolbyAudioEffect.java:114)

at com.motorola.dlbafx.DolbyAudioEffectManager.checkDolbyInstance(DolbyAudioEffectManager.java:55)

at com.motorola.dlbafx.DolbyAudioEffectManager.getDolbyAudioEffect(DolbyAudioEffectManager.java:42)

at com.dolby.dax2appUI.MainActivity.onCreate(MainActivity.java:337)

at android.app.Activity.performCreate(Activity.java:7224)

at android.app.Activity.performCreate(Activity.java:7213)

at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1272)

at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2927)

... 11 more
[Android Software Development] crackerjack1957:
Anyone get Dolby working on Pixel stock rom or any device on stock............Dolby require other roms?
[Android Software Development] acuicultor:
Working flawesly here in stock oos rom.
[Android Software Development] crackerjack1957:
You have to do anything else beside flash module with Magisk?
[Android Software Development] Wolfcity:
As I see Dolby from a Motorola device, any news about a 32bit build?

Or a way to make it work on arm?
[Android Software Development] HatchetEgg:
Would there be any chance of tasker integration?

For example, so you can switch off the dsp when headphones are unplugged automatically?

Or even load your Atmos profile depending on app?
[Android Software Development] acuicultor:
Nope, just that.
[Android Software Development] Skittles9823:
Nah, I'm on Android 10 so the manifest.xml can't be patched. I have to wait untill topjohnwu adds a way to overlay files pre-init again.
[Android Software Development] exodius48:
[MENTION=4445176]guitardedhero[/MENTION] Just reporting, heeyy.. this ViPERAtmos_Redux-0.2 is great combination. Working great on havoc 3.1 android 10. Previous version 0.10 make my device bootloop after installing viper driver. And that make me suprised is without aml both of those can be processed the audio mod... WOOOOOWWW

Please support this great module ... keep up the great job brayy.

Btw, could you update 1st post with working link of your latest release? coz it make me confused to find latest version of dolby, viper and viperatmos redux, i need to search your post to find latest release.
[Android Software Development] Qwerty182:
After instal this module i face an issue when i capture a picture in gcam sir
[Android Software Development] aarkee:
Why Dolby Atmos doesn't detect to AML?
[Android Software Development] Bogdans29:
bcs AML developer didn't implemented module..
[Android Software Development] Bogdans29:
deleted
[Android Software Development] adi_cr_7:
Sir finally dolby atmos xperia port opening. Its opening now but it says dolby atmos is turned off.
[Android Software Development] Skyllery:
Nevermind
[Android Software Development] laugeek57:
Try Xperia5 dolby atmos no broke my Gcam on my OP7 AOSIP Derpfest Q :good:
[Android Software Development] ShadoV90:
To everyone who wants complain about "some apps don't work after install motorola dolby".

Don't worry. This is normal.

This module changes "on paper" device model to motorola one as well as device manufacturer,brand to motorola. So every app prepared for certain model like system app for Always on display for my LG G7 will not work.
[Android Software Development] Bogdans29:
Deleted
[Android Software Development] ShadoV90:
It's just information. Not everyone wants to sacrifice usability of his own phone. In case of my AOD it's no problem. But some people don't know what's happen and will treat unusual behavior of their device as an issue, which is not if an app is model dependent.

There is one more problem. Some other audio mods like DTS Headphone X or DTS:X Ultra under UltraM8 development. Because this audio mod needs to change model device too (into ASUS XQ00D or Asus Zenfone 5 if i'm correct).

So these mods can't be used together with Motorola Dolby.

In case of problems of compatibility with other apps it will be better to try using other dolby options like axon 9 pro :P
[Android Software Development] marquelito:
Cant get any to work, with or without acdb installed. Motorola Version got me booting to download mode, not even start to boot. So sad :( anyone got it workin on s9+ android Q?
[Android Software Development] laugeek57:
Try Other version bro 0.64 /0.89/ xperia5 ;)
[Android Software Development] gokart2:
[MENTION=4445176]guitardedhero[/MENTION]

Was wondering if a modifiable echo script could be used to change preset values on .89? Idea is for those of us who have the app working, but WITHOUT GUI to be able to utilize it better. Or optimize it a bit better for user liking?

Example:

echo dolbyatmos_mode=music
echo dolbyatmos_EQ_40hz=6.2
echo dolbyatmos_EQ_60hz=6.5
echo dolbyatmos_EQ_80hz=5.7
echo dolbyatmos_volume-leveler=off
echo dolbyatmos_bass-enhancer=on

Obviously code is just for reference. But it would allow no GUI users to actually change settings....I think? And I know how you like scripting. Or even an install set-up like how arise is with the arise_customize.prop? Just thinking?
[Android Software Development] Jbb3393:
Moto Atmos broke gcam on my htc U11.
[Android Software Development] Wolfcity:
First of all thank you for building a 32bit version too.

I installed it the moto6play version on my testing device, Motorola Moto G2014(titan) running Resurrection Remix 7.0.2 (Pie)with magisk 20.3 stable, selinux permissive.

what I tried:

First uninstall

-AML

-James DSP

-Ainur Sauron

Then install -DolbyAudio-moto-g6-32bit-0.01-ACDB.zip

using Magisk Manager.

Install went through without an error (see attached log).

Dolby force closed several times, no way to start it.

Device was named as G6play in settings as expected.

Attached:

Magisk install log

Crash log link: https://del.dog/ynegimengo

manifest.xml

dumpsys audio.media-flinger

[MENTION=4445176]guitardedhero[/MENTION]: If you need anything else to troubleshoot please let me know what you need.

Thx for your commitment!
[Android Software Development] laugeek57:
With Xperia5 works?
[Android Software Development] marquelito:
I already tried all and viperatmos :crying:
[Android Software Development] laugeek57:
Sorry bro try without viper and others mods in magisk :angel:
[Android Software Development] marquelito:
Done it too :(
[Android Software Development] laugeek57:
Give a logcat for Guitardedhero....
[Android Software Development] marquelito:
Already done it too
[Android Software Development] Jbb3393:
Xperia5 broke my camera too. Atmos .89 ACDB does not break my camera.
[Android Software Development] Adamk102:
Viper Atmos work Perfect! Thanks dev

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] EstherTakumi:
So far I'm satisfied with the thing are right now.

I'm using One Plus 6 OB4, been using both ViPERAtmos-Redux0.031.zip and DolbyAtmos_0.89-ACDB.zip without issue, because I dont know which one should I flash and use lol, as long rhey are know issue, i will keep using it.

Thank you so much Guitarhero, I'm appreciate you hardwork! keep it up!
[Android Software Development] panchogg:
Where can i download your Dolby Atmos?
[Android Software Development] guitardedhero:
Sorry, guys. I've been sick as hell the past couple days. I'm gonna try to catch up really soon. :good:
[Android Software Development] RustleEvil:
Ur health is priority take rest
[Android Software Development] avaie:
[MENTION=4445176]guitardedhero[/MENTION]

Can you look through my logs and disclose what could be the reason why there are no audio-processing? A stock function prevents all sound mods from working. This is from LG V40. Thanks.
[Android Software Development] ramrastus:
Take rest bro.
[Android Software Development] Wolfcity:
This.

In Germany we have the saying "Without health everything is nothing".
[Android Software Development] EstherTakumi:
You can find it in this thread