Related
Hi guys,
When I get a message the phone vibrates 3 times, like normal. But sometimes randomly it vibrates 1 time and then unlimited vibration. Until I get it out of my pocket and press the powerbutton so the screen goes on again. When the screen is on again the phone resumes the 2 vibrates. Very strange. I had it on multiple roms with different radio's. I don't use TF3D but HTC Home Plugin VGA edition.
I've experienced the same issue you speak of with the stock ROM, and I haven't found a solution or cause yet either.
I think it was this what caused my phone to sometimes go out. Because the vibration consumed all the power.
Do you use Touch Flo?
_MsG_ said:
Hi guys,
When I get a message the phone vibrates 3 times, like normal. But sometimes randomly it vibrates 1 time and then unlimited vibration. Until I get it out of my pocket and press the powerbutton so the screen goes on again. When the screen is on again the phone resumes the 2 vibrates. Very strange. I had it on multiple roms with different radio's. I don't use TF3D but HTC Home Plugin VGA edition.
Click to expand...
Click to collapse
That would be the angry bee. It is something that just happens. I've had it so bad that I have had to soft reset the phone. It only happens to me every great once in a while. However, I haven't run the stock rom since about 2 hours after buying the phone.
has happened to me twice now.
ive had the phone about 2 months.
Dane Austin said:
That would be the angry bee. It is something that just happens. I've had it so bad that I have had to soft reset the phone. It only happens to me every great once in a while. However, I haven't run the stock rom since about 2 hours after buying the phone.
Click to expand...
Click to collapse
I've had it happen to me a few times and had to soft reset it to make it stop. It doesn't happen too often, so I haven't been too worried about it.
I've had it happen when I launch an application just as it is starting to vibrate to signal a notification.
Do you guys also always have it as the second vibration? When it hangs it always is the second vibration at me. And when I press the screen again he makes 2 after it again.
I had a similar issue with the initial stock rom - my wife messaged me in the middle of a meeting and my phone would not STOP VIBRATING. Since it was on the desk, it buzzbuzzbuzzed really loud.
Now I'm on the Energy 3.0 rom and have not had an issue. Even with the updated leaked stock rom I didn't have the issue.
I discover that it only vibrates wrongly when I have the screen off. Pretty annoying though.
Don't we use some kind of stuff in common?
I use:
HTC Home VGA Edition for front end instead of manilla
HomeScreen++ for the handy shortcuts
I checked some things again, I am not 100% sure but I think it was HomeScreen++ that caused the problems here. The exact settings: at the Tools tab "Lock if Display is Off and vice versa, which didn't work anyway at the touch pro (did work on htc's I had before though), but I checked it off and now it still rings 3 times and no less or more. Hope this was it.
I do not use HomeScreen++ and it happens to me at least once a day, sometimes twice. Mine always seems to happen on the third vibrate, it will do the first two and then the third one just stays on. I press the power button for the screen to come back on and it stops.
I have it too sometimes.
EnergyRom 3.0
And you guys have something that auto lock the screen when you press the power off button? Or do you lock the screen before pressing the power button? Because here it seems to have something to do with the locking in combination of the standby mode (screen off)
I got a used HTC sensation XE with audio beats, with WiFi not working (GB was installed). Wifi & Teathering services always remained on "Error" when wifi turned on. Bluetooth, SIM services all were doing good. Used it in this condition for 2~ days, all went fine exept I once found it powered off while it was on wall charging.
Then I upgraded it to ICS downloading Stock ICS ROM from this thread. Which was isntalled successfully and the WiFi started to work.
It worked fine for 2 days, except my phone restarted on its own once or twice. At that moment i was using 340 MB of internal storage for apps and 750 was free. One night i was playing "Cut the Rope" and my phone prolonged a game sound and turned off, I removed battery and replaced it and turned on, but nothing happened, it remained off. Attached it to charging but no response. I left it there and after about an hour charging light turned on and it powered on.
From that moment, Phone often shows message "Low Storage Space", Hangs and then turns off. And fails to turn on again, sometimes for 24 hours. I did a "Factory Restore" from boot loader (power + voluem dwn), but its still behaving same.
Lattest: It turns on by pressing power button for 20 to 30 sec. Sometime goes upto lock screen and turns off, sometimes turns off on first screen and most of the times dies at audio-beats screen (after or before change is screen brightness). Remains dead for some time then again to same position.
Any expert openion/ experiance/ etc....
I don't have option of replacement. What to do? :crying:
khaled_j_k said:
From that moment, Phone often shows message "Low Storage Space", Hangs and then turns off. And fails to turn on again, sometimes for 24 hours. I did a "Factory Restore" from boot loader (power + voluem dwn), but its still behaving same.
Lattest: It turns on by pressing power button for 20 to 30 sec. Sometime goes upto lock screen and turns off, sometimes turns off on first screen and most of the times dies at audio-beats screen (after or before change is screen brightness). Remains dead for some time then again to same position.
Any expert openion/ experiance/ etc....
I don't have option of replacement. What to do? :crying:
Click to expand...
Click to collapse
But it never turns off just sitting at the bootloader or fastboot screen? Doesn't turn off while doing a factory reset? Only when trying to load software and activate hardware booting into the OS?
MS Gray Man said:
But it never turns off just sitting at the bootloader or fastboot screen? Doesn't turn off while doing a factory reset? Only when trying to load software and activate hardware booting into the OS?
Click to expand...
Click to collapse
Yes it didn't turned off sitting idle in bootloader. But it completed its factory reset in 3 restarts; 1st right after loading stock, 2nd configuring apps 10/36 and 3rd at 23/36. Then 4th time it died on fresh Lock Screen.
NOTE: I removed SIM, SD Card in the very beggining of the problem.
khaled_j_k said:
Yes it didn't turned off sitting idle in bootloader. But it completed its factory reset in 3 restarts; 1st right after loading stock, 2nd configuring apps 10/36 and 3rd at 23/36. Then 4th time it died on fresh Lock Screen.
NOTE: I removed SIM, SD Card in the very beggining of the problem.
Click to expand...
Click to collapse
I would try replacing the battery... it's about all that's left as it appears your phone is locked and more or less all stock..
Cuts down your options for things. Any sign of moisture exposure?
MS Gray Man said:
I would try replacing the battery... it's about all that's left as it appears your phone is locked and more or less all stock..
Cuts down your options for things. Any sign of moisture exposure?
Click to expand...
Click to collapse
Haven't tried out any other battery, I tested it on voltage meter and it showed ok, BUT you have got a point; I must check it with some other battery of working phone.
Moisture:: Well there was Mist/ Fog a few days back but mostly I stayed at warm place + I kept it in fromt of fan heater after ealry episodes..
I found a problem with the Airplane Mode:
I put my device on Airplane Mode before goint to bed, with the battery at ~70%. I woke up today and the battery was at 0%, completely drained in less than 10 hrs. It turns out that when I lock my device after turning on Airplane Mode the device froze, and for some reason it keep consuming energy.
I could replicate the bug 3 times already. To do so:
Reboot the device.
Connect it to something via USB (somehow this has something to do). Wait for a minute and disconnect it.
I'm being cautious here and I'm waiting two minutes before next step (I don't know if it's really necessary).
From the Quick Settings on the Notification Menu turn Airplane Mode on. And wait a few seconds.
Lock the device and don't touch it for 2 minutes.
Profit... I mean... Tada!! It's frozen now. You have to reboot it.
I'm gonna keep investigating and searching about this.
If anybody could tell me if you can reproduce this error or give me some advice I would appreciate it.
(The device is a XT1032, with stock ROM 4.4.2 (173.44.x))
sebbasttian said:
I found a problem with the Airplane Mode:
I put my device on Airplane Mode before goint to bed, with the battery at ~70%. I woke up today and the battery was at 0%, completely drained in less than 10 hrs. It turns out that when I lock my device after turning on Airplane Mode the device froze, and for some reason it keep consuming energy.
I could replicate the bug 3 times already. To do so:
Reboot the device.
Connect it to something via USB (somehow this has something to do). Wait for a minute and disconnect it.
I'm being cautious here and I'm waiting two minutes before next step (I don't know if it's really necessary).
From the Quick Settings on the Notification Menu turn Airplane Mode on. And wait a few seconds.
Lock the device and don't touch it for 2 minutes.
Profit... I mean... Tada!! It's frozen now. You have to reboot it.
I'm gonna keep investigating and searching about this.
If anybody could tell me if you can reproduce this error or give me some advice I would appreciate it.
(The device is a XT1032, with stock ROM 4.4.2 (173.44.x))
Click to expand...
Click to collapse
Nopes Can't reproduce.. A question though.. what lock times have you set.. the error might not have been reproduced due to that
iceporing said:
Nopes Can't reproduce.. A question though.. what lock times have you set.. the error might not have been reproduced due to that
Click to expand...
Click to collapse
Thanks for you reply. My Display settings are:
Sleep: After 1 minute of inactivity.
I am using a One Plus One and recently flashed Cyanogen 12.1.
Something very interesting is happening:
One morning my phone's screen wasn't displaying anything yet the phone was obviously working. I know this because the hard-button lights were on and I could feel the vibration when I held down the volume button to put it into vibrate mode. I even pressed the buttons to take a screenshot and when I looked in my gallery later, it was there.
So the phone was functioning in every way except for the display.
To fix it, I tried rebooting. It didn't work. So then I went into TWRP and wiped the dalvik cache. When the phone rebooted, the screen turned on and everything worked as normal.
So the next morning, the same thing happened. It happened at the same time of the day, right after I woke up. It had been charging all night. I woke up to the alarm on my phone and the screen was on so that I could turn the alarm off. Then I turned the screen off. The next time I tried to turn the phone on, same thing... screen not on... dalvik cache... yadeeyadayada...
So I thought maybe it was charging my phone all night that caused it. So the next night, I didn't charge my phone overnight, and in the morning, the same result.
So then it occurred to me that it might be my alarm app (I use 'Morning Routine'), but even when I didn't use the app, the same thing still happened.
I read up online and followed so advice (turning off proximity sensor, disabling the "prevent accidental wakeup function"). The advice did not work.
I am at a loss and can only figure that my phone's screen not turning on is caused by having it off for quite a while (6-8 hours). And the only solution for it is wiping the dalvik cache. This is really annoying to do every morning considering wiping the dalvik cache results in all of my apps needing to be "optimized for android."
Any help would be great. Thanks!
XDA Visitor said:
I am using a One Plus One and recently flashed Cyanogen 12.1.
Something very interesting is happening:
One morning my phone's screen wasn't displaying anything yet the phone was obviously working. I know this because the hard-button lights were on and I could feel the vibration when I held down the volume button to put it into vibrate mode. I even pressed the buttons to take a screenshot and when I looked in my gallery later, it was there.
So the phone was functioning in every way except for the display.
To fix it, I tried rebooting. It didn't work. So then I went into TWRP and wiped the dalvik cache. When the phone rebooted, the screen turned on and everything worked as normal.
So the next morning, the same thing happened. It happened at the same time of the day, right after I woke up. It had been charging all night. I woke up to the alarm on my phone and the screen was on so that I could turn the alarm off. Then I turned the screen off. The next time I tried to turn the phone on, same thing... screen not on... dalvik cache... yadeeyadayada...
So I thought maybe it was charging my phone all night that caused it. So the next night, I didn't charge my phone overnight, and in the morning, the same result.
So then it occurred to me that it might be my alarm app (I use 'Morning Routine'), but even when I didn't use the app, the same thing still happened.
I read up online and followed so advice (turning off proximity sensor, disabling the "prevent accidental wakeup function"). The advice did not work.
I am at a loss and can only figure that my phone's screen not turning on is caused by having it off for quite a while (6-8 hours). And the only solution for it is wiping the dalvik cache. This is really annoying to do every morning considering wiping the dalvik cache results in all of my apps needing to be "optimized for android."
Any help would be great. Thanks!
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Dalvik cache trick throws a wrench into things, but I used to have a similar issue with an older device - the screen wouldn't come one, but the hard button backlight would - pulling the battery and rebooting relieved the problem for that fit. I ended up scaling down the max processor speed (as it was being overclocked on the current custom ROM) back to the stock value. The problem went away at the point. But that was for my device, and because yours requires a dalvik cache wipe, it is probably a different cause.
At any rate, please go ahead and create an XDA account. Then, venture over to post in the [Q&A] Help thread. Ask away! (Noob friendly) thread, (or at least) in the > OnePlus One > ONE Q&A, Help & Troubleshooting forum. Your device experts can be found there.
Hope this helps, and good luck!
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!