Database Develop

Losing Bluetooth Connection

I have a weird problem with my Moto X 2014 (Pure Edition). It's randomly losing bluetooth connection in a background (basically any BT connection – to auto, smartwatch, etc.) but the phone itself says everything is fine (Bluetooth is on and devices are connected). But actual connection is not working: unable to play music via BT, unable to discover a new BT device, notifications not coming through to a smartwatch, etc. Bluetooth devices continue to show as connected even if I power them off, and when I turn them back on, they won't reconnect.
I meet this problem every 1-2 hours, sometimes even 10-20 minutes. The only way to fix this problem - to turn off BT and then turn it on again. Or keep Wi-Fi always off.
I tried to use another Moto X (2014, same software build version), to pair and unpair devices, to clean cache and even do a factory reset (with and without backup restoring) – the problem is still here. That's weird but this problem start appears 2-3 weeks ago, before everything was just fine.
Phone: Moto X 2014 Pure Edition @ T-Mobile, Lollipop 5.1 (TMO_Pure_5.1_LPE23.32-21.3_5_23.16.3.victara_tmo.tmo.en.US)
Devices: Pebble Time, Pebble Time Steel, Ford SYNC2, Moto Stream.
Things I tried that didn't help: deleting and re-pairing devices, deleting all old device profiles, clearing cache, reflash, factory reset, safe mode, flash CM12.

BT HCI Logs:
A disconnect at 1:28pm
dropbox.com/s/q3pka5egagq3e5g/01_btsnoop_hci.log?dl=0
A disconnect at at 3:09pm (or so)
dropbox.com/s/f2kl4rowr12lypt/02_btsnoop_hci.log?dl=0

Same issue here with a VZW XT1096, since OTA to 5.1. Factory reset does not help.

Up

Same issue here, same device & carrier & software build version & Pebble Time Steel. As long as I'm constantly making use of a BT connection, it seems to stay alive just fine, but as soon as it sits idle for more than a couple minutes, the connection drops (according to the BT device, but not according to the phone). I've tried all the same things with the same total lack of success. I have nothing new/helpful to offer, but at least you're not suffering alone.

That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.

Just to say I have the same problem with a Pebble Time Steel and my 2014 Moto X. Have e to disable BT and dependable BT to get phone to connect to Pebble to only be dropped a few minutes later from Pebble side.
Lyre

AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
I'm having the same problems and have also had it "go away" for extended periods of time only to reappear after a day or two. Mine will drop the BT connection even if I'm actively listening to audio over my headset.

Registered because I'm having the same issue. I'm running stock 5.1, no root. The connection to my Pebble Time Steel is very unreliable. The Bluetooth settings thinks it's still connected, the Pebble Time app on my phone thinks it's still connected, but my watch shows no connection and there's no communication to or from my watch. Sometimes it'll work for hours just fine and then drop, sometimes it'll only be a few minutes. It seems to be when the phone screen is off. Turning BT off and on always fixes it, it'll immediately automatically reconnect and show it on the watch.
I've tried the Pebble troubleshooting online (factory reset & recovery mode on watch, uninstall Pebble Time app, forget pairing on all devices, remove all other BT apps, reboot phone, reinstall Pebble Time app, re-pair) but the problem remains.
In the past, I've had it where my Fitbit One seems to have dropped the connection. Since the sync is so infrequent, I don't notice it much but I did catch it where it hadn't synced in a few days. (That app was uninstalled while I try to figure the Pebble thing out)
Next step is factory reset on the phone, but it sounds like that's not a fix for some people. That, or design a watchface that sends a keep alive signal to the phone, which runs an app to reset the BT when the connection drops. Since it's still listed as connected, I don't think Tasker will fix it.

Same issue. My phone is a Verizon Moto X and I've tried factory reset. Hoping that whenever they update to 6 that it will fix the issue, but I'm ready to smash my Moto x over this

AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
While I hope your problem is "fixed" I would not be too hopeful. I have had this problem as long as I've had the phone. Sometimes it goes away for a while but it always returns. Right after I unlocked my bootloader and it did a complete factory reset the problem went away for a week but it eventually returned. I've seen similar problems reported with all the MX14 variations and nobody seems to have a solution. There was a thread on the Moto forums with folks reporting these issues to Moto but nothing ever came of it. Seems to be connected to wifi somehow because I don't seem to drop the BT connection if wifi is turned off. Not really a useful solution but it does seem to work. I just gave up and put a BT toggle button on my homescreen.

I had the same problem using marshmallow, I downgraded to 5.1 and it went to normal

Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?

jimbo0914 said:
Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?
Click to expand...
Click to collapse
Update: I changed over to Android M on CM13 and no longer have this issue. Nice not to have to power toggle the BT function a couple times a day anymore.
YMMV

Met the same problem after updating to Android M.
I often connect to BT during driving and after a few days working normally, my headset will be disconnect without any "notification".
My solution is to wipe cache, after that BT connection will work well for another few days.
Never met this issue in Android L, but I just love M so much.
Looking for better solution / fix.

I found this thread while searching for some solution for my BT+Android Wear problems. I have them since circa february / march 2017.
But today, I got a problem with non-Wear watch (Fossil Q Grant). I noticed my phone was locked even if I have smart lock set up. I checked fossil q app, the watch was connected, it received notifications so far. But in the phone settings, in smart lock, all my devices vanished. I checked the BT setting and saw the same. All my paired devices disappeared! It happened after nothing more than a restart, after my fossil lost connection earlier today and did not want to reconnect. So I restarted the phone.
This happened to me the second time already, but first time I somehow did not pay attention because I was frustrated by the Wear app problems and weekly factory resets to get my Wear watches working.
Could our issues be related? Some bluetooth software bug in phone? THIS IS PURE HELL!
Moto X4 cant come soon enough.

Phone keeps forgetting Bluetooth pairs.

My Nexus 6 keeps forgetting my Bluetooth pairs. I'll wake up and notice that my pairs are gone. Which is an annoyance with my car and Android Wear watch. It happened once before but then when it happened last night I know there is an issue. It started after I upgraded to Marshmallow. I'm running the MRA58R build. Any ideas?

I have the same issue...ever since marshmallow...both 6.0.0 official and 6.0.1 official, both times before installs the phone was wiped...but never the less it always forgets my bluetooth pairs
it seems to correlate to when the phone fully dies. If the phone fully dies 1-2 out of 5 times it will boot back up without the bluetooth pairings.
Also if I don't pair my Wear watch(original 360) this does not seem to happen either

I'm having this issue as well. My phone will randomly ask to pair with my car, even though it's been paired already. And sometimes it will just ask me to allow it to share Messaging, which was also already set. It's frustrating. I've only noticed it with Marshmallow.
For me it doesn't seem to correlate with charge level.

Having the same problem here and now that you mention it, it does seem to happen when it fully dies. Until someone comes up with a solution I'm going to see about backing them up and restore if it happens again.

Allowing your phone to completely die is a bad idea. The sudden shut down is what is corrupting it.
Also restoring that type of system data is just asking for other random issues, also not a great idea.
While I run an AOSP based rom I have never had my device forget any of my 5 BT pairings.

I agree don't let phone die.
Also if low battery plays a role (before phone dies), it could be related to battery saver features that can activate at low batteries level. (Adjustable in settings)
For the android wear app, turn off battery optimization (to prevent it from being interrupted by doze. )
I have had zero disconnection between my n6 and my moto 360 g1 android wear watch in the last month.

I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.

Blown 89 said:
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Click to expand...
Click to collapse
My phone has done this now twice in three days on N Preview 3. Has anyone found a solution?

mine does it too. but it will forget ALL my paired devices. it's pretty annoying

This is happening to me as well. Nexus 6 is forgetting all paired bluetooth devices.
Most annoying is the Android Wear issue because I've been having to factory reset the watch to get it to pair again. Some of this might be the watch because I'm running a Samsung Gear 2 with Android Wear but I also have several other devices that I have to repair every time.
Also seems to correlate with the battery dying.

