Database Users

[ROM] ReACTV Rom for MotoACTV

This is a project I've been working on and off since I got my MotoACTV several months ago. A port of AOSP android for the MotoACTV.
What works:
- Wifi
- Audio
- Bluetooth (limited)
- Backlight level and leds.
- FM Radio.
- GPS.
- Accelerometer.
- all google apps
- most android functions. This is GingerBread 2.3.4.
What doesn't work (yet):
- Audio input
- native codecs, no video playing with stock players.
- HW acceleration
- some other things...
This is a work in progress yet, I just felt it reached a point where it's starting to be usable, so I'm releasing them as previews.
systemPreview13.img.zip 25/jan/2013
systemPreview18.img.zip 29/jan/2013 fixed battey icons, slightly improvement in video reproduction
That file is only the system image, it needs to be flashed with fastboot or ClearD's Image Flasher. The MotoACTV needs to be wiped. You need a boot image from the latest Motorola based roms, such as DPRom9.
No questions will be answered at this point. This is not finished, if you don't know how to install this, then wait for a more finished version. I already know most problems with this rom, please, no bug reporting, or improvement suggestion yet.
This is completely build from sources except for some non-open source binaries related to the hardware of the MotoACTV.
I am making the needed files to build this available to anyone who wants to give it a try and help. Atarii from the irc channel is already contributing.
https://github.com/dproldan
What can you do to help/contribute?
Post information that you feel could be usefull for other users. Apps that you have tried and found working, etc.
If you find a problem and know the solution, post about it.
During the development of this ROM, I bricked my dev MotoACTV. If you want to encourage development, use the donate button!
Enjoy!

Looking good, keep up the good work!
Sent from my GT-I9300 using Tapatalk 2

...Is this really happening??? ^_^
Will donate some cash come payday in a couple days. This is unreal.

So I'm excited. Thanks!

This looks amazing. I would guess no Motorola launcher and actv functions?
Either way I'm incredibly excited and will do my best to provide any productive feedback that I can.

donated 10 bucks to the motoactv fund

Me too $10 to dproldan, keep up the great work! It will be great if u could update your other ROM as well pls.

bluetooth audio
Did anyone try if audio-in (microphone) works with bluetooth headsets? It would be amazing if I could make calls with skype on this rom.
Update: I bought a mono bluetooth (non a2dp) headset and tried it with this rom and Atarii's boot.img with bluetooth profiles. Pairing was successful but neither microphone nor audio worked. I installed the BTmono app to make the headset accessible to apps other than the dialer (which works perfekt on my phone), but no sucess on the motoactv.

Can someone give some feedback on this rom especially if we can install run keeper? Thank
you
Sent from my GT-N7100 using Tapatalk 2

yreham said:
Can someone give some feedback on this rom especially if we can install run keeper? Thank
you
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I don't think dp is going to share any info on this one until he is further along. You could flash it and see how it goes. If you don't like it you could always go back to beta9 or whatever else you like.

No posts in a while, this project still active? Or dare I say... actv? ha ha ok bad joke.

Just busy with other things...
Sent from my GT-N7100 using xda app-developers app

This looks great, but is it possible to get Market on it? I downloaded the APK, but when I open Play Store it tells me I will now add a google account to the device, but when I click Yes, I get returned to home-screen..
EDIT: I see in the pictures you attached, you have Play Store, so I guess i must have done something wrong?

You have to install gapps from recovery mode.
http://goo.im/gapps/gapps-gb-20110828-signed.zip
Sent from my GT-N7100 using xda app-developers app

Thanks dproldan.
Another question, how do I set a keyboard as default, everytime I reboot my watch, I have to reactivate Flit Keyboard..

tips with this rom
1) install superuser via cwm from http://androidsu.com/superuser/ , not necessary, but important for most of my uses
2) install google apps via cwm, I had trouble with the recommended 20110828, so i went with gapps-gb-20110613-signed.zip which worked first time
3) drop the lcd density so more fits on screen. I like 90, but 100 is probably more practical
4) install mx player and the recommended armv7 codecs from play store, even without hardware accel working, there's just enough oomf in there for software decoding of most sd formats
more to come

Does anyone have BT tethering working on this ROM? Is it supported by the stack? If not, is there anything I can do to try and get it working?

Further to the above question: does anyone have bluetooth anything working with this rom? When I flashed it, it seemed like the names of bluetooth devices were bugged (as in - I couldn't see any, and when I paired with something by it's code instead, any app that wanted the name just crashed).
I just want to make sure it's the rom and not something I did.
When you say bluetooth tethering, do you mean something using the watch's wifi connection? Or do you mean the watch using your phone/pc net connection?

