Database Users

Z3/Z3C Sony Stock camera on AOSP/CM

Not being stranger to ROM changing, after buying my Xperia Z3 Compact, I went straight for the bootloader unlock (following CM official wiki page). I did not backup my TA partition and therefore, my DRM keys are gone forever. Such is life. But I am not giving up...
I installed ResurrectionRemix (AOSP/CM based) and I am quite happy with it, but I thought it would be nice to have the original stock Sony camera functionality.
What I managed to do so far:
Mod the RR framework using this guide, which means:
- get /system/framework/framework.jar from your phone
- unpack classes.dex using your favorite archive tool
- decompile the classes.dex using Rom Tools (direct download link)
- overwrite the files with the ones from the linked guide
- compile it back to new classes.dex
- pack the modded classes.dex to the framework.jar
- copy the new framework.jar to /system
Install Sony Stock camera using this guide:
- flash the stock camera port
- flash panorama sweep fix
- flash face detection fix
Deactivate the standard CM camera apps
- including CameraWorkaround, Camera2, etc.
Clear data of all camera-related apps
- if you don't, the Sony Stock camera might crash, I checked logcat and found out it was because of SQLite DB version mismatch that the CM camera created and the Sony Stock camera couldn't use.
Then I found this thread:
[Z~Z5 Series][EXRxTHS]SONY DRM FUNCTION RESTORATION FOR UB DEVICE | Z3 lines support!
If what is claimed there really works, then the Sony proprietary image processing can be enabled even without the DRM keys. That basically means that the DRM keys are only used as verification, but the software performing the processing is indeed in the ROM.
The thread itself states that it is only for stock-based ROMs as AOSP/CM ROMs don't have the functionality in the first place. I might be wrong, but I believe that by modifying my framework I have imported some of these functionalities back into the phone.
If it was possible to port some parts, it should be possible to port more of them, including the image processing.
So I am starting this thread to track progress in this and to find the last piece of the puzzle - to bridge the gap between having Stock Camera framework and app on AOSP/CM ROM and the DRM patch, which probably patches the DRM-checking core to always return "keys are fine" even if they are missing,

I am interested in this as well, because I always prefer using AOSP than stock rom, be it on Sony device, Samsung, whatever. But lack of proper camera is keeping me away, mainly the reversed fish eye effect.
Have you experienced some crashes with that setup? I remember that people reported various crashes with that port.
I would help, but I have zero knowledge about coding and porting and everything associated with it unfortunately.

no crashes for me like this. but i have uninstalled most of the "fancy effects" apps in the bundle. so i got superauto, manual, livecast, some fx and stickers and thats about it

Hey, I'm also interessted in your work. How do you handle updates with this mod?

curlyboi said:
no crashes for me like this. but i have uninstalled most of the "fancy effects" apps in the bundle. so i got superauto, manual, livecast, some fx and stickers and thats about it
Click to expand...
Click to collapse
I don't need fancy stuff either, I would keep 4k video and Slow motion video out of all those and that's it. So I guess I could try some AOSP if it works on your side as you say
Some questions though. Do you think I can use zezadas' unlocked camera app with this port? It's just a matter of replacing apk only, nothing else.
And which version of RR do you use, based on CM13 or CM12.1?

It's RR based on 12.1.
And I don't plan on updating too often... Maybe once some very important fix comes out, but before that it's not necessary. I customize everything so every ROM reinstall is so much pain in the ass for me, hours going thru all the 200 apps and setting everything