There has to be a common bug. As all my devices have no issue remembering the pairing. Mind you I also dont pair to my car.
Also keep in mind that it was found long ago that OEM put in lists of cars that it will not work with in their roms. We found it on samsung devices years ago where it would block all connections to BMW, Audi and a few others.

N6 running 6.0.1 (no root)
This just started happening to me yesterday but has happened twice so far in two days. My phone has not died as seems to be a symptom for others here. It did get below 10% today but I charged it up without issue. it wasn't until several hours later that it wiped all of its paired devices. below is a list of my paired devices:
Samsung ATIV book 8 (windows 10)
UE Mobile BoomBox
Moto360 2nd Gen
2014 Infiniti Q50
2015 Nissan Murano
After it wiped everything yesterday I re-paired the following:
Samsung ATIV book 8
Infiniti Q50
Moto 360
After the first wipe today I paired the watch and the car.
If anyone has any ideas I would be grateful. This is a GIANT PIA!

Does not look like there is a solution to this forthcoming... is there anyone with this problem that's recently updated to N? And has it gone away? I get this usually after a forced reboot... all bt settings gone. Totally a problem.

Any update on this. I think it started happening after I updated to 7 and then went back to 6 after having battery issues?
rkshack

Giant PIA
Blown 89 said:
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Click to expand...
Click to collapse
I have this same problem too. Running Android 6.0.1 on a Samsung Galaxy A5. I drive a lot for work, and need my phone paired to a JVC headunit (listed as JVC UNIT on my phone) in my van so I can take phone calls handsfree, and listen to podcasts. Every now and again, maybe once a day, with no rhyme or reason that I can discern, I get into the van and notice that my phone is not paired. It's a pain to have to pull over and re-pair the phone, and then set it up a a trusted bluetooth device again (so as to avoid entering my passcode whenever unlocking the screen).
- Definitely nothing to do with battery levels. My phone is normally fully charged and plugged in to a charger.
- I don't lose all paired devices, as my UE Boom 2 (not often used) is still listed as a paired device, whereas the JVC UNIT drops off fairly often.
Please could someone sort this issue out! It sounds like quite a few people are experiencing it.
thanks,
Phil

Phil in NZ said:
I have this same problem too. Running Android 6.0.1 on a Samsung Galaxy A5.
Click to expand...
Click to collapse
Not likely to get sorted for your phone in this N6 thread. [emoji6]

I am on Android 11 and it still happens to me, my car pairing is being forgotten from time to time. Happens to any of you?

Bluetooth Constantly Becoming Disabled

Within the last few weeks I have noticed that upon reset or simply after a period of time, my Bluetooth will either disconnect with my Moto 360 Sport or will become disabled altogether. If I restart my phone, the Bluetooth toggle in settings is always disabled.
Several users have been discussing this issue over in the PureNexus ROM forum, but we have not identified the culprit yet. Some who are experiencing it have Android Wear devices, but not all people do. Those who are experiencing it are on different ROMs, or different builds of the same ROM, leading me to believe that it is an app and not specific to a ROM. Also, for everyone who is experiencing it, it started withing the last few weeks.
I wanted to start a thread to allow people experiencing this issue to find a common cause so that we can correct it.
I'll also tag those who have said they are having this issue to lead them to this post: @Moguledyouth @uberbdon @MVLJR @ethanhunt123 @MysticKing32 @danman7 @hawkz28