Saeviomage said:
Further to the above question: does anyone have bluetooth anything working with this rom? When I flashed it, it seemed like the names of bluetooth devices were bugged (as in - I couldn't see any, and when I paired with something by it's code instead, any app that wanted the name just crashed).
I just want to make sure it's the rom and not something I did.
When you say bluetooth tethering, do you mean something using the watch's wifi connection? Or do you mean the watch using your phone/pc net connection?
Click to expand...
Click to collapse
the first time i installed reactv, my bluetooth could scan for devices and would even pair with a bluetooth headset, but would not play any sound. a few days later after i'd accidentally wiped my data in cwm instead of running a backup and restored most of my settings with titanium i noticed sound was playing through my headset.
bluetooth tethering i can't test as my other android device lost this function in the latest official update and i haven't gotten around to working around that yet
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
Has anyone else been able to rebuild reactv from source? i've tried following the directions and can get a compiled disk image, but it always hangs on boot before the adb service kicks in.
-fg

fg said:
the first time i installed reactv, my bluetooth could scan for devices and would even pair with a bluetooth headset, but would not play any sound. a few days later after i'd accidentally wiped my data in cwm instead of running a backup and restored most of my settings with titanium i noticed sound was playing through my headset.
bluetooth tethering i can't test as my other android device lost this function in the latest official update and i haven't gotten around to working around that yet
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
Has anyone else been able to rebuild reactv from source? i've tried following the directions and can get a compiled disk image, but it always hangs on boot before the adb service kicks in.
-fg
Click to expand...
Click to collapse
I've been trying, but the instructions are not as clear as they could be (especially the bits about fixing user tags in android.mk files?). It would be nice if someone who knows how to do it would put out a script.
I have a script that does what I THINK needs to be done (except for fixing the android.mk files - because I have no idea what to do there), but I'm not 100% sure, and when it gets to the point of running make, it cannot find a makefile
-----start script-----
#run from the root of your vanilla android workspace
#download the motorola files
mkdir extracted_temp
cd extracted_temp
for i in system-core.tgz system-wlan-ti.tgz README.txt system-bluetooth.tgz motorola-external-visualization.tgz motorola-external-wbxmlparser.tgz motorola-external-util-linux.tgz motorola-external-jcifs.tgz motorola-external-jid3lib.tgz motorola-external-lbl.tgz motorola-external-bthelp.tgz motorola-external-hunspell.tgz kernel-omap3.tgz hardware-ti-omap3.tgz external-iproute2.tgz external-iptables.tgz external-elfcopy.tgz external-elfutils.tgz external-expat.tgz external-e2fsprogs.tgz external-dnsmasq.tgz external-dbus.tgz external-bluetooth-bluez.tgz external-bluetooth-glib.tgz external-bison.tgz external-alsa-lib.tgz bionic.tgz
do
if [ ! -f $i ]
then
echo $i
wget --trust-server-name "https://downloads.sourceforge.net/project/motoactv.motorola/MOTOACTV-Americas/1.7.11/$i"
fi
done
#extract them
for i in *.tgz
do
tar -xvf $i
done
#go through the extracted folders, and whenever there are files in a folder, delete the contents of that folder from the vanilla workspace
#so we overwrite the folder instead of merging. Note - this takes ages because it re-does the delete for each file in each folder
#but I can't be bothered to fix it
find -wholename "*/**" -exec rm .`dirname \{\}`/* \;
#copy the extracted folders to their destinations
for i in *
do
if [ -d $i ]
then
cp -r $i ..
fi
done
cd ..
#configure
lunch generic_G2-userdebug
#make
make
----end script-----

FM Radio for R1_HD

Thanks to the release of other roms for the R1_HD it was proven that the hardware does work as an FM radio.
The spec sheet did say it had the feature.
To anyone interested in adding the radio. Attached is a flashable recovery zip that will enable it for you.
ATTENTION:!!!! For the radio to function, the kernel needed to be made "permissive"
This was line in logcat that pointed me to permissive.
Code:
W android.fmradio: type=1400 audit(0.0:641230): avc: denied { read write } for name="fm" dev="tmpfs" ino=9679 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:fm_device:s0 tclass=chr_file permissive=0
So this update will re-flash your boot.img , And because the newest supersu has been systemless it modified your boot.img. This means after flashing this you will need to reinstall supersu.
This obviously only will work if you're rooted and have custom recovery.
Note,.1
the changed boot loader may cause the stock messenger app to force close. Other sms, and txt apps seem to be fine.
Note. 2
Just noticed amazon music and amazon video did not work after installing this. Reflashing the stock boot image allpws them to work again bit kill the radio.
Will update the zip if i find another way to allow permisive and have amazon apps still work
Boot.img seems to effect too much for my likeing. Found new (old) way to switch to permissive. .
New method for installing does not change boot.img
mode changer app is old and as of now it has hard coded root, looking for the binary in /system/xbin. This new fm_Radio_WITHOUT_boot.zip also has the fix for this root problem.
Need to install this SELinux Mode changer app
http://forum.xda-developers.com/showthread.php?t=2524485
http://forum.xda-developers.com/devdb/project/?id=1561#downloads

Awesome.
Works well from what I tried. Thanks for sharing!

Anybody know if this will KO safetynet? I already change to permissive and back, as well as tried just copying the system files, so that doesn't ko it. However, not sure what else is done.
Guess I could back up and try. If nobody knows I guess I will, but thought I would ask first.

This worked great, thank you. I'm running vampirefo's safe v6.6. Flashed your FM zip in TWRP, rebooted and it worked.

Just curious what method you chose for using permissive? I guess I've seen: kernel hack (vamp's kernel) echo script|command run w/ root, boot param. Also any ideas where the radio fails due to non-permissive mode.
How does the radio actually work btw, I know about the headphone jack requirement, but is there a specific app that uses that feature?
e/ Just a theory, I can test when I get home to build it
Code:
diff --git a/drivers/misc/mediatek/selinux_warning/selinux_warning.c b/drivers/misc/mediatek/selinux_warning/selinux_warning.c
index b8bbadb..3c70b40 100644
--- a/drivers/misc/mediatek/selinux_warning/selinux_warning.c
+++ b/drivers/misc/mediatek/selinux_warning/selinux_warning.c
@@ -52,7 +52,7 @@ const char *aee_filter_list[AEE_FILTER_NUM] = {
"u:r:ppp:s0",
/* "u:r:platform_app:s0", */
"u:r:racoon:s0",
-/* "u:r:radio:s0", */
+ "u:r:radio:s0",
"u:r:recovery:s0",
"u:r:rild:s0",
"u:r:runas:s0",

