Database Users

[Guide] How to record Call On our Galaxy 3

All Galaxy 3 Firmwares don't have the ability to record both streams of a call. This is not a bug, it was designed like this because in most countries it is illegal to record someone without their permission. Yes, there are apps that will let you record a call, but without software support, it will record the other end from the microphone, which will result in low quality, but there is a workaround.
This might be illegal in your country! I'm not responsible if you get sued for recording someone without their permission.
12.1 Download the attached "CallRecord.zip" and unpack it.
12.2 After unpacking you should have 3 .so files. You need to get these files into your /system/lib folder with either adb or by copying them to the phone and then using "Root Explorer" to copy them to the proper folder.
12.3 Reboot.
12.4 After the phone has rebooted, you can use most apps that are on the market to record calls properly (that means not from the microphone). I use AllCallRecorder because it is simple and does the job. There are also Phone.apk's that have call recording built in, you could also install one of those and record your calls with it.
Sorry don't use this . Not working.

shreyasharusia said:
All Galaxy 3 Firmwares don't have the ability to record both streams of a call. This is not a bug, it was designed like this because in most countries it is illegal to record someone without their permission. Yes, there are apps that will let you record a call, but without software support, it will record the other end from the microphone, which will result in low quality, but there is a workaround.
This might be illegal in your country! I'm not responsible if you get sued for recording someone without their permission.
12.1 Download the attached "CallRecord.zip" and unpack it.
12.2 After unpacking you should have 3 .so files. You need to get these files into your /system/lib folder with either adb or by copying them to the phone and then using "Root Explorer" to copy them to the proper folder.
12.3 Reboot.
12.4 After the phone has rebooted, you can use most apps that are on the market to record calls properly (that means not from the microphone). I use AllCallRecorder because it is simple and does the job. There are also Phone.apk's that have call recording built in, you could also install one of those and record your calls with it.
Click to expand...
Click to collapse
Nice one mate..!
Thank u

Thanks!
This will surely help me to pull pranks

that means not from microphone
Click to expand...
Click to collapse
What does this means?

I soft-bricked my phone when I tried this. :-\
Did it work for anyone? :O
Sent from my GT-I5801 using Tapatalk

Problem!!
Hmm.. Thought i was the only one. I'm stuck at Samsung logo for abt an hr now.
gonna try flashing ROM to recover. Nothing works as of now. Tried Factory Reset and Rebooting etc., Please be clear on the specificity of changing our Phone's settings It might not end well for all. And I don't know if it helps, I moved the files through Root Explorer and my phone is I5801.

krishk said:
Hmm.. Thought i was the only one. I'm stuck at Samsung logo for abt an hr now.
gonna try flashing ROM to recover. Nothing works as of now. Tried Factory Reset and Rebooting etc., Please be clear on the specificity of changing our Phone's settings It might not end well for all. And I don't know if it helps, I moved the files through Root Explorer and my phone is I5801.
Click to expand...
Click to collapse
EVEN SAME HAPPENED FOR ME TOO!!
My phone even got hanged at samsung logo... now flashing Dharam's Ultra Clean Ultimate ROM... really got f**cked by these files.... Please be clear on what you posted actually!!

This worked with my stock xxjpm.I dont know why this not worked for you.
By the way this is taken for galaxy s forum. Not developed by me.I had tried this and it worked for me so i posted it.

I have tried it two months ago, but i got a bootloop...

same here, got a soft brick !

if you have changed the proper permission of the 3 files?
sorry for my englisth,i am chinese

if someone can make a call recording successfully?
if someone can make a call recording successfully?
there are 3 important .so files that make the phone has the ability of recording a call,the 3 .so files looks like from samsung i9000.

need help!!!
I need the ability of making a call recording,can someone help me?
thank you

everyday I come here,and everytime i am so disappointed.
I need the function of recording call.
My phone is Sumsung Galaxy I5800.

Did you try this? Did you try it with different roms?
P.S. I haven't tried it yet, but I made an (unsigned) update.zip for people that want it

can someone pls confirm??!

unreal3000 said:
can someone pls confirm??!
Click to expand...
Click to collapse
Not working... tried with kyrilos 5.7
Stuck in boot loop....

