Related
I've recently acquired a new car which has a built in stereo system (Renault Megane Estate 2012 Bose edition) which is able to receive CBR encoded A2DP streams. It works well, connects, music plays, even controls work.
Awesome!
Using catlog I can see that the bitpool that is negotiated is 51. While the sound isn't horrible, I believe the handsets (Samsung Galaxy SIII Int. and Nexus 7, both running CM10 nightly) are able to encode and transmit at a higher bitrate/bitpool then currently is set.
I've tried my best effort in changing this settings. I've built my own Ubuntu kitchen, followed all the guides and have from the looks of it compiled a successful ROM image. Sadly enough when I flash it, my tablet dies (black screen) and even CWM is destroyed. Using fastbood and USB I've been able to recover the tablet, so no problem there, but still, no working ROM. Even without changing something. But that is not what this thread is for, I'll figure that out eventually.
I am trying to recreate the results that are in the following topic : http://forum.xda-developers.com/showthread.php?t=1880298
Sadly, the files provided are not compatible with my CM10 devices and changing the source and then compiling it and replacing the files yields no result. Whatever I try, it stays at 51 (The bitpool it SENDS to the radio as max). There are several files which are connected to the settings, such as cbr.c , audio.a2dp.default.so, etc. but I don't really know what to change to get the desired results.
If anyone is able to help, that would be greatly appreciated. Point me to the right file where I can find the values to change, either in a compiled ROM or in the source so that I can compile it and change the files in
my running ROM using rootexplorer. Whatever works.
I would like to try settings as high as 125. But ideally, I would like to experiment what my headunit accepts, what it can be forced to, and thus finding the highest quality possible using my combination of equipment.
In this the Nexus 7 is the most important because that will be permanently located in the car.
update--
I have found a thread on bluez surrounding this topic.
http://www.spinics.net/lists/linux-bluetooth/msg23091.html
Could someone more knowledgeable then me please take a look at this for me and maybe change the file? Sadly that goes way beyond my programming knowledge, but I would really love to give it a try!
update--
Some extra information and a good explanation as to why I am looking for this (and maybe more people with me).
Bitpool values as high as 128 are possible on Windows Mobile devices (including mine), which means they are possible in A2DP. Such a high value is necessary for some genres of current music, which are highly
compressed (the problem was once discussed in one of Xiph Foundation's articles). SBC is unable to encode such material properly if it doesn't have enough bandwidth.
Click to expand...
Click to collapse
I've done some more tests editing and replacing files and I think I've actually gotten it to sync higher but it still displays it's at 51. The sound just sounds a lot better, but of course, that can always be a placebo effect. :silly:
So, anyone have any insight, or who can point me into the right direction of what needs to be changed and where? As said, I think I have reached the quality increase (bitpool 100) but the logs still display 51.... not quite there yet. And in light of people using the Nexus 7 in a cars a lot (which I also intend) and the borked headphones output I read everywhere, CD quality streaming over A2DP (It's possible) would be awesome!
Kitchen fixed
So I got my kitchen working and am cooking working ROM's.
Just getting the right files changed is giving me some problems.
I think I fixed most of it, but for some reason when I check the logs it still states that it's sending a max bitpool of 51. I believe in the background it's using the 128 as I stated in the source files, but still. I would like the logs to show the same, just to acknowledge I'm a not having a placebo effect.
The files I have changed are the following:
/android/system/external/bluetooth/bluez
a2dp.c
gsta2dpsink.c
gstscenc.c
liba2dp.c
pcm_bluetooth.c
I used the patch listed above on the pcm_bluetooth.c. And I do believe it overrides the settings and it's not set to 51 anymore but the 128 I put in all the files manually. Music sounds great, but it's hard to subjectively test.
Hopefully we can find some people who have a greater understanding of bluez.
Little kick
Little kick to see if someone wants to assist me on this or not. I think it could potentially benefit a lot of people making Bluetooth audio/A2DP go from barely adequate to High Fidelity!
I'd love to help you test this - I also find the A2DP quality to be lacking in a lot of more "active" or compressed music. Acoustic and softer music sounds great, but rock/metal tends to sound like a 128kbps mp3. It actually seems to sound better from my Galaxy Nexus than the 7 as well. I'm running a Bugless Beast ROM now but was running CM10.
Also, not sure if you've seen this but I found an article (soundexpert.org/news/-/blogs/bluetooth-audio-quality-a2dp, sorry can't post links yet) that shows the bitrate per bitpool value. At a bitpool value of 53, the bitrate is around 320kbps. A2DP itself supports a bitrate of up to 512kbps for stereo, but through other optionally-supported codecs. SBC however, in this profile, only seems to go to ~320. It might be worth checking out if your car stereo supports mp3 over A2DP - there is an option in /etc/bluetooth/audio.conf to set MPEG12Sources from 0 to 1 and SBCSources from 1 to 0.
ROM up for download
Hi there, thnx's for joining the cause.
I compiled a new daily today with settings set to bitpool 128. But I don't really hear much change, maybe the setting is too high, maybe something else is going wrong. As stated above, in the logs I can only see it sending 51 as max pool to the device and setteling with it. But since I'm using an edit pcm_bluetooth.c it should override that setting, say it's going to do 51 and then stream and the values I defined in the files.
.....in theory at least...... the only subjective evidence I have for this are my own ears.
So, I will provide you with access to the 128 version and am going to compile a 64 version while I'm at it.
Use an FTP client to connect to:
host: oss.quindorian.org
user: XDA
pass: ROMROM
Anyone is welcome to give it a try. I have put limits on the FTP site, so please beware of that. But I'll put ROM's there you can try and report back on. Tell me if you think it does nothing or if you think it makes it sound like a singing angel. Any feedback is appreciated.
As source I use the CM10 repository so I am basically building modded nightly builds. Today it allready has the 4.1.2 flavor with the newest drivers and everything included. Don't forget to flash gapps if you need them.
Understand
ChrisK15 said:
Also, not sure if you've seen this but I found an article (soundexpert.org/news/-/blogs/bluetooth-audio-quality-a2dp, sorry can't post links yet) that shows the bitrate per bitpool value. At a bitpool value of 53, the bitrate is around 320kbps. A2DP itself supports a bitrate of up to 512kbps for stereo, but through other optionally-supported codecs. SBC however, in this profile, only seems to go to ~320. It might be worth checking out if your car stereo supports mp3 over A2DP - there is an option in /etc/bluetooth/audio.conf to set MPEG12Sources from 0 to 1 and SBCSources from 1 to 0.
Click to expand...
Click to collapse
Yeah, I understand what that article says. But for me, the quality just isn't up to par to listening to a 320Kbit stream. Also, there is what A2DP officialy supports and there is what works. I'm shooting for the last type. If I can get a 1000Kbit stream between my device and my headunit, I will, even if it doens't add much above say 786Kbit, more is always better in this case. If it works that is, ofcourse.
Because I wish to use spotify, I believe my only choice is to use the SBC encoder. Spotify will never let you transfer it's source file to anywhere because of DRM. Alternativly, if we could enable an AAC stream or something (also supported I believe) we'd need less bitrate/bitpool for better quality! And from what I have read, the SBC encoder standard used it just quite crappy. So while a 320Kbit LAME encoded MP3 might sound great/perfect, using a sub-standard encoder can still give it artifacts and low quality. Thus the hunt for insane amounts of bitrate!
Awesome, I'll definitely give it a shot. If it's possible to exceed the Bluetooth standard spec then that'd be awesome. I'm more worried about our receivers not being able to support the higher bandwidth - my head unit is new but only supports SBC unfortunately.
Cool
ChrisK15 said:
Awesome, I'll definitely give it a shot. If it's possible to exceed the Bluetooth standard spec then that'd be awesome. I'm more worried about our receivers not being able to support the higher bandwidth - my head unit is new but only supports SBC unfortunately.
Click to expand...
Click to collapse
Cool, I just put the bitpool64 version there too. Tested it and I notice no real difference. Sadly the quality is still not great, it's not horrible.... but certainly not great so I still feel like my settings are maybe not having any effect whatsoever. As reflected by the logs using catlog. It sen bitpool 51 max and settles for that. For all the values I have changed in the files and that stay the same, I really do not understand. Wish I could fix that, but with my knowledge I have just run out of places where to look.
Let me know if in your case it makes any difference!
I just tried it out and to me it seems like there's an improvement. I normally stream Pandora One in my car, and that definitely seemed like it had more clarity. However Google Music streaming sounded the same, although it was already good to begin with. I would think that compressing more highly-compressed music from the start (Pandora) would have a worse effect on quality than less-compressed music, which seems to be the case. Or maybe I'm just hearing things
Thanks for looking into this, I've been trying to find a way to do this for a while!
Quindor said:
Hi there, thnx's for joining the cause.
I compiled a new daily today with settings set to bitpool 128. But I don't really hear much change, maybe the setting is too high, maybe something else is going wrong. As stated above, in the logs I can only see it sending 51 as max pool to the device and setteling with it. But since I'm using an edit pcm_bluetooth.c it should override that setting, say it's going to do 51 and then stream and the values I defined in the files.
.....in theory at least...... the only subjective evidence I have for this are my own ears.
(...) .
Click to expand...
Click to collapse
perhaps you can test if the patch does anything - by setting bitpool to some very LOW value ?
ChrisK15 said:
It might be worth checking out if your car stereo supports mp3 over A2DP - there is an option in /etc/bluetooth/audio.conf to set MPEG12Sources from 0 to 1 and SBCSources from 1 to 0.
Click to expand...
Click to collapse
On my CM12.1 official nightly ROM (2015/12/03) for my Samsung i9505, there is no file audio.conf
Does that mean I can simply create it with the two lines
MPEG12Sources=1
SBCSources=0
in order to test wether a bluetooth SNK device such as a car stereo or a headset supports mp3 over A2DP?
So does anyone have some actual logs or HCI captures showing bitpool above 53?
..
So, I tried choosing "Apt-X" from within the developer settings - but it doesn't stick. I know my headphones support it, and I looked up the SD660 - it has support for it as well. So, is there a way to enable Apt-X on the A2?
When you say "stick" u mean u can't select it? I can select either of the AptX options and they stay selected. But I'm not closing settings and shutting off the phone to check if it's still "sticking".
If you can't select them, it may be some other BT setting you've changed that's preventing those from being selected? All of my other BT selections are of the 'Auto' type.
AsItLies said:
[...] But I'm not closing settings and shutting off the phone to check if it's still "sticking". [...]
Click to expand...
Click to collapse
Thats exactly right - I can select them, but back out of settings and then check again and its back to the default (auto). I also tried changing the setting while my headphones were connected - in that case, it doesn't even change temporarily and will stay on AAC.
Same here it always goes back to default setting.. can't even use srgb mode
I think the device build is missing the aptx libraries. Currently aptx is not supported. Maybe they will integrate this in any coming release, but I wouldn't count on that.
Weird enough the device is able to use AAC apple Bluetooth driver.
Sent from my Mi A2 using Tapatalk
soulicro said:
Thats exactly right - I can select them, but back out of settings and then check again and its back to the default (auto). I also tried changing the setting while my headphones were connected - in that case, it doesn't even change temporarily and will stay on AAC.
Click to expand...
Click to collapse
After further reflection;
Remembered there are other USB settings that don't persist also. Change the USB connection type (say from Midi to Charge Only), back out, return...
It's not persistent either.
I found a way to work around it, for my purposes anyway, just leave the settings app up, don't close it. And sometimes just connecting with USB set it back, so would have to reset it again. But eventually it worked.
Kind of a pain. Because Android One and Lineage are so similar, I'd check in Lineage forums to see if there's a fix for that.
Small update: I installed Magisk and tried applying two separate modules that should add the Apt-X library files to the phone, but no luck. I've resigned to going back to stock and being hopeful that as community support starts ramping up for our device, we'll see a solution.
Oh well! AAC will need to hold us over 'til then.
need aptX support also
Just came across this in a MiA1 thread, it seems (like camera2API) that it has to be enabled (root access needed) for it to work;
https://forum.xda-developers.com/mi-a1/how-to/guide-enable-custom-bluetooth-audio-t3744371
I can't check, but I saw on another forum that someone enabled aptx this way (and noticed sound improvement): connect headphones, start palying music and only then enable aptx in developer settings. I think you should try it.
AlexX333BY said:
I can't check, but I saw on another forum that someone enabled aptx this way (and noticed sound improvement): connect headphones, start palying music and only then enable aptx in developer settings. I think you should try it.
Click to expand...
Click to collapse
Where did you read this?
pianistaPL said:
Where did you read this?
Click to expand...
Click to collapse
4pda.ru
AlexX333BY said:
I can't check, but I saw on another forum that someone enabled aptx this way (and noticed sound improvement): connect headphones, start palying music and only then enable aptx in developer settings. I think you should try it.
Click to expand...
Click to collapse
Could anybody verify this method?
AsItLies said:
Just came across this in a MiA1 thread, it seems (like camera2API) that it has to be enabled (root access needed) for it to work;
https://forum.xda-developers.com/mi-a1/how-to/guide-enable-custom-bluetooth-audio-t3744371
Click to expand...
Click to collapse
Does not work for me
soulicro said:
So, I tried choosing "Apt-X" from within the developer settings - but it doesn't stick. I know my headphones support it, and I looked up the SD660 - it has support for it as well. So, is there a way to enable Apt-X on the A2?
Click to expand...
Click to collapse
I have the same with my Sony MDR-1000X. They support aptx to. But the A2 won't stick to it
a5c said:
Could anybody verify this method?
Click to expand...
Click to collapse
doesn't work for me. it immediately switches back to sbc.
soulicro said:
Small update: I installed Magisk and tried applying two separate modules that should add the Apt-X library files to the phone, but no luck. I've resigned to going back to stock and being hopeful that as community support starts ramping up for our device, we'll see a solution.
Oh well! AAC will need to hold us over 'til then.
Click to expand...
Click to collapse
I used to have a MI Max and I was able to enable apt-x hd after installing some libraries with magisk. Which process did you follow? I still can't try it on my phone.
apt-x on Mi A2? Yesss! i did it! https://forum.xda-developers.com/mi-a2/help/apt-x-mi-a2-yesss-t3854813
rulezman said:
apt-x on Mi A2? Yesss! i did it! https://forum.xda-developers.com/mi-a2/help/apt-x-mi-a2-yesss-t3854813
Click to expand...
Click to collapse
Just got the official October update. Aptx is supported nativly now. No need to install any magisk module.
Hello guys !
I just updated my MIUI ROM from Android 8 to Android 9. Since I have this one, my Bose QC35 II connected via Bluetooth uses the SBC Codec, which delivers a bad quality comparing to AAC. I tried to change this via the developer options, but when I set to AAC it always comes back to SBC. When I was on Android 8, I had the AAC.
Do you know how can I change that ? I'm on MIUI 10.1.1.0 Global
Thanks a lot, hope my english is understandable
I didn't find a solution, always on SBC Codec which the sound quality quite bad. If anyone has a solution
Isn't Aac a iPhone/apple thing....?
Anyways you can force a specific output mode in developers settings.
My mi8 on global beta defaults to aptx when using my Bluetooth headset.
Stoffl_ said:
Isn't Aac a iPhone/apple thing....?
Anyways you can force a specific output mode in developers settings.
My mi8 on global beta defaults to aptx when using my Bluetooth headset.
Click to expand...
Click to collapse
No it isn't, it's a classical codec. I tried to force it, but it always goes back to SBC, here is my problem !
What I meant is that aptx is superior in every way.
But I guess the BT device your using is aimed at iphones and doesn't support aptx ?
Maybe try and switch to global beta and check if the issue was fixed.
Eozum said:
No it isn't, it's a classical codec. I tried to force it, but it always goes back to SBC, here is my problem !
Click to expand...
Click to collapse
Same thing on my mi mix 2s. While everything works just fine with an Nvidia shield and Android pie. So it's xiaomi fault. I'm Very disappointed because SBC is really inferior.
Try developer mode!
Already tried on dev mod, doesn't change anything. When you set on AAC, the phone simply doesn't care, hope it will be corrected in an update !
Now I am having the same problem and couldn't find any solution. In Developer options, my arrangements revert to old ones when close, they don't stick. I have Android 8 MIUI 10 Xiaomi Mi6. Via Magisk Manager, I flashed codecs and necessary modules to my phone but nothing's changed. when i connect my JBL Free to my phone, SBC logo right next to the earphone's name is there. Before I lose my mind, someone please help me! I am inexperienced to this complex Android world :crying:
I'd start by posting in the correct MI6 subforum
You can use PowerAmp, it can force better audio codec (by cable and BT).
Have you tried it ? It doesn't work
Just a quick update, since the last update 10.2.3.0, i've got the AAC when using my Bose QC-35 The sound quality is waaaaayyyy better than before. Thx Xiaomi !
Eozum said:
Just a quick update, since the last update 10.2.3.0, i've got the AAC when using my Bose QC-35 The sound quality is waaaaayyyy better than before. Thx Xiaomi !
Click to expand...
Click to collapse
Oh great! Now I am on MIUI 10 MiRoom 9.3.14 custom rom. Can we apply 10.2.3.0’s bluetooth codecs to my rom? I do not want to switch my rom but if It is the only solution I will switch
vidanj said:
Oh great! Now I am on MIUI 10 MiRoom 9.3.14 custom rom. Can we apply 10.2.3.0’s bluetooth codecs to my rom? I do not want to switch my rom but if It is the only solution I will switch
Click to expand...
Click to collapse
I don't know,, you should maybe wait for the next update of your ROM
Eozum said:
I don't know,, you should maybe wait for the next update of your ROM
Click to expand...
Click to collapse
I didn't receive BT fix with my new update and I dont believe I will I bought Sennheiser Momentum True Wireless Earbuds and I rarely have stutters thanks to aptX but if codecs were good I would have perfect connection with these earbuds.
I'm afraid you just have to turn on BT in order to change BT CODEC
I have a serious problem with Bluetooth audio.
I have really good headphones, but they are quite old and there's no support for ldac or aptx (just sbc). However I'm coming from Huawei P20 Pro and I never had any problem with audio quality on that phone.
And what exactly I mean? When I'm listening the music I can hear occasional drops of audio bitrate. It's extremely annoying. And no, I'm not using different Bluetooth devices (but I was able to do this with Huawei which had older Bluetooth version [!]), everything about multiple output is disabled, that option in developer's menu is set to 1.6. I'm out of ideas and pretty disappointed that premium device like Note 9 have problems with basic functions like this.
Ps. It's not a problem with my device. Same thing is happening on my friend's Note 9.
connect headphone via Bluetooth then go to
developer mode enable it/Bluetooth audio codec/(select the code you needed)
At what volume do you listen via bluetooth?
I have the same issue with my car receiver and noticed that if i play it at max volume i experience that and if i play it at a slighty lower volume, one or two steps from max, the issue is gone (or so i hope) for now it seems it is resolved by lowering the volume from max, or it is fixed in CSC1
---------- Post added at 10:42 AM ---------- Previous post was at 10:06 AM ----------
Amit.A said:
connect headphone via Bluetooth then go to
developer mode enable it/Bluetooth audio codec/(select the code you needed)
Click to expand...
Click to collapse
How do you make it stay on the selected option? Regardless which option i select the moment i go back or out of developer options it goes back to SBC
u sure ure not streaming through some streaming app and not reading actuall media from internal storage?
I'd try local media and see how that behaves.
bober10113 said:
u sure ure not streaming through some streaming app and not reading actuall media from internal storage?
I'd try local media and see how that behaves.
Click to expand...
Click to collapse
I do not know about the OP but in my case regardles if it is a streaming service (deezer) local files (mp3) and sometimes with call audio, it does that.
_robojock_ said:
I do not know about the OP but in my case regardles if it is a streaming service (deezer) local files (mp3) and sometimes with call audio, it does that.
Click to expand...
Click to collapse
what build if android are you running?
bober10113 said:
what build if android are you running?
Click to expand...
Click to collapse
Devbase PIE CSC1 (It does it with all previous builds too.) I have also tried Dr. Ketan and other n9 roms same issue.
_robojock_ said:
Devbase PIE CSC1 (It does it with all previous builds too.) I have also tried Dr. Ketan and other n9 roms same issue.
Click to expand...
Click to collapse
im using viper audio and other audio mods.
not sure if its me that dosen't realise it but i dont think I've experienced any of this. i use only local media. i play it through power amp and set the audio output manually to high res output.
bober10113 said:
u sure ure not streaming through some streaming app and not reading actuall media from internal storage?
I'd try local media and see how that behaves.
Click to expand...
Click to collapse
No. I'm not using any streaming services. Just FLAC or 320kbps AAC files ripped directly from CD.
_robojock_ said:
At what volume do you listen via bluetooth?
I have the same issue with my car receiver and noticed that if i play it at max volume i experience that and if i play it at a slighty lower volume, one or two steps from max, the issue is gone
Click to expand...
Click to collapse
I'm not listening on max volume, but sometimes it's close (older or more niche music recorded and mastered properly).
Btw just tried listening on my dad's S8+ and it's the same, so Samsung generally has something broken with sbc codec which is rather disappointing.
Btw, I'm using European Exynos model.
That's probably why Samsung still includes the headphone jack with their phones. I don't use bluetooth that often, except in the car and I don't recall experiencing any issues with it. Maybe I don't pay attention to it, but I will this time and see.
I have a task for one of school project to allow play a short audio on voice call. I've been searching for long time for a solution to that problem or at least a starting point, I found some topics that talking about modifying the kernel of android to allow this but I have no idea how to do The project needs to be done in latest android versions ( 10 or 9) with Samsung devices (S10 for example ) which are rooted Thank you
FearNaiim said:
I have a task for one of school project to allow play a short audio on voice call. I've been searching for long time for a solution to that problem or at least a starting point, I found some topics that talking about modifying the kernel of android to allow this but I have no idea how to do The project needs to be done in latest android versions ( 10 or 9) with Samsung devices (S10 for example ) which are rooted Thank you
Click to expand...
Click to collapse
what is it exactly that youre trying to accomplish?
youdoofus said:
what is it exactly that youre trying to accomplish?
Click to expand...
Click to collapse
Thank you for your replay. I'm trying to stream an audio clip through the system on voice call. Means when I am in phone call talking to someone, I can play a short audio clip that can be heard by the other party too. The project is for personal purpose, it means only me that can be using that option, so I can root my device or make a custom rom, I just need to know how i can do that things
Thank you
FearNaiim said:
Thank you for your replay. I'm trying to stream an audio clip through the system on voice call. Means when I am in phone call talking to someone, I can play a short audio clip that can be heard by the other party too. The project is for personal purpose, it means only me that can be using that option, so I can root my device or make a custom rom, I just need to know how i can do that things
Thank you
Click to expand...
Click to collapse
you shouldnt need root to have an apk play audio at the push of a button while on a phone call at the same time
I also search for this feature.
The best would be, if it would be possible to play internal Audio directly via the Voice-Uplink (this is the Audio which goes to the other person), and the Speaker.
Is it possible to Mix the Voice-Uplink Channel, to contain the Microphone input (the Voice) and the Media Audio-Channel?
(That's like the "Stereomix" on Realtek Audio-Cards on PC https://www.google.com/search?safe=...i29i30j0i10i30j0i10i203j35i362i39.7TvHA0zwoeQ)
profi_fahrer said:
I also search for this feature.
The best would be, if it would be possible to play internal Audio directly via the Voice-Uplink (this is the Audio which goes to the other person), and the Speaker.
Is it possible to Mix the Voice-Uplink Channel, to contain the Microphone input (the Voice) and the Media Audio-Channel?
(That's like the "Stereomix" on Realtek Audio-Cards on PC https://www.google.com/search?safe=...i29i30j0i10i30j0i10i203j35i362i39.7TvHA0zwoeQ)
Click to expand...
Click to collapse
this is what i was expecting android to do automatically, and in many cases it does it seems. I was reading about this a bit last night and saw where people were indeed able to play something on the speaker of their phone and have the very same phones mic and play on the phone call for both parties to be able to hear. It was a native in the phones where users reported this ability. It was even reported to work on some older samsung phones. I still have a S4 and could test it out, if i remember to do it (my license plate says IFORGOT). @AthieN this is the thread i was talking about
youdoofus said:
this is what i was expecting android to do automatically, and in many cases it does it seems. I was reading about this a bit last night and saw where people were indeed able to play something on the speaker of their phone and have the very same phones mic and play on the phone call for both parties to be able to hear. It was a native in the phones where users reported this ability. It was even reported to work on some older samsung phones. I still have a S4 and could test it out, if i remember to do it (my license plate says IFORGOT). @AthieN this is the thread i was talking about
Click to expand...
Click to collapse
So basically, they told me that they used to record uing Tinyalsa library (tinycap exactly), but they couldn't do it with samsung S10, when I search I found that there is not tinyalsa included in that phone. So I was wondering if I can add it directly to the system or I have to make own rom for that ?
I hope @AthieN can give us hint on that. Thank you both of you for your help
profi_fahrer said:
I also search for this feature.
The best would be, if it would be possible to play internal Audio directly via the Voice-Uplink (this is the Audio which goes to the other person), and the Speaker.
Is it possible to Mix the Voice-Uplink Channel, to contain the Microphone input (the Voice) and the Media Audio-Channel?
(That's like the "Stereomix" on Realtek Audio-Cards on PC )
Click to expand...
Click to collapse
That's seems a good idea but idk if applicable to android devices or not
Sorry for the late reply. This used to be possible, but not since API 20 or 21 due to security concerns.