[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

[ROM][AOSP][SM-T705] Android 7.1.2 NZH54D (2017-09-12)

AOSP - Android Nougat - 7.1.2 - NZH54D
​This is a pure build of AOSP Android 7.1 Nougat, the goal is to have a pure AOSP rom for Samsung T705, so it is not the objective of this project to include any functionality that is not native to Android AOSP.
Download:
ROM: Mega, AndroidFileHost
Modem(OJ1): Mega, AndroidFileHost
Gapps:
OpenGapps: http://opengapps.org/
Choose ARM platform
Root:
SuperSU: http://www.supersu.com/download
Credits:
Kernel is based on LineageOS's Exynos5420 kernel, device tree is based on @Schischu, @deadman96385 and his Exynos5420 team's marvelous works.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Code:
2017-09-12
　　- Latest AOSP (NZH54D) Android 7.1.2_r33
　　- Screen rotating glitches fixed
　　- New Bluetooth HAL, distortion fixed
　　- Rework RIL, more stable phone calling and receiving
　　- IR blaster fixed with new IR HAL
　　- This might well be the last Nougat release, I will work on Oreo from now on
2017-06-19
　　- Latest AOSP (NJH47B) Android 7.1.2_r17
　　- Some kernel tweaks
2017-06-14
　　- AOSP (N2G47O) Android 7.1.2_r8
　　- Kernel 3.4.113
　　- Baseband version OJ1 (see download link above for modem file)
　　- Fingerprint disabled, everything else work, [B]including mobile data[/B]
Flashing instructions:
Flash TWRP 3.0.2 or higher
Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check
Dalvik Cache
System
Cache
Data
and wipe them. Don't reboot just yet.
Go into install menu
Select and flash rom file aosp-XXX.zip
Select and flash SM-T705_OJ1_MODEM.zip if needed. You might need to change the file name to modem.zip
Wipe cache/dalvik cache and reboot to system. Due to some bugs, we can't flash opengapps alone with this rom
After the successful first boot, boot back into recovery and flash gapps and supersu.
Reboot to system
Contributors:
@scubajeff
Source Code: https://github.com/scubajeff/
ROM OS Version: 7.1.2 Nougat NZH54D
ROM Kernel: Linux 3.4.113
Based On: AOSP
Status: Stable
Created: 2017-06-14
Last Updated: 2017-09-12

Reserved.

UI Screenshot please
Waaaaww.. Another klimtlte AOSP.. Really amazing works.. Could you give us partial screnshoot please..
And do you have a plan to continue to maintain this build..?
Thankssss in advance :good::good:

maz izaackovich said:
Waaaaww.. Another klimtlte AOSP.. Really amazing works.. Could you give us partial screnshoot please..
And do you have a plan to continue to maintain this build..?
Thankssss in advance :good::good:
Click to expand...
Click to collapse
Of course I will maintain this build and I'm planing for a Android O update in the near future.

scubajeff said:
Of course I will maintain this build and I'm planing for a Android O update in the near future.
Click to expand...
Click to collapse
Nice..!! Android O . Glad to see another dev like you maintain this AOSP, since schisu and maloshasa has stopped their project, in AOSP based on MM os. Downloading now, I'll report back if there's some bug..
Currently using latest RR Nougat
Thankssss sir..
___________________________________________________________________
hy sir.. come again to report some issues
1. there's glitches in every opening apps or recent apps, ie. : i opened browser and then i opened COC or others, so i found there was glitches between switching that apps, and nearly happened in every swtching or opening apps ( i guess this aint my screen problem, never have been happened before)
2. ext sdcard issue: when i copied file from internal sdcard to external sdcard, i couldnt access my copied file immediately via my laptop, it must be unmounted fisrt (ext sdcard) then mounted back to make it accessible.
3. in owner user setting: i got my picture placing upside down than it supposed to be.
over all it works smooth and light. i hope i dont bother you with my issues report
thaannnnkkss..

Sorry, I'm english short.
When I'm calling with bluetooth, voice distorted. Please fix this problem. Thank you.

Ssanmai man said:
Sorry, I'm english short.
When I'm calling with bluetooth, voice distorted. Please fix this problem. Thank you.
Click to expand...
Click to collapse
Distortion happen on your side or the other side can't hear your voice clear enough?
Sent from my Samsung SM-T705 using XDA Labs

maz izaackovich said:
Nice..!! Android O . Glad to see another dev like you maintain this AOSP, since schisu and maloshasa has stopped their project, in AOSP based on MM os. Downloading now, I'll report back if there's some bug..
Currently using latest RR Nougat
Thankssss sir..
___________________________________________________________________
hy sir.. come again to report some issues
1. there's glitches in every opening apps or recent apps, ie. : i opened browser and then i opened COC or others, so i found there was glitches between switching that apps, and nearly happened in every swtching or opening apps ( i guess this aint my screen problem, never have been happened before)
2. ext sdcard issue: when i copied file from internal sdcard to external sdcard, i couldnt access my copied file immediately via my laptop, it must be unmounted fisrt (ext sdcard) then mounted back to make it accessible.
3. in owner user setting: i got my picture placing upside down than it supposed to be.
over all it works smooth and light. i hope i dont bother you with my issues report
thaannnnkkss..
Click to expand...
Click to collapse
1. I have glitches when rotating the screen, but never see them when switching apps, even when using double tapping of recent app button to fast switch between 2 most recent apps.
2. I will look into this one, however could you kindly be more elaborate that during all those steps, was your t705 mounted to you laptop thru. MTP ?
3. I could not reproduct this one neither, my avatar in owner profile now is clearly showing that the nose is below the eyes.
Thx for reporting. Keep them coming.
Sent from my Samsung SM-T705 using XDA Labs

scubajeff said:
1. I have glitches when rotating the screen, but never see them when switching apps, even when using double tapping of recent app button to fast switch between 2 most recent apps.
2. I will look into this one, however could you kindly be more elaborate that during all those steps, was your t705 mounted to you laptop thru. MTP ?
3. I could not reproduct this one neither, my avatar in owner profile now is clearly showing that the nose is below the eyes.
Thx for reporting. Keep them coming.
Sent from my Samsung SM-T705 using XDA Labs
Click to expand...
Click to collapse
1 yes.. . Glitches in opening apps, and rotating it.
2. Yah, thru MTP. I can't see my file, but ext sdcard is accesible thru my laptop, but not a copied file. When i look for it into "file explorer" in my tablet, it's there. So I have to unmount-remount my ext sdcard, and even worst i have to restart my tablet then i plug in back thru my laptop to get "my copied file" accessible..
Thaannkksss...

maz izaackovich said:
1 yes.. . Glitches in opening apps, and rotating it.
2. Yah, thru MTP. I can't see my file, but ext sdcard is accesible thru my laptop, but not a copied file. When i look for it into "file explorer" in my tablet, it's there. So I have to unmount-remount my ext sdcard, and even worst i have to restart my tablet then i plug in back thru my laptop to get "my copied file" accessible..
Thaannkksss...
Click to expand...
Click to collapse
Do you mean that the list of file is not refreshed on the laptop side?
Sent from my Samsung SM-T705 using XDA Labs

scubajeff said:
Do you mean that the list of file is not refreshed on the laptop side?
Sent from my Samsung SM-T705 using XDA Labs
Click to expand...
Click to collapse
Yeessss.. Thats right.. Sorry for my bad english

maz izaackovich said:
2. ext sdcard issue: when i copied file from internal sdcard to external sdcard, i couldnt access my copied file immediately via my laptop, it must be unmounted fisrt (ext sdcard) then mounted back to make it accessible.
Click to expand...
Click to collapse
I can reproduct this one, seems to me it's an long overdue bug of Google's implementation of MTP, related to media rescan. It happened under many circumstances, see this bug report --> https://issuetracker.google.com/issues/37071807
Sadly, Google refuse to acknowledge it as a bug.

Hi Scubajeff
I am experiencing an issue with com.android.phone and android.process.acore keeps failing to respond and its having a detremental effect on the battery life.
Any ideas how to fix this ?

ypmud said:
Hi Scubajeff
I am experiencing an issue with com.android.phone and android.process.acore keeps failing to respond and its having a detremental effect on the battery life.
Any ideas how to fix this ?
Click to expand...
Click to collapse
I ever had that issue, when i unisntalled google stock contact "Contacts.apk and ContactsProvider.apk" to replace with "zenui dialer and contact"
I guessed your issue it's related with, that your stock contact isnt installed properly
Try to flash these two .apks (Contacts.apk and ContactsProvider.apk) taken from your rom thru trwp or cwm recovery . It's solved my problem.

is there a way i can disable both phone and contacts ?
I am not on a rooted device
---------- Post added at 07:20 PM ---------- Previous post was at 06:49 PM ----------
Its ok I have figured it out that I needed to wipe the device due to it using my previous apk's

ypmud said:
---------- Post added at 07:20 PM ---------- Previous post was at 06:49 PM ----------
Its ok I have figured it out that I needed to wipe the device due to it using my previous apk's
Click to expand...
Click to collapse
Yes, if you are coming from other ROM, it's really, truly, absolutely important to WIPE ALL before flashing.

scubajeff said:
Distortion happen on your side or the other side can't hear your voice clear enough?
Click to expand...
Click to collapse
First, I confirm that my side distorted.

So far not bad. Both my 3G and LTE data are working fine, not sure about calls yet as I haven't tried. I do get those weird artifacts when I rotate the screen, but I've seen that on most of the Nougat 7.1 based ROMs. Nice work with the Kernel. It seems to be VERY customisable in Deathly Adiutor which is great for me. As with all Nougat based ROMs, the audio input latency is the best it's ever been. I would like the ability to enable software keys and to be able to bypass the hardware keys because as you most certainly know they have a strong tendency to interfere with this device (I keep catching them with my hand). Also, the IR blaster doesn't work AT ALL. I would like that to be fixed as Peel Smart Remote is an everyday app for me and I can't use it with this ROM.

simonjonnemeth said:
So far not bad. Both my 3G and LTE data are working fine, not sure about calls yet as I haven't tried. I do get those weird artifacts when I rotate the screen, but I've seen that on most of the Nougat 7.1 based ROMs. Nice work with the Kernel. It seems to be VERY customisable in Deathly Adiutor which is great for me. As with all Nougat based ROMs, the audio input latency is the best it's ever been. I would like the ability to enable software keys and to be able to bypass the hardware keys because as you most certainly know they have a strong tendency to interfere with this device (I keep catching them with my hand). Also, the IR blaster doesn't work AT ALL. I would like that to be fixed as Peel Smart Remote is an everyday app for me and I can't use it with this ROM.
Click to expand...
Click to collapse
I have to admitted that I didn't test the IR at all. Will give it a run asap. Sorry.
Sent from my Samsung SM-T705 using XDA Labs

I can now say I can only just make a phone call with this ROM. It's echoey and almost unmanageable when it does work, but it doesn't always work (no sound, normally causes the phone to lock up and force reset upon hanging up). I really want a non-stock ROM that works, preferably Android Nougat 7.1.2 but everyone seems to get the half finished, get fed up and leave us in the dark, and then finally after 6 months mark it as discontinued (cough cough LiquidDeath). I hope you don't do that because this ROM is promising.
Edit: The locking up may have been my fault for overclocking too high.

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