yashsingh1/xdaforums huggingface dataset:
[Android Software Development] laugeek57:
I flash Xperia5 i cant turn on Dolby Atmos :(

I remove xpreia5

I flash one power motorola works fine but broke Gcam :crying:

I remove one power....

I flash Xperia5 Tadaa I can turn on Dolby Atmos it's strange lol :D

---------- Post added at 06:57 PM ---------- Previous post was at 06:51 PM ----------

Try flash one power motorola before Xperia5 for me works i can turn on Dolby..

.It's strange but worked for me lol
[Android Software Development] guitardedhero:
This indicates to me that the current function to patch /vendor/etc/vintf/manifest.xml is finally successful for you, whereas the function used in that particular Xperia 5 zip was unsuccessful.

This is because /vendor/etc/vintf/manifest.xml is only effective as it exists on the partition. Including a patched manifest.xml within the module simply does not link to the partition early enough for anything added to the file be registered.

Such an edit in /vendor or /system will remain until the partition is flashed over. Even deleting the entire module will have no effect on a patched manifest.xml. Of course, if manifest.xml.bak exists (as is done when patched by the installation script), restoration of manifest.xml is possible with this backup file.
[Android Software Development] JakunTech1010:
Managed to get DolbyAudio Motorola One Power port work with Viper4Android now. Here's how I do it:

1. Install Magisk (Well OBVIOUSLY)

2. Flash DolbyAudio and don't restart

3. Flash viper4android 2.7.1.0 (or 2.5.0.5, your choice) and reboot

4. Reflash DolbyAudio and reboot

5. Enjoy

I don't know why but I can't get Dolby 0.89 ZTE port or Xperia5 or Xperia5 sound system port work with Viper4Android ( I got to step 4 then reboot then bootloop :confused: ).

If your solution is using ViperAtmos Redux, then sorry but I can't get it work: Atmos work fine, but Viper driver status is abnormal and version is 0.0.0.0 :confused: .

If you got it to work, please let me know how

I'm using LOS 17 for A70 by Grarak
[Android Software Development] guitardedhero:
Razer™

Note: All Dolby Atmos/Audio systems except for Axon 9 Pro include license checks resolved by system.prop changing the values for the following four properties:

ro.product.model=
ro.product.brand=
ro.product.device=
ro.product.manufacturer=

This currently breaks some form of device functionality outside of the Dolby system for some users - camera, for example - so be aware.

This will hopefully be temporary as I have some ideas for license checks that will seek unique property values and not native ones.
[Android Software Development] Bogdans29:
Just to remind on page 428 i left some logs if you interested to see..you can check whan you be healthy again..
[Android Software Development] ShadoV90:
"This will hopefully be temporary as I have some ideas for license checks that will seek unique property values and not native ones."

Wow. This is interesting. I am very curious how you want to "cheat" license checks. I'm curious, because i didn't see anyone who did it.
[Android Software Development] guitardedhero:
MASSIVE emphasis on "hopefully" lol.
[Android Software Development] ShadoV90:
Oh. But i hope you will figure out how to cheat it. I know there is low chance to do that, but i have hope, because it will not break usability of some apps :D
[Android Software Development] guitardedhero:
Razer™ 2
[Android Software Development] JakunTech1010:
OK will give it a try. Currently using Motorola One Power port because it doesn't cause bootloop like Xperia5 or ZTE Axon when trying it with Viper4Android :good:.

UPDATE: Alright I've installed it alongside Viper and so far no bootloop :good:, Dolby is working and Viper driver is good. Everything is great :good:. But did the Demo inside Dolby app suppose to have sound cyz I can't hear anything from the demo beside the sound of my phone disconnect charger :confused: .
[Android Software Development] Lord Sithek:
Is there any advantage of this mod over moto, xperia and axon, or is it just another option?

Edit: I flashed it for testing and it's working, but seems to has less impact on audio than moto mod on my device. Still, all of those Dolby mods have one thing in common: I can get them work only if after flashing I turn them off and reboot and then turn on. I have to do this before and after every reboot. Nevertheless, I'm greatful that I have working Dolby Atmos at all, it greatly enhances my music experience :highfive:
[Android Software Development] Bogdans29:
Is this for 64bit or 32?
[Android Software Development] Soumy1234:
Is acbd compatible with v4a 2.7.1.0 and/or Dolby Digital Plus?
[Android Software Development] ramrastus:
Bro how are you? How's your health now?

---------- Post added at 08:40 PM ---------- Previous post was at 08:33 PM ----------

Bro after flashing razer & razer 2 zip. Camera get FC & not taking pictures.. Tested both zip. Solution required?
[Android Software Development] shantam3108:
No success with modules with Los based roms.

For aosp based the modules worked but with Los based none of them Worked on both my devices. The app never launches just gives a force close message
[Android Software Development] shantam3108:
Log
[Android Software Development] guitardedhero:
Yeah, that certainly seems to be the case. Is the stock kernel base similar across different devices? I ask because kernels have been found to have that same effect - flashing an alternate kernel being all that was necessary in those cases.

I highly recommend testing one or more different kernels before abandoning LineageOS, if that is the rom you presently prefer.
[Android Software Development] shantam3108:
Mostly the same effect. I am using op3 and op5 with havoc and Los respectively and both are tested on custom as well as stock kernel and still the same. The app wouldn't just Launch.

Only dolby app that has launched was moto one power mod but after launching ui didn't work so couldn't toggle it on
[Android Software Development] ckanth12:
Has low volume on Movie preset compared to Dolby Atmos 0.89 ACDB, but has more controls - Bass Boost and Dialogue Enhancer.

Still better sounding than previous Razer 0.05.
[Android Software Development] guitardedhero:
The OnePlus 7t Pro dax_default.xml seems to be fully compatible with the Razer 2 Atmos system. You may want to give it a try. Differences you notice may be clear when comparing both xml's

Place in the module directory overwriting the existing dax_default.xml and reboot device to test.

Warning*

This xml is only compatible with the Razer 2 port and will break all other ports available at this time - including Razer (1) port
[Android Software Development] ckanth12:
Sounds better, but I will stick to 0.89 for now and wait for vanilla Dolby Atmos with more controls.

0.89 sounds better and has tile displaying active mode which makes it easy to use.

Looking forward to initial stable release.
[Android Software Development] Lord Sithek:
Wow, great elaboration. And great that you are willing to make those ports for us :good:
[Android Software Development] ramrastus:
I hope you definitely fix it [emoji1303] and you're my best sound software developer bro!

I never forgot our arise combo sound mod ever! Really love it [emoji4][emoji817]
[Android Software Development] laugeek57:
I confirm Razer 2 broke Gcam on OP7 aosip Derpfest Q

return on Xperia5 ok for turn on Dolby... ;)
[Android Software Development] guitardedhero:
Telegram
[Android Software Development] Bravin Joshua:
Works fine great work ?
[Android Software Development] RustleEvil:
Haha sorry I abbreviated I mean " Take rest your health is the first priority"
[Android Software Development] guitardedhero:
Xperia 5 Android 10 Dolby Atmos™ port (should be compatible with Pie, as well)

