Related
Hi, I have a Samsung Galaxy nexus. There has been no physical damage or any exposure to water. Although I had dropped my cell phone a few months back which cracked my screen at the bottom-right corner( did not damage the display). Suddenly today the mic isnt working. When on a call the other end do not hear a word neither does any voice recognition software works. but when i switch on to loudspeaker the other end can hear my voice . similar is the case when i plug in headphones. I tried flashing and also did a factory reset. Nothing happened.
I am really worried as to what is the issue. Do is consider replacing the mic strip? Is there any cause behind this? I am not ble to figure out whether its a hardware or software issue . Please HELP.
[email protected]
juz got my m8. amazing build quality. amazing interface. I just changed from S4, and I can say the stock keyboard is much better!! S4 would get some lags on LINE app after awhile... but so far my m8 rock seems very good. I will wait a few weeks to see how it goes.
Separately, anyone encountered a very soft "click" / tick sound whenever the vibration haptic feedback? This happens once every so often (say every 10 vibrations will yield one "tick" sound). When i put my ear to the phone, it seems as though the vibrating motor itself is maybe not aligned, so there is slight rattle sound. NOTE: I have already switch off the SOUND click feedback. This is definitely a mechanical tick....super duper soft...
Is this common? Maybe in just ocd...
This phone is so perfect in all other ways...
Sent from my HTC One_M8 using Tapatalk
Yeah I have it too.
Had it on my S4 as well so I don't care.
Received my OP3 yesterday and immediately i noticed the vibration motor is kind of weak / noisy.
It makes some kind of rattling noise. Im not sure if this is normal or a defective unit so i was wondering if more people having the same issue.
Thanks :good:
Yeah, same here. It may have to do with the vibration intensity which may be set a bit high in OOS 3.1.2. But it's just my guess. You could try a ROM with a modifiable vibration intensity and see what the results are then.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
DonJuan89 said:
Yeah, same here. It may have to do with the vibration intensity which may be set a bit high in OOS 3.1.2. But it's just my guess. You could try a ROM with a modifiable vibration intensity and see what the results are then.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just seen the android authority review they state it as " Sub-par vibration motor ". I agree.
Somewhat agree, feel's very much like the same motor used in the opo. I don't actually mind it to be honest, phone may be silenced but instill can just about hear it when a notification comes in..
Yeah its not that much of a big deal, but im used to strong vibration motors i think i just have to get used to it
But it feels a little bit cheap on such a high end build
My S7E haptic feedback motor is strong but very muted/quiet. When I got my OP3 I immediately thought it was broken. It really disturbs me at the moment amd I hope I get used to it or find info about some units being defective so I can send it back for fixing.
Same here. But I had the side affect of knowing this behavior from my opo.
On my note 4 it was Better in terms of vibration intensity. The opo 3 is louder but generates less vibration. It feels and sounds cheap. Although I have to admit that for me it's not that big of a deal since I have my phone on the desk all the time and vibration for me is just a quieter way of informing me rather than having the sound on...
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
zat0x said:
Received my OP3 yesterday and immediately i noticed the vibration motor is kind of weak / noisy.
It makes some kind of rattling noise. Im not sure if this is normal or a defective unit so i was wondering if more people having the same issue.
Thanks :good:
Click to expand...
Click to collapse
I have the same issue. In fact it wasn't like this before. I like to set a very light vibration when I type and I've just noticed a hiss noise each time I press a button/key. I use OP 3 for a week and it definitely wasn't like this before this moment. It may be related to recent update I've got yesterday (but this seems unlikely), or the engine isn't so good than I thought. Anyway that's a bit disappointing. Is your vibration hissing too? I can hear it even at the lowest settings when the vibration barely noticeable but the noise is still present. Sounds very cheap, even my $100 Jiayu sounded better.
Mine feels the same, too rattly.
Do you think there are a few defective unites around or is it the same on all OP3's and a bunch of us are more sensitive to it than the rest?
I did take mine to the service center where they said that if the vibration motor was defective in any way, it would just not work at all and mine apparently has no issues.
mines noisy and kinda weak as well but i arranged with it just fine
I have the same issue too. The phone makes a rattling noise while vibrating and it is annoying!!
Ask for a replacement!!
I have this vibration issue too, but it occured after some weeks, not at day 1.
I did a service request, described the issue and sent it in.
After some days my OP3 came back, protocol said "no service needed, all test went fine".
Funny thing, the vibration issue was gone.
The next morning it was back again and now I'm in forum right now, looking for a solution...
Oh man, they used the same cheap and rattly vibration motor they used on the One, not the good one from 2. I just realized.
i think the buds are really good.... but I am now on my third pair, as the first two both malfunctioned, and i'm starting to wonder if its the buds or the phone. In . both cases, when new, I had equal stereo, but within a few days, I found the left side to be much quieter than the right side. One day they were fine. the next day they weren't, and they never returned to working properly. Identical experience on the first two sets. In both cases I had tried resetting them, removing and re-pairing them, messing around with loads of different galaxy buds and bluetooth parameters etc. Of course, I tried reversing them in the opposite ears, but it was the bud, not my ear! So now im on my third pair, and hoping they dont go wrong. Anyone else had these issues? Perhaps its the device itself?
enable disable absolute volume.
set volume to max on ur earbuds and never to change again. change the touch controls to some other function or lock it. control volume only via phone.
Sent from my SM-G975F using Tapatalk
jemfalor said:
enable disable absolute volume.
set volume to max on ur earbuds and never to change again. change the touch controls to some other function or lock it. control volume only via phone.
Click to expand...
Click to collapse
What is the basis for these being the solution?
ekerbuddyeker said:
What is the basis for these being the solution?
Click to expand...
Click to collapse
in case your buds were accidentally softened?
Sent from my SM-G975F using Tapatalk
They weren't.
Well I can say that the other end of a call not being able to hear you, and the crackling of presumably crappy bluetooth connection when phone in pocket does NOT improve with a different phone. I had to warranty my s10+ for the sprint signal issues and no change on either front. Getting ready to try and see if they'll swap out my buds now, but who knows with samsung nowadays
AestenD said:
Well I can say that the other end of a call not being able to hear you, and the crackling of presumably crappy bluetooth connection when phone in pocket does NOT improve with a different phone. I had to warranty my s10+ for the sprint signal issues and no change on either front. Getting ready to try and see if they'll swap out my buds now, but who knows with samsung nowadays
Click to expand...
Click to collapse
I had major issues with my buds after an update so much that I couldn't put my phone in my pocket without 2 or 3 second dropouts. I had to reset the buds a couple of times and now they are perfect again. Have you tried this?
Does the ambient sound work for you? For me and other users who reported the issue in Samsung forum it does not, meaning that it does not make any difference...
There was an update in the last few days. I've had much better luck since then.
Hey guys I have an issue with my galaxy Buds.
They are not loud enough and dont produce good sound quality for calls as well as for music, they also dont get along with bluetooth connectivity. Most of the time gets disconnected and produce uneven sound while they are connected to the device, people on the call do not hear my voice properly and clearly.
Have tried reset option but it does not work for me, face the same problems time and again.
Any solutions? Definitely not going for a replacement as the procedure will be lengthy as I got them in the pre order sale.
[email protected] said:
Hey guys I have an issue with my galaxy Buds.
They are not loud enough and dont produce good sound quality for calls as well as for music, they also dont get along with bluetooth connectivity. Most of the time gets disconnected and produce uneven sound while they are connected to the device, people on the call do not hear my voice properly and clearly.
Have tried reset option but it does not work for me, face the same problems time and again.
Any solutions? Definitely not going for a replacement as the procedure will be lengthy as I got them in the pre order sale.
Click to expand...
Click to collapse
Have you tried adjusting the volume of your buds? Go into the wear app, select your buds (my app defaults to my Gear S3), and go into touch pad. Change it to volumn up. By default they are set to like 1/2 the volumn they are capable of.
todd3835 said:
Have you tried adjusting the volume of your buds? Go into the wear app, select your buds (my app defaults to my Gear S3), and go into touch pad. Change it to volumn up. By default they are set to like 1/2 the volumn they are capable of.
Click to expand...
Click to collapse
Did that the very first day but I did not help. So have sold the buds after all.
ekerbuddyeker said:
i think the buds are really good.... but I am now on my third pair, as the first two both malfunctioned, and i'm starting to wonder if its the buds or the phone. In . both cases, when new, I had equal stereo, but within a few days, I found the left side to be much quieter than the right side. One day they were fine. the next day they weren't, and they never returned to working properly. Identical experience on the first two sets. In both cases I had tried resetting them, removing and re-pairing them, messing around with loads of different galaxy buds and bluetooth parameters etc. Of course, I tried reversing them in the opposite ears, but it was the bud, not my ear! So now im on my third pair, and hoping they dont go wrong. Anyone else had these issues? Perhaps its the device itself?
Click to expand...
Click to collapse
don't update them, I seem to think the update bricked my pair so now I just don't mess with updates..
Sent from my SM-G975U using Tapatalk
My buds were shipped to me the day the phone launched. From the beginning they seemed low budget in every respect except sound quality. Sound wise they are solid mid tier Bluetooth buds. Like many I had spotty connectivity while pocketing the phone. I had the right bud with less battery life/capacity then the left. And now my bud are being sent in to Samsung since the case no longer tops the earbud off without being plugged in. Fully charged case, insert dead buds, 3 hours latter buds still 0%. Light inside case never turns on.
My right one stopped connecting :/
hey,
does anyone else have a battery drain on the f3 update? my right bud keeps draining my case and itself.
The case was fully charged I left it and after 24h the case was dead and the right bud is at 30%, while the left bud is at 100%.
I tried resetting, cleaning case and even adding papers on top of right bud(bad connection) but nothing helped.
I know my bud is charging for sure because the light recognizes it but it seems unable to fully go out when in case(The bud).
Anyone had the same issue? anything that can help? I really like the buds but this issue that came with the last update(I THINK) is really a downer
Hi All!
I just got a new a70 5 days ago, it's performing very well, but i did notice one thing. Sometimes my quick touches when i just very quickly and barely touch the screen, the touch is not registered. I activated the factory diagnostic mode (*#0*#) and tested and got some interesting results. If i touch the screen quickly enough, the touch is not registered at all, even though i apply a substantial force. I can do this like 3-4 times out of 10 if i really try. I also tried it on my galaxy S5, and although I could reproduce the same issue, it was much harder to get it to miss a touch than on my brand new a70. I did try it with and without a screen protector and it didn't make any difference. I'm actually surprised, I didn't think I can touch the screen too quickly so that the sensor (or software?) fails to register it. My question is: is this an expected behaviour, or something that should be looked into? It doesn't really affect everyday use, but ever since i discovered this I'm now always having this weir feeling anytime i'm about to touch the screen that "is this touch going to miss?". So my questions are the following:
1. Is this behaviour normal?
2. Why does my S5 seems to be more "reliable" and is harder to get to miss a touch.
3. Is there a 'minimum touch duration' for these capacitive screens?
4. Anybody else who has A70 experienced this, could try it out?
(it was not very easy to reproduce at first. i started noticing it when i wanted to open messenger chats, that some of my touches missed. for the issue to be easily reproduced one would have to try and tap as quickly as possible, so that your finger touches the screen for the shortest time possible)
crazylachesis said:
Hi All!
I just got a new a70 5 days ago, it's performing very well, but i did notice one thing. Sometimes my quick touches when i just very quickly and barely touch the screen, the touch is not registered. I activated the factory diagnostic mode (*#0*#) and tested and got some interesting results. If i touch the screen quickly enough, the touch is not registered at all, even though i apply a substantial force. I can do this like 3-4 times out of 10 if i really try. I also tried it on my galaxy S5, and although I could reproduce the same issue, it was much harder to get it to miss a touch than on my brand new a70. I did try it with and without a screen protector and it didn't make any difference. I'm actually surprised, I didn't think I can touch the screen too quickly so that the sensor (or software?) fails to register it. My question is: is this an expected behaviour, or something that should be looked into? It doesn't really affect everyday use, but ever since i discovered this I'm now always having this weir feeling anytime i'm about to touch the screen that "is this touch going to miss?". So my questions are the following:
1. Is this behaviour normal?
2. Why does my S5 seems to be more "reliable" and is harder to get to miss a touch.
3. Is there a 'minimum touch duration' for these capacitive screens?
4. Anybody else who has A70 experienced this, could try it out?
(it was not very easy to reproduce at first. i started noticing it when i wanted to open messenger chats, that some of my touches missed. for the issue to be easily reproduced one would have to try and tap as quickly as possible, so that your finger touches the screen for the shortest time possible)
Click to expand...
Click to collapse
Yeah the touch on this device is horrible. Don't listen to fanboys, this device has a couple of issues other than the touch screen having an awful response time.
Check:
+
The SD675 isn't well optimized for most games, so it lags in most of them, while on the A50's weaker processor, the Exynos 9610, games work just fine. Most of the time, they work better on the A50 than on the A70.
And there's another issue with dark colors being turned off instead of dimmed, because the screen doesn't know the difference between "dark" and "totally black". I'm gonna demonstrate this later by comparing the A70 and A50 side by side.
The A70 has a stronger CPU than the A50. The A50 has a stronger GPU than the A70. The A70 has better battery life.
That said, yeah touch problems. I notice it all the time when browsing. Trying to tap on small links are not registered most of the time. I have to zoom in.
I believe it to be a hardware issue that is not fixable in software.