I've noticed that my display sometimes doesn't turn off. It'll dim like it's about to turn off, but just stays dimmed. It doesn't do it all the time and I can't seem to figure out why sometimes it doesn't turn off and other times it does.
The tablet is rooted, I'm using Nova launcher, and have Hide Soft Keys installed, though have had problems with Hide Soft Keys disabled too. I have a bunch of other apps already loaded too. So before I start uninstalling everything, was just wondering if anyone else has noticed this issue?
Ravynmagi said:
I've noticed that my display sometimes doesn't turn off. It'll dim like it's about to turn off, but just stays dimmed. It doesn't do it all the time and I can't seem to figure out why sometimes it doesn't turn off and other times it does.
The tablet is rooted, I'm using Nova launcher, and have Hide Soft Keys installed, though have had problems with Hide Soft Keys disabled too. I have a bunch of other apps already loaded too. So before I start uninstalling everything, was just wondering if anyone else has noticed this issue?
Click to expand...
Click to collapse
That's because of the crappy power button. You've got to press it harder.
No. I was referring to the automatic idle turn off after a couple minutes. My screen will dim after 2 minutes (what I have the turn off period set to), but once in a while it never completely turns off and will stay on. I set the tablet down, went to the store, came back and the display was still on in a dimmed, but not off state.
Ravynmagi said:
No. I was referring to the automatic idle turn off after a couple minutes. My screen will dim after 2 minutes (what I have the turn off period set to), but once in a while it never completely turns off and will stay on. I set the tablet down, went to the store, came back and the display was still on in a dimmed, but not off state.
Click to expand...
Click to collapse
Yes I have noticed this as well. Must be a bug? I have my screen time out set to 2 minutes (default I believe) and i have set it down for over 10 minutes and came back with the screen still on.
I did a factory reset yesterday morning.
First, I was kinda surprised after the factory reset, that after I logged into the device again, I found that some of the files were erased, but not all of them. Usually factory reset wipes everything, even the root. But SuperUser was still installed. And I installed AdAway and confirmed root was still working. My TitantiumBackup folder got wiped, but Kindle folder remained. Not sure why the factory reset seemed to only half work.
However it does seem factory reset might have fixed the problem I was having with the screen not turning off sometimes. When I first setup the Nexus 7 I choose the option to restore from my Google backup and I got all the apps I had installed on my Nexus 4 (my Nexus 4 seems fine with those apps). So this time around after the factory reset I played it safe and did not choose the restore from Google backup option and just manually reinstalled the apps I need for now. And so far so good.
Related
I have a Tilt 2, so does my Wife and my Father. This is the 3rd HTC device i've had (mogul, diamond). This setting should be pretty easy.
So my Dad is complaining about the screen dimming really quickly, I change the settings to 2 min. seems to work well for a while. Then he tels me it's still doing it. I check his settings and its back to 10 sec. we go through this a couple of more time, I'm thinking he is changing it and doesn't know it.
So we just turn off the dim feature (on battery) Today he says it's still doing it, we check his settings and the dim feature is turned off, still! but i saw it go dim after 7-10 secs.
Any ideas? Am i missing a setting, i have done mine and my wifes with no problems.
does he have his backlight on auto adjust?
drearg said:
does he have his backlight on auto adjust?
Click to expand...
Click to collapse
Probably, but i have never see such a dramatic change with the auto adjust. it doesn't seem to matter how much light there is. and it's consistantly 7 to 10 seconds.
I tried the at&t "chat" help, they were worthless.
maybe try turning it off. maybe need to do a soft reset on the side of phone.
we turned it off (unchecked it) but it still dims the backlight, never seen anything like it, i will try the soft reset tomorrow. hopefully that will work!
I had the same issue...
I created a reg file to manually fix. What is happening is when the device wakes up from screen sleep or changing from external to battery power, WM6.1 changes this key:
HKEY_CURRENT_USER\ControlPanel\BackLight\BatteryTimeout to 8 (seconds in hex).
I used my reg file and added to my start menu (you could also assing to a hardware button if you have the right tools), and run it when the device sets it to 8 seconds. Its a couple of clicks, but less then navigating to the UI settings.
The reg file is set for 2 minutes. Edit as you wish, but keep in mind you need to convert the seconds to hex.
Send it Back!!
The AT&T folks said to send it back (its still within the 30 days) Dad also told me that the speaker sounds funny, i really didn't believe him, thought it was just "different" from his old Razor.
So we tried it i used his phone and called him using mine, dang if it didn't sound funny!
So i am on the phone getting another sent!!
Thanks for helping!
This problem is with the screen and phone not going to sleep mode after an event that brings it out of sleep.
After i lock the screen manually by pressing the button on the top, the phone would wake up briefly due to an event like a calendar reminder, text, phone etc.
So after certain duration of inactivity, it should go back into the sleep mode automatically. Right, it used to, but not anymore. It just stopped. I have checked the Advanced settings under the Battery option but no good.
Although after say 30 seconds (as per my setting) the screen fades to low light to conserve battery, but remains active.
As a result i have inadvertently pocket dialed quite a many and it's beginning to be a privacy concern and a pain in the butt for me and others. Not to mention the charges from the international number my phone self-dialed.
I'm using a TP-2 Rhodium OS 6.1.
As if the battery didn't suck enough, I needed this !!!
Any tips would be appreciated.
If the phone "used to" go to sleep but doesn't anymore, it sounds like a recently installed program or process is running in the background forcing it to stay on.
Does the phone refuse to go to sleep only after being woken up by an event?
...or does it not go to sleep on its own at all anymore?
Isn't pressing that button on the top just closing the screen?, unless you set it as the lock as well
I should have mentioned - the phone will go back to sleep mode if I manually operate the button on the top. Just that it won't go to sleep on its own anymore.
You may be right user602, about the recently installed apps, but is there any way to narrow down on the culprit instead of uninstalling all of them?
s6a6n6d6m6a6n said:
I should have mentioned - the phone will go back to sleep mode if I manually operate the button on the top. Just that it won't go to sleep on its own anymore.
You may be right user602, about the recently installed apps, but is there any way to narrow down on the culprit instead of uninstalling all of them?
Click to expand...
Click to collapse
Go back and check the power settings again; make sure they are set to have the screen turn off. Change the settings to some other value and see if that helps. Maybe something just messed around with your registry entries.
If not, you will need to uninstall those programs, in reverse order, until the device works.
I'd start by changing the power settings as suggested by stevedebi above.
If that doesn't help, and you want to avoid uninstalling a bunch of stuff, you can look at what's running using Task Manager:
-Begin by stopping running programs one at a time, and seeing if the device will sleep.
-If that doesn't help, stop processes one at a time, and again see if the device will sleep (watch out for critical system processes, though).
...or if you're lucky, you may find something in the \windows\startup folder, such as a program you were not aware is starting on boot.
Of course, this all ends with uninstalling programs one at a time if none of the above suggestions work.
-602
------- "I'd start by changing the power settings as suggested by stevedebi above."
I can swear i tried this before and it didn't work. Changed it one last time before doing anything else,... and voila !!!
Thanks 602 & stevedebi
That was easy!
I'm glad the simplest solution worked for you.
...That's usually not my luck!
Cheers,
-602
I just bought it yesterday and the watch has been updated to 5.0.2. Cant find findthis settingin andoird wear app as the image attached. I live in Taiwan and pair with lg g3. Tks you guys
When you are on that screen, tap on the item that says "Asus Zenwatch Connected" and you'll see the option to adjust tilt & wake.
thank you very much for the advise I was trying to find that setting aswel.
Buggy Zenwatch keeps turning on twist to wake even though set to "Off"!
btonetbone said:
When you are on that screen, tap on the item that says "Asus Zenwatch Connected" and you'll see the option to adjust tilt & wake.
Click to expand...
Click to collapse
My Asus Zenwatch has been buggy as heck lately after the last few firmware updates. The main issue now is that the watch face lights up and comes on whenever I move or twist my arm or hand even though I've set and reset the shake to wake setting to "Off". I've tried resetting and rebooting the watch to no avail. I've noticed that the battery life on my watch has shortened now too as it does not even last a full day! I also used to be able to tap the watch face one time to wake it. Now it does not wake up unless I tap the face two or more times. Sometimes it can't wake up at all and is dead until I press the power reset button on the back of the watch.
It is also constantly vibrating every now and then every few minutes as if I got some notification or lost connection with the phone when none of those activities really happen. It just vibrates and then when I twist my arm up to look at it, it wakes up and lights up even though I have "Shake to Wake" mode turned "OFF"! WTF?
exists2wonder said:
My Asus Zenwatch has been buggy as heck lately after the last few firmware updates. The main issue now is that the watch face lights up and comes on whenever I move or twist my arm or hand even though I've set and reset the shake to wake setting to "Off". I've tried resetting and rebooting the watch to no avail. I've noticed that the battery life on my watch has shortened now too as it does not even last a full day! I also used to be able to tap the watch face one time to wake it. Now it does not wake up unless I tap the face two or more times. Sometimes it can't wake up at all and is dead until I press the power reset button on the back of the watch.
It is also constantly vibrating every now and then every few minutes as if I got some notification or lost connection with the phone when none of those activities really happen. It just vibrates and then when I twist my arm up to look at it, it wakes up and lights up even though I have "Shake to Wake" mode turned "OFF"! WTF?
Click to expand...
Click to collapse
I know you said you reset your watch, but have you done a full factory reset? That should fix just about anything wrong with it...
If that doesn't work, try to pair it temporarily with another phone or perform a factory reset on your phone. Maybe there is an app on your phone causing the watch to go haywire.
Go to setting on Zenwatch and search system update, you will go to 5.1.1, the best version I have see on this watch. Then do a factory reset.
I think this will go fine
AlanRoot said:
Go to setting on Zenwatch and search system update, you will go to 5.1.1, the best version I have see on this watch. Then do a factory reset.
I think this will go fine
Click to expand...
Click to collapse
No that was not the problem. I was already on the latest updated firmware for awhile when all this bugginess happened. Factory resetting the watch did not help.
I did finally uninstall the Android Wear and the Asus Zenwatch Manager apps and cleared those apps data and cache. Then reinstalled them. Did this several times until I got the watch to connect properly and successfully and stay connected. I adjusted all the settings on the phone app itself instead of from the Asus Zenwatch itself and that seems to have fixed my issues. Twist to wake is really "Off" now and the watch does not keep vibrating every few minutes. So hopefully this will not get corrupted again in time (as it seems to have before).
I've had this issue before on my LG Power (Straight Talk branded LG Leon), running on Lollipop 5.0. No matter what I look for I can't find anyone who's experienced similar issues.
It just happened last night on my 5-day old Nexus. I could not open any of my folders to access apps. As soon as a touched a folder, it briefly showed the animation to open it, and it immediately closed. Whenever I selected a widget or the app drawer, they would immediately close as well. When I attempted to swipe down the notification/quick settings shade, they immediately closed themselves. Turning off the screen resulted in the screen immediately turning back on, albeit locked. I was even having trouble turning the device off because the 'Power Off' menu would disappear right after it popped up. Eventually I was able to time it right and was able to power off. Since I restarted I have not have any issues.
Any idea what gives? I'm unrooted, locked bootloader, everything 100% stock, running MM 6.0.1.
the only explanations i can come up with are:
-accidental touching the area in some way (unlikely)
-getting some substance stuck on the screen in that area (unlikely)
-a faulty touch panel (unlikely and very specific defect)
-a hickup in the software (again unlikely)
then again, if the OS (for whatever reason) thinks the home button is pressed, on default it should not only pull you back to the homescreen, but continue and send you right through to google. the conclusion of which would be, that this UI area is triggered repeatedly rather than continuously.
keep an eye out for what could have triggered it in case it occurs again.
check your settings what build exactly you are running (settings -> about phone -> build number).
ans lastly, if it happens again, you should still be able to hold your power button to hard-reboot it (no further interaction with the UI required).
RockinAmigo14 said:
I've had this issue before on my LG Power (Straight Talk branded LG Leon), running on Lollipop 5.0. No matter what I look for I can't find anyone who's experienced similar issues.
It just happened last night on my 5-day old Nexus. I could not open any of my folders to access apps. As soon as a touched a folder, it briefly showed the animation to open it, and it immediately closed. Whenever I selected a widget or the app drawer, they would immediately close as well. When I attempted to swipe down the notification/quick settings shade, they immediately closed themselves. Turning off the screen resulted in the screen immediately turning back on, albeit locked. I was even having trouble turning the device off because the 'Power Off' menu would disappear right after it popped up. Eventually I was able to time it right and was able to power off. Since I restarted I have not have any issues.
Any idea what gives? I'm unrooted, locked bootloader, everything 100% stock, running MM 6.0.1.
Click to expand...
Click to collapse
Try to clean your screen also with a towel
That is extremely weird. It really sounds like a faulty digitizer, but you'd be the first... Maybe it's a rogue app, but unlikely.
Were you doing something before this starts to happen?
I haven't noticed any consistent apps or behaviors when this would occur. This most recent time, I was low on battery (10%) and I had just flipped on my data.
fyi. you could also just press and hold the power button, for 10 secs, for a reboot ( might come in handy when the screen isn't working properly).
dpj52190 said:
fyi. you could also just press and hold the power button, for 10 secs, for a reboot ( might come in handy when the screen isn't working properly).
Click to expand...
Click to collapse
appreciate the tip! I'll keep this in mind if it happens again.
Finally was able to capture a video. The issue occurred after I was playing around with Open Camera and it crashed. Holding down the power button didn't work when this glitch is happening.
https://youtu.be/4n5vzXlUPqM
RockinAmigo14 said:
Finally was able to capture a video. The issue occurred after I was playing around with Open Camera and it crashed. Holding down the power button didn't work when this glitch is happening.
https://youtu.be/4n5vzXlUPqM
Click to expand...
Click to collapse
What's the icon on the lock screen, top right in the status bar? That behavior is unusual if it's not a screen defect. Are you using any apps that monitor battery, a task killer, or maybe a security monitor app?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
What's the icon on the lock screen, top right in the status bar? That behavior is unusual if it's not a screen defect. Are you using any apps that monitor battery, a task killer, or maybe a security monitor app?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
The icon is a picture for my user profile on the phone.
I don't use anything like that. I had Clean Master installed briefly but it's been uninstalled for a couple of days now.
so it seems like this issue pops up whenever the camera crashes. happens occasionally when using the camera shortcut (double power tap) or in an app that uses the camera.
It's got to be software IMO. It didn't happen when you went to Google Now and your Recent Apps. I'd try uninstalling the Open Camera app first. Do you have Face Unlock active by chance? After that I'd FDR...
exninja said:
It's got to be software IMO. It didn't happen when you went to Google Now and your Recent Apps. I'd try uninstalling the Open Camera app first. Do you have Face Unlock active by chance? After that I'd FDR...
Click to expand...
Click to collapse
right, that's what's confusing me. i did a factory reset last week, set up the phone as a new device. haven't installed a new camera app, just the stock google camera. the issue occurred again last night when using an app called Shopkick, which accesses the camera but crashed.
Hi,
recently I started to use bluetooth because I bought a smart watch which requires bluetooth for smart notifications, ... Its been working great, until one day. Every time I didnt use smartwatch, I turned bluetooth off. And one day I tapped the icon to turn it on, and the bluetooth icon stayed pressed for a 5-6 seconds and then it went back white which means, it did not turn on. I tried everything, reboot, safe mod, recovery mode, force stop, ... Nothing worked. Then I did factory reset, which changed everything and bluetooth started to work again, but not for very long. After 2 days, exactly same thing happend and I have no idea what to do. Im pretty sure its a software problem, but no idea how to solve it. Please any ideas??
Thanks a lot.
feri_crosby said:
Hi,
recently I started to use bluetooth because I bought a smart watch which requires bluetooth for smart notifications, ... Its been working great, until one day. Every time I didnt use smartwatch, I turned bluetooth off. And one day I tapped the icon to turn it on, and the bluetooth icon stayed pressed for a 5-6 seconds and then it went back white which means, it did not turn on. I tried everything, reboot, safe mod, recovery mode, force stop, ... Nothing worked. Then I did factory reset, which changed everything and bluetooth started to work again, but not for very long. After 2 days, exactly same thing happend and I have no idea what to do. Im pretty sure its a software problem, but no idea how to solve it. Please any ideas??
Thanks a lot.
Click to expand...
Click to collapse
Found this on another forum... I had the same problem and it got solved by following this.
What you need to do is clear the Bluetooth Share app cache and data, then perform a Network Settings Reset. I'd recommend doing it in that specific order.
First, open App Manager from Settings menu. Then use the three vertical dots on the top right to open the options. Select "Show System". Scroll to the Bluetooth Share app, and open up it's settings. Tap Storage. Tap Clear Cache, wait a moment, the cache will clear to 12.00KB. Now tap Clear Data.
Next, open the main Android settings again. Go to Backup & Reset, then Network Settings Reset. Tap Reset Settings and enter pin, if prompted. Tap Reset Settings one more time.
After that completes, which should be fairly instantly, try to turn on your Bluetooth. It should turn on! Yahoo! Let me know if this works for you!
Thanks to the original poster (I cannot post links here).