I'm unsure which thread is the most appropriate to post this in, so I'll throw it here.
I don't believe the entire issue is tied to 7.1.1. I believe it originated in 7.1.0 or earlier, but got worse in 7.1.1. (Side note, I did on occasion get a "Bluetooth Share has stopped" notification, but only if I was actively using the phone).
My phone's bluetooth began "cycling" at the very latest in 7.1.0. I first noticed the issue when using an app called "wear aware," an app designed to let you know if you leave your phone behind (on your android wear watch). It was frequently giving me "false positives," so I ultimately uninstalled the app. I also began to have issues with android auto, where it would occasionally freeze and stop showing me data. Likewise, when I'd be on a phone call, my radio would randomly turn on and I'd assume the call got disconnected -- until I realized the other party was still on the line but now on speaker phone.
The reason I believe it got worse in 7.1.1 is because it used to cycle bluetooth. At least when it crashed, it restarted. Now it appears to require intervention to re-enable it. As a temporary work-around, I have Trigger set up to enable bluetooth if it gets disconnected from my watch. It doesn't work 100% of the time, but at least it re-enables bluetooth frequently for me (it claims to have run 10 times in the last 2 hours).
It's probably also worth noting that it's been reported on at least the Nexus 6 and the Pixel, from what I've seen.
My current setup:
PureNexus (1/21 release, rooted)
Franco Kernel
Huawei Watch
Prior to this, I was running Stock, unrooted, with the same issues.

Thanks for the workaround (Trigger) - like the speakerphone issue we are experiencing, it might not be an official fix but it works for now. It seems like the more updates we get, the more bugs we get. Seriously, 6.0.1 was about perfect, and I might flash back to that and add the additional Nougat features via xposed.

Post deleted

Finally getting some traction on this issue: Many users are experiencing random Bluetooth disconnects on the Pixel and Pixel XL

Fvolfrine said:
Finally getting some traction on this issue: Many users are experiencing random Bluetooth disconnects on the Pixel and Pixel XL
Click to expand...
Click to collapse
Anyone try to revert to an earlier dialer app or is it in the framework of the Feb patch?

I don't think it's the phone app. I get Bluetooth share disconnects with just a Pebble smartwatch.

As is stated in the second article, this issue is not related to the phone dialer app. I'll delete that post as it might cause some confusiom
Sent from my Nexus 6 using Tapatalk

I thought my phone was dying. I'm having this issue as well. I found that uninstalling Heart Trace, which records my heart rate every 15 minutes from my Huawei Watch, helped a lot with the Bluetooth issue.
It used to be that my Bluetooth would turn off in the middle of the night and I lose my sleep tracking data from my watch (Sleep as Android).

Don't google test their sofware?
This is a poor show by them.

Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data

semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
But how often do you have to keep doing this?

Fvolfrine said:
Within the last few weeks I have noticed that upon reset or simply after a period of time, my Bluetooth will either disconnect with my Moto 360 Sport or will become disabled altogether. If I restart my phone, the Bluetooth toggle in settings is always disabled.
Several users have been discussing this issue over in the PureNexus ROM forum, but we have not identified the culprit yet. Some who are experiencing it have Android Wear devices, but not all people do. Those who are experiencing it are on different ROMs, or different builds of the same ROM, leading me to believe that it is an app and not specific to a ROM. Also, for everyone who is experiencing it, it started withing the last few weeks.
I wanted to start a thread to allow people experiencing this issue to find a common cause so that we can correct it.
I'll also tag those who have said they are having this issue to lead them to this post: @Moguledyouth @uberbdon @MVLJR @ethanhunt123 @MysticKing32 @danman7 @hawkz28
Click to expand...
Click to collapse
I'd like to say that after (dirty) flashing the 2/15 update, my issue is resolved. When I reboot now, BT remains enabled.

danman7 said:
I'd like to say that after (dirty) flashing the 2/15 update, my issue is resolved. When I reboot now, BT remains enabled.
Click to expand...
Click to collapse
What is the 2/15 update?

@home said:
What is the 2/15 update?
Click to expand...
Click to collapse
PureNexus ROM. And I'm glad to hear that it resolved this issue, might be time to flashback over from stock.
On a side note, the one thing that I feel stock is missing, and this is minor, is a battery percentage that is not in the icon. Google has added just about everything I wanted to stock except for this one small detail, and yet I'm going to flash over because of it.
Sent from my Nexus 6 using Tapatalk

