Database Users

ViPER4ANDROID not working

I flashed the OTA (SOAK TEST (NOGAUT) and rooted my device and installed busybox, and after that I flushed viper4android, but the sarrow is its not working???? any body give remedy please........
Thanks in advance

Vendor>etc> . Rename audio.settings.conf to audio.settings.conf.bak.You'll get viper working

syedhmed said:
Vendor>etc> . Rename audio.settings.conf to audio.settings.conf.bak.You'll get viper working
Click to expand...
Click to collapse
The problem still exists....??
I changed as you said but it's becoming unsupported file....??

I figured it out.... It's selinux mode. Changed to permissive now it's working.....???

naveen135 said:
The problem still exists....
I changed as you said but it's becoming unsupported file....
Click to expand...
Click to collapse
1) Install BusyBOX and run Install there module
2) Install Selinux put in permissive mode,... tadaa it will work

[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

[GUIDE][OSPREY] Pass SafetyNet on Custom Roms

Hey guys,
After seeing this Magisk module https://github.com/DeicPro/xiaomi-safetynet-fix
I began to experiment to make SafetyNet pass on Osprey.
And finally I was able to do just that.
DO REMEMBER THAT THIS REQUIRES MAGISK WITH MAGISK HIDE ENABLED. THIS WILL NOT WORK WITH SUPERSU.
IF YOU ALREADY HAD SuperSU, CLEAN FLASH THE ROM AND THEN FLASH MAGISK ZIP.
Steps-
NOTE: SINCE GOOGLE HAS UPDATED SAFETYNET, THE BELOW METHOD NOW REQUIRES MAGISK v14.0+-
Open the build.prop file located in /system. [REQUIRES ROOT]
Add this line to the build.prop file-
For XT1550(Retail Asia | India (2GB))-
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
For XT1543(Retail Latin America (1GB)) -
ro.build.fingerprint=motorola/osprey_retla_ds/osprey_uds:6.0.1/MPI24.107-55-2/2:user/release-keys
For XT1540(Retail US (2GB)) -
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
For XT1540(Retail US (1GB))-
ro.build.fingerprint=motorola/osprey_retus/osprey_umts:6.0/MPI24.65-25.1/1:user/release-keys
Save and Exit.
Make sure you have enabled Magisk Hide in Magisk setings.
Reboot.
NEW! Magisk module is available here.
~Please read the Note section below~
---------------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE-
1. The fingerprint values need to be exactly the same. Any small change will trigger safetynet.
2. You can use any fingerprint value for your device. It's not necessary for you to take value specific to your device. As long as the fingerprint is valid, it will work.
3. This same trick should also work on Merlin devices.
4. Read this too please.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Thanks to -
@Rohi09 for providing stock ROM XT1550 build.prop
@Deic for his magisk module which inspired me to do this.
@KrisM22 for providing XT1540(2 GB) values.
@xMotoDA for providing XT1543 values.
@lettucecube for providing XT1540(1 GB) values and creating the Magisk module.

This method is working fine on purenexus rom

This is only for Asian Ospreys with 2GB of RAM, right?

Absolute killer! Thanks man.
Unfortunately, I still can't use digibank. Don't know what sort of check they perform.
xMotoDA said:
This is only for Asian Ospreys with 2GB of RAM, right?
Click to expand...
Click to collapse
Does that really matter?

Changing these specific values to the ones in the stock ROM makes SafetyNet pass! Since mine is dual sim and a different model I changed this in build.prop:
Code:
ro.product.name=osprey_retla_ds
ro.product.device=osprey_uds
ro.build.product=osprey_uds
ro.build.fingerprint=motorola/osprey_retla_ds/osprey_uds:6.0.1/MPI24.107-55-2/2:user/release-keys

bin.sayantan said:
Absolute killer! Thanks man.
Unfortunately, I still can't use digibank. Don't know what sort of check they perform.
Click to expand...
Click to collapse
Try to enable Magisk Hide for that specific app. Its there in the settings.

coolguy_16 said:
Try to enable Magisk Hide for that specific app. Its there in the settings.
Click to expand...
Click to collapse
Nothing happened. I even went a step further by totally uninstalling Magisk. Yet no luck.

bin.sayantan said:
Absolute killer! Thanks man.
Unfortunately, I still can't use digibank. Don't know what sort of check they perform.
Does that really matter?
Click to expand...
Click to collapse
I cant also log in my digi bank acount...i hav got a fixed deposit there....what is creating problem?any help
---------- Post added at 12:57 PM ---------- Previous post was at 12:35 PM ----------
Grt work....
I didnt found two lines in my build prop..so i add those...and safety net passed...
Thanx mate:good:

Can someone help me with this build.prop. Its from aex 4.2

Susan Dahal said:
Can someone help me with this build.prop. Its from aex 4.2
Click to expand...
Click to collapse
On AEX, you can simply add this line
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
anywhere in the build.prop.
Make sure the above value is exactly the same.

coolguy_16 said:
On AEX, you can simply add this line
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
anywhere in the build.prop.
Make sure the above value is exactly the same.
Click to expand...
Click to collapse
It worked Thanks

If you are willing could you look at mine - this is from a Moto G3 2015 XT1540 2GB US ATT
Thanks!
My stock is XT1540_OSPREY_RETUS_2GB_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml.zip
So I tried
ro.build.fingerprint=motorola/OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
also tried
ro.build.fingerprint=motorola/XT1540_OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.

KrisM22 said:
If you are willing could you look at mine - this is from a Moto G3 2015 XT1540 2GB US ATT
Thanks!
My stock is XT1540_OSPREY_RETUS_2GB_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml.zip
So I tried
ro.build.fingerprint=motorola/OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
also tried
ro.build.fingerprint=motorola/XT1540_OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
Click to expand...
Click to collapse
The problem here is that the value "ro.build.fingerprint" has to be the exact same as Motorola made it. Meaning even a small change(even CAPS) will trigger safetynet.
Anyways, I searched XDA for your device build.prop and found what you can replace that value with-
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
You can use the fingerprint value of my device too(the one mentioned in post). It will work without any issues.
I myself tried the fingerprint value of another model(that too a 1GB model) and it still worked.
Edit: I even tried the build.prop of your device on mine and that worked too.
Edit2: It seems like Step 2 in my OP is actually not necessary. Only fingerprint value is needed.

coolguy_16 said:
The problem here is that the value "ro.build.fingerprint" has to be the exact same as Motorola made it. Meaning even a small change(even CAPS) will trigger safetynet.
Anyways, I searched XDA for your device build.prop and found what you can replace that value with-
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
You can use the fingerprint value of my device too(the one mentioned in post). It will work without any issues.
I myself tried the fingerprint value of another model(that too a 1GB model) and it still worked.
Edit: I even tried the build.prop of your device on mine and that worked too.
Edit2: It seems like Step 2 in my OP is actually not necessary. Only fingerprint value is needed.
Click to expand...
Click to collapse
Huge thanks for your time. I realized I had not installed magisk so I installed that but I have supersu 2.79 installed so maybe need to uninstall that and install the special one for LinOS?

KrisM22 said:
Huge thanks for your time. I realized I had not installed magisk so I installed that but I have supersu 2.79 installed so maybe need to uninstall that and install the special one for LinOS?
Click to expand...
Click to collapse
I'm pretty sure it won't work with SuperSU.
Yep, remove SuperSu and also Magisk.
Then flash magisk zip again.This time it will install MagiskSU too(Magisk avoids MagiskSU if existing root solution is detected)

coolguy_16 said:
I'm pretty sure it won't work with SuperSU.
Yep, remove SuperSu and also Magisk.
Then flash magisk zip again.This time it will install MagiskSU too(Magisk avoids MagiskSU if existing root solution is detected)
Click to expand...
Click to collapse
It works! Huge thanks!
(This is LineageOS 5-11-17 )
When I removed SuperSU, I chose not to clean up the boot since I saw someone who supposedly bricked their phone doing that, so of course Magisk gave a nasty message about it when flashing,
so I wiped everything (dalvic/ART,Data,System,Cache) and rebuilt: flash rom, flash gapps, install, when get to desktop, install Magisk Mgr with play store and d/l zip(Magisk-v12.0.zip), and go back to TWRP and flash that zip (it does not say anything about su), but after boot I installed TBPro and discovered that yes, indeed I had root. Somewhere in there I set Magisk to "hide". So modified build.prop by only adding the one line you gave me up 2 posts (repeated below) and voila! And PokeGo works!
This is the line I added:
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
HINT: I used the JRummy Root Browser for a file manager to copy the line from a text file on my SDcard(from PC), to /system/build.prop and within that I use RB text editor. I say that because for some reason X-plore didn't work for me - edited fine, said saved, but didn't. Wasted time with that.
I do notice that HIDE is checked only for PokemonGo for me, so far, but I haven't tried any banking apps.
THANKS!!!.

Oops - next morning, no root access. Magisk status still shows good. Magisk/Superuser shows all 3 apps (BBS, JR RootBrowser, TBPro) and all switched ON.
EDIT: In Magisk/3 bars/Settings/Superuser - Superuser Access - Set it to "Apps and ADB". Root is back!

I believe @coolguy_16 has said this but I just went and tested and used the line from the 1st post:
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
and safetynet works just fine. So it would seem that as long as you have a valid fingerprint for some phone, it doesn't seem to matter what phone you put it on.
It is unknown whether google's "snet" would eventually alert the safetynet folks to this incongruity and then block it. EDIT - I would guess in the long run it would probably be better to use an "exact" fingerprint that would look correct.
EDIT There is a short FAQ in the first post that may help for solving Magisk problems:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Guys just an FYI.
Even though one can pass safetynet, some apps will still refuse to work.
You can try to enable Magisk hide for that specific app(see Magisk settings)
This happens because -
1. The app is sh*t
2. The app checks for other "dangerous props"
So anything which the app finds wrong in your build.prop will cause that.
Well, to find out what your app is checking exactly for.. You will have to decompile it and check for yourself. (Google is your friend)

:good: Great, tks m8.
I am now able to use my banking app (KBC Sign)
(however the app has to be checked in Magisk Hide, otherwise it wont work) :good:

Fix bluetooth audio & APTX in Treble-GSI

it's for Treble-GSI only
Tested in AospExtended V6.3 (B partition)
1. Bluetooth audio connection fix
Simply remove /vendor/overlay/BluetoothResCommon.apk via root explorer
2. AptX-HD
1) Install "Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler" from Download of Magisk Manager (APTX for Android Oreo & Pie NOT WORK)
2) Remove /vendor/overlay/RazerAuraBluetoothRes.apk (There's content of aptx and I don't know why it is in here)
!:?촒 resources.arsc5? ?com.android.bluetooth.overlay.razer.aura X 8$attrinteger?,"Gra2dp_source_codec_priority_aptx""a2dp_source_codec_priority_aptx_hd((a2dp_source_codec_priority_aptx_adaptive##a2dp_source_codec_priority_aptx_tws [email protected] 0   PK !:AndroidManifest.xml븪켷 A ?總?bp굛 ?C(??*
Click to expand...
Click to collapse
3) Open /vendor/build.prop and find "persist.vendor.bt.a2dp_offload_cap=sbc-aac" and replace "sbc-aac" to "sbc-aac-aptx-aptXHD" (Add -aptx-aptXHD)
4) Profit!
I've only tested in AOSPExtended GSI v6.3 so if you are in stock only try living in the edge