Edit*

Sorry, I forgot that I had left the minimum SDK of 29 in the apk's, so Android 10 only. This is intended as a full Android 10 Dolby Atmos™ port for Android 10 devices anyway.

Edit**

Version 0.02 ensures that installation executes only for Android 10 devices.

Edit***

Version 0.03 ensures that the app is able to be launched from the App Drawer.

Edit****

To hell with it. Please let this post die lol.
[Android Software Development] JakunTech1010:
Android 10 only huh ?

Perfect, I'll test these out now since my device is LOS 17 ( Android 10 ) and I don't mind that this sound mod changed my model number cuz nothing will break in LOS 17 :good:. However, that will be a huge problem on Samsung Stock ROM :eek:.
[Android Software Development] shantam3108:
Wew finally it worked on Los based rom. :angel:
[Android Software Development] guitardedhero:
Xperia 5 Android 10 Dolby Atmos™ port for Android 10 devices attached below.
[Android Software Development] JakunTech1010:
Great although the previous post make me a little bit confused because when I download 0.02 there's 0.03 and when I downloaded 0.03 that post is died and 0.04 released. Luckily I didn't flashed 0.03 or else...

Anyway this Xperia5 port did not cause bootloop when use with Viper4Android so that's a big improvement :good:. However, there's less options than Razer (both 1 and 2) port. But hey, at least it did not changed the model number so that's good if I'm using Samsung Stock ROM. :good:
[Android Software Development] guitardedhero:
Sorry. Not being able to test the installation is why it's taken 4 zips... until now:

Added an additional compatibility check.
[Android Software Development] yyz71:
This one installs ? but won't turn on.. But this is a start for me ?

Pixel 4 stock Feb security patch.
[Android Software Development] guitardedhero:
I think I've finally got it going lol.
[Android Software Development] yyz71:
Was just a matter of time bruh ? Like myself very persistent.. Good job my friend. Once I saw that it opened up I was a happy camper. Now to see if this will turn on... Fingers crossed lol.
[Android Software Development] JakunTech1010:
Didn't work