I'm on stock firmware and Project Fi on Nexus 6 and been having this problem lately yet I have had no updates since the Oct 5 2016 security update on Android v7.0. I wear a fitbit Charge 2 and occasionally use either a bluetooth headset or my car's bluetooth audio. I try real hard to keep my battery charge above 40% at all times. Normally I'm at 70% or higher when these problems occur. [edited to add] Forgot we also have a few Tiles and a LugLoc.
When not using bluetooth at all I frequently find bluetooth has disabled itself on my phone.
When using the bluetooth headset during a phone call bluetooth shuts off and my headset reports it has lost a connection to my phone.
In my car bluetooth is flawless and never shuts down even on long drives 2-4 hours.
I have also enabled trusted devices in Security when certain devices are connected via bluetooth.
Sometimes bluetooth settings loses a device. Sometimes they come back on their own but more often than not I have to repair the device to the phone.
Right now there are so many issues with this phone (including dust in the camera sensor) that makes it real frustrating as an owner.

@home said:
But how often do you have to keep doing this?
Click to expand...
Click to collapse
Only had to do it once

semsem_605 said:
Only had to do it once
Click to expand...
Click to collapse
I just did this about ten minutes ago and rebooted. Bluetooth turned back on after the boot, which is nice. Hopefully it stays on. Thanks for the tip!

semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
Fvolfrine said:
I just did this about ten minutes ago and rebooted. Bluetooth turned back on after the boot, which is nice. Hopefully it stays on. Thanks for the tip!
Click to expand...
Click to collapse
I tried this earlier today. Made it through two one hour conference calls with only one hiccup between the bluetooth headphones and the phone which did reconnect. No disabled bluetooth yet. I hope this is the fix!

semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
Are you on 7.0 or 7.1.1 & also which security patch?
Thanks

Microphone only works during calls

Good afternoon,
I have had a Nokia 8 for a few weeks now and have now found that my microphone only works during calls. While I'm on the phone everything works normally but in all other apps nothing happens, e.g. in Whatsapp you only hear a short crack when you hear a voice message and then nothing, although you have said something (see attachment), also other apps that use the microphone like the Google Home App or a guitar vocal app don't work. Of course the permissions are set correctly for all apps but apparently this has no effect (see attachment). I've already written with Nokia Support, but after 14 mails about permissions, emptying caches and doing softresets they couldn't help me. Finally I was told to wait for the next Android update and hope that my problem was fixed there, or I should send my phone back to the dealer. My hope now is that one of you has an idea what could be the cause of the problem.
Thank you for your time!
- Joeigel
Attachments:
picload.org/view/dclcpodg/screenshot_20181201-165257.png.html
picload.org/view/dclcpodr/screenshot_20181201-165237.png.html
Audio Message from Whatsapp:
instaud.io/30ZI

Hello to everyone there,
I have next problem on my Nokia 8:
When somebody calls me or when I call someone on viber, I turn on speakers and other side can't hear me. Also when I put it on video call the same issue conitnuous to take. Regular GSM calls or viber VoIp calls works great as well as video calls with headphones.
I open ticket to a viber about this problem, and they told me I need to contact my manufacturer.
Yesterday I installed an Android pie from beta labs, but the problem still exists. How do you think the problem is hardware?

ratola said:
Hello to everyone there,
I have next problem on my Nokia 8:
When somebody calls me or when I call someone on viber, I turn on speakers and other side can't hear me. Also when I put it on video call the same issue conitnuous to take. Regular GSM calls or viber VoIp calls works great as well as video calls with headphones.
I open ticket to a viber about this problem, and they told me I need to contact my manufacturer.
Yesterday I installed an Android pie from beta labs, but the problem still exists. How do you think the problem is hardware?
Click to expand...
Click to collapse
Hi ratola,
you can dial *#*#372733#*#* for a hidden FQC test menu, here you can test each mic seperated, i guess in your case it's the second mic in the top-speaker.
- Joeigel

