Galaxy Note 8 Announcement and Owners' Thread

Forums › Android › Galaxy Note 8 Announcement and Owners' Thread

1 | ... | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49

Networkn
32864 posts

Uber Geek
+1 received by user: 15454

ID Verified

Trusted

Lifetime subscriber

#2009794 8-May-2018 10:44

Ok, I have a persistent issue that is driving me crazy. I have smart unlock configured at home. A fair percentage of the time it doesn't work. It's crazy annoying. I removed everything from smart locations and reconfigured from scratch. Same thing. For example, works upstairs at my home, not downstairs! It's set to 100m from my GPS location and that is accurately configured.

Lizard1977

2133 posts

Uber Geek
+1 received by user: 624

ID Verified

#2034195 12-Jun-2018 10:13

Lizard1977:

I chased up Samsung support about this issue, and they haven't got anything else to suggest on the software side, and have suggested I take it back to Spark, who will send it on to Telegistics for assessment.

They note that "possible charges may apply if the product is out of warranty [it's not] or if the technician finds no fault or if it is a non-manufacturing fault. In these cases, quote will be provided after inspection. If you accept the quote, repair will be carried out, otherwise, inspection charges will apply."

I guess I'm a little apprehensive about this for a couple of reasons. Firstly, I'm a little skeptical about the technician finding a fault. I'm pretty convinced it's a software issue, as it happened immediately after the Oreo update, so I doubt they will find it to be a hardware fault. But it seems like these kinds of issues, being so intermittent, are easy to write off as "no fault" or being a non-manufacturing fault (whatever that is), and leaving me with a bill. Secondly, being without a phone for any length of time is becoming less and less viable these days, so the thought of handing my phone over for inspection only to have them determine that there isn't a problem they an replicate, and billing me for the privilege, doesn't thrill me.

Has anyone else had any experience with Spark/Telegistics and dealing with a fault like this? I might feel a little reassured if the prospects of a good outcome were higher.

I finally had some time this weekend to do a bit of troubleshooting, to avoid having to take my phone in to Spark for servicing. I connected my Note 8 to a friend's car stereo via bluetooth (an aftermarket adapter), and it worked fine, no glitches at all. To compare, I connected it to my normal car stereo, and it struggled to connect, and when it did connect lost the connection within seconds. Okay - looks like the problem is with my stereo, not my phone. But then I connected my old iPod Touch to my car stereo via bluetooth, and it's fine. It's been playing flawlessly for the last 2 days. Weird...

