Develop Bugs

Audio lowerings itself

Hey guys, I've been having a problem with the N5X since I bought it. First thing I did when I bought it was to root it and change the ROM, of course. I installed BlissROM (don't remember which build) and ARISE Mod but everytime when I started playing a song (or when someone called me) the audio always started playing loud (as it should) but after a second or two it would lower itself (not the volume steps, just the speaker sound). At first I thought it was a problem with the ARISE mod so I tried without it but the sound was terrible, so I tried changing ROMs and I found that Resurrection Remix with Arise works without problems (the audio works perfectly). But now I've got the same problem if I try to update the ROM (I'm using 20160616 build) the audio starts lowering itself again and I'm stuck with Android 6.0.1 because of it. Can somebody tell me what is causing the problem so I can fix it ? I tried different ROMs, different kernels and different versions of ARISE without luck and I'm out of ideas. Sorry for the long post and thanks in advance

Umm, is there a compatibility chart with ROMs for ARISE? I use something different and that's Viper4Android that works slick with all Android M ROMs.
Suspect an issue with ARISE.

theLazyGeek said:
Umm, is there a compatibility chart with ROMs for ARISE? I use something different and that's Viper4Android that works slick with all Android M ROMs.
Suspect an issue with ARISE.
Click to expand...
Click to collapse
Yup, I tried V4A without ARISE, no luck.

Try going to TWRP Advanced and fix se Linux contents which does se Linux enforcing which will be needed for some mods.

theLazyGeek said:
Try going to TWRP Advanced and fix se Linux contents which does se Linux enforcing which will be needed for some mods.
Click to expand...
Click to collapse
Sadly, didn't help.

Laggy video playback and no audio

Hi all, after I flash any rom (ressurection remix or lineage os 14.1) video lags in YouTube and there is no audio when it does play. Also Spotify has no audio and same with Facebook videos etc.
This is obviously a system wide thing so if someone could help me I'd greatly appreciate it as I can't use my phone for what id normally use it for. Many thanks in advance.

Hi, I have the same problem, only I am using stock rom 9.2.3.0 can't find any reason why this happened. All videos stutter with no audio. Before I updated to newest release it was all working.

magin1 said:
Hi, I have the same problem, only I am using stock rom 9.2.3.0 can't find any reason why this happened.
Click to expand...
Click to collapse
Sorry for the late response but I have the solution worked perfect for me. Follow this and then reboot.
https://forum.xda-developers.com/mi-5s/help/media-lags-phone-browser-t3685290
He means build prop editor too.

I have the same problem with LOS 16.
Unfortunately buildprop cannot find an attribute called audio.deep_buffer.media.
What else can I do?