Joeigel27 said:
Good afternoon,
I have had a Nokia 8 for a few weeks now and have now found that my microphone only works during calls. While I'm on the phone everything works normally but in all other apps nothing happens, e.g. in Whatsapp you only hear a short crack when you hear a voice message and then nothing, although you have said something (see attachment), also other apps that use the microphone like the Google Home App or a guitar vocal app don't work. Of course the permissions are set correctly for all apps but apparently this has no effect (see attachment). I've already written with Nokia Support, but after 14 mails about permissions, emptying caches and doing softresets they couldn't help me. Finally I was told to wait for the next Android update and hope that my problem was fixed there, or I should send my phone back to the dealer. My hope now is that one of you has an idea what could be the cause of the problem.
Thank you for your time!
- Joeigel
Attachments:
picload.org/view/dclcpodg/screenshot_20181201-165257.png.html
picload.org/view/dclcpodr/screenshot_20181201-165237.png.html
Audio Message from Whatsapp:
instaud.io/30ZI
Click to expand...
Click to collapse
Hi Joeigel, unfortunately I have the same issue (and story regarding contacting support). The only way I can make calls via for instance WhatsApp is by using a handfree headset, or setting it to speaker-mode.
Waiting for the Android 9 release, if this isn't fixed with it, I'll send it in for warranty.
I do have another issue with the phone, and that's when I unlock my phone using the fingerprint scanner, 1 out of 4 times or so, the phone enables split screenmode. Do you (or someone else here) have similar experiences. It's quite annoying.

Update: Installed Pie, and no improvement. Issues still persists. Returning the phone today.

Sorry for the late response, my phone is also on it's way back to GB...

Joeigel27 said:
Sorry for the late response, my phone is also on it's way back to GB...
Click to expand...
Click to collapse
Ok, just got an update from the repair-center, they replaced a part and it should work OK now. Curious to see what they did and if it's resolved. Have to wait until it's shipped back. But keep us also posted about your progress
Off-topic: another issue I sometimes experience is when I unlock my phone with fingerprint, it sometimes switches automatically to the split-screen mode. It happens quite often and it's a bit annoying. Did you experience something similar with your Nokia?

odyon said:
Ok, just got an update from the repair-center, they replaced a part and it should work OK now. Curious to see what they did and if it's resolved. Have to wait until it's shipped back. But keep us also posted about your progress
Off-topic: another issue I sometimes experience is when I unlock my phone with fingerprint, it sometimes switches automatically to the split-screen mode. It happens quite often and it's a bit annoying. Did you experience something similar with your Nokia?
Click to expand...
Click to collapse
I didn't experienced something like this. Did they send it back to you yet? Maybe they fixed both... ^^'

Microphone issue here too.
Internal mic on front facing camera is the culprit. I noticed a few weeks back that my 'ok google' hotwords were no longer working. This became a problem after I installed the december security patch. I rolled back to the november security patch and this did temporarily fix the issue, after I had gone through the initial setup of the phone, my 'ok google' hotwords worked, until i went to use the camera to see if the issue still existed... unfortunately it does. Contemplating rolling back to july to see if the issue is resolved, or trying to move forward and installing pie.

nagesco said:
Microphone issue here too.
Internal mic on front facing camera is the culprit. I noticed a few weeks back that my 'ok google' hotwords were no longer working. This became a problem after I installed the december security patch. I rolled back to the november security patch and this did temporarily fix the issue, after I had gone through the initial setup of the phone, my 'ok google' hotwords worked, until i went to use the camera to see if the issue still existed... unfortunately it does. Contemplating rolling back to july to see if the issue is resolved, or trying to move forward and installing pie.
Click to expand...
Click to collapse
Could any up or downgrade fix it?

Joeigel27 said:
Could any up or downgrade fix it?
Click to expand...
Click to collapse
I've tried going up or down, I have oreo and pie on each of my A/B partitions and it does nothing. When i downgraded to oreo it worked for awhile but updating the google app or some sort of background service broke it again. Its definately mic 3 that has a fault, it has background interference noise when i do the test, it also occurs when recording video with the front facing mic on camera, the problem with the mic never goes away, after up/downgrading, I can't say whether this is related since it works prior to updating. rolling back/disabling doesn't solve the problem for the apps. Microphone/earpiece holes are clean and undamaged.