Thank you so much! Switching the FM radio to speaker is nice and loud. Wish it was this loud for my calls.
Installed fm_Radio.zip and UPDATE-SuperSU-v2.78-20160905010000.zip via TWRP on my 16/2GB on Stock Rom v12 and no issues with amazon video or stock messenger app. Will try on my 8/1GB this weekend.
EDIT
DARN! Tried to use my GPS (Waze) and screen won't rotate. Anyone one else having this issue after applying the FM radio?

mumbel said:
How does the radio actually work btw, I know about the headphone jack requirement, but is there a specific app that uses that feature?
Click to expand...
Click to collapse
If you are asking does it use a special radio app, yeah, it appears so. There is an app added to priv-app called FM-Radio in the zip. It might work with others, but I don't know. Only none specific radio app I know of (that works on many different radios) is SpiritFM, which doesn't work. Too bad, I like it.
As for SafetyNet, seems it passes it, at least for now. They are constantly making it harder to pass, so who knows what the future holds. Even just removing wirelessupdate now causes a soft fail/almost fail/whatever, blue in safetynet helper, had to restore /system from a backup.
Also, I had to switch to lopestom's recovery in order to install, as Vamp's sets the phones name as P6601, which isn't allowed by the zip.

Rotation fix
FerociousAndroid said:
Thank you so much! Switching the FM radio to speaker is nice and loud. Wish it was this loud for my calls.
Installed fm_Radio.zip and UPDATE-SuperSU-v2.78-20160905010000.zip via TWRP on my 16/2GB on Stock Rom v12 and no issues with amazon video or stock messenger app. Will try on my 8/1GB this weekend.
EDIT
DARN! Tried to use my GPS (Waze) and screen won't rotate. Anyone one else having this issue after applying the FM radio?
Click to expand...
Click to collapse
It can be fixed by http://forum.xda-developers.com/r1-hd/development/custom-rom-r1hd-zen-ui-t3473593/page5 #44