stubborn_d0nkey said:
Did you try this? Did you try it with different roms?
P.S. I haven't tried it yet, but I made an (unsigned) update.zip for people that want it
Click to expand...
Click to collapse
thank you very much for your reply ,i have not tried it,i want to know if that is possible.i want to know if someone has successed.

Enable tethering through build.prop issues

So recently... I have tried to enable tethering through editing the build.prop. Upon reboot... My camera app stops working and 3rd party camera apps become buggy if I try to replace the stock app.
I am using the "net.tethering.noprovisioning=true" technique.... And changing nothing else. Has anyone else run into this issue or does anyone have a fix.
Issue specifics:
- Happens no matter on stock ROM rooted or custom ROM (currently on resurrection remix)
- flashlight will also stop working until I edit quick menu icons and then it works.
- I have tried wiping cache and formatting.
- tried rebooting
- tried backing up build.prop and restoring it... Issue still stays.
- for awhile I was using elementalx kernel... But the problem still seems to stay on Ex or stock kernel.
- happens on both android 6.0.1 and 7.1.1 ( 7.1.1 currently used)
- moto g4 xt1625 (non-amazon) Athens retus phone model
Any thoughts or fixes?
Thanks

Sorry to double post... But I had a separate thought...
Is there any reason to believe that editing the build.prop outside of Android OS on a Windows PC then remounting it.... Would fix the problem? It doesn't seem to make logical sense that it would help, but at this point I'm grasping at straws.
Thanks

30mmrain said:
Sorry to double post... But I had a separate thought...
Is there any reason to believe that editing the build.prop outside of Android OS on a Windows PC then remounting it.... Would fix the problem? It doesn't seem to make logical sense that it would help, but at this point I'm grasping at straws.
Thanks
Click to expand...
Click to collapse
I had the same exact problem, and tried many of things you tried without success. I finally tried the solution on another site and it fixed all the problems. After I tried it, I realized it was probably a permission issue on build.prop.
I'm not allowed to post the link of the site. However, long story short, try changing the permissions of build.prop by using chmod 644 build.prop, or change build.prop to -rw-r--r-- .

Need HELP @ Note 3 ( SM-N9002 / SM-N9009 ) SIM2 Call Audio/Mic Routing & MagMa-NX ROM

Need HELP @ Note 3 ( SM-N9002 / SM-N9009 ) SIM2 Call Audio/Mic Routing & MagMa-NX ROM
Got my hands on this one beautiful piece of Samsung Galaxy Note3 SM-N9002 Dual-Sim, and it had this odd version of Chinese samsung rom on it, as it comes from factory, half apps installed that comes with it was in Chinese and had no play store etc and was on 4.xx android, so I went and did my research, found working TWRP, managed to install it OK, then tried few beautiful ROM versions and found MagMa-NX (note7 ported ROM) works wonderfully well, zero crashes etc etc and it also has kernel support for SM-N9002 during installation which I chose to use, all features work 100% and everything works ok, all but SIM#2 call audio.
I mean, I have signal on both sim cards simultaneously OK, I can make and receive calls and all would seem ok, but when dialed to or from SIM#2 there is no audio coming out from earpiece or loudspeaker and mic dont seem to activate as even if I try to record call which feels like muted for both caller and receiver ends, call audio recorder while recording does not pick up any sound trough phone microphones, so I think its something to do with settings in some file not done right or else I dont know what I could be doing wrong.
both sim cards worked 100% ok before ROM flash, but now I'm lost because I cant even flash back to old stock rom, and yes I have gathered original android 4.xx rom but it fails flashing via ODIN every time, so my best bet is on doing some DIY on current MagMa-NX note7 port rom... I wonder if there are any fellows who I could buy the paypal-beer for great help sorting me out on this DIY project? Please PM me or post here if you feel like you could collaborate in resolving this dilemma for me... would highly appreciate folks
I will keep an eye out

I think I figured something. Everytime I attempt to make a phone call on this, I get to choose from which sim card should I dial, #1 or #2 , but what I have noticed now is that I am being asked "SIM1" or "Slot2" ... SLOT 2 I thought? That may be the reason that audio routing doesnt work well for this... tried searching build.prop but this string is not there and I just dont know where to search for this string to get this fixed, anybody can chime in?
Thanks

Did you figure it out ? As i have the same problem with the same rom in addition that when i call anyone and he is on a call i don't get notified with " call waiting