nagesco said:
I've tried going up or down, I have oreo and pie on each of my A/B partitions and it does nothing. When i downgraded to oreo it worked for awhile but updating the google app or some sort of background service broke it again. Its definately mic 3 that has a fault, it has background interference noise when i do the test, it also occurs when recording video with the front facing mic on camera, the problem with the mic never goes away, after up/downgrading, I can't say whether this is related since it works prior to updating. rolling back/disabling doesn't solve the problem for the apps. Microphone/earpiece holes are clean and undamaged.
Click to expand...
Click to collapse
After further testing of this issue, the 'OK Google' issue is still present, if I want to ask google assistant 'ok google' the microphone barely picks up anything or even my question, practically screaming into the microphone is the only way to activate it, this matches with the results on my google activity, listening to my recordings of my queries shows evidence that the microphone sensitivity is way too low.
HOWEVER, when using google assistant by means of pressing the microphone and then asking the question, the result is clear and understandable and doesn't suffer from volume issues, I can't pinpoint if this is an issue with the Nokia specifically, it is not a problem with any other application that uses the microphone.

Having the same issue with Mic 3. It means I can't use it in speakerphone mode during calls or in Skype. It doesn't prevent me from using the Google assistant though.

My smartphone was sent in and repaired (complete motorboard replaced). During the time it was gone Android 9 came out, so I'm not sure if it was the repair or the software update.
But it works again without any problems
Kind regards
Joeigel

I can't believe how many issues I've encountered since Pie update

Hello all,
I have the 960U1 US Unlocked version of the Note 9 I've had since Day 1 release of last August. It's quite the powerhouse of a phone, and has everything of what you want in a smartphone. I was aggravated by how late the Pie update came, but I never expected how many issues came along with that changed the user experience since Oreo. After updating to Pie, I did a factory reset for a clean run but then I ran into these following issues:
Download, installing, and uninstalling apps from the Play store: I've tried to download apps, which get stuck at 99% or 100%, but then just hangs there to not install. Same thing with uninstalling. It'll say uninstall for an abnormally long time.
GPS issues: I travel frequently on weekends. Sometimes I would like to pull up my Google Maps timeline to review where I went and at what times. One weekend, I went out of town 3 hours away from home and yet my timeline showed me saying I stayed all day and night where my Home location is. Map guidance still worked, but it still showed me that my "current location" was still being at home.
Bluetooth Power indicator pop up: This is a recent issue I found that other Samsung users in other forums encountered as well. I have a Sony WI-1000x Bluetooth neckband that does extremely well for all the bells and whistles it does. I've noticed that after I factory reset again after experiencing the previous 2 issues to get them fixed, there is a pop up that keeps appearing every 10 or so seconds that tell me my headset is battery at 100%. I have found no way of disabling that, and I had to unpair/pair my headset as well as clear Bluetooth data in System App settings to try and get rid of it. Good thing it hasn't been doing that after several tries, but now there is another issue with BT.
Bluetooth notification sound output: I've noticed when my BT is connected, I don't hear notifications from my text messaging app, e-mail, Arlo, and social media apps. I've checked to see that my Sound settings are all up and running as it should be. Then I went to try and play a notification sound, and nothing came out of my phone speakers. It only played through the headset itself, and that's an annoyance as I don't wear them all the time in my ear unless I'm using it for phone calls or listening to media. It seems to be an Android Pie issue and I have yet to find a permanent solution as this wasn't an issue before on Oreo. The only workaround I've found is using the SmartThings Audio Output toolbar in the Notifications drop down and select to play Media from my device. The notification sounds work then, and I can still answer calls through my headset. But it's a dumb issue that I have to manually set this whenever I want to go back to listening media.
The Note 9 is a great phone despite the small shortcomings it had before the Pie update. Now it's after the Pie update, all these issues come up and I don't understand what happened in what Samsung did. I'm almost tempted in calling Samsung to ask if my phone just somehow became defective, but I don't want to have something done and they send me some refurbished model when I kept my phone in near mint condition. What are your guys' thoughts about the issues I've had and what solutions would you suggest?