mumbel said:
Just curious what method you chose for using permissive? I guess I've seen: kernel hack (vamp's kernel) echo script|command run w/ root, boot param. Also any ideas where the radio fails due to non-permissive mode.
How does the radio actually work btw, I know about the headphone jack requirement, but is there a specific app that uses that feature?
e/ Just a theory, I can test when I get home to build it
Code:
diff --git a/drivers/misc/mediatek/selinux_warning/selinux_warning.c b/drivers/misc/mediatek/selinux_warning/selinux_warning.c
index b8bbadb..3c70b40 100644
--- a/drivers/misc/mediatek/selinux_warning/selinux_warning.c
+++ b/drivers/misc/mediatek/selinux_warning/selinux_warning.c
@@ -52,7 +52,7 @@ const char *aee_filter_list[AEE_FILTER_NUM] = {
"u:r:ppp:s0",
/* "u:r:platform_app:s0", */
"u:r:racoon:s0",
-/* "u:r:radio:s0", */
+ "u:r:radio:s0",
"u:r:recovery:s0",
"u:r:rild:s0",
"u:r:runas:s0",
Click to expand...
Click to collapse
I did not make the change to be permissive. I just used the boot.img from zenrom.
But now I have decided to suggest using the selinux mode changer app instead of changing the boot.img

theredbaron1834 said:
If you are asking does it use a special radio app, yeah, it appears so. There is an app added to priv-app called FM-Radio in the zip. It might work with others, but I don't know. Only none specific radio app I know of (that works on many different radios) is SpiritFM, which doesn't work. Too bad, I like it.
As for SafetyNet, seems it passes it, at least for now. They are constantly making it harder to pass, so who knows what the future holds. Even just removing wirelessupdate now causes a soft fail/almost fail/whatever, blue in safetynet helper, had to restore /system from a backup.
Also, I had to switch to lopestom's recovery in order to install, as Vamp's sets the phones name as P6601, which isn't allowed by the zip.
Click to expand...
Click to collapse
i can add that assert. But it is not the recovery that sets it it is the build prop on phone.

FerociousAndroid said:
Thank you so much! Switching the FM radio to speaker is nice and loud. Wish it was this loud for my calls.
Installed fm_Radio.zip and UPDATE-SuperSU-v2.78-20160905010000.zip via TWRP on my 16/2GB on Stock Rom v12 and no issues with amazon video or stock messenger app. Will try on my 8/1GB this weekend.
EDIT
DARN! Tried to use my GPS (Waze) and screen won't rotate. Anyone one else having this issue after applying the FM radio?
Click to expand...
Click to collapse
Please restore to your previous boot.img, reflash supersu and use the mode changer app to make it permissive. Will need to run the new install zip so that root will work with mode changer.

mrmazak said:
i can add that assert. But it is not the recovery that sets it it is the build prop on phone.
Click to expand...
Click to collapse
Yeah, not sure what's up with it. Just know that vampire's twrp had the name p6601 and the other one worked.

Why do we have to have root if we have TWRP? Or do we not really need it?

voluptuary said:
Why do we have to have root if we have TWRP? Or do we not really need it?
Click to expand...
Click to collapse
because the selinux mode changer app needs root. and for radio to work it needs selinux set to permissive.

Rotation Fix!
Wow, that worked on stock v12 (8GB/1GB and 16GB/2GB models)!!!! Thank you so much!!!
bjbjs said:
It can be fixed by http://forum.xda-developers.com/r1-hd/development/custom-rom-r1hd-zen-ui-t3473593/page5 #44
Click to expand...
Click to collapse
LOL... Was linked to an old post of mine that I never followed up.

mrmazak said:
because the selinux mode changer app needs root. and for radio to work it needs selinux set to permissive.
Click to expand...
Click to collapse
For what it's worth I pulled SelinuxModeChanger from FDroid and it requested root at /su/xbin just fine. No need for the files in your zip (I removed xbin from yours) I'm using v12 stock on an Amazon Blu R1 HD.

parkerlreed said:
For what it's worth I pulled SelinuxModeChanger from FDroid and it requested root at /su/xbin just fine. No need for the files in your zip (I removed xbin from yours) I'm using v12 stock on an Amazon Blu R1 HD.
Click to expand...
Click to collapse
Thanks. Good to know. I was just trying to stay with the version from tje developers thread.

Just installed SELinux Mode changer app downloaded from f-droid.org and flashed the fm radio zip file wow working like a charm!
Great job, dude!

I assume this uses the standard method of using the earphones as an antenna? Or will the radio work without earphones plugged in?

ase1590 said:
I assume this uses the standard method of using the earphones as an antenna? Or will the radio work without earphones plugged in?
Click to expand...
Click to collapse
Yep the standard headphone antenna

[ROOT][GUIDE] Install Viper for Android on Galaxy S8/S8+

This is tested on NEMESIS NOUGAT S8 1.0 but it also should work on STOCK ROMs.
You will need:
- Root
- Magisk
- V4A 2.5.0.5 APK (attached below)
- audio_effects.conf file (attached below)
- Root Explorer or some file browser app
- Titanium Backup (not necessary)
With Titanium Backup you must freeze SoundAlive app, if you don't have Titanium Backup, then you will have to delete the app. -> go to /system/priv-app/SoundAlive_51/ and delete the .apk file.
Copy audio_effects.conf to /system/vendor/etc and overwrite if prompted.
Install V4A .apk (don't open app yet) then go to Magisk -> Downloads and search for Viper4Android, download and install module, reboot.
If all went correctly, you should have Viper for Android installed on your S8/S8+
If you've got any question just leave a comment here, I won't answer PMs!

I'm still confused by this, isn't the DAC in the S8+ actually rated as being really good? So all you'd be doing with Viper is putting it through digital filters which merely alter the sound and don't add any quality...?

You could save yourself some trouble and just flash the arise audio zip

Hogyoku said:
You could save yourself some trouble and just flash the arise audio zip
Click to expand...
Click to collapse
Can you please tell me where can I get Arise Audio for Galaxy S8/S8 Plus?

dreams.sri said:
Can you please tell me where can I get Arise Audio for Galaxy S8/S8 Plus?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=457095661767141554
Im using this one

angelky said:
https://www.androidfilehost.com/?fid=457095661767141554
Im using this one
Click to expand...
Click to collapse
Wow, thanks for the link! One more question, I can simply flash it through the recovery right? Any special steps that I should know of?

dreams.sri said:
Wow, thanks for the link! One more question, I can simply flash it through the recovery right? Any special steps that I should know of?
Click to expand...
Click to collapse
Just flash and follow the instructions no special steps needed

Hogyoku said:
Just flash and follow the instructions no special steps needed
Click to expand...
Click to collapse
It's using AROMA installer, so it's pretty easy

tmorterlaing said:
I'm still confused by this, isn't the DAC in the S8+ actually rated as being really good? So all you'd be doing with Viper is putting it through digital filters which merely alter the sound and don't add any quality...?
Click to expand...
Click to collapse
Viper is easily the best EQ system out there. I wouldn't have a phone without it, the difference is vast.

Batfink33 said:
Viper is easily the best EQ system out there. I wouldn't have a phone without it, the difference is vast.
Click to expand...
Click to collapse
yes, yes it is.
I like how Viper is now integrated (baked) into my settings as well, that's pretty cool!
anyways... have you guys tried tasker with Viper yet?
So i have Viper set up so that when it connects to a particular bluetooth device it auto-loads my pre-configured audio Profile for that device... I have a diffent Profile for the car, home stereo and different headphones i use. It also upon connection auto adjusts media volume to max volume for bluetooth. Additionally, its also programmed to auto close my media apps and turn off bluetooth once the connected bluetooth device is powered off (useful for getting out of the car) I've also got it programmed to auto start Pandora, load my Viper Profile for when I get into the car.
(lmfao about people who say root and unlock bl is redundant, they really have no idea!)

cantenna said:
yes, yes it is.
I like how Viper is now integrated (baked) into my settings now, that's pretty cool!
Anyone know how to disable loud volume warning? I rember seeing it somewhere but can't find it..
Click to expand...
Click to collapse
Settings, sounds and vibration, volume, 3 dots right top. Turn on and set to full limit.

sicerik said:
Settings, sounds and vibration, volume, 3 dots right top. Turn on and set to full limit.
Click to expand...
Click to collapse
okay, so it seems I dont need to do this, seems the mod im using bakes Viper into settings and overides this.

Wait, there is already a root? Even with a locked bootloader?

sicerik said:
Settings, sounds and vibration, volume, 3 dots right top. Turn on and set to full limit.
Click to expand...
Click to collapse
okay, so it seems I dont need to do this? Anywhere else?

How's volume boost (+6db) of V4A on S8? Is it close to HTC 10 now?

Feche said:
If you've got any question just leave a comment here, I won't answer PMs!
Click to expand...
Click to collapse
I still can't get this to work on stock ROM. Viper status still says processing = no. I've renamed soundalive, installed viper and the magisk module and copied over the .conf file but something keeps overwriting it (I assume the magisk module) to a version that's not the same as the one in your zip file. Any ideas?

degsyh said:
I still can't get this to work on stock ROM. Viper status still says processing = no. I've renamed soundalive, installed viper and the magisk module and copied over the .conf file but something keeps overwriting it (I assume the magisk module) to a version that's not the same as the one in your zip file. Any ideas?
Click to expand...
Click to collapse
Your audio_effects.conf file gets replaced after reboot?

Feche said:
Your audio_effects.conf file gets replaced after reboot?
Click to expand...
Click to collapse
Yes. I've just checked the magisk log and it says "replace vendor/etc/audio_effects.conf". The first line starts
libraries {
v4a_fx {
path /system/lib/soundfx/libv4a_fx_ics.so
}
and then it continues with the rest of the soundalive references.

How are you people rooting this phone?

degsyh said:
Yes. I've just checked the magisk log and it says "replace vendor/etc/audio_effects.conf". The first line starts
libraries {
v4a_fx {
path /system/lib/soundfx/libv4a_fx_ics.so
}
and then it continues with the rest of the soundalive references.
Click to expand...
Click to collapse
Mhh not sure

Porting Dolby 2.5 from Leaked Android 8 beta?

So for a while I've been trying to port Dolby Atmos 2.5 but to no avail. I tried using the Dolby Atmos Axon 7 magisk module as a reference to which libs and other files it may depend on, but it seems that there are different files, removed, possibly changed and added.
I've listed below the lib/dependency files and folders in the magisk module and the known Dolby atmos files from the system.raw image of the leaked build
These are the ones in the magisk module zip
/system/etc/media_codecs_dolby.xml
/system/etc/dolby/dax-default.xml
/system/lib/soundfx/libhwdax.so
/system/lib/soundfx/libswdax.so
/system/lib/libdlbdapstorage.so
/system/lib/libdlbmemoryservice.so
/system/lib/libhwdaphal.so
/system/lib/libstagefright_soft_ddpdec.so
/system/lib64/libhwdaphal.so
And now these are the ones that I have found in the system.raw image of the leaked Oreo ROM. I assumed the ones named "libdlb*" are ones used by Dolby so I included those, along with lib files that are similar to the old ones just incase.
/system/etc/dolby/dax-default.xml
/system/lib/soundfx/libswdap.so
/system/lib/soundfx/libswvlldp.so
/system/lib/libdlbdapstorage.so
/system/lib/libdlbdsservice.so
/system/lib/libdlbmemoryservice.so
/system/lib/libdlbnativeservice.so
The ones in red are the new libs that could be related to dolby that I've found. And as you can see, some of them are gone or changed such as /system/etc/media_codecs_dolby.xml and the lib files in /system/lib/soundfx/
Upon flashing these new files, the dolby app crashes. Logcat says this: https://i.imgur.com/ClcqbVr.png
I'm not developer guys but I am good at piecing things together. If there was a simpler way this could be done we could figure it out easily. Maybe some libs were added, removed, or modified for the Magisk Module to be compatible with ahrion's AML. I have uploaded a flashable zip that I created using Nikhil's Android Flashable Zip Creator which you can download right here. Make a backup, of course,
before flashing this. This is all being tested on the Project New World Oreo ROM by OrdenKrieger

I'm running the latest 8.1.0 Project World ROM and I'm reporting back with some force closing if the Dolby Atmos application. I can't seem to launch the app at all due to this. Thanks for trying to make this work, I appreciate it. ?

troy5890 said:
I'm running the latest 8.1.0 Project World ROM and I'm reporting back with some force closing if the Dolby Atmos application. I can't seem to launch the app at all due to this. Thanks for trying to make this work, I appreciate it.
Click to expand...
Click to collapse
Well if you noticed, the app does hang a little bit before crashing as it tries to load everything. But it seems when it can't load the audio effects it crashes. I don't know if it's related to audio_effects.conf or something

Teet1 said:
Well if you noticed, the app does hang a little bit before crashing as it tries to load everything. But it seems when it can't load the audio effects it crashes. I don't know if it's related to audio_effects.conf or something
Click to expand...
Click to collapse
I've noticed it do that when I try to launch it. My guess is that it has something to do with the audio_effects.conf

I uploaded the /system/ folder of the leaked ROM as a zip if anyone feels bold enough to try. Download here

Teet1 said:
I uploaded the /system/ folder of the leaked ROM as a zip if anyone feels bold enough to try. Download here
Click to expand...
Click to collapse
Why don't we ask the magisk module guys.
@ahrion and @Zackptg5 Is there a port of the Oreo Atmos version under way? Teet1 couldn't make it work by just taking the libs it seems

Choose an username... said:
Why don't we ask the magisk module guys.
@ahrion and @Zackptg5 Is there a port of the Oreo Atmos version under way? Teet1 couldn't make it work by just taking the libs it seems
Click to expand...
Click to collapse
I hope they are working on it....but I am certain the magisk module version was modified to work with their audio modification library. Perhaps I can try messing with that, but I probably can't share it if its their code
EDIT: so...after looking through the system image, I have found most of those missing files inside the /system/vendor/ folder...and just occured to me that a lot of the magisk patching occurs in the /system/vendor/ folder. Looking into it....
edit again: oh yes, I think I hav efigured out the problem. Now to test... https://i.imgur.com/ZfcGGka.png

Okay, so I'm making some progress. After copying from libs and other files from /system/vender/ it seems that the dolby service starts to work but still stops working. Ultimately, in the logs it ends in "dolby service not found". Also noticed a new error, the app crashes with an error saying "AudioEffect: set/get parameter error"
The app opens briefly, and hangs and then crashes. Attempting to play music pauses it for a while, then starts. Opening the dolby app while music plays pauses the music and then continues again. I copied a lot of audio files and "mixer pathes" files. If you take a look at my logcat, it seems as if I made the speakers work as they should as if it was in the stock rom! Maybe...they don't distort at high levels anymore and it's much clearer and louder. I can't get proper logs right now as I'm about to go to sleep and on my phone so i'll upload quick screenshots
I may still be missing some files, but who knows.
I am getting close. I've uploaded a link to the new zip here
Be warned, make a backup before flashing this. It's to test only, it doesn't work.
Here are some quick screenshots:
https://imgur.com/a/YQyKM

Have you had any progress?

chrisrodsa210 said:
Have you had any progress?
Click to expand...
Click to collapse
Nope, stumped now. I moved a lib/lib64 file called libaudioeffect_jni.so and that caused the app to instantly crash with a new error, which unfortunately I can't remember. The behavior was the same where the music took a couple seconds to start playing and then starts playing and opening the dolby app causes the music to pause for a bit. I took a look at that lib file and saw there were other audio libs it asks for so I moved those, which lead the phone into a bootloop. I assume that the service wants to work but can't call the audio effects for some reason. I'm not a developer, so I don't know what else I can do

Hello,
Here is a OnePlus 5 port of our Oreo Dolby. Maybe you can find the necessary files there. The current version of that thread works with OP5 but sadly didn't work with the first Project New World build, maybe the newest build works with this? Looking forward to this
https://forum.xda-developers.com/oneplus-5/themes/app-dolby-atmos-axon-7-oreo-port-t3734040

mariusfl0rian said:
Hello,
Here is a OnePlus 5 port of our Oreo Dolby. Maybe you can find the necessary files there. The current version of that thread works with OP5 but sadly didn't work with the first Project New World build, maybe the newest build works with this? Looking forward to this
https://forum.xda-developers.com/oneplus-5/themes/app-dolby-atmos-axon-7-oreo-port-t3734040
Click to expand...
Click to collapse
I'll definitely test this with the latest Project World and report back
---------- Post added at 09:07 PM ---------- Previous post was at 08:44 PM ----------
troy5890 said:
I'll definitely test this with the latest Project World and report back
Click to expand...
Click to collapse
EDIT: Tested the zip out and it didn't install on twrp. It just kept going and didn't install. Had to do a Hard Reboot.

getting the same issue where it doesn't install. I could try to use the files it moves, but theres a lot of scripts of setting permissions, writing things, etc and i feel like thats so much more complicated than just moving files it needs. I'm more hopeful of that zip than with mine.

NO AUDIO INPUT AND OUTPUT

Hello!
My problem is my device doesnt have audio. i tried calling using my device and mute is disabled. I cant also voice record. No audio from playing videos (youtube, netflix, spotify, chrome, etc). I cant record videos too.
What is wrong with my device? Do we have audio patch for this? I have also custom rom my phone with DotOS v.5.0.1 thru TWRP.. tell me if im missing a system app..

dyoliya said:
Hello!
i’m very new with having custom ROM. And I flashed my device with DotOS v5.0.1 thru TWRP. (Also tried diffrent custom rom)
My problem is my device doesnt have audio. i tried calling using my device and mute is disabled. I cant also voice record. No audio from playing videos. I cant record videos too.
did i miss something? Im sorry im really new with this. I dont know if there is a patch that i should use...
Click to expand...
Click to collapse
Not familiar with your custom ROM but many people don't properly install custom ROMs
Did you FORMAT (not Wipe - it's completely different thing) Data partition (!) when you switched the ROM? If you didn't, you must do it
Assuming you had audio with the official MIUI (otherwise, you may have hardware issue)

zgfg said:
Not familiar with your custom ROM but many people don't properly install custom ROMs
Did you FORMAT (not Wipe - it's completely different thing) Data partition (!) when you switched the ROM? If you didn't, you must do it
Assuming you had audio with the official MIUI (otherwise, you may have hardware issue)
Click to expand...
Click to collapse
ive done that. after flashing a ROM, I format data..
My audio was working before I custom ROM too. idk if i should just go back to stock rom

UPDATE:
I've tried several custom ROMs now, also stock ROM. But no luck. How am I supposed to know if this is a hardware issue??
WHAT'S NOT WORKING:
- Built-in speakers
- Video recording
- Screen recording
- Voice recording
- Headphones/Earphones
- Bluetooth earphones/speakers
- No audio calls, no ringtones
- Unable to disable/enable mute button during call
- During call, speakers are enabled but cant be disabled (still no sound)
WHAT'S WORKING:
- Adjusting volume sliders
I'm not sure if this has something to do with hardware since I dont recall it falling, etc.. It suddenly stopped working at all.

There are codes that you dial and you can test all your hardware separately. It depends on rom, so you have to try

man we have the same issues. my device has no audio source since i switched on custom rom. i tried to back again on stock rom but it doesent work again. the technician recommend to replace the audio ic which is hardware issues. anyone can help us on this problem? my device is mi 9t

Try to wipe all, including recovery. Don't install newest rom, try older like android 10 and then if it doesn't work, you can try editing propsconfig

yaro666 said:
Try to wipe all, including recovery. Don't install newest rom, try older like android 10 and then if it doesn't work, you can try editing propsconfig
Click to expand...
Click to collapse
I’ve tried going back to android 10 but the Original problem of my phone goes back again. It lags big time!! So i dont have a choice but to switch to a custom ROM.
i havent tried editing propsconfig yet. How do you do that?

swaggyp01 said:
man we have the same issues. my device has no audio source since i switched on custom rom. i tried to back again on stock rom but it doesent work again. the technician recommend to replace the audio ic which is hardware issues. anyone can help us on this problem? my device is mi 9t
Click to expand...
Click to collapse
I have same problem but no one is trying to replace Audio ichha

Jeetp126 said:
I have same problem but no one is trying t
Click to expand...
Click to collapse
yaro666 said:
Try to wipe all, including recovery. Don't install newest rom, try older like android 10 and then if it doesn't work, you can try editing propsconfig
Click to expand...
Click to collapse
how can i edit the props config? hoping for help . big thanks. i want to try it so bad. but i dont know how to do that.

swaggyp01 said:
how can i edit the props config? hoping for help . big thanks. i want to try it so bad. but i dont know how to do that.
Click to expand...
Click to collapse
If you have Magisk, use Magisk Hide Props Config module to add/edit/remove any prop
Otherwise, from TWRP, Advanced, File Manager (for e.g. build.prop file) go to /system and copy the file build.prop to /sdcard.
Reboot to Android, edit your copy of build.prop saved to Internal memory.
Reboot again to TWRP, mount System as writable, copy build.prop to e.g. build.bak and copy your edited build.prop from /sdcard to /system
If anyting goes wrong, reboot to TWRP, remove your build prop and rename your build.bak back to build.prop
You can also copy build prop from TWRP to PC, edit it there and copy back
Google for details if you are unfamiliar with, this is just general idea
If using TWRP, make sure you make a backup file (like build.bak) to be able to resolve possible brick or something
If using Magisk and that MHCP module, changes will be systemless (google if not familiar with the term) and you can simply disable the module (and automatically all your changes on props) if anything goes wrong
Generally, it's not for beginners to play with props

zgfg said:
If you have Magisk, use Magisk Hide Props Config module to add/edit/remove any prop
Otherwise, from TWRP, Advanced, File Manager (for e.g. build.prop file) go to /system and copy the file build.prop to /sdcard.
Reboot to Android, edit your copy of build.prop saved to Internal memory.
Reboot again to TWRP, mount System as writable, copy build.prop to e.g. build.bak and copy your edited build.prop from /sdcard to /system
If anyting goes wrong, reboot to TWRP, remove your build prop and rename your build.bak back to build.prop
You can also copy build prop from TWRP to PC, edit it there and copy back
Google for details if you are unfamiliar with, this is just general idea
If using TWRP, make sure you make a backup file (like build.bak) to be able to resolve possible brick or something
If using Magisk and that MHCP module, changes will be systemless (google if not familiar with the term) and you can simply disable the module (and automatically all your changes on props) if anything goes wrong
Generally, it's not for beginners to play with props
Click to expand...
Click to collapse

Thanks for explaining everything brother. Now I will do a research about editing audio or sound on build prop. Hopefully this is not a hardware issues.

Same issue encountered with me also. I am in a great distress right now. Tried more than 30+ roms (including recover, fastboot, custom, and stock), but nothing helps.
IF you find anything please update here.. THat'll be a great help indeed!!

dyoliya said:
UPDATE:
I've tried several custom ROMs now, also stock ROM. But no luck. How am I supposed to know if this is a hardware issue??
WHAT'S NOT WORKING:
- Built-in speakers
- Video recording
- Screen recording
- Voice recording
- Headphones/Earphones
- Bluetooth earphones/speakers
- No audio calls, no ringtones
- Unable to disable/enable mute button during call
- During call, speakers are enabled but cant be disabled (still no sound)
WHAT'S WORKING:
- Adjusting volume sliders
I'm not sure if this has something to do with hardware since I dont recall it falling, etc.. It suddenly stopped working at all.
Click to expand...
Click to collapse
Exactly same thing happened with me, at that time I was on Miui global stable 12.0.9.0.. It happened all on a sudden. Now I am phoneless

swaggyp01 said:
man we have the same issues. my device has no audio source since i switched on custom rom. i tried to back again on stock rom but it doesent work again. the technician recommend to replace the audio ic which is hardware issues. anyone can help us on this problem? my device is mi 9t
Click to expand...
Click to collapse
Same exactly

If you r getting error while playing ringtone through settings then its your ui problem. You have to shift custom ui i recommend pixel UI or Oxygen os

Jeetp126 said:
If you r getting error while playing ringtone through settings then its your ui problem. You have to shift custom ui i recommend pixel UI or Oxygen os
Click to expand...
Click to collapse
Yes You are right

IMPORTANT UPDATE:
Hello everyone! it's a request to everyone who has/is facing this problem PLEASE GIVE A FEEDBACK via FEEDBACK APP.
I talked to one of the official MIUI representative & he further talked to the MOD & they said they haven't got any such feedback so please spam this problem!
here is the proof: AGB the official representative of MIUI
View attachment 5525269 View attachment 5525271View attachment 5525273View attachment 5525275

IMPORTANT UPDATE:
Hello everyone! it's a request to everyone who has/is facing this problem PLEASE GIVE A FEEDBACK via FEEDBACK APP.
I talked to one of the official MIUI representative & he further talked to the MOD & they said they haven't got any such feedback so please spam this problem!
here is the proof: AGB the official representative of MIUI
View attachment 5525269 View attachment 5525271View attachment 5525273View attachment 5525275