What was the original issue with BT in Pie?

ewgit said:
What was the original issue with BT in Pie?
Click to expand...
Click to collapse
Fail to connect to bluetooth audio in Treble-GSI Roms
It's due to Razer's overlay issue.
And Also APT-X Disabler exists in Razer's overlays

This definitely doesn't work on stock. Something keeps restoring RazerAuraBluetoothRes.apk (and BluetoothResCommon.apk reappears after the magisk mod is installed, if that matters).

Nomyth said:
This definitely doesn't work on stock. Something keeps restoring RazerAuraBluetoothRes.apk (and BluetoothResCommon.apk reappears after the magisk mod is installed, if that matters).
Click to expand...
Click to collapse
There are kernel protections in stock that disable modification of the vendor partition. Arter97's kernel has these disabled but I strongly recommend NOT modifying the vendor partition(it pisses off the bootloader). Learning how to make a custom Magisk module would be a better option here...

Nomyth said:
This definitely doesn't work on stock. Something keeps restoring RazerAuraBluetoothRes.apk (and BluetoothResCommon.apk reappears after the magisk mod is installed, if that matters).
Click to expand...
Click to collapse
I tried it in stock but don't work at stock (Enabled aptx but connect failed)

Does this actually work? I want the gsi ROMs

Craftingmod said:
I tried it in stock but don't work at stock (Enabled aptx but connect failed)
Click to expand...
Click to collapse
Hmm. If I remember right stock needs aptx libs to work. I tried that at one point and it actually connected, but only succeeded in making my ears bleed with a horrible static screeching when trying to play audio. Maybe both the libs and this thread are required...