GigaSPX said:
Hello all,
I have the 960U1 US Unlocked version of the Note 9 I've had since Day 1 release of last August. It's quite the powerhouse of a phone, and has everything of what you want in a smartphone. I was aggravated by how late the Pie update came, but I never expected how many issues came along with that changed the user experience since Oreo. After updating to Pie, I did a factory reset for a clean run but then I ran into these following issues:
Download, installing, and uninstalling apps from the Play store: I've tried to download apps, which get stuck at 99% or 100%, but then just hangs there to not install. Same thing with uninstalling. It'll say uninstall for an abnormally long time.
GPS issues: I travel frequently on weekends. Sometimes I would like to pull up my Google Maps timeline to review where I went and at what times. One weekend, I went out of town 3 hours away from home and yet my timeline showed me saying I stayed all day and night where my Home location is. Map guidance still worked, but it still showed me that my "current location" was still being at home.
Bluetooth Power indicator pop up: This is a recent issue I found that other Samsung users in other forums encountered as well. I have a Sony WI-1000x Bluetooth neckband that does extremely well for all the bells and whistles it does. I've noticed that after I factory reset again after experiencing the previous 2 issues to get them fixed, there is a pop up that keeps appearing every 10 or so seconds that tell me my headset is battery at 100%. I have found no way of disabling that, and I had to unpair/pair my headset as well as clear Bluetooth data in System App settings to try and get rid of it. Good thing it hasn't been doing that after several tries, but now there is another issue with BT.
Bluetooth notification sound output: I've noticed when my BT is connected, I don't hear notifications from my text messaging app, e-mail, Arlo, and social media apps. I've checked to see that my Sound settings are all up and running as it should be. Then I went to try and play a notification sound, and nothing came out of my phone speakers. It only played through the headset itself, and that's an annoyance as I don't wear them all the time in my ear unless I'm using it for phone calls or listening to media. It seems to be an Android Pie issue and I have yet to find a permanent solution as this wasn't an issue before on Oreo. The only workaround I've found is using the SmartThings Audio Output toolbar in the Notifications drop down and select to play Media from my device. The notification sounds work then, and I can still answer calls through my headset. But it's a dumb issue that I have to manually set this whenever I want to go back to listening media.
The Note 9 is a great phone despite the small shortcomings it had before the Pie update. Now it's after the Pie update, all these issues come up and I don't understand what happened in what Samsung did. I'm almost tempted in calling Samsung to ask if my phone just somehow became defective, but I don't want to have something done and they send me some refurbished model when I kept my phone in near mint condition. What are your guys' thoughts about the issues I've had and what solutions would you suggest?
Click to expand...
Click to collapse
I had issues with android pie sprint model. Ended up flashing android oreo back and no more issues. Theirs guides out their all u need to do is download the correct files and flash file ,real easy process just follow instructions. Do your research and ull be good

GigaSPX said:
...
I have the 960U1 US Unlocked version of the Note 9...
The Note 9 is a great phone despite the small shortcomings it had before the Pie update...
What are your guys' thoughts about the issues I've had and what solutions would you suggest?
Click to expand...
Click to collapse
timex300 said:
I had issues with android pie sprint model. Ended up flashing android oreo back and no more issues. Theirs guides out their all u need to do is download the correct files and flash file ,real easy process just follow instructions. Do your research and ull be good
Click to expand...
Click to collapse
Hey GigaSPX, noting you have a 960U1 US Unlocked, I've been working on this step-by-step for a 960U1:
Confirm These Steps to Downgrade US Unlocked SM-N960U1 from Pie to Oreo
If you decide to go this route, take a look and share your experience.

Thanks for the links and guide tips to downgrade to Oreo, but I enjoy One UI too much to give up on that user experience. I still have my Note 8 and I know it benefited significantly from the pie update to have it last all day unlike before on Oreo.

GigaSPX said:
Thanks for the links and guide tips to downgrade to Oreo, but I enjoy One UI too much to give up on that user experience. I still have my Note 8 and I know it benefited significantly from the pie update to have it last all day unlike before on Oreo.
Click to expand...
Click to collapse
You're welcome.
Good to know about your Pie experience on your Note 8.