Database Develop

Pioneer Next 4100

So my radio came in today and android auto doesn't work. It says my phone was not compatible. I have a rooted note 4 running android 5.0.2 (cm 12). I also used my fiancée sg5 with the new stock 5.0 and it still doesn't work! Anybody care to help?

Anybody?

Did you try calling pioneer?

I'm having the same issue. I have a rooted T-Mobile LG G3 running 5.0.

I thought I was the only one

smalltownbird said:
Did you try calling pioneer?
Click to expand...
Click to collapse
Close on the weekend

There are YouTube videos of car audio installers using it so it has to work

Same here, I have an HTC One M8 rooted and its not working for me either. I read the manual and apparently you need a CD-MU200 interface cable from pioneer. Don't know if that's bulls**t or not, but we'll find out. I have the USB setup so that I can use the built-in port in my car. I don't know if that's what the reason is or not. I'll have to call pioneer on Monday.
Sent from my HTC One_M8 using Tapatalk

Well that's three people with the same problem

I think you need the Google apps loaded for one thing, and having an account enabled may be even better.
Lollipop is essential at this time, and I think 5.1 is even better.
Nexus also has a better chance of working.
I am trying to get developer mode working and I am mainly using my Nexus 7 2012 w/ 5.1 because my 2013 N7 and N9 both are still on 5.0.

But its just about api21 that AA runs on. 5.1 has api22 and its confirmed AA is working on "normal" lollipop, I mean 5.0.x

I'm running 5.0.1 on my M8 and Android Auto isn't working
Sent from my HTC One_M8 using Tapatalk