The previous version (0.03) have no problem and run fine

But this one isn't

I got bootloop with v4a

:crying: :crying:
[Android Software Development] grumpfli:
Hello

Which version for:

ZTE Axon 7 A2017G

Android 9

PixelExperience_Plus

Kernel Version: 3.18.124 lineageos

From this Thred:

https://xdaforums.com/axon-7/development/rom-pixel-experience-t3953999

Thanks for your work.

Gesendet von meinem ZTE A2017X mit Tapatalk
[Android Software Development] gyuuuu:
no successfull this is version

0.03 suceess but no dolby active on

i use pixel 3 stock
[Android Software Development] Arkmars20:
Appreciate all the work your doing with all these releases. My phone's a OP6T and been using Dolby Digital Plus by repey6. I've tried all current releases and Atmos won't install correctly on OOS
[Android Software Development] Adamk102:
will it update Viper Atmos? the application works great for some time then the Dolby Atmos effects work only when the application is active. just switch to other applications and they don't work anymore.

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] laugeek57:
Remove DolbyAtmos_0.89-ACDB and install DolbyAtmos-xperia5-A10-0.06-ACDB on N5X Pixel Eperience Q

Works fine :D Goob job GH :)
[Android Software Development] TheLusciousLucas:
DolbyAtmos-xperia5-A10-0.06-ACDB appears to be working OnePlus 6T OOS 10.3.1 Magisk v20.1(solohsu) EdXposed...

Hung for a minute or two while flashing in Magisk while checking for rom compatibility but then completed just fine.
[Android Software Development] lkp171:
On oneplus 6 it failed the combatibility check?

---------- Post added at 06:59 PM ---------- Previous post was at 06:40 PM ----------

Okay with 0.06 it starts but i can't enable it

---------- Post added at 07:00 PM ---------- Previous post was at 06:59 PM ----------

Same here on oneplus 6
[Android Software Development] laugeek57:
Tried with magisk v20.3 ??
[Android Software Development] TheLusciousLucas:
Haven't tried that as it, to my understanding, not working well with EdXposed. I'm using the modified solohsu version of Magisk https://github.com/solohsu/magisk_files/blob/master/README.md
[Android Software Development] guitardedhero:
Yes, the rom compatibility check can take some time. If Magisk Manager crashes during installation, the installation console usually disappears and doesn't freeze, at least in my experience so far.

Two Motorola Dolby systems - a G8 Plus Android Pie port and a One(?) Android 10 port.

This Android 10 port seems to only be compatible with Android 10, so this zip currently restricts an installation on Pie and lower.
[Android Software Development] suhas.holla:
Moto g8 plus pie build works fine in OnePlus 5T running OOS 9.0.10, but builds from Motorola vision and power stuck at boot with back screen and white led flashing
[Android Software Development] EstherTakumi:
I dont have any problem with EdXposed, im using official magisk. Only the early build of magisk that are problem.

---------- Post added at 06:47 AM ---------- Previous post was at 06:46 AM ----------

Try flash custom kernel, dolby atmos will work like magic
[Android Software Development] lkp171:
Tried it with bluspark and elemental x, but i can't turn atmos on
[Android Software Development] guitardedhero:
Is there any output from the following terminal command?

