Related
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
mredmond2012 said:
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
Click to expand...
Click to collapse
I am having this same issue as well. It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly. I've had that happen where I have my hands in my pockets and next thing I know I've accidentally got my Facebook up and running and typed half a book in the status field.
Again, I know that sounds silly but I ask because it's happened to me before.
Concordium said:
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly.
Click to expand...
Click to collapse
That's fine, its an important clarification to make. But no, I am absolutely sure I have not changed any of the options unknowingly. As I said in the OP, ALL vibration/haptic feedback will cease to function entirely. I've often had it happen that in the middle of typing something, the haptic feedback for the keyboard will just go away. Immediately after this if I check the soft key buttons or test the vibration for notifications, none of these will produce any sort of vibration response either. Then randomly a few minutes, hours, or days later, all haptic feedback will just return. Its been an extremely strange and frustrating issue.
4nth0ny said:
It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Click to expand...
Click to collapse
For me, when the vibration stops working, it stops working for everything, even when the phone rings. But that's what I can't figure out: if it is a software or hardware related issue. I was having this problem on stock Sense, and I figured if it was software related, perhaps flashing a new ROM (in my case, CM7), would fix it. However it hasn't, so I'm beginning to think if it is indeed a software issue, it must be a bug somewhere very deep within the code, otherwise it has to be a hardware issue. But if its a hardware issue, I can't figure out why it would randomly stop/start working like it does, and the thing is, most (75%) of the time, it is working. Its just the other 25% that annoys the hell out of me. That's why I thought I'd ask and see if anyone else had experienced it or found any solutions.
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
infamousteeboy said:
Its a CM7 thing...Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
Well like I said before, I was having this problem on my stock Sense ROM.....
infamousteeboy said:
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Concordium said:
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Click to expand...
Click to collapse
Well I kinda had the same problem that he's run into on CM but I figured it out but I figured since he's had the problem on a sense ROM also then maybe its not the ROM but I jus went into everything that had the option to vibrate and turned them all on cuz I've flashed a couple ROMs and the vibration would be off I try not complain about anything about any ROM its a person hard work they've done for free I try to figure things out on my own as much as possible before I create a thread not bad talkin the OP but jus sayin you know?
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it. I think it's just a crappy vibrator. (If there's a better name than "vibrator", please someone tell me.)
I had vibration problems on my first Evo as well, it was never rooted. My second Evo was a HW004 and the haptic feedback was perfect - it was softer instead of the shock-like haptic feedback I've experienced with my 003s. My current and third Evo is also a 003, so I assumed it had something to do with the motor used in 003s.
I've just turned haptic feedback off. I thought I'd miss it, but I've gotten used to it. I still use have my phone set to vibrate for notifications and calls and I've seen fewer issues.
If you think you can go without, I'd suggest turning haptic feedback off. Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Sent from my Evo + MIUI using Tapatalk!
plainjane said:
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it...
...Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Click to expand...
Click to collapse
Yeah, its definitely not ROM related...I don't know if people aren't reading the posts, but I've said several times that this occasionally happened on stock Sense, both before and after rooting.
Dang. I didn't want to have to bring it in to get it fixed, but I guess that's what I'm gonna have to do if its a hardware problem...I was really hoping it was software related or if someone would know of a way to fix it so that I could avoid dealing with warranty services...I got suckered into the Best Buy warranty, and it turns out that even though they either give you a new or refurbished model, they make you turn yours in and wait 5-7 days for the replacement to come in instead of ordering the replacement and then doing a trade with you when it comes in. I already experienced it once before when my USB port broke... :/
Not being able to replicate the issue is my main concern since sometimes it works and sometimes it doesn't. Trying to get it to stop working at a time when I can actually run out to the store is gonna be a pain...And I really don't want to waste a trip to the Best Buy store only to have it start working again with me trying to tell the GeekSquad Agent, "I promise, I promise! It was broken just 5 minutes ago!!" I can't imagine how many of those they have to deal with....
I noticed this from the beginning, but didn't pay much attention to it because I thought it was my fault. But it happens again and again and I'm sure I don't do anything to cause this.
The problem: often when I haven't used the phone for a while the ringer volume is mysteriously turned down to a miminum level.
I now lock the ringer volume with an app, so this kinda solved the problem for me. Nevertheless I'm wondering if there are others who have this weird volume behavior.
BTW this is not the "classical" volume bug that was solved a few days ago with the OTA patch.
Can't say I ever have any problem like that. Might be an app on your phone that is turning the volume down? I agree it's definitely not the button bug since you can't change the volume with those buttons without unlocking the screen.
Sent from my Galaxy Nexus using XDA App
appelflap said:
I noticed this from the beginning, but didn't pay much attention to it because I thought it was my fault. But it happens again and again and I'm sure I don't do anything to cause this.
The problem: often when I haven't used the phone for a while the ringer volume is mysteriously turned down to a miminum level.
I now lock the ringer volume with an app, so this kinda solved the problem for me. Nevertheless I'm wondering if there are others who have this weird volume behavior.
BTW this is not the "classical" volume bug that was solved a few days ago with the OTA patch.
Click to expand...
Click to collapse
This might be an app. For example the 1Password reader app changes your volume based on some setting in the app.
yep. since day 1. no idea what causes and it's definitely no app causing it as i returned to factory settings to test it out and i still had the same issue
i honestly think it's the placement of the volume buttons but really difficult to be certain, as sometimes i will find the phone on vibrate and i am 100% i haven't touched the volume button.
At least now i am know i am not going crazy as this has been my one and only gripe about the phone
what app are you using to keep the volume locked?
Does you phone have the update? If not, then I'd assume it is the bug.
Why would I assume that. Cause the bug picks up noise on the volume keys, which control volume of everything, ringers, media, notifications, ect. The buttons control different things depending on what screen you might happen to be on. So it's possible that the bug could change your ringer volume as well.
coleburns said:
yep. since day 1. no idea what causes and it's definitely no app causing it as i returned to factory settings to test it out and i still had the same issue
i honestly think it's the placement of the volume buttons but really difficult to be certain, as sometimes i will find the phone on vibrate and i am 100% i haven't touched the volume button.
At least now i am know i am not going crazy as this has been my one and only gripe about the phone
what app are you using to keep the volume locked?
Click to expand...
Click to collapse
Ahhh thx, this was driving me bananas .. at least I now know that it can be mysteriously reproduced on other devices. I've tried to monitor my own actions but I'm also pretty sure I don't accidentally touch the volume keys. I didn't do extensive research because I just thought it wasn't worthwhile. But because I missed some calls lately because of this it is now pretty high on my annoyance list.
The app I'm using is Volume + (free version will do). Until now it seems to work well. It runs a background service and intercepts volume key presses events and pushes the volume back to a saved level. (Could have used that for the other volume bug)
mobilehavoc said:
This might be an app. For example the 1Password reader app changes your volume based on some setting in the app.
Click to expand...
Click to collapse
Always difficult to say, but I wiped my device a few days ago to root it and didn't install many apps yet (only twitter and thumb keyboard)
Luxferro said:
Does you phone have the update? If not, then I'd assume it is the bug.
Why would I assume that. Cause the bug picks up noise on the volume keys, which control volume of everything, ringers, media, notifications, ect. The buttons control different things depending on what screen you might happen to be on. So it's possible that the bug could change your ringer volume as well.
Click to expand...
Click to collapse
I've installed the latest update (build ITL41F). Maybe the fix doesn't cover all scenarios yet?
Sounds like interference to me. The fix added a 2ms de-bounce time which is ALOT. What frequency is your network on? You should try fixing it to 3g just to check if that fixes it. If it does its most likely interference.
I wonder if you have a bad ground connection in it somewhere (hardware fault).
If you can tell me the frequency your network uses (or your operator and i'll look it up) I can calculate the GSM burst time and see how it fits in 2ms. Ironically the burst arrives when you're about to receive a call so its turning the ringer down just before it rings lol
kam187 said:
Sounds like interference to me. The fix added a 2ms de-bounce time which is ALOT. What frequency is your network on? You should try fixing it to 3g just to check if that fixes it. If it does its most likely interference.
I wonder if you have a bad ground connection in it somewhere (hardware fault).
If you can tell me the frequency your network uses (or your operator and i'll look it up) I can calculate the GSM burst time and see how it fits in 2ms. Ironically the burst arrives when you're about to receive a call so its turning the ringer down just before it rings lol
Click to expand...
Click to collapse
My operator uses 900 MHz (for 2G) /1800 MHz (3g) . Operator is T-Mobile Netherlands
Btw I just accidentaly catched the bug doing it's nasty thing on 3g.
Anyone know where to report this?
Can't replicate this myself, however before submitting this as a bug maybe worth checking out the logcat trace around the time the volume is changing.
With the "SAV" issue, I seem to recall someone saw overrun errors in the log around the time of interference.
You may find something similar in the log or likewise there maybe some entries in there detailing a rogue process doing something a bit wacky which causes your issues.
Highland3r said:
Can't replicate this myself, however before submitting this as a bug maybe worth checking out the logcat trace around the time the volume is changing.
With the "SAV" issue, I seem to recall someone saw overrun errors in the log around the time of interference.
You may find something similar in the log or likewise there maybe some entries in there detailing a rogue process doing something a bit wacky which causes your issues.
Click to expand...
Click to collapse
SAV issue, overruns start on line 4
I'm also having this issue using: ICL35F.I9250XWKL2.
I can't find a way to reproduce it. If/when I find more info, I'll try to keep up to date.
From preliminary tests I've conducted, I now find Talk 4.0.2-235179 to be the culprit.
I have notification on and its tone is Silent. If I'm chatting with someone and that someone replies, the volume changes to 0???
I've written an app that polls the volume and notifies when it changes. Later today I might post the code.
Talk in Silent
Finally have a found the real reason. When Talk is set to:
Notification: System Bar;
Sound: Silent.
When a message comes and the chat is in foreground, the volume is changed to level 3.
The program I've made, once started, poles the sound level each 5 seconds and when it's different a notification appears.
To this post I've attached the .apk, its source and a silent ringtone to overcome this bug.
DoomFragger said:
Finally have a found the real reason. When Talk is set to:
Notification: System Bar;
Sound: Silent.
When a message comes and the chat is in foreground, the volume is changed to level 3.
The program I've made, once started, poles the sound level each 5 seconds and when it's different a notification appears.
To this post I've attached the .apk, its source and a silent ringtone to overcome this bug.
Click to expand...
Click to collapse
Thanks for your detective work. This is exactly what was causing my volume to seemingly change at random. It was especially annoying because some days I use gtalk quite a bit and other days not at all.
I linked to your post and this thread on the relevant Google Code Android bug report that someone had created back in December for the same issue. It can be found here if anyone cares to star the issue in hopes of giving this bug more exposure: http://code.google.com/p/android/issues/detail?id=22579
I can confirm the problem. It only happens with Talk in the foreground running and with the silent notification on.
Thank you very much, I got the new One X and was wondering if it was a software bug in HTC software....guess not
So i have been reading here alot on the Q&A and seem to have found relevant posts/threads mentioning this issue..i don't exactly know if this is isolated or its from a faulty batch or its really a stupid feature of the One X..currently i am pissed so great on this phone..sorry to some who loved this phone but this phone is PITA for me..
here are the relevant threads i have gathered..and some people discussing the same issue i have..
thread 1
thread 2
thread 3
on those threads the issue of "Sensor still staying up even the call is already done" is imminent and in one case it is using VIBER that this issue arises..well on my issue i don't have anything installed on my Phone so i am just using my stock Call app(HTC one..)and when i make calls this issue just repeats is self..
to be more precise
-when i make a call, it will turn on sensor then it will immediately turn off screen even if the phone is not even near my ear..
-after the call the sensor is still lit up so i have to make a dummy call to turn it off and on this instance the screen again shuts itself off and sometimes its hard to wake it up..
if someone can provide a solution to this much better..or can explain to me what the heck is this phone made off..and what the heck this phone is doing..i have tried almost every kernel and reverted to stock via RUU still the same friggin issue persists..
hello everyone , so i use to have this bug back to kitkat also but it wasn't happening as often as it doesnt now that i have lollipop rom installed on my galaxy tab s T705 , the issue is with touch key lights which stays on even when i have them always off from settings , they act super weird when they are in that mode , they go off few sec after screen is off and if i shake the device they go on again as it looks like they are connected to accelerator sensor or something lolz ,the solution is super easy tho just hit the power saving on and then off again and they work normally again i heard some other ppl dealing with same issue but i wanted to know if there is a perma solution for it or not , im sure its a software issue but is there a way to fix it ?
Install a custom rom like cyanogen or something stock based.
I have the same problem. I usually have it set to turn the lights off after 6 seconds, but after a couple of days they don't work anymore. I would change the setting to off, then on, then back to 6 seconds, and it'll work again. After a few more days, they stop. I haven't seen a permanent fix for this.
Sent from my SAMSUNG-SM-G925A using Tapatalk
Same for me. Would usually opt to have the buttons backlight always off, but randomly it starts actin like always on, although the settings remains 'always off'. Toggling the setting to anything else and back to always off fixes the problem temporeraly.
Im running stock swiss lollipop on my t700.
Yes, this is driving me nuts too! I hope they resolve this in the next update and soon!
Sent from my SM-T700 using Tapatalk
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
Me too have the touch key settings to always off and found the same problem.
In my case I think it only happens when I plug the Tablet to AC.
Did this happen to anyone under another circumstances?
Thanks in adavance!
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
TLAgnesB said:
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
Click to expand...
Click to collapse
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
TLAgnesB said:
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
Click to expand...
Click to collapse
Yes but you will need root.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
I heard that there's a new update available for the Tab S. (I already returned my tablet before my 30 days to get a full refund.) Did any one get the new update, and if so, did it fix the issues like this touch key light?
Hey,
I had this problem on the original KK software - upgraded to Lollipop a few days back and I still have the bug... in fact, it is even worse! Occurs more frequently than on LP.
I wouldn't mind leaving the lights on all the time, but they're so damn BRIGHT, and there's no way to adjust the backlight intensity!
Cheers,
Su
I found this solution on another forum...
If you enable smart stay, the touch key light duration will work properly.
Any further movement on this?. I've found that if I take my tab out of the book case the problem goes away. Seems like it's a bug with the case sensor.
No movement that I'm aware of. I'm really frustrated that there hasn't been a fix after all this time. I'm holding out hope that if there is ever an update to Marshmallow, that the issue will go away. Interesting observation about the case -I have a book case on mine. I'll remove it and see what happens...
I am not entirely sure if I'm tripping, but I seem to be missing phone calls pretty damn often. I think I recall at one point I randomly grabbed my phone to have it by me and noticed that someone was calling me but it wasn't ringing at all, though the screen did light up. I made sure my settings do have have "Do Not Disturb" mode on. I have the CPH2451 and running stock with latest OTA A.10 update. After doing a brief Google search, I see that OnePlus has had issues in the past but those are from the OnePlus3 and OnePlusNord so I am not sure if that's still relevant in this day and age.
Anyone experiencing something similar or have any clues as to what might be going on?
Edited: Fat fingered the model #. Fixed.
simplicityy said:
I am not entirely sure if I'm tripping, but I seem to be missing phone calls pretty damn often. I think I recall at one point I randomly grabbed my phone to have it by me and noticed that someone was calling me but it wasn't ringing at all, though the screen did light up. I made sure my settings do have have "Do Not Disturb" mode on. I have the CPH2541 and running stock with latest OTA A.10 update. After doing a brief Google search, I see that OnePlus has had issues in the past but those are from the OnePlus3 and OnePlusNord so I am not sure if that's still relevant in this day and age.
Anyone experiencing something similar or have any clues as to what might be going on?
Click to expand...
Click to collapse
This might be obvious to you, so just ignore if you know this.
When holding your phone in your hand like you're texting in portrait mode, there's a switch top right and on side of phone.
Adjust the switch so it's down.
Ive experienced this, even after swapping to 2449.
Seems theres a couple settings that revert on reboots for some odd reason.
Just go into the phone app settings, notifications and reset thr ring tone and all set after 2 times doing it ... annoying?? damn right!... but at least its fixable ....
kevp75 said:
Ive experienced this, even after swapping to 2449.
Seems theres a couple settings that revert on reboots for some odd reason.
Just go into the phone app settings, notifications and reset thr ring tone and all set after 2 times doing it ... annoying?? damn right!... but at least its fixable ....
Click to expand...
Click to collapse
That's so dumb... The more I use this phone, the more I get buyer's remorse.
I haven't restarted my phone since I got it I think but I'll try that and see if the issue persists. Thanks!
Edit: Any word if OnePlus is aware of this and plans on fixing it? If not, perhaps I should forward this to them.
simplicityy said:
That's so dumb... The more I use this phone, the more I get buyer's remorse.
I haven't restarted my phone since I got it I think but I'll try that and see if the issue persists. Thanks!
Edit: Any word if OnePlus is aware of this and plans on fixing it? If not, perhaps I should forward this to them.
Click to expand...
Click to collapse
don't know if they are aware. just to add to the weirdness of it... for me... after the second time, the setting sticks...
i have this problem with my 8 pro, the phone doesn't ring and i think it goes straight to VM? seems like something broke with one of the latest OP updates?
There's no such version as CPH2541.
And here it works perfectly. Factory reset and try again.