Related
Hi All,
How can we have call recording enabled on Stock unrooted ROM? Is it necessary to root for call recording?
Thanks
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
No one???
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
sroy001 said:
No one???
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Have you tried BoldBeast Call recorder? Works great on Oneplus2, my goto app for recording the past year or so.
sroy001 said:
Hi All,
How can we have call recording enabled on Stock unrooted ROM? Is it necessary to root for call recording?
Thanks
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
no call recording in Oxygen OS!
i am using ACR and its ok.
Thanks guys. I purchased ARC Pro and it works great.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Confirm arc or working great.
Sent from my ONEPLUS A3003 using Tapatalk
H2OS has built-in call recorder.
Sent from OnePlus3
where can we find it
Which one? Link please as there are several apps with similar name.
TIA
https://play.google.com/store/apps/details?id=com.nll.acr
...and licence, if you want to have it full
https://play.google.com/store/apps/details?id=com.nll.acr.license
Pr0metheus2 said:
https://play.google.com/store/apps/details?id=com.nll.acr
...and licence, if you want to have it full
https://play.google.com/store/apps/details?id=com.nll.acr.license
Click to expand...
Click to collapse
I can confirm ACR works just fine. Thanks Pr0metheus2 for the links.
naishadh said:
Confirm arc or working great.
Click to expand...
Click to collapse
sroy001 said:
Thanks guys. I purchased ARC Pro and it works great.
Click to expand...
Click to collapse
pascanu said:
I can confirm ACR works just fine. Thanks Pr0metheus2 for the links.
Click to expand...
Click to collapse
Hi guys!
Glad ACR pro is found working on OP3
Has anyone tried recording phonecalls via bluetooth headset?
I found that some devices simply do not record one or the other side on bluetooth headset and this is very important to me.
For anyone interested Honor 7 and Wiko ufeel work fine of the devices currently on the market. I am willing to buy OP3 if it works too!
Thank you for a test!
G
#G# said:
Has anyone tried recording phonecalls via bluetooth headset?
I found that some devices simply do not record one or the other side on bluetooth headset and this is very important to me.
Thank you for a test!
G
Click to expand...
Click to collapse
I tried it, it works, but only in about 1/3 of the cases. Since I only use BT in my car , hands free, I switched to MIC recording so recording still works fine for me.
Curious what others have to say, apparently it CAN record via BT, but doesn't always work (bug?!)
Boldbeast works great
After playing with ACR a little longer I can now confirm it works 100%, both normal and via Bluetooth. I realised I had set the recording delay to 0, so sometimes it didn't record the other party. After setting the Audio Source to Auto and recording delay to 1 second everything works just fine.
Oxygen os not providing inbuilt call record function. But arc works fine for mi
I can confirm SKvalex Call Recorder is working on OP3 either direct or via BT headset.
To figure out the settings took me some time but finally it's all fine.
Choose Standard API / Source Voice Communication / Format eiter WAV, AMR or MP3 and make sure Don't use AMR driver is ticked. When BT connected Do nothing works fine with my Plantronics BT headset.
endrus said:
I can confirm SKvalex Call Recorder is working on OP3 either direct or via BT headset.
To figure out the settings took me some time but finally it's all fine.
Choose Standard API / Source Voice Communication / Format eiter WAV, AMR or MP3 and make sure Don't use AMR driver is ticked. When BT connected Do nothing works fine with my Plantronics BT headset.
Click to expand...
Click to collapse
I use that recorder as well. Haven't messed around with any specific detailed setup but found that it works fine when choosing OnePlus 2 instead of OnePlus 3 as device in the settings.
endrus said:
I can confirm SKvalex Call Recorder is working on OP3 either direct or via BT headset.
To figure out the settings took me some time but finally it's all fine.
Choose Standard API / Source Voice Communication / Format eiter WAV, AMR or MP3 and make sure Don't use AMR driver is ticked. When BT connected Do nothing works fine with my Plantronics BT headset.
Click to expand...
Click to collapse
slonn said:
I use that recorder as well. Haven't messed around with any specific detailed setup but found that it works fine when choosing OnePlus 2 instead of OnePlus 3 as device in the settings.
Click to expand...
Click to collapse
Hi..
Does Call Recorder by skvalex works on non-rooted one plus 3? Or is rooting required?
techie_vintage said:
Hi..
Does Call Recorder by skvalex works on non-rooted one plus 3? Or is rooting required?
Click to expand...
Click to collapse
Request you to read About Me section of the application.
Hello, can anyone who bought Moto Z Play confirm it supports aptX audio codec and successfully play audio through an aptX connection to an aptX supported audio device, or confirm it does not? On the official pages and GSMArena specs I saw only A2DP which is SBC codec.
I wrote to Lenovo tech support and they responded they don't know anything about aptX then suggested me ask aptX team. So wrote another e-mail and seems that the response will be slow. So does anyone can kindly prove it here? Thanks you.
There is another way to confirm, one can check if there is a file named something like libbt-aptX-ARM-4.2.2.so under the path /system/lib/ which means this device supports aptX codec. Can somebody confirm this?
RenoYeh said:
Hello, can anyone who bought Moto Z Play confirm it supports aptX audio codec and successfully play audio through an aptX connection to an aptX supported audio device, or confirm it does not? On the official pages and GSMArena specs I saw only A2DP which is SBC codec.
I wrote to Lenovo tech support and they responded they don't know anything about aptX then suggested me ask aptX team. So wrote another e-mail and seems that the response will be slow. So does anyone can kindly prove it here? Thank you.
Click to expand...
Click to collapse
RenoYeh said:
There is another way to confirm, one can check if there is a file named something like libbt-aptX-ARM-4.2.2.so under the path /system/lib/ which means this device supports aptX codec. Can somebody confirm this?
Click to expand...
Click to collapse
There is a file with the exactly name you said on that folder. So i am inclined to think it has support to aptX codec.
Even the first Moto G supported aptX, last years Moto X Play supported aptX, even though Motorola did not mention it anywhere. Somehow they never talk about aptX but one can take it as granted.
Weird how aptx support almost never seems to be marketed or even mentioned. It costs money to license, you'd think hardware makers would at least tuck the info somewhere. Not that I'm implying that this phone absolutely does support it, as much as circumstantial evidence would suggest. Only way to be sure would have someone with one of those devices that light up some indicator when it's supported test it and chime in.
I'm using Moto Z transmitting to Cambridge BT100, and the LED on the Bluetooth dongle blinks every 2 seconds. That means apt-x is ON!
Looks like a few people found fixes to this, but unfortunately i am not one of them. I tried switching the AVRCP version to 1.3 which led to a successful connection and the phone connection to work. However, media still does not work. My car is a 2018 Toyota Camry XSE. iPhone connects with no issues. I'm a tad bit upset I bought a brand new car and new phone only having to resort to using an aux cord
Wondering if there are any lucky people out there who got their connection to work with any different methods?
I can use the phone for making calls, but Bluetooth audio doesn't work (Audi A4 B9 MMI+).
My workaround is using Android Auto for music playback, this at least works. But I hope Google will fix this...
BabelHuber said:
I can use the phone for making calls, but Bluetooth audio doesn't work (Audi A4 B9 MMI+).
My workaround is using Android Auto for music playback, this at least works. But I hope Google will fix this...
Click to expand...
Click to collapse
Same here. Unfortunately, Toyota doesn't support Android Auto...I believe android 8.1 is supposed to be released today so maybe moving off of beta into that will work
So you can't play music over bluetooth to your car? That sucks. Music over Bluetooth works fine for both of my cars. Wonder what the issue is
BabelHuber said:
I can use the phone for making calls, but Bluetooth audio doesn't work (Audi A4 B9 MMI+).
My workaround is using Android Auto for music playback, this at least works. But I hope Google will fix this...
Click to expand...
Click to collapse
I have an Audi S4 B8.5 MMI+ and I haven't had any issues with bluetooth connectivity for music or calls on any OS. The only concern I has is with Pandora the clock counter for the song didn't always register, but I thought that had more to do with the app as Spotify worked correctly.
Bluetooth works fine on my Jeep Cherokee 2017. However I don't get audio songs names , that was on 8.0 though. I will try tomorrow with 8.1 on.
Sent from my Pixel 2 XL using Tapatalk
Maybe the head unit needs a software update, those are available all the time. I know Toyota will just tell you that your phone isn't on the "list" of approved phones and that the issue is with you phone because it's got too new of an OS.
BabelHuber said:
I can use the phone for making calls, but Bluetooth audio doesn't work (Audi A4 B9 MMI+).
My workaround is using Android Auto for music playback, this at least works. But I hope Google will fix this...
Click to expand...
Click to collapse
Works fine on my B9 S4.
Sent from my Pixel 2 XL using Tapatalk
millerd79 said:
Works fine on my B9 S4.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Thanks! I'll be at my Audi dealer next week and will push for a software update ?
If Bluetooth headphones support both codecs the phone will always select AAC. I can go into developer options and change it to aptX but the next time I connect the headphones it changes back to AAC. Has anyone found a solution to this? I definitely prefer aptX quality.
Sent from my LM-G820 using Tapatalk
immerstark said:
If Bluetooth headphones support both codecs the phone will always select AAC. I can go into developer options and change it to aptX but the next time I connect the headphones it changes back to AAC. Has anyone found a solution to this? I definitely prefer aptX quality.
Sent from my LM-G820 using Tapatalk
Click to expand...
Click to collapse
You're doing it wrong. Going in dev options is not the sollution.
You must do this:
After you paired the headphones to Bluetooth, go into Bluetooth settings for the headphones and enable priority to sound quality. Long press bluetooth icon when the headphones are connected, then click on the settings icon of the headphones and select priority to sound quality.
I was told that if you add _NOAAC to the bluetooth device name,
it will select the next available best codec, which should be aptX.
It didn't work for me, but worth a try.
Inerent said:
You're doing it wrong. Going in dev options is not the sollution.
You must do this:
After you paired the headphones to Bluetooth, go into Bluetooth settings for the headphones and enable priority to sound quality. Long press bluetooth icon when the headphones are connected, then click on the settings icon of the headphones and select priority to sound quality.
Click to expand...
Click to collapse
The only settings available for my headset are toggles to enable or disable call audio and media audio. Are you giving instructions that work on a pure version of Android like a Pixel or Nexus device would have?
Sent from my LM-G820 using Tapatalk
Here
If you don't have it, then headphones are cheap...
LDAC for example
Inerent said:
LDAC for example
Click to expand...
Click to collapse
Mmmkay, yours are using Sony's proprietary codec. The issue arises when headphones support both AAC and aptX. I have a speaker that only supports SBC and aptX HD and I'm able to select between quality or stability.
Sent from my LM-G820 using Tapatalk
This is the solution!
lentm said:
I was told that if you add _NOAAC to the bluetooth device name,
it will select the next available best codec, which should be aptX.
It didn't work for me, but worth a try.
Click to expand...
Click to collapse
This absolutely does work provided your device actually has aptX. I have a photo but can't post external links yet, so as an example, Fugoo XL was the name of the Bluetooth device, I changed it by only adding _NOAAC to the end of the name. Now it says Fugoo XL_NOAAC and it is coming up aptX in Developer menu every single time without any intervention, just observation. I've done it to all the devices that have defaulted to AAC that support aptX, and it's like it was never an issue to begin with. Using an LG G8X ThinQ. Was my only gripe with the device and now it's over.
nerdydaddyo said:
This absolutely does work provided your device actually has aptX. I have a photo but can't post external links yet, so as an example, Fugoo XL was the name of the Bluetooth device, I changed it by only adding _NOACC to the end of the name. Now it says Fugoo XL_NOAAC and it is coming up aptX in Developer menu every single time without any intervention, just observation. I've done it to all the devices that have defaulted to AAC that support aptX, and it's like it was never an issue to begin with. Using an LG G8X ThinQ. Was my only gripe with the device and now it's over.
Click to expand...
Click to collapse
A thousand thanks. It does work!!!!!! [emoji16]
Sent from my LM-G820 using Tapatalk
nerdydaddyo said:
This absolutely does work provided your device actually has aptX. I have a photo but can't post external links yet, so as an example, Fugoo XL was the name of the Bluetooth device, I changed it by only adding _NOAAC to the end of the name. Now it says Fugoo XL_NOAAC and it is coming up aptX in Developer menu every single time without any intervention, just observation. I've done it to all the devices that have defaulted to AAC that support aptX, and it's like it was never an issue to begin with. Using an LG G8X ThinQ. Was my only gripe with the device and now it's over.
Click to expand...
Click to collapse
immerstark said:
A thousand thanks. It does work!!!!!! [emoji16]
Sent from my LM-G820 using Tapatalk
Click to expand...
Click to collapse
I'm glad that it works for you guys although it doesn't work on my Sprint LG G8. :silly:
I have the unlocked Amazon version, which incidentally doesn't have the Google Assistant button at all.
Sent from my LM-V450 using Tapatalk
lentm said:
I was told that if you add _NOAAC to the bluetooth device name,
it will select the next available best codec, which should be aptX.
It didn't work for me, but worth a try.
Click to expand...
Click to collapse
Confirming this works on my AT&T LG-G8 with wireless earbuds that supports the codec set {SBC,AAC,AptX}. A huge fix to an annoying problem I've had with these headphones; thanks!
Bizarrely this works on my Boost Mobile Samsung Galaxy S8+, so I'm thinking it's baked into Android. Also work on my Sprint LG V50.
Sent from my LM-G820 using Tapatalk
It boggles my mind that a phone that lives on it's audio quality would fail this miserably at bluetooth.
---------- Post added at 05:22 PM ---------- Previous post was at 05:16 PM ----------
nerdydaddyo said:
This absolutely does work provided your device actually has aptX. I have a photo but can't post external links yet, so as an example, Fugoo XL was the name of the Bluetooth device, I changed it by only adding _NOAAC to the end of the name. Now it says Fugoo XL_NOAAC and it is coming up aptX in Developer menu every single time without any intervention, just observation. I've done it to all the devices that have defaulted to AAC that support aptX, and it's like it was never an issue to begin with. Using an LG G8X ThinQ. Was my only gripe with the device and now it's over.
Click to expand...
Click to collapse
I've tried this and it is still defaulting to AAC in the developer options
it works
lentm said:
I was told that if you add _NOAAC to the bluetooth device name,
it will select the next available best codec, which should be aptX.
It didn't work for me, but worth a try.
Click to expand...
Click to collapse
It works on my of g7 thinq Italian version and my cheap but fabulous soundcore life p2 twrue wireless buds supporting aac and aptx.
Thank you a lot.... also more!
Such a supremely elegant solution - can't believe this is the only thread I can find about this. Now, if only I could find out how to get my WH-1000XM3's to connect via AptX HD by default instad of LDAC, I'll be laughing!
_NOLDAC?
Sent from my LM-G820 using Tapatalk
Good news here, I updated my Sprint LG G8 to Android 10 (20a) that was leaked recently, and tested _NOAAC method that didn't work on Pie, finally works now.
Works on LG Velvet
nerdydaddyo said:
This absolutely does work provided your device actually has aptX. I have a photo but can't post external links yet, so as an example, Fugoo XL was the name of the Bluetooth device, I changed it by only adding _NOAAC to the end of the name. Now it says Fugoo XL_NOAAC and it is coming up aptX in Developer menu every single time without any intervention, just observation. I've done it to all the devices that have defaulted to AAC that support aptX, and it's like it was never an issue to begin with. Using an LG G8X ThinQ. Was my only gripe with the device and now it's over.
Click to expand...
Click to collapse
Had the same problem with my Sennheiser CX 400BT (has AAC and aptX codecs) and my LG Velvet 5G (has multiple codecs). Changed the codec from AAC to aptX in Developer Options. Powered off my earbuds and powered them back on and LG would default codec to AAC. Did exactly what you said by changing bluetooth name from 'CX 400BT TW' to 'CX 4000BT TW_NOAAC' and codec on Velvet stays on aptX and no longer defaults back to AAC. It works.
Fantastic! Thank you so much. Searched for a solution for a couple of hours.
My G8 thin Q works with an aptx HD headset after I added _NOAAC so thanks for this suggestion.
I see that in the Bluetooth configuration screen for the headset, there is indeed a setting to switch to highest quality (as opposed best connection, which seems to be the default). Changing that may fix the problem, if the name change by itself doesn't work.
hi guys, I have the pixel experience 13 rom on redmi note 8 pro and I have a hearing aid that only works in videos, music, etc. but not in calls, is there any way to fix it? I read about magisk module, I'm not an expert, maybe tell me a solution, I need it
Here too, same problem. Is there some additional info?
lucarenna01 said:
hi guys, I have the pixel experience 13 rom on redmi note 8 pro and I have a hearing aid that only works in videos, music, etc. but not in calls, is there any way to fix it? I read about magisk module, I'm not an expert, maybe tell me a solution, I need it
Click to expand...
Click to collapse
So far I found out that Pixel extendet and evolution X custom rom for veux DO somehow support asha for hearing aids. Unfortunatly the call function is NOT working. Both roms do playback via asha connected hearing aids and on both roms whatsapp calls via hearing aids are possible.