su -c /vendor/bin/hw/*dolby*
[Android Software Development] lkp171:
No i don't think so?
[Android Software Development] guitardedhero:
That's what compatibility looks like.
[Android Software Development] lkp171:
Ah okay, so the problem lies elsewhere i suppose
[Android Software Development] guitardedhero:
Yes, attach /sdcard/dumpsys.txt after running the following command:

su -c dumpsys media.audio_flinger > /sdcard/dumpsys.txt
[Android Software Development] Bogdans29:
There will be nice to attach proper

Commands and how to send logs what you need..
[Android Software Development] JakunTech1010:
So recently I switched to Havoc OS 3.1 for Samsung A70 . I've installed Motorola One Atmos port. I've done the same steps when I install every Atmos port from this Post: Install Dolby then Viper then restart then reflash Dolby. Dolby worked well without any issues but Viper just don't work. It keeps reporting Driver Not Found although I've installed it. I've successfully install both this Dolby and Viper on LOS 17. Can anyone tell me what's going on? Thanks.

UPDATE: Install Viper with AML and then Dolby Atmos seems to fix the problem. OK now I'm confused cuz I DON'T NEED AML TO MAKE THIS WORK IN LOS :confused:
[Android Software Development] nikothebarber:
Do you think you can check my log and let me know what keep to Install the atmos?
[Android Software Development] marquelito:
[MENTION=4445176]guitardedhero[/MENTION] now im on permissive kernel, could install viper legacy. Reboot, viper works. Installed dolby axon9 on top and reboot. Dolby didnt work, and breaked viper driver, then i installed aml and viper works again. But dolby dont work, and cant open app anyway got fc
[Android Software Development] EstherTakumi:
By bluspark, did you mean custom recovery? Or custom kernel?

Im using mauronofrio recovery with elemental x, and my op6 using OB4

What is your selinux status? Enforcing or Permissive?

Hope that help, I will attach screenshot of my current module here.
[Android Software Development] lkp171:
Both, the kernel and recovery, also op 6 and ob4. Yeah it should be permissive, but i will try it again with the magisk selinux module you have. Thanks for you answer
[Android Software Development] lkp171:
So my kernel is definitely permissive, i installed atmos again with both kernels but it still doesn't work. I don't think its because of the recovery because i managed to get the first axon a10 file in this thread to work but only once
[Android Software Development] panchogg:
Why i must install V4A For use dolby Atmos?
[Android Software Development] Adamk102:
what is your rom? I installed dolby audio, reset, then Viper legacy, reset, then aml, reset and everything works. My ROM is Miui 11 android 9

Wysłane z mojego moto g(8) plus przy użyciu Tapatalka
[Android Software Development] panchogg:
Lineage 14.1, Dolby Atmos Nougat, but i will have a redmi Note 8 soon, and i don't know why users speak V4A about.

Why install many audio mods?

Need current Dolby Atmos install V4A?
[Android Software Development] Bogdans29:
ACDBv15 errror with installed moto ACDB 32BIT 001V.
[Android Software Development] Adamk102:
dolby and viper4android gives a LOT of better sound than standard audio. When you check it yourself, you will thank the developer for his mod

Wysłane z mojego moto g(8) plus przy użyciu Tapatalka
[Android Software Development] guitardedhero:
The only time this is true is when installing ViPER|Atmos, and that is only because avoiding a v4a installation with a ViPER|Atmos zip would require changes to the installation script.

ViPER|Atmos is just a package deal offering something in a single installation that some users want that would otherwise require two separate installations to achieve the same thing.
[Android Software Development] guitardedhero:
I updated the troubleshooting guide post and I encourage everyone to check it out.

Troubleshooting Guide
[Android Software Development] Bogdans29:
I get nothing with this command

Su -c vendor/bin/hw/*dolby*
[Android Software Development] Bogdans29:
Flinger command
[Android Software Development] Bogdans29:
Ami didn't get ACDB install right .. about that you have above ☝️
[Android Software Development] nikothebarber:
[MENTION=4445176]guitardedhero[/MENTION] please check my log a page or two back
[Android Software Development] Bogdans29:
Logs whan i try to launch app

https://en.files.fm/u/4ysjj38m
[Android Software Development] Bogdans29:
Here this from telegram using motog6 32bit v001
[Android Software Development] panchogg:
Thanks Dev...

Are you planning make a MMT-Extended (susscesor of Unity Installer) ?
[Android Software Development] guitardedhero:
That is just a customized Magisk template, right?
[Android Software Development] panchogg:
Yes, but u dont know if it's nesscesary a version with this template..
[Android Software Development] Skittles9823:
MMT has no advantages for the end user over the regular template.

Guitardedhero has been doing fine with the normal template and his own helper functions, I doubt he'll switch to MMT. However, I'm sure he'll have a look at it.
[Android Software Development] EstherTakumi:
Sorry that I can't help much, it just weird that we both have the same phone, yet it not working for you.

Im using selinux module to change back selinux status to enforcing, because I'm using Dolby Plus by Repey before this, that one need permissive status.
[Android Software Development] lkp171:
Yes strange, well i'll try through the troubleshooting thread maybe it helps, thanks for your concern:good:

---------- Post added at 05:37 PM ---------- Previous post was at 05:03 PM ----------

So according to the guide it should add the code to the manifest.xml but it doesn't in my case, copying it in didn't work. Any idea where i went wrong?

---------- Post added at 06:23 PM ---------- Previous post was at 05:37 PM ----------

DolbyAtmos-axon9-A10-0.64-1.zip works again now, i don't know whats going on?
[Android Software Development] guitardedhero:
Changed the entire mounting function, system and vendor variables, and removed the limitation of Magisk Manager-only installations.
[Android Software Development] CallMeAldy:
For some reason this causes the brightness function on OnePlus 6T to freeze. Auto brightness no longer works and even manual reduction and increase of brightness no longer functions
[Android Software Development] guitardedhero:
Which zip?
[Android Software Development] guitardedhero:
Would you provide me all variations of audio_effects.xml and audio_effects.conf that exist in /vendor/etc/?

You may have configuration being sourced that has a unique name, thus not being targeted by the Dolby zip.
[Android Software Development] lcsd:
Logs attached (recovery & dumpsys). SafetyNet error in Magisk!?

Reinst ver0202, app ok, no FC.
[Android Software Development] guitardedhero:
Friendly head's up

:

Installations using Unity integrated installation zip's require two flashes if any current installation already exists, as the first installation attempt accomplishes merely an uninstallation and nothing more. :good:
[Android Software Development] laugeek57:
Not processing after installation :confused:

Thank's for fix :D
[Android Software Development] Kuljeet Singh:
[MENTION=4445176]guitardedhero[/MENTION] Can you please update your previous mod to work with magisk 15? As the zip works properly with system install but magisk installation gives trouble by not appearing in app drawer. Thanks for your work. I'm on OnePlus 3 Oxygen OS 8.0.0 Link to the mod:-

https://xdaforums.com/android/softw...y-research-t3379709/post74901736#post74901736
[Android Software Development] lcsd:
V0206-1: apk ok (=v0202) SafetyNet ok.
[Android Software Development] Trupen:
Understood first flash uninstalls Dolby and second flash installs

But same problem again FC
[Android Software Development] Trupen:
Same issue again nothing changed
[Android Software Development] Zackptg5:
It already had been updated for magisk 15
[Android Software Development] Kuljeet Singh:
Bro its the old dolby mod for oreo check the link, and the problem described occurs, can you fix it? It's not based on this mod.

[MENTION=6037748]Zackptg5[/MENTION] I have been using this mod of Dolby Atmos for oreo and doesn't have single problem just magisk install problem.. i have uploaded that zip here... I request you to please check it once.. that would be greatful

Here is the link https://drive.google.com/file/d/119ARAMM5aRYjqA8HglfgzwHPzUZhAo1N/view?usp=drivesdk
[Android Software Development] Dedojyoti:
I alray flash magisk can this flash cause boot loop??
[Android Software Development] Kuljeet Singh:
No it will not cause bootloop, just remove your currently installed dolby mod and flash this using system setting, it should work fine.
[Android Software Development] Dedojyoti:
System setting means??
[Android Software Development] Kuljeet Singh:
Means u install that in system and not magisk module, extract arise_parameters.prop from the zip and edit it to system.install=true and place it in the root of internal storage, and then flash.
[Android Software Development] ShadoV90:
HTC 10 oreo +magisk -> install 20180206-1 version -> frozen on white HTC word just half second before green circle and green HTC word and boot system. Tried restart three times before uninstall module.

How can i get more... useful informations like logcat from boot? I don't know how to do it.
[Android Software Development] guitardedhero:
Changelog

:

[B]20180206-2 -[/B]

- Redundant changelog is redundant.
[Android Software Development] Bordo_Bereli51:
Stuck at bootlogo when flashing with magisk manager.

Huawei Mate 10 Pro with 15.3 Magisk and permissive kernel
[Android Software Development] Trupen:
[MENTION=4445176]guitardedhero[/MENTION] Man you are trying very hard and continuously for us zip after zip after zip.

Really Appreciate you

Hope this latest version works for all
[Android Software Development] guitardedhero:
20180206-2 zip or earlier zip?

Lol, me too, man. Me too. :good:
[Android Software Development] Bordo_Bereli51:
Earlier zip but will try the new zip

P.S Still stuck at bootlogo with the new zip 2018.02.06-2 Flashed through Magisk Manager latest verssion, Magisk v15.3 Kernel permissive.
[Android Software Development] lcsd:
DAX ver 20180206-2, Apk FC. Logs attached.
[Android Software Development] onliner:
Yes, same here, but only with custom roms, with OOS works fine.

I tested with Viper Redux and the first port released here (I don't remember the device from that was ported).
[Android Software Development] JakunTech1010:
I installed DolbyAtmos Axon 9 port 0.918 then Viper then reboot then aml then DolbyAtmos again.

Dolby failed to run (I guess): Attempting to run it show nothing but if I do that too much the phone suddenly reboot.

My phone is Samsung A70 running Havoc OS 3.0

Here is dumpsys.txt, logcat when starting phone until I try to open DolbyAtmos. Execute of su -c /vendor/bin/hw/*dolby* show nothing.