This does not work in the ROM suggested too, the Bluetooth fails to work, doesn't even turn on, its something to do with BluetoothResCommon.apk

popeye2468 said:
This does not work in the ROM suggested too, the Bluetooth fails to work, doesn't even turn on, its something to do with BluetoothResCommon.apk
Click to expand...
Click to collapse
Once you delete the BluetoothRrsCommon then reflashing your rom and wiping cache should fix Bluetooth.

Managed to get music working but not in call Bluetooth audio

popeye2468 said:
Managed to get music working but not in call Bluetooth audio
Click to expand...
Click to collapse
In call audio is a known issue of the the base phh-treble rom as per this issue: https://github.com/phhusson/treble_experimentations/issues/374
That being said, if you are running a CAF based rom you may be able to get in call working with methods mentioned in the above issue thread.
Edit: fixed link to proper issue

Not AptX, but apparently LDAC just works on the stock ROM simply by adding it to the offload prop. It's supposedly just part of a standard Android build now, but needs a certification process for the OEM to be allowed to turn it on.

CurtisMJ said:
Not AptX, but apparently LDAC just works on the stock ROM simply by adding it to the offload prop. It's supposedly just part of a standard Android build now, but needs a certification process for the OEM to be allowed to turn it on.
Click to expand...
Click to collapse
Has anyone tried this method? I just got a bluetooth device which can use the advanced codecs so I want to get ldac working.