Mr.Ultimate said:
Got my hands on this one beautiful piece of Samsung Galaxy Note3 SM-N9002 Dual-Sim, and it had this odd version of Chinese samsung rom on it, as it comes from factory, half apps installed that comes with it was in Chinese and had no play store etc and was on 4.xx android, so I went and did my research, found working TWRP, managed to install it OK, then tried few beautiful ROM versions and found MagMa-NX (note7 ported ROM) works wonderfully well, zero crashes etc etc and it also has kernel support for SM-N9002 during installation which I chose to use, all features work 100% and everything works ok, all but SIM#2 call audio.
I mean, I have signal on both sim cards simultaneously OK, I can make and receive calls and all would seem ok, but when dialed to or from SIM#2 there is no audio coming out from earpiece or loudspeaker and mic dont seem to activate as even if I try to record call which feels like muted for both caller and receiver ends, call audio recorder while recording does not pick up any sound trough phone microphones, so I think its something to do with settings in some file not done right or else I dont know what I could be doing wrong.
both sim cards worked 100% ok before ROM flash, but now I'm lost because I cant even flash back to old stock rom, and yes I have gathered original android 4.xx rom but it fails flashing via ODIN every time, so my best bet is on doing some DIY on current MagMa-NX note7 port rom... I wonder if there are any fellows who I could buy the paypal-beer for great help sorting me out on this DIY project? Please PM me or post here if you feel like you could collaborate in resolving this dilemma for me... would highly appreciate folks
I will keep an eye out
Click to expand...
Click to collapse
Which CSC did you choose?

I did not figure anything out guys... as I was trying to get this working, I tried every CSC option possible... none worked. Which should have been the one that's working for this models?
in fact Im thinking of selling this beauty of note3, its almost new... in case someone interested I have it... because I would love note7 port rom on this, and nothing else... PS I could live with it being just single-sim option, it works but not perfect as sim #2 is useless then... signal there and texts only works for it as described above...
at the moment its on stock adroid 5.0 and its all 100% ok and fine, flawless, but its boring!

Mr.Ultimate said:
I did not figure anything out guys... as I was trying to get this working, I tried every CSC option possible... none worked. Which should have been the one that's working for this models?
in fact Im thinking of selling this beauty of note3, its almost new... in case someone interested I have it... because I would love note7 port rom on this, and nothing else... PS I could live with it being just single-sim option, it works but not perfect as sim #2 is useless then... signal there and texts only works for it as described above...
at the moment its on stock adroid 5.0 and its all 100% ok and fine, flawless, but its boring!
Click to expand...
Click to collapse
Well, i know that mixer paths are different on single sim and dual sim phones.
Can you extract from stock rom the file "/system/etc/mixer_paths.xml" and overwrite the one in custom rom ?

I think I tried something similar if not exact with no success .. let me repeat the process just in case...
PS also, I will try and dump both versions of these files. Is there anything else I may need to dump from stock rom 5.0 rom?

Mr.Ultimate said:
I think I tried something similar if not exact with no success .. let me repeat the process just in case...
PS also, I will try and dump both versions of these files. Is there anything else I may need to dump from stock rom 5.0 rom?
Click to expand...
Click to collapse
There are some specific binaries and libs, but i'm pretty sure magma rom already inject them during flash when you select n9002 as variant.
Dumping the CSC folder is a good idea too.

zlazaar said:
There are some specific binaries and libs, but i'm pretty sure magma rom already inject them during flash when you select n9002 as variant.
Dumping the CSC folder is a good idea too.
Click to expand...
Click to collapse
cool, which is the csc folder to be exact? will there should there be any conflicts between 5.0 stock android and 6.0 in magma rom when doing CSC trick?
thanks

Mr.Ultimate said:
cool, which is the csc folder to be exact? will there should there be any conflicts between 5.0 stock android and 6.0 in magma rom when doing CSC trick?
thanks
Click to expand...
Click to collapse
Path : /system/csc
Indeed, conflits may happen. But just dump it and let we examine it.

Ok here is what I managed to try, I backed up stock rom android 5.0 all working state mixer files from etc dir, then flashed magma rom again, backed up those same files for restoration to working state, replaced files with ones extracted while on 5.0 stock android, reboot device, no sound whatsoever, phone wont even buzz keypad dialtones or connect dial phonecalls just hangs. So I went and restored back original magmanx rom mixer files, reboot, but still no success... so now I have just finished restoring 5.0 again, will dump csc folder and share with you. will also need to charge my battery a bit because @ 30% cant expect much to happen when flashing magma nx...
Thanks for the help amigo!!!