So, to sum up. My Note 8 plays fine via bluetooth on other stereos, but not on my own car's stereo. And other devices play fine on my car stereo. It's just this particular combination of my Note 8 and my stereo. That's very particular. Both are updated to the latest software, so there's no updates to apply. The only thing I can think is that somehow the bluetooth driver on my phone is strangely now "incompatible" with my stereo (though I can't imagine how or why). Is anyone else aware of such an incompatibility, and how I might resolve it? I really don't want to replace my car stereo just because the bluetooth doesn't work properly, but it's a real nuisance. There's also no point in putting my Note 8 or my stereo in for servicing, because the problem is only related to this combination of devices - other devices work fine. Any thoughts?

myndlyz

472 posts

Ultimate Geek
+1 received by user: 99

#2034196 12-Jun-2018 10:15

Lizard1977:

Lizard1977:

I chased up Samsung support about this issue, and they haven't got anything else to suggest on the software side, and have suggested I take it back to Spark, who will send it on to Telegistics for assessment.

They note that "possible charges may apply if the product is out of warranty [it's not] or if the technician finds no fault or if it is a non-manufacturing fault. In these cases, quote will be provided after inspection. If you accept the quote, repair will be carried out, otherwise, inspection charges will apply."

I guess I'm a little apprehensive about this for a couple of reasons. Firstly, I'm a little skeptical about the technician finding a fault. I'm pretty convinced it's a software issue, as it happened immediately after the Oreo update, so I doubt they will find it to be a hardware fault. But it seems like these kinds of issues, being so intermittent, are easy to write off as "no fault" or being a non-manufacturing fault (whatever that is), and leaving me with a bill. Secondly, being without a phone for any length of time is becoming less and less viable these days, so the thought of handing my phone over for inspection only to have them determine that there isn't a problem they an replicate, and billing me for the privilege, doesn't thrill me.

Has anyone else had any experience with Spark/Telegistics and dealing with a fault like this? I might feel a little reassured if the prospects of a good outcome were higher.

I finally had some time this weekend to do a bit of troubleshooting, to avoid having to take my phone in to Spark for servicing. I connected my Note 8 to a friend's car stereo via bluetooth (an aftermarket adapter), and it worked fine, no glitches at all. To compare, I connected it to my normal car stereo, and it struggled to connect, and when it did connect lost the connection within seconds. Okay - looks like the problem is with my stereo, not my phone. But then I connected my old iPod Touch to my car stereo via bluetooth, and it's fine. It's been playing flawlessly for the last 2 days. Weird...

So, to sum up. My Note 8 plays fine via bluetooth on other stereos, but not on my own car's stereo. And other devices play fine on my car stereo. It's just this particular combination of my Note 8 and my stereo. That's very particular. Both are updated to the latest software, so there's no updates to apply. The only thing I can think is that somehow the bluetooth driver on my phone is strangely now "incompatible" with my stereo (though I can't imagine how or why). Is anyone else aware of such an incompatibility, and how I might resolve it? I really don't want to replace my car stereo just because the bluetooth doesn't work properly, but it's a real nuisance. There's also no point in putting my Note 8 or my stereo in for servicing, because the problem is only related to this combination of devices - other devices work fine. Any thoughts?

any way you can try a different note8 to see if it will connect to your stereo?

Lizard1977

2133 posts

Uber Geek
+1 received by user: 624

ID Verified

#2034198 12-Jun-2018 10:19

Sadly, I'm the only person in my circle with a Note (and one of very few Androids, I might add).

tripp

3848 posts

Uber Geek
+1 received by user: 1220

Trusted

Lifetime subscriber

#2034249 12-Jun-2018 11:15

myndlyz:

Lizard1977:

Lizard1977:

I chased up Samsung support about this issue, and they haven't got anything else to suggest on the software side, and have suggested I take it back to Spark, who will send it on to Telegistics for assessment.

They note that "possible charges may apply if the product is out of warranty [it's not] or if the technician finds no fault or if it is a non-manufacturing fault. In these cases, quote will be provided after inspection. If you accept the quote, repair will be carried out, otherwise, inspection charges will apply."

I guess I'm a little apprehensive about this for a couple of reasons. Firstly, I'm a little skeptical about the technician finding a fault. I'm pretty convinced it's a software issue, as it happened immediately after the Oreo update, so I doubt they will find it to be a hardware fault. But it seems like these kinds of issues, being so intermittent, are easy to write off as "no fault" or being a non-manufacturing fault (whatever that is), and leaving me with a bill. Secondly, being without a phone for any length of time is becoming less and less viable these days, so the thought of handing my phone over for inspection only to have them determine that there isn't a problem they an replicate, and billing me for the privilege, doesn't thrill me.

Has anyone else had any experience with Spark/Telegistics and dealing with a fault like this? I might feel a little reassured if the prospects of a good outcome were higher.

I finally had some time this weekend to do a bit of troubleshooting, to avoid having to take my phone in to Spark for servicing. I connected my Note 8 to a friend's car stereo via bluetooth (an aftermarket adapter), and it worked fine, no glitches at all. To compare, I connected it to my normal car stereo, and it struggled to connect, and when it did connect lost the connection within seconds. Okay - looks like the problem is with my stereo, not my phone. But then I connected my old iPod Touch to my car stereo via bluetooth, and it's fine. It's been playing flawlessly for the last 2 days. Weird...

So, to sum up. My Note 8 plays fine via bluetooth on other stereos, but not on my own car's stereo. And other devices play fine on my car stereo. It's just this particular combination of my Note 8 and my stereo. That's very particular. Both are updated to the latest software, so there's no updates to apply. The only thing I can think is that somehow the bluetooth driver on my phone is strangely now "incompatible" with my stereo (though I can't imagine how or why). Is anyone else aware of such an incompatibility, and how I might resolve it? I really don't want to replace my car stereo just because the bluetooth doesn't work properly, but it's a real nuisance. There's also no point in putting my Note 8 or my stereo in for servicing, because the problem is only related to this combination of devices - other devices work fine. Any thoughts?

any way you can try a different note8 to see if it will connect to your stereo?

Wonder if its an audio codec issue, does bluetooth connect and just drop or does not connect at all?

Lizard1977

2133 posts

Uber Geek
+1 received by user: 624

ID Verified

#2034295 12-Jun-2018 12:07

It struggles to connect at first, then it drops at random.

AliExpress

Shop now on AliExpress (affiliate link).

obsshn

95 posts

Master Geek
+1 received by user: 3

#2034602 12-Jun-2018 20:29

Lizard1977:
Sadly, I'm the only person in my circle with a Note (and one of very few Androids, I might add).

If your in CHCH I'd be happy to provide mine

Lizard1977

2133 posts

Uber Geek
+1 received by user: 624

ID Verified

#2034772 13-Jun-2018 08:40

@obsshn Thanks for the offer, but I'm in Palmerston North.

@tripp if it is a codec issue, how would I check/change things?

tripp

3848 posts

Uber Geek
+1 received by user: 1220

Trusted

Lifetime subscriber

#2034821 13-Jun-2018 09:18

Lizard1977:

if it is a codec issue, how would I check/change things?

I know some phones will let you change the codec used under dev options or under the paired devices area in bluetooth (where you select call audio or media audio).

That might be another thing you want to try is deselecting call audio in bluetooth and seeing if you have the issue still, then try it for media audio as well.

Lizard1977

2133 posts

Uber Geek
+1 received by user: 624

ID Verified

#2038110 15-Jun-2018 11:12

So I was able to try a few things the last couple of days. I tried deselecting call audio in bluetooth, and for about a minute I thought it had worked, but then the bluetooth connection kept disconnecting, and it made no difference.

The other day I downloaded Android Auto to have a play around, and just to see what happened I tried reconnecting to bluetooth. It was solid for about 3 minutes, but then it started disconnecting. Because I had my handset in the cradle and in my line of sight, I was able to see visually what happens (previously my phone was in my pocket or in the centre console, out of sight). Android Auto would exit, indicating clearly that the bluetooth connection with the stereo was lost. But it would immediately attempt to reconnect and would make a connection (Android Auto restarted), but then immediately drop off (AA exited). Again and again, a perpetual loop of connection and disconnection. So I don't think it's just that the bluetooth is stuttering or interrupting, the data connection is completely lost.

I also found someone at work who has a Note 8 and was able to do a quick test. It took a bit of finangling to get his phone to pair (I had similar experiences when I first paired my Note8), but eventually it connected. I didn't have a lot of time to experiment, but his phone held a rock-solid connection for nearly 5 minutes before he had to go. By comparison, when I re-connected my phone, it dropped the connection within about 45 seconds.

So this just confounds me even more. My phone will pair and work with other bluetooth car stereos, but has problems with my own. Other devices will pair and work with my own car stereo, but my phone has problems.

I'm in a bind here. If I take my phone in for servicing, they will (quite rightly) probably find no problem, as it seems to work with other bluetooth stereos just fine. If I try and claim that my car stereo is faulty, it will (almost certainly) work with other devices no problem. But I'm left with an unfortunate pairing (literally) of two devices. Any other suggestions?