elyod said:
Has anyone tried this method? I just got a bluetooth device which can use the advanced codecs so I want to get ldac working.
Click to expand...
Click to collapse
I had tried before posting actually sorry, so I can confirm LDAC works fine. I remember there was more than one prop though. I'll try find the ones I changed...

CurtisMJ said:
I had tried before posting actually sorry, so I can confirm LDAC works fine. I remember there was more than one prop though. I'll try find the ones I changed...
Click to expand...
Click to collapse
Thanks I appreciate it. I spent quite a while trying to find other resources for it, best I could find was people porting ldac on Sony phones and I was hesitant to try it on the razer.

elyod said:
Thanks I appreciate it. I spent quite a while trying to find other resources for it, best I could find was people porting ldac on Sony phones and I was hesitant to try it on the razer.
Click to expand...
Click to collapse
Ok, so the following prop change is needed:
persist.vendor.bt.a2dp_offload_cap=sbc-aac-ldac
I can't seem to find the other one I changed, I suspect it didn't exist. I'll try to get back to my scripts tommorow to check. There are various ways to change props. I think there's a Magisk module to do custom ones (I just have my own boot scripts for this kind of stuff).
No porting needed as the LDAC libs are part of Android 9.

CurtisMJ said:
Ok, so the following prop change is needed:
persist.vendor.bt.a2dp_offload_cap=sbc-aac-ldac
I can't seem to find the other one I changed, I suspect it didn't exist. I'll try to get back to my scripts tommorow to check. There are various ways to change props. I think there's a Magisk module to do custom ones (I just have my own boot scripts for this kind of stuff).
No porting needed as the LDAC libs are part of Android 9.
Click to expand...
Click to collapse
Cool, I've modified the build.prop several times using a text editor so that's what I'm comfortable with. I'll give it a shot.

Okay, so I found a magisk module that enabled ldac.
Confirmed working using the companion app for my ES100 bt dac.

popeye2468 said:
Managed to get music working but not in call Bluetooth audio
Click to expand...
Click to collapse
by using this method?

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