Same problem happened to me yesterday (didn't hear the alarm clock cause there was no sound ). I'm on the same version of unofficial rr16 from 4 months and this issue began yesterday. If i reboot the phone the problem disappear for some time, then comes back again.
P.S. i don't have audio.deep_buffer.media in my build prop too

Lol you saved me. I am using a miui gsi right now, I also didn't have the prop. Simply download a root explorer like mixplorer, go to /system/build.prop and open it with text editor. Then add: audio.deep_buffer.media=false

LDAC 8.1

So I have been trying to get LDAC or apt-X working on my razer phone but it has not worked. I am on the latest stock ROM rooted with magisk (via ADB not TWRP) and with the rayglobe magisk module installed but it just stays on AAC. My headphones are Sony WH-1000XM2 and LDAC was working when using the resurrection remix ROM from the development thread but I had to uninstall the ROM due to instability and no sign of progression. Any help would be appreciated.

Firebuster said:
So I have been trying to get LDAC or apt-X working on my razer phone but it has not worked. I am on the latest stock ROM rooted with magisk (via ADB not TWRP) and with the rayglobe magisk module installed but it just stays on AAC. My headphones are Sony WH-1000XM2 and LDAC was working when using the resurrection remix ROM from the development thread but I had to uninstall the ROM due to instability and no sign of progression. Any help would be appreciated.
Click to expand...
Click to collapse
They locked it down somehow I think. I have 2 threads in here asking for help but no one seems to be able to help me. For added reference, here is the error produced even when all the files are added with root to enable aptx or ldac

I installed the magisk aptx&aptxHD module and modified /system/vendor/build.prop then aptx got working.
(I couldn't test with aptxHD or LDAC cos I have no compatibe device with them.)
Code:
persist.vendor.bt.a2dp_offload_cap=sbc-aac
to
Code:
persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptXHD
This is the same parameter the magisk module set to /system/build.prop.
To guess, LDAC will may work if an appropriate value set to the prop.

ClubRaptor said:
I installed the magisk aptx&aptxHD module and modified /system/vendor/build.prop then aptx got working.
(I couldn't test with aptxHD or LDAC cos I have no compatibe device with them.)
to
This is the same parameter the magisk module set to /system/build.prop.
To guess, LDAC will may work if an appropriate value set to the prop.
Click to expand...
Click to collapse
This worked to enable switching to them however now Bluetooth just crashes. I changed it to persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptxhd-ldac
Edit:
Some interesting notes. I tried a few steps to debugging including readding AAC to the list which did nothing but if I only add aptx then the Bluetooth app no longer crashes however no sound plays so I'm guessing it's the lib files that are not correct? I just used the aptx package in magisk so if there's any other that I'm missing or other suggestions that would be useful

Firebuster said:
This worked to enable switching to them however now Bluetooth just crashes. I changed it to persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptxhd-ldac
Edit:
Some interesting notes. I tried a few steps to debugging including readding AAC to the list which did nothing but if I only add aptx then the Bluetooth app no longer crashes however no sound plays so I'm guessing it's the lib files that are not correct? I just used the aptx package in magisk so if there's any other that I'm missing or other suggestions that would be useful
Click to expand...
Click to collapse
I still can't get it to switch to aptx (the one I want) or ldac. It still falls back to SBC usually or aac if I'm on a different speaker. Any idea what I'm doing wrong? I'm on slot a on my device, rooted with magisk and I have tried multiple aptx modules. Is there a specific build.prop editor you use? Both my speakers and headphones support it and work with other devices and I'm still getting the error I replied with above (page one)
I'm an experienced rooter, so don't be afraid to fully explain any steps I may be missing out!

manor7777 said:
I still can't get it to switch to aptx (the one I want) or ldac. It still falls back to SBC usually or aac if I'm on a different speaker. Any idea what I'm doing wrong? I'm on slot a on my device, rooted with magisk and I have tried multiple aptx modules. Is there a specific build.prop editor you use? Both my speakers and headphones support it and work with other devices and I'm still getting the error I replied with above (page one)
I'm an experienced rooter, so don't be afraid to fully explain any steps I may be missing out!
Click to expand...
Click to collapse
I used root explorer and changed the build.prop entries in system\vendor\. In the first place I used the root essentials build.prop editor which shows a different build.prop. other than that I literally just edited that line and that allowed me to change it. I can't think of anything else I did other than install a bunch of library files which I'm guessing you found the same ones as me because it was very limited on what was available and up to date

Firebuster said:
I used root explorer and changed the build.prop entries in system\vendor\. In the first place I used the root essentials build.prop editor which shows a different build.prop. other than that I literally just edited that line and that allowed me to change it. I can't think of anything else I did other than install a bunch of library files which I'm guessing you found the same ones as me because it was very limited on what was available and up to date
Click to expand...
Click to collapse
OK, awesome. You rock. That got it to select aptx - now my 2nd problem, no audio! I can see in dev options and bt settings that it's showing aptx, but I get no audio (well, I get an almost click click click noise) then my Bluetooth adaptor for my headphones crashes. And it forces my headphones to turn off. I tried 3 different magisk modules for the library files, any ideas - I was getting SBC audio before

manor7777 said:
OK, awesome. You rock. That got it to select aptx - now my 2nd problem, no audio! I can see in dev options and bt settings that it's showing aptx, but I get no audio (well, I get an almost click click click noise) then my Bluetooth adaptor for my headphones crashes. And it forces my headphones to turn off. I tried 3 different magisk modules for the library files, any ideas - I was getting SBC audio before
Click to expand...
Click to collapse
Sounds like the same problem I am having. Aptx doesn't work and aptx HD and LDAC just crash Bluetooth. Genuinely have no idea where to go from here. It must be a driver or library file. Real shame it's not working.

Edit: seems to be looping these messages in catlog

Firebuster said:
Sounds like the same problem I am having. Aptx doesn't work and aptx HD and LDAC just crash Bluetooth. Genuinely have no idea where to go from here. It must be a driver or library file. Real shame it's not working.
Click to expand...
Click to collapse
OK, so last night and this morning I have been just messing with things. I no longer crash my headphones and force them to turn off, but I still have no audio over aptx - though at least it's not crashing my headphones (Bluetooth in the phone was always OK). There is one error I'm getting and I'm not sure if its related of not, but is to do with a buffer failing to release. See my screenshots of logs (just documenting here for reference)

so basically i went your path a few days ago and dropped that idea. please post updates if you manage to get aptx\aptx hd\ldac working (Razer Phone + Sony WH-1000 XM2)

hatemosphere said:
so basically i went your path a few days ago and dropped that idea. please post updates if you manage to get aptx\aptx hd\ldac working (Razer Phone + Sony WH-1000 XM2)
Click to expand...
Click to collapse
Cc @Firebuster
So, I might be an experienced rooter (no 1 click toolkits here) I am NOT a developer. I've tried a combination of a bunch of things to try and get this to work, and nothing has!
I did however get it to work by installing a GSI (basically a rom) to the device, but even that was painful to get working (well, installed). Now running AOSP 8.1 GSI w/gapps and I flashed magisk for root. I then installed the Aptx magisk module from the built in repo and it works perfectly fine. Not sure if It's something in razer software as I'm technically more up to date now so it's not like I was using the wrong drivers.
Can't find a decent dolby atmos I can install that will work along side v4a, all the magisk modules are for android 7 or 6.
Otherwise that's the only way I have found so far, sorry guys! - benefit is, other than AOSP's ****ty camera app (use the gcam port instead), literally everything works fine, and I even get stronger vibration on a GSI

manor7777 said:
Cc @Firebuster
So, I might be an experienced rooter (no 1 click toolkits here) I am NOT a developer. I've tried a combination of a bunch of things to try and get this to work, and nothing has!
I did however get it to work by installing a GSI (basically a rom) to the device, but even that was painful to get working (well, installed). Now running AOSP 8.1 GSI w/gapps and I flashed magisk for root. I then installed the Aptx magisk module from the built in repo and it works perfectly fine. Not sure if It's something in razer software as I'm technically more up to date now so it's not like I was using the wrong drivers.
Can't find a decent dolby atmos I can install that will work along side v4a, all the magisk modules are for android 7 or 6.
Otherwise that's the only way I have found so far, sorry guys! - benefit is, other than AOSP's ****ty camera app (use the gcam port instead), literally everything works fine, and I even get stronger vibration on a GSI
Click to expand...
Click to collapse
Yeah I might move onto that too. To try to fix the Bluetooth issues. I can only assume razer excluded some of the functionality but since it's baked into android 8 I don't see why they would remove it.

Razer and their development team is already informed about this issue, and they have correctly addressed it, and all the Bluetooth issues (which were a few), in the upcoming update MR2. No ETA.

linuxct said:
Razer and their development team is already informed about this issue, and they have correctly addressed it, and all the Bluetooth issues (which were a few), in the upcoming update MR2. No ETA.
Click to expand...
Click to collapse
so i've just got a new update and now i'm wondering if we should try this again...

hatemosphere said:
so i've just got a new update and now i'm wondering if we should try this again...
Click to expand...
Click to collapse
Go ahead, I can't since I'm on a Pie GSI.
If anyone has an LDAC BT Headset please give this a try.
cc @Firebuster

Great news, I just spent 2 hours updating my phone, with flashing back to stock because the OTA did not want to update me since I had Magisk, then putting everything back like before.
The update did not change anything.

Tried to do my research on issues with the Razer phone before getting it, but I guess this is just one of those things you don't comprehend until actually having the device in your hands. I came from a Oneplus One on Lineage OS and am comfortable with flashing (but no experience with GSI yet).
My razer phone is stock and not rooted. Anything I can do to contribute to test getting Apt-X working? The settings says my phone is up to date (build number OPM1.171019.011-RZR-180803.6033).

Got the official Pie installed - no LDAC nor AptX still.

cubeover said:
Got the official Pie installed - no LDAC nor AptX still.
Click to expand...
Click to collapse
you installed the official pie update for the razer phone 1?

[GSI] [treble] Android 9 pie Bluetooth in call problem

I've tried all treble pie roms and in all are the same problem with Bluetooth in call sound. First I thougt it's a problem with my elephone u pro, but in the meanwhile I've recognized that the same problem exist in many phones.
I'll hope that we can support the developers with a payment if they fix this problem.
I am willing to pay up to 50$ if someone is able to fix this problem for the elephone u pro.
If there's someone else who wants to get the problem solved then please write here your payment offer.
But it would be a shame if people make an offer here and do not stick to it later.

Root first, then go to Vendor/Overlay/BluetoothResCommon.apk
delete it,then reboot,

a05haiji28 said:
Root first, then go to Vendor/Overlay/BluetoothResCommon.apk
delete it,then reboot,
Click to expand...
Click to collapse
I'll try in the bext days....

a05haiji28 said:
Root first, then go to Vendor/Overlay/BluetoothResCommon.apk
delete it,then reboot,
Click to expand...
Click to collapse
Hi, I've tried today but in my elephone u pro there isn't a Vendor/Overlay/BluetoothResCommon.apk
Other ideas?

Laptapper said:
I've tried all treble pie roms and in all are the same problem with Bluetooth in call sound. First I thougt it's a problem with my elephone u pro, but in the meanwhile I've recognized that the same problem exist in many phones.
I'll hope that we can support the developers with a payment if they fix this problem.
I am willing to pay up to 50$ if someone is able to fix this problem for the elephone u pro.
If there's someone else who wants to get the problem solved then please write here your payment offer.
But it would be a shame if people make an offer here and do not stick to it later.
Click to expand...
Click to collapse
1. You have to extract stock /vendor/etc/audio/audio_policy_configuration.xml and delete A2DP related section like this:
https://github.com/PixelExperience-...mmit/977444af69f10fc135d07e19f1e5f1183e73e9ff
then replace it (by root explorer or creating magisk module).
2. You also need to change /system/bin/rw-system.sh.
Please delete
Code:
mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true
and save.
NOTE: This works only on CAF based custom roms. It doesn't work on AOSP.

AndroPlus said:
You have to extract stock /vendor/etc/audio/audio_policy_configuration.xml and delete A2DP related section like this:
https://github.com/PixelExperience-...mmit/977444af69f10fc135d07e19f1e5f1183e73e9ff
then replace it (by root explorer or creating magisk module).
Click to expand...
Click to collapse
Hi
I've tried, but the changed and saved file
/vendor/etc/audio/audio_policy_configuration.xml
will be automatically deleted at restart.
The folder is empty after restart.
Any ideas?

Laptapper said:
Hi
I've tried, but the changed and saved file
/vendor/etc/audio/audio_policy_configuration.xml
will be automatically deleted at restart.
The folder is empty after restart.
Any ideas?
Click to expand...
Click to collapse
Oops, you also need to change /system/bin/rw-system.sh.
Please delete
Code:
mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true
and save.

AndroPlus said:
Oops, you also need to change /system/bin/rw-system.sh.
Please delete
Code:
mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true
and save.
Click to expand...
Click to collapse
Great job! Bluetooth In call is working.
I'll think it's not your development but for your know how to, I've send you 15 Euro.
Do you know also how to get Bluetooth audio music working?

By any chance did you get fully functional Bluetooth on the gsi rom or anyone else?

[email protected] said:
By any chance did you get fully functional Bluetooth on the gsi rom or anyone else?
Click to expand...
Click to collapse
I'll hope so. 
 @AndroPlus has already fixed in call and may be he's on the way to solve audio also.

Has it been rectified in all builds
so is it safe to say that we can install the latest version of GSI provided by rom providers made in and released in march.
I would like to know that before i go ahead and transition over from stock to custom rom... mainly called PixelDust Pie rom version march

Laptapper said:
Great job! Bluetooth In call is working.
I'll think it's not your development but for your know how to, I've send you 15 Euro.
Do you know also how to get Bluetooth audio music working?
Click to expand...
Click to collapse
Thank you, but BT music works fine on my phone (Mi 9).
I don't know how to fix it...
[email protected] said:
so is it safe to say that we can install the latest version of GSI provided by rom providers made in and released in march.
I would like to know that before i go ahead and transition over from stock to custom rom... mainly called PixelDust Pie rom version march
Click to expand...
Click to collapse
No, the fix needs device specific path and not all GSI has it.

I have the Razer Phone and have got either audio working or in call but never both... I am in the process of going through both audio routing files and see if I can combine them to get it to work, but I haven't messed with Android in years so it's taking more time than I anticipated to get caught up on all the changes you guys have made. The last time I built a rom was when treble was just on the discussion table. It really amazes me this bug has gone on this long, but maybe there's more to it than I'm seeing so far. I have seen some good devs working on this.

Enlighten me Please
AndroPlus said:
Thank you, but BT music works fine on my phone (Mi 9).
I don't know how to fix it...
No, the fix needs device specific path and not all GSI has it.
Click to expand...
Click to collapse
Hey @AndroPlus , could you possibly explain how to go about it. I would appreciate the help. I have got a nokia 7 plus with pixel dust pie rom on latest version running. Where and what do i need to do to get it up and running on my phone. I need to get in call bluetooth running. Thats the only thing stopping me from using this amazing blazing rom

Bluetooth music also does not work with me. However bluetooth calls work, so its weird that music/audio is not working.

Bluetooth music also does not work for me, but bluetooth calls work fine. I'm using Arrow GSI with Mi Mix 3.

Laptapper said:
Great job! Bluetooth In call is working.
I'll think it's not your development but for your know how to, I've send you 15 Euro.
Do you know also how to get Bluetooth audio music working?
Click to expand...
Click to collapse
That's on my AOSP ROM?

phhusson said:
That's on my AOSP ROM?
Click to expand...
Click to collapse
It's on resurrection remix pie, also headset over usb c is working. Only audio sound over Bluetooth is a problem. Do you've got a solution ir an idea what should I can try?
Btw do you have any idea how to control the led colours?

i still have no bluetooth calling on Mi Mix 3 on the @AndroPlus rom's so his solution definitely doesn't work for all devices.
furthermore there is still a bounty to get bluetooth working perfectly on vanilla android gsi's

AndroPlus said:
Oops, you also need to change /system/bin/rw-system.sh.
Please delete
Code:
mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true
and save.
Click to expand...
Click to collapse
Thank you sooo much! That´s all, I needed to do to fix my incall audio problem!
No changes in audio_policy.xml were needed - only removing this line from rw-system.sh

Flashlight & Camera stopped working after updating to OOS 10.0.0!

After updating from OOS 9.0.10 to OOS 10.0.0, flashlight toggle is grayed out and when i try to open camera it says 'failed to open camera' does anybody has the same problem? any solution?
OnePlus 5t, rooted (magisk 20.4) with edxposed. i dirt flashed the full OTA file and flashed magisk zip right afterwards on TWRP recovery (i used to do that and it worked for me)

nadiration said:
After updating from OOS 9.0.10 to OOS 10.0.0, flashlight toggle is grayed out and when i try to open camera it says 'failed to open camera' does anybody has the same problem? any solution?
OnePlus 5t, rooted (magisk 20.4) with edxposed. i dirt flashed the full OTA file and flashed magisk zip right afterwards on TWRP recovery (i used to do that and it worked for me)
Click to expand...
Click to collapse
Hi, one plus already shared that u can go back to its previous version but for that u have to wipe full data from your device. Try to downgrade and then update through oxygen updater. It will help you download full update for your rooted device.

atulsharma1224 said:
Hi, one plus already shared that u can go back to its previous version but for that u have to wipe full data from your device. Try to downgrade and then update through oxygen updater. It will help you download full update for your rooted device.
Click to expand...
Click to collapse
it seems you didn't understand what I'm talking about never mind i will figure out how to solve it
Sent from my ONEPLUS A5010 using Tapatalk

2 times this has been asked in a forum of loads of people. Do the people it has happened to think they have done everything right? as I myself would look and say I form a rather small percentage with what happened to me and come to the conclusion it must be the way I installed it and try installing it properly without anything else and work my way through.
The last post was days ago being 2 threads down and clearly stated it had to do with magisk for that person.
So common sense and a bit of reading would make you think it's obviously a module or magisk version.
Why don't people read and see no one else is really suffering from this problem so just putting up oos10 flash and camera broken doesn't help. Maybe at least put what you did and used step by step so anyone who did want to help you doesn't get shot down as it wasn't the quickfix answer you wanted.
PS. by that I mean what modules do u have installed and what mods have you done as having magisk modules can cause all sorts of problems and edexposed in an update from 9-10 is rather stupid thing to do seeing as half the modules used in 9 don't support 10 unless I'm reading wrong and you installed edexposed and correct modules for your software afterwords.

I'm facing same issue
Since Oos 9.0.11 the camera and flashlight isn't working
Tried all flashing method but give same issue
Tried all custom rom where it using Oosbeta blob-Oos stable blob will give same error
The only one custom rom where the camera working is msm xtended

zhukry said:
I'm facing same issue
Since Oos 9.0.11 the camera and flashlight isn't working
Tried all flashing method but give same issue
Tried all custom rom where it using Oosbeta blob-Oos stable blob will give same error
The only one custom rom where the camera working is msm xtended
Click to expand...
Click to collapse
My current rom where the camera working fine

WireMessiah said:
2 times this has been asked in a forum of loads of people. Do the people it has happened to think they have done everything right? as I myself would look and say I form a rather small percentage with what happened to me and come to the conclusion it must be the way I installed it and try installing it properly without anything else and work my way through.
The last post was days ago being 2 threads down and clearly stated it had to do with magisk for that person.
So common sense and a bit of reading would make you think it's obviously a module or magisk version.
Why don't people read and see no one else is really suffering from this problem so just putting up oos10 flash and camera broken doesn't help. Maybe at least put what you did and used step by step so anyone who did want to help you doesn't get shot down as it wasn't the quickfix answer you wanted.
PS. by that I mean what modules do u have installed and what mods have you done as having magisk modules can cause all sorts of problems and edexposed in an update from 9-10 is rather stupid thing to do seeing as half the modules used in 9 don't support 10 unless I'm reading wrong and you installed edexposed and correct modules for your software afterwords.
Click to expand...
Click to collapse
I don't use any module event it clean flash from the flashtool by edl but still give error no camera and flashlight

zhukry said:
I'm facing same issue
Since Oos 9.0.11 the camera and flashlight isn't working
Tried all flashing method but give same issue
Tried all custom rom where it using Oosbeta blob-Oos stable blob will give same error
The only one custom rom where the camera working is msm xtended
Click to expand...
Click to collapse
I posted a solution try it https://forum.xda-developers.com/on...-camera-updating-rooted-t4108335/post82718935

I solved it myself and posted solution here https://forum.xda-developers.com/on...-camera-updating-rooted-t4108335/post82718935

@nadiration THREAD CLOSED!
If interested in the solution, please refer to here: https://forum.xda-developers.com/oneplus-5t/how-to/fix-flashlight-camera-updating-rooted-t4108335
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse
Next time, please provide your solution in your already existing thread. You can also always request the moderators' team (best via the report function) to move the thread to a different sub-forum.