Related
Having a problem with the lock screen in CM10.1 that is happening more frequently.
It seems it happens after I open the case lid and the Nook HD+ wakes up. I use pattern lock (but it's happened in the swipe lock also), and for a moment, it looks like it's unlocked. The desktop or app that was up when it went to sleep is there, but only for about 1 second. It goes right back to the lock screen. It repeats over and over. At first, I thought only a reboot would fix it and allow me to unlock it, but I found if I hit the power button to put it to sleep and wake it up, it typically unlocks. Sometimes it might need me trying that a couple of times, but it usually works.
Ideas? Anyone else having a problem unlocking after sleep? So far, I'm not sure if it's just lid-induced sleep or if it would happen after I use the power button to sleep it.
Again, it doesn't happen all the time, but i'm finding it happen more frequently.
Thanks!
lancorp said:
Having a problem with the lock screen in CM10.1 that is happening more frequently.
It seems it happens after I open the case lid and the Nook HD+ wakes up. I use pattern lock (but it's happened in the swipe lock also), and for a moment, it looks like it's unlocked. The desktop or app that was up when it went to sleep is there, but only for about 1 second. It goes right back to the lock screen. It repeats over and over. At first, I thought only a reboot would fix it and allow me to unlock it, but I found if I hit the power button to put it to sleep and wake it up, it typically unlocks. Sometimes it might need me trying that a couple of times, but it usually works.
Ideas? Anyone else having a problem unlocking after sleep? So far, I'm not sure if it's just lid-induced sleep or if it would happen after I use the power button to sleep it.
Again, it doesn't happen all the time, but i'm finding it happen more frequently.
Thanks!
Click to expand...
Click to collapse
I have heard about this problem from several people, but usually it is on an HD+ with the cover that wakes up the tablet. However, I just experienced this a few minutes ago and my Nook has never had a case on it, let alone one that wakes it.
It happened when waking it with the n button but after turning off the screen with the power button and back on with the power button, it worked. (not turning off the Nook, just screen off and back on)
So it appears that it is not only the magnetic wake up that causes the issue.
Sent from my nook HD+ running cm10.1 on emmc from Tapatalk HD
Mine does that too. I thought it was a hardware defect, but I tried another one and it does exactly the same thing.
So far it's only happened with a case-induced wake for me. It happens regardless of whether I sleep it using the case or the power switch.
The lockscreen loop stops if I sleep/wake it using the cover consistently, but it doesn't go away if I sleep/wake it using the power switch, oddly.
same problem with no known solution
lancorp said:
Having a problem with the lock screen in CM10.1 that is happening more frequently.
It seems it happens after I open the case lid and the Nook HD+ wakes up. I use pattern lock (but it's happened in the swipe lock also), and for a moment, it looks like it's unlocked. The desktop or app that was up when it went to sleep is there, but only for about 1 second. It goes right back to the lock screen. It repeats over and over. At first, I thought only a reboot would fix it and allow me to unlock it, but I found if I hit the power button to put it to sleep and wake it up, it typically unlocks. Sometimes it might need me trying that a couple of times, but it usually works.
Ideas? Anyone else having a problem unlocking after sleep? So far, I'm not sure if it's just lid-induced sleep or if it would happen after I use the power button to sleep it.
Again, it doesn't happen all the time, but i'm finding it happen more frequently.
Thanks!
Click to expand...
Click to collapse
I have the same problem and no solution. I wonder if a newer release of CM would help.
Also, in regards to temporary coping, when this problem appears is there a method (besides reset) to deal with the problem. I noticed that sometimes I can eventually get past the lockscreen without restarting, but I'm not sure what causes that. The best solution I have for my wife at this point is I delayed locking-after-sleep to 30 minutes.
Two-user set-up (my wife and me). I am fairly new to the scene--first time I ever loaded CM on any device. I recently bought the HD+ from Best Buy for $150. I tried to follow the verbatim instructions from e.mote titled "[NOOK HD/HD+] Installing CyanogenMod 10.1 for Dummies." I haven't used custom ROMs much since my heady days with my Palm Pre.
I'm in the same boat. Hd+ running CM 10.1.3. I wonder if this still happens on the 10.2 builds...
While on 10.1 this happened to me every time after charging (well, maybe not every time, but that's when it happened...), but if I just turned off screen and then back on I was fine until next charging.
I put on 10.2 earlier today (from Iamafanof site, so not from here). Will be interesting to see if the problem is till there, but I won't know tat for a while yet.
Nook HD problems waking up
asawi said:
While on 10.1 this happened to me every time after charging (well, maybe not every time, but that's when it happened...), but if I just turned off screen and then back on I was fine until next charging.
I put on 10.2 earlier today (from Iamafanof site, so not from here). Will be interesting to see if the problem is till there, but I won't know tat for a while yet.
Click to expand...
Click to collapse
Im seeing this on both 10.1 and 10.2 on my nook HD no cover.
I'm seeing this even without a lock screen. The screen turns on for a second, after that turns off. After many tries it works or after a restart. With lock screen it is the same as above.
Happend on CM 10.1 and CM 10.2 with a cover
So there's no solution to this problem and you just have to reboot it?
You just close and open the cover again
Sent from my rooted GS3 running CM11
oboefiend said:
You just close and open the cover again
Sent from my rooted GS3 running CM11
Click to expand...
Click to collapse
I'll try that again but I don't think it worked.
I have been having the same issue as well with mine. Just curious if really has been a solution to this?
No it is a hardware issue. There are two options close and reopen cover or cut magnets out and turn on manually. I don't think anyone has tried more powerful magnets if you want to test that it would be helpful.
Sent from my SPH-L900 using XDA Free mobile app
I kinow its an old thread, but I Fixed it by closing and opening the magnetic cover, rather than using the power/off/on screen button and it worked.
Only fix is to do one of three things. Remove the magnet from the cover, remove the cover is self, disable the lock screen. It's because the cover and lock screen confuse each other and it has the cover wake it, then the lock screen sleep it, then it sticks. It's very well known, and nothing to panic over, just really freaking annoying.
I recently installed CM 10.1.2 Stable and it was working fine until about a week ago - great work, thanks to the Devs.
The problem that I am having is that the home screen and drawer is locked in portrait mode. I have tried EVERY setting I could find and it only stays on portrait. All the other apps stay in landscape when rotation lock is on (my preferred usage mode) with the exception of the dialer and the lock screen. The only time the home screen behaves is when I put the device in it's car dock - THEN it orients correctly.
The actual events right before it went wonky are as follows:
1) I was using it in the car dock, turned off the vehicle, and removed it. The lock screen seemed to be taking it's time orienting.
2) While I was fumbling with it I dropped it on the corner closest to the USB port (I know, normally it's in an Otterbox but I had just pulled it out of the car). It also got a little moisture on it, but none appeared to penetrate.
3) After I dropped it, everything was stuck in portrait mode - all apps, etc.
4) I restarted, and then did a cold boot, and it got to where I am now.
I have tried reinstalling CM, and various combinations of car dock/rotate settings but I'm baffled. It is my understanding that the accellerometers might cause bad rotation behavior, but it doesn't affect the other apps. Any suggestions?
Thanks,
R
R2.0 said:
I recently installed CM 10.1.2 Stable and it was working fine until about a week ago - great work, thanks to the Devs.
The problem that I am having is that the home screen and drawer is locked in portrait mode. I have tried EVERY setting I could find and it only stays on portrait. All the other apps stay in landscape when rotation lock is on (my preferred usage mode) with the exception of the dialer and the lock screen. The only time the home screen behaves is when I put the device in it's car dock - THEN it orients correctly.
The actual events right before it went wonky are as follows:
1) I was using it in the car dock, turned off the vehicle, and removed it. The lock screen seemed to be taking it's time orienting.
2) While I was fumbling with it I dropped it on the corner closest to the USB port (I know, normally it's in an Otterbox but I had just pulled it out of the car). It also got a little moisture on it, but none appeared to penetrate.
3) After I dropped it, everything was stuck in portrait mode - all apps, etc.
4) I restarted, and then did a cold boot, and it got to where I am now.
I have tried reinstalling CM, and various combinations of car dock/rotate settings but I'm baffled. It is my understanding that the accellerometers might cause bad rotation behavior, but it doesn't affect the other apps. Any suggestions?
Thanks,
R
Click to expand...
Click to collapse
If that happened after your dropped it, you can try to recalibrate the accellerometer (if that's still an option on the cappy).
If that doesn't work, you can always try to flash stock odin KK4 without bootloaders (after a backup of course). But my guess is that it's hardware related so flashing won't change much.
If all fails, you can contact Josh @ mobiletechvideos.com. He's well known around here for fixing cappys.
My HD (running 10.1.3 stable) has just started behaving strangely when I wake it up from sleep. The screen will flash then go black. Whether I push the Nook button or the power button, the same thing happens. It may do it 2 or 3 times before it comes on. Started doing this yesterday. Just now, it would not come on at all. I see the screen for a half second, then it goes black. Just wondering if it's already toast or if this is a known problem with a remedy.
Probably software issue.
If your using a magnetic case (problem)
You could try disabling the lockscreen if its enabled.
Daydream could in my theory affect that time frame.
The backlight should last years longer. The gpu should as well. I can't think of any other hardware issue.
If you have an sdcard try cm11 [or the bn rom] and see what happens. OR full backup of current rom in cwm and flash cm11 to internal. Clean and restore 10.1.3 and be back to right where you left off.
lmacmil said:
My HD (running 10.1.3 stable) has just started behaving strangely when I wake it up from sleep. The screen will flash then go black. Whether I push the Nook button or the power button, the same thing happens. It may do it 2 or 3 times before it comes on. Started doing this yesterday. Just now, it would not come on at all. I see the screen for a half second, then it goes black. Just wondering if it's already toast or if this is a known problem with a remedy.
Click to expand...
Click to collapse
Yes I have the same flickering issues when trying to wake it up from sleep. I would have to press either button numerous times to get it to stay on and not black out. I'm on the same 10.1.3 stable. I am using a magnetic case but it happens without it. Before this happen, my slide to unlock screen would act up by not unlocking when I slide to unlock; it would just go back to the initial lock screen. Slide to unlock would not work so I turn off the lockscreen, now experiencing blackout screens when I try to wake it up by pressing either buttons. This problem happens infrequently but it is annoying.
kinvid said:
Yes I have the same flickering issues when trying to wake it up from sleep. I would have to press either button numerous times to get it to stay on and not black out. I'm on the same 10.1.3 stable. I am using a magnetic case...
Click to expand...
Click to collapse
I learned from another post that if it does not awaken when the magnetic case is opened the first time, close and open it again. This works for me 95% of the time. Sometimes there's 2 or 3 second lag but it almost always comes on.
Sent from my Nexus 7 using XDA Free mobile app
lmacmil said:
I learned from another post that if it does not awaken when the magnetic case is opened the first time, close and open it again. This works for me 95% of the time. Sometimes there's 2 or 3 second lag but it almost always comes on.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Works like this on my HD+, too. Sometimes requires opening case cover twice, but the screen always comes on.
When I bought the watch back in November, the screen would stay ON all the time. I know it to be a fact because I used to leave it on a desk without ever touching it (for hours) and it would always display the time (it was like having a desk clock, for when I would rather not wear it to have more comfortable wrists while writing or that sort of things).
Also in the train (I used to travel a lot in that period) I would leave the watch hung on the wall while sleeping (at night) and it would not turn itself off, so I could check the time in case I woke up in the middle of the night, without neededing to reach for the watch.
Recently (it was January) I noticed that it does not work like that anymore. After a very short time, the watch screen goes off. It is still in standby: it goes back on if I touch it or press the button.....but I want it to stay on 'without limits' (in dimmed mode). It was like that before.
Somehow this is the behaviour of the 'keep screen always ON' setting.....but in fact, that setting is already set to 'ON'.
So is there some kind of firmware update that changed this behaviour? I would like the clock to not go off when it is not on my wrist, sometimes I just need to keep track of time AND have my wrists free....and it is not possible anymore.
nothing?
It is actually a key feature....no point in having a watch that doesn't show the time unless you touch it (if you leave it on a desk or simply hung on a wall at night). Also I wonder why it changed (did not do this last year so I thought it must be some update but could not find anything in the changelogs about this).
You have the Setting enabled in Android Wear for keeping the screen Always On?
My screen only goes out when on the charger. When I had a Samsung Gear Live, it would stay on while on the charger, via the Developer Setting on the watch to keep the screen on while charging. But that has never worked for me on the "R", not even last year.
The screen of the watch goes off while charging (although I remember it being different back in October...).
The settting for 'screen always on' is activated. I activated from the watch, from the phone, restarted the watch, nothing worked. The screen goes off after a while IF I DO NOT wear the watch.
No problem if I wear it....that means there is some connection between the screen going off and the accelerometer :-/
But as I said, I need the watch to stay on even if I am not wearing it (working at a desk or similar when I can't wear the watch, I would look at the time at the watch lying on the table). I am sure 1000% it did not turn off before (started in January, or at least I noticed it in January). I read all the changelogs for all the updates and I did not find anything about this.
Can someone also try? My brother has the same watch and his also goes off if he does not wear it. I find this really unneeded. At least they should have put a setting available.
You best option is Wear Charging Widget. It will keep the screen on when charging. Although it does dim a bit, like a night clock in a mostly dark room. It is the only option I've found that works.
I wanted the "R" to work like my old Gear Live and keep the screen on when charging and even when not wearing it. But I've never found a means for that to happen short of Wear Charging Widget.
Sent from my Nexus 10 using Tapatalk
Darnell_Chat_TN said:
You best option is Wear Charging Widget. It will keep the screen on when charging. Although it does dim a bit, like a night clock in a mostly dark room. It is the only option I've found that works.
I wanted the "R" to work like my old Gear Live and keep the screen on when charging and even when not wearing it. But I've never found a means for that to happen short of Wear Charging Widget.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Yes it looks it is like that now. Maybe you bought the watch after the two last updates (501 / 502) ?
Would be nice if somebody else, besides me, could confirm that in fact the watch was staying on (dimmed mode) all the time even without wearing it in the previous months (release date to December).
rogermorse said:
Yes it looks it is like that now. Maybe you bought the watch after the two last updates (501 / 502) ?
Would be nice if somebody else, besides me, could confirm that in fact the watch was staying on (dimmed mode) all the time even without wearing it in the previous months (release date to December).
Click to expand...
Click to collapse
I've had my "R" since last year, before v5 came out for the watches. And the "R" never kept the screen on while charging. I never noticed it involved simply not wearing it. Since when I'm not wearing, I'm charging.
Sent from my Nexus 10 using Tapatalk
Screen shuts off completely
The screen on my GWR has started shutting off, completely dark not dim. I checked the settings and it is set to "Always on screen": ON.
This is a fairly new problem, it did not used to behave this way, I could see the screen dim, and move my wrist and it would go bright and display "OK Google".
Any ideas on how to fix this bug? Or do I/we need to wait for a software update/fix? Current software version: 5.0.2
Watch is not very useful if I can't see the time without having to push the crown/button.
Anyone else having this issue?
Screen is working again.
Had some time to try some options, did a "Reset Device" and the screen came back.
Lost all the apps I had loaded on the watch, not a big deal, wasn't using many of them.
Guess I can just download them again from the play store, if I want them back. Something I loaded onto the watch may have caused the loss of the screen.
Last couple of apps I downloaded were CompassX and a charging app that shows charging progress while charging.
Glad to have the watch face back.
I'm having the same problem as you. The ambient mode won't come on. Instead of dimming to ambient mode it now just goes dark completely (like when it is charging). I would love another fix before I have to reset the watch. Any ideas?
2leaponover1 said:
I'm having the same problem as you. The ambient mode won't come on. Instead of dimming to ambient mode it now just goes dark completely (like when it is charging). I would love another fix before I have to reset the watch. Any ideas?
Click to expand...
Click to collapse
Bumping this. I reset the watch. Went about two weeks and now back to the same problem. Ambient mode has disappeared. It's just black all the time until i turn it back on.
2leaponover1 said:
Bumping this. I reset the watch. Went about two weeks and now back to the same problem. Ambient mode has disappeared. It's just black all the time until i turn it back on.
Click to expand...
Click to collapse
The user support for this watch is non-existent Still no help with this problem
2leaponover1 said:
The user support for this watch is non-existent Still no help with this problem
Click to expand...
Click to collapse
I confirm that I have this trouble also in normal use, previously it worked fine and would stay on all the time if that's what I wanted.
Am very tempted to reset the watch after backing up.
I have nearly the same problem. For months now, when my screen dims, it goes to a very dark/dim red. I've removed all programs from my phone and did a factory reset on the watch three times. I'm not sure what else to try. Is there a way to flash the memory? It seems like a setting is stuck in the non-volatile memory.
I was having the same problem and found that I had theater mode set on. Switched to off and now works great.
Sent from my Nexus 6 using Tapatalk
Check your theater mode setting.
Turning mine off worked.
extrabilly said:
Anyone else having this issue?
Click to expand...
Click to collapse
I'm experiencing the same. On my watch it seems to be somehow related to accelometer. Almost everytime, when using LG G Watch R in golfing, it starts to shut down the screen. It doesn't wakeup even when tapping the screen.
I haven't found other solution than resetting the device
Same issue with 5.1.1
I had this issue with 5.0.2 and hoped that the next update would solve it but sadly it persists in 5.1.1 .
Theatre mode is off, Always on is on but still the screen blanks, showing the ambient mode screen briefly before blanking.
I've reset multiple times, occasionally Always On comes back but only for a short while.
Always on is a feature I really like
Fixed it on mine
I had to turn wrist gestures on. With it off screen on doesn't work.
I have the exact problem on my GWAR, software version 5.1.1. I bought my in December and it never happened until now. It started happening yesterday all of a sudden. I tried factory reseting it through bootloader, throught settings, uninstalling the Wear app, uninstalling the watchface i was using, and still nothing.
Here is what I did to fix it (and i know its overkill): Uninstall Wear app, clear google play services data and reset the device through settings. Now it's finaly working.
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
JimSmith94 said:
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
if youre using lightflow id suggest wiping the data in it and resetting your notification settings. it does tend to override the system so i can see that screwing with the duration of the notification, and starting fresh usually solves most problems
i have mine set to wake the screen for SMS but not MMS. it creates similar problems with the screen
Thanks for the info. I tried just toggling the screen on settings on and back off for all of the Light Flow apps, and it seems to have fixed my screen turn on problem, at least for now.
Sent from my Nexus 6 using Tapatalk
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
A.Ahmed79 said:
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
Click to expand...
Click to collapse
LightFlow fixed my screen problems, but it was just a coincidence that I installed Marshmallow and my sounds got cut off around the same time. I'm still looking for a solution to that issue. Similar to you, if my screen is on, the notification sounds work correctly. If the screen is off, they get cut off.