Alright, tried merging csc from 5.0 to magmanx 6.0, no luck. then tried after this to merge mixer file from 5.0 to magmanx 6.0 , no luck, back at square1....
files attatched both versions... obviously something wasnt done right from looong time ago and had never been reported, been forgotten... in regards of 9002 users..
https://forum.xda-developers.com/attachment.php?attachmentid=4154927&stc=1&d=1495202856

Mr.Ultimate said:
Alright, tried merging csc from 5.0 to magmanx 6.0, no luck. then tried after this to merge mixer file from 5.0 to magmanx 6.0 , no luck, back at square1....
files attatched both versions... obviously something wasnt done right from looong time ago and had never been reported, been forgotten... in regards of 9002 users..
https://forum.xda-developers.com/attachment.php?attachmentid=4154927&stc=1&d=1495202856
Click to expand...
Click to collapse
Indeed, the mixer_paths of TW6 is missing the whole part concerning "cp2" (second sim).
I'm not a reel dev but i tried to add missing parts from TW5.
Can you please try the attached mixer_paths on magma ? (don't touch csc).

zlazaar said:
Indeed, the mixer_paths of TW6 is missing the whole part concerning "cp2" (second sim).
I'm not a reel dev but i tried to add missing parts from TW5.
Can you please try the attached mixer_paths on magma ? (don't touch csc).
Click to expand...
Click to collapse
amazing, will try in few mins

no success, exact same fail of global audio post merging files... any more ideas... ? really appreciate your effort man, really do!

Mr.Ultimate said:
no success, exact same fail of global audio post merging files... any more ideas... ? really appreciate your effort man, really do!
Click to expand...
Click to collapse
Did you checked correct permissions before reboot ?
I'm afraid the problem is deeper than mixer paths.
I'll try to digg more.

I enable root explorer in third party file manage, grant permission, copy file from sd card to system/etc, prompt to overwrite -grant, overwrite complete, power off phone from power-button menu, power on, done. is this bad/incorrect procedure? magmanx has root from stock, when I navigate root dir I get access grant prompt, I grant it and then I can modify whatever.
please let me know what else I could do? maybe there are specific files I could look in to dump out of working 5.0 rom? Thanks!
or maybe just directory content filenames that could/would make sense by their name etc?
its weird, I think its something to do with the kernel itself... maybe Im wrong, but I dont think 9002/9008 kernels were ever made properly to be tested thus the errors... I cant even find any other kernels for 9002 other than included in magmanx and it aint working well anyway

Mr.Ultimate said:
I enable root explorer in third party file manage, grant permission, copy file from sd card to system/etc, prompt to overwrite -grant, overwrite complete, power off phone from power-button menu, power on, done. is this bad/incorrect procedure? magmanx has root from stock, when I navigate root dir I get access grant prompt, I grant it and then I can modify whatever.
please let me know what else I could do? maybe there are specific files I could look in to dump out of working 5.0 rom? Thanks!
or maybe just directory content filenames that could/would make sense by their name etc?
its weird, I think its something to do with the kernel itself... maybe Im wrong, but I dont think 9002/9008 kernels were ever made properly to be tested thus the errors... I cant even find any other kernels for 9002 other than included in magmanx and it aint working well anyway
Click to expand...
Click to collapse
The file "mixer_paths.xml" must have permission set to 0644 (like other files in /system/etc directory).
And try darklord Kernel.

6044 is as per read/write permissions for user enabled, as per this link http://permissions-calculator.org/decode/0644/ , I assume these permissions will auto set after moving replacing file do they not?
Where do I obtain the darklord kernel? I was pretty sure it comes with it... let me re-do the rom and take some snips as I go

Mr.Ultimate said:
6044 is as per read/write permissions for user enabled, as per this link http://permissions-calculator.org/decode/0644/ , I assume these permissions will auto set after moving replacing file do they not?
Where do I obtain the darklord kernel? I was pretty sure it comes with it... let me re-do the rom and take some snips as I go
Click to expand...
Click to collapse
Sorry i just noticed you already have darklord kernel.
And set permission like other files in this directory (if not already done by your file manager).

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.

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?