So, I pick up my device from the wireless charger, a minute later, it buzzes.
I put the device down on my desk, it buzzes every minute or so. Yet, there's NO notification that tells me something needs attention.
The constant buzzing is driving me nuts. If I have the sound on like I do at home, it's accompanied by the default sound every time a buzz happens.
Anyone know what's going on? And, can I stop it?
No, turning off the device and putting it on my pocket isn't an option because I need to be using the device.
It sounds like a replacement :-/
sackynuts said:
It sounds like a replacement :-/
Click to expand...
Click to collapse
I don't think there's anything wrong with the device, I think it's got an issue with something running that is making it buzz so often but for the life of me I can't figure out what it is that's running.
***FIGURED IT OUT*** It was the software update that I paused. Seems the S8+ kept buzzing to tell me that it wasn't done. It is MEANT to be annoying***
Fixed the buzzing by downloading the rest of the update and not applying it.
Related
[Q] This auto-dim "bug" is completely unacceptable...and is driving me beserk
Basically, if I turn autodim off and turn the brightness up over 50%, the screen shuts off and when I press power to wake, flashes for 1/10 of a second and then turns off. The only way I can use my tablet with brightness over 50% is when it is plugged in.
How has this not been fixed yet? It's got to be a software issue right? This is completely and totally ridiculous.
Chief85 said:
Basically, if I turn autodim off and turn the brightness up over 50%, the screen shuts off and when I press power to wake, flashes for 1/10 of a second and then turns off. The only way I can use my tablet with brightness over 50% is when it is plugged in.
How has this not been fixed yet? It's got to be a software issue right? This is completely and totally ridiculous.
Click to expand...
Click to collapse
I don't have this problem. I use it at 75-100% most of the time on battery.
I have zero idea what it could possibly be. I'm on the verge of returning and just washing my hands of this thing. It's a shame because the Galaxy Tab will definitely be at a higher price point.
exchange it. Something is wrong. No one else is reporting this issue. I've had my ft stock, running Paul's rom and prime, and all the different kernels. No such problem. Sounds like a hardware fault.
crater said:
exchange it. Something is wrong. No one else is reporting this issue. I've had my ft stock, running Paul's rom and prime, and all the different kernels. No such problem. Sounds like a hardware fault.
Click to expand...
Click to collapse
This.
I get that people can get frustrated when something's wrong but the store should always be the first point of call if you've got a problem. If you get it exchanged and it still has an issue, THEN you get to post about it and complain. Even so, at least post in the right forum...
I have this problem and I've seen 2-3 other people with it, so its not that common by the looks of it. I tried to find a solution but I am RMAing mine as there isnt a fix at the moment.
cpalmer98 said:
I have this problem and I've seen 2-3 other people with it, so its not that common by the looks of it. I tried to find a solution but I am RMAing mine as there isnt a fix at the moment.
Click to expand...
Click to collapse
tryed to mimic the issue here and it does not have that issue, its gotta be a bad unit. these things happen , it just sucks when it happens to u
Hi, I have an HTC Inspire rooted with the newest Cyanogenmod 7. Out of randomness, my phone is now deciding it wants to vibrate during calls, the entirety of them. Also if I adjust my volume, it will be stuck playing notification sounds as if I were getting a call. This happens even if I lock the phone. If I put my phone on silent, this fixes everything, but I can't have that; What can I do? This is a completely fresh CM install.
There is a setting for it. Not sure where. Try in telephone, settings and uncheck vibrate in call ir whatever it's called.
Sent from a dream.
Teichopsia said:
There is a setting for it. Not sure where. Try in telephone, settings and uncheck vibrate in call ir whatever it's called.
Sent from a dream.
Click to expand...
Click to collapse
That's not the problem at all. The phone is vibrating nonstop. Not just once when answering and hanging up. I've disabled these options and it still continues to vibrate.
c1o5ry1991 said:
That's not the problem at all. The phone is vibrating nonstop. Not just once when answering and hanging up. I've disabled these options and it still continues to vibrate.
Click to expand...
Click to collapse
take it to one of those pure romance parties, im sure you could sell it for $300+ with that feature!!
on a serious note, it is sounding either like it was a bad download or bad flash. I wouldnt rule out hardware either. Has the phone ever been dropped or get exposed to water?
edit: did some reading and it's sounding like there is possibly a short in the vibrate circuit. is it under warranty still?
Darunion said:
take it to one of those pure romance parties, im sure you could sell it for $300+ with that feature!!
on a serious note, it is sounding either like it was a bad download or bad flash. I wouldnt rule out hardware either. Has the phone ever been dropped or get exposed to water?
edit: did some reading and it's sounding like there is possibly a short in the vibrate circuit. is it under warranty still?
Click to expand...
Click to collapse
It is, and I'll be taking it back if a reflash and then unroot doesn't fix it. However what about the ringing issue?
Well, a reflash worked. If this happens again however, what the heck could it possibly be?
c1o5ry1991 said:
Well, a reflash worked. If this happens again however, what the heck could it possibly be?
Click to expand...
Click to collapse
could be a number of things. if it happens again i would just return it to stock and get it replaced. diagnosing things like this is like trying to fix a car over the internet, it mostly just involves people guessing until you get lucky or break it more
i have a LTE device (s-off, rooted, stock, 4.2.2) which is working great, only one annoying issue: sometimes, maybe once in two weeks, my device just turns off during charging at night while i sleep. i couldn't guess the reason for this strange behavior so far, but it can be really annoying, since i depend on the alarms set. it was the same when i was still on android 4.1.2.
is there a way, a log hidden somewhere or something to help me track the issue? anybody?
thanks!
Could the reason be, that it is getting hot and shutting down to prevent the phone get damaged?
Have heard of such things already, so maybe investigate in this direction.
i doubt, since i've had it it's never been even warm. and this always happen at night when nothing special is happening on the device. i thought maybe it's the automatic titanium backup, but the days are wrong...
is there any special log on the device that covers reboots and crashes to look at?
Don't know about log.
If you charge it, when its happening, it can get warm after some time.
Thats the only idea i have.
yes, it's always charging when it happens.
My Nexus 5 vibrate motor seems to randomly stop. Usually, it stops working for just a few seconds at a time, but sometimes it stops for more than just a few seconds. It started randomly one day, and I haven't been able to tie it to a specific app yet, and it didn't coincide with the installation of a kernel or ROM.
I'm running rooted stock Lollipop with elementalX kernel (2.03).
I've tried pushing on the back, since some people have issues with the vibration motor not making good contact with the rest of the phone, but it seems that doesn't really do anything for me. It seems to help occasionally, but not necessarily.
Sometimes turning the screen off and back on helps, but sometimes not either.
Unfortunately, the inconsistency is making it difficult for me to figure out what the problem is. Could it just be a dying motor?
You can open it up and reseat the vibration motor on its sticky pad if you're not worried about the warranty. Alternatively, some of those with the issue have reported success giving the phone a good smack.
bblzd said:
You can open it up and reseat the vibration motor on its sticky pad if you're not worried about the warranty. Alternatively, some of those with the issue have reported success giving the phone a good smack.
Click to expand...
Click to collapse
Thanks for the ideas
I did try reseating the motor, and I thought it was going well, but after about a full day or so, I was hit with a non-vibrating motor again Turning the phone off and back on didn't help, but shaking it a bit seemed to do well
I have tried giving the phone a good smack, but it seems like a temporary thing. I'm mostly afraid I might miss a call, message, or vibrate alarm if I run into this problem with the phone in my pocket
And it happens with stock kernel as well, correct? If it has been less than 1 year you could RMA.
chronostorm said:
Thanks for the ideas
I did try reseating the motor, and I thought it was going well, but after about a full day or so, I was hit with a non-vibrating motor again Turning the phone off and back on didn't help, but shaking it a bit seemed to do well
I have tried giving the phone a good smack, but it seems like a temporary thing. I'm mostly afraid I might miss a call, message, or vibrate alarm if I run into this problem with the phone in my pocket
Click to expand...
Click to collapse
I had this problem as well and still encountering it sometimes. Don't worry about a missed call though. My vibration completely stopped working and a reboot didn't help, however a call made the vibration work again lol and it has been working since. Fingers crossed same **** doesn't happen again.
I'll try to keep this short yet detailed.
So I basically flashed Custom ROM on my whyred 2-3 years back.
RR Rom and I have no Vibration since then. (I might have wiped incorrect partition Idk, some people said something about the device tree I've no idea.)
Lemme answer few questions that will pop up in your minds.
Yes I checked every setting, everything's ON.
QC Test failed for vibration.
I got my vibration motor changed as well.
I flashed fastboot ROM as well.
Flashed custom kernels as well.
Multiple ROMs - Pixel, Lineage, RR, Evolution X.
Nothing worked for me.
It's been more than couple of years now. Same happened with Kenzo it still work but without vibration.
PS - I've other devices that work fine on custom ROMs, probably because I've been more careful.
PPS- Vibration comes back sometimes but that's literally like once a year.
Sounds to me, like there is not enough power to trigger the actual motor, based on the fact you've tried so many roms and had same problem for so long.
This can be caused by custom roms, or maybe the motor is just old n cranky, (ok, you changed it) and needing a wee shove to trigger it into moving again, after being still for so long.
Think ps3 controller, if you can open your fone, and put the tiniest bit of wd40 on the motor spindle, then lightly turn it by 'finger' lol, that should do the trick if it's not software related, and it works when it CAN rather than when it wants or is told to.
Just a suggestion. If you do go to look and do the wd40, test the power on the red and black cable while instructing fone to vibrate, if all is good, it's the roms.
Edit: Oh, and it's a good idea to look into notification settings, see what permissions are granted to vibrate/sound/on off? Some apps like to change settings we make being not so obvious. Sometimes denying other apps can affect such stupid things.
Yup I got it, but I'm an electronics guy... If you can confirm if there is power TO the motor (set ringer to vibrate then call yourself, while testing power)... yup....if you cant get power to motor, backtrace the power till you find it.
Its software after that.
.
Pachacouti said:
Sounds to me, like there is not enough power to trigger the actual motor, based on the fact you've tried so many roms and had same problem for so long.
This can be caused by custom roms, or maybe the motor is just old n cranky, (ok, you changed it) and needing a wee shove to trigger it into moving again, after being still for so long.
Think ps3 controller, if you can open your fone, and put the tiniest bit of wd40 on the motor spindle, then lightly turn it by 'finger' lol, that should do the trick if it's not software related, and it works when it CAN rather than when it wants or is told to.
Just a suggestion. If you do go to look and do the wd40, test the power on the red and black cable while instructing fone to vibrate, if all is good, it's the roms.
Edit: Oh, and it's a good idea to look into notification settings, see what permissions are granted to vibrate/sound/on off? Some apps like to change settings we make being not so obvious. Sometimes denying other apps can affect such stupid things.
Yup I got it, but I'm an electronics guy... If you can confirm if there is power TO the motor (set ringer to vibrate then call yourself, while testing power)... yup....if you cant get power to motor, backtrace the power till you find it.
Its software after that.
Click to expand...
Click to collapse
Hey, thanks for the reply.
I'm also an electronics guy, and I'll definitely get the motor power checked.
Yesterday only it randomly started working but it was so weak I knew it wasn't getting enough power. But not sure how.
About the setting vibration is on everywhere and There's no app which may cause any sort of problems. I'm pretty sure it's either the kernels or something else entirely.
Thanks again.
Could be time to get a new battery, or look at one of my teenage hacks:
Redmi Note 9S weird Battery Issue
Hello, My phone problem is, whenever i charged my phone to any certain percentage like 80%, 90%, 100%, and unplugged the charger and using the phone, first 5-10 minutes its consume 5-6% battery and first 1 hour of using its consume 10-12%. This...
forum.xda-developers.com