I recently bought a used Nexus One, but it's in great shape. It was preloaded with CM 6.0 RC1, so I decided to update it to stable CM 6.1.1.
I love the phone and CM, but there seems to be an issue whenever waking up the phone from sleep.
If I have the phone on a perfectly even surface (table, etc.), wake up and unlock the phone, it will sometimes wake up with the screen orientation in landscape mode instead of portrait. This even occurs when I lock the screen in portrait mode.
Another issue is when I'm using my phone in bed. When I lay down and hold my phone above my head to browse and stuff, the phone will act very oddly. For example, if I'm in the browser and scrolling up and down with my fingers, it would register as a press on the soft keys. This ONLY occurs when I hold the phone above my head to use the phone (imagine the phone upside down).
Any ideas? There seems to be something loose in the phone. I searched the forums and people guess that the accelerometer is loose, but it's normal.
I have this too. My phone is unusable if its flat, i.e if it's layed down on a table. If i do this the screen barely responds at all to touch.
Anyone else having this issue? It's pretty annoying!
I've been having a bit of a strange problem lately - sometimes my phone won't enter the lock screen. I'll turn the screen off, or let it go to sleep, and then when I go to turn the screen back on again (could be hours later), it goes directly to the home screen, and never see the lock screen. This makes it very easy to pocket-dial, or launch apps - my pocket started blaring music one day.
A restart seems to fix it for a little while, but within a day it will start doing the same thing, and I don't think I saw the lock screen at all yesterday. Does anyone have any idea what might be causing this? It started a couple months ago, but it seems to be more frequent now.
I am currently running Motorola Milestone, CM7 (kabaldan's beta with swap enabled). It was also happening some with CM7.2.1
Thanks in advance!
Anyone have any ideas?
Another interesting point is that after NOT seeing the lockscreen, and then playing around on the phone, I'll open one of the apps (say the browser), and THEN it will drop into the lockscreen. So right in the middle of doing stuff, it will make me have to unlock the phone. Can be a little frustrating.
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.
Hiya folks. Running CM10.1 stable on my targa (aka Droid Bionic). It was beautiful except for lack of nav dock support, a problematic Google Now (different problem, with workaround), and this particular problem, which I hope someone know what I am talking about...
When a call comes in and I answer by the slider, the screen goes black, whether or not I held the phone up to my head.
I cannot turn the screen back on. None of the buttons seem to do anything, though backlight for the 4 hard buttons does turn on indicating that some command was received by the touchscreen. Not even the power button will bring the screen back during the call.
If the other party hangs up, the phone goes back to normal.
With screen off, I can't hang up.
I can hang up if my Bluetooth headset was connected and I hang up with that.
I've searched all over and this issue seem to be a pretty popular issue last December across all CM 10 builds. However, I don't know if this was ever resolved for this build.
I can't find an option in the ROM to just flat "turn off face proximity detection" either. Or in any way to "tweak" it.
CPU-Z says my proximity sensor is working, so I guess it's just not calibrated properly for the dialer?
Can we get a "special hidden tweaker" much like the light sensor tweak for the auto-brightness levels?
Figured it out. It wasn't CM. It was Screebl and the stupid orientation sensor, and how the Launcher is fixed to portrait mode.
I think I had my phone laid down and it's at a diagonal so it's in landscape mode, and the phone's fine with that when it's just showing contacts. Screebl kicks in and determines that landscape, phone orientation says stay on, so screen stayed on. It was set to turn off the screen IMMEDIATELY when the orientation goes out of "viewing range". (Saving batteries, ya know).
When the call was answered, Screebl should have turned itself off (i.e. ignore input while call is in progress). But it didn't. The "answer the phone" screen flipped the display back to portrait mode. The phone, still laid flat, in "landscape", is now "out of viewing range", and Screebl turned off the screen.
Strange interaction among the various apps, yes.
I'm still trying to figure out how to make my Bionic, with extended battery last the whole day. Juicedefender Ultimate somehow just keeps turning the screen back on every X seconds (taking root control for SOMETHING) and Wakelock detector says the phone is not going into enough deep sleep (kinda like me, hahaha)
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.