Related
hi,
i recently got a gear s3 classic, wifi and bt edition.
whenever i want to make a call from the watch its just erasing the numbers and doing nothing. also when im trying to call a contact, it's freezin for a few seconds and after its doing nothing. when i receive a call i can just decline it but not accept it. my bluetooth seems proberly connected, im getting notifications and similiar thing, also the gear app says im connected. using it with a oneplus2 on RR, android 7.1.2.
i hope someone got fix for this.
iLucas said:
hi,
i recently got a gear s3 classic, wifi and bt edition.
whenever i want to make a call from the watch its just erasing the numbers and doing nothing. also when im trying to call a contact, it's freezin for a few seconds and after its doing nothing. when i receive a call i can just decline it but not accept it. my bluetooth seems proberly connected, im getting notifications and similiar thing, also the gear app says im connected. using it with a oneplus2 on RR, android 7.1.2.
i hope someone got fix for this.
Click to expand...
Click to collapse
Do you have other devices paired to your phone? If so, you might experiment by UNpairing other devices (headphones, bt speakers, whatever) and then try again.
I've seen my go both ways. But I prefer it paired with my car so have tried to limit the bt pairing between my phone and the watch to notices and some data updates but NOT voice.
fred2546 said:
Do you have other devices paired to your phone? If so, you might experiment by UNpairing other devices (headphones, bt speakers, whatever) and then try again.
I've seen my go both ways. But I prefer it paired with my car so have tried to limit the bt pairing between my phone and the watch to notices and some data updates but NOT voice.
Click to expand...
Click to collapse
thanks for your answer. i've tried this, doesn't work. i've also reseted my watch already and reinstall all the samsung stuff. not working at all.
ive fixed the problem so far. its caused by the rom, if i use the oxygenos it's working
I can confirm that there are a few custom roms (7.1.2) which supports the calling functionality in OP2.
You don't really have to move back to the stock Oxygen OS. :good:
PureNexus
HalogenOS
AICP etc..
Guys, this issue has been pestering for a month now and I seem to have not found a fix for this yet. I first started to notice the problem with my phone when I was unable to attend the calls, the screen will usually get stuck or i will not be able to swipe up the green button during the call. Even if sometimes I manage to i will be able to hear the other person speak but I wont be able to speak to them. So sometimes once I restart the phone it will seem to work fine for an indefinite period of time and again it starts.
Then things started getting very bad, sometimes during normal device usage, the screen just turns to a monochrome black and white screen ( just as you see when there was no signal on older television sets). And when I switch to the bootloader screen, when I power the device on, I get a very thin green line for an instant on the screen and then the booting sequence starts.
I have made a lot of factory resets and stock image flashing, and by far I noticed one considerably situation, the times when the sound functions fine, the booting sequence where the 4 google dots animation appears and when there is no sound, the booting sequence gets stuck on Google and made by Google screen.
Other observations are during abnormal device behavior, no function related to sound will properly. To elaborate it, Google assistant wont work, videos cannot be played and even the system sounds wont be heard. I am open to suggestions here. Please let me know what can be done to test the phone out. FYI I know there is a problem with the Pixel microphone, but I am not convinced that its the exact problem. Please correct me if I am wrong. Thank you.
Sounds like a hardware defect. RMA if possible.
Sent from my Pixel using XDA Labs
It is a hardware issue indeed, I am facing the same issue, I contacted google , they told that replacement is possible tho I'm out of Canada at the moment so I'm just dealing with it through my Bluetooth earphones, everybody works fine with Bluetooth.
That's the only way I suppose!...did you get the phone directly from the Google store?...are they accepting phones bought from a retailer?...since I am in Singapore now...Google support is next to nothing here...try contacting them but it's of no use...only when I get to India I will be able to go forward with the replacement!.....but the thing is .... yesterday...I updated the phone to Oreo and the audio stopped working completely....and after repeated switching between safe and normal mode....the speakers are working now...but the microphone is still busted.
This happened to me, I was given a replacement phone from EE UK
Current update guys...as per the pixel support centre person's suggestion ...I rebooted the device to safe mode to check if the phone is operating normally ...which it did not....but surprisingly ...after restarting to normal mode ...it started working normally again...my query is how is this zeroed down to an hardware issue if in case it's perfectly working for a while and at some point goes bonkers...can you guys please enlighten me on this...coz I don't have much knowledge on the hardware field.
MK1207 said:
Current update guys...as per the pixel support centre person's suggestion ...I rebooted the device to safe mode to check if the phone is operating normally ...which it did not....but surprisingly ...after restarting to normal mode ...it started working normally again...my query is how is this zeroed down to an hardware issue if in case it's perfectly working for a while and at some point goes bonkers...can you guys please enlighten me on this...coz I don't have much knowledge on the hardware field.
Click to expand...
Click to collapse
hello, i am facing the same things as you do since updating to oreo, my question is how do i test everything in safe mode, to see if everything is alright as you did
ndiri said:
hello, i am facing the same things as you do since updating to oreo, my question is how do i test everything in safe mode, to see if everything is alright as you did
Click to expand...
Click to collapse
Tough luck mate! Sorry to hear that....you can check it out by pressing down the power button until you get the power off and restart menu. Keeping pressing down on the power off menu...it will reboot to safe mode without your prompt. In safe mode for me it was the same....maybe you will have a better luck...try it out!
MK1207 said:
Tough luck mate! Sorry to hear that....you can check it out by pressing down the power button until you get the power off and restart menu. Keeping pressing down on the power off menu...it will reboot to safe mode without your prompt. In safe mode for me it was the same....maybe you will have a better luck...try it out!
Click to expand...
Click to collapse
well, its been almost an hour the phone wont turn sound back on.
Keep switching it to and out of safe mode...at some point ideally at least the speakers must start lest the microphone. Tried contacting Google about it and no response at all...mine started acting weird only for the past month...I suppose from the Aug months patch update....tried reverting it back to previous stock versions...but I suppose the damage is permanently done
When I contacted google, they told me to send it back to Canada and let someone there give it to google.. which won't happen in my case , my phone also started acting like this after Oreo beta . Now I will restart the phone whenever it happens to get it back working :/
The only reason I am still sticking to this phone is coz of it's camera. Planning to get back to India around December to get this fixed. Support for pixel in Singapore now is next to nothing since it wasn't launched here. I had no problem at all with the Nexus line up but this is kind of a disappointment.
Alaadragonfire said:
It is a hardware issue indeed, I am facing the same issue, I contacted google , they told that replacement is possible tho I'm out of Canada at the moment so I'm just dealing with it through my Bluetooth earphones, everybody works fine with Bluetooth.
Click to expand...
Click to collapse
You've mentioned it as through Bluetooth it works fine....care to elaborate on this?...are you able to input voice commands to Google assistant and speak over calls using it ?...since I am planning to buy one in case its a perfect workaround
MK1207 said:
You've mentioned it as through Bluetooth it works fine....care to elaborate on this?...are you able to input voice commands to Google assistant and speak over calls using it ?...since I am planning to buy one in case its a perfect workaround
Click to expand...
Click to collapse
Yea, Bluetooth works fine for calls, as for google assistant voice command you can enable that from google app settings. Of course other media will be working with Bluetooth as music, YouTube, etc..
Alaadragonfire said:
Yea, Bluetooth works fine for calls, as for google assistant voice command you can enable that from google app settings. Of course other media will be working with Bluetooth as music, YouTube, etc..
Click to expand...
Click to collapse
Excellent!...thanks for the input....let me check and get myself one and I will have to manage with it till December....and are you able to connect to a laptop thru Bluetooth...coz I am unable to do so...it just says paired...but the bt symbol in the phone doesn't change to connected..did you try that out ?
MK1207 said:
Excellent!...thanks for the input....let me check and get myself one and I will have to manage with it till December....and are you able to connect to a laptop thru Bluetooth...coz I am unable to do so...it just says paired...but the bt symbol in the phone doesn't change to connected..did you try that out ?
Click to expand...
Click to collapse
Hmmm I don't remember connecting to a laptop via Bluetooth.. you mean for file transfer ? Anyway Bluetooth has nothing to do with the sound issue we are facing, it might be your laptop Bluetooth driver needs to be updated
Alaadragonfire said:
Hmmm I don't remember connecting to a laptop via Bluetooth.. you mean for file transfer ? Anyway Bluetooth has nothing to do with the sound issue we are facing, it might be your laptop Bluetooth driver needs to be updated
Click to expand...
Click to collapse
Just bought a Bluetooth headset....works fine for the most part...but sometimes during calls...the phone just hangs and it automatically restarts....sigh! pixel just can't be trusted to be my daily driver?
MK1207 said:
Just bought a Bluetooth headset....works fine for the most part...but sometimes during calls...the phone just hangs and it automatically restarts....sigh! pixel just can't be trusted to be my daily driver?
Click to expand...
Click to collapse
Sorry to hear so, I actually installed ElementalX kernel and it is less to happen. Try to flash the kernel.
Alaadragonfire said:
Sorry to hear so, I actually installed ElementalX kernel and it is less to happen. Try to flash the kernel.
Click to expand...
Click to collapse
Planning to do just that....I may have better luck with a custom kernel...will post an update once I have flashed it.
I had been on the 8.0 beta for a while. Then got 8.0.
Though just 2 days ago, my mic was starting to have issues. Then yesterday, only my speaker phone would work.
Now I can't get any audio/mic except though Bluetooth (I've got a portable speaker with a mic, and Bluetooth on my car.
Contacted Google support. Will be getting a replacement on their warranty.
They didn't tell me this, but I did some searching, and apparently many of the pixels (mostly from the first 3 months of production) had an issue with the soldering of the audio codec. though usage, little bumps here and there, that soldering can get loose. Which explains why my audio and mic were spotty, and within an hour yesterday morning, all aspects of it stopped working.
So, it's a hardware issue.
I got the Pixel 1, and it was working fine and great on 7.0, then 8.0 came along and i did the update, now its complete garbage. The phone will periodically shut off and turn back on, the bluetooth is almost not usable.
I drive a Ram, so it utilzes the Uconnect system, it worked flawlessly on 7.0, but now when its connected and i play spotify thru the Uconnect, it does not display song name or artist, it just says pixel, i never had this issue before. And to add insult to injury, this morning when i made a call to my wife thru my Uconnect system, it didn't even connect to my bluetooth, it was ringing thru my phone, I even checked to make sure the BT was on, it says it was and it was connected.
so does anyone know if there is a fix for this? or am i SOL? I really like the phone otherwise, these issues only came up after i updated to 8.0, can i downgrade it back to 7?
truwrxtacy said:
I got the Pixel 1, and it was working fine and great on 7.0, then 8.0 came along and i did the update, now its complete garbage. The phone will periodically shut off and turn back on, the bluetooth is almost not usable.
I drive a Ram, so it utilzes the Uconnect system, it worked flawlessly on 7.0, but now when its connected and i play spotify thru the Uconnect, it does not display song name or artist, it just says pixel, i never had this issue before. And to add insult to injury, this morning when i made a call to my wife thru my Uconnect system, it didn't even connect to my bluetooth, it was ringing thru my phone, I even checked to make sure the BT was on, it says it was and it was connected.
so does anyone know if there is a fix for this? or am i SOL? I really like the phone otherwise, these issues only came up after i updated to 8.0, can i downgrade it back to 7?
Click to expand...
Click to collapse
Bluetooth is an intermittent issue with Pixel and Oreo. Google is aware and apparently added a fix in most recent update (November).
Fortunately, I have had no issue with Bluetooth and Oreo on my Pixel.
Concerning downgrade, you can always flash any factory image.
does it not have a rollback protection? From my understanding, i would need to OEM unlock it first before i can roll it back, mine is on 8.0 from verizon and apprantly the oem unlock is protected so i cannot turn it on
truwrxtacy said:
does it not have a rollback protection? From my understanding, i would need to OEM unlock it first before i can roll it back, mine is on 8.0 from verizon and apprantly the oem unlock is protected so i cannot turn it on
Click to expand...
Click to collapse
Wasn't aware you had Verizon's version. You may want to check with Google Forums concerning the Bluetooth issue. Best wishes!
As per phonearena.com Mate 9 is starting to get update to Oreo
https://www.phonearena.com/news/Unlocked-Huawei-Mate-9-receiving-Android-8.0-Oreo-in-the-US_id102104
Wait is over
Android Central is reporting it too. Anyone get it?
I have checked mine several times and nothing yet
it's approved for update in Firmware Finder
Edit: nevermind, jumped the gun...only approved if you check without the imei.
As someone who has been on the beta test for this for the past 2 months, it's pretty disappointing that they're releasing this. It has issues that they haven't fixed. If .360 is the final version, I'll have to see if I can get rolled back to Nougat.
dscline said:
As someone who has been on the beta test for this for the past 2 months, it's pretty disappointing that they're releasing this. It has issues that they haven't fixed. If .360 is the final version, I'll have to see if I can get rolled back to Nougat.
Click to expand...
Click to collapse
What issues are you having?
audioman42 said:
What issues are you having?
Click to expand...
Click to collapse
I stream Google Play Music via Bluetooth in my car. Until Oreo, when I turn off my car, or switch to another audio source, streaming from the phone is paused. Next time I start up the car, it resumes. Now, I have about a 50% chance of it resuming Google Play Music. It will randomly decide to instead use the built in music app to play something stored on the phone (one of the demo songs that came with the phone, or the one track I have saved on the SD card). I’m constantly having to go to Google Play Music & re-start whatever I was playing.
I’m also having unreliable visual notifications, particularly text messages (I use Textra). I do at least sometimes get the audio ding, but more often than not, no flashing light, and no badge on the shortcut. So if I’m not within earshot of the phone when I get a txt, I don’t know I received one (I can’t say for certain audio notifications always work, but I know at least sometimes I’ve heard the ding, but visually the phone doesn’t indicate it).
The above two issues are new since the Oreo update. Another issue I have that also existed in Nougat: the phone has difficulty managing multiple simultaneous Bluetooth connections. My car requires two connections: one for phone calls, and another to a 3rd party streaming adapter. If I have my Huawei Watch on/already connected to the phone when I get in the car, the two car connections won’t connect, at least not both of them. I have to toggle Bluetooth off/on on the phone to get all three connected at the same time. If I don’t have my watch on, there’s a better chance that both will connect, but at least one will. I didn’t seem to have these issues with my previous Note 3, but the Mate 9 seems to have a hard time reconnecting Bluetooth when there are multiple simultaneous connections involved. This issue is the one that caused me to join the beta, hoping to ensure it was fixed in the new software. Instead, it persists, and I gained a couple new ones.
dscline said:
I stream Google Play Music via Bluetooth in my car. Until Oreo, when I turn off my car, or switch to another audio source, streaming from the phone is paused. Next time I start up the car, it resumes. Now, I have about a 50% chance of it resuming Google Play Music. It will randomly decide to instead use the built in music app to play something stored on the phone (one of the demo songs that came with the phone, or the one track I have saved on the SD card). I’m constantly having to go to Google Play Music & re-start whatever I was playing.
I’m also having unreliable visual notifications, particularly text messages (I use Textra). I do at least sometimes get the audio ding, but more often than not, no flashing light, and no badge on the shortcut. So if I’m not within earshot of the phone when I get a txt, I don’t know I received one (I can’t say for certain audio notifications always work, but I know at least sometimes I’ve heard the ding, but visually the phone doesn’t indicate it).
The above two issues are new since the Oreo update. Another issue I have that also existed in Nougat: the phone has difficulty managing multiple simultaneous Bluetooth connections. My car requires two connections: one for phone calls, and another to a 3rd party streaming adapter. If I have my Huawei Watch on/already connected to the phone when I get in the car, the two car connections won’t connect, at least not both of them. I have to toggle Bluetooth off/on on the phone to get all three connected at the same time. If I don’t have my watch on, there’s a better chance that both will connect, but at least one will. I didn’t seem to have these issues with my previous Note 3, but the Mate 9 seems to have a hard time reconnecting Bluetooth when there are multiple simultaneous connections involved. This issue is the one that caused me to join the beta, hoping to ensure it was fixed in the new software. Instead, it persists, and I gained a couple new ones.
Click to expand...
Click to collapse
Same here with bluetooth inconsistencies when connected to my car. I have resynched several times and sometimes it helps for a short while and other times no improvement. Sometimes I can control songs and other times not. Sometimes it shows songs and other times it shows connecting. Sometimes it shows the correct name of song and other times it freezes on a song title that is long gone. Even when deleting and resynching my phone, an old song title is displayed and not the same as being played. Total bummer as I use bluetooth music every time I get into my car. On recent update (360) which appears to be the same one they are releasing as OTA.
hmmm, this must be a states model thing, my huawei mate 9 works perfectly on oreo...i dont use textra, use normal default...anyway is one of the reason i dont buy or use states systems on no phone...i always buy the international phones(orignal phone) the company put out...they better and receive the update in a timely manner...sorry, but state phones suck! i havent bought one in over at least 10 years....
Still waiting. To be honest though, it's not even Oreo I want, I just want the dang security updates. April 2017 is wayyy too old.
dscline said:
I stream Google Play Music via Bluetooth in my car. Until Oreo, when I turn off my car, or switch to another audio source, streaming from the phone is paused. Next time I start up the car, it resumes. Now, I have about a 50% chance of it resuming Google Play Music. It will randomly decide to instead use the built in music app to play something stored on the phone (one of the demo songs that came with the phone, or the one track I have saved on the SD card). I’m constantly having to go to Google Play Music & re-start whatever I was playing.
I’m also having unreliable visual notifications, particularly text messages (I use Textra). I do at least sometimes get the audio ding, but more often than not, no flashing light, and no badge on the shortcut. So if I’m not within earshot of the phone when I get a txt, I don’t know I received one (I can’t say for certain audio notifications always work, but I know at least sometimes I’ve heard the ding, but visually the phone doesn’t indicate it).
The above two issues are new since the Oreo update. Another issue I have that also existed in Nougat: the phone has difficulty managing multiple simultaneous Bluetooth connections. My car requires two connections: one for phone calls, and another to a 3rd party streaming adapter. If I have my Huawei Watch on/already connected to the phone when I get in the car, the two car connections won’t connect, at least not both of them. I have to toggle Bluetooth off/on on the phone to get all three connected at the same time. If I don’t have my watch on, there’s a better chance that both will connect, but at least one will. I didn’t seem to have these issues with my previous Note 3, but the Mate 9 seems to have a hard time reconnecting Bluetooth when there are multiple simultaneous connections involved. This issue is the one that caused me to join the beta, hoping to ensure it was fixed in the new software. Instead, it persists, and I gained a couple new ones.
Click to expand...
Click to collapse
I've noticed similar Bluetooth problems. I stream in my car pretty often and through headphones at work, and at times I won't be able to skip songs via the receiver/headset. Since a reboot always fixes it, I've been doing preemptive reboots as I walk to my car in the morning to circumvent the issue.
I've had zero issues with Textra. If anything, it's working even better now than it did before - all of my MMS sending issues are gone. Apparently, though, this was less of a Huawei problem and more of a Nougat problem.
cross1989 said:
hmmm, this must be a states model thing, my huawei mate 9 works perfectly on oreo...i dont use textra, use normal default...anyway is one of the reason i dont buy or use states systems on no phone...i always buy the international phones(orignal phone) the company put out...they better and receive the update in a timely manner...sorry, but state phones suck! i havent bought one in over at least 10 years....
Click to expand...
Click to collapse
Which region did you rebrand to? I was on 432 running a custom ROM for a while, but went back to 567 thinking that would solve my MMS sending issues. I want to rebrand, but I've heard that rebranded phones don't receive OTA updates because the IMEI doesn't match the region.
Thanks
I did not rebrand any thing, as I stated I don't buy state side phones, I buy original unlock phones directly from company (Amazon).. I have international version, MHA-L29C185... Now on oreo from Ota... Yea you loose Ota on those rebranding systems most of those require to unlock bootloader and twrp... That alter the system... If you want a good Huawei phone, buy international or China version off Amazon, yes both work in the states.
Just got my ota update today
Can someone who got Ota update check to see if any of the files on the FF app are giving an imei approval?
Mine still isn't and I didn't get Ota yet, so if it does for you and u got the Ota it may shed some light on whether the server shown on FF is directly linked to Ota files...
I just got the OTA update...downloading it now
kullum79 said:
I just got the OTA update...downloading it now
Click to expand...
Click to collapse
Where are you located??
shae23 said:
Where are you located??
Click to expand...
Click to collapse
I am in Chicago Central Standard Time... playing with the camera as we speak....
kullum79 said:
I am in Chicago Central Standard Time... playing with the camera as we speak....
Click to expand...
Click to collapse
Lool same location, no update, man Huawei is funny, oh well, guess it'll get here in its own time
It doesn't matter about the area it's being done in Bach's by imei .
---------- Post added at 09:11 AM ---------- Previous post was at 09:02 AM ----------
U can download it in ff but when it finishes download and install it won't verify because the it's has the imei in the download bricked one phone so I will wait for the ota I called huwaei to c about unbricking and the told me the date and time of the forced update voided the warranty
I got my Oreo update just a few hours ago, bought off Amazon, in KY, on T-Mobile
Oreo Update
I got my OTA update late yesterday. Haven't had it long enough to see if the battery life is better.
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!
nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.
So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders