I want to take a minute and share a bluetooth issue I've had with my Galaxy S6. Maybe others have observed the same thing, and while I'm not specifically looking for a solution, suggestions are welcome. The S6 is about 3 months old, Andriod 5.0.2, unrooted, and other than Apex launcher pretty vanilla.
For the record, with the exception of the issue I'm about to describe, this phone has been phenomenal.
I use the phone in my car over bluetooth to and from work every day. For the first two months this worked great, no problems at all with podcast addict or poweramp. Then, I noticed the audio would dip momentarily. As if someone turned the volume down and back up. The bluetooth connection never gets lost, just the audio dip. Then, eventually the problem became perpetual. I will describe the symptom the best I can, as if the volume were being turned up and down. This wasn't the case, more like the bluetooth stream was somehow going away and coming back.
I tried all the obvious things, like re-pair the phone to the car, clear the bluetooth cache, Volume Up + Home + Power button and then "wipe cache partition". As a last resort I did a factory reset. This last step actually solved the issue, for a while. This was a few days ago, but this morning I noticed the same periodic blips in the sound, so I suspect over time the same problem will once again return.
<rant>
I was in touch with Samsungs customer support, who is supposed to "values you as a customer and want to insure that we have provided you with the answer you were looking for". Unfortunately, the blunt truth was they ended up being useless with an offer to allow me to send my 2 month old phone to them and wait for an undisclosed time, for what might end up being a refurbed replacement.
</rant>
Since I don't see mention of this in the forums, maybe it's not a wide spread problem. Maybe a compatibility problem between these two specific chipsets? Whatever the issue, hopefully some future update comes out that fixes things. Defaulting the phone every few months would be a considerable drag.
Related
Hi, everyone.
I searched for this and didn't find anything, but it's a little hard to know what to search for.
I use WunderRadio to listen to Internet radio. A few weeks ago, the Video Out (TV Out) screen started popping up at random times, usually when I was tapping something on the menu or on the screen. When it did, it was almost impossible to close and it really messed up my listening.
Some days it wasn't too bad. Sometimes, when it got really frustrating, a soft reset would stop it temporarily (or at least slow it down). When it was at its worst, though, nothing helped, and it was impossible to listen to WunderRadio.
It wasn't only in WunderRadio that this would happen--it would pop up occasionally in other applications, as well. But it was the most frustrating by far in WunderRadio.
I recently did a hard reset, so I only had a few applications installed. I first assumed that this was being caused by WunderRadio, so I uninstalled it. I still kept seeing that Video Out screen.
I selectively uninstalled applications and thought a couple of times that I had identified a program that was causing the problem. However, it kept coming back, seemingly regardless of what was installed or uninstalled.
A few days ago, this stopped happening. I haven't seen the Video Out screen a single time. I don't know if it has fixed itself (I doubt it) or whether it will suddenly reappear.
At this point, it seems like this could be due to faulty software, firmware, or hardware.
In July, I had a similar thing going on. I don't know if it was related to this or if this is just a coincidence. The phone all of sudden decided that it wanted to redial the last number called--over and over again! I would think I had it stopped, put the phone in my pocket, and get a call from a contact asking if I had called them. No, I hadn't, but my phone had!
As with the Video Out problem, sometimes a soft reset would help. Often, however, I ended up just having to turn the phone off for a few hours, then cross my fingers and try again.
With both of these problem, I was hesitant to send the phone in for warranty repair, because they were both so unpredictable that the repair shop would probably be unable to make either of these symptoms appear. My fears have since been borne out by the fact that both problems seem to have been solved--at least semi-permanently.
On the other hand, either or both of these problems could come back at any time!
Can anyone tell me what's going on here and what I can do about it?
Thanks in advance!
Are you using a wired headset? Maybe the pins are a little off and acting like the tvout cable USB pins and that's triggering it.
You should try to think if there is any correlation between a wire headset and this activity.
Also, do you actually use TV-out? You can just disable it entirely by a registry tweak so it won't be able to popup if that helps.
If you need anything further feel free to PM me since it's unlikely I'll find this post again
Good point! Yes, I am using a wired headset--most often when I'm listening to WunderRadio--which would explain why it happens most often when I'm listening.
I switched from headphones to earphones the other day, and that could very well be the reason it's no longer happening.
It's either the headphones or your USB port that's bad. But since you've said the problem has went away with new headphones, I'd say it's those. But it's a guaranteed hardware issue, although not necessarily the phone.
I had the same problem - TP would switch to TV Out mode randomly when mini usb was used (either charge or headphones). Mine needed a new usb socket, although I think theyyyyy jutssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssst swap the whole board. And I know it's off topic but can someone point me in the right direction to sort out my keyboard problem above?!
jjjacksonjjj said:
I had the same problem - TP would switch to TV Out mode randomly when mini usb was used (either charge or headphones). Mine needed a new usb socket, although I think theyyyyy jutssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssst swap the whole board. And I know it's off topic but can someone point me in the right direction to sort out my keyboard problem above?!
Click to expand...
Click to collapse
hehe does your keyboard repeat too quick? Settings - Personal - Buttons and reduce the repeat rates on 'up/down control'...on and stop eating so much candy while playing with your phone
Hey guys,
I've just receieved my third HTC handset with what I'd consider to be a major issue.
HTC Touch2 in 2009 - would often power off during calls (probably due to WinMo). Hardware buttons quickly became loose after about a month of use, and the backlighting stopped working.
HTC Legend in 2010 - this phone is two months old and the top speaker is so broken I can barely hear somebody on a call. Everything crackles and pops and, according to people on the other end, they can barely hear me either. It's annoying as when I bought it the call quality was great but gradually the speaker got buzzier and buzzier.
HTC 7 Trophy - the most serious of the bunch. Yesterday, whilst web browsing, the phone displayed a still multicoloured screen of static. None of the buttons would work. After taking the battery out and restarting, the static re-appeared. I've managed to power on the phone since - you have to wait an hour with the battery out - but you get the same static lock ups when web browsing or using search after about five minutes. Having had a similar experience on my laptop, it looks to me like a GPU failure.
Am I the only one who has experienced incredibly shoddy hardware quality control from HTC? I'm going to have to replace the HTC Trophy and, at the moment, I'm starting to seriously question going with an HTC. The touch2's button issues were forgiveable because that was relatively cheap, the Legend's speaker was incredibly annoying but the Trophy's GPU failures are completely unforgiveable IMO. They render the phone completely useless.
Am I just unlucky or have others experienced similar concerns?
Cheers
My Hero has been fine, along with my touch... Although that met a washing machine in the end
Finally ~ Someone With A Similar Issue
Finally, someone that doesn't purely worship HTC... Although I haven't experienced issues to the magnitude of your's, I haven't been 100% happy with my phone since the day I bought it. I have a HTC Desire, and I got this phone in confidence after reading many reviews about how good the phone was, these reviews were clearly written from people with 0% experience with the phone.
I will number the issues I have had with the build quality of this phone...
1) The case on the back of the phone, has only ever been took off about 4 times, I have never dropped my phone or anything, however it starting to come off, yes, I can take the back of my phone off, without using the finger slot.
2) The screen is so easy to scratch? It was in a pocket with an Asthma spray, and there was no vigorous shaking of my pocket, yet somehow the screen just completely f****d up man... wow.
3) This is probably the worst issue I have. Every time HTC releases an update for my phone, I run into some sort of issue. I got my phone in May/April 2010 (it's on Orange UK however de-branded and now due to update issues, running a custom ROM) and immidiatley I found that an update had been released. After downloading the update the phone started to install the update, however it restarted and nothing happened. Left it for about an hour, nothing... So yes, I did the worst, took the battery out and messed it up completely. The shop I got it from forced me to send it to HTC, it took them 5 weeks (VERY poor customer service) and when I got it back they had barely fixed it, as when I turned it on, it finished installing the update?
4) I have had some other software issues, such as the system occasionally locking up and having to remove the battery to get anything to work. Occasionally the screen will lock up, like I won't be able to click any icons, however I'll be able to swipe from screen to screen, and it really can be quite annoying. As far as battery goes, it will last me an entire day, but will require a charge at the end of the day.
However, I think me and you are in a minority. I'm 14 years old, and I talked my Dad into buying a HTC Desire HD. He hasn't had a single problem with his, it installs updates perfectly without and issue, and the software performs seaming-less (except for a problem with a process that took up 80.9% of the RAM, fixed by turning the USB Debugging on?) So I believe HTC are good, theres just a few really, really bad apples in there, and unfortunately HTC won't admit this, and don't want to do anything about it... I hope I helped, I'm fairly new on here...
Cheers, Michael.
Well guys,you are a minority indeed.This Tuesday I received my Desire HD,which is my fourth handset from HTC.I have had a Diamond,a Hero,a Desire and now the Desire HD.The only problem I ever had was with my Diamond which,after one year and a half took some water in it without getting exposed to any water,but it was because the climate here is very humid.Other than that I have never had an issue.And I am no fanboy,if I had problems I would change without second thought.
I'll just tell you that a friend of mine punched my Desire HD with his full strength(don't ask why) while it was in my pocket.I thought the phone was done for,scrap,but the phone is like nothing happened.My friend's hand wasn't so lucky however,it still needs ice!
Hello all:
I am on my first replacement phone, and am experiencing a recurring problem that I also had on my original phone. At times during the call, the person on the other end will not be able to hear me (a la 'mute'), but I can hear them. I have confirmed that the mute function is not activated (even turned it on then off), but no luck. My initial impression was just a faulty microphone/hardware, but given that my second phone is also experiencing then same problem, I wonder if it is something that I am doing. I can assure you that I am not in any way blocking the microphone hole at the bottom of the phone (experimented with that to see if it was the cause). I can also rule out network issues due to moving between cells - I have experienced this problem driving and sitting still at my desk.
This problem, more than the GPS issue, will be the deal breaker for me - this is a business phone and I spend a substantial amount of time every day on work related calls.
Thanks in advance.
Thomas
I have the same issue. My coworker had the same issue with his the replacement under warranty.
If I use the headset it works fine. If I mute the phone and un-mute it it starts working.
Something is fishy with the microphone of this model ...
Okay, now this is getting ridiculous. Either I have really bad luck, or I am doing something wrong. On my second replacement phone, and like the last two, I have problems with the microphone cutting out during the middle of calls. Am I completely alone, or am I just lucky in getting phones with bad mics?
I keep the phone in my pocket with a body glove case. The mic is not plugged up, and it seems random. Could there be a software issue (ie a piece of software interfering and taking over the soundstream from the mic)? Even though the person on the far end cannot hear me, I can hear them.
Thanks
T
@ banesong: I'm having similar issues. I've had my phone for a little more than 24 hours. last night i couldn't hear anything coming from my mic and obviously could not communicate from my end. taking the battery out and back in fixed it for me. but i look at this as only a temporary solution. hopefully this isn't a hardware issue
I am having the same issue. I've had my Captivate since the end of July and it is running stock 2.1 that came with it and unrooted. I can't remember when the issue first started. But it has been doing it a lot more lately. It seems to happen around 8 or 9 minutes after I am on the phone call. At first I would hang up and just call back. Then I discovered that the mic would start working again if I just turned the speakerphone on and then off again.
It is really starting to get annoying now. I am thinking about getting a warranty replacement. The only reason why I didn't get a warranty replacement sooner is because I don't feel like having to remember and reinstall all the apps that I have on my phone now.
Having the same issue here and I have an idea about the problem.
If you remove the lid on the back that covers the battery the microphone is disabled and no warning appears on the screen. This is the same behaviour we are all experiencing.
There are two round blank spots on the inside of the cover matching two contacts on the phone. My idea is that the 'lid open' detection checks if the lid connects these two contacts.
My microphone usually starts working when I squeeze the phone.
Not sure about a workaround yet but connecting the two connectors directly inside the phone should solve it permanently (but voids the warranty).
Hope that helps.
T
Sorry, please ignore my previous message. I couldn't reproduce it yesterday so it must have been coincidence.
However, I have the same microphone problem and would like to know if there is a fix for it.
Cheers
T
Possible fix
I know this is an old thread but I have one of these old phones and was having this problem. After fiddling with the settings a bit I found a setting under Call Settings->Voice Call->Noise suppression. I unchecked the box and the mic seems to be working - for now.
I keep hearing about this unfixed Nexus S reboot bug. I'm curious... is it really so widespread? Or is it only something a few people experience, like the luck of the draw?
I apologize if this question has been asked before. I'm considering buying the phone but can't decide if I should wait.
It always seems to pop up in the forums but it has never happened to me. I've had mine for almost a month now and it all seems to be perfect. No defects with screens or buttons or reboots. Maybe im just lucky...or people with complaints are just louder than ones who are satisfied.
The issue is real and Google have confirmed it. They've been working on a fix and the official word was an OTA update was going to be released this week:
Just a heads up that our initial tests look good and that we are expecting to send out an OTA within one to two weeks that will resolve the issue. Thanks for your continued patience!
Click to expand...
Click to collapse
code.google.com/p/android/issues/detail?id=13674
silfer said:
It always seems to pop up in the forums but it has never happened to me. I've had mine for almost a month now and it all seems to be perfect. No defects with screens or buttons or reboots. Maybe im just lucky...or people with complaints are just louder than ones who are satisfied.
Click to expand...
Click to collapse
Argh. I did not have this problem until yesterday (had the phone since January). Now my phone will reboot right after a call.
apreichner said:
I keep hearing about this unfixed Nexus S reboot bug. I'm curious... is it really so widespread? Or is it only something a few people experience, like the luck of the draw?
I apologize if this question has been asked before. I'm considering buying the phone but can't decide if I should wait.
Click to expand...
Click to collapse
I've had three Nexus S so far. The first one I picked up on dec 16th and didn't get a single reboot on - but the oleophobic coating on the screen was coming off in spots so I swapped it for another unit.
The second unit had issues rebooting. I saw it immediately - it rebooted while sitting on my desk. I could constantly recreate this by streaming audio over BT in my car - every 10-15 minutes it would reboot.
I picked up a mt4g for a few weeks to see if they could sort whether this was a hardware of sw issue (that thing is a brick to hold) and eventually picked up a third Nexus S once they identified it as a SW issue. This device has not rebooted a single time in the 27 days I've had it. I can stream audio and make long calls without an issue.
All three devices have operated with identical configurations. Based on this I'd say that some units are worse than others.
Maybe it's issue with the hardware tolerances and some hardware that falls within the accepted tolerance is not operating as expected and causing kernel panics as a result. This would explain why some have this issue constantly and others rarely or never see it. Perhaps it's something seemingly unrelated that everyone experiencing the reboots has in common. It would be nice if Google weren't so tight lipped about this. Supposedly the OTA will address these issues and moving forward it should be irrelevant.
I get this issue at least 60% of my calls (not that i call much). i have made 4 calls today, and 3 of them my phone rebooted during the proccess.
I am returning this to CW tommorrow for a replacment unit, i love the phone dearly but do not want to be robbed for £429 but not being able to take it back if they do not resolve.
It could be a batch issue, or something i guess, but that's not my job to find that out, that's for the people i paid for the hardware/software
I hope i get another unit, and if not problem free at least i can rely on a warranty, hopefully making sure if google slack on fixing this i can get my money back.
If it fixes soon or the new handsets ok, i can keep this lil beauty of a phone
I've had my SNS since launch. My phones has rebooted on me twice. It was right after playing a 3D game. Right after i exited the game the phone rebooted. Funny though, it hasn't happened again.
I've gone back to using my Desire until Google sort this out. For me, any call above 5 minutes has a 50% chance of rebooting the handset.
The handset (running stock 2.3.2 and un-rooted) will on occasion spontaneously reboot as well. Not good.
It is a bug that seems to be very limited in scope but is very serious for those affected. Personally, I've never had it happen to me or my wife.
Thank you for your replies, they were very helpful. I was keeping up with the OTA Bugfix promised by Google for the Nexus S. Although, that was promised almost 3 weeks ago and still no word from Google since. That's one of the reasons why I came here to ask for advice before I bought the phone. Although I'm curious to see if 2.3.3 resolved the issue. I know the 2.3.3 just lists API changed, but I wouldn't expect them to list bugfixes on a list of API changes.
I think I'm ready to buy the phone and hope for the best. I'll probably just get Best Buy insurance just to be safe.
apreichner said:
Thank you for your replies, they were very helpful. I was keeping up with the OTA Bugfix promised by Google for the Nexus S. Although, that was promised almost 3 weeks ago and still no word from Google since. That's one of the reasons why I came here to ask for advice before I bought the phone. Although I'm curious to see if 2.3.3 resolved the issue. I know the 2.3.3 just lists API changed, but I wouldn't expect them to list bugfixes on a list of API changes.
I think I'm ready to buy the phone and hope for the best. I'll probably just get Best Buy insurance just to be safe.
Click to expand...
Click to collapse
Getting the insurance is definitely the right choice. I hope you enjoy your phone and your stay here!
I get periodic reboots on both my phones.
It is not that noticeable, since it often happens when I am not using the phone and unless I glance at it and see the start animation, I may be unaware of it.
But it has happened during a call as well (couple of times on each phone) and then it is definitely noticeable.
I have this bug... not during phone calls but random reboots. 2-3 a day. I hate it but its tolerable.
Weird, I don't have this bug
If flashing a custom rom, the problem will be solved? Since i am considering if i should get Nexus s later on.
Thanks
Around late June 2018 my phone was updated to Oreo. I posted this complaining of a slow and sluggish phone with poor battery life. After a full clean flash the phone improved noticeably but still wasn't where I thought it should be. Certain apps still seemed slow to open I continue to have WiFi issues.
About four to six weeks later there was another update. I'm not sure if it was a Samsung update or an AT&T update (security patch maybe?). Once again all aspects of the phone became slow and battery life plummeted. I was back down to eight or nine hours per charge. So, once again, I performed a clean flash of the phone and things got a little better. I was back on par with my initial post-Oreo clean flash and still nowhere near my pre-Oreo performance.
About four or five weeks ago my phone started nagging me to update again. I kept WiFi turned off and continually procrastinated the update for about a week or two. Finally I allowed the update and again I am having major performance issues. Battery life is unacceptable. I get around eight hours per charge. All apps are noticeably slower to open and run slower. My G-Mail app is slow to open and show new correspondence. My navigation app is virtually intolerable. The telephone app takes forever to open. Often it will ring four times and go to voicemail before the caller ID opens to show who is calling. My Swype keyboard sometimes takes two or three seconds to come up also, I forgot to backup my custom dictionary before my last clean flash so I lost all my slang and cuss words.
Here is an interesting and annoying quirk. Bluetooth now fails. I'll get in the car and the phone will automatically sync to my JVC receiver. This still happens without any issues. The issue is that, at random times, the music will just stop playing through the stereo and it will play through the phone's speaker. The bluetooth connection is not broken or interrupted (the devices are still conntected), it just randomly starts sending music to the phone's speaker instead of the car's stereo. The easiest work around I have is to hit the pause button on the car's stereo, wait one or two seconds then un-pause. It may be simple but it is BS. I shouldn't have to do it. It wasn't a problem before and it should not be a problem now. This happens with other bluetooth devices as well such as my headphones (no pause button) and a bluetooth adapter (also no pause button) that is connected to an older home stereo that doesn't have bluetooth.
So here are my questions:
1) How can I know who is responsible for these updates? Is it AT&T? Samsung? Which 'higher power' can I direct complaints to? Honestly it feels like my phone's performance is purposely being compromised in an effort to push me to a new device. If this is the case then I'll purchase a cheap 'Sprawl-Mart' phone. At least I know I'll be buying a cheap, slow and crappy phone for $60 or $70 instead of a $750 'flagship' phone that is only good for 18 months.
2) Is it possible to set my phone to never even look for updates? I look at it this way; if I have to perform a clean flash every time my phone updates then I don't want the updates anymore. Since Oreo, none of the updates seem to provide me with any noticeable benefits.
Just a bump
Just a bump to get me back to the top of the pack. Hoping somebody has some answers for me.
Thanks,
PR