Also it's important to have latest GMS installed.
http://www.apkmirror.com/apk/google-inc/google-play-services/
Check version you need, download it and install. I can bet all of you have old versions (as I was surprised some time ago that it's not updating and I was stuck on 6.x when for months there was 7.x available)

brainscollector said:
Also it's important to have latest GMS installed]
Check version you need, download it and install. I can bet all of you have old versions (as I was surprised some time ago that it's not updating and I was stuck on 6.x when for months there was 7.x available)
Click to expand...
Click to collapse
Thanks for the help. Unfortunately it didn't work for me. I went on the reviews for android auto app on Google play and it seems a lot of other people are having the same issue.

Theres a new update on pioneer site, but didn't fix problem.

Maybe
You can generally find the Android Auto button located on the home screen of your car's digital display. How to navigate to the home screen will vary by manufacturer, so check your car's user guide.
I plugged in my phone, found the Android Auto button, but it won't open.
If this is the first time you’re using Android Auto in a particular car, be sure to unlock your phone and accept the terms and conditions on your phone’s screen after you’ve connected and touched the Android Auto button on your display.
Also, make sure that the "Only connect to known cars" setting in the Android Auto app is unchecked.
The voice command button takes me out of Android Auto.
My USB cable isn't working.
Not all USB cables will work with all cars. Your car's user guide should have information about the best USB cable to connect your phone to the display.
Click to expand...
Click to collapse
https://support.google.com/androidauto/

killa2009 said:
Theres a new update on pioneer site, but didn't fix problem.
Click to expand...
Click to collapse
Update for what ? Pioneer firmware ? Can you link ?

mikereidis said:
Update for what ? Pioneer firmware ? Can you link ?
Click to expand...
Click to collapse
Pioneer nex 4100 radio

mikereidis said:
Update for what ? Pioneer firmware ? Can you link ?
Click to expand...
Click to collapse
http://www.pioneerelectronics.com/S...tibility/15MY_FW-Update_v1.03_4G_20150318.zip
http://www.pioneerelectronics.com/PUSA/Car/NEX/AVH-4100NEX
funny that it has tomorrows release date today ^^

brainscollector said:
http://www.pioneerelectronics.com/S...tibility/15MY_FW-Update_v1.03_4G_20150318.zip
http://www.pioneerelectronics.com/PUSA/Car/NEX/AVH-4100NEX
funny that it has tomorrows release date today ^^
Click to expand...
Click to collapse
Yup, I still updated but no change.

No notification sound through bluetooth??

Hi,
My phone is the D5803 z3c and after staying up late trying to understand rooting the phone I think I got it all together. However, I downloaded a bunch of images so honestly I don't even know what rom i'm running. It's a basic pre-rooted/debloated rom from the 1st page of the development section.
Anyway, I use a bluetooth headset at work. I am a limo driver and my rides are dispatched via text. My bluetooth headset works fine, except it will not play the notification sound for texts, only the ringtone when a phone call comes in. The media/phone box is checked. I can play youtube videos and sound comes through, but for some reason the notify doesn't work.
This is important to me, sometimes I leave my phone on the seat and can't hear it due to the music or whatever, but with my Nexus 5 I just came from, it worked right out of the box .
I've tried searching, and didn't come up with much. I also tried playing around with some apps, and I think for a little bit I used an app that seemed to do the trick, but now it doesn't work anymore.
ANY IDEAS???
Note: I have 2 bluetooth headsets, same thing on both. On my Nexus 5 both worked fine.

Nurmi_CEO said:
Hi,
My phone is the D5803 z3c and after staying up late trying to understand rooting the phone I think I got it all together. However, I downloaded a bunch of images so honestly I don't even know what rom i'm running. It's a basic pre-rooted/debloated rom from the 1st page of the development section.
Anyway, I use a bluetooth headset at work. I am a limo driver and my rides are dispatched via text. My bluetooth headset works fine, except it will not play the notification sound for texts, only the ringtone when a phone call comes in. The media/phone box is checked. I can play youtube videos and sound comes through, but for some reason the notify doesn't work.
This is important to me, sometimes I leave my phone on the seat and can't hear it due to the music or whatever, but with my Nexus 5 I just came from, it worked right out of the box .
I've tried searching, and didn't come up with much. I also tried playing around with some apps, and I think for a little bit I used an app that seemed to do the trick, but now it doesn't work anymore.
ANY IDEAS???
Note: I have 2 bluetooth headsets, same thing on both. On my Nexus 5 both worked fine.
Click to expand...
Click to collapse
Okay, I just thought I had this problem... here the same, after the latest update to 5.1.1.
I'm try with 2 bluetooth headsets (Plantronics - Jabra) and a full factory reset but no notifications for text messages (sms, chat, whatsapp ect ect ect)
Italian Sony Xperia Z3C (Vodafone) Android 5.1.1 - 23.4.A.1.200

I found a thread on another forum of someone complaining about the same thing. He had a xperia z1. Supposedly Sony support emailed him and said xperias do not support this feature?? This doesn't seem like a complicated feature.
I should note my rom that I loaded is 5.1.1. qmaxmobile, did you have 4.4.4 on your phone and it worked? I'm willing to downgrade to 4.4.4 to get this feature to work, although I am happy with my 5.1.1 setup now.
I'm willing to pay a bounty if someone can create a mod so I can have this feature!

Nurmi_CEO said:
I found a thread on another forum of someone complaining about the same thing. He had a xperia z1. Supposedly Sony support emailed him and said xperias do not support this feature?? This doesn't seem like a complicated feature.
I should note my rom that I loaded is 5.1.1. qmaxmobile, did you have 4.4.4 on your phone and it worked? I'm willing to downgrade to 4.4.4 to get this feature to work, although I am happy with my 5.1.1 setup now.
I'm willing to pay a bounty if someone can create a mod so I can have this feature!
Click to expand...
Click to collapse
With Lollypop 5.0.2 all works....maybe tomorrow try to update at latest Android 5.1.1 - 23.4.A.1.232

qmaxmobile said:
With Lollypop 5.0.2 all works....maybe tomorrow try to update at latest Android 5.1.1 - 23.4.A.1.232
Click to expand...
Click to collapse
I'm confused. You have 5.0.2 and the notifications work? I have the latest Android 5.1.1 loaded and it doesn't work. I'm pretty sure I had 5.1.1 on my Nexus 5 and it worked fine.

Nurmi_CEO said:
I'm confused. You have 5.0.2 and the notifications work? I have the latest Android 5.1.1 loaded and it doesn't work. I'm pretty sure I had 5.1.1 on my Nexus 5 and it worked fine.
Click to expand...
Click to collapse
Yes my Sony with 5.0.2 sms notification on bt works, all works....after latest update to 5.1.1...don't

qmaxmobile said:
Yes my Sony with 5.0.2 sms notification on bt works, all works....after latest update to 5.1.1...don't
Click to expand...
Click to collapse
Well I decided to flash a 4.4.4 ROM because the battery life is supposedly better (althought my 5.1.1 had great battery life, almost 7 hr SOT). However same thing, no notification through bluetooth.
qmaxmobile, what rom were you running on 5.0.2 to have notifications play through through bluetooth? I only found one 5.0.2 rom and I couldn't get it to boot, and seems like others in the thread had the same problem.
I really need bluetooth notifications. Seems like a simple app would do the trick, but haven't found much except a thread on a forum saying Xperia phones don't support it.

So I posted on the Sony Xperia forum, and a sony rep confirmed that Sony firmware does not support this feature (why????). I tried high and low to find an app in the play store to get it to work, but no dice.
Supposedly the rep also said that if you get a Sony bluetooth headset you can get the sony app to control that feature. I'm not so sure....
If anyone can confirm a sony bluetooth headset will in fact work with stock xperia firmware, please post!
The only option I was able to think of was to unlock the bootloader and flash a custom rom. I just did that and it worked. My DRM keys are backed up in case I decide to relock. So now I'm running Ressurrection Remix rom. It's a shame, as I didn't mind the Sony interface.

Well, I did unlock the bootloader and loaded a custom version of android. It worked. But I went back to the Sony firmware because battery life was better.
I picked up a Sony bluetooth MBH20 headset, and you guessed it, still doesn't work.
There HAS to be a way! $25 if you create a simple app that makes this work for me!

Nurmi_CEO said:
Well, I did unlock the bootloader and loaded a custom version of android. It worked. But I went back to the Sony firmware because battery life was better.
I picked up a Sony bluetooth MBH20 headset, and you guessed it, still doesn't work.
There HAS to be a way! $25 if you create a simple app that makes this work for me!
Click to expand...
Click to collapse
Well, I don't know about you, but notifications go out when using Bluetooth for me on the latest Sony stock room.
You may try the apps SoundAbout, or Mono Bluetooth Router, though.

That's so weird. No idea how it works for you. I found a few threads on other forums complaining about the same thing. I even posted on the Sony forum and support said I need a Sony app and a Sony headset because this "feature" isn't supported.
I did monkey with SoundAbout, no luck. There are so many options, and I didn't see a specific one for this feature.

Cataclysm ROM: Skype stuttering when running in background

Title says it all. This is a fresh, "stock" install of Cataclysm 6.0r1 on an XT1103 with no tweaks or kernel replacements or anything else. Skype works great but the receive audio stutters any time Skype is not running as the foreground app (transmit audio remains unaffected). Locking the phone makes no difference. Speaker vs Bluetooth makes no difference. Any ideas?
(posted here because my account is too new to post on the Cataclysm dev thread).

Same issue with a oneplus one and Cyanogenmod 13.
Did you found a solution yet?

The problem is still here, but is related to gapps on Marshmallow.
Oneplus One running sultanxda's cm13, tried reflashing without gapps and the problem disappeared but I need them so I think I'll wait for Android N so the problem will be fixed then I guess.

Bluetooth Metadata issues after Nougat Upgrade

Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!

aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.

zelendel said:
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.
Click to expand...
Click to collapse
Appreciate the feedback, thanks!
Yup... Definitely understand that iOS and Android are 2 complete different bases...I tested with the iPhone to make sure that the aftermarket Bluetooth receiver in the car was not the problem.
I do believe it's something that Google has changed and I'm starting to realize that the only option I may have is to wait and see.
One point I want to add is that the Nougat update did not break anything when it comes to connecting to my wife's Acura with built in Bluetooth. The track info continues to work fine..
I was hoping someone with more in depth knowledge of the Android systems maybe be able to chime in on what could have changed...I know the 3rd party apps i use have gone through multiple updates since Nougat came out so if they were gonna update something due to compatibility with Nougat, it would've happened already.

aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.

Syndrome666 said:
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.
Click to expand...
Click to collapse
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!

aerohp said:
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!
Click to expand...
Click to collapse
Happy to help. No my Si doesn't have the navigation option, I just use my Shamu for that. I've finally got the attention of AICP moderator and developer at AICP G+ community, so it's looking like the Bluetooth metadata issue is a CM/LOS issue so far, they're going to look into it. I captured a logcat and pictures which are posted there under bugs+logcat. It's under AICP G+ community if you want to look at it, posted under my main Google account as Andrey K, you can check it out here: https://plus.google.com/112643646080294190790/posts/4FRbAonGT55.
As for you never hearing about SIX ROM, that's because the dev doesn't participate on XDA forums. It's a really stable nougat ROM all around, and now supports phh's root, which if paired with Magisk app, allows to hide root access from apps like Android pay and Pokemon go.
The most a manufacturer would offer is to replace the device, possibly for a fee, that won't solve your problem. Most nougat ROMs are currently experiencing this bug. Cyanide, SIX, and Pure Nexus do not have this problem, at least not on Shamu.

anyone ever come across a fix for this?

nerdyone255 said:
anyone ever come across a fix for this?
Click to expand...
Click to collapse
Nah, still struggling with it...I keep hoping that a new Android update will fix it but so far no luck. It used to work fine for me in Lollipop but nothing since I've upgraded to Nougat. I'm on Nexus 6. Wife has a pixel XL and had the same issue when she was on Nougat so it's not the phone. She did get the Oreo update this week so I'll try again to see if it works. If not, then this must be a compatibility issue that the adapter manufacturer may need to look at...
The annoying thing is that the metadata transfer is fine when using my work iPhone. But I hate the iPhone/Apple so I only touch that thing when I absolutely have to (work calls, work emails, etc)

Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)

Bluetooth Phone Calls Don't Work

I've heard this a bug with Oreo, but I've had this issue since Nougat. Essentially, I've tried connecting several Bluetooth devices to my OnePlus 3T with OOS 5.0.3 rooted w/ Magisk, and while I can get music and notifications to play, I can neither hear nor speak through the phone options using Bluetooth. I've searched for hours on Google as to why this may be happened, and while there are hundreds of reports and instances of this happening, there isn't a single consistent solution.
I've tried messing with the settings, codecs, deleting cache, deleting data from Bluetooth, repairing devices, deactivating Google Now, resetting the phone, you name it.
Is this a problem that is still prevalent with Oreo? This is probably the stupidest unsolvable thing I've ever encountered, and I'm convinced its software related, given that music and all other audio works.

Never had such issue with Nougat or Oreo.
Where did you read about such standard bug at Oreo?
Unleashed by my rooted OP3T on 8.0

RASTAVIPER said:
Never had such issue with Nougat or Oreo.
Where did you read about such standard bug at Oreo?
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
https://www.zdnet.com/article/andro...-looking-into-buggy-bluetooth-audio-problems/
https://forums.oneplus.com/threads/bluetooth-mic-not-working-on-phone-calls.805719/
https://www.reddit.com/r/oneplus/comments/7zz7fc/oneplus_55t_callers_cant_hear_me_solution/
https://forums.oneplus.com/threads/...all-whether-i-m-calling-or-vice-versa.731333/

smo69 said:
https://www.zdnet.com/article/andro...-looking-into-buggy-bluetooth-audio-problems/
https://forums.oneplus.com/threads/bluetooth-mic-not-working-on-phone-calls.805719/
https://www.reddit.com/r/oneplus/comments/7zz7fc/oneplus_55t_callers_cant_hear_me_solution/
https://forums.oneplus.com/threads/...all-whether-i-m-calling-or-vice-versa.731333/
Click to expand...
Click to collapse
Of those links, only the last one is relevant to the 3T.
What specific Bluetooth devices do you have the problem with?
I've use the phone feature with 3 different headsets, my car head unit, and a BT speaker, all with no issues with calls.

I have a problem with every Bluetooth device that uses phone features. This includes a Gear S3, Car Dongle and ear phones.

I have tried 2 BT SPEAKERS, 2 BT headset,.1 smart band and 1 smartwatch (moto 360).
No issues at all
Unleashed by my rooted OP3T on 8.0

I must have some kind of app causing the problem. I'm just not even sure which app it could possibly be.

smo69 said:
I must have some kind of app causing the problem. I'm just not even sure which app it could possibly be.
Click to expand...
Click to collapse
Any Magisk modules being used? I haven't seen this Bluetooth issue specifically (from Magisk modules) but they can sometimes cause random bugs, and it is a good enough place to start as any.
I think the Samsung gear watches in general, do not play well with a lot of non-Sammy phones. At least from other threads I've seen around. But it is suspicious that you are having the issue on multiple Bluetooth devices (although you don't name the other brands). So I think you are on the right track, that it may be an app or something else peculiar to your device setup.
I've had the phone functions work just fine with Motorola, Plantronics, JBL headsets, JBL speaker, Subaru head unit (Kenwood made stereo, from what I understand).

smo69 said:
I've heard this a bug with Oreo, but I've had this issue since Nougat. Essentially, I've tried connecting several Bluetooth devices to my OnePlus 3T with OOS 5.0.3 rooted w/ Magisk, and while I can get music and notifications to play, I can neither hear nor speak through the phone options using Bluetooth. I've searched for hours on Google as to why this may be happened, and while there are hundreds of reports and instances of this happening, there isn't a single consistent solution.
I've tried messing with the settings, codecs, deleting cache, deleting data from Bluetooth, repairing devices, deactivating Google Now, resetting the phone, you name it.
Is this a problem that is still prevalent with Oreo? This is probably the stupidest unsolvable thing I've ever encountered, and I'm convinced its software related, given that music and all other audio works.
Click to expand...
Click to collapse
I have the exact same issue. I've tried nougat/oreo.....official OOS....different roms also. Clean flashed the 3T but no luck.
Media audio works perfectly fine. As soon as somebody calls and I answer, the line becomes mute to whatever it is connected to. I've tried both with my car and BT speaker.
I then have to route the call to the ear pierce on the phone to be able to continue with the call.
Everyone I have found with this issue have sent their phones back for repairs.

OnePlus 3Ts seem to face an issue where if you're in a voice call using your SIM card, and also connected to some Bluetooth device at the same time, the WiFi seems to just s**t itself. It can't give more than 0.10 Mbps ever. It left me confused for a long time until I figured it was due to me calling on my Bluetooth headset/speaker. Truly annoying imo.

I finally figured it out. As I stated earlier, I was sure it was software based because music worked just fine, so I was looking for a culprit app that might have been hogging the phone audio/mic. Oddly enough, it was the T-Mobile Visual Voicemail app. I went ahead an uninstalled it. That app was not worth being unable to use Bluetooth hands-free in my car.

I take that back. Suddenly, it's not working anymore, so I'm more inclined to believe there's something wrong with the phone speaker/mic suddenly hanging with apps other than the actual phone app. The Visual Voicemail app only exposed that there was an issue with this, but the app itself did not seem to be the problem.

Same problem here, I am on Oreo (final beta). Have you managed to find a solution?

DIOmenik said:
Same problem here, I am on Oreo (final beta). Have you managed to find a solution?
Click to expand...
Click to collapse
Just saying.
When was the last time that you had a factory reset?
Sent from my ONEPLUS A3003 using Tapatalk

RASTAVIPER said:
Just saying.
When was the last time that you had a factory reset?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
A few months ago, when moving back from Oreo to Nougat for battery problems.
If you can confirm that on the last (stable?) Oreo release you are not facing this issue, I would really appreciate it and proceed with a factory reset.

DIOmenik said:
A few months ago, when moving back from Oreo to Nougat for battery problems.
If you can confirm that on the last (stable?) Oreo release you are not facing this issue, I would really appreciate it and proceed with a factory reset.
Click to expand...
Click to collapse
I am not at any stable version.
And have tried many different bt sets.
Also never had battery problems at Oreo
Sent from my ONEPLUS A3003 using Tapatalk

DIOmenik said:
A few months ago, when moving back from Oreo to Nougat for battery problems.
If you can confirm that on the last (stable?) Oreo release you are not facing this issue, I would really appreciate it and proceed with a factory reset.
Click to expand...
Click to collapse
I'm on stable OOS 5.0.6 (and multiple/sequential stable OOS builds before that) and never had issues with BT calls, using a headset and my car stereo.

2020, OnePlus 3T rooted magisk, android Pie, same bluetooth problem.