not if I'm in the right place to post this but,,,,,, what happens is that my nexus 5 ceases to vibrate completely for a few hours, whether or not activated the vibration, I have it set to always vibrate, calls, messages, etc.
but like I said only stops vibrating as in a few hours back the vibration, I've made a reset to factory, turn off and turn on the phone, but that does not help and does not happen every day but sometimes from week to also Signed in safe mode to verify that an application is not what is causing this but nothing I can not change because the lost with the guarantee that the holes for the increased volume ,,, any idea why this happens and any solution, thanks
You could return to stock, flash the factory image, and hope it solves the problem. But I'm guessing not and it's a hardware issue
Related
Hello all...
just got my polaris last month. everything was ok, the phone was NEVER been dropped or what so ever. i treated it like my baby. but sometimes something weird happened. my polaris keeps vibrating when there is incoming message. and it keeps vibrating until i have to soft reset it. anything else wont do. the X button, task manager etc. everything in my polaris is original. anyone had this problem before? please help!
thank you
It has happened to me a couple of times.
I've no idea why, I have also treated my phone gently as is my custom with all my technology. There do not seem to have been any side effects though and it has only happend twice since i got the phone three months ago.
I don't think it's much to worry about.
*fingers crossed*
Just flash new rom, it helps
paulcoul said:
Just flash new rom, it helps
Click to expand...
Click to collapse
No, that won't help. Got the problem 3 times now, i think, in more then 6 months. Got the problem with the original, bepe and with the latest udK Diamond ROM. Just soft-reset and wait till the next time it happens
If your phone gets stuck vibrating, you can turn off the vibration by triggering an event that causes a vibration (instead of having to reboot the device). I used to have to send myself a text message (I have my phone set to vibrate for incoming texts) and that would do the trick. Now with the latest S2U2 builds with the volume control enhancement, I just use that to turn vibrate on and off (it will vibrate when you turn it to vibrate) and that does the trick as well.
hmm...i guess there is no absolute solution to this problem.
My HTC Cruise got splattered with beer last night and now its constantly vibrating, i mean...even if i turn off the device it still does it. Tried soft and hard reset, dry, clean, dry again and nothing happened, still the same. It only stops when i remove the battery of course.
The weird thing is that it vibrates in a less strong way than normal vibration. is this a known issue? How do i solve it? doest it have anything to do with the water detector on this type of phones?
Please, someone help me its really anoying to have a phone vibrating like that in my pocket lol. Thank you in advance.
Hello Guys,
I started to have problems with my wing and end up in three-color bootloader screen. I can tell you that I am not playing around with my phone. I do not even install any software not to risk its basic phone functionality since I am using this phone as a business phone. So, no crazy rom flash or etc has been done prior to this problem.
My phone started to have problems with answering calls last week. When it was ringing, it was keep ringing and I was not able to take the call even though I was pressing every possible buttons on the phone. It was locking.
I noticed that phone was locking the buttons too. So, I selected "do not lock buttons when the device is off". But, this does not have any effect. Phone was keep locking my buttons.
Last night, I noticed that my phone was unresponsive once again as usual, I soft reset the device, and it booted to the three color screen (I think you guys call this bootloader screen?) where it says "IPL 4.26.0002" and "SPL 4.26.0000". Tried to soft reset probably another 10 more times. same thing...
I took out the battery, went to sleep. Put back the battery in the morning, it booted to the OS and phone is running. But none of the hard buttons were working. It also hangs up the incoming call after first ring. I soft reset the device once again and it went back to the three-color screen.
I went to the Tmobile website, and found that there is an upgrade ROM. I downloaded and ran that program. It said that it installed it to the device successfully, and then the device rebooted itself. Guess what, back to the three-color screen.
I have been reading your forum since morning, and read a lot about brick phones etc. I tried couple of the techniques for recovering brick phones, but nothing helped. Hopefully, someone here can tell me what is going on, even though if the answer is to throw the device to the trash.
Additional Observations
It looks like nobody is interested
I have other observations.
- When "do not lock buttons" is checked, phone starts acting even more weirder. it generates keystrokes by itself. Camera starts taking photos.
- If the battery of the phone is out at least an hour (I don't know why), phones boots fine. If you soft reset at the moment, it will always goes back to the three color bootloader.
Can this be a virus?
The problem started about a week ago. Whether it was coincidence or not I don't know but around the same time the software updates through OTA update and u replaced the battery (Zerolemon 7000).
Anyway, what happens is that if my phone is asleep and I get a call or text, the screen comes on, but I can't answer the call or text (screen is unresponsive) until I tap the power button twice to turn the screen off and then back on. At that point the screen works perfectly.
I've tried clearing the cache and changing batteries but it didn't change anything.
Any ideas? I'm completely stock and unrooted.
Sent from my SCH-I535 using Tapatalk 2
Hi everyone!
I have a situation here. I have this old A106, i am using as a secondary phone. Upgraded it to lollipop 15-20 days back and since then something or the other is happening with the phone.
First was the proximity sensor, the screen would shut off right after i dial a number and wont come up unless i press the power button. The proximity sensor is not functioning at all i guess.
Secondly, since this morning, I am unable to receive any calls on my phone. The phone rings, I swipe it to the right but nothing happens and the icon comes back to the middle, and within a few seconds the call gets disconnected.
Tried factory reset/data wipe from recovery but it didnt fix the issue. Any help would be highly appreciated.
Thanks, Have a good day!
Now this doesn't happen all the time every time, but usually around a notification and the screen is off, I go to hit a button to turn on the phone and it doesn't respond but the touch-keys are backlit. If Always-on Display is on, the screen is black regardless, not even showing the time or notifications. The only fix is waiting ~10 seconds for the phone to respond, which in some cases can be the difference between a missed call.
Now, seeing Always On Display off like that while it should be on made me think back to when I saw some sort of Nougat optimization setting that allowed me to select Always On Display, and as far as I remember, I did. That makes me think this process is killing AoD and it is taking that long to start back up, where the phone won't unlock until AoD (is back on and) can confirm that it's trying to wake up out of that state.
However, I don't believe this is the issue. I have turned off AoD and the issue still happened directly afterward, after a Messenger notification. This is stock firmware, however it is not factory firmware. I believe I downloaded it from Sam-Mobile, and they had the 7.0 Nougat upgrade that I would have gotten OTA with the factory firmware anyway.
Somehow I don't think it's the flashed firmware that is the problem, however please let me know if that's a possibility.
While the phone (or whatever) is hanging, I can still hold down the power button and I will feel haptic feedback as if the power menu has opened, and when the phone responds the power menu will be open, so the phone does still receive input. It just doesn't seem to act upon it or wake the screen properly. Is this perhaps merely a known Nougat bug or is it a glitch with my flashed stock firmware?
I'm sorry I don't have much more information. I do have Greenify, but I don't think that can or is set to disrupt anything that would affect the phone waking, or that would hang the OS, homescreen or whatever it is.
I haven't done other troubleshooting because I don't know what direction to attack this from, and that is why I have come here.
Help please!
Thanks in advance. :good:
UPDATE: It seems to happen directly after my screen shuts off from being on. So, if a notification wakes my phone but I don't interact with it in time and the screen goes off, when I press the power button it won't respond for ~10-15s. That's all I've really noticed... Anyone else have this problem??
BUMP.
Also, the same thing happens if I press the power button on my phone (by accident) and then go to turn it back on almost immediately - it won't respond for a while.
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
*Detection* said:
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
Click to expand...
Click to collapse
Won't be factory resetting unless I plan to root or something. I'll fiddle with the keep screen off setting that I do have on, and I highly doubt gestures would affect it but regardless I haven't enabled or used any. Thanks for the reply.
So the "Keep screen off" setting didn't affect anything. I turned Always On Display back on and I see the same issues. However, now sometimes I notice when I lock my screen or it shuts off, sometimes the AOD will appear and then quickly disappear, and stay in this hanging state for 10-15s. Then, if I haven't touched it during that time, the AOD will reappear. Any ideas? :/
So nobody else has this issue? This is still a problem, even if I press the power button and sometimes I'll want to turn it back on again as I just remember something to do before putting the phone away, it hangs on black for too long to be useful in that moment. The only potential solution is a factory reset?
Even if I lock the screen... If I try to turn it back on too soon, and I think it's specific timing... I have to wait 10-20 seconds. Sounds and vibrations still work.
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Kilva said:
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Click to expand...
Click to collapse
This happens for me also as a point of interest.
I am hoping that O solves it, since the monthly updates have never helped.
I haven't had this happen since upgrading to Oreo a